[Touch-packages] [Bug 1495262] Re: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
*** This bug is a duplicate of bug 1433320 *** https://bugs.launchpad.net/bugs/1433320 ** This bug is no longer a duplicate of bug 1494950 programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel() ** This bug has been marked a duplicate of bug 1433320 systemd-journald crashed with SIGABRT in sd_event_wait() -- 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/1495262 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() Status in systemd package in Ubuntu: New Bug description: Occurs only on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: udev 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CustomUdevRuleFiles: 80-net-setup-link.rules Date: Sat Sep 12 23:39:00 2015 ExecutablePath: /lib/systemd/systemd-udevd InstallationDate: Installed on 2015-03-25 (171 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-udevd ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () ?? () __libc_start_main (main=0x56419c4c1870, argc=1, argv=0x7ffcd70edec8, init=, fini=, rtld_fini=, stack_end=0x7ffcd70edeb8) at libc-start.c:289 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1495262/+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 1495258] Re: systemd-journald crashed with SIGABRT in __epoll_wait_nocancel()
*** This bug is a duplicate of bug 1433320 *** https://bugs.launchpad.net/bugs/1433320 ** This bug is no longer a duplicate of bug 1494950 programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel() ** This bug has been marked a duplicate of bug 1433320 systemd-journald crashed with SIGABRT in sd_event_wait() -- 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/1495258 Title: systemd-journald crashed with SIGABRT in __epoll_wait_nocancel() Status in systemd package in Ubuntu: New Bug description: Occurs only on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sun Sep 13 08:41:07 2015 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2015-03-25 (171 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-journald ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () __libc_start_main (main=0x5652314f8440, argc=1, argv=0x7ffc1cbb79e8, init=, fini=, rtld_fini=, stack_end=0x7ffc1cbb79d8) at libc-start.c:289 ?? () Title: systemd-journald crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1495258/+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 1495260] Re: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
*** This bug is a duplicate of bug 1433320 *** https://bugs.launchpad.net/bugs/1433320 ** This bug is no longer a duplicate of bug 1494950 programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel() ** This bug has been marked a duplicate of bug 1433320 systemd-journald crashed with SIGABRT in sd_event_wait() -- 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/1495260 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() Status in systemd package in Ubuntu: New Bug description: Occurs only on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: udev 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CustomUdevRuleFiles: 80-net-setup-link.rules Date: Sat Sep 12 23:39:00 2015 ExecutablePath: /lib/systemd/systemd-udevd ExecutableTimestamp: 1441816017 InstallationDate: Installed on 2015-03-25 (171 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-udevd ProcCwd: / ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () ?? () __libc_start_main (main=0x56419c4c1870, argc=1, argv=0x7ffcd70edec8, init=, fini=, rtld_fini=, stack_end=0x7ffcd70edeb8) at libc-start.c:289 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1495260/+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 1494950] Re: programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel()
*** This bug is a duplicate of bug 1433320 *** https://bugs.launchpad.net/bugs/1433320 ** This bug has been marked a duplicate of bug 1433320 systemd-journald crashed with SIGABRT in sd_event_wait() -- 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/1494950 Title: programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel() Status in systemd package in Ubuntu: New Bug description: Only occurs on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Fri Sep 11 10:29:00 2015 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2015-03-25 (170 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-logind ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () __libc_start_main (main=0x55d8c5f18030, argc=1, argv=0x7ffd39b7cba8, init=, fini=, rtld_fini=, stack_end=0x7ffd39b7cb98) at libc-start.c:289 ?? () Title: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1494950/+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 1494952] Re: systemd-timesyncd crashed with SIGABRT in epoll_wait()
*** This bug is a duplicate of bug 1433320 *** https://bugs.launchpad.net/bugs/1433320 ** This bug is no longer a duplicate of bug 1494950 programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel() ** This bug has been marked a duplicate of bug 1433320 systemd-journald crashed with SIGABRT in sd_event_wait() -- 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/1494952 Title: systemd-timesyncd crashed with SIGABRT in epoll_wait() Status in systemd package in Ubuntu: New Bug description: Only occurs on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 10 22:52:55 2015 ExecutablePath: /lib/systemd/systemd-timesyncd InstallationDate: Installed on 2015-03-25 (170 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-timesyncd ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: epoll_wait () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () __libc_start_main (main=0x55b565b91f70, argc=1, argv=0x7ffd518bfc98, init=, fini=, rtld_fini=, stack_end=0x7ffd518bfc88) at libc-start.c:289 ?? () Title: systemd-timesyncd crashed with SIGABRT in epoll_wait() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1494952/+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 1495259] Re: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel()
*** This bug is a duplicate of bug 1433320 *** https://bugs.launchpad.net/bugs/1433320 ** This bug is no longer a duplicate of bug 1494950 programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel() ** This bug has been marked a duplicate of bug 1433320 systemd-journald crashed with SIGABRT in sd_event_wait() -- 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/1495259 Title: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel() Status in systemd package in Ubuntu: New Bug description: Occurs only on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 12 12:18:44 2015 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2015-03-25 (171 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-logind ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () __libc_start_main (main=0x55d738326030, argc=1, argv=0x7ffea015ded8, init=, fini=, rtld_fini=, stack_end=0x7ffea015dec8) at libc-start.c:289 ?? () Title: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1495259/+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 1495261] Re: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel()
*** This bug is a duplicate of bug 1433320 *** https://bugs.launchpad.net/bugs/1433320 ** This bug is no longer a duplicate of bug 1494950 programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel() ** This bug has been marked a duplicate of bug 1433320 systemd-journald crashed with SIGABRT in sd_event_wait() -- 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/1495261 Title: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel() Status in systemd package in Ubuntu: New Bug description: Occurs only on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 12 12:18:44 2015 ExecutablePath: /lib/systemd/systemd-logind ExecutableTimestamp: 1441816014 InstallationDate: Installed on 2015-03-25 (171 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-logind ProcCwd: / ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () __libc_start_main (main=0x55d738326030, argc=1, argv=0x7ffea015ded8, init=, fini=, rtld_fini=, stack_end=0x7ffea015dec8) at libc-start.c:289 ?? () Title: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1495261/+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 1495263] Re: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
*** This bug is a duplicate of bug 1433320 *** https://bugs.launchpad.net/bugs/1433320 ** This bug is no longer a duplicate of bug 1494950 programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel() ** This bug has been marked a duplicate of bug 1433320 systemd-journald crashed with SIGABRT in sd_event_wait() -- 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/1495263 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() Status in systemd package in Ubuntu: New Bug description: Occurs only on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: udev 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CustomUdevRuleFiles: 80-net-setup-link.rules Date: Sat Sep 12 23:39:00 2015 ExecutablePath: /lib/systemd/systemd-udevd ExecutableTimestamp: 1441816017 InstallationDate: Installed on 2015-03-25 (171 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-udevd ProcCwd: / ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () ?? () __libc_start_main (main=0x56419c4c1870, argc=1, argv=0x7ffcd70edec8, init=, fini=, rtld_fini=, stack_end=0x7ffcd70edeb8) at libc-start.c:289 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1495263/+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 1494954] Re: programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel()
*** This bug is a duplicate of bug 1433320 *** https://bugs.launchpad.net/bugs/1433320 ** This bug is no longer a duplicate of bug 1494950 programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel() ** This bug has been marked a duplicate of bug 1433320 systemd-journald crashed with SIGABRT in sd_event_wait() -- 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/1494954 Title: programs using libsystemd crashed with SIGABRT in __epoll_wait_nocancel() Status in systemd package in Ubuntu: New Bug description: Only occurs on QEMU-based virtual machine. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: udev 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CustomUdevRuleFiles: 80-net-setup-link.rules Date: Fri Sep 11 16:25:31 2015 ExecutablePath: /lib/systemd/systemd-udevd InstallationDate: Installed on 2015-03-25 (170 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-udevd ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () ?? () __libc_start_main (main=0x5624e58a7870, argc=1, argv=0x7ffdb7ca9ef8, init=, fini=, rtld_fini=, stack_end=0x7ffdb7ca9ee8) at libc-start.c:289 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1494954/+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 1433320] Re: systemd-journald, udev, logind get killed by 1 min watchdog timeout
** Summary changed: - systemd-journald crashed with SIGABRT in sd_event_wait() + systemd-journald, udev, logind get killed by 1 min watchdog timeout -- 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/1433320 Title: systemd-journald, udev, logind get killed by 1 min watchdog timeout Status in systemd package in Ubuntu: Confirmed Bug description: Errors Bucket - https://errors.ubuntu.com/bucket/?id=/lib/systemd/systemd-journald%3A6%3A__epoll_wait_nocancel%3Asd_event_wait%3Asd_event_run%3Amain nothing ProblemType: CrashDistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1 Uname: Linux 3.19.0-8-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 Date: Tue Mar 17 17:18:08 2015 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2014-02-24 (386 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcCmdline: /lib/systemd/systemd-journald ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-8-generic root=UUID=7f776823-8240-460b-ab2d-45c8a2b2f2b6 ro quiet splash Signal: 6SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () __libc_start_main (main=0x7f94ef54c760, argc=1, argv=0x7ffe7c6e2fa8, init=, fini=, rtld_fini=, stack_end=0x7ffe7c6e2f98) at libc-start.c:287 ?? () Title: systemd-journald crashed with SIGABRT in __epoll_wait_nocancel() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1433320/+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 1495360] Re: the background of the "restart" button is gray
Lukas your "Introduce a GlobalShortcut QML component for handling global keyboard shortcuts" commit changed the colors, any reason? ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-system-settings (Ubuntu) Status: New => Invalid ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Lukáš Tinkl (lukas-kde) ** Changed in: unity8 (Ubuntu) Importance: Undecided => High ** Changed in: unity8 (Ubuntu) Status: New => Triaged -- 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/1495360 Title: the background of the "restart" button is gray Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Triaged Bug description: system-image-cli -i current build number: 121 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-09-14 11:56:40 version version: 121 version ubuntu: 20150911 version device: 20150821-736d127 version custom: 20150821-887-33-32-vivid reproduce steps: 1.long press the power button 2.3 buttons display, "Power off " "Restart" "Cancel" 3.the background of the "Restart" button is gray expect result: as before the background of the “restart" button is green To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1495360/+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 1494820] Re: /usr/bin/unity8-dash:6:fprintf:qt_message_print:qt_message:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration
"UbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is running, and the correct socket is being used and is accessible. The shell may have\nrejected the incoming connectio" Wonder if this being rc-proposed this is just people testing/debugging https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1487946 ? ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Also affects: qtubuntu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1494820 Title: /usr/bin/unity8-dash:6:fprintf:qt_message_print:qt_message:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration Status in mir package in Ubuntu: New Status in qtubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.12+15.04.20150814-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/003f0e8f98fef2cbbb6f8c3800fd04241ededbed contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1494820/+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 1433320] Re: systemd-journald, udev, logind get killed by 1 min watchdog timeout
There is nothing specific to epoll_wait(), that's just the function that these daemons wait in for practially all the time. The SIGABRT is due to systemd killing/restarting the processes as they don't respond withing 1 minute (watchdog). In Fila's case the kernel reports hung tasks (in a page fault, i. e. slow/broken swap?), but in Till's reports there is no other apparent error message. This is not just limited to QEMU, e. g. duplicate bug 1438805 is a real machine with a hardware watchdog. So we still only merely know the symptoms -- something stalls these QEMU or real laptop processes, but we don't know yet how. Does anyone have some observations/recipes how to reproduce this? I. e. did you start a lot of QEMU instances in parallel or something else what could make these slow? Maybe a running SSD TRIM in the background? ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete -- 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/1433320 Title: systemd-journald, udev, logind get killed by 1 min watchdog timeout Status in systemd package in Ubuntu: Incomplete Bug description: Errors Bucket - https://errors.ubuntu.com/bucket/?id=/lib/systemd/systemd-journald%3A6%3A__epoll_wait_nocancel%3Asd_event_wait%3Asd_event_run%3Amain nothing ProblemType: CrashDistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1 Uname: Linux 3.19.0-8-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 Date: Tue Mar 17 17:18:08 2015 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2014-02-24 (386 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcCmdline: /lib/systemd/systemd-journald ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-8-generic root=UUID=7f776823-8240-460b-ab2d-45c8a2b2f2b6 ro quiet splash Signal: 6SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () __libc_start_main (main=0x7f94ef54c760, argc=1, argv=0x7ffe7c6e2fa8, init=, fini=, rtld_fini=, stack_end=0x7ffe7c6e2f98) at libc-start.c:287 ?? () Title: systemd-journald crashed with SIGABRT in __epoll_wait_nocancel() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1433320/+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 1452610] Re: /etc/modprobe.d is not a file
This is not really a bug in ubuntu-drivers-common. Those are just debugging messages (no actual error there). I can probably get rid of them but still that doesn't explain why a second xserver was started. Maybe another user logged into the system from lightdm? Or maybe lightdm is acting funny for some reason. -- 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/1452610 Title: /etc/modprobe.d is not a file Status in lightdm package in Ubuntu: Triaged Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: /var/log/upstart# cat lightdm.log /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file /etc/modprobe.d is not a file update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf Above looks weird... modprobe.d is a directory & why update- alternatives are called?! This is lightdm 1.10.5-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1452610/+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 1494820] Re: /usr/bin/unity8-dash:6:fprintf:qt_message_print:qt_message:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration
Indeed this is crash #3 from errors.ubuntu.com of late. Although it appears to be unrelated to the other two: bug 1487649 bug 1494062 ** Summary changed: - /usr/bin/unity8-dash:6:fprintf:qt_message_print:qt_message:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration + /usr/bin/unity8-dash crashes on startup in UbuntuClientIntegration constructor while logging "UbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is\nrunning, and the correct socket is being used and is accessible. The shell may have\nrejected the incoming connectio" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1494820 Title: /usr/bin/unity8-dash crashes on startup in UbuntuClientIntegration constructor while logging "UbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is\nrunning, and the correct socket is being used and is accessible. The shell may have\nrejected the incoming connectio" Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in qtubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.12+15.04.20150814-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/003f0e8f98fef2cbbb6f8c3800fd04241ededbed contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1494820/+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 1494820] Re: /usr/bin/unity8-dash crashes on startup in UbuntuClientIntegration constructor while logging "UbuntuClientIntegration: connection to Mir server failed. Check that a
Doesn't appear to be related to Mir...
#0 __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:47
No locals.
#1 0xb611a62e in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
_a1 = 0
_a3tmp = 6
_a1tmp = 0
_a3 = 6
_nametmp = 268
_a2tmp = 3232
_a2 = 3232
_name = 268
_sys_result =
pd = 0xb6f2f000
pid = 0
selftid = 3232
#2 0xb611b332 in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0},
sa_mask = {__val = {3069375680, 1, 0, 3069304799, 3069383600, 1, 5, 3056365568,
3681224, 0, 3056456264, 3069374464, 3069375680, 1, 0, 3069304799, 3069383600,
1, 5, 0, 0, 3054484428, 3203518664, 3056829517, 3203518704, 0, 3203519780,
3203519204, 3069190020, 3069324028, 3069375688, 3069377464}}, sa_flags =
-1225591607, sa_restorer = 0x0}
sigs = {__val = {32, 0 }}
#3 0xb6335d04 in fprintf (__fmt=0xb653e1ec "%s\n", __stream=0xb6f2f000) at
/usr/include/arm-linux-gnueabihf/bits/stdio2.h:98
No locals.
#4 qt_message_print (message=..., context=..., msgType=QtFatalMsg) at
global/qlogging.cpp:1386
No locals.
#5 qt_message (buf=..., ap=..., msg=0xbef1d0e0 "\340*\375\263", context=...,
msgType=QtFatalMsg) at global/qlogging.cpp:224
No locals.
#6 QMessageLogger::fatal (this=0xb61e1088 , this@entry=0xbef1d0f0,
msg=0xb3fd3190 "UbuntuClientIntegration: connection to Mir server failed. Check
that a Mir server is\nrunning, and the correct socket is being used and is
accessible. The shell may have\nrejected the incoming connectio"...) at
global/qlogging.cpp:633
message = {static null = {}, d = 0x12074c0}
ap = {__ap = 0xbef1d0e0}
#7 0xb3fc09f4 in UbuntuClientIntegration::UbuntuClientIntegration
(this=) at ../../../src/ubuntumirclient/integration.cpp:80
defaultGridUnit =
gridUnit =
gridUnitString = {static MaxSize = 1073741808, d = 0x2}
#8 0xb3fc3264 in UbuntuMirClientIntegrationPlugin::create (this=, system=...) at ../../../src/ubuntumirclient/plugin.cpp:36
No locals.
#9 0xb6cb595e in loadIntegration (argv=0x1, argc=@0xbef1d2e4: 2,
parameters=..., key=..., loader=0xb6f01f84
<_ZZN12_GLOBAL__N_112Q_QGS_loader13innerFunctionEvE6holder>) at
kernel/qplatformintegrationfactory.cpp:56
result =
index =
#10 QPlatformIntegrationFactory::create (platform=..., paramList=...,
argc=@0xbef1d2e4: 2, argv=0x1, argv@entry=0xbef1d524, platformPluginPath=...)
at kernel/qplatformintegrationfactory.cpp:73
No locals.
#11 0xb6cbd878 in init_platform (argv=0xbef1d524, argc=@0xbef1d2e4: 2,
platformThemeName=..., platformPluginPath=..., pluginArgument=...) at
kernel/qguiapplication.cpp:1010
** Changed in: mir (Ubuntu)
Status: New => Invalid
** Also affects: mir
Importance: Undecided
Status: New
** Changed in: mir
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1494820
Title:
/usr/bin/unity8-dash crashes on startup in UbuntuClientIntegration
constructor while logging "UbuntuClientIntegration: connection to Mir
server failed. Check that a Mir server is\nrunning, and the correct
socket is being used and is accessible. The shell may have\nrejected
the incoming connectio"
Status in Mir:
Invalid
Status in mir package in Ubuntu:
Invalid
Status in qtubuntu package in Ubuntu:
New
Status in unity8 package in Ubuntu:
New
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem
regarding unity8. This problem was most recently seen with version
8.12+15.04.20150814-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/003f0e8f98fef2cbbb6f8c3800fd04241ededbed
contains more details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1494820/+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 1367907] Re: Segfault in gc with cyclic trash
The version with the fix in trusty-proposed since 2 months, it was validated by 2 developers 1 month 1/2 ago, but then nothing happened. What's going on with this issue? The fix was pushed into CPython 3.4 on May 2014. Come on Ubuntu, please do something for Python 3.4! This bug is a major bug. I don't understand why it is not fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1367907 Title: Segfault in gc with cyclic trash Status in oslo.messaging: Invalid Status in Python: Fix Released Status in python3.4 package in Ubuntu: Fix Released Status in python3.4 source package in Trusty: Fix Committed Bug description: Trusty's python3.4 package is affected by python bug http://bugs.python.org/issue21435. This bug was fixed in http://hg.python.org/cpython/rev/64ba3f2de99c. Trusty should pull this fix into the python3.4 package. Note this definitely affects some python projects. `git clone https://git.openstack.org/openstack/oslo.messaging && cd oslo.messaging && edit tox.ini file, copy py33 target and rename to py34 && tox -repy34` will segfault due to this bug. With previous versions of python unaffected by this bug there is no segfaulting. Now for details, broken using: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy python3.4 python3.4: Installed: 3.4.0-2ubuntu1 Candidate: 3.4.0-2ubuntu1 Version table: *** 3.4.0-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status If I install the following python3.4 packages for Unicorn on Trusty this bug is corrected. The Unicorn packages here on lp for python3.4 are python3.4.1 which includes the bug fix for this bug. libpython3.4_3.4.1-10ubuntu1_amd64.deb libpython3.4-dev_3.4.1-10ubuntu1_amd64.deb libpython3.4-stdlib_3.4.1-10ubuntu1_amd64.deb python3.4-dbg_3.4.1-10ubuntu1_amd64.deb python3.4-minimal_3.4.1-10ubuntu1_amd64.deb libpython3.4-dbg_3.4.1-10ubuntu1_amd64.deb libpython3.4-minimal_3.4.1-10ubuntu1_amd64.deb python3.4_3.4.1-10ubuntu1_amd64.deb python3.4-dev_3.4.1-10ubuntu1_amd64.deb Note I installed the -dbg packages too just in case I needed to use gdb but that wasn't necessary as the test case works with these newer versions of python. $ apt-cache policy python3.4 python3.4: Installed: 3.4.1-10ubuntu1 Candidate: 3.4.1-10ubuntu1 Version table: *** 3.4.1-10ubuntu1 0 100 /var/lib/dpkg/status 3.4.0-2ubuntu1 0 500 http://az2.clouds.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages [Impact] This python bug can cause python processes that tickle it to segfault python. This means there could be a significant number of python packages that are broken when run under this interpreter. The fix for this bug should be backported to avoid seemingly random and hard to debug segfaults from happening when users use python. Unicorn's 3.4.1 packages fix this bug by including the patch at http://hg.python.org/cpython/rev/64ba3f2de99c. [Test Case] There is a test case detailed in the upstream bug http://bugs.python.org/issue21435, though I have been doing the following instead: git clone https://git.openstack.org/openstack/oslo.messaging cd oslo.messaging git fetch https://review.openstack.org/openstack/oslo.messaging refs/changes/90/118790/2 && git checkout FETCH_HEAD tox -repy34 # This should end with segfaulting test runners. Note if you don't have tox installed you will need to install version 1.7.2 or greater. `sudo pip install tox==1.7.2` will do this. [Regression Potential] The patch in question is small. If we go straight to python 3.4.1 the diff will be larger but that isn't necessary to fix this particular issue. The biggest regression potential would be that the garbage collector is newly broken by the this bug fix. Considering that the garbage collector is already broken and this patch comes with test cases to check it is less broken the risk of regression here is less than the pain of dealing with this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/oslo.messaging/+bug/1367907/+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 1494820] Re: /usr/bin/unity8-dash crashes on startup in UbuntuClientIntegration constructor while logging "UbuntuClientIntegration: connection to Mir server failed. Check that a
Although this might happen if unity8 crashed just as unity8-dash was starting. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1494820 Title: /usr/bin/unity8-dash crashes on startup in UbuntuClientIntegration constructor while logging "UbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is\nrunning, and the correct socket is being used and is accessible. The shell may have\nrejected the incoming connectio" Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in qtubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.12+15.04.20150814-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/003f0e8f98fef2cbbb6f8c3800fd04241ededbed contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1494820/+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 1494514] Re: When the screen timeout is set to one minute, the screen doesn't dim before going off
unity8 doesn't have any part on setting the timings nor on doing the actual dimming (AFAIK) ** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Also affects: unity-system-compositor (Ubuntu) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu) Status: New => Invalid -- 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/1494514 Title: When the screen timeout is set to one minute, the screen doesn't dim before going off Status in ubuntu-system-settings package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description: When set to two mins or more, the screen dims for 10 secs then goes off. (I also thought the intended time on dim was 15 secs or more not 10, its a bit too quick to react to) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1494514/+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 1495180] Re: package account-plugin-google (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/accounts/services/google-im.service », qui apparti
** Package changed: account-plugins (Ubuntu) => ktp-accounts-kcm (Ubuntu) -- 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/1495180 Title: package account-plugin-google (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/accounts/services/google-im.service », qui appartient aussi au paquet kde-config-telepathy-accounts 4:15.08.0-0ubuntu1 Status in ktp-accounts-kcm package in Ubuntu: New Bug description: Error while installing the metapackage ubuntu-gnome-desktop. Similar problem was encountered while installing unity8-desktop and apt-get was lost into cyclic dependencies that couldn't be satisfied. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: account-plugin-google (not installed) ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: i386 Date: Sat Sep 12 10:10:12 2015 DuplicateSignature: package:account-plugin-google:(not installed):tentative de remplacement de « /usr/share/accounts/services/google-im.service », qui appartient aussi au paquet kde-config-telepathy-accounts 4:15.08.0-0ubuntu1 ErrorMessage: tentative de remplacement de « /usr/share/accounts/services/google-im.service », qui appartient aussi au paquet kde-config-telepathy-accounts 4:15.08.0-0ubuntu1 InstallationDate: Installed on 2015-08-31 (12 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150825.1) RelatedPackageVersions: dpkg 1.18.2ubuntu3 apt 1.0.9.10ubuntu6 SourcePackage: account-plugins Title: package account-plugin-google (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/accounts/services/google-im.service », qui appartient aussi au paquet kde-config-telepathy-accounts 4:15.08.0-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ktp-accounts-kcm/+bug/1495180/+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 1495039] Re: long left swipe and home button do not reset department
*** This bug is a duplicate of bug 1357053 *** https://bugs.launchpad.net/bugs/1357053 ** This bug has been marked a duplicate of bug 1357053 [Launcher] home button should reset dash department -- 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/1495039 Title: long left swipe and home button do not reset department Status in Ubuntu UX: New Status in unity8 package in Ubuntu: New Bug description: Title is quite self explanatory. My girlfriend could not see the department selection and when clicking on the home button or doing a left swipe there was no reset. So she could not go back to home. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1495039/+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 1493872] Re: Keyboard stays open on lock screen / Unity8 doesn't unfocus app when switching to lock screen first time
*** This bug is a duplicate of bug 1491034 *** https://bugs.launchpad.net/bugs/1491034 ** This bug has been marked a duplicate of bug 1491034 keyboard stays above lockscreen when locking -- 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/1493872 Title: Keyboard stays open on lock screen / Unity8 doesn't unfocus app when switching to lock screen first time Status in Canonical System Image: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: If the screen is locked after an application has been first opened unity doesn't remove focus from the app. It does remove focus on subsequent screen locks. This results in the keyboard not being dismissed if it was displayed prior to the screen being locked. Steps to reproduce: - Open the messaging app - Start composing a message - Lock the screen using the power button (or waiting for your automatic screen lock timeout) - Wake the phone by briefly pressing the power button Result: the keyboard is still overlayed on top of the lock screen. (see attachment) Expected result: the keyboard is not shown on the lock screen. This can also be seen in the application log (e.g. ~/.cache/upstart /application-legacy-messaging-app-.log), where you would expect to see the message: UbuntuWindow::handleSurfaceFocusChange(focused=false) Indicating that focus has been removed from the app, however this doesn't happen the first time you lock the screen after starting the app, only on subsequent locks. --- OS build number: 234 Ubuntu Image part: 20150908 Ubuntu build description: Ubuntu 15.04 - armhf (20150908-020305) Device Image part: 20150819 Device build description: aosp_mako-userdebug 4.4.2 KOT49H 20150818-1500-0ubuntu1 test-keys Customisation Image part: 20150908 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1493872/+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 972077] Re: apt repository disk format has race conditions
** Description changed: Apt archives are accessed over HTTP; this has resulted in a cluster of bugs (reported here, and upstream) about problems behind intercepting caches, problems with squid etc. There are 3 interlocking issues: A - mirror networks may be out of sync with each other (e.g. a file named on one mirror may no longer exist, or may not yet exist, on another mirror) B - updating files on a single mirror is not atomic - and even small windows of inconsistency will, given enough clients, cause headaches. C - caches exacerbate race conditions - when one happens, until the cached data expires, all clients of the cache will suffer from the race Solving this requires one of several things: - file system transactions - an archive format that requires only weakly ordered updates to the files at particular urls with the assumption that only one file may be observed to change at a time (because a lookup of file A, then B, may get a cache miss on A and a cache hit on B, so even if all clients strictly go A, then B, updates may still see old files when paths are reused). - super robust clients that repeatedly retry with progressively less cache friendly headers until they have a consistent view. (This is very tricky to do). It may be possible to do a tweak to the apt repository format though, which would allow publishing a race-free format in parallel with the existing layout, while clients migrate. To be safe against issue (A) the mirror network would need some care around handling of dns round-robin mirrors [to minimise the situation where referenced data is not available], but this should be doable - or alternatively clients doing 'apt-get update' may need to be willing to retry to accommodate round- robin skew. What would such an archive format look like? - It would have only one well known file name (e.g. Releases-2), which would be internally signed. Rather than signing e.g. Packages.gz, it would sign a uniquely named packages and sources file - e.g. Packages-$HASH.gz or Packages-$serialno.gz. + It would have only one well known file name (InRelease), which would be internally signed. Rather than signing e.g. Packages.gz, it would sign a uniquely named packages and sources file - e.g. Packages-$HASH.gz or Packages-$serialno.gz. Backwards compatibility is achieved by using the same filenames for deb's and the like. We need to keep writing Packages.gz though, and Releases, until we no longer worry about old apt clients. We can optimise disk space a little by making Packages.gz a symlink to a Packages-$HASH.gz (and so on for Sources..), but it may be simpler and less prone to unexpected behaviour to keep using regular files. tl;dr * Unique file names for all unique file content with one exception - * Releases-2, a self-signed file that provides hashes and names the index files (Packages, Sources, Translations etc) + * InRelease, a self-signed file that provides hashes and names the index files (Packages, Sources, Translations etc) * Coexists with existing archive layout - Related bugs: - * bug 804252: Please support InRelease files - * bug 1430011: support apt by-hash mirrors + * bug 804252: Please support InRelease files + * bug 1430011: support apt by-hash mirrors -- 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/972077 Title: apt repository disk format has race conditions Status in apt package in Ubuntu: Confirmed Bug description: Apt archives are accessed over HTTP; this has resulted in a cluster of bugs (reported here, and upstream) about problems behind intercepting caches, problems with squid etc. There are 3 interlocking issues: A - mirror networks may be out of sync with each other (e.g. a file named on one mirror may no longer exist, or may not yet exist, on another mirror) B - updating files on a single mirror is not atomic - and even small windows of inconsistency will, given enough clients, cause headaches. C - caches exacerbate race conditions - when one happens, until the cached data expires, all clients of the cache will suffer from the race Solving this requires one of several things: - file system transactions - an archive format that requires only weakly ordered updates to the files at particular urls with the assumption that only one file may be observed to change at a time (because a lookup of file A, then B, may get a cache miss on A and a cache hit on B, so even if all clients strictly go A, then B, updates may still see old files when paths are reused). - super robust clients that repeatedly retry with progressively less cache friendly headers until they have a consistent view. (This is very tricky to do). It may be possible to do a tweak to the apt repository format though, which would allow publishing a race
[Touch-packages] [Bug 1495408] Re: Black square in header
** Attachment added: "addressbok_20150914_14787.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495408/+attachment/4463820/+files/addressbok_20150914_14787.png ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Tags added: regression-proposed -- 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/1495408 Title: Black square in header Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en Same on latest arale There is a black square in the header in several applications (address-book, messaging, dialler, cf screenshots) To display the black square: - dialler: open 'Recent calls' - messaging: tap on a message and go back - contact: tap on a contact To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495408/+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 1495408] [NEW] Black square in header
Public bug reported: current build number: 122 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en Same on latest arale There is a black square in the header in several applications (address- book, messaging, dialler, cf screenshots) To display the black square: - dialler: open 'Recent calls' - messaging: tap on a message and go back - contact: tap on a contact ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Tags: regression-proposed ** Attachment added: "dialler_20150914_095911782.png" https://bugs.launchpad.net/bugs/1495408/+attachment/4463818/+files/dialler_20150914_095911782.png -- 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/1495408 Title: Black square in header Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en Same on latest arale There is a black square in the header in several applications (address-book, messaging, dialler, cf screenshots) To display the black square: - dialler: open 'Recent calls' - messaging: tap on a message and go back - contact: tap on a contact To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495408/+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 1495408] Re: Black square in header
** Attachment added: "messaging_20150914_095927419.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495408/+attachment/4463819/+files/messaging_20150914_095927419.png -- 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/1495408 Title: Black square in header Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en Same on latest arale There is a black square in the header in several applications (address-book, messaging, dialler, cf screenshots) To display the black square: - dialler: open 'Recent calls' - messaging: tap on a message and go back - contact: tap on a contact To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495408/+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 1495408] Re: Black square in header
** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Milestone: None => ww40-2015 -- 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/1495408 Title: Black square in header Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en Same on latest arale There is a black square in the header in several applications (address-book, messaging, dialler, cf screenshots) To display the black square: - dialler: open 'Recent calls' - messaging: tap on a message and go back - contact: tap on a contact To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495408/+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 1373463] Re: [indicators] Impossible to disable cellular data from indicator
Recently I've been woken up a couple of times during the night because someone from Asia mentioned me on twitter (by mistake) and because of e-mails I've been receiving during the night. All these events trigger notifications, which wake me up. Please save my sleep :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1373463 Title: [indicators] Impossible to disable cellular data from indicator Status in Ubuntu UX: Triaged Status in indicator-network package in Ubuntu: Triaged Bug description: I was wondering : Why it isn't possible to disable data from the network indicator ? Probably with a switch button that offer the choice between no data or data activated (with the last data activated state (2g only or 2G,3G,4G). Why this ? Because it's the first setting to change to save battery, and probably one of the most used (I asked around me, everyone agreed they would prefer that over Wi-Fi if only one was possible). I think it's stupid to go to the settings app for the most common action (and very frustrating). Of course, this also apply for the battery setting page (that already contain Wi-Fi, GPS, Bluetooth and brightness settings). I asked that on the phone ML, I've been invited to file a wishlist bug there to "help" designers with next iteration of network indicator. So here it is ! [1] : mailing list discussion with already some support to this idea : https://lists.launchpad.net/ubuntu-phone/msg09910.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1373463/+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 1494591] Re: not translated lock screen statistic
*** This bug is a duplicate of bug 1376296 *** https://bugs.launchpad.net/bugs/1376296 Duplicate of 1398016 that is a duplicate of 1376296 ** This bug has been marked a duplicate of bug 1376296 libusermetrics translations not imported into LP, and missing from langpack exports -- 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/1494591 Title: not translated lock screen statistic Status in unity8 package in Ubuntu: New Bug description: Language set to hungarian. In the middle of the locked screen I turned off the statistics. Now it says: "No data sources available" This sentence need to be translated to hungarian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1494591/+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 1488540] Re: Right clicks go through popovers
** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui-toolkit/clickThru -- 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/1488540 Title: Right clicks go through popovers Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: When displaying e.g. an ActionSelectionPopover (but this is valid for generic Popovers too), clicking anywhere outside of the popover will dismiss it by default. A left-click inside the popover will typically trigger the action under the cursor. But a right-click is not intercepted and goes through the popover, to be processed by whatever is below it. I would tend to think that this is unwanted behaviour in the general case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1488540/+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 1495408] Re: Black square in header
** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Confirmed ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Zoltan Balogh (bzoltan) ** Changed in: canonical-devices-system-image Status: New => 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/1495408 Title: Black square in header Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en Same on latest arale There is a black square in the header in several applications (address-book, messaging, dialler, cf screenshots) To display the black square: - dialler: open 'Recent calls' - messaging: tap on a message and go back - contact: tap on a contact To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495408/+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 1495408] Re: Black square in header
** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: High => Critical ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Tim Peeters (tpeeters) ** Changed in: canonical-devices-system-image Assignee: Zoltan Balogh (bzoltan) => Tim Peeters (tpeeters) -- 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/1495408 Title: Black square in header Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en Same on latest arale There is a black square in the header in several applications (address-book, messaging, dialler, cf screenshots) To display the black square: - dialler: open 'Recent calls' - messaging: tap on a message and go back - contact: tap on a contact To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495408/+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 1494885] Re: package apport 2.17.2-0ubuntu1.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1494885 Title: package apport 2.17.2-0ubuntu1.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in apport package in Ubuntu: Confirmed Bug description: any ProblemType: Package DistroRelease: Ubuntu 15.04 Package: apport 2.17.2-0ubuntu1.4 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportLog: ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CrashReports: 600:0:118:116823:2015-09-11 16:07:24.816389799 +0200:2015-09-11 16:07:25.816389799 +0200:/var/crash/apport.0.crash Date: Fri Sep 11 16:07:25 2015 DuplicateSignature: package:apport:2.17.2-0ubuntu1.4:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-30 (12 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: apport Title: package apport 2.17.2-0ubuntu1.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1494885/+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 1410996] Re: [Browser] Add WebView.mediaAccessPermissionRequested API
** Changed in: webbrowser-app (Ubuntu) Assignee: Olivier Tilloy (osomon) => Ugo Riboni (uriboni) ** Changed in: webbrowser-app (Ubuntu) Status: Confirmed => In Progress -- 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/1410996 Title: [Browser] Add WebView.mediaAccessPermissionRequested API Status in Canonical System Image: Confirmed Status in Oxide: Fix Released Status in Ubuntu UX: Fix Committed Status in webbrowser-app package in Ubuntu: In Progress Bug description: This keeps getting pushed aside by other tasks, but it's really about time we got this done (as it's required for sites to be able to access the camera / microphone) --- --- --- --- UX Comment: Relevant wireframes/pages added to specification: https://docs.google.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g3ddd7bb9c_00 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1410996/+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 1495422] [NEW] CMake warnings: Policy CMP0028 is not set
Public bug reported: I get a bunch of CMake warnings when I try to compile gallery-app: tim@ubuntu:~/dev/r/gallery-app$ cmake . -- Could NOT find Lcov (missing: LCOV_EXECUTABLE GENHTML_EXECUTABLE) -- Could NOT find gcovr (missing: GCOVR_EXECUTABLE) -- Autopilot tests enabled. -- Configuring done CMake Warning (dev) at src/CMakeLists.txt:51 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "gallery-app" links to target "Qt5::Xml" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at src/medialoader/CMakeLists.txt:27 (add_library): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "gallery-medialoader" links to target "Qt5::Widgets" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at tests/unittests/command-line-parser/CMakeLists.txt:12 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "command-line-parser" links to target "Qt5::Widgets" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at tests/unittests/mediamonitor/CMakeLists.txt:18 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "mediamonitor" links to target "Qt5::Widgets" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at tests/unittests/mediamonitor/CMakeLists.txt:18 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "mediamonitor" links to target "Qt5::Widgets" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at tests/unittests/mediamonitor/CMakeLists.txt:18 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "mediamonitor" links to target "Qt5::Widgets" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at tests/unittests/resource/CMakeLists.txt:12 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "resource" links to target "Qt5::Widgets" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at tests/unittests/video/CMakeLists.txt:28 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "video" links to target "Qt5::Xml" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. -- Generating done -- Build files have been written to: /home/tim/dev/r/gallery-app tim@ubuntu:~/dev/r/gallery-app$ ** Affects: gallery-app (Ubuntu) Importance: Undecided Status: New
[Touch-packages] [Bug 1475850] Re: Several update-rc.d/insserv warnings
I have never seen this issue on acpid but I'm also seeing it for example on reinstalling cron. Can you check if this issue appears if you reinstall/reconfigure cron? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to insserv in Ubuntu. https://bugs.launchpad.net/bugs/1475850 Title: Several update-rc.d/insserv warnings Status in insserv package in Ubuntu: Confirmed Status in sysvinit package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 15.10 dev with insserv 1.14.0-5ubuntu3 and sysv-rc 2.88dsf-59.2ubuntu1 and on configuring packages I have seen now for some time several update-rc.d/insserv warnings. If I'm reconfiguring all packages installed on my system they appear on: - cron 3.0pl1-127ubuntu1: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: stop runlevel arguments (1) do not match cron Default-Stop values (none) insserv: warning: current stop runlevel(s) (1) of script `cron' overrides LSB defaults (empty). - cryptsetup 2:1.6.1-1ubuntu7: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults - grub-common 2.02~beta2-26ubuntu3: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults - keyboard-configuration 1.108ubuntu5: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults - ntp 1:4.2.6.p5+dfsg-3ubuntu6: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults - procps 1:3.3.9-1ubuntu8: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults - x11-common 1:7.7+7ubuntu4: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/insserv/+bug/1475850/+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 1450960] Re: dev file system is mounted without noexec
** Changed in: initramfs-tools (Ubuntu) Status: Fix Committed => Triaged -- 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/1450960 Title: dev file system is mounted without noexec Status in initramfs-tools package in Ubuntu: Triaged Status in lxc package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: I just found that the /dev filesystem of most Ubuntu system is mounted without noexec, nosuid etc options. If you do everything to harden your system, and you are using squashfs as root file system (which is read-only), such auto-mounted devices can be a serious leak. This volume usually is quite small and for most folders only root has write access, so I don't know how much this bug is security relevant, but I think there is no reason to not change the mount options for /dev. And especially for LXC containers, I don't even know a workaround to fix it. STEPS TO REPRODUCE: me:~# cat >/dev/call-me.sh <<.e > #!/bin/sh > echo "I'm executable" > .e me:~# chmod +x /dev/call-me.sh me:~# /dev/call-me.sh I'm executable EXPECTED BEHAVIOUR me:~# /dev/call-me.sh -bash: /dev/call-me.sh: Permission denied WORKAROUND me:~# mount -oremount,noexec,nosuid /dev me:~# /dev/call-me.sh -bash: /dev/call-me.sh: Permission denied Unfortunately, this workaround doesn't work in LXC containers (where the same problem occurs) because of missing capabilities. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.11 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: XFCE CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied CustomUdevRuleFiles: 51-android.rules 60-vboxdrv.rules Date: Sat May 2 01:48:26 2015 MachineType: Gigabyte Technology Co., Ltd. H97-HD3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=/dev/mapper/vg_ssd-lv_system_trusty1404 ro SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2014-04-18 (378 days ago) dmi.bios.date: 06/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97-HD3 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: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/26/2014:svnGigabyteTechnologyCo.,Ltd.:pnH97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H97-HD3 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/1450960/+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 1495421] [NEW] [Latitude 3160] Having troubles while resume from Hibernation/S4
Public bug reported: Unable to resume normally after hibernation, screen may goes black or display garbled console message, wait after awhile and switching between VTs might also bring back the desktop environment. Although, users may not able to hibernate from GUI menu, but this could be a problem while suspend(pm-suspend-hybrid) until battery runs out. Seeing a lot similar message in syslog: hpet1: lost [numbers] rtc interrupts ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.13 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: Mon Sep 14 04:34:40 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 15.07.00, 3.13.0-63-generic, x86_64: installed fwts-efi-runtime-dkms, 15.07.00, 3.16.0-49-generic, x86_64: installed fwts-efi-runtime-dkms, 15.07.00, 3.19.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06a8] InstallationDate: Installed on 2015-09-11 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2989 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 3160 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic root=UUID=83f4e0c6-61e7--87c6-947f96b09043 ro rootdelay=60 quiet splash initcall_debug SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 03Y010 dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd05/24/2015:svnDellInc.:pnLatitude3160:pvr01:rvnDellInc.:rn03Y010:rvrD02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3160 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Sep 14 02:20:16 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9052 vendor AUO xserver.version: 2:1.17.1-0ubuntu3~trusty1 ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-meta-lts-vivid (Ubuntu) Importance: Low Assignee: Anthony Wong (anthonywong) Status: Confirmed ** Tags: 201503-17148 amd64 apport-bug compiz-0.9 taipei-lab trusty ubuntu ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1495421/+attachment/4463864/+files/syslog ** Package changed: xorg (Ubuntu) => linux-meta-lts-vivid (Ubuntu) ** Changed in: linux-meta-lts-vivid (Ubuntu) Status: New => Confirmed ** Changed in: linux-meta-lts-vivid (Ubuntu) Importance: Undecided => Low ** Also affects: hwe-next Importance: Undecided Status: New ** Changed in: linux-meta-lts-vivid (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) ** Description changed: - Unable to resume normally after hibernation, screen my goes black or - display garbled console message. + Unable to resume normally after hibernation, screen may goes black or + display garbled console message, wait after awhile and switching between + VTs might also bring back the desktop environment. Although, users may not able to hibernate from GUI menu, but this could be a problem while suspend(pm-suspend-hybrid) until battery runs out. Seeing a lot similar message in syslog: hpet1: lost [numbers] rtc interrupts ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5 Uname: Linux 3.19.
[Touch-packages] [Bug 1494135] Re: Microphone mute hotkey for Dell Precision series
I've verify the package libudev1 204-5ubuntu20.14 udev 204-5ubuntu20.14 which fix this issue. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1494135 Title: Microphone mute hotkey for Dell Precision series Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Trusty: Fix Committed Bug description: Microphone mute hotkey on Dell Precision series is needed to be support. I encounter this issue on Ubuntu OEM project. This feature is similar to microphone mute hotkey on Dell Latitude series. I've submit a patch to systemd upstream and have been merged. https://github.com/systemd/systemd/commit/0018e4e47947b1a65855e8404480131e9d0c93ca Now we can backport to Ubuntu system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1494135/+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 1495408] Re: Black square in header
I reproduced the bug as described above on device, but I can also reproduce it on my laptop with gallery-app (click on a photo, and then go back). -- 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/1495408 Title: Black square in header Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en Same on latest arale There is a black square in the header in several applications (address-book, messaging, dialler, cf screenshots) To display the black square: - dialler: open 'Recent calls' - messaging: tap on a message and go back - contact: tap on a contact To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495408/+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 1495293] Re: Upon switching sound output device sound mutes
@Raymond,from reading the description of that patch it looks like it might be a regression of it. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- 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/1495293 Title: Upon switching sound output device sound mutes Status in pulseaudio package in Ubuntu: New Bug description: So this is what happened, I just plugged in my headphones, and even though before when I was using the volume was up almost full, the volume went to mute, then I turned up the volume, and when I switched back to my normal speakers, the volume went to mute again! So it seems annoyingly that if I switch from one sound output device to the other, if I change the volume from the newly set mute to a different volume it automatically turns the other to mute (although randomly it does other things)... Now I'm also finding that if I turn the volume up, then switch and it goes to mute, if I then switch back without changing anything the volume goes to just above mute (but sometimes mute) on the one I am switching to. And I am seeing lots of other strange behaviour like this. I have attempted renaming the "~/.config/pulse" directory and then running "pulseaudio -k", but the problem still remains. Adapted from my AskUbuntu question: https://askubuntu.com/questions/673735/upon-switching-sound-output- device-sound-mutes --- OS Information: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.04 Release: 15.04 Codename: vivid Flavour: GNOME GNOME Version: 3.16 Package Information: pulseaudio: Installed: 1:6.0-0ubuntu6 Candidate: 1:6.0-0ubuntu6 Version table: *** 1:6.0-0ubuntu6 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1495293/+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 1299322] Re: [Alienware 18, Realtek ALC3661] Sound only comes out of subwoofer, and requires lid to be closed then opened to come out of speakers at all
*** This bug is a duplicate of bug 1332900 *** https://bugs.launchpad.net/bugs/1332900 Hi All was this problem solved or Not I also have Alienware 18 I have tried to configure it as above Same deal I think the sound is only coming out from the Sub I have spent a week trying to sort it and have done many re-installs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1299322 Title: [Alienware 18, Realtek ALC3661] Sound only comes out of subwoofer, and requires lid to be closed then opened to come out of speakers at all Status in alsa-driver package in Ubuntu: Expired Bug description: To get any sound out of the speakers I need to close the lid of the laptop, let it go to sleep, then re-open it. When I unlock the computer the sound will then work from the speakers. Sound from the speakers is not using all of the speakers, and appears to only come out the subwoofer channel or center channel on the bottom of the laptop. There's no sound from the 'speakers' on the front. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kevin 2265 F pulseaudio /dev/snd/controlC0: kevin 2265 F pulseaudio Date: Fri Mar 28 23:16:26 2014 InstallationDate: Installed on 2014-03-28 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [Alienware 18, Realtek ALC3661, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2013 dmi.bios.vendor: Alienware dmi.bios.version: A02 dmi.board.name: 01W2J2 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A02 dmi.modalias: dmi:bvnAlienware:bvrA02:bd07/15/2013:svnAlienware:pnAlienware18:pvr1747:rvnAlienware:rn01W2J2:rvrA00:cvnAlienware:ct8:cvrA02: dmi.product.name: Alienware 18 dmi.product.version: 1747 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1299322/+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 1495408] Re: Black square in header
I reproduced the bug (with gallery-app on desktop) with UITK staging r1612, and verified that the bug is not present in r1611, so it broke with this MR: https://code.launchpad.net/~zsombi/ubuntu-ui- toolkit/cppActionItem/+merge/268348 -- 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/1495408 Title: Black square in header Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en Same on latest arale There is a black square in the header in several applications (address-book, messaging, dialler, cf screenshots) To display the black square: - dialler: open 'Recent calls' - messaging: tap on a message and go back - contact: tap on a contact To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495408/+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 1495422] Re: CMake warnings: Policy CMP0028 is not set
I reproduced the bug with UITK staging r1612, and verified that the bug is not present in r1611, so it broke with this MR: https://code.launchpad.net/~zsombi/ubuntu-ui- toolkit/cppActionItem/+merge/268348 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1495422 Title: CMake warnings: Policy CMP0028 is not set Status in gallery-app package in Ubuntu: New Bug description: I get a bunch of CMake warnings when I try to compile gallery-app: tim@ubuntu:~/dev/r/gallery-app$ cmake . -- Could NOT find Lcov (missing: LCOV_EXECUTABLE GENHTML_EXECUTABLE) -- Could NOT find gcovr (missing: GCOVR_EXECUTABLE) -- Autopilot tests enabled. -- Configuring done CMake Warning (dev) at src/CMakeLists.txt:51 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "gallery-app" links to target "Qt5::Xml" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at src/medialoader/CMakeLists.txt:27 (add_library): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "gallery-medialoader" links to target "Qt5::Widgets" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at tests/unittests/command-line-parser/CMakeLists.txt:12 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "command-line-parser" links to target "Qt5::Widgets" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at tests/unittests/mediamonitor/CMakeLists.txt:18 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "mediamonitor" links to target "Qt5::Widgets" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at tests/unittests/mediamonitor/CMakeLists.txt:18 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "mediamonitor" links to target "Qt5::Widgets" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at tests/unittests/mediamonitor/CMakeLists.txt:18 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "mediamonitor" links to target "Qt5::Widgets" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at tests/unittests/resource/CMakeLists.txt:12 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "resource" links to target "Qt5::Widgets" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at tests/unittests/video/CMakeLists.txt:28 (add_executable): Policy CMP0028 is not set: Double colon in targ
[Touch-packages] [Bug 1495422] Re: CMake warnings: Policy CMP0028 is not set
sorry, I commented on the wrong bug! Ignore the comment above! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1495422 Title: CMake warnings: Policy CMP0028 is not set Status in gallery-app package in Ubuntu: New Bug description: I get a bunch of CMake warnings when I try to compile gallery-app: tim@ubuntu:~/dev/r/gallery-app$ cmake . -- Could NOT find Lcov (missing: LCOV_EXECUTABLE GENHTML_EXECUTABLE) -- Could NOT find gcovr (missing: GCOVR_EXECUTABLE) -- Autopilot tests enabled. -- Configuring done CMake Warning (dev) at src/CMakeLists.txt:51 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "gallery-app" links to target "Qt5::Xml" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at src/medialoader/CMakeLists.txt:27 (add_library): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "gallery-medialoader" links to target "Qt5::Widgets" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at tests/unittests/command-line-parser/CMakeLists.txt:12 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "command-line-parser" links to target "Qt5::Widgets" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at tests/unittests/mediamonitor/CMakeLists.txt:18 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "mediamonitor" links to target "Qt5::Widgets" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at tests/unittests/mediamonitor/CMakeLists.txt:18 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "mediamonitor" links to target "Qt5::Widgets" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at tests/unittests/mediamonitor/CMakeLists.txt:18 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "mediamonitor" links to target "Qt5::Widgets" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at tests/unittests/resource/CMakeLists.txt:12 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the policy and suppress this warning. Target "resource" links to target "Qt5::Widgets" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at tests/unittests/video/CMakeLists.txt:28 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy details. Use the cmake_policy command to set the
[Touch-packages] [Bug 1495436] [NEW] Apport sometimes sends notifications with no Subject
Public bug reported: When Apport comments on a Launchpad bug report with the stacktrace, it seems to set a Subject line of "" for the comment. This is not useful. It results in Launchpad sending out an e-mail notification with "Subject: [Bug ] ", omitting the usual bug summary. Probably this bug should be fixed at the same time as bug 534461. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Example e-mail message" https://bugs.launchpad.net/bugs/1495436/+attachment/4463891/+files/%5BBug%201271233%5D.eml -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1495436 Title: Apport sometimes sends notifications with no Subject Status in apport package in Ubuntu: New Bug description: When Apport comments on a Launchpad bug report with the stacktrace, it seems to set a Subject line of "" for the comment. This is not useful. It results in Launchpad sending out an e-mail notification with "Subject: [Bug ] ", omitting the usual bug summary. Probably this bug should be fixed at the same time as bug 534461. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1495436/+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 534461] Re: apport-collect should use the bug title, not the attachment name
** Description changed: Binary package hint: apport This is on up-to-date lucid installed afresh from alpha 3. When apport-collect is run, it makes Launchpad send a series of emails titled "[Bug ] ". The title should be "[Bug ] ". While this might seem a pedantic point, it does make a difference if the email client a bug subscriber uses gathers emails by subject to display "email conversations", like GMail does. Then all email notifications pertaining to the same bug report, be they from apport-collect, from the Launchpad web interface or from direct email replies, would show up in the same "conversation". + Fixing this bug may also fix bug 1495436. + ProblemType: Bug ApportLog: - + Architecture: i386 Date: Mon Mar 8 15:17:47 2010 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1) Package: apport 1.12.1-0ubuntu5 PackageArchitecture: all ProcEnviron: - PATH=(custom, user) - LANG=en_GB.utf8 - SHELL=/bin/bash + PATH=(custom, user) + LANG=en_GB.utf8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-16.24-generic SourcePackage: apport Uname: Linux 2.6.32-16-generic i686 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/534461 Title: apport-collect should use the bug title, not the attachment name Status in apport package in Ubuntu: New Bug description: Binary package hint: apport This is on up-to-date lucid installed afresh from alpha 3. When apport-collect is run, it makes Launchpad send a series of emails titled "[Bug ] ". The title should be "[Bug ] ". While this might seem a pedantic point, it does make a difference if the email client a bug subscriber uses gathers emails by subject to display "email conversations", like GMail does. Then all email notifications pertaining to the same bug report, be they from apport-collect, from the Launchpad web interface or from direct email replies, would show up in the same "conversation". Fixing this bug may also fix bug 1495436. ProblemType: Bug ApportLog: Architecture: i386 Date: Mon Mar 8 15:17:47 2010 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1) Package: apport 1.12.1-0ubuntu5 PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_GB.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-16.24-generic SourcePackage: apport Uname: Linux 2.6.32-16-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/534461/+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 1495437] [NEW] Arale gets hot with camera-app opened and phone locked
You have been subscribed to a public bug: Test case. - Open camera app. - Lock the device. - Wait 15 minutes. Expected result. - Device is correctly suspended and doesn't make heavy use of the CPU. Actual result. - The device gets hot. current build number: 111 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en ** Affects: camera-app (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: qa-silo -- Arale gets hot with camera-app opened and phone locked https://bugs.launchpad.net/bugs/1495437 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app 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 1475850] Re: Several update-rc.d/insserv warnings
You are right about that one: Preparing to unpack .../cron_3.0pl1-127ubuntu1_i386.deb ... Unpacking cron (3.0pl1-127ubuntu1) over (3.0pl1-127ubuntu1) ... Processing triggers for man-db (2.7.3-1) ... Processing triggers for systemd (225-1ubuntu4) ... Processing triggers for ureadahead (0.100.0-19) ... Setting up cron (3.0pl1-127ubuntu1) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: stop runlevel arguments (1) do not match cron Default-Stop values (none) Looks like its one of the non transitionned yet, the latest upgrade is quite old: cron (3.0pl1-127ubuntu1) vivid; urgency=low * Merge from Debian unstable. Remaining changes: - debian/control: + Move MTA to Suggests field. - debian/cron.upstart: Add Upstart script. - debian/rules: Call dh_installinit to install Upstart job properly. - d/cron.default: change to a deprecated message to make it clear that the file is no longer in use. -- Michael Vogt Mon, 27 Oct 2014 10:19:21 +0100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to insserv in Ubuntu. https://bugs.launchpad.net/bugs/1475850 Title: Several update-rc.d/insserv warnings Status in insserv package in Ubuntu: Confirmed Status in sysvinit package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 15.10 dev with insserv 1.14.0-5ubuntu3 and sysv-rc 2.88dsf-59.2ubuntu1 and on configuring packages I have seen now for some time several update-rc.d/insserv warnings. If I'm reconfiguring all packages installed on my system they appear on: - cron 3.0pl1-127ubuntu1: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: stop runlevel arguments (1) do not match cron Default-Stop values (none) insserv: warning: current stop runlevel(s) (1) of script `cron' overrides LSB defaults (empty). - cryptsetup 2:1.6.1-1ubuntu7: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults - grub-common 2.02~beta2-26ubuntu3: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults - keyboard-configuration 1.108ubuntu5: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults - ntp 1:4.2.6.p5+dfsg-3ubuntu6: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults - procps 1:3.3.9-1ubuntu8: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults - x11-common 1:7.7+7ubuntu4: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/insserv/+bug/1475850/+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 1495437] Re: Arale gets hot with camera-app opened and phone locked
Confirmed on arale 111, when the device is suspended camera_service uses ~45% CPU. ** Project changed: camera-app => camera-app (Ubuntu) ** Changed in: camera-app (Ubuntu) Status: New => Confirmed ** Changed in: camera-app (Ubuntu) Importance: Undecided => Critical ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Importance: Undecided => Critical ** Changed in: canonical-devices-system-image Milestone: None => ww40-2015 ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Bill Filler (bfiller) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1495437 Title: Arale gets hot with camera-app opened and phone locked Status in Canonical System Image: Confirmed Status in camera-app package in Ubuntu: Confirmed Bug description: Test case. - Open camera app. - Lock the device. - Wait 15 minutes. Expected result. - Device is correctly suspended and doesn't make heavy use of the CPU. Actual result. - The device gets hot. current build number: 111 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495437/+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 1495408] Re: Black square in header
Bug can be reproduced by running the qml code below, clicking the 'next'
button, and then clicking the back button in the header:
import QtQuick 2.4
import Ubuntu.Components 1.2
MainView {
width: units.gu(40)
height: units.gu(60)
Component.onCompleted: pageStack.push(page1)
PageStack {
id: pageStack
}
Page {
id: page1
title: "one"
Button {
anchors.centerIn: parent
text: "next"
onClicked: pageStack.push(page2)
}
}
Page {
id: page2
title: "two"
visible: false
head.backAction: Action {
iconName: "back"
onTriggered: pageStack.pop()
}
}
}
--
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/1495408
Title:
Black square in header
Status in Canonical System Image:
Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
current build number: 122
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
Same on latest arale
There is a black square in the header in several applications
(address-book, messaging, dialler, cf screenshots)
To display the black square:
- dialler: open 'Recent calls'
- messaging: tap on a message and go back
- contact: tap on a contact
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495408/+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 1495441] [NEW] Oom killer can trigger a crash which will cause a lot of io on the cpu stopping the call from being answered
You have been subscribed to a public bug: STEPS: 1. On a BQ device install the terminal and d-day tower defense 2. Open the terminal and run free -h 3. Open d-day and start the game playing 4. Flip back to the terminal and run free -h again 5. There should be about 21MB free 6. Put the phone to sleep 7. Now call the phone 8. As the dialer app is opened it looks like the oom killer kills the open apps which in turn triggers apport which then hog the cpu EXPECT: I expect to the able to answer the call with no issues ACTUAL: The phone can lock up completely making it impossible to answer the call, the call goes to answering machine and when the phone is able to be used you get the missed call notification. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: qa-manual-testing -- Oom killer can trigger a crash which will cause a lot of io on the cpu stopping the call from being answered https://bugs.launchpad.net/bugs/1495441 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 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 1495447] [NEW] problem_ubuntu.14.04.3
Public bug reported: several times I tried to "boot-format" a USB-stick with help of "Startmedienersteller", which in fact does not works! in the upstart procedere shows "schwerwiegender Fehler im Root-system" ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-29.31~14.04.1-generic 3.19.8-ckt6 Uname: Linux 3.19.0-29-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.13 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: Mon Sep 14 11:56:56 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0860] InstallationDate: Installed on 2015-09-10 (3 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Acer Aspire E3-111 ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-29-generic 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: 09/12/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.29 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Roxy dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.29:bd09/12/2014:svnAcer:pnAspireE3-111:pvrV1.29:rvnAcer:rnRoxy:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E3-111 dmi.product.version: V1.29 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Sep 14 11:52:38 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8540 vendor AUO xserver.version: 2:1.17.1-0ubuntu3.1~trusty1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- 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/1495447 Title: problem_ubuntu.14.04.3 Status in xorg package in Ubuntu: New Bug description: several times I tried to "boot-format" a USB-stick with help of "Startmedienersteller", which in fact does not works! in the upstart procedere shows "schwerwiegender Fehler im Root-system" ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-29.31~14.04.1-generic 3.19.8-ckt6 Uname: Linux 3.19.0-29-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.13 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: Mon Sep 14 11:56:56 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0860] InstallationDate: Installed on 2015-09-10 (3 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Acer Aspire E3-111 ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-29-generic 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: 09/12/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.29 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Roxy dmi.board.
[Touch-packages] [Bug 1495408] Re: Black square in header
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Tim Peeters (tpeeters) => Zsombor Egri (zsombi) ** Changed in: canonical-devices-system-image 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/1495408 Title: Black square in header Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en Same on latest arale There is a black square in the header in several applications (address-book, messaging, dialler, cf screenshots) To display the black square: - dialler: open 'Recent calls' - messaging: tap on a message and go back - contact: tap on a contact To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495408/+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 1495441] Re: Oom killer can trigger a crash which will cause a lot of io on the cpu stopping the call from being answered
** Package changed: linux (Ubuntu) => unity8 (Ubuntu) -- 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/1495441 Title: Oom killer can trigger a crash which will cause a lot of io on the cpu stopping the call from being answered Status in Canonical System Image: New Status in unity8 package in Ubuntu: New Bug description: STEPS: 1. On a BQ device install the terminal and d-day tower defense 2. Open the terminal and run free -h 3. Open d-day and start the game playing 4. Flip back to the terminal and run free -h again 5. There should be about 21MB free 6. Put the phone to sleep 7. Now call the phone 8. As the dialer app is opened it looks like the oom killer kills the open apps which in turn triggers apport which then hog the cpu EXPECT: I expect to the able to answer the call with no issues ACTUAL: The phone can lock up completely making it impossible to answer the call, the call goes to answering machine and when the phone is able to be used you get the missed call notification. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495441/+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 1495408] Re: Black square in header
** Changed in: canonical-devices-system-image Assignee: (unassigned) => Zsombor Egri (zsombi) -- 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/1495408 Title: Black square in header Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en Same on latest arale There is a black square in the header in several applications (address-book, messaging, dialler, cf screenshots) To display the black square: - dialler: open 'Recent calls' - messaging: tap on a message and go back - contact: tap on a contact To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495408/+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 1495451] Re: Page pushed on a stack gets instantiated twice, and PageStack.push() returns null
** Attachment added: "test.qml" https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495451/+attachment/4463941/+files/test.qml -- 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/1495451 Title: Page pushed on a stack gets instantiated twice, and PageStack.push() returns null Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: It looks to me like a regression introduced by the latest UITK landing (1.3.1627+15.04.20150908-0ubuntu1). See the attached standalone reproducer (run it with qmlscene). In a MainView, pushing a page component on a page stack instantiates the page twice. Additionally, the result of pageStack.push(pageComponent) is null, and it seems the 'currentPage' property of the stack is not updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495451/+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 1495451] Re: Page pushed on a stack gets instantiated twice, and PageStack.push() returns null
Is my example code doing something obviously wrong that would trigger this behaviour, or is this a valid bug? -- 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/1495451 Title: Page pushed on a stack gets instantiated twice, and PageStack.push() returns null Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: It looks to me like a regression introduced by the latest UITK landing (1.3.1627+15.04.20150908-0ubuntu1). See the attached standalone reproducer (run it with qmlscene). In a MainView, pushing a page component on a page stack instantiates the page twice. Additionally, the result of pageStack.push(pageComponent) is null, and it seems the 'currentPage' property of the stack is not updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495451/+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 1495451] Re: Page pushed on a stack gets instantiated twice, and PageStack.push() returns null
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided => Critical -- 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/1495451 Title: Page pushed on a stack gets instantiated twice, and PageStack.push() returns null Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: It looks to me like a regression introduced by the latest UITK landing (1.3.1627+15.04.20150908-0ubuntu1). See the attached standalone reproducer (run it with qmlscene). In a MainView, pushing a page component on a page stack instantiates the page twice. Additionally, the result of pageStack.push(pageComponent) is null, and it seems the 'currentPage' property of the stack is not updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495451/+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 1495451] [NEW] Page pushed on a stack gets instantiated twice, and PageStack.push() returns null
Public bug reported: It looks to me like a regression introduced by the latest UITK landing (1.3.1627+15.04.20150908-0ubuntu1). See the attached standalone reproducer (run it with qmlscene). In a MainView, pushing a page component on a page stack instantiates the page twice. Additionally, the result of pageStack.push(pageComponent) is null, and it seems the 'currentPage' property of the stack is not updated. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Critical Assignee: Zsombor Egri (zsombi) Status: 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/1495451 Title: Page pushed on a stack gets instantiated twice, and PageStack.push() returns null Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: It looks to me like a regression introduced by the latest UITK landing (1.3.1627+15.04.20150908-0ubuntu1). See the attached standalone reproducer (run it with qmlscene). In a MainView, pushing a page component on a page stack instantiates the page twice. Additionally, the result of pageStack.push(pageComponent) is null, and it seems the 'currentPage' property of the stack is not updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495451/+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 1495451] Re: Page pushed on a stack gets instantiated twice, and PageStack.push() returns null
I’m also seeing the following error printed twice on the console, I guess it’s related: file:///usr/lib/arm-linux- gnueabihf/qt5/qml/Ubuntu/Components/1.3/PageWrapperUtils.js:45: TypeError: Type error -- 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/1495451 Title: Page pushed on a stack gets instantiated twice, and PageStack.push() returns null Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: It looks to me like a regression introduced by the latest UITK landing (1.3.1627+15.04.20150908-0ubuntu1). See the attached standalone reproducer (run it with qmlscene). In a MainView, pushing a page component on a page stack instantiates the page twice. Additionally, the result of pageStack.push(pageComponent) is null, and it seems the 'currentPage' property of the stack is not updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495451/+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 471646] Re: [K8M800]with kernel 2.6.31-14-generic my X server crashes during KDE 4.3.2 startup, _mesa_reference_renderbuffer() assertion
** Changed in: xserver-xorg-video-openchrome (Ubuntu) Status: Triaged => Fix Released ** No longer affects: xserver-xorg-video-openchrome (Ubuntu) -- 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/471646 Title: [K8M800]with kernel 2.6.31-14-generic my X server crashes during KDE 4.3.2 startup, _mesa_reference_renderbuffer() assertion Status in openchrome: New Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Invalid Status in Debian: Fix Released Status in Gentoo Linux: New Bug description: I just upgraded my Jaunty machine running Linux 2.6.28-16-generic to Karmic running Linux 2.6.31-14-generic, and noticed that KDE crashes back to the KDM login screen during startup. I can run Fluxbox just fine, and KDE works if I boot into Linux 2.6.28-16-generic. I can also startx remotely over Xephyr/SSH. Locally, however, I get the following error in kdm.log (and output during startx): =[ CUT ]= X.Org X Server 1.6.4 Release Date: 2009-9-27 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.24-23-server i686 Ubuntu Current Operating System: Linux phoenix 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 Kernel command line: root=UUID=c29b60cc-e6ef-450c-b3c5-ea761c6e3416 ro single Build Date: 26 October 2009 05:15:02PM xorg-server 2:1.6.4-2ubuntu4 (buildd@) Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon Nov 2 14:39:52 2009 (==) Using config file: "/etc/X11/xorg.conf" Fulfilled via DRI at 20976640 Freed 20976640 (pool 2) X: main/renderbuffer.c:2159: _mesa_reference_renderbuffer: Assertion `oldRb->Magic == 0xaabbccdd' failed. xinit: connection to X server lost. =[ CUT ]= I'm using a VIA Technologies, Inc. K8M800/K8N800/K8N800A [S3 UniChrome Pro] (rev 01) video chipset with the xserver-xorg-video-openchrome driver, and the crash occurs whether I use an xorg.conf or not. The xorg.conf, if used, is =[ CUT ]= Section "Device" Identifier "Configured Video Device" Option "UseFBDev" "true" EndSection Section "Monitor" Identifier "Configured Monitor" Option "DPMS" HorizSync 31.5-65.2 # 31.5-37.9 EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" Device "Configured Video Device" DefaultDepth24 SubSection "Display" Depth24 Modes"1280x1024" EndSubSection EndSection =[ CUT ]= I'd appreciate any help with this matter, and advice about other information that I should provide. Thanks! ProblemType: Bug Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer', '/dev/sequencer2'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'V8237'/'VIA 8237 with ALC655 at 0xd400, irq 22' Mixer name : 'Realtek ALC655 rev 0' Components : 'AC97a:414c4760' Controls : 48 Simple ctrls : 29 Date: Mon Nov 2 15:29:22 2009 DistroRelease: Ubuntu 9.10 HibernationDevice: RESUME=UUID=f4ed7091-30d8-4c93-9e4b-e7ae7eb77d34 Package: linux-image-2.6.31-14-generic 2.6.31-14.48 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=c29b60cc-e6ef-450c-b3c5-ea761c6e3416 ro quiet splash ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic RelatedPackageVersions: linux-backports-modules-2.6.31-14-generic N/A linux-firmware 1.24 RfKill: SourcePackage: linux Uname: Linux 2.6.31-14-generic i686 WpaSupplicantLog: XsessionErrors: (process:3009): Gtk-CRITICAL **: gtk_clipboard_get_for_display: assertion `display != NULL' failed (:3009): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed dmi.bios.date: 12/29/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: K8M800-8237 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd12/29/2006:svn:pn:pvr:rvn:rnK8M800-8237:rvr:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/openchrome/+bug/47
[Touch-packages] [Bug 1492783] Re: GPS does not work on my Bq E5
@Ladela: please mark the bug as "affecting me" in the top left corner if
you haven't done so.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1492783
Title:
GPS does not work on my Bq E5
Status in location-service package in Ubuntu:
Confirmed
Bug description:
I have a Bq E5 (not an E4.5) and the GPS does not seem to work. The
SensorsStatus app shows GPS as returning no results for location
(every reading ("Latitude", "Longitude", etc) is shown as a dash,
except "Method" which is "Satellite" and "Speed" which is "nan") . I
have attached various logfiles in the hope that they will help. I have
tried turning off location detection and GPS and turning them back on
again, to no avail. I have also tried turning off wifi, to no avail.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1492783/+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 1495451] Re: Page pushed on a stack gets instantiated twice, and PageStack.push() returns null
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Zsombor Egri (zsombi) -- 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/1495451 Title: Page pushed on a stack gets instantiated twice, and PageStack.push() returns null Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: It looks to me like a regression introduced by the latest UITK landing (1.3.1627+15.04.20150908-0ubuntu1). See the attached standalone reproducer (run it with qmlscene). In a MainView, pushing a page component on a page stack instantiates the page twice. Additionally, the result of pageStack.push(pageComponent) is null, and it seems the 'currentPage' property of the stack is not updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495451/+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 1495453] [NEW] atk6-flood_router26 wlan0 makes network crash
Public bug reported: Install thc-ipv6 and do a sudo atk6-flood_router26 wlan0 (it was wireless network in my case) and the internet connection is lost. You can't access the web you can't ping or do anything on the world wide web. If you stop the operation (Ctrl + C) the state continues, so still nothing, only after manually connecting to the network will it work, and sometimes when trying to reconnect it will give me: Device disconnect failed. I'm using Ubuntu 15.04 64-bit. Neither should my internet access stop, or the network manager behave like that. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1495453 Title: atk6-flood_router26 wlan0 makes network crash Status in network-manager package in Ubuntu: New Bug description: Install thc-ipv6 and do a sudo atk6-flood_router26 wlan0 (it was wireless network in my case) and the internet connection is lost. You can't access the web you can't ping or do anything on the world wide web. If you stop the operation (Ctrl + C) the state continues, so still nothing, only after manually connecting to the network will it work, and sometimes when trying to reconnect it will give me: Device disconnect failed. I'm using Ubuntu 15.04 64-bit. Neither should my internet access stop, or the network manager behave like that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1495453/+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 1495458] [NEW] Black screen when resuming after sleep
Public bug reported: I have a fresh install of Kubuntu Wily Beta 1. My laptop is a Dell XPS 15 with a Nvidia video. I tried both drivers nouveau and nvidia with the same result. I can reproduce the error ALWAYS, when I put the laptop to sleep it wont resume, I can see the power light and the keyboard backlight turning on as if it will wake up, but then just a black screen. I cannot even switch to a terminal (Ctr+Alt+F1), the only solution it to restart. The problem is not only when sleeping, it also happens when the screen is turned off by Power Management. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Sep 14 20:29:21 2015 InstallationDate: Installed on 2015-09-12 (1 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug fonts kubuntu wily -- 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/1495458 Title: Black screen when resuming after sleep Status in xorg package in Ubuntu: New Bug description: I have a fresh install of Kubuntu Wily Beta 1. My laptop is a Dell XPS 15 with a Nvidia video. I tried both drivers nouveau and nvidia with the same result. I can reproduce the error ALWAYS, when I put the laptop to sleep it wont resume, I can see the power light and the keyboard backlight turning on as if it will wake up, but then just a black screen. I cannot even switch to a terminal (Ctr+Alt+F1), the only solution it to restart. The problem is not only when sleeping, it also happens when the screen is turned off by Power Management. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Sep 14 20:29:21 2015 InstallationDate: Installed on 2015-09-12 (1 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1495458/+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 1495461] [NEW] Phone freezes when trying to record a video
Public bug reported: [Description] This bug affects both E4.5 and E5 devices, as reported by some users on IRC. I use: OS build number: 5 Ubuntu image part: 20150825.1 Device build: VEGETA01A-S23A_BQ_L100EN_2005_150825 Customization image part: 20150821-887-33-32-vivid [Reproduction] Whenever I try to record a video on my E5 and I switch in the camera app from taking pictures to record videos and hit the record button the phone freezes. ** Affects: camera-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 camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1495461 Title: Phone freezes when trying to record a video Status in camera-app package in Ubuntu: New Bug description: [Description] This bug affects both E4.5 and E5 devices, as reported by some users on IRC. I use: OS build number: 5 Ubuntu image part: 20150825.1 Device build: VEGETA01A-S23A_BQ_L100EN_2005_150825 Customization image part: 20150821-887-33-32-vivid [Reproduction] Whenever I try to record a video on my E5 and I switch in the camera app from taking pictures to record videos and hit the record button the phone freezes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1495461/+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 534461] Re: apport-collect should use the bug title, not the attachment name
My original argument is wrong: email messages are arranged in "conversations" by their "In-Reply-To" field, not their subject. In any case, it would be useful to have meaningful subject and "In-Reply-To" fields set in all messages from Launchpad. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/534461 Title: apport-collect should use the bug title, not the attachment name Status in apport package in Ubuntu: New Bug description: Binary package hint: apport This is on up-to-date lucid installed afresh from alpha 3. When apport-collect is run, it makes Launchpad send a series of emails titled "[Bug ] ". The title should be "[Bug ] ". While this might seem a pedantic point, it does make a difference if the email client a bug subscriber uses gathers emails by subject to display "email conversations", like GMail does. Then all email notifications pertaining to the same bug report, be they from apport-collect, from the Launchpad web interface or from direct email replies, would show up in the same "conversation". Fixing this bug may also fix bug 1495436. ProblemType: Bug ApportLog: Architecture: i386 Date: Mon Mar 8 15:17:47 2010 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1) Package: apport 1.12.1-0ubuntu5 PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_GB.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-16.24-generic SourcePackage: apport Uname: Linux 2.6.32-16-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/534461/+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 1450960] Re: dev file system is mounted without noexec
This also applies when booting systemd without an initramfs. NOSUID is already set, but not NOEXEC. I proposed that in https://github.com/systemd/systemd/pull/1265 ** Changed in: systemd (Ubuntu) Status: Invalid => In Progress -- 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/1450960 Title: dev file system is mounted without noexec Status in initramfs-tools package in Ubuntu: Triaged Status in lxc package in Ubuntu: Confirmed Status in systemd package in Ubuntu: In Progress Bug description: I just found that the /dev filesystem of most Ubuntu system is mounted without noexec, nosuid etc options. If you do everything to harden your system, and you are using squashfs as root file system (which is read-only), such auto-mounted devices can be a serious leak. This volume usually is quite small and for most folders only root has write access, so I don't know how much this bug is security relevant, but I think there is no reason to not change the mount options for /dev. And especially for LXC containers, I don't even know a workaround to fix it. STEPS TO REPRODUCE: me:~# cat >/dev/call-me.sh <<.e > #!/bin/sh > echo "I'm executable" > .e me:~# chmod +x /dev/call-me.sh me:~# /dev/call-me.sh I'm executable EXPECTED BEHAVIOUR me:~# /dev/call-me.sh -bash: /dev/call-me.sh: Permission denied WORKAROUND me:~# mount -oremount,noexec,nosuid /dev me:~# /dev/call-me.sh -bash: /dev/call-me.sh: Permission denied Unfortunately, this workaround doesn't work in LXC containers (where the same problem occurs) because of missing capabilities. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.11 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: XFCE CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied CustomUdevRuleFiles: 51-android.rules 60-vboxdrv.rules Date: Sat May 2 01:48:26 2015 MachineType: Gigabyte Technology Co., Ltd. H97-HD3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=/dev/mapper/vg_ssd-lv_system_trusty1404 ro SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2014-04-18 (378 days ago) dmi.bios.date: 06/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97-HD3 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: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/26/2014:svnGigabyteTechnologyCo.,Ltd.:pnH97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H97-HD3 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/1450960/+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 1495461] Re: Phone freezes when trying to record a video
Update: I tried before about 6 times and I got the above, now I tried again, I got prompted this time to allow mic access and recording all of a sudden works. Some users on IRC reported still having the issue but in different ways. I hope they will respond to this bug or file new ones. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1495461 Title: Phone freezes when trying to record a video Status in camera-app package in Ubuntu: New Bug description: [Description] This bug affects both E4.5 and E5 devices, as reported by some users on IRC. I use: OS build number: 5 Ubuntu image part: 20150825.1 Device build: VEGETA01A-S23A_BQ_L100EN_2005_150825 Customization image part: 20150821-887-33-32-vivid [Reproduction] Whenever I try to record a video on my E5 and I switch in the camera app from taking pictures to record videos and hit the record button the phone freezes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1495461/+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 1495461] Re: Phone freezes when trying to record a video
I can confirm this bug on my Bq E 4.5. Not the whole phone freezes, but the camera app. In the system settings, no app has access to the microphone. The camera app never asked for access. After some trying and fiddling, I could get the camera app to record video, but without sound. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1495461 Title: Phone freezes when trying to record a video Status in camera-app package in Ubuntu: New Bug description: [Description] This bug affects both E4.5 and E5 devices, as reported by some users on IRC. I use: OS build number: 5 Ubuntu image part: 20150825.1 Device build: VEGETA01A-S23A_BQ_L100EN_2005_150825 Customization image part: 20150821-887-33-32-vivid [Reproduction] Whenever I try to record a video on my E5 and I switch in the camera app from taking pictures to record videos and hit the record button the phone freezes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1495461/+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 1495467] Re: Memory leak on previews
** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Albert Astals Cid (aacid) ** Changed in: unity-scopes-shell (Ubuntu) Assignee: (unassigned) => Albert Astals Cid (aacid) ** Changed in: unity-scopes-shell (Ubuntu) Status: New => In Progress ** Changed in: unity8 (Ubuntu) Status: New => In Progress ** Changed in: unity-scopes-shell (Ubuntu) Importance: Undecided => High ** Changed in: unity8 (Ubuntu) Importance: Undecided => High ** Branch linked: lp:~aacid/unity8/keepPreviewStackAround -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1495467 Title: Memory leak on previews Status in unity-scopes-shell package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: Preview stack objects leak memory because of the custom QObject::event() handlers that shell plugin uses. These event handlers need to call base QOBject::event for unhandled events, and unity8 needs to make sure it keeps the reference to PreviewStack object (not just preview model) for as long as needed till the preview is closed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1495467/+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 1495467] [NEW] Memory leak on previews
Public bug reported: Preview stack objects leak memory because of the custom QObject::event() handlers that shell plugin uses. These event handlers need to call base QOBject::event for unhandled events, and unity8 needs to make sure it keeps the reference to PreviewStack object (not just preview model) for as long as needed till the preview is closed. ** Affects: unity-scopes-shell (Ubuntu) Importance: High Assignee: Albert Astals Cid (aacid) Status: In Progress ** Affects: unity8 (Ubuntu) Importance: High Assignee: Albert Astals Cid (aacid) Status: In Progress ** Also 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 unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1495467 Title: Memory leak on previews Status in unity-scopes-shell package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: Preview stack objects leak memory because of the custom QObject::event() handlers that shell plugin uses. These event handlers need to call base QOBject::event for unhandled events, and unity8 needs to make sure it keeps the reference to PreviewStack object (not just preview model) for as long as needed till the preview is closed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1495467/+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 1491542] Re: libunity ftbfs in wily
This bug was fixed in the package libunity -
7.1.4+15.10.20150911-0ubuntu1
---
libunity (7.1.4+15.10.20150911-0ubuntu1) wily; urgency=medium
* Tools: use proper type prefix to fix FTB (LP: #1491542)
-- Marco Trevisan (Treviño) Fri, 11 Sep 2015 14:54:05
+
** Changed in: libunity (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 libunity in Ubuntu.
https://bugs.launchpad.net/bugs/1491542
Title:
libunity ftbfs in wily
Status in libunity:
In Progress
Status in libunity package in Ubuntu:
Fix Released
Bug description:
libunity seems to no longer be buildable in wily. This is a problem
because it must be rebuilt for Python 3.5, but it is failing for
unrelated reasons. Here's an excerpt of the build log from a local
build using the current wily source package:
/usr/bin/glib-compile-resources --sourcedir . --target=unity-tool-res.c
--generate-source unity-tool-res.gresource.xml
/usr/bin/valac -C --vapidir ../vapi --vapidir=../protocol --vapidir=../src
--pkg config --pkg gtk+-3.0 --pkg gmodule-2.0 --pkg unity-internal --pkg
unity-protocol --pkg glib-2.0 --pkg gmodule-2.0 --pkg gobject-2.0 --pkg gio-2.0
--pkg gio-unix-2.0 --pkg dee-1.0 --pkg Dbusmenu-0.4 unity-tool.vala
unity-tool-dbus-util.vala unity-tool-ui.vala preview-renderer.vala
music-track-model-renderer.vala
unity-tool-ui.vala:846.13-846.21: error: `ListStore' is an ambiguous
reference between `GLib.ListStore' and `Gtk.ListStore'
private ListStore uimodel = null;
^
unity-tool-ui.vala:847.13-847.21: error: `ListStore' is an ambiguous
reference between `GLib.ListStore' and `Gtk.ListStore'
private ListStore ui_filter_model = null;
^
unity-tool-ui.vala:848.13-848.21: error: `ListStore' is an ambiguous
reference between `GLib.ListStore' and `Gtk.ListStore'
private ListStore scope_list_model = null;
^
unity-tool-ui.vala:849.13-849.21: error: `ListStore' is an ambiguous
reference between `GLib.ListStore' and `Gtk.ListStore'
private ListStore ui_cat_model = null;
^
unity-tool-ui.vala:43.62-43.70: error: `ListStore' is an ambiguous reference
between `GLib.ListStore' and `Gtk.ListStore'
uimodel = builder.get_object("results_model") as ListStore;
^
unity-tool-ui.vala:44.70-44.78: error: `ListStore' is an ambiguous reference
between `GLib.ListStore' and `Gtk.ListStore'
ui_filter_model = builder.get_object("filters_model") as
ListStore;
^
unity-tool-ui.vala:45.70-45.78: error: `ListStore' is an ambiguous reference
between `GLib.ListStore' and `Gtk.ListStore'
ui_cat_model = builder.get_object("categories_model") as
ListStore;
^
unity-tool-ui.vala:158.74-158.82: error: `ListStore' is an ambiguous
reference between `GLib.ListStore' and `Gtk.ListStore'
scope_list_model = builder.get_object("scope_list_model") as
ListStore;
^
music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
public ListStore track_view_model { get; construct; }
^
music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
public ListStore track_view_model { get; construct; }
^
music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
public ListStore track_view_model { get; construct; }
^
music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
public ListStore track_view_model { get; construct; }
^
Compilation failed: 12 error(s), 0 warning(s)
Seems like the same problem in all cases, and I'm not sure which
ListStore is intended. Full buildlog is available in the Python 3.5
-as-default PPA:
https://launchpadlibrarian.net/216183170/buildlog_ubuntu-wily-
amd64.libunity_7.1.4%2B14.10.20140808-0ubuntu1_BUILDING.txt.gz
This is blocking several other critical packages which need updating
for Python 3.5.
To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/1491542/+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
[Touch-packages] [Bug 1448566] Re: Ubuntu 15.04 - Macbook Pro Early 2015 (12, 1) Bluetooth disabled
I confirm the test fix described in the mailing-list thread pointed by @morphis makes the controller work almost correctly. I was able to use my BT keyboard and trackpad without problem. However, I failed to use my phone as a remote connection. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1448566 Title: Ubuntu 15.04 - Macbook Pro Early 2015 (12,1) Bluetooth disabled Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: Fresh install of 15.04 on a Macbook Pro 12,1. I get no Bluetooth icon in the status bar, and in System Settings > Bluetooth, everything is greyed out (i.e., can't turn it on). $lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; rfkill list all; lsmod | grep bluetooth; hciconfig -a; uname -a Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 004: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 32.369395] usb 1-3: Product: Bluetooth USB Host Controller [ 32.435743] input: Broadcom Corp. Bluetooth USB Host Controller as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:05AC:8290.0006/input/input7 [ 32.490662] hid-generic 0003:05AC:8290.0006: input,hidraw5: USB HID v1.11 Keyboard [Broadcom Corp. Bluetooth USB Host Controller] on usb-:00:14.0-3/input0 [ 32.490750] input: Broadcom Corp. Bluetooth USB Host Controller as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.1/0003:05AC:8290.0007/input/input8 [ 32.490995] hid-generic 0003:05AC:8290.0007: input,hidraw6: USB HID v1.11 Mouse [Broadcom Corp. Bluetooth USB Host Controller] on usb-:00:14.0-3/input1 [ 34.866186] Bluetooth: Core ver 2.20 [ 34.866205] Bluetooth: HCI device and connection manager initialized [ 34.866751] Bluetooth: HCI socket layer initialized [ 34.866754] Bluetooth: L2CAP socket layer initialized [ 34.866759] Bluetooth: SCO socket layer initialized [ 0.158493] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored [ 0.168342] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain [bus 00-9b] only partially covers this bridge [ 35.003383] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2 [ 35.290656] brcmf_c_preinit_dcmds: Firmware version = wl0: Mar 13 2015 08:11:08 version 7.35.177.36 (r540934) FWID 01-e4dc15b 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no bluetooth 491520 1 btusb Linux hxn-laptop-linux 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1448566/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails
Then report a bug to them, telling that the print rendering (PDF output) is fixed in Cairo 1.13 and that this needs to get backported somehow into Gecko, either by switching to 1.13 or doing another patch. Please post the link to your bug report(s) here. -- 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/802942 Title: printing PDFs (and other complex documents) from GTK applications fails Status in cups package in Ubuntu: Invalid Status in cups-filters package in Ubuntu: New Status in firefox package in Ubuntu: New Status in thunderbird package in Ubuntu: New Bug description: Hello, I'm discovering a bug when printing complex PDFs or other complex documents from GTK applications. Printing complex PDFs from evince, or sometimes even printing comples webpages from firefox result in one error page being printed instead of the document content: +-+ | ERROR NAME;| | undefined| | COMMAND; | | Q| | OPERAND STACK; | +-+ My printer is a Brother HL 5270DN. It doesn't matter whether the printer is connected via USB or as network printer. In both cases the described bug does happen. The PPD I use is "Brother HL-5270DN BR- Script3", similar to the one at http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd I discovered this bug in up-to-date Debian unstable for several years already. Now I switched one of my laptops to Ubuntu Natty (fresh installation), and unfortunately discovered the same bug there as well. I'm pretty sure that this bug is related to bug #419143, and not really in CUPS, but rather in some library (poppler or cairo) used by GTK applications. The same PDFs that produce the described error in evince, print fine in okular. I attach an example PDF that doesn't print in evince, but prints fine in okular. It's sufficient to (try to) print page 1 of the document. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: cups 1.4.6-5ubuntu1.2 ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5 Uname: Linux 2.6.39-0-generic x86_64 Architecture: amd64 CupsErrorLog: Date: Tue Jun 28 13:13:29 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426) Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU MachineType: LENOVO 4180W1H Papersize: a4 PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3 ProcEnviron: LANGUAGE=de:en LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180W1H dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4180W1H dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/802942/+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 1495461] Re: Phone freezes when trying to record a video
After a reboot, the camera app asked for microphone access, and now it works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1495461 Title: Phone freezes when trying to record a video Status in camera-app package in Ubuntu: New Bug description: [Description] This bug affects both E4.5 and E5 devices, as reported by some users on IRC. I use: OS build number: 5 Ubuntu image part: 20150825.1 Device build: VEGETA01A-S23A_BQ_L100EN_2005_150825 Customization image part: 20150821-887-33-32-vivid [Reproduction] Whenever I try to record a video on my E5 and I switch in the camera app from taking pictures to record videos and hit the record button the phone freezes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1495461/+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 1495471] Re: ListItems.Subtitled subText not visible on SuruDark
** Attachment added: "subtextbug.qml" https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495471/+attachment/4463960/+files/subtextbug.qml -- 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/1495471 Title: ListItems.Subtitled subText not visible on SuruDark Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: As the title says. See attached qml file for an example. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495471/+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 1495471] [NEW] ListItems.Subtitled subText not visible on SuruDark
Public bug reported: As the title says. See attached qml file for an example. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- 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/1495471 Title: ListItems.Subtitled subText not visible on SuruDark Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: As the title says. See attached qml file for an example. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495471/+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 1495473] [NEW] ItemSelector has "highlighted" background always on on SuruDark
Public bug reported: On SuruDark, the ItemSelector looks like being active all the time. See attached example qml. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Attachment added: "selectorbug.qml" https://bugs.launchpad.net/bugs/1495473/+attachment/4463959/+files/selectorbug.qml -- 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/1495473 Title: ItemSelector has "highlighted" background always on on SuruDark Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: On SuruDark, the ItemSelector looks like being active all the time. See attached example qml. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495473/+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 1495475] [NEW] DatePicker hard to use/read when in Dialogs and SuruDark theme
Public bug reported: As the summary says, see attached example qml ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Attachment added: "datepickerbug.qml" https://bugs.launchpad.net/bugs/1495475/+attachment/4463961/+files/datepickerbug.qml -- 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/1495475 Title: DatePicker hard to use/read when in Dialogs and SuruDark theme Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: As the summary says, see attached example qml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495475/+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 1495477] [NEW] TextField placeholderText not visible on SuruDark
Public bug reported: As summary says, see attached example qml. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- 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/1495477 Title: TextField placeholderText not visible on SuruDark Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: As summary says, see attached example qml. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495477/+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 1495477] Re: TextField placeholderText not visible on SuruDark
** Attachment added: "textfieldbug.qml" https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495477/+attachment/4463962/+files/textfieldbug.qml -- 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/1495477 Title: TextField placeholderText not visible on SuruDark Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: As summary says, see attached example qml. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495477/+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 1491566] Re: Shell not responsive after an incoming SMS or call notification
ran combinations of phone call, sms and swiping throughout the weekend, no issue. -- 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/1491566 Title: Shell not responsive after an incoming SMS or call notification Status in Canonical System Image: Confirmed Status in Mir: In Progress Status in unity-system-compositor package in Ubuntu: In Progress Bug description: RC proposed MX4 r100 This happened twice in the last two days Receive an incoming text Screen turns on and notification is shown notification goes away try to interact with the phone and nothing works another text message is received and the notification is displayed Adding incoming calls as also suspected to be triggering the issue Note this has been impossible to reproduce, and in use only happens very rarely To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+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 1484300] Re: /usr/bin/dialer-app:11:QScopedLoopLevelCounter:QCoreApplication::notifyInternal:sendEvent:QCoreApplicationPrivate::sendPostedEvents:QCoreApplication::sendPostedEvent
In top 10 crashes over the past week on stable phones. ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => Critical ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Milestone: None => ww40-2015 ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Bill Filler (bfiller) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1484300 Title: /usr/bin/dialer- app:11:QScopedLoopLevelCounter:QCoreApplication::notifyInternal:sendEvent:QCoreApplicationPrivate::sendPostedEvents:QCoreApplication::sendPostedEvents Status in Canonical System Image: Confirmed Status in dialer-app package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding dialer-app. This problem was most recently seen with version 0.1+15.10.20150615-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/86fd27665d578509408b73f1950422e5b3f31faa contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1484300/+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 1495482] [NEW] SortFilterModel cannot sort by a numeric role
Public bug reported: I’d like to replace a custom model in webbrowser-app with SortFilterModel (my model does both sorting and filtering), but at the moment I can’t because SortFilterModel does its sort on string comparisons, and the role I want to compare on is an integer. 10 > 2, but "2" > "10". Ideally, SortFilterModel would detect the type of the role, and apply the appropriate comparison, instead of casting everything to a string. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- 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/1495482 Title: SortFilterModel cannot sort by a numeric role Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: I’d like to replace a custom model in webbrowser-app with SortFilterModel (my model does both sorting and filtering), but at the moment I can’t because SortFilterModel does its sort on string comparisons, and the role I want to compare on is an integer. 10 > 2, but "2" > "10". Ideally, SortFilterModel would detect the type of the role, and apply the appropriate comparison, instead of casting everything to a string. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495482/+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 1493530] Re: /usr/bin/unity8-dash:6:qt_message_print:qt_message:QMessageLogger::fatal:deallocate:~QString
Trace in top 10 crashes on stable phones. Adding a C.S.I. task. ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => Critical ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Milestone: None => ww40-2015 ** Changed in: canonical-devices-system-image Assignee: (unassigned) => kevin gunn (kgunn72) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1493530 Title: /usr/bin/unity8-dash:6:qt_message_print:qt_message:QMessageLogger::fatal:deallocate:~QString Status in Canonical System Image: Confirmed Status in qtubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.11+15.04.20150821-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/4b65a8a3a3b3a1ec81d12698b84dc4e8dda85187 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1493530/+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 1372011] Re: ListItem.Subtitled subText color is too dark with SuruDark
+1. The SuruDark theme has gotten into a very bad shape by now and is hardly usable for apps any more. -- 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/1372011 Title: ListItem.Subtitled subText color is too dark with SuruDark Status in permy: New Status in Ubuntu UX: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: It is hard to read ListItem.Subtitled subText when using the SuruDark theme (or other dark themes). To manage notifications about this bug go to: https://bugs.launchpad.net/permy/+bug/1372011/+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 1487157] Re: mako and flo should have hotspot disabled
** Changed in: indicator-network (Ubuntu) Status: Confirmed => In Progress ** Changed in: indicator-network (Ubuntu) Assignee: Pete Woods (pete-woods) => Jonas G. Drange (jonas-drange) ** Branch linked: lp:~jonas-drange/ubuntu-system-settings/allow- insecure-hotspot ** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-system-settings (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1487157 Title: mako and flo should have hotspot disabled Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: METABUG FOR OTA6: Mako has an issue with wpa-supplicant that use 100% of the cpu and stops the phone from functioning as expected when hotspot is in use. Mako currently has hotspot installed, it can be enabled but devices can not connect to it. https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1429314 Flo only has one modem wifi which is turn into the outgoing source for hotspot therefore disabling wifi. https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1487158 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487157/+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 1372011] Re: ListItem.Subtitled subText color is too dark with SuruDark
Hi Jamie and Michael, We're working on the colours as we speak. We're aware that the new colours need to fit into the dark and light theme and I'm hoping that when we're done (in the near future) we'll have a set of colours that will solve the problem highlighted in the bug and work for the Dark Theme as well. Thanks for the prod though! On Mon, Sep 14, 2015 at 1:03 PM Michael Zanetti < michael.zane...@canonical.com> wrote: > +1. The SuruDark theme has gotten into a very bad shape by now and is > hardly usable for apps any more. > > -- > You received this bug notification because you are subscribed to Ubuntu > UX. > https://bugs.launchpad.net/bugs/1372011 > > Title: > ListItem.Subtitled subText color is too dark with SuruDark > > Status in permy: > New > Status in Ubuntu UX: > Fix Released > Status in ubuntu-ui-toolkit package in Ubuntu: > Incomplete > > Bug description: > It is hard to read ListItem.Subtitled subText when using the SuruDark > theme (or other dark themes). > > To manage notifications about this bug go to: > https://bugs.launchpad.net/permy/+bug/1372011/+subscriptions > -- Jamie Young Design lead Platform & Apps Design Team Canonical UK Ltd +44 7890 098672 -- 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/1372011 Title: ListItem.Subtitled subText color is too dark with SuruDark Status in permy: New Status in Ubuntu UX: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: It is hard to read ListItem.Subtitled subText when using the SuruDark theme (or other dark themes). To manage notifications about this bug go to: https://bugs.launchpad.net/permy/+bug/1372011/+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 1487157] Re: mako and flo should have hotspot disabled
** Changed in: ubuntu-system-settings (Ubuntu) Assignee: (unassigned) => Jonas G. Drange (jonas-drange) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1487157 Title: mako and flo should have hotspot disabled Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: METABUG FOR OTA6: Mako has an issue with wpa-supplicant that use 100% of the cpu and stops the phone from functioning as expected when hotspot is in use. Mako currently has hotspot installed, it can be enabled but devices can not connect to it. https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1429314 Flo only has one modem wifi which is turn into the outgoing source for hotspot therefore disabling wifi. https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1487158 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487157/+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 1342400] Re: avahi-daemon constantly reporting "Invalid response packet from host"
Im getting this on my Rasspberry Pi 2 also ... every few seconds ... v annoying 192.168.1.15 is a windows 10 box that is hosting a share im connected to using CIFS Sep 14 07:41:22 pi-server avahi-daemon[2628]: Invalid response packet from host 192.168.1.15. Sep 14 07:41:47 pi-server avahi-daemon[2628]: Invalid response packet from host 192.168.1.15. Sep 14 07:41:51 pi-server avahi-daemon[2628]: Invalid response packet from host 192.168.1.15. liked the idea of getting a script to run to clean it out added this into a script file in /etc/cron.hourly sed -i".bak" '/Invalid response packet from host/d' /var/log/syslog seem to work welljust removes the lines directly from the syslog and creates a backup /var/log/syslog.bak -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1342400 Title: avahi-daemon constantly reporting "Invalid response packet from host" Status in avahi package in Ubuntu: Confirmed Bug description: After installing Ubuntu 14.04 (Release: 14.04) and looking for other information in /var/log/syslog, I see that syslog is being flooded by "Invalid response packet from host" messages from avahi-daemon. I searched around to see why this might be and ran across the following avahi mailing list post along with a patch to fix it: http://lists.freedesktop.org/archives/avahi/2012-July/002171.html >>> I would say you can safely ignore it, since any machine on your network running a recent OSX version will cause these messages. Here's a patch with what we change to avoid these messages flooding syslog. -Justin <<< The patch which fixes this is here: http://lists.freedesktop.org/archives/avahi/attachments/20120719/1e71846e/attachment.obj To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1342400/+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 1372011] Re: ListItem.Subtitled subText color is too dark with SuruDark
Hi Jamie and Michael, We're working on the colours as we speak. We're aware that the new colours need to fit into the dark and light theme and I'm hoping that when we're done (in the near future) we'll have a set of colours that will solve the problem highlighted in the bug and work for the Dark Theme as well. Thanks for the prod though! -- 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/1372011 Title: ListItem.Subtitled subText color is too dark with SuruDark Status in permy: New Status in Ubuntu UX: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: It is hard to read ListItem.Subtitled subText when using the SuruDark theme (or other dark themes). To manage notifications about this bug go to: https://bugs.launchpad.net/permy/+bug/1372011/+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 1495467] Re: Memory leak on previews
** Branch linked: lp:~aacid/unity-scopes-shell/eventsFix ** Branch linked: lp:~aacid/unity-scopes-shell/eventsFix1504 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1495467 Title: Memory leak on previews Status in unity-scopes-shell package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: Preview stack objects leak memory because of the custom QObject::event() handlers that shell plugin uses. These event handlers need to call base QOBject::event for unhandled events, and unity8 needs to make sure it keeps the reference to PreviewStack object (not just preview model) for as long as needed till the preview is closed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1495467/+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 1495168] Re: At startup debug windows appear, no evident problem seen
*** This bug is a duplicate of bug 1495148 *** https://bugs.launchpad.net/bugs/1495148 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1495148, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1495168/+attachment/4462741/+files/CoreDump.gz ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1495168/+attachment/4462744/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1495168/+attachment/4462745/+files/ProcStatus.txt ** This bug has been marked a duplicate of private bug 1495148 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1495168 Title: At startup debug windows appear, no evident problem seen Status in libunity package in Ubuntu: New Bug description: This is not a new situation, after starup many crashes signs appears. Before reboot I upgraded system. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: libunity9 7.1.4+14.10.20140808-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-48.64~14.04.1-generic 3.16.7-ckt15 Uname: Linux 3.16.0-48-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 12 20:48:40 2015 ExecutablePath: /usr/bin/unity-scope-loader InstallationDate: Installed on 2015-03-30 (166 days ago) InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS amd64 (20150323) ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope applications/scopes.scope commands.scope SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: libunity UpgradeStatus: Upgraded to wily on 2015-09-01 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1495168/+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 1487157] Re: mako and flo should have hotspot disabled
Hotspot creation is done in exclusively System Settings per the specification, so let's disable it there for now. ** Changed in: indicator-network (Ubuntu) Status: In Progress => Invalid ** Changed in: indicator-network (Ubuntu) Assignee: Jonas G. Drange (jonas-drange) => Pete Woods (pete-woods) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1487157 Title: mako and flo should have hotspot disabled Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: METABUG FOR OTA6: Mako has an issue with wpa-supplicant that use 100% of the cpu and stops the phone from functioning as expected when hotspot is in use. Mako currently has hotspot installed, it can be enabled but devices can not connect to it. https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1429314 Flo only has one modem wifi which is turn into the outgoing source for hotspot therefore disabling wifi. https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1487158 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487157/+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 1495381] Re: pulseaudio crashed with SIGABRT in main()
*** This bug is a duplicate of bug 1425447 *** https://bugs.launchpad.net/bugs/1425447 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1425447, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1495381/+attachment/4463699/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1495381/+attachment/4463702/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1495381/+attachment/4463704/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1495381/+attachment/4463705/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1495381/+attachment/4463706/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1495381/+attachment/4463707/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1495381/+attachment/4463708/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1425447 pulseaudio crashed with SIGABRT in core_free() at login ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1495381 Title: pulseaudio crashed with SIGABRT in main() Status in pulseaudio package in Ubuntu: New Bug description: Reported on boot ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: pulseaudio 1:6.0-0ubuntu11 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pdg2004 F pulseaudio CrashCounter: 1 Date: Mon Sep 14 07:20:56 2015 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2014-10-04 (344 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) LANGUAGE=en_GB:en XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/false PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: ?? () from /usr/lib/libpulsecore-6.0.so main () Title: pulseaudio crashed with SIGABRT in main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 09/04/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 122-CK-NF68 dmi.board.vendor: EVGA dmi.board.version: 2 dmi.chassis.type: 3 dmi.chassis.vendor: EVGA dmi.chassis.version: 122-CK-NF68 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/04/2008:svnEVGA:pn122-CK-NF68:pvr2:rvnEVGA:rn122-CK-NF68:rvr2:cvnEVGA:ct3:cvr122-CK-NF68: dmi.product.name: 122-CK-NF68 dmi.product.version: 2 dmi.sys.vendor: EVGA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1495381/+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 1425447] Re: pulseaudio crashed with SIGABRT in core_free() at login
** Tags added: wily -- 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/1425447 Title: pulseaudio crashed with SIGABRT in core_free() at login Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Incomplete Status in pulseaudio package in Fedora: Unknown Bug description: When I login, I get no sound, a "Dummy Output" device which is not functional, and then an error report about this. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME Date: Wed Feb 25 03:14:39 2015 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2013-09-29 (513 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog Signal: 6 SourcePackage: pulseaudio StacktraceTop: ?? () from /usr/lib/libpulsecore-6.0.so main () Title: pulseaudio crashed with SIGABRT in main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1425447/+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 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all
diff --git a/include/sound/ac97_codec.h b/include/sound/ac97_codec.h
index 0e9d75b..9e659e2 100644
--- a/include/sound/ac97_codec.h
+++ b/include/sound/ac97_codec.h
@@ -31,6 +31,7 @@
#include
#include
#include
+#include
/* maximum number of devices on the AC97 bus */
#defineAC97_BUS_MAX_DEVICES4
@@ -531,6 +532,10 @@ struct snd_ac97 {
struct device dev;
struct snd_pcm_chmap *chmaps[2]; /* channel-maps (optional) */
+
+ struct snd_jack *hp_jack;
+ struct snd_jack *lo_jack;
+ struct snd_jack *sp_jack;
};
#define to_ac97_t(d) container_of(d, struct snd_ac97, dev)
diff --git a/sound/pci/ac97/ac97_patch.c b/sound/pci/ac97/ac97_patch.c
index f4234ed..581000c 100644
--- a/sound/pci/ac97/ac97_patch.c
+++ b/sound/pci/ac97/ac97_patch.c
@@ -1886,6 +1886,23 @@ static int patch_ad1981a(struct snd_ac97 *ac97)
static const struct snd_kcontrol_new snd_ac97_ad198x_2cmic =
AC97_SINGLE("Stereo Mic", AC97_AD_MISC, 6, 1, 0);
+#define AD198X_JS1_ST 0x08
+#define AD198X_JS0_ST 0x04
+
+void ad198x_handle_hp_jack(struct snd_ac97 *ac97)
+{
+ bool hp_plugged = (snd_ac97_read(ac97, AC97_AD_JACK_SPDIF) &
+ AD198X_JS1_ST) == AD198X_JS1_ST;
+ snd_jack_report(ac97->hp_jack, hp_plugged ? SND_JACK_HEADPHONE : 0);
+}
+
+void ad198x_handle_lo_jack(struct snd_ac97 *ac97)
+{
+ bool lo_plugged = (snd_ac97_read(ac97, AC97_AD_JACK_SPDIF) &
+ AD198X_JS0_ST) == AD198X_JS0_ST;
+ snd_jack_report(ac97->lo_jack, lo_plugged ? SND_JACK_LINEOUT : 0);
+}
+
static int patch_ad1981b_specific(struct snd_ac97 *ac97)
{
int err;
@@ -1894,8 +1911,23 @@ static int patch_ad1981b_specific(struct snd_ac97 *ac97)
return err;
if (check_list(ac97, ad1981_jacks_blacklist))
return 0;
- return patch_build_controls(ac97, snd_ac97_ad1981x_jack_sense,
+ err = patch_build_controls(ac97, snd_ac97_ad1981x_jack_sense,
ARRAY_SIZE(snd_ac97_ad1981x_jack_sense));
+ if (err < 0)
+ return err;
+ if (( err = snd_jack_new(ac97->bus->card, "Headphone",
SND_JACK_HEADPHONE,
+ &ac97->hp_jack, true, false)) < 0)
+ return err;
+ ad198x_handle_hp_jack(ac97);
+ if (( err = snd_jack_new(ac97->bus->card, "Line Out", SND_JACK_LINEOUT,
+ &ac97->lo_jack, true, false)) < 0)
+ return err;
+ ad198x_handle_lo_jack(ac97);
+ if (( err = snd_jack_new(ac97->bus->card, "Internal Speaker",
SND_JACK_LINEOUT,
+ &ac97->sp_jack, true, true)) < 0)
+ return err;
+ snd_jack_report(ac97->sp_jack, SND_JACK_LINEOUT);
+ return 0;
}
static const struct snd_ac97_build_ops patch_ad1981b_build_ops = {
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/893210
Title:
[Dell OptiPlex GX620 - AD1981b, playback] No sound at all
Status in ALSA driver:
Confirmed
Status in alsa-driver package in Ubuntu:
Incomplete
Bug description:
fresh install of ubuntu studio and updates but internal speakers do
not play. dell optiplex gx620 love ya
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: alsa-base 1.0.24+dfsg-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Card0.Amixer.info:
Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
Mixer name : 'Analog Devices AD1981B'
Components : 'AC97a:41445374'
Controls : 28
Simple ctrls : 20
Card1.Amixer.info:
Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at
usb-:00:1d.7-4.1.4,'
Mixer name : 'USB Mixer'
Components : 'USB0d8c:0105'
Controls : 13
Simple ctrls : 6
Date: Mon Nov 21 11:51:25 2011
InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386
(20111011.1)
PackageArchitecture: all
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
Symptom_Type: No sound at all
Title: [ICH4 - Intel ICH7, playback] No sound at all
UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
dmi.bios.date: 11/30/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0F8101
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex GX
[Touch-packages] [Bug 1495178] Re: Failed to set wall message, ignoring: Message recipient disconnected from message bus without replying
This was fixed in https://launchpad.net/ubuntu/+source/systemd/225-1ubuntu4 * Fix shutdown with specifying a time. ** Information type changed from Private to Public ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- 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/1495178 Title: Failed to set wall message, ignoring: Message recipient disconnected from message bus without replying Status in systemd package in Ubuntu: Fix Released Bug description: Tried to shutdonw in 3 min got this message. repeatable happened yesterday as well 15.04 ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 12 22:54:23 2015 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2015-01-29 (226 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 10117 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=94709fac-8bfa-41bf-8d29-24abdd9f77cc ro drm.debug=0xe plymouth:debug SegvAnalysis: Segfault happened at: 0x7f1002cbc6fa :movdqu (%rax),%xmm12 PC (0x7f1002cbc6fa) ok source "(%rax)" (0x55907c00) not located in a known VMA region (needed readable region)! destination "%xmm12" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: systemd StacktraceTop: strlen () at ../sysdeps/x86_64/strlen.S:106 __GI___strdup (s=0x55907c00 ) at strdup.c:41 ?? () ?? () ?? () Title: systemd-logind crashed with SIGSEGV in strlen() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/05/2013 dmi.bios.vendor: LENOVO dmi.bios.version: I7KT31AUS dmi.board.vendor: LENOVO dmi.board.version: 31900058 STD dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrI7KT31AUS:bd11/05/2013:svnLENOVO:pn10117:pvrLenovoH535:rvnLENOVO:rn:rvr31900058STD:cvnLENOVO:ct3:cvr: dmi.product.name: 10117 dmi.product.version: Lenovo H535 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1495178/+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
