[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
The problem still persists with network-manager-gnome 1.2.2 after all. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
I installed network-manager-gnome version 1.2.2 available in yakkety. After preliminary testing (a couple of suspend cycles) it seems to have fixed the problem! You can download binaries from https://launchpad.net/ubuntu/yakkety/+source/network-manager-applet or build it on xenial like this: # apt-get install devscripts # apt-get build-dep network-manager-applet $ dget http://archive.ubuntu.com/ubuntu/pool/main/n/network-manager-applet/network-manager-applet_1.2.2-0ubuntu1.dsc $ dpkg-source -x network-manager-applet_1.2.2-0ubuntu1.dsc $ cd network-manager-applet-1.2.2 $ dpkg-buildpackage -uc -us # dpkg -i *.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
network-manager{,-gnome} both 1.2.0-0ubuntu0.16.04.3, problem still
persists.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after re-enabling wifi
Status in NetworkManager:
Confirmed
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
after re enabling wifi, up-down arrows just like wired network. cannot
see any wifi ssid.
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error
Hi! Some conflicts still remain in the /etc/signon-ui/webkit-options.d directory. Comment #59 has a fix proposal though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libaccounts-glib in Ubuntu. https://bugs.launchpad.net/bugs/1451728 Title: [master] kde-config-telepathy-accounts package install error Status in Kubuntu PPA: Fix Released Status in meta-telepathy: Fix Released Status in kaccounts-integration package in Ubuntu: In Progress Status in kaccounts-providers package in Ubuntu: Confirmed Status in ktp-accounts-kcm package in Ubuntu: Triaged Status in libaccounts-glib package in Ubuntu: Fix Released Status in kaccounts-providers source package in Wily: Triaged Status in ktp-accounts-kcm source package in Wily: Triaged Bug description: Installing from Kubuntu 15.04 backports: Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) over (0.9.0-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/facebook-im.service', which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) To manage notifications about this bug go to: https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error
Indeed, the patches are not applied. Also, the patch upstream_allow_install_other_providers.patch does not apply since the target file differs from what the patch provider used. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libaccounts-glib in Ubuntu. https://bugs.launchpad.net/bugs/1451728 Title: [master] kde-config-telepathy-accounts package install error Status in Kubuntu PPA: Fix Released Status in meta-telepathy: Fix Released Status in kaccounts-integration package in Ubuntu: Fix Released Status in kaccounts-providers package in Ubuntu: Triaged Status in ktp-accounts-kcm package in Ubuntu: Triaged Status in libaccounts-glib package in Ubuntu: Fix Released Status in kaccounts-providers source package in Wily: Triaged Status in ktp-accounts-kcm source package in Wily: Triaged Bug description: Installing from Kubuntu 15.04 backports: Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) over (0.9.0-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/facebook-im.service', which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) To manage notifications about this bug go to: https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1564951] Re: systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument
Whoops, 4.4.0-17 is still in -proposed :) Better file a bug against it then... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1564951 Title: systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument Status in systemd package in Ubuntu: Confirmed Bug description: After upgrading systemd from 229-3ubuntu1 to 229-3ubuntu2, I noticed this on one of my VM: systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument systemd-timesyncd says it was able to sync the clock but also report failures: # systemctl status systemd-timesyncd ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-timesyncd.service.d └─disable-with-time-daemon.conf Active: active (running) since Fri 2016-04-01 10:55:09 EDT; 3s ago Docs: man:systemd-timesyncd.service(8) Main PID: 2523 (systemd-timesyn) Status: "Synchronized to time server 172.24.21.1:123 (ntp.ubuntu.com)." Tasks: 2 (limit: 512) CGroup: /system.slice/systemd-timesyncd.service └─2523 /lib/systemd/systemd-timesyncd Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd[1]: Starting Network Time Synchronization... Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd[1]: Started Network Time Synchronization. Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd-timesyncd[2523]: Failed to call clock_adjtime(): Invalid argument Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd-timesyncd[2523]: Synchronized to time server 172.24.21.1:123 (ntp.ubuntu.com). The clock_adjtime error repeats every ~30 seconds after that. Oddly, I cannot reproduce this on my physical machine, only on this VM. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-3ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Fri Apr 1 10:50:35 2016 Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=UUID=ce88e7e4-836f-42d6-8e39-4bc8abd23541 ro console=hvc0 kaslr SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-2.0:cvnBochs:ct1:cvr: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-2.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1564951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1564951] Re: systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument
This seems to be a kernel issue. On my both laptops, with the current 4.4.0-17 kernel systemd-timesyncd fails to adjust time or does it only once, which is interesting. With the previous kernel 4.4.0-16 it works just fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1564951 Title: systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument Status in systemd package in Ubuntu: Confirmed Bug description: After upgrading systemd from 229-3ubuntu1 to 229-3ubuntu2, I noticed this on one of my VM: systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument systemd-timesyncd says it was able to sync the clock but also report failures: # systemctl status systemd-timesyncd ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-timesyncd.service.d └─disable-with-time-daemon.conf Active: active (running) since Fri 2016-04-01 10:55:09 EDT; 3s ago Docs: man:systemd-timesyncd.service(8) Main PID: 2523 (systemd-timesyn) Status: "Synchronized to time server 172.24.21.1:123 (ntp.ubuntu.com)." Tasks: 2 (limit: 512) CGroup: /system.slice/systemd-timesyncd.service └─2523 /lib/systemd/systemd-timesyncd Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd[1]: Starting Network Time Synchronization... Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd[1]: Started Network Time Synchronization. Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd-timesyncd[2523]: Failed to call clock_adjtime(): Invalid argument Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd-timesyncd[2523]: Synchronized to time server 172.24.21.1:123 (ntp.ubuntu.com). The clock_adjtime error repeats every ~30 seconds after that. Oddly, I cannot reproduce this on my physical machine, only on this VM. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-3ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Fri Apr 1 10:50:35 2016 Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=UUID=ce88e7e4-836f-42d6-8e39-4bc8abd23541 ro console=hvc0 kaslr SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-2.0:cvnBochs:ct1:cvr: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-2.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1564951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1564951] Re: systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument
Unable to synchronize time on two different laptops. Works in a VMware Fusion virtual machine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1564951 Title: systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument Status in systemd package in Ubuntu: Confirmed Bug description: After upgrading systemd from 229-3ubuntu1 to 229-3ubuntu2, I noticed this on one of my VM: systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument systemd-timesyncd says it was able to sync the clock but also report failures: # systemctl status systemd-timesyncd ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-timesyncd.service.d └─disable-with-time-daemon.conf Active: active (running) since Fri 2016-04-01 10:55:09 EDT; 3s ago Docs: man:systemd-timesyncd.service(8) Main PID: 2523 (systemd-timesyn) Status: "Synchronized to time server 172.24.21.1:123 (ntp.ubuntu.com)." Tasks: 2 (limit: 512) CGroup: /system.slice/systemd-timesyncd.service └─2523 /lib/systemd/systemd-timesyncd Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd[1]: Starting Network Time Synchronization... Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd[1]: Started Network Time Synchronization. Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd-timesyncd[2523]: Failed to call clock_adjtime(): Invalid argument Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd-timesyncd[2523]: Synchronized to time server 172.24.21.1:123 (ntp.ubuntu.com). The clock_adjtime error repeats every ~30 seconds after that. Oddly, I cannot reproduce this on my physical machine, only on this VM. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-3ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Fri Apr 1 10:50:35 2016 Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=UUID=ce88e7e4-836f-42d6-8e39-4bc8abd23541 ro console=hvc0 kaslr SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-2.0:cvnBochs:ct1:cvr: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-2.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1564951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553147] Re: xenial preseed cannot set keyboard layout
Works for me now. I have this in the installer parameters: keymap=fi console-setup/ask_detect=false -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1553147 Title: xenial preseed cannot set keyboard layout Status in console-setup package in Ubuntu: Incomplete Bug description: Using network booted preseed with the following lines to configure keyboard layout: d-i console-setup/ask_detect false d-i keyboard-configuration/layoutcode string de d-i keyboard-configuration/layout select German d-i keyboard-configuration/modelcode string pc105 System comes up with US keyboard only (see screenshot). Content of /etc/default/keyboard: XKBMODEL="pc105" XKBLAYOUT="" XKBVARIANT="" XKBOPTIONS="" BACKSPACE="guess" Content of /etc/default/console-setup: ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" CODESET="guess" FONTFACE="Fixed" FONTSIZE="8x16" VIDEOMODE= The same preseed file works on wily and successfully configures a German keyboard layout. The full preseed file can be found at https://github.com/jschule/ubuntu/blob/gh-pages/preseed/jts.txt Please advice how to set German keyboard layout with preseed installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1553147/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553147] Re: xenial preseed cannot set keyboard layout
Sorry, I'm unable to verify or test for a week, but IIRC setting it as
parameter (or using the alias keymap=fi) did actually change the layout
in the installer console.
However the changes were not saved in the target system in
/etc/default/keyboard as XKBLAYOUT="fi". I also tried setting these
items in preseed without success:
{d-i,keyboard-configuration} keyboard-configuration/{layout,layoutcode
,xkb-keymap,variant}
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1553147
Title:
xenial preseed cannot set keyboard layout
Status in console-setup package in Ubuntu:
Incomplete
Bug description:
Using network booted preseed with the following lines to configure
keyboard layout:
d-i console-setup/ask_detect false
d-i keyboard-configuration/layoutcode string de
d-i keyboard-configuration/layout select German
d-i keyboard-configuration/modelcode string pc105
System comes up with US keyboard only (see screenshot).
Content of /etc/default/keyboard:
XKBMODEL="pc105"
XKBLAYOUT=""
XKBVARIANT=""
XKBOPTIONS=""
BACKSPACE="guess"
Content of /etc/default/console-setup:
ACTIVE_CONSOLES="/dev/tty[1-6]"
CHARMAP="UTF-8"
CODESET="guess"
FONTFACE="Fixed"
FONTSIZE="8x16"
VIDEOMODE=
The same preseed file works on wily and successfully configures a
German keyboard layout.
The full preseed file can be found at
https://github.com/jschule/ubuntu/blob/gh-pages/preseed/jts.txt
Please advice how to set German keyboard layout with preseed
installation.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1553147/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1267059] Re: "Unattended-Upgrade::Remove-Unused-Dependencies" does not work
Happens on Trusty and Xenial too. There are a few bug reports about it marking kernels as manually installed. They may be related. Here's a test case anyway: Normal run: # apt-get install lolcat # apt-mark showmanual lolcat lolcat # apt-mark auto lolcat lolcat set to automatically installed. # unattended-upgrade # dpkg -l lolcat dpkg-query: no packages found matching lolcat With --dry-run: # apt-get install lolcat # apt-mark showmanual lolcat lolcat # apt-mark auto lolcat lolcat set to automatically installed. # unattended-upgrade --dry-run # dpkg -l lolcat ii lolcat ... # apt-mark showmanual lolcat lolcat -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1267059 Title: "Unattended-Upgrade::Remove-Unused-Dependencies" does not work Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Precise: Fix Released Status in unattended-upgrades source package in Trusty: Fix Released Bug description: I have a system that runs unattended-upgrades just fine. Now i want to automate removal of old kernels and kernel header packages that are accumulating otherwise. So i set 'Unattended-Upgrade::Remove-Unused- Dependencies "true";'. But it doesn't work. Details: Lots of stuff pending autoremoval: $ apt-get --assume-no autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED linux-headers-3.2.0-38 linux-headers-3.2.0-38-generic linux-headers-3.2.0-39 linux-headers-3.2.0-39-generic linux-headers-3.2.0-40 linux-headers-3.2.0-40-generic linux-headers-3.2.0-41 linux-headers-3.2.0-41-generic linux-headers-3.2.0-43 linux-headers-3.2.0-43-generic linux-headers-3.2.0-44 linux-headers-3.2.0-44-generic linux-headers-3.2.0-45 linux-headers-3.2.0-45-generic linux-headers-3.2.0-48 linux-headers-3.2.0-48-generic linux-headers-3.2.0-51 linux-headers-3.2.0-51-generic linux-headers-3.2.0-52 linux-headers-3.2.0-52-generic linux-headers-3.2.0-53 linux-headers-3.2.0-53-generic linux-headers-3.2.0-54 linux-headers-3.2.0-54-generic linux-headers-3.2.0-55 linux-headers-3.2.0-55-generic linux-headers-3.2.0-56 linux-headers-3.2.0-56-generic linux-image-3.2.0-39-generic linux-image-3.2.0-40-generic linux-image-3.2.0-41-generic linux-image-3.2.0-43-generic linux-image-3.2.0-44-generic linux-image-3.2.0-45-generic linux-image-3.2.0-48-generic linux-image-3.2.0-51-generic linux- image-3.2.0-52-generic linux-image-3.2.0-53-generic linux-image-3.2.0-54-generic linux-image-3.2.0-55-generic linux-image-3.2.0-56-generic 0 upgraded, 0 newly installed, 41 to remove and 13 not upgraded. After this operation, 2,893 MB disk space will be freed. Do you want to continue [Y/n]? N Abort. Note that the majority of these packages have been installed by unattended-upgrades from precise-security. According to the comments within/etc/apt/apt.conf.d/50unattended- upgrades, this should automate autoremoval: // Do automatic removal of new unused dependencies after the upgrade // (equivalent to apt-get autoremove) Unattended-Upgrade::Remove-Unused-Dependencies "true"; but nothing happens (note the line "Packages that are auto removed: '' ": $ unattended-upgrades --debug --dry-run Initial blacklisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=precise-security'] adjusting candidate version: '' adjusting candidate version: '' adjusting candidate version: '' adjusting candidate version: '' adjusting candidate version: '' adjusting candidate version: '' Checking: bc ([""]) Checking: grub-common ([""]) Checking: grub-pc ([""]) Checking: grub-pc-bin ([""]) Checking: grub2-common ([""]) Checking: iproute ([""]) Checking: landscape-common ([""]) pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) blacklist: [] Packages that are auto removed: '' InstCount=0 DelCount=0 BrokenCout=0 No packages found that can be upgraded unattended I am using unattended-upgrades-0.76ubuntu1 on Ubuntu 12.04.3 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1267059/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1267059] Re: "Unattended-Upgrade::Remove-Unused-Dependencies" does not work
I tested on Precise. When running with --dry-run, unattended-upgrade marks the autoremovable packages as manually installed. This prevents them from being removed when running without --dry-run afterwards. Check "apt-mark showmanual". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1267059 Title: "Unattended-Upgrade::Remove-Unused-Dependencies" does not work Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Precise: Fix Released Status in unattended-upgrades source package in Trusty: Fix Released Bug description: I have a system that runs unattended-upgrades just fine. Now i want to automate removal of old kernels and kernel header packages that are accumulating otherwise. So i set 'Unattended-Upgrade::Remove-Unused- Dependencies "true";'. But it doesn't work. Details: Lots of stuff pending autoremoval: $ apt-get --assume-no autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED linux-headers-3.2.0-38 linux-headers-3.2.0-38-generic linux-headers-3.2.0-39 linux-headers-3.2.0-39-generic linux-headers-3.2.0-40 linux-headers-3.2.0-40-generic linux-headers-3.2.0-41 linux-headers-3.2.0-41-generic linux-headers-3.2.0-43 linux-headers-3.2.0-43-generic linux-headers-3.2.0-44 linux-headers-3.2.0-44-generic linux-headers-3.2.0-45 linux-headers-3.2.0-45-generic linux-headers-3.2.0-48 linux-headers-3.2.0-48-generic linux-headers-3.2.0-51 linux-headers-3.2.0-51-generic linux-headers-3.2.0-52 linux-headers-3.2.0-52-generic linux-headers-3.2.0-53 linux-headers-3.2.0-53-generic linux-headers-3.2.0-54 linux-headers-3.2.0-54-generic linux-headers-3.2.0-55 linux-headers-3.2.0-55-generic linux-headers-3.2.0-56 linux-headers-3.2.0-56-generic linux-image-3.2.0-39-generic linux-image-3.2.0-40-generic linux-image-3.2.0-41-generic linux-image-3.2.0-43-generic linux-image-3.2.0-44-generic linux-image-3.2.0-45-generic linux-image-3.2.0-48-generic linux-image-3.2.0-51-generic linux- image-3.2.0-52-generic linux-image-3.2.0-53-generic linux-image-3.2.0-54-generic linux-image-3.2.0-55-generic linux-image-3.2.0-56-generic 0 upgraded, 0 newly installed, 41 to remove and 13 not upgraded. After this operation, 2,893 MB disk space will be freed. Do you want to continue [Y/n]? N Abort. Note that the majority of these packages have been installed by unattended-upgrades from precise-security. According to the comments within/etc/apt/apt.conf.d/50unattended- upgrades, this should automate autoremoval: // Do automatic removal of new unused dependencies after the upgrade // (equivalent to apt-get autoremove) Unattended-Upgrade::Remove-Unused-Dependencies "true"; but nothing happens (note the line "Packages that are auto removed: '' ": $ unattended-upgrades --debug --dry-run Initial blacklisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=precise-security'] adjusting candidate version: '' adjusting candidate version: '' adjusting candidate version: '' adjusting candidate version: '' adjusting candidate version: '' adjusting candidate version: '' Checking: bc ([""]) Checking: grub-common ([""]) Checking: grub-pc ([""]) Checking: grub-pc-bin ([""]) Checking: grub2-common ([""]) Checking: iproute ([""]) Checking: landscape-common ([""]) pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) blacklist: [] Packages that are auto removed: '' InstCount=0 DelCount=0 BrokenCout=0 No packages found that can be upgraded unattended I am using unattended-upgrades-0.76ubuntu1 on Ubuntu 12.04.3 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1267059/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1267059] Re: "Unattended-Upgrade::Remove-Unused-Dependencies" does not work
For what it's worth; I've worked around this by installing the version from wily on some trusty machines. So far so good. The machines upgrade daily and old kernels and their headers are removed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1267059 Title: "Unattended-Upgrade::Remove-Unused-Dependencies" does not work Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: I have a system that runs unattended-upgrades just fine. Now i want to automate removal of old kernels and kernel header packages that are accumulating otherwise. So i set 'Unattended-Upgrade::Remove-Unused- Dependencies "true";'. But it doesn't work. Details: Lots of stuff pending autoremoval: $ apt-get --assume-no autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED linux-headers-3.2.0-38 linux-headers-3.2.0-38-generic linux-headers-3.2.0-39 linux-headers-3.2.0-39-generic linux-headers-3.2.0-40 linux-headers-3.2.0-40-generic linux-headers-3.2.0-41 linux-headers-3.2.0-41-generic linux-headers-3.2.0-43 linux-headers-3.2.0-43-generic linux-headers-3.2.0-44 linux-headers-3.2.0-44-generic linux-headers-3.2.0-45 linux-headers-3.2.0-45-generic linux-headers-3.2.0-48 linux-headers-3.2.0-48-generic linux-headers-3.2.0-51 linux-headers-3.2.0-51-generic linux-headers-3.2.0-52 linux-headers-3.2.0-52-generic linux-headers-3.2.0-53 linux-headers-3.2.0-53-generic linux-headers-3.2.0-54 linux-headers-3.2.0-54-generic linux-headers-3.2.0-55 linux-headers-3.2.0-55-generic linux-headers-3.2.0-56 linux-headers-3.2.0-56-generic linux-image-3.2.0-39-generic linux-image-3.2.0-40-generic linux-image-3.2.0-41-generic linux-image-3.2.0-43-generic linux-image-3.2.0-44-generic linux-image-3.2.0-45-generic linux-image-3.2.0-48-generic linux-image-3.2.0-51-generic linux- image-3.2.0-52-generic linux-image-3.2.0-53-generic linux-image-3.2.0-54-generic linux-image-3.2.0-55-generic linux-image-3.2.0-56-generic 0 upgraded, 0 newly installed, 41 to remove and 13 not upgraded. After this operation, 2,893 MB disk space will be freed. Do you want to continue [Y/n]? N Abort. Note that the majority of these packages have been installed by unattended-upgrades from precise-security. According to the comments within/etc/apt/apt.conf.d/50unattended- upgrades, this should automate autoremoval: // Do automatic removal of new unused dependencies after the upgrade // (equivalent to apt-get autoremove) Unattended-Upgrade::Remove-Unused-Dependencies "true"; but nothing happens (note the line "Packages that are auto removed: '' ": $ unattended-upgrades --debug --dry-run Initial blacklisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=precise-security'] adjusting candidate version: '' adjusting candidate version: '' adjusting candidate version: '' adjusting candidate version: '' adjusting candidate version: '' adjusting candidate version: '' Checking: bc ([""]) Checking: grub-common ([""]) Checking: grub-pc ([""]) Checking: grub-pc-bin ([""]) Checking: grub2-common ([""]) Checking: iproute ([""]) Checking: landscape-common ([""]) pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) blacklist: [] Packages that are auto removed: '' InstCount=0 DelCount=0 BrokenCout=0 No packages found that can be upgraded unattended I am using unattended-upgrades-0.76ubuntu1 on Ubuntu 12.04.3 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1267059/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 445333] Re: remember password on printing to windows printers does not work
Works perfectly for me. With an empty keychain, Firefox prompts for credentials and saves them in the keychain, and printing just works. Gedit (GTK3 application) is then able to use the same credentials, although they are a bit different from what GTK3 saves to the keychain. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/445333 Title: remember password on printing to windows printers does not work Status in GTK+ GUI Toolkit: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+2.0 source package in Trusty: Fix Committed Status in gtk+3.0 source package in Trusty: Fix Released Bug description: [Impact] * Passwords for printers are not stored and the users are required to retype it with every print job for password protected printers [Test Case] * Configure a remote (shared via SMB), password-protected printer. * Request a print job. * Each subsequent job will require retyping the password. [Regression Potential] * Cherry-pick from upstream (present in Gtk+3.13.8). * Minor conflict resolution needed (line numbers changed) [Other Info] * Original bug description: i am printing from my ubuntu karmic to a windows box. everytime i print i get asked to input username and password to windows box, then the document gets printed. there is a "remember password" checkbox, but it keeps asking me when printing the next document. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/445333/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350357] Re: Support disabling of user switching per seat
That is the Trusty version from ubuntu-desktop PPA, all updates are
installed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1350357
Title:
Support disabling of user switching per seat
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Fix Released
Status in “lightdm” package in Ubuntu:
Fix Released
Status in “lightdm” source package in Trusty:
Confirmed
Status in “lightdm” source package in Utopic:
Fix Released
Bug description:
Let me start by saying it's possible I'm missing some subtleties here,
and if so, I'd be happy to get a more detailed explanation.
In LightDM 1.10.1 (Trusty), unity seats are forced to enable user
switching (in seat-unity.c). However, I think this is something that
should be configurable in the display manager. In a public computing
environment, fast-user-switching is undesirable, as it interferes with
serial re-usability and various cleanup tasks. Most public computing
labs want to maintain a 1-1 relationship between individuals and
workstations, and a workstation should either be in use by one user,
or not in use at all. In the past, our site has accomplished this in
various desktop environment configurations (such as the
org.gnome.desktop.lockdown gsettings, etc). Unfortunately, most of
these settings are ignored in Unity (I have filed separate bugs about
those).
Obviously, there are workarounds, including stealing all the other
VTs, or playing stupid D-Bus games, or wrapping X. Currently, our
preferred ("preferred") solution is to have our custom greeter check
logind and refuse to do anything other than unlock the existing
session if a user is already logged in on an X seat, but that's not
ideal, because you still end up with a second greeter running, and in
fact that becomes the primary greeter when the original user logs out.
That having been said, I believe it is the system administrator's
prerogative to dictate that there shall be one and only one seat
available on any given workstation, and instruct LightDM not to spawn
any additional ones. It would be great if this was added in future
releases. Alternatively, if that's not possible because of Unity
design, it would be great if there was a way for a greeter to say to
lightdm "I'm done, this seat is shutting down, switch back to an
original session." (And obviously, doing that if there is no other
session to switch to would be an error).
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1350357/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350357] Re: Support disabling of user switching per seat
Using lightdm 1.10.2, I tested setting allow-user-switching to false.
Now, every time I log out of a Unity session I get the "The system is
running in low-graphics mode" window. None of the options really help -
I have to "start lightdm" from console to get to the greeter.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1350357
Title:
Support disabling of user switching per seat
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Fix Released
Status in “lightdm” package in Ubuntu:
Fix Released
Status in “lightdm” source package in Trusty:
Confirmed
Status in “lightdm” source package in Utopic:
Fix Released
Bug description:
Let me start by saying it's possible I'm missing some subtleties here,
and if so, I'd be happy to get a more detailed explanation.
In LightDM 1.10.1 (Trusty), unity seats are forced to enable user
switching (in seat-unity.c). However, I think this is something that
should be configurable in the display manager. In a public computing
environment, fast-user-switching is undesirable, as it interferes with
serial re-usability and various cleanup tasks. Most public computing
labs want to maintain a 1-1 relationship between individuals and
workstations, and a workstation should either be in use by one user,
or not in use at all. In the past, our site has accomplished this in
various desktop environment configurations (such as the
org.gnome.desktop.lockdown gsettings, etc). Unfortunately, most of
these settings are ignored in Unity (I have filed separate bugs about
those).
Obviously, there are workarounds, including stealing all the other
VTs, or playing stupid D-Bus games, or wrapping X. Currently, our
preferred ("preferred") solution is to have our custom greeter check
logind and refuse to do anything other than unlock the existing
session if a user is already logged in on an X seat, but that's not
ideal, because you still end up with a second greeter running, and in
fact that becomes the primary greeter when the original user logs out.
That having been said, I believe it is the system administrator's
prerogative to dictate that there shall be one and only one seat
available on any given workstation, and instruct LightDM not to spawn
any additional ones. It would be great if this was added in future
releases. Alternatively, if that's not possible because of Unity
design, it would be great if there was a way for a greeter to say to
lightdm "I'm done, this seat is shutting down, switch back to an
original session." (And obviously, doing that if there is no other
session to switch to would be an error).
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1350357/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
