Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - cuscotravelservices

Pages: 1 [2] 3 4 ... 7
16
wattOS R8 / Re: Package Installation and Upgrade Management
« on: November 21, 2014, 09:55:01 PM »
Best advise is to learn the hard way  ;)

https://www.debian.org/doc/manuals/debian-reference/ch02.en.html

Hi Blaze,

In this case, that's not suitable advice because the computer is not mine.

It will mostly be used by a 9 year old and occasionally her parents. Their primary languages are Spanish and Quechua and as I said they do not have advanced computer experience.

The sources.list file is as follows. This is also how it appears within the ISO.

Code: [Select]
# deb http://ftp.us.debian.org/debian/ wheezy main

deb http://ftp.us.debian.org/debian/ wheezy main non-free contrib
deb-src http://ftp.us.debian.org/debian/ wheezy main non-free contrib

deb http://security.debian.org/ wheezy/updates main contrib non-free
deb-src http://security.debian.org/ wheezy/updates main contrib non-free

# wheezy-updates, previously known as 'volatile'
deb http://ftp.us.debian.org/debian/ wheezy-updates main contrib non-free
deb-src http://ftp.us.debian.org/debian/ wheezy-updates main contrib non-free

# backports
deb http://ftp.us.debian.org/debian/ wheezy-backports main non-free contrib

The first line is also disabled in the MATÉ version.

Also, I have been doing this round of tests in the Live environment, with Persistence, but hopefully that shouldn't make any difference.

Thanks, Michael.

17
wattOS R8 / Re: Package Installation and Upgrade Management
« on: November 21, 2014, 04:07:06 PM »
This is wattOS lxde R8 you are on, right? Why do you have disabled "wheezy main"? Would you mind posting your source list?

Hi Blaze,

Yes, Lxde R8.

I didn't disable "wheezy main". It's just what I observed.

I'm on a bus at the moment. I'll post my sources.list this afternoon.

Thanks, Michael.

18
wattOS R8 / Re: Package Installation and Upgrade Management
« on: November 21, 2014, 12:41:05 AM »
People, this is getting very tedious.

Both Update Manager and Software Update still display packages that have been Locked within Synaptic.

Doesn't seem correct to me.

Hasta luego, Michael.

19
Feedback and Suggestions / Re: wattOS R9 Suggestions
« on: November 21, 2014, 12:18:52 AM »
WattOS R9 should be Debian Sid, Crunchbang and all other progressive Debian Distro's will be or are now , WattOS is quite an achievement, it works and works quite well, meaning all aspects of WattOS is fuctional, and fast.  Take Watt OS forward and make it a clear debut of awesome. Nuff said. zephyr

Debian Sid is unstable!

20
wattOS R8 / Re: Package Installation and Upgrade Management
« on: November 20, 2014, 08:51:29 PM »
The Software Settings applet for the gnome-packagekit shows "deb http://ftp.us.debian.org/debian/ wheezy main" as being disabled.

So, I looked in /etc/apt/sources.list which confirmed it as being disabled.

What does "stable/main (ftp.us.debian.org)", that I see in the List for Origin in Synaptic,refer to then?

Neither the gnome-packagekit nor the Update Manager have been maintained since 2012 according to their Change Logs.

Thanks, Michael.

21
Linux and desktops / Re: Broadband USB Modem not switching to modem mode
« on: November 20, 2014, 04:05:54 AM »
Here's the history and results of my testing. Short story - it's broken.

I approached things differently to what I did with MX-14 when I allowed all upgrades to be installed at once.

Before starting the upgrades I retrieved the following information from the Terminal.

lsusb
Code: [Select]
Bus 001 Device 005: ID 12d1:1506 Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard
dmesg | grep usb
Code: [Select]
[    5.380027] usb 1-4: new high-speed USB device number 4 using ehci-pci
[    5.512985] usb 1-4: New USB device found, idVendor=12d1, idProduct=14fe
[    5.512992] usb 1-4: New USB device strings: Mfr=2, Product=1, SerialNumber=0
[    5.512996] usb 1-4: Product: HUAWEI Mobile
[    5.512999] usb 1-4: Manufacturer: HUAWEI
[    5.514685] usb-storage 1-4:1.0: USB Mass Storage device detected
[    5.514836] scsi5 : usb-storage 1-4:1.0
[    5.515036] usb-storage 1-4:1.1: USB Mass Storage device detected
[    5.515182] scsi6 : usb-storage 1-4:1.1
[   18.914700] usb 1-4: USB disconnect, device number 4
[   24.176029] usb 1-4: new high-speed USB device number 5 using ehci-pci
[   24.309119] usb 1-4: New USB device found, idVendor=12d1, idProduct=1506
[   24.309127] usb 1-4: New USB device strings: Mfr=3, Product=2, SerialNumber=0
[   24.309131] usb 1-4: Product: HUAWEI Mobile
[   24.309134] usb 1-4: Manufacturer: HUAWEI
[   24.311259] usb-storage 1-4:1.4: USB Mass Storage device detected
[   24.314210] scsi7 : usb-storage 1-4:1.4
[   24.314459] usb-storage 1-4:1.5: USB Mass Storage device detected
[   24.316079] scsi8 : usb-storage 1-4:1.5
[   24.451918] usbcore: registered new interface driver usbserial
[   24.452266] usbcore: registered new interface driver usbserial_generic
[   24.452563] usbserial: USB Serial support registered for generic
[   24.464903] usbcore: registered new interface driver option
[   24.465454] usbserial: USB Serial support registered for GSM modem (1-port)
[   24.466162] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB0
[   24.466409] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB1
[   24.466624] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB2
[   24.582481] usbcore: registered new interface driver cdc_ncm
[   24.715026] usbcore: registered new interface driver cdc_wdm
[   24.751831] huawei_cdc_ncm 1-4:1.1 wwan0: register 'huawei_cdc_ncm' at usb-0000:00:10.4-4, Huawei CDC NCM device, 58:2c:80:13:92:63
[   24.751880] usbcore: registered new interface driver huawei_cdc_ncm

Next, using the Upgrade Manager in Safe Mode, I installed the Third Party upgrades for the packages I mentioned as being the problem in MX-14.

The following 2 images are the output from Upgrade Manager.





After the updates I rebooted.

lsusb produced the same output as before.

dmesg | grep usb
Code: [Select]
[    1.944056] usb 1-4: new high-speed USB device number 4 using ehci-pci
[    2.084869] usb 1-4: New USB device found, idVendor=12d1, idProduct=1506
[    2.084877] usb 1-4: New USB device strings: Mfr=3, Product=2, SerialNumber=0
[    2.084881] usb 1-4: Product: HUAWEI Mobile
[    2.084884] usb 1-4: Manufacturer: HUAWEI
[    2.086841] usb-storage 1-4:1.4: USB Mass Storage device detected
[    2.087131] scsi5 : usb-storage 1-4:1.4
[    2.087314] usb-storage 1-4:1.5: USB Mass Storage device detected
[    2.087469] scsi6 : usb-storage 1-4:1.5

[   19.968331] usbcore: registered new interface driver usbserial
[   19.968357] usbcore: registered new interface driver usbserial_generic
[   19.968375] usbserial: USB Serial support registered for generic
[   19.970912] usbcore: registered new interface driver option
[   19.970938] usbserial: USB Serial support registered for GSM modem (1-port)
[   20.040501] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB0
[   20.040727] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB1
[   20.040858] usb 1-4: GSM modem (1-port) converter now attached to ttyUSB2
[   20.550967] usbcore: registered new interface driver cdc_ncm
[   20.645337] usbcore: registered new interface driver cdc_wdm
[   20.691237] huawei_cdc_ncm 1-4:1.1 wwan0: register 'huawei_cdc_ncm' at usb-0000:00:10.4-4, Huawei CDC NCM device, 58:2c:80:13:92:63
[   20.691288] usbcore: registered new interface driver huawei_cdc_ncm

And as you can see the Modem was properly detected and I was able to connect etc.

So, next I installed the Security Upgrades which were the following:

Code: [Select]
libgcrypt11_1.5.0-5+deb7u2_i386.deb
libnss3_2%3a3.14.5-1+deb7u3_i386.deb
libmagic1_5.11-2+deb7u6_i386.deb
file_5.11-2+deb7u6_i386.deb
libcurl3-gnutls_7.26.0-1+wheezy11_i386.deb
iceweasel_31.2.0esr-3~deb7u1_i386.deb
wget_1.13.4-3+deb7u2_i386.deb
xulrunner-24.0_24.8.1esr-2~deb7u1_i386.deb
libmozjs24d_24.8.1esr-2~deb7u1_i386.deb
python-libxml2_2.8.0+dfsg1-7+wheezy2_i386.deb
libxml2_2.8.0+dfsg1-7+wheezy2_i386.deb
libtasn1-3_2.13-2+deb7u1_i386.deb
wpasupplicant_1.0-3+deb7u1_i386.deb
openssl_1.0.1e-2+deb7u13_i386.deb
libssl1.0.0_1.0.1e-2+deb7u13_i386.deb

Upgrade Manager produced the output you can see in the following image.



And now there was not an option available to Enable Broadband Modem and the Connection I had previously created wasn't listed as being available.

lsusb produced the following:

Code: [Select]
Bus 001 Device 004: ID 12d1:14fe Huawei Technologies Co., Ltd.
dmesg | grep usb produced the following:

Code: [Select]
[    5.384033] usb 1-4: new high-speed USB device number 4 using ehci-pci
[    5.525187] usb 1-4: New USB device found, idVendor=12d1, idProduct=14fe
[    5.525196] usb 1-4: New USB device strings: Mfr=2, Product=1, SerialNumber=0
[    5.525200] usb 1-4: Product: HUAWEI Mobile
[    5.525203] usb 1-4: Manufacturer: HUAWEI
[    5.526824] usb-storage 1-4:1.0: USB Mass Storage device detected
[    5.544374] scsi5 : usb-storage 1-4:1.0
[    5.544660] usb-storage 1-4:1.1: USB Mass Storage device detected
[    5.567617] scsi6 : usb-storage 1-4:1.1

So, it would appear, there is a conflict between one or more of the packages for the Security Upgrades and the Third Party Upgrades for Device and Hotplug Management or something missing from one of them.

The next thing I did was to downgrade the Upgrades, for Device and Hotplug Management, back to 204-8~bpo70+1 and BINGO the USB Modem is being properly detected (activated) again and able to connect to the Internet.

The following is the output from the Downgrade.

Code: [Select]
dpkg: warning: downgrading libgudev-1.0-0:i386 from 204-14~bpo70+1 to 204-8~bpo70+1
(Reading database ... 95621 files and directories currently installed.)
Preparing to replace libgudev-1.0-0:i386 204-14~bpo70+1 (using libgudev-1.0-0_204-8~bpo70+1_i386.deb) ...
Unpacking replacement libgudev-1.0-0:i386 ...
dpkg: warning: downgrading libsystemd-login0:i386 from 204-14~bpo70+1 to 204-8~bpo70+1
Preparing to replace libsystemd-login0:i386 204-14~bpo70+1 (using libsystemd-login0_204-8~bpo70+1_i386.deb) ...
Unpacking replacement libsystemd-login0:i386 ...
dpkg: warning: downgrading libudev1:i386 from 204-14~bpo70+1 to 204-8~bpo70+1
Preparing to replace libudev1:i386 204-14~bpo70+1 (using libudev1_204-8~bpo70+1_i386.deb) ...
Unpacking replacement libudev1:i386 ...
dpkg: warning: downgrading udev from 204-14~bpo70+1 to 204-8~bpo70+1
Preparing to replace udev 204-14~bpo70+1 (using udev_204-8~bpo70+1_i386.deb) ...
Unpacking replacement udev ...
Setting up libsystemd-login0:i386 (204-8~bpo70+1) ...
Setting up libudev1:i386 (204-8~bpo70+1) ...
Setting up udev (204-8~bpo70+1) ...
Installing new version of config file /etc/init.d/udev ...
Installing new version of config file /etc/init/udev-finish.conf ...
Installing new version of config file /etc/modprobe.d/fbdev-blacklist.conf ...
[ ok ] Stopping the hotplug events dispatcher: udevd.
[ ok ] Starting the hotplug events dispatcher: udevd.
update-initramfs: deferring update (trigger activated)
update-rc.d: warning: default start runlevel arguments (2 3 4 5) do not match udev Default-Start values (S)
update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match udev Default-Stop values (none)
update-rc.d: warning: default start runlevel arguments (2 3 4 5) do not match udev-finish Default-Start values (S)
update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match udev-finish Default-Stop values (none)
Setting up libgudev-1.0-0:i386 (204-8~bpo70+1) ...
Processing triggers for man-db ...
Processing triggers for initramfs-tools ...
update-initramfs: /boot/initrd.img-3.13-0.bpo.1-486 has been altered.
update-initramfs: Cannot update. Override with -t option.

Next I installed the Distribution Updates using Upgrade Manager with the Safe Upgrade option.

The modem is still correctly detected and activated.

I only have the remaining Third Party Upgrades to install before this round of testing is completed.

Hasta pronto, Michael.

22
Linux and desktops / Re: Broadband USB Modem not switching to modem mode
« on: November 20, 2014, 03:50:20 AM »
2nd image attachment

23
Linux and desktops / Re: Broadband USB Modem not switching to modem mode
« on: November 20, 2014, 03:23:33 AM »
Post for image attachment

24
wattOS R8 / Re: Package Installation and Upgrade Management
« on: November 20, 2014, 01:14:20 AM »
I just noticed, yesterday, that the Linux for older PCs (meta-package) 3.16+62~bpo70+1 package, that I mentioned in the previous post, is not shown in Upgrade Manager. It is shown in both Synaptic and Software Update. What would cause this apparent anomaly?

Thanks, Michael.

25
Linux and desktops / Re: Broadband USB Modem not switching to modem mode
« on: November 18, 2014, 01:25:18 AM »
Did the problem ever arise for you in wattOS? If so, did the linked workaround work for you or did you use another method to solve it?

Hi Blaze,

I'll give it a go on the Live USB version and report back.

Hasta pronto, Michael.

26
wattOS R8 / Package Installation and Upgrade Management
« on: November 18, 2014, 01:20:45 AM »
Hi Ron, Blaze et al,

Whilst looking for a solution to the translation problems with Update Manager, I discovered the following page.

Advice needed: update-manager in wheezy considered dangerous

So, I installed gnome-packagekit (3.4.2-2) which installs 3 applications (Software Update, Add/Remove Software and Software Settings).

Software Update appears to have to download the list of available updates every time it is opened. It only has 2 categories which are Security Updates and Other Updates. The list of Security Updates matches what I see in Update Manager.

There is no Third Party Updates category and those problem packages associated with the use of Broadband USB Modems are included under the category of Other Updates.

Software Update shows the same packages as Update Manager.

Translations appear to be working for all 3 applications for the gnome-packagekit package.

I noticed the following being suggested as an upgrade.
   Linux for older PCs (meta-package) 3.16+62~bpo70+1

Currently, the following 2 packages are installed.
Code: [Select]
    linux-image-3.13-0.bpo.1-486 (for use on PCs with a Single Processor not supporting PAE)
        Installed and Ultimate version are the same - 3.13.10-1~bpo70+1
    linux-image-486 (for use on PCs with a Single Processor not supporting PAE)
        Installed version is 3.13+56~bpo70+1 and Ultimate version is 3.16+62~bpo70+1

Should any of these be installed on a PC with a Pentium P4 that supports PAE and has the following characteristics?
Code: [Select]
coreinfo v3.21 - Dump information on system CPU and memory topology
Copyright (C) 2008-2013 Mark Russinovich
Sysinternals - www.sysinternals.com

              Intel(R) Pentium(R) 4 CPU 2.66GHz
x86 Family 15 Model 4 Stepping 1, GenuineIntel
HTT             *       Hyperthreading enabled
HYPERVISOR      -       Hypervisor is present
VMX             -       Supports Intel hardware-assisted virtualization
SVM             -       Supports AMD hardware-assisted virtualization
EM64T           *       Supports 64-bit mode

SMX             -       Supports Intel trusted execution
SKINIT          -       Supports AMD SKINIT

NX              -       Supports no-execute page protection
SMEP            -       Supports Supervisor Mode Execution Prevention
SMAP            -       Supports Supervisor Mode Access Prevention
PAGE1GB         -       Supports 1 GB large pages
PAE             *       Supports > 32-bit physical addresses
PAT             *       Supports Page Attribute Table
PSE             *       Supports 4 MB pages
PSE36           *       Supports > 32-bit address 4 MB pages
PGE             *       Supports global bit in page tables
SS              *       Supports bus snooping for cache operations
VME             *       Supports Virtual-8086 mode
RDWRFSGSBASE    -       Supports direct GS/FS base access

FPU             *       Implements i387 floating point instructions
MMX             *       Supports MMX instruction set
MMXEXT          -       Implements AMD MMX extensions
3DNOW           -       Supports 3DNow! instructions
3DNOWEXT        -       Supports 3DNow! extension instructions
SSE             *       Supports Streaming SIMD Extensions
SSE2            *       Supports Streaming SIMD Extensions 2
SSE3            *       Supports Streaming SIMD Extensions 3
SSSE3           -       Supports Supplemental SIMD Extensions 3
SSE4a           -       Supports Sreaming SIMDR Extensions 4a
SSE4.1          -       Supports Streaming SIMD Extensions 4.1
SSE4.2          -       Supports Streaming SIMD Extensions 4.2

AES             -       Supports AES extensions
AVX             -       Supports AVX intruction extensions
FMA             -       Supports FMA extensions using YMM state
MSR             *       Implements RDMSR/WRMSR instructions
MTRR            *       Supports Memory Type Range Registers
XSAVE           -       Supports XSAVE/XRSTOR instructions
OSXSAVE         -       Supports XSETBV/XGETBV instructions
RDRAND          -       Supports RDRAND instruction
RDSEED          -       Supports RDSEED instruction

CMOV            *       Supports CMOVcc instruction
CLFSH           *       Supports CLFLUSH instruction
CX8             *       Supports compare and exchange 8-byte instructions
CX16            *       Supports CMPXCHG16B instruction
BMI1            -       Supports bit manipulation extensions 1
BMI2            -       Supports bit manipulation extensions 2
ADX             -       Supports ADCX/ADOX instructions
DCA             -       Supports prefetch from memory-mapped device
F16C            -       Supports half-precision instruction
FXSR            *       Supports FXSAVE/FXSTOR instructions
FFXSR           -       Supports optimized FXSAVE/FSRSTOR instruction
MONITOR         *       Supports MONITOR and MWAIT instructions
MOVBE           -       Supports MOVBE instruction
ERMSB           -       Supports Enhanced REP MOVSB/STOSB
PCLULDQ         -       Supports PCLMULDQ instruction
POPCNT          -       Supports POPCNT instruction
LZCNT           -       Supports LZCNT instruction
SEP             *       Supports fast system call instructions
LAHF-SAHF       -       Supports LAHF/SAHF instructions in 64-bit mode
HLE             -       Supports Hardware Lock Elision instructions
RTM             -       Supports Restricted Transactional Memory instructions

DE              *       Supports I/O breakpoints including CR4.DE
DTES64          *       Can write history of 64-bit branch addresses
DS              *       Implements memory-resident debug buffer
DS-CPL          *       Supports Debug Store feature with CPL
PCID            -       Supports PCIDs and settable CR4.PCIDE
INVPCID         -       Supports INVPCID instruction
PDCM            -       Supports Performance Capabilities MSR
RDTSCP          -       Supports RDTSCP instruction
TSC             *       Supports RDTSC instruction
TSC-DEADLINE    -       Local APIC supports one-shot deadline timer
TSC-INVARIANT   -       TSC runs at constant rate
xTPR            *       Supports disabling task priority messages

EIST            -       Supports Enhanced Intel Speedstep
ACPI            *       Implements MSR for power management
TM              *       Implements thermal monitor circuitry
TM2             *       Implements Thermal Monitor 2 control
APIC            *       Implements software-accessible local APIC
x2APIC          -       Supports x2APIC

CNXT-ID         *       L1 data cache mode adaptive or BIOS

MCE             *       Supports Machine Check, INT18 and CR4.MCE
MCA             *       Implements Machine Check Architecture
PBE             *       Supports use of FERR#/PBE# pin

PSN             -       Implements 96-bit processor serial number

PREFETCHW       -       Supports PREFETCHW instruction

Maximum implemented CPUID leaves: 00000005 (Basic), 80000008 (Extended).

Logical to Physical Processor Map:
*  Physical Processor 0

Logical Processor to Socket Map:
*  Socket 0

Logical Processor to NUMA Node Map:
*  NUMA Node 0

Logical Processor to Cache Map:
*  Data Cache          0, Level 1,   16 KB, Assoc   8, LineSize  64
*  Unified Cache       0, Level 2,    1 MB, Assoc   8, LineSize 128

This all leaves me wondering as to how to advise new Linux Users, who do not have advanced computer experience, as to the best way to manage Package Installations and Updates instead of blindly accepting what is presented by the various Package/Update Managers.

Given that Update Manager has a category for Third Party Updates, is that the preferred application, at present, for managing updates for non-technical users? If so, then, I still need a solution to the translation problems with it.

For myself, when testing changes to the Operating System (OS), I have been using partclone from the Terminal command line of the Live Persistent version I have on a USB Flash Drive. I am thinking that the easiest way, for non-technical people, to manage things in case an installation or upgrade needs to be reversed is to use a graphical backup utility. Which would you recommend? Can these be used to backup and restore the partition of an active OS?

Otherwise, the other option, given that I will be remastering the installation once I have it all configured and configuring a USB Flash Drive with persistence with the remastered ISO as a backup system, is to document instructions to do what I have been doing with partclone but non-technical users may find that to be rather tedious and inconvenient.

With Synaptic (version 0.75.13), I discovered that Filters can't be deleted. Would it be safe to install version 0.81.2 from Jessie which fixes this problem?
http://metadata.ftp-master.debian.org/changelogs/main/s/synaptic/unstable_changelog

After installing gnome-packagekit, Synaptic now has a Rapid Filter feature in the Toolbar as I had seen when using Mint 16 KDE. So, that's 1 benefit to installing gnome-packagekit.

Does anyone have a clue as to what Dependency, installed for the gnome-packagekit, would have caused that change in Synaptic? The version number of Synaptic was not changed.

Thanks, Michael.

27
wattOS R8 / Re: Update Manager - Third Party Updates?
« on: November 18, 2014, 12:22:20 AM »
There are third-party repos developed to work with Debian. Or build from source.But not Ubuntu PPAs for example, it is high risk of borking.

Hi Blaze,

The packages that are listed under the category of "Third Party Updates" are as follows.

 
Code: [Select]
libgudev-1.0-0 : GObject-based wrapper library for libudev
  Status:                 Installed (upgradeable)
  Priority:               optional
  Section:                Libraries
  Installed Version:      204-8~bpo70+1
  Last available version: 204-14~bpo70+1


libldb1 : LDAP-like embedded database - shared library
  Status:                 Installed (upgradeable)
  Priority:               optional
  Section:                Libraries
  Installed Version:      1:1.1.16-1~bpo70+1
  Last available version: 1:1.1.17-1~bpo70+1


libsmbclient : shared library for communication with SMB/CIFS servers
  Status:                 Installed (upgradeable)
  Priority:               optional
  Section:                Libraries
  Installed Version:      2:4.1.6+dfsg-1~bpo70+1
  Last available version: 2:4.1.11+dfsg-1~bpo70+1


libsystemd-login0 : systemd login utility library
  Status:                 Installed (upgradeable)
  Priority:               optional
  Section:                Libraries
  Installed Version:      204-8~bpo70+1
  Last available version: 204-14~bpo70+1


libtalloc2 : Memory allocator based on hierarchical group
  Status:                 Installed (upgradeable)
  Priority:               optional
  Section:                Libraries
  Installed Version:      2.1.0-1~bpo70+1
  Last available version: 2.1.1-1~bpo70+1


libtdb1 : Trivial Database - shared library
  Status:                 Installed (upgradeable)
  Priority:               optional
  Section:                Libraries
  Installed Version:      1.2.12-1~bpo70+1
  Last available version: 1.3.0-1.1~bpo70+1


libtevent0 : talloc-based event loop library - shared library
  Status:                 Installed (upgradeable)
  Priority:               optional
  Section:                Libraries
  Installed Version:      0.9.19-1~bpo70+1
  Last available version: 0.9.21-1~bpo70+1


libudev1 : libudev shared library
  Status:                 Installed (upgradeable)
  Priority:               important
  Section:                Libraries
  Installed Version:      204-8~bpo70+1
  Last available version: 204-14~bpo70+1


libwbclient0 : Samba winbind client library
  Status:                 Installed (upgradeable)
  Priority:               optional
  Section:                Libraries
  Installed Version:      2:4.1.6+dfsg-1~bpo70+1
  Last available version: 2:4.1.11+dfsg-1~bpo70+1


python-talloc : hierarchical pool based memory allocator - Python bindings
  Status:                 Installed (upgradeable)
  Priority:               optional
  Section:                Python Programming Language
  Installed Version:      2.1.0-1~bpo70+1
  Last available version: 2.1.1-1~bpo70+1


samba-libs : Samba core libraries
  Status:                 Installed (upgradeable)
  Priority:               optional
  Section:                Libraries
  Installed Version:      2:4.1.6+dfsg-1~bpo70+1
  Last available version: 2:4.1.11+dfsg-1~bpo70+1


udev : /dev/ and hotplug management daemon
  Status:                 Installed (upgradeable)
  Priority:               important
  Section:                System Administration
  Installed Version:      204-8~bpo70+1
  Last available version: 204-14~bpo70+1

How does Update Manager know to categorise them as Third Party?

Thanks, Michael.

28
wattOS R8 / Update Manager - Third Party Updates?
« on: November 16, 2014, 08:36:24 PM »
Hi Ron, Blaze et al,

With reference to the Broadband USB Modem not switching to modem mode topic I started, for example, would it be best to assume that Third Party Updates should not be installed?

Thanks, Michael.

29
wattOS R8 / Re: Update Manager Window - Displayed Language not 100% correct
« on: November 16, 2014, 01:37:05 AM »
Hi Ron, Blaze et al,

I've tried looking for clues as to the cause of the problem but Update Manager is not retrieving the translations for some of the Strings in code nor for the interface objects which have been specified as translatable. Only the "Stock Buttons" appear to be translated.

Can someone point me in the right direction to solve this?

Thanks, Michael.

30
wattOS R8 / Re: [Solved] - Best Way to Prevent Bluetooth from Starting?
« on: November 14, 2014, 07:44:25 PM »
Thanks seppalta!

To stop bluetooth from runing on your computer, enter the following into the terminal:
                 
Code: [Select]
sudo update-rc.d bluetooth remove.

Curious to know what this actually does, I discovered that the above removes the entries for bluetooth from the files ".depend.start" and ".depend.stop".


To restart bluetooth:
                 
Code: [Select]
sudo update-rc.d bluetooth defaults

The above inserts the entries for bluetooth into the files ".depend.start" and ".depend.stop".


To get the exact names of the processes on your computer, install the little tool rcconf, and run in the terminal:
                 
Code: [Select]
sudo rcconf Any of these processes can be stopped or restarted using the recipe just described for bluetooth.
http://lxlinux.com/#21

Will do.

When I do a Remaster, will the change be incorporated?

Hasta luego, Michael.

Pages: 1 [2] 3 4 ... 7