[Touch-packages] [Bug 1725582] [NEW] System freeze on boot since upgrade to 17.10
Public bug reported: This freeze appears on each boot since the dist upgrade to 17.10 (from 17.04) with the following kernel: linux-image-4.13.0-16-generic. The ssh connexion becomes available after 3 to 5 minutes, and the login screen after more than 20 minutes. This issue doesn't show up in recovery mode. This issue doesn't show up with the previous kernel (from 17.04): linux-image-4.10.0-37-generic. I Also tried the mainline drm-current: linux-image-4.14.0-996-generic_4.14.0-996.201710202201_amd64.deb The issue is not visible then, but I don't have ethernet access any longer (which may be completely unrelated). lsb_release -rd: Description:Ubuntu 17.10 Release:17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Sat Oct 21 08:18:25 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/580] [1002:67df] (rev ef) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Radeon RX 570 [1da2:e366] InstallationDate: Installed on 2017-09-30 (20 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=99791e36-3af2-42ca-8376-ce7138f67d70 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0810 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0810:bd08/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful freeze 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/1725582 Title: System freeze on boot since upgrade to 17.10 Status in xorg package in Ubuntu: New Bug description: This freeze appears on each boot since the dist upgrade to 17.10 (from 17.04) with the following kernel: linux-image-4.13.0-16-generic. The ssh connexion becomes available after 3 to 5 minutes, and the login screen after more than 20 minutes. This issue doesn't show up in recovery mode. This issue doesn't show up with the previous kernel (from 17.04): linux-image-4.10.0-37-generic. I Also tried the mainline drm-current: linux-image-4.14.0-996-generic_4.14.0-996.201710202201_amd64.deb The issue is not visible then, but I don't have ethernet access any longer (which may be completely unrelated). lsb_release -rd: Description: Ubuntu 17.10 Release: 17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Sat Oct 21 08:18:25 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reprodu
[Touch-packages] [Bug 1500193] Re: systemd-journald crashed with SIGABRT in dev_kmsg_record()
** Tags added: artful -- 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/1500193 Title: systemd-journald crashed with SIGABRT in dev_kmsg_record() Status in systemd package in Ubuntu: Confirmed Bug description: I don't know details ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 Date: Sun Sep 27 01:21:55 2015 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2015-09-26 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) Lsusb: Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 064e:c341 Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcCmdline: /lib/systemd/systemd-journald ProcEnviron: LANG=el_GR.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic.efi.signed root=UUID=38873c09-af33-49bc-a9cb-4762d8e857d1 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () __libc_start_main (main=0x55ee81dd0440, argc=1, argv=0x7fff46d4c1f8, init=, fini=, rtld_fini=, stack_end=0x7fff46d4c1e8) at libc-start.c:289 ?? () Title: systemd-journald crashed with SIGABRT in __libc_start_main() UdevLog: Error: [Errno 2] Δεν υπάρχει τέτοιο αρχείο ή κατάλογος: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/16/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.61 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2166 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.42 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.61:bd01/16/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2166:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 098B1140410620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1500193/+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 1500193] Re: systemd-journald crashed with SIGABRT in dev_kmsg_record()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1500193 Title: systemd-journald crashed with SIGABRT in dev_kmsg_record() Status in systemd package in Ubuntu: Confirmed Bug description: I don't know details ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 Date: Sun Sep 27 01:21:55 2015 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2015-09-26 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) Lsusb: Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 064e:c341 Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcCmdline: /lib/systemd/systemd-journald ProcEnviron: LANG=el_GR.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic.efi.signed root=UUID=38873c09-af33-49bc-a9cb-4762d8e857d1 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () __libc_start_main (main=0x55ee81dd0440, argc=1, argv=0x7fff46d4c1f8, init=, fini=, rtld_fini=, stack_end=0x7fff46d4c1e8) at libc-start.c:289 ?? () Title: systemd-journald crashed with SIGABRT in __libc_start_main() UdevLog: Error: [Errno 2] Δεν υπάρχει τέτοιο αρχείο ή κατάλογος: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/16/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.61 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2166 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.42 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.61:bd01/16/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2166:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 098B1140410620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1500193/+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 1725575] Re: systemd-journald crashed with SIGABRT in sd_event_dispatch()
*** This bug is a duplicate of bug 1500193 *** https://bugs.launchpad.net/bugs/1500193 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 #1500193, 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/1725575/+attachment/4981052/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725575/+attachment/4981055/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725575/+attachment/4981063/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725575/+attachment/4981065/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725575/+attachment/4981066/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725575/+attachment/4981067/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725575/+attachment/4981070/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1500193 systemd-journald crashed with SIGABRT in dev_kmsg_record() ** 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1725575 Title: systemd-journald crashed with SIGABRT in sd_event_dispatch() Status in systemd package in Ubuntu: New Bug description: Happened shortly after login to Gnome. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 03:56:16 2017 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2012-12-20 (1765 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 6457BBG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /lib/systemd/systemd-journald ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: ?? () ?? () from /lib/systemd/libsystemd-shared-234.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-234.so sd_event_run () from /lib/systemd/libsystemd-shared-234.so ?? () Title: systemd-journald crashed with SIGABRT in sd_event_dispatch() UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago) UserGroups: dmi.bios.date: 03/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC9WW (2.29 ) dmi.board.name: 6457BBG 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:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn6457BBG:pvrThinkPadT61:rvnLENOVO:rn6457BBG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T61 dmi.product.name: 6457BBG dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725575/+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 1725573] Re: systemd-udevd crashed with SIGABRT in __libc_open64()
*** This bug is a duplicate of bug 1715782 *** https://bugs.launchpad.net/bugs/1715782 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 #1715782, 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/1725573/+attachment/4981024/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725573/+attachment/4981027/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725573/+attachment/4981035/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725573/+attachment/4981037/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725573/+attachment/4981038/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725573/+attachment/4981039/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725573/+attachment/4981040/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1715782 ** 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1725573 Title: systemd-udevd crashed with SIGABRT in __libc_open64() Status in systemd package in Ubuntu: New Bug description: Message is displayed after using unetbootin. Unetbooting shows a blank screen. Happened once in new Ubuntu session, but reporting this bug in Xorg session too. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CustomUdevRuleFiles: 70-snap.core.rules Date: Sat Oct 21 14:05:31 2017 ExecutablePath: /lib/systemd/systemd-udevd InstallationDate: Installed on 2017-07-30 (82 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20384 ProcCmdline: /lib/systemd/systemd-udevd ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=072d29f4-52fa-44c3-a7aa-9a9cecb33fb5 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_open64 (file=0x5650214f44d0 "/dev/sdb", oflag=657408) at ../sysdeps/unix/sysv/linux/open64.c:46 ?? () ?? () ?? () ?? () Title: systemd-udevd crashed with SIGABRT in __libc_open64() UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) UserGroups: dmi.bios.date: 04/18/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9DCN32WW(V3.02) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo B50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo B50-70 dmi.modalias: dmi:bvnLENOVO:bvr9DCN32WW(V3.02):bd04/18/2015:svnLENOVO:pn20384:pvrLenovoB50-70:rvnLENOVO:rnLenovoB50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoB50-70: dmi.product.family: IDEAPAD dmi.product.name: 20384 dmi.product.version: Lenovo B50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725573/+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 1688364] Re: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq
> correction - needed to disable dnsmasq service as network manager > starts it instead. network-manager in 17.04 and later is not expected to start dnsmasq, it integrates with resolved instead. Have you overridden the default network-manager config? Is it possible your issue is related to LP: #1694156? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1688364 Title: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq Status in dnsmasq package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Status in resolvconf package in Ubuntu: New Bug description: May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+so
[Touch-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily
netcfg is also fixed. netcfg (1.142ubuntu4) artful; urgency=medium * Add resolved support. LP: #1714167 -- Dimitri John Ledkov Wed, 20 Sep 2017 09:52:03 +0100 ** Changed in: netcfg (Ubuntu) Status: Confirmed => 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/1712283 Title: Cannot resolve DNS in artful daily Status in casper package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Fix Released Status in netcfg package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. * /etc/resolv.conf is empty file on most images built, which is not right, it should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in image generation? systemd? * Adding a hack, to create /etc/resolv.conf if it does not exist, or is empty. src:systemd * network-manager does not consider that dns is managed by resolved if .53 is present in /etc/resolv.conf or if it points to stub- resolv.conf. src:network-manager * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf. Needs checking / fixing * caster has resolvconf integration * livecd-rootfs has resolvconf integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1725567] [NEW] Can't deactivate repositories using checkbox
Public bug reported: In software-properties I can't deactivate repositories using checkbox. If I try to disable repo, checkbox dimmed and nothing happens. 1) Ubuntu 17.10 2) software-properties-gtk 0.96.24.17 3) Repositories deactivated (checkbox not activated) 4) checkbox dimmed and nothing happens. Checkbox still activated ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 07:49:16 2017 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2017-05-11 (163 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1725567 Title: Can't deactivate repositories using checkbox Status in software-properties package in Ubuntu: New Bug description: In software-properties I can't deactivate repositories using checkbox. If I try to disable repo, checkbox dimmed and nothing happens. 1) Ubuntu 17.10 2) software-properties-gtk 0.96.24.17 3) Repositories deactivated (checkbox not activated) 4) checkbox dimmed and nothing happens. Checkbox still activated ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 07:49:16 2017 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2017-05-11 (163 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1725567/+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 1712283] Re: Cannot resolve DNS in artful daily
network-manager is also fixed: network-manager (1.8.2-1ubuntu6) artful; urgency=medium * src/dns/nm-dns-manager.c: - Fix resolved detection, the symlink target is usually relative to the root, such that in chroots the file points to a file inside the chroot. But keep absolute targets too, as these may have been in use with older version of systemd. - Add support for stub-resolv.conf detection. ** Changed in: network-manager (Ubuntu) Status: Triaged => 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/1712283 Title: Cannot resolve DNS in artful daily Status in casper package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Fix Released Status in netcfg package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. * /etc/resolv.conf is empty file on most images built, which is not right, it should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in image generation? systemd? * Adding a hack, to create /etc/resolv.conf if it does not exist, or is empty. src:systemd * network-manager does not consider that dns is managed by resolved if .53 is present in /etc/resolv.conf or if it points to stub- resolv.conf. src:network-manager * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf. Needs checking / fixing * caster has resolvconf integration * livecd-rootfs has resolvconf integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1712283] Re: Cannot resolve DNS in artful daily
livecd-rootfs fixed in version 2.468: livecd-rootfs (2.468) artful; urgency=medium [ Dimitri John Ledkov ] * Drop obsolete fix-ups of resolv.conf, debootstrap should now result in correct symlink to resolved without any further fixes. [ Michael Hudson-Doyle ] * Have subiquity.service order after on a service defined by the subiquity snap, which in turn will order after the job that mounts the subiquity snap. (LP: #1721414) ** Changed in: livecd-rootfs (Ubuntu) Status: Confirmed => 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/1712283 Title: Cannot resolve DNS in artful daily Status in casper package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Fix Released Status in netcfg package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. * /etc/resolv.conf is empty file on most images built, which is not right, it should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in image generation? systemd? * Adding a hack, to create /etc/resolv.conf if it does not exist, or is empty. src:systemd * network-manager does not consider that dns is managed by resolved if .53 is present in /etc/resolv.conf or if it points to stub- resolv.conf. src:network-manager * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf. Needs checking / fixing * caster has resolvconf integration * livecd-rootfs has resolvconf integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1725333] Re: do-release-upgrade broke WSL
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bash (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1725333 Title: do-release-upgrade broke WSL Status in bash package in Ubuntu: Confirmed Bug description: I had Ubuntu 17.04 installed in WSL and decided to upgrade it to 17.10, so I had run do-release-upgrade, as I did before to upgrade to 17.04. Everything was fine before script started upgrading packages. It's started from bash updating, and somehow there is a problem revealed that locale files is missing, and locale-gen can't be run (because of bug in WSL). I've tried to install language-pack-en as was suggested, but problem haven't resolved, any attempt to update leads to this error. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: bash 4.4-2ubuntu1.1 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Fri Oct 20 18:03:30 2017 Dmesg: DpkgTerminalLog: Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ... preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. dpkg: error processing archive /var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack): subprocess new pre-installation script was killed by signal (Aborted), core dumped DuplicateSignature: package:bash:4.4-2ubuntu1.1 Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ... preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. dpkg: error processing archive /var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack): subprocess new pre-installation script was killed by signal (Aborted), core dumped ErrorMessage: subprocess new pre-installation script was killed by signal (Aborted), core dumped RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: bash Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new pre-installation script was killed by signal (Aborted), core dumped UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1725333/+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 1712283] Re: Cannot resolve DNS in artful daily
So how was /etc/resolv.conf configured before you removed it? To my understanding, there should be no problems after upgrade from any of the default configurations in 17.04. -- 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/1712283 Title: Cannot resolve DNS in artful daily Status in casper package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Confirmed Status in netcfg package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. * /etc/resolv.conf is empty file on most images built, which is not right, it should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in image generation? systemd? * Adding a hack, to create /etc/resolv.conf if it does not exist, or is empty. src:systemd * network-manager does not consider that dns is managed by resolved if .53 is present in /etc/resolv.conf or if it points to stub- resolv.conf. src:network-manager * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf. Needs checking / fixing * caster has resolvconf integration * livecd-rootfs has resolvconf integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1684506] Re: QT4 Trolltech.conf settings lost after reboot
Yes, in Artful all is ok. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1684506 Title: QT4 Trolltech.conf settings lost after reboot Status in qt4-x11 package in Ubuntu: Confirmed Bug description: Since the update to Kubuntu 17.04 / plasma 5.9.4 all qt4 based applications (e.g. KeePassX) render using wrong font instead of my personal configured font. When I run qtconfig-qt4 (4.8.7), change font and click 'save', a fresh .config/Trolltech.conf is saved, contains the correct font config and all qt4 applications now show correct font. These settings however do not survive a reboot although Trolltech.conf exists and contains correct settings. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 Uname: Linux 4.10.11 x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 20 10:33:21 2017 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to zesty on 2017-04-11 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1684506/+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 1721821] Re: Kubuntu 17.10 freezes 50 seconds before KDE Plasma starts
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1721821 Title: Kubuntu 17.10 freezes 50 seconds before KDE Plasma starts Status in network-manager package in Ubuntu: Confirmed Bug description: I upgraded my Kubuntu 17.04 to 17.10 four days ago. My PC is booting fast: ~10 seconds to see the greeter. But when I connect to my Plasma session, the greeter is staying ~50 seconds at screen, before Plasma is starting (in ~10 more seconds). There was no problem before upgrading to Kubuntu 17.10. I connected to a terminal session just after having entered my password in the greeter, and I launched the htop command: all I can say is that there is no cpu eating process. The cpu is nearly idle during these 50 seconds. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: sddm 0.14.0-4ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu2 Architecture: i386 CurrentDesktop: KDE Date: Fri Oct 6 18:13:42 2017 InstallationDate: Installed on 2012-07-31 (1893 days ago) InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) SourcePackage: sddm 0.14.0-4ubuntu1 UpgradeStatus: Upgraded to artful on 2017-10-02 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1721821/+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 1717839] Re: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1717839 Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 Status in systemd package in Ubuntu: Confirmed Bug description: Not able to upgrade ProblemType: Package DistroRelease: Ubuntu 17.04 Package: systemd-sysv 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic i686 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: i386 Date: Sun Sep 17 19:49:21 2017 ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationDate: Installed on 2017-09-16 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: systemd Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 UpgradeStatus: Upgraded to zesty on 2017-09-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1717839/+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 1720684] Re: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile
** Changed in: pulseaudio Status: Confirmed => Fix Released -- 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/1720684 Title: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Confirmed Bug description: Kubuntu 17.04 Bluetooth device: https://smile.amazon.com/VicTsing-Wireless-Waterproof-Hands-Free-Speakerphone/dp/B074DX13T1 (itentifies itself as "C6") The above Bluetooth speaker paired and started streaming audio perfectly in Kubuntu 17.04. But the audio quality was poor, because the default audio profile was the low-quality HSP/HFP one. When I switched it to the A2DP profile, it sounded perfect again. Can we make A2DP the default playback profile for Bluetooth audio devices? To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720684/+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 1725558] Re: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
*** This bug is a duplicate of bug 1717839 *** https://bugs.launchpad.net/bugs/1717839 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 #1717839, 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. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1717839 package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 -- 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/1725558 Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: na ProblemType: Package DistroRelease: Ubuntu 17.04 Package: systemd-sysv 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic i686 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: i386 Date: Fri Oct 20 22:00:08 2017 ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: systemd Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725558/+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 1725558] [NEW] package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
*** This bug is a duplicate of bug 1717839 *** https://bugs.launchpad.net/bugs/1717839 Public bug reported: na ProblemType: Package DistroRelease: Ubuntu 17.04 Package: systemd-sysv 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic i686 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: i386 Date: Fri Oct 20 22:00:08 2017 ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: systemd Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 third-party-packages zesty -- 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/1725558 Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: na ProblemType: Package DistroRelease: Ubuntu 17.04 Package: systemd-sysv 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic i686 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: i386 Date: Fri Oct 20 22:00:08 2017 ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: systemd Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725558/+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 1712283] Re: Cannot resolve DNS in artful daily
I just upgraded from 17.04 to release version of 17.10, then I encounter this problem, too. comment #6's method fixed this issue for me. -- 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/1712283 Title: Cannot resolve DNS in artful daily Status in casper package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Confirmed Status in netcfg package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. * /etc/resolv.conf is empty file on most images built, which is not right, it should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in image generation? systemd? * Adding a hack, to create /etc/resolv.conf if it does not exist, or is empty. src:systemd * network-manager does not consider that dns is managed by resolved if .53 is present in /etc/resolv.conf or if it points to stub- resolv.conf. src:network-manager * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf. Needs checking / fixing * caster has resolvconf integration * livecd-rootfs has resolvconf integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1725169] Re: Black Screen after Upgrade from Kubuntu 17.04 to 17.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1725169 Title: Black Screen after Upgrade from Kubuntu 17.04 to 17.10 Status in xorg package in Ubuntu: Confirmed Bug description: I just upgraded Kubuntu from 17.04 to 17.10 on two machines with the same Result: After reboot, the first kernel in grub was 'linux-image-4.13.0-16-lowlatency'. This kernel does not work with the nvidia-grafic-card and lead to a black screen. After purging this kernel in a tty-session it booted up smothely. I think this can help many others. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Oct 20 09:57:26 2017 DistUpgraded: 2017-10-20 08:57:01,633 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: kubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GM107 [GeForce GTX 750 Ti] [1458:362d] InstallationDate: Installed on 2016-12-23 (300 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 062a:4102 Creative Labs Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z170X-Gaming 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=99e6e2ce-07c5-4553-be22-2ccd3c3a73cc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) dmi.bios.date: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22d dmi.board.asset.tag: Default string dmi.board.name: Z170X-Gaming 3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22d:bd06/30/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170X-Gaming 3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1725169/+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 1725169] Re: Black Screen after Upgrade from Kubuntu 17.04 to 17.10
Same problem here - booting kubuntu 17.10 using the new, default 'lowlatency' kernel led to a black screen. Manually selecting the 'generic' kernel via the advanced options in grub worked fine. I've got an nvidia 780 card. -- 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/1725169 Title: Black Screen after Upgrade from Kubuntu 17.04 to 17.10 Status in xorg package in Ubuntu: Confirmed Bug description: I just upgraded Kubuntu from 17.04 to 17.10 on two machines with the same Result: After reboot, the first kernel in grub was 'linux-image-4.13.0-16-lowlatency'. This kernel does not work with the nvidia-grafic-card and lead to a black screen. After purging this kernel in a tty-session it booted up smothely. I think this can help many others. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Oct 20 09:57:26 2017 DistUpgraded: 2017-10-20 08:57:01,633 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: kubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GM107 [GeForce GTX 750 Ti] [1458:362d] InstallationDate: Installed on 2016-12-23 (300 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 062a:4102 Creative Labs Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z170X-Gaming 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=99e6e2ce-07c5-4553-be22-2ccd3c3a73cc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) dmi.bios.date: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22d dmi.board.asset.tag: Default string dmi.board.name: Z170X-Gaming 3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22d:bd06/30/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170X-Gaming 3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1725169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.
[Touch-packages] [Bug 1723198] Re: package ca-certificates 20170717~16.04.1 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ca-certificates (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1723198 Title: package ca-certificates 20170717~16.04.1 failed to install/upgrade: triggers looping, abandoned Status in ca-certificates package in Ubuntu: Confirmed Bug description: I have no further information to give at this time except to say that there were several errors during the upgrade process from 14.04. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ca-certificates 20170717~16.04.1 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Thu Oct 12 17:52:19 2017 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2013-11-16 (1425 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: ca-certificates Title: package ca-certificates 20170717~16.04.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2017-10-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1723198/+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 1724307] Re: Mouse cursor flickers when using external DisplayLink monitor
Hi all, I have the exact same issue on my primary monitor. Alienware Alpha R2 Primary monitor connected to Nvidia GTX 960 Secondary monitor connected to Startech USB32HD4K (Displaylink Driver) Ubuntu 16.04.3 LTS One interesting thing I noticed is that if you set rotation in "All Settings"->"Screen Display" to "Clockwise", "Anti-clockwise" or "180 degrees" (just not "Normal"), this issue disappeared. This my workaround currently. Dont know if this helps. Cheers -- 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/1724307 Title: Mouse cursor flickers when using external DisplayLink monitor Status in xorg package in Ubuntu: Triaged Bug description: When I connect my laptop to my DisplayLink based device with USB (Wavlink universal USB 3.0 docking station https://www.wavlink.com/en/product/150 WL-UG39DK1V), and connect the Wavlink to my AOC E2775SJ Monitor via HDMI, the mouse icon flickers. Only if the mouse is on the laptop monitor, it can vanish for several minutes, but remains active. Animations/overlays or typing inside a Chrome window causes the mouse pointer to flicker more often. If there is no interaction or animation, the mouse pointer remains static and drawn. Monitor 1: 1920 x 1080 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor This issue doesn't happen if I don't connect my laptop to an external monitor via the Wavlink device. This issue is reproducible with DisplayLink driver 1.4, and 1.3.54. This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Oct 17 10:01:55 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:082a] InstallationDate: Installed on 2017-10-16 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.2.1 dmi.board.name: 05FPM2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 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: Tue Oct 17 09:39:15 2017 xserver.configfile: default xserver.errors: modeset(G0): glamor initialization failed xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5193 vendor SHP xserver.version: 2:1.19.3-1ubuntu1~16.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724307/+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 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Description changed: - This seems to be the same problem as described in bug #1636262, only - this time it happened during upgrade from 16.10 to 17.04. The setup - process (do-release-upgrade -d) aborted and I had to finish it manually. + [Impact] + Upgrading cracklib-runtime is not working for some systems due to trigger cycles. This is making distribution upgrades challenging. - ProblemType: Package - DistroRelease: Ubuntu 17.04 + [Test Case] + While we haven't been able to replicate this directly the following tests will confirm that there are no regressions. + + Test A + -- + 1) Install cracklib-runtime from -proposed. + 2) Reinstall dictionaires-common and verify that the trigger is called + + Test B + -- + 1) With the version of cracklib-runtime from -proposed installed confirm that a distribution upgrade to next supported release succeeds. + + Test C + -- + 1) Test a release upgrade from an affected release (Trusty, Xenial) to the next supported release (Xenial, Zesty) with -proposed enabled. To do this upgrade you'll need to edit /etc/apt/sources.list to the target release and run 'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed. + + [Regression Potential] + It's possible that upgrades will break hence all the regression tests in the Test Case. + + Original Description + + This seems to be the same problem as described in bug #1636262, only this time it happened during upgrade from 16.10 to 17.04. The setup process (do-release-upgrade -d) aborted and I had to finish it manually. + + ProblemType: PackageDistroRelease: Ubuntu 17.04 Package: cracklib-runtime 2.9.2-3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sun Apr 9 17:09:37 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-07-26 (257 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: - dpkg 1.18.10ubuntu1 - apt 1.4 - SourcePackage: cracklib2 + dpkg 1.18.10ubuntu1 + apt 1.4SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago) -- 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/1681231 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Confirmed Status in cracklib2 package in Ubuntu: Fix Released Status in cracklib2 source package in Trusty: Incomplete Status in cracklib2 source package in Xenial: Triaged Status in cracklib2 source package in Yakkety: Won't Fix Status in cracklib2 source package in Zesty: Triaged Status in cracklib2 package in Debian: Fix Released Bug description: [Impact] Upgrading cracklib-runtime is not working for some systems due to trigger cycles. This is making distribution upgrades challenging. [Test Case] While we haven't been able to replicate this directly the following tests will confirm that there are no regressions. Test A -- 1) Install cracklib-runtime from -proposed. 2) Reinstall dictionaires-common and verify that the trigger is called Test B -- 1) With the version of cracklib-runtime from -proposed installed confirm that a distribution upgrade to next supported release succeeds. Test C -- 1) Test a release upgrade from an affected release (Trusty, Xenial) to the next supported release (Xenial, Zesty) with -proposed enabled. To do this upgrade you'll need to edit /etc/apt/sources.list to the target release and run 'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed. [Regression Potential] It's possible that upgrades will break hence all the regression tests in the Test Case. Original Description This seems to be the same problem as described in bug #1636262, only this time it happened during upgrade from 16.10 to 17.04. The setup process (do-release-upgrade -d) aborted and I had to finish it manually. ProblemType: PackageDistroRelease: Ubuntu 17.04 Package: cracklib-runtime 2.9.2-3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sun Apr 9 17:09:37 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-07-26 (257 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4SourcePackage: cracklib2 Title: package cracklib-runtim
[Touch-packages] [Bug 1725385] Re: one
** Information type changed from Private Security to Public -- 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/1725385 Title: one Status in xorg package in Ubuntu: New Bug description: no further information ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic i686 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Oct 20 18:21:34 2017 DistUpgraded: 2017-10-13 20:50:46,659 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.4.0-31-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-97-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-98-generic, i686: installed ndiswrapper, 1.60, 4.4.0-97-generic, i686: installed ndiswrapper, 1.60, 4.4.0-98-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 3450/3470] [1002:95c4] (prog-if 00 [VGA controller]) Subsystem: Dell RV620/M82 [Mobility Radeon HD 3450/3470] [1028:0254] InstallationDate: Installed on 2017-10-13 (7 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803) MachineType: Dell Inc. Studio 1535 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic root=UUID=18271d74-75ec-4847-a14e-5541b0a44390 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-10-13 (6 days ago) XorgLogOld: dmi.bios.date: 07/02/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0F700C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd07/02/2008:svnDellInc.:pnStudio1535:pvr:rvnDellInc.:rn0F700C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Studio 1535 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1725385/+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 1725513] Re: HP hs3110 WWAN adapter not recognized
PS: Debian apparently added the udev rules in usb-modeswitch-data, version 20160803-1; see https://launchpad.net/debian/+source/usb- modeswitch-data/+changelog. -- 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/1725513 Title: HP hs3110 WWAN adapter not recognized Status in network-manager package in Ubuntu: New Bug description: The HP hs3110 WWAN adapter is not recognized and does not work out of the box. The device is a rebranded Huawei MU736 but reports a different VID/PID pair (03f0:521d). With a few manual steps the device will work. Add the following two udev rules: # HP hs3110 (Huawei MU736) ATTR{idVendor}=="03f0", ATTR{idProduct}=="521d", RUN+="usb_modeswitch '%b/%k'" ATTR{idVendor}=="03f0", ATTR{idProduct}=="521d", RUN+="/bin/bash -c 'modprobe option && echo 03f0 521d > /sys/bus/usb-serial/drivers/option1/new_id'" After that, a PIN prompt appears on boot, the device appears in Network Manager and can be configured. Before a conection can be established, the following AT commands need to be sent to /dev/ttyUSB2: ATZ ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 AT+CGDCONT=1,"IP" (I’ve successfully automated this using wvdial and running it once manually before establishing a 3G connection.) After that, a 3G connection can be established. Would be great if this were supported out of the box, especially if sending the AT commands could be automated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Sat Oct 21 02:15:58 2017 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-09 (1045 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-01-24T03:17:24.095174 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1725513/+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 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Changed in: cracklib2 (Ubuntu Zesty) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: cracklib2 (Ubuntu Xenial) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: cracklib2 (Ubuntu) Status: Triaged => Fix Released ** Changed in: cracklib2 (Ubuntu Xenial) Status: Incomplete => Triaged -- 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/1681231 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Confirmed Status in cracklib2 package in Ubuntu: Fix Released Status in cracklib2 source package in Trusty: Incomplete Status in cracklib2 source package in Xenial: Triaged Status in cracklib2 source package in Yakkety: Won't Fix Status in cracklib2 source package in Zesty: Triaged Status in cracklib2 package in Debian: Fix Released Bug description: This seems to be the same problem as described in bug #1636262, only this time it happened during upgrade from 16.10 to 17.04. The setup process (do-release-upgrade -d) aborted and I had to finish it manually. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: cracklib-runtime 2.9.2-3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sun Apr 9 17:09:37 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-07-26 (257 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1681231/+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 1725513] [NEW] HP hs3110 WWAN adapter not recognized
Public bug reported: The HP hs3110 WWAN adapter is not recognized and does not work out of the box. The device is a rebranded Huawei MU736 but reports a different VID/PID pair (03f0:521d). With a few manual steps the device will work. Add the following two udev rules: # HP hs3110 (Huawei MU736) ATTR{idVendor}=="03f0", ATTR{idProduct}=="521d", RUN+="usb_modeswitch '%b/%k'" ATTR{idVendor}=="03f0", ATTR{idProduct}=="521d", RUN+="/bin/bash -c 'modprobe option && echo 03f0 521d > /sys/bus/usb-serial/drivers/option1/new_id'" After that, a PIN prompt appears on boot, the device appears in Network Manager and can be configured. Before a conection can be established, the following AT commands need to be sent to /dev/ttyUSB2: ATZ ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 AT+CGDCONT=1,"IP" (I’ve successfully automated this using wvdial and running it once manually before establishing a 3G connection.) After that, a 3G connection can be established. Would be great if this were supported out of the box, especially if sending the AT commands could be automated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Sat Oct 21 02:15:58 2017 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-09 (1045 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-01-24T03:17:24.095174 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1725513 Title: HP hs3110 WWAN adapter not recognized Status in network-manager package in Ubuntu: New Bug description: The HP hs3110 WWAN adapter is not recognized and does not work out of the box. The device is a rebranded Huawei MU736 but reports a different VID/PID pair (03f0:521d). With a few manual steps the device will work. Add the following two udev rules: # HP hs3110 (Huawei MU736) ATTR{idVendor}=="03f0", ATTR{idProduct}=="521d", RUN+="usb_modeswitch '%b/%k'" ATTR{idVendor}=="03f0", ATTR{idProduct}=="521d", RUN+="/bin/bash -c 'modprobe option && echo 03f0 521d > /sys/bus/usb-serial/drivers/option1/new_id'" After that, a PIN prompt appears on boot, the device appears in Network Manager and can be configured. Before a conection can be established, the following AT commands need to be sent to /dev/ttyUSB2: ATZ ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 AT+CGDCONT=1,"IP" (I’ve successfully automated this using wvdial and running it once manually before establishing a 3G connection.) After that, a 3G connection can be established. Would be great if this were supported out of the box, especially if sending the AT commands could be automated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: MATE Date: Sat Oct 21 02:15:58 2017 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-09 (1045 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-01-24T03:17:24.095174 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1725513/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchp
[Touch-packages] [Bug 1718869] Re: Migrate to hunspell-en-us in libreoffice-dictionaries
** Also affects: scowl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hunspell-en-us in Ubuntu. https://bugs.launchpad.net/bugs/1718869 Title: Migrate to hunspell-en-us in libreoffice-dictionaries Status in hunspell-en-us package in Ubuntu: New Status in libreoffice-dictionaries package in Ubuntu: New Status in scowl package in Ubuntu: New Status in hunspell-en-us package in Debian: Fix Released Status in libreoffice-dictionaries package in Debian: Won't Fix Bug description: libreoffice-dictionaries upstream ships hunspell-en-us, which is properly maintained and is newer than the one currently in Debian and Ubuntu (20070829-6ubuntu3). Please consider migrating to the one in libreoffice-dictionaries. The other English variants (British, Australian and others) are already provided by libreoffice- dictionaries and are more up-to-date than the US variant. Debian bugs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874519 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795159 Inside the source of libreoffice-dictionaries in Debian, I can find en_US.aff and en_US.dic but there is not a built package for them. https://sources.debian.net/src/libreoffice-dictionaries/1:5.2.5-1/dictionaries/en/ See this README from the Libreoffice/dictionaries git, https://cgit.freedesktop.org/libreoffice/dictionaries/tree/en/README_en_US.txt It seems that this is now dead, https://sourceforge.net/projects/hunspell/files/Spelling%20dictionaries/en_US/ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hunspell-en-us 20070829-6ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 09:43:32 2017 InstallationDate: Installed on 2017-09-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) PackageArchitecture: all SourcePackage: hunspell-en-us UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hunspell-en-us/+bug/1718869/+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 1725227] Re: mission-control-5 crashed with signal 5 in g_object_new_valist()
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-mission- control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1725227 Title: mission-control-5 crashed with signal 5 in g_object_new_valist() Status in telepathy-mission-control-5 package in Ubuntu: New Bug description: fter upgrade from 16.04 to 17.10 ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: telepathy-mission-control-5 1:5.16.4-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 20 02:03:43 2017 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationDate: Installed on 2017-10-16 (3 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) KernLog: ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=9bb2a796-4147-45c9-8e2b-460f44857d45 ro quiet splash vt.handoff=7 Signal: 5 SourcePackage: telepathy-mission-control-5 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: mission-control-5 crashed with signal 5 in g_object_new_valist() UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1725227/+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 1050569] Re: Cannot file an ubiquity bug using apport after performing offline installation
I tested this with an Ubuntu 17.10 install with no-network and the results were the same. ** Tags added: artful -- 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/1050569 Title: Cannot file an ubiquity bug using apport after performing offline installation Status in apport package in Ubuntu: Triaged Status in ubiquity package in Ubuntu: Won't Fix Bug description: After performing an offline installation, I am unable to run apport via ubuntu-bug to file a bug against ubiquity until I first run an apt-get update to update the archive. When an installation is offline, it seems like this list is missing. Apport gives the following error: dpkg-query: no packages found matching ubiquity After running the update, everything went fine, and obviously, network access is required to file a bug. However, this interaction is confusing, and if possible should be fixed. Could ubiquity generate the list during an offline install? Could apport run an update if it doesn't find the package in the current list before giving the error? This might just be a 'won't fix'. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Thu Sep 13 15:07:51 2012 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120913.3) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1050569/+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 1725505] [NEW] Connection is continued to be attempted after answering no
Public bug reported: $ ssh -p git.surgut.co.uk Warning: the ECDSA host key for 'git.surgut.co.uk' differs from the key for the IP address '51.15.93.191' Offending key for IP in /home/xnox/.ssh/known_hosts:371 Matching host key in /home/xnox/.ssh/known_hosts:329 Are you sure you want to continue connecting (yes/no)? no The authenticity of host '[git.surgut.co.uk]: ([51.15.93.191]:)' can't be established. ECDSA key fingerprint is SHA256:5NH82FK/oUVqMrJo7trygYhKb8PjOamfwJrZ+miTAFg. Are you sure you want to continue connecting (yes/no)? no Host key verification failed. I was expecting for the client to exit after answering "no" to the first question. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1725505 Title: Connection is continued to be attempted after answering no Status in openssh package in Ubuntu: New Bug description: $ ssh -p git.surgut.co.uk Warning: the ECDSA host key for 'git.surgut.co.uk' differs from the key for the IP address '51.15.93.191' Offending key for IP in /home/xnox/.ssh/known_hosts:371 Matching host key in /home/xnox/.ssh/known_hosts:329 Are you sure you want to continue connecting (yes/no)? no The authenticity of host '[git.surgut.co.uk]: ([51.15.93.191]:)' can't be established. ECDSA key fingerprint is SHA256:5NH82FK/oUVqMrJo7trygYhKb8PjOamfwJrZ+miTAFg. Are you sure you want to continue connecting (yes/no)? no Host key verification failed. I was expecting for the client to exit after answering "no" to the first question. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1725505/+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 1718869] Re: Migrate to hunspell-en-us in libreoffice-dictionaries
** Changed in: hunspell-en-us (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hunspell-en-us in Ubuntu. https://bugs.launchpad.net/bugs/1718869 Title: Migrate to hunspell-en-us in libreoffice-dictionaries Status in hunspell-en-us package in Ubuntu: New Status in libreoffice-dictionaries package in Ubuntu: New Status in hunspell-en-us package in Debian: Fix Released Status in libreoffice-dictionaries package in Debian: Won't Fix Bug description: libreoffice-dictionaries upstream ships hunspell-en-us, which is properly maintained and is newer than the one currently in Debian and Ubuntu (20070829-6ubuntu3). Please consider migrating to the one in libreoffice-dictionaries. The other English variants (British, Australian and others) are already provided by libreoffice- dictionaries and are more up-to-date than the US variant. Debian bugs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874519 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795159 Inside the source of libreoffice-dictionaries in Debian, I can find en_US.aff and en_US.dic but there is not a built package for them. https://sources.debian.net/src/libreoffice-dictionaries/1:5.2.5-1/dictionaries/en/ See this README from the Libreoffice/dictionaries git, https://cgit.freedesktop.org/libreoffice/dictionaries/tree/en/README_en_US.txt It seems that this is now dead, https://sourceforge.net/projects/hunspell/files/Spelling%20dictionaries/en_US/ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hunspell-en-us 20070829-6ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 09:43:32 2017 InstallationDate: Installed on 2017-09-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) PackageArchitecture: all SourcePackage: hunspell-en-us UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hunspell-en-us/+bug/1718869/+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 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen. Additionally, if I wait a very long time the screen does not lock either. Switching from LightDM to GDM3 fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 6 09:17:35 2017 DisplayManager: lightdm InstallationDate: Installed on 2016-01-22 (592 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+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 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen. Additionally, if I wait a very long time the screen does not lock either. Switching from LightDM to GDM3 fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 6 09:17:35 2017 DisplayManager: lightdm InstallationDate: Installed on 2016-01-22 (592 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+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 1613729] Re: NetworkManager autoconnects to wired profiles in reverse order
I'm no longer working there so it's not very important to me anymore. I suppose if somebody still needed this fix they would have made a comment here by now... With 18.04 around the corner I imagine desktop usage of 14.04 isn't very applicable anymore. -- 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/1613729 Title: NetworkManager autoconnects to wired profiles in reverse order Status in network-manager package in Ubuntu: Invalid Status in network-manager source package in Trusty: New Bug description: When I select a wired profile manually and reboot, NetworkManager instead connects to the profile that has the oldest timestamp. So it's not connecting to the last used profile, which is troublesome. On all of our machines (about 500), we define three wired network profiles, one DHCP and two static. We're migrating from Debian to Ubuntu, so this bug has only surfaced now for us. This can be reproduced by creating a couple of network profiles on the same wired interface and then rebooting or restarting network-manager. It will loop through the network profiles in the same order always. So it's doing the exact reverse of what's supposed to happen. I did some digging and I applied a simple patch to the source code. This seems to have fixed the issue. I posted my patch for verification on the networkmanager mailing list and it was verified as being correct by Beniamino Galvani, one of the developers. Here is the link to the network-manager topic: https://mail.gnome.org/archives/networkmanager- list/2016-August/msg00053.html This is the patch (also included as attachment): --- nm-device.c 2016-08-16 15:37:50.0 +0200 +++ nm-device_patched.c 2016-08-16 15:44:08.308729955 +0200 @@ -1267,7 +1267,7 @@ s_con = nm_connection_get_setting_connection (connection); g_assert (s_con); if (nm_setting_connection_get_autoconnect (s_con)) - available_conns = g_slist_prepend (available_conns, connection); + available_conns = g_slist_append (available_conns, connection); } if (!available_conns) I hope to get this patch included in the trusty package, so somebody else can benefit from this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.3 ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CRDA: Error: [Errno 2] Bestand of map bestaat niet: 'iw' CurrentDesktop: Unity Date: Tue Aug 16 15:23:17 2016 IfupdownConfig: auto lo iface lo inet loopback IpRoute: default via 10.30.6.1 dev em1 proto static 10.30.6.0/24 dev em1 proto kernel scope link src 10.30.6.204 metric 1 10.40.8.0/21 dev tun0 proto kernel scope link src 10.40.8.31 IwConfig: tun0 no wireless extensions. em1 no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=nl_BE: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_BE SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH DHCP 702624f9-f052-473a-b131-acd2045e6ec2 802-3-ethernet1471353746 di 16 aug 2016 15:22:26 CEST yes no /org/freedesktop/NetworkManager/Settings/1 Proximus 7a9a5bc2-d51a-46b4-b721-050a607951bc 802-3-ethernet1471353744 di 16 aug 2016 15:22:24 CEST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH em1802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1613729/+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 1218701] Re: software-properties-gtk crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.Spawn.PermissionsInvalid: The permission of the set
** Tags added: artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1218701 Title: software-properties-gtk crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.Spawn.PermissionsInvalid: The permission of the setuid helper is not correct Status in software-properties package in Ubuntu: Confirmed Bug description: After applying recent updates to Saucy I get this error ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: software-properties-gtk 0.92.25 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Thu Aug 29 22:33:48 2013 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2012-11-02 (300 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 PythonArgs: ['/usr/bin/software-properties-gtk'] SourcePackage: software-properties Title: software-properties-gtk crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.Spawn.PermissionsInvalid: The permission of the setuid helper is not correct UpgradeStatus: Upgraded to saucy on 2013-08-14 (15 days ago) UserGroups: adm backup cdrom dialout dip disk kismet kvm libvirtd lpadmin netdev plugdev sambashare sudo tty video www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1218701/+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 1725484] Re: software-properties-gtk crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknow
*** This bug is a duplicate of bug 1218701 *** https://bugs.launchpad.net/bugs/1218701 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 #1218701, 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. ** Tags removed: need-duplicate-check ** Changed in: software-properties (Ubuntu) Importance: Undecided => Medium ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725484/+attachment/4980293/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725484/+attachment/4980294/+files/ProcStatus.txt ** This bug has been marked a duplicate of bug 1218701 software-properties-gtk crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.Spawn.PermissionsInvalid: The permission of the setuid helper is not correct ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1725484 Title: software-properties-gtk crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1 Status in software-properties package in Ubuntu: New Bug description: Description: Ubuntu 17.10 Release: 17.10 Installed: 0.96.24.17 Versions: *** 0.96.24.17 500 500 http://ru.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: MATE Date: Sat Oct 21 00:00:58 2017 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2017-10-17 (3 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 (20170926) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=4 ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=ru LANG=ru_RU.UTF-8 Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=4'] PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SourcePackage: software-properties Title: software-properties-gtk crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1725484/+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 1164016] Re: restore type-ahead find
I can confirm there's an issue again on Ubuntu 17.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1712921] Re: enabling networkd appears to eat up entropy
There's a bit of netplan in that too. ** Also affects: nplan (Ubuntu) Importance: Undecided Status: New ** Changed in: nplan (Ubuntu Artful) Status: New => In Progress ** Changed in: nplan (Ubuntu Artful) Importance: Undecided => Critical ** Changed in: nplan (Ubuntu Artful) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1712921 Title: enabling networkd appears to eat up entropy Status in nplan package in Ubuntu: In Progress Status in openssh package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Triaged Status in nplan source package in Artful: In Progress Status in openssh source package in Artful: Fix Released Status in systemd source package in Artful: Triaged Bug description: enabling networkd appears to eat up entropy as seen in openssh autopkgtest failing, when networkd is enabled by default. See http://autopkgtest.ubuntu.com/packages/openssh/artful/amd64 with triggers systemd/234-2ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1712921/+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 1697146] Re: Unable to use apport to report any bugs prior to the first software update
I just installed the final release of Artful, without choosing to install updates from the network, and /var/lib/apt/lists is full and I am able to use 'ubuntu-bug apport' without having to run a software update. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Invalid ** Changed in: apport (Ubuntu) Status: Confirmed => Fix Released -- 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/1697146 Title: Unable to use apport to report any bugs prior to the first software update Status in apport package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Bug description: Running `ubuntu-bug gnome-shell` from within an installed artful system claims that it is not an official ubuntu package. Running it from the live CD session works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1697146/+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 1725479] [NEW] systemd-udevd crashes writing ISO with usb-creator-gtk
Public bug reported: At the end of the writing process, systemd-udevd crashes, i see this in dmesg: [ 1934.273458] INFO: task systemd-udevd:298 blocked for more than 120 seconds. [ 1934.273462] Tainted: G OE 4.10.0-37-generic #41~16.04.1-Ubuntu [ 1934.273464] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1934.273466] systemd-udevd D0 298 1 0x0004 [ 1934.273468] Call Trace: [ 1934.273474] __schedule+0x232/0x700 [ 1934.273475] schedule+0x36/0x80 [ 1934.273477] schedule_preempt_disabled+0xe/0x10 [ 1934.273478] __mutex_lock_slowpath+0x193/0x290 [ 1934.273480] mutex_lock+0x2f/0x40 [ 1934.273482] __blkdev_get+0x6f/0x400 [ 1934.273483] blkdev_get+0x129/0x330 [ 1934.273485] blkdev_open+0x82/0xd0 [ 1934.273487] do_dentry_open+0x208/0x310 [ 1934.273488] ? blkdev_get_by_dev+0x50/0x50 [ 1934.273489] vfs_open+0x4c/0x70 [ 1934.273491] ? may_open+0x9b/0x100 [ 1934.273492] path_openat+0x2ac/0x1430 [ 1934.273494] do_filp_open+0x91/0x100 [ 1934.273496] ? __alloc_fd+0x46/0x170 [ 1934.273498] do_sys_open+0x12d/0x280 [ 1934.273500] SyS_open+0x1e/0x20 [ 1934.273502] entry_SYSCALL_64_fastpath+0x1e/0xad [ 1934.273503] RIP: 0033:0x7f915b83bc60 [ 1934.273504] RSP: 002b:7ffccbefa178 EFLAGS: 0246 ORIG_RAX: 0002 [ 1934.273505] RAX: ffda RBX: 55baf1f7e760 RCX: 7f915b83bc60 [ 1934.273506] RDX: 55baf1422592 RSI: 000a0800 RDI: 55baf1f6dcc0 [ 1934.273507] RBP: R08: 0073 R09: 0003 [ 1934.273507] R10: R11: 0246 R12: [ 1934.273508] R13: 55baf1f7e760 R14: 7ffccbefa0f0 R15: ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu19 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 20 22:46:10 2017 InstallationDate: Installed on 2016-02-21 (606 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic root=UUID=9ada941b-b897-4db2-94f4-db4646410ed0 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-06-28 (479 days ago) dmi.bios.date: 09/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2105 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A78T-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2105:bd09/11/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78T-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "crash log found in /var/crash/_lib_systemd_systemd-udevd.0.crash" https://bugs.launchpad.net/bugs/1725479/+attachment/4980243/+files/crash.txt -- 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/1725479 Title: systemd-udevd crashes writing ISO with usb-creator-gtk Status in systemd package in Ubuntu: New Bug description: At the end of the writing process, systemd-udevd crashes, i see this in dmesg: [ 1934.273458] INFO: task systemd-udevd:298 blocked for more than 120 seconds. [ 1934.273462] Tainted: G OE 4.10.0-37-generic #41~16.04.1-Ubuntu [ 1934.273464] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1934.273466] systemd-udevd D0 298 1 0x0004 [ 1934.273468] Call Trace: [ 1934.273474] __schedule+0x232/0x700 [ 1934.273475] schedule+0x36/0x80 [ 1934.273477] schedule_preempt_disabled+0xe/0x10 [ 1934.273478] __mutex_lock_slowpath+0x193/0x290 [ 1934.273480] mutex_lock+0x2f/0x40 [ 1934.273482] __blkdev_get+0x6f/0x400 [ 1934.273483] blkdev_get+0x129/0x330 [ 1934.273485] blkdev_open+0x82/0xd0 [ 1934.273487] do_dentry_open+0x208/0x310 [ 1934.273488] ? blkdev_get_by_dev+0x50/0x50 [ 1934.273489] vfs_open+0x4c/0x70 [ 1934.273491] ? may_open+0x9b/0x100 [ 1934.273492] path_openat+0x2ac/0x1430 [ 1934.273494] do_filp_open+0x91/0x100 [ 1934.273496] ? __alloc_fd+0x46/0x170 [ 1934.273498] do_sys_open+0x12d/0x280 [ 1934.273500] SyS_open+0x1e/0x20 [ 1934.273502] entry_SYSCALL_64_fastpath+0x1e/0xad [ 1934.273503] RIP: 0033:0x7f915b83bc60 [ 1934.273504] RSP: 002b:7ffccbefa178 EFLAGS:
[Touch-packages] [Bug 1613729] Re: NetworkManager autoconnects to wired profiles in reverse order
Wow, I'm sorry I totally forget about this. Are you still interested in seeing this fixed in the Ubuntu archive? -- 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/1613729 Title: NetworkManager autoconnects to wired profiles in reverse order Status in network-manager package in Ubuntu: Invalid Status in network-manager source package in Trusty: New Bug description: When I select a wired profile manually and reboot, NetworkManager instead connects to the profile that has the oldest timestamp. So it's not connecting to the last used profile, which is troublesome. On all of our machines (about 500), we define three wired network profiles, one DHCP and two static. We're migrating from Debian to Ubuntu, so this bug has only surfaced now for us. This can be reproduced by creating a couple of network profiles on the same wired interface and then rebooting or restarting network-manager. It will loop through the network profiles in the same order always. So it's doing the exact reverse of what's supposed to happen. I did some digging and I applied a simple patch to the source code. This seems to have fixed the issue. I posted my patch for verification on the networkmanager mailing list and it was verified as being correct by Beniamino Galvani, one of the developers. Here is the link to the network-manager topic: https://mail.gnome.org/archives/networkmanager- list/2016-August/msg00053.html This is the patch (also included as attachment): --- nm-device.c 2016-08-16 15:37:50.0 +0200 +++ nm-device_patched.c 2016-08-16 15:44:08.308729955 +0200 @@ -1267,7 +1267,7 @@ s_con = nm_connection_get_setting_connection (connection); g_assert (s_con); if (nm_setting_connection_get_autoconnect (s_con)) - available_conns = g_slist_prepend (available_conns, connection); + available_conns = g_slist_append (available_conns, connection); } if (!available_conns) I hope to get this patch included in the trusty package, so somebody else can benefit from this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.3 ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CRDA: Error: [Errno 2] Bestand of map bestaat niet: 'iw' CurrentDesktop: Unity Date: Tue Aug 16 15:23:17 2016 IfupdownConfig: auto lo iface lo inet loopback IpRoute: default via 10.30.6.1 dev em1 proto static 10.30.6.0/24 dev em1 proto kernel scope link src 10.30.6.204 metric 1 10.40.8.0/21 dev tun0 proto kernel scope link src 10.40.8.31 IwConfig: tun0 no wireless extensions. em1 no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=nl_BE: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_BE SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH DHCP 702624f9-f052-473a-b131-acd2045e6ec2 802-3-ethernet1471353746 di 16 aug 2016 15:22:26 CEST yes no /org/freedesktop/NetworkManager/Settings/1 Proximus 7a9a5bc2-d51a-46b4-b721-050a607951bc 802-3-ethernet1471353744 di 16 aug 2016 15:22:24 CEST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH em1802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1613729/+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 1725458] Re: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful
I changed my fstab from UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4 errors=remount-ro 0 1 to UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4 rw,errors=remount-ro 0 1 and it now boots fine again. I don't know why that is necessary now and why the update didn't notify me or made the change automatically. -- 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/1725458 Title: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful Status in systemd package in Ubuntu: New Bug description: After not touching my notebook since 30th September (where I did the dist-upgrade to artful and installed all available updates), I did all available updates today (20th October) and the system didn't boot after that. The last message I see is "Reached target Bluetooth". Before that, there are several failed services. GDM doesn't come up. After logging in on tty2, I saw that the root partition was mounted read-only. Inspecting the messages of e.g. systemd-resolved shows that it didn't start because of the read-only filesystem. After remounting it fw, I was able to restart the daemons and could also start GDM and login fine. My fstab shows: UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4 errors=remount-ro 0 1 The UUID is correct as "mount / -o remount,rw" works fine. Booting with the previous kernel doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 21:46:36 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-26 (451 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago) dmi.bios.date: 09/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81A1 dmi.board.vendor: HP dmi.board.version: 33.76 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458/+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 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Changed in: cracklib2 (Ubuntu Yakkety) Status: Triaged => Won't Fix -- 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/1681231 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Confirmed Status in cracklib2 package in Ubuntu: Triaged Status in cracklib2 source package in Trusty: Incomplete Status in cracklib2 source package in Xenial: Incomplete Status in cracklib2 source package in Yakkety: Won't Fix Status in cracklib2 source package in Zesty: Triaged Status in cracklib2 package in Debian: Fix Released Bug description: This seems to be the same problem as described in bug #1636262, only this time it happened during upgrade from 16.10 to 17.04. The setup process (do-release-upgrade -d) aborted and I had to finish it manually. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: cracklib-runtime 2.9.2-3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sun Apr 9 17:09:37 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-07-26 (257 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1681231/+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 1725458] [NEW] System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful
Public bug reported: After not touching my notebook since 30th September (where I did the dist-upgrade to artful and installed all available updates), I did all available updates today (20th October) and the system didn't boot after that. The last message I see is "Reached target Bluetooth". Before that, there are several failed services. GDM doesn't come up. After logging in on tty2, I saw that the root partition was mounted read-only. Inspecting the messages of e.g. systemd-resolved shows that it didn't start because of the read-only filesystem. After remounting it fw, I was able to restart the daemons and could also start GDM and login fine. My fstab shows: UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4errors =remount-ro 0 1 The UUID is correct as "mount / -o remount,rw" works fine. Booting with the previous kernel doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 21:46:36 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-26 (451 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago) dmi.bios.date: 09/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81A1 dmi.board.vendor: HP dmi.board.version: 33.76 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible dmi.sys.vendor: HP ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1725458 Title: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful Status in systemd package in Ubuntu: New Bug description: After not touching my notebook since 30th September (where I did the dist-upgrade to artful and installed all available updates), I did all available updates today (20th October) and the system didn't boot after that. The last message I see is "Reached target Bluetooth". Before that, there are several failed services. GDM doesn't come up. After logging in on tty2, I saw that the root partition was mounted read-only. Inspecting the messages of e.g. systemd-resolved shows that it didn't start because of the read-only filesystem. After remounting it fw, I was able to restart the daemons and could also start GDM and login fine. My fstab shows: UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4 errors=remount-ro 0 1 The UUID is correct as "mount / -o remount,rw" works fine. Booting with the previous kernel doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 21:46:36 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-26 (451 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago) dmi.bios.date: 09/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81A1 dmi.boar
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
Verification-done for xenial with nplan 0.29~16.04.1: This was a regression in the development release that transpired in a new SRU that has not been migrated to the stable release. The bad version is 0.26; current state of nplan in xenial is 0.23~16.04.1 in -updates. Verified that lxc list shows an IPv4 and IPv6 address when a container is set up to use netplan with 0.29~16.04.1. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in nplan source package in Zesty: Fix Committed Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+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 1693948] Re: useless diagnostics in dpkg.log from journalctl due to ellipses
** Summary changed: - useless diagnostics in DpkgTerminalLog from journalctl due to ellipses + useless diagnostics in dpkg.log from journalctl due to ellipses ** Changed in: apport (Ubuntu) Status: Incomplete => Confirmed ** Package changed: apport (Ubuntu) => dpkg (Ubuntu) -- 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/1693948 Title: useless diagnostics in dpkg.log from journalctl due to ellipses Status in dpkg package in Ubuntu: Confirmed Bug description: Many of the apport hooks try to include some information about why a service didn't start correctly. One recent report included the following: May 26 18:39:19 ux305ua-linux systemd[1]: Starting OpenBSD Secure Shell serv May 26 18:39:19 ux305ua-linux sshd[2500]: /etc/ssh/sshd_config line 64: miss May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Main process exited, ...a[0m May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;31mFailed to start OpenBSD Secure She[0m May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Unit entered failed s[0m May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Failed with result 'e[0m Hint: Some lines were ellipsized, use -l to show in full. The actual error information is this: /etc/ssh/sshd_config line 64: miss and Failed with result 'e This is very nearly useless. We should include the -l parameter as suggested so that we stand a chance of seeing an error that doesn't occur in the first twenty characters of program output. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1693948/+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 1725455] [NEW] Dual 4K monitor via Displayport MST not working (Lenovo Ultra Dock)
Public bug reported: I am experiencing serious issues after upgrading to Ubuntu 17.10 (coming from 17.04 with Gnome, kernel 4.13). I have 2 x 4K (Asus PB279Q) monitors, connected to a Lenovo Ultra Dock (containing 2 x Displayport via MST), where the Lenovo T550 is connected onto it. Both monitors were working perfectly fine at 30Hz simultaneously in an extended desktop, 4K resolution in my old setup with Gnome for over half a year (since kernel 4.10 blink issues on 4K were solved, i used this setup since then). However after upgrading to 17.10 using the new Gnome interface: When the laptop is connected to the Lenovo Ultra Dock (to work on both monitors), the system is hanging and becoming unresponsive. The mouse pointer is freezing and the only way is to do a hard-reboot. I have checked the monitor settings, it's displayed at 60Hz when active, and it appears I am never able to use both monitors simultaneously. When I get 1 monitor working (disconnecting the 2nd monitor from the MST port), after rebooting it works fine. I tried to put settings of the 4K manually on 30Hz, reconnecting, but the system hangs again. I have tried several combinations. It results in a blank (purple) screen and hanging mouse (see attachment). I tried also with the installation-iso to run a fresh 17.10 and tried the same, the symptoms are similar. I suspect that must be an issue with the Displayport MST on dual 4K setups in the new 17.10. When I connect 1 x 4K monitor to the rear displayport of the Lenovo Ultra Dock (there are 2 for MST on the rear, so I disconnected the other) *and* when I connect the other 4K monitor on the separate displayport of the T550 itself instead, it works 100% fine! Shortly: based on my knowledge that must definitely be some issue with the MST displayport functionality itself, that is unable to recognize/identify both 4K monitors when connected to the dock's both displayport connections? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.13.4-041304-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 21:10:50 2017 DistUpgraded: 2017-10-19 21:54:53,162 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2225] Subsystem: Lenovo GM108M [GeForce 940M] [17aa:2225] InstallationDate: Installed on 2017-04-16 (186 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.4-041304-generic root=UUID=9fcc7f4c-35c0-4297-9c98-4dac9acee798 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET42W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CKCTO1WW:pvrThinkPadT550:rvnLENOVO:rn20CKCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CKCTO1WW dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Apr 17 17:36:46 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu wayland-session ** Attachment added: "Hanging during boot, when both monitors are connected" https://bugs.launchpad.net/bugs/1725455/+attachment/4980053/+files/IMG_4311.jpg -- 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/1725455 Title: Dual 4K monitor via Displayport MST not working (Lenovo Ultra Dock)
[Touch-packages] [Bug 1693948] Re: useless diagnostics in DpkgTerminalLog from journalctl due to ellipses
The file /var/log/dpkg.log contains the ellipsized lines so yeah I think dpkg is better place for this. -- 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/1693948 Title: useless diagnostics in dpkg.log from journalctl due to ellipses Status in dpkg package in Ubuntu: Confirmed Bug description: Many of the apport hooks try to include some information about why a service didn't start correctly. One recent report included the following: May 26 18:39:19 ux305ua-linux systemd[1]: Starting OpenBSD Secure Shell serv May 26 18:39:19 ux305ua-linux sshd[2500]: /etc/ssh/sshd_config line 64: miss May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Main process exited, ...a[0m May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;31mFailed to start OpenBSD Secure She[0m May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Unit entered failed s[0m May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Failed with result 'e[0m Hint: Some lines were ellipsized, use -l to show in full. The actual error information is this: /etc/ssh/sshd_config line 64: miss and Failed with result 'e This is very nearly useless. We should include the -l parameter as suggested so that we stand a chance of seeing an error that doesn't occur in the first twenty characters of program output. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1693948/+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 1628763] Re: Example of Queue from documentation fails
** Changed in: python3-defaults (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1628763 Title: Example of Queue from documentation fails Status in python3-defaults package in Ubuntu: Invalid Bug description: Reading https://docs.python.org/3.5/library/multiprocessing.html #exchanging-objects-between-processes, I have copy-pasted the code into a file. Running it with python3 fails thus: Traceback (most recent call last): File "q.py", line 7, in q = Queue() File "/usr/lib/python3.5/multiprocessing/context.py", line 100, in Queue from .queues import Queue File "/usr/lib/python3.5/multiprocessing/queues.py", line 20, in from queue import Empty, Full ImportError: cannot import name 'Empty' I will attach the actual code file. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Sep 28 20:54:17 2016 InstallationDate: Installed on 2016-08-08 (51 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1628763/+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 1724256] Re: apport-cli crashed with UnicodeEncodeError in show(): 'ascii' codec can't encode characters in position 5-8: ordinal not in range(128)
** Information type changed from Private to Public ** Changed in: apport (Ubuntu) Status: Incomplete => New -- 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/1724256 Title: apport-cli crashed with UnicodeEncodeError in show(): 'ascii' codec can't encode characters in position 5-8: ordinal not in range(128) Status in apport package in Ubuntu: New Bug description: Possible duplicate of bug 1083555. I got this trying to run apport over ssh from a Mac. The same thing worked from a different system running Ubuntu. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportLog: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashReports: 640:1000:115:18974:2017-10-17 15:42:52.743125200 +0200:2017-10-17 16:04:06.029511936 +0200:/var/crash/_usr_bin_apport-cli.1000.crash Date: Tue Oct 17 15:42:53 2017 ExecutablePath: /usr/bin/apport-cli InstallationDate: Installed on 2016-05-31 (504 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/apport-cli 2819 Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/bin/apport-cli', '2819'] PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SourcePackage: apport Title: apport-cli crashed with UnicodeEncodeError in show(): 'ascii' codec can't encode characters in position 5-8: ordinal not in range(128) UpgradeStatus: Upgraded to artful on 2017-10-05 (12 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1724256/+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 1725433] Re: evolution-addressbook-factory-subprocess crashed with SIGSEGV in i18n::phonenumbers::RegExp::FullMatch()
*** This bug is a duplicate of bug 1723375 *** https://bugs.launchpad.net/bugs/1723375 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 #1723375, 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/1725433/+attachment/4979855/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725433/+attachment/4979857/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725433/+attachment/4979861/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725433/+attachment/4979862/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725433/+attachment/4979863/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725433/+attachment/4979864/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725433/+attachment/4979866/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1723375 ** 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 evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1725433 Title: evolution-addressbook-factory-subprocess crashed with SIGSEGV in i18n::phonenumbers::RegExp::FullMatch() Status in evolution-data-server package in Ubuntu: New Bug description: I dont no ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: evolution-data-server 3.26.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 20 20:57:06 2017 ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory-subprocess InstallationDate: Installed on 2017-04-06 (197 days ago) InstallationMedia: ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory-subprocess --factory google --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx1891x3 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/1891/3 SegvAnalysis: Segfault happened at: 0x7f6f1411ed20:add%al,(%rax) PC (0x7f6f1411ed20) in non-executable VMA region: 0x7f6f1400-0x7f6f14517000 rw-p None source "%al" ok destination "(%rax)" (0x7f6f1411ed20) ok Stack memory exhausted (SP below stack segment) SegvReason: executing writable VMA None Signal: 11 SourcePackage: evolution-data-server Title: evolution-addressbook-factory-subprocess crashed with SIGSEGV in i18n::phonenumbers::RegExp::FullMatch() UpgradeStatus: Upgraded to artful on 2017-10-01 (19 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1725433/+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 1725407] Re: systemd-udevd crashed with SIGABRT in __libc_open64()
*** This bug is a duplicate of bug 1715782 *** https://bugs.launchpad.net/bugs/1715782 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 #1715782, 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/1725407/+attachment/4979657/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725407/+attachment/4979660/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725407/+attachment/4979667/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725407/+attachment/4979669/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725407/+attachment/4979670/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725407/+attachment/4979671/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725407/+attachment/4979672/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1715782 ** 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1725407 Title: systemd-udevd crashed with SIGABRT in __libc_open64() Status in systemd package in Ubuntu: New Bug description: Occurred right after logout/login of user. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 08:33:03 2017 ExecutablePath: /lib/systemd/systemd-udevd InstallationDate: Installed on 2017-06-13 (128 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170613) MachineType: ASUS All Series ProcCmdline: /lib/systemd/systemd-udevd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=ef479f79-2edf-4de1-a70f-d90ea62c6f93 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_open64 (file=0x5654173eed40 "/dev/sde", oflag=657408) at ../sysdeps/unix/sysv/linux/open64.c:46 ?? () ?? () ?? () ?? () Title: systemd-udevd crashed with SIGABRT in __libc_open64() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725407/+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 1681249] Re: tracker-extract crashed with signal 31 in chdir()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tracker (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1681249 Title: tracker-extract crashed with signal 31 in chdir() Status in tracker package in Ubuntu: Confirmed Bug description: tracker crash while indexing my homedir ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: tracker-extract 1.12.0-0ubuntu1 Uname: Linux 4.10.8-041008-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 8 14:00:45 2017 EcryptfsInUse: Yes ExecutablePath: /usr/lib/tracker/tracker-extract ExecutableTimestamp: 1490023113 JournalErrors: No journal files were found. -- No entries -- ProcCmdline: /usr/lib/tracker/tracker-extract ProcCwd: /home/bonnaudl Signal: 31 SourcePackage: tracker Title: tracker-extract crashed with signal 31 in chdir() UpgradeStatus: Upgraded to zesty on 2017-04-08 (0 days ago) UserGroups: adm cdrom dip fuse libvirt libvirtd lpadmin plugdev sambashare staff sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1681249/+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 1724805] Re: wpa_supplicant fails to shutdown
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wpa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1724805 Title: wpa_supplicant fails to shutdown Status in wpa package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 wpasupplicant 2.4-0ubuntu10 System shutdown hangs because wpa_supplicant is not stopping itself. Test with: $ sudo systemctl stop wpa_supplicant Journal shows: 11:37:32 systemd[1]: Stopping WPA supplicant... 11:37:32 wpa_supplicant[941]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 11:37:32 wpa_supplicant[941]: p2p-dev-wlp2s0: CTRL-EVENT-TERMINATING 11:37:32 kernel: wlp2s0: deauthenticating from by local choice (Reason: 3=DEAUTH_LEAVING) 11:39:02 systemd[1]: wpa_supplicant.service: State 'stop-sigterm' timed out. Killing. 11:39:02 systemd[1]: wpa_supplicant.service: Killing process 941 (wpa_supplicant) with signal SIGKILL. 11:40:33 systemd[1]: wpa_supplicant.service: Processes still around after SIGKILL. Ignoring. 11:42:03 systemd[1]: wpa_supplicant.service: State 'stop-final-sigterm' timed out. Killing. 11:42:03 systemd[1]: wpa_supplicant.service: Killing process 941 (wpa_supplicant) with signal SIGKILL. 11:43:33 systemd[1]: wpa_supplicant.service: Processes still around after final SIGKILL. Entering failed mode. 11:43:33 systemd[1]: Stopped WPA supplicant. 11:43:33 systemd[1]: wpa_supplicant.service: Unit entered failed state. 11:43:33 systemd[1]: wpa_supplicant.service: Failed with result 'timeout'. lspci output: 02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 30) P.S. also shows this bug, but reporting much more frequently then 2 minutes: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1323089 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1724805/+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 1725392] Re: signon-ui crashed with SIGSEGV in QWindow::setModality()
*** This bug is a duplicate of bug 1723230 *** https://bugs.launchpad.net/bugs/1723230 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 #1723230, 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/1725392/+attachment/4979524/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725392/+attachment/4979526/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725392/+attachment/4979529/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725392/+attachment/4979530/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725392/+attachment/4979531/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725392/+attachment/4979532/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725392/+attachment/4979533/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1723230 ** 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 signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1725392 Title: signon-ui crashed with SIGSEGV in QWindow::setModality() Status in signon-ui package in Ubuntu: New Bug description: Simply trying to add online accounts in Kubuntu 17.10 ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: signon-ui-x11 0.17+17.10.20170606-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Fri Oct 20 11:21:22 2017 ExecutablePath: /usr/bin/signon-ui InstallationDate: Installed on 2017-09-18 (31 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/signon-ui ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f54c5cfe5a0 <_ZN7QWindow11setModalityEN2Qt14WindowModalityE>: mov0x8(%rdi),%rax PC (0x7f54c5cfe5a0) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: signon-ui StacktraceTop: QWindow::setModality(Qt::WindowModality) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 ?? () ?? () ?? () QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 Title: signon-ui crashed with SIGSEGV in QWindow::setModality() UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo XsessionErrors: (kerneloops-applet:2014): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", (kerneloops-applet:2014): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1725392/+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 1725410] [NEW] Intel Integrated Card not working Asus Hero Alpha VIII
Public bug reported: After upgrading to the latest Kernel, the issue appeared. Basically it always says there is no cable detected and the LAN (Wired) connection never works. Only wireless. If I go back to a previous Ubuntu version it works, but after either 4.12 or 4.13 the issue appeared. I also checked the BIOS version and it works only if I stay with a previous Ubuntu version. The device that is having an issue is: description: Ethernet interface product: Ethernet Connection (2) I219-V vendor: Intel Corporation physical id: 1f.6 bus info: pci@:00:1f.6 logical name: enp0s31f6 version: 31 serial: 34:97:f6:36:cb:d6 capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k firmware=0.7-4 latency=0 link=no multicast=yes port=twisted pair resources: irq:132 memory:df70-df71 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8] (rev 31) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 11:59:57 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-10-19 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.1.1 dev wlp9s0 proto static metric 600 169.254.0.0/16 dev wlp9s0 scope link metric 1000 192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.13 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Linux 74b235bc-acdd-4fc3-a028-d960c890fbe0 802-11-wireless 1508522270 Fri 20 Oct 2017 11:57:50 AM CST yes 0 no /org/freedesktop/NetworkManager/Settings/2 yes wlp9s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Intel ce6b4984-a66e-306e-9a98-9487e5b3c553 802-3-ethernet 1508435911 Thu 19 Oct 2017 11:58:31 AM CST yes 4294966297no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp9s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Linux 74b235bc-acdd-4fc3-a028-d960c890fbe0 /org/freedesktop/NetworkManager/ActiveConnection/1 enp0s31f6 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1725410 Title: Intel Integrated Card not working Asus Hero Alpha VIII Status in network-manager package in Ubuntu: New Bug description: After upgrading to the latest Kernel, the issue appeared. Basically it always says there is no cable detected and the LAN (Wired) connection never works. Only wireless. If I go back to a previous Ubuntu version it works, but after either 4.12 or 4.13 the issue appeared. I also checked the BIOS version and it works only if I stay with a previous Ubuntu version. The device that is having an issue is: description: Ethernet interface product: Ethernet Connection (2) I219-V vendor: Intel Corporation physical id: 1f.6 bus info: pci@:00:1f.6 logical name: enp0s31f6 version: 31
[Touch-packages] [Bug 1725387] Re: systemd-udevd crashed with SIGABRT in __libc_open64()
*** This bug is a duplicate of bug 1715782 *** https://bugs.launchpad.net/bugs/1715782 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 #1715782, 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/1725387/+attachment/4979474/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725387/+attachment/4979477/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725387/+attachment/4979484/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725387/+attachment/4979486/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725387/+attachment/4979487/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725387/+attachment/4979488/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725387/+attachment/4979489/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1715782 ** 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1725387 Title: systemd-udevd crashed with SIGABRT in __libc_open64() Status in systemd package in Ubuntu: New Bug description: None ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CustomUdevRuleFiles: 70-snap.core.rules 70-snap.hiri.rules 70-snap.libreoffice.rules Date: Fri Oct 13 12:56:21 2017 ExecutablePath: /lib/systemd/systemd-udevd InstallationDate: Installed on 2017-10-13 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171013) MachineType: LENOVO 4518W2Q ProcCmdline: /lib/systemd/systemd-udevd ProcEnviron: LANG=es_BO.UTF-8 LANGUAGE=es_BO:es PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=2cec7de1-06bd-425f-a813-a86044f86f54 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_open64 (file=0x55c11d773d80 "/dev/sdb", oflag=657408) at ../sysdeps/unix/sysv/linux/open64.c:46 ?? () ?? () ?? () ?? () Title: systemd-udevd crashed with SIGABRT in __libc_open64() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/10/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT47AUS dmi.board.vendor: LENOVO dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvr9HKT47AUS:bd01/10/2012:svnLENOVO:pn4518W2Q:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 4518W2Q dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725387/+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 1725404] [NEW] 10-finger typing: Ctrl+Alt does not work as "AltGr for left hand"
Public bug reported: Touch typing (or 10-finger typing) requires to utilize both hands to maximize writing speed. Unfortunately, Ubuntu currently doesn't support a left-hand alternative to AltGr. Related questions: StackOverflow: https://askubuntu.com/questions/919257/ctrl-alt-not-working-on-ubuntu-but-does-on-windows Launchpad: https://answers.launchpad.net/ubuntu/+question/657015 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1725404 Title: 10-finger typing: Ctrl+Alt does not work as "AltGr for left hand" Status in xorg package in Ubuntu: New Bug description: Touch typing (or 10-finger typing) requires to utilize both hands to maximize writing speed. Unfortunately, Ubuntu currently doesn't support a left-hand alternative to AltGr. Related questions: StackOverflow: https://askubuntu.com/questions/919257/ctrl-alt-not-working-on-ubuntu-but-does-on-windows Launchpad: https://answers.launchpad.net/ubuntu/+question/657015 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1725404/+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 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs
On 20.10.2017 [08:24:37 -0700], Nish Aravamudan wrote: > On 20.10.2017 [07:18:15 -], Jan Gutter wrote: > > I had a look at the two proposals and could not spot any obvious > > mistakes: > > > > - the correct upstream git commit has been cherry-picked > > - I don't have any objections to attribution or log messages > > > > Thanks again for shepherding this one through! > > You're welcome, I'll upload them both today. > > Thank you and Monique for filing the SRU template properly! I have sponsored both packages. They will need to be approved by an SRU team member (probably next week) before they appear in {trusty,xenial}-proposed and then they will need testing as built in proposed, with a minimum bake time of 7 days in proposed. Thank you and Monique for your contribution to Ubuntu! -Nish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1720126 Title: [ip link] Message truncated error for large number of passthrough VFs Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Trusty: New Status in iproute2 source package in Xenial: Confirmed Status in iproute2 source package in Zesty: Fix Released Status in iproute2 package in CentOS: Unknown Bug description: [Impact] When querying a Physical Function netdev with a large amount of VF's (more than 30), the resulting return message can overflow the 16K netlink message buffer. This can be fixed by enabling message peeking on the socket and resizing the buffer on receive, or by simply enlarging the receive buffer. Since there's an upper limit to the number of VF's per PF, it's relatively sane to just enlarge the receive buffer. Please see the attached patch. [Test Case] # Set up 60 VF's on an SR-IOV device ip link show > /dev/null Observe the following: Message truncated Message truncated Message truncated [Regression Potential] 1) Applications relying on the broken behaviour will need to be updated, but it would be a really dubious use case. 2) Increasing the rx buffer size increases the memory footprint (but realistically, this is tiny). 3) Extra processing time is now needed to parse the larger buffer, in the case that a call to "ip link" is on the critical time path of an application, (called multiple times in a tight loop, for example), it would affect load. [Other Info] Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04 = Ubuntu16 system stack@cluster04:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial stack@cluster04:~$ uname -r 4.4.0-93-generic stack@cluster04:~$ apt-cache policy iproute2 iproute2: Installed: 4.3.0-1ubuntu3.16.04.1 Version table: *** 4.3.0-1ubuntu3.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages = Ubuntu14 system: root@boomslang:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.3 LTS Release: 14.04 Codename: trusty root@boomslang:~# uname -r 4.4.0-96-generic root@boomslang:~# apt-cache policy iproute2 iproute2: Installed: 3.12.0-2ubuntu1 Version table: *** 3.12.0-2ubuntu1 0 500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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 1720525] Re: Sync python-evdev 0.7.0+dfsg-2 (universe) from Debian unstable (main)
** Summary changed: - Update package to newer version + Sync python-evdev 0.7.0+dfsg-2 (universe) from Debian unstable (main) ** Description changed: + Please sync python-evdev 0.7.0+dfsg-2 (universe) from Debian unstable + (main) + + This sync request is (obviously) targeted for BB once the development + archive opens. + + Explanation of the Ubuntu delta and why it can be dropped: + So far the package has been packaged in Ubuntu only¸ but it is now available in Debian as well. + The Debian maintainer commented in comment #2 that there doesn't seem to be any changes added in the Ubuntu package which isn't in upstream. + (I haven't investigated the details) + + Changelog entries in Debian: + + python-evdev (0.7.0+dfsg-2) unstable; urgency=medium + + * Limit the architecture to linux-any. Closes: #875624. + * Switch to Python 3 Docutils and Sphinx, build-conflicting on + python-sphinx to avoid issues with that being picked in preference to + python3-sphinx. + * Clean up debian/control with cme. + * Drop the new-package-should-not-package-python2-module override + since this is no longer a new package. + * Standards-Version 4.1.1, no change required. + + -- Stephen Kitt Sat, 07 Oct 2017 11:49:45 +0200 + + python-evdev (0.7.0+dfsg-1) unstable; urgency=medium + + * Initial release. Closes: #709988. + + -- Stephen Kitt Fri, 01 Sep 2017 13:56:02 +0200 + + + Original description: + In Artful (and older releases) the version of the package is 0.4.7 even though 0.7.0 is already out. Debian Buster and Sid has 0.7.0 in the repos. The changes are bug fixes and features (see http://python-evdev.readthedocs.io/en/latest/changelog.html). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1720525 Title: Sync python-evdev 0.7.0+dfsg-2 (universe) from Debian unstable (main) Status in python-evdev package in Ubuntu: New Bug description: Please sync python-evdev 0.7.0+dfsg-2 (universe) from Debian unstable (main) This sync request is (obviously) targeted for BB once the development archive opens. Explanation of the Ubuntu delta and why it can be dropped: So far the package has been packaged in Ubuntu only¸ but it is now available in Debian as well. The Debian maintainer commented in comment #2 that there doesn't seem to be any changes added in the Ubuntu package which isn't in upstream. (I haven't investigated the details) Changelog entries in Debian: python-evdev (0.7.0+dfsg-2) unstable; urgency=medium * Limit the architecture to linux-any. Closes: #875624. * Switch to Python 3 Docutils and Sphinx, build-conflicting on python-sphinx to avoid issues with that being picked in preference to python3-sphinx. * Clean up debian/control with cme. * Drop the new-package-should-not-package-python2-module override since this is no longer a new package. * Standards-Version 4.1.1, no change required. -- Stephen Kitt Sat, 07 Oct 2017 11:49:45 +0200 python-evdev (0.7.0+dfsg-1) unstable; urgency=medium * Initial release. Closes: #709988. -- Stephen Kitt Fri, 01 Sep 2017 13:56:02 +0200 Original description: In Artful (and older releases) the version of the package is 0.4.7 even though 0.7.0 is already out. Debian Buster and Sid has 0.7.0 in the repos. The changes are bug fixes and features (see http://python-evdev.readthedocs.io/en/latest/changelog.html). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-evdev/+bug/1720525/+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 1686189] Re: External monitor connecting problem on Intel graphics card
@Kai-Heng thanks a lot, using the modesetting driver helped! I just read that using the Intel driver is not recommended anymore on newer systems, I didn't know that. -- 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/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+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 1688364] Re: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq
correction - needed to disable dnsmasq service as network manager starts it instead. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1688364 Title: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq Status in dnsmasq package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Status in resolvconf package in Ubuntu: New Bug description: May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1688364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://he
[Touch-packages] [Bug 1725172] Re: package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: tentata sovrascrittura di "/usr/share/doc/libperl5.24/changelog.Debian.gz" (condiviso), diverso da alt
*** This bug is a duplicate of bug 1574351 *** https://bugs.launchpad.net/bugs/1574351 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1574351, so it 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. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1574351 package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1725172 Title: package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: tentata sovrascrittura di "/usr/share/doc/libperl5.24/changelog.Debian.gz" (condiviso), diverso da altre istanze del pacchetto libperl5.24:i386 Status in perl package in Ubuntu: New Bug description: I cannot install this package ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libperl5.24 5.24.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Wed Oct 18 08:40:53 2017 ErrorMessage: tentata sovrascrittura di "/usr/share/doc/libperl5.24/changelog.Debian.gz" (condiviso), diverso da altre istanze del pacchetto libperl5.24:i386 InstallationDate: Installed on 2016-11-05 (348 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: perl Title: package libperl5.24 5.24.1-2ubuntu1 failed to install/upgrade: tentata sovrascrittura di "/usr/share/doc/libperl5.24/changelog.Debian.gz" (condiviso), diverso da altre istanze del pacchetto libperl5.24:i386 UpgradeStatus: Upgraded to zesty on 2017-10-08 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1725172/+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 1725333] Re: do-release-upgrade broke WSL
** Summary changed: - do-release-upgrade broked WSL + do-release-upgrade broke WSL -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1725333 Title: do-release-upgrade broke WSL Status in bash package in Ubuntu: New Bug description: I had Ubuntu 17.04 installed in WSL and decided to upgrade it to 17.10, so I had run do-release-upgrade, as I did before to upgrade to 17.04. Everything was fine before script started upgrading packages. It's started from bash updating, and somehow there is a problem revealed that locale files is missing, and locale-gen can't be run (because of bug in WSL). I've tried to install language-pack-en as was suggested, but problem haven't resolved, any attempt to update leads to this error. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: bash 4.4-2ubuntu1.1 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Fri Oct 20 18:03:30 2017 Dmesg: DpkgTerminalLog: Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ... preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. dpkg: error processing archive /var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack): subprocess new pre-installation script was killed by signal (Aborted), core dumped DuplicateSignature: package:bash:4.4-2ubuntu1.1 Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ... preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. dpkg: error processing archive /var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack): subprocess new pre-installation script was killed by signal (Aborted), core dumped ErrorMessage: subprocess new pre-installation script was killed by signal (Aborted), core dumped RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: bash Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new pre-installation script was killed by signal (Aborted), core dumped UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1725333/+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 1725354] Re: systemd-udevd crashed with SIGABRT in ioctl()
*** This bug is a duplicate of bug 1497641 *** https://bugs.launchpad.net/bugs/1497641 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 #1497641, 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/1725354/+attachment/4979242/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725354/+attachment/4979245/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725354/+attachment/4979252/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725354/+attachment/4979254/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725354/+attachment/4979255/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725354/+attachment/4979256/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725354/+attachment/4979257/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1497641 ** 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1725354 Title: systemd-udevd crashed with SIGABRT in ioctl() Status in systemd package in Ubuntu: New Bug description: Just updated to 17.10 the previous day. Not looking how it should. Creating USB startup with Ubuntu .iso ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CustomUdevRuleFiles: 60-ssd-scheduler.rules Date: Fri Oct 20 16:54:57 2017 ExecutablePath: /lib/systemd/systemd-udevd InstallationDate: Installed on 2015-05-03 (901 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Gigabyte Technology Co., Ltd. GA-880GM-UD2H ProcCmdline: /lib/systemd/systemd-udevd ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=e5e9c37e-0d34-4caf-a86e-946ddc7f7100 ro quiet splash Signal: 6 SourcePackage: systemd StacktraceTop: ioctl () at ../sysdeps/unix/syscall-template.S:84 ?? () ?? () ?? () ?? () Title: systemd-udevd crashed with SIGABRT in ioctl() UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) UserGroups: dmi.bios.date: 10/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8 dmi.board.name: GA-880GM-UD2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd10/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GM-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GM-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GM-UD2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725354/+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 1638695] Re: Python 2.7.12 performance regression
I have managed to prepare the static build without PIE on top the latest artful version [1]. I have added the results to the same spreadsheet. What I've found particularly interesting are the results of the python_startup & python_startup_no_site tests. In subsequent runs (the result in the spreadsheet was for the second run of the testsuite) the improvement is really significant. I believe this is thanks to the fact that the relative addresses don't need to be patched before running the binary. In case of the rest of the tests: there are some small improvements as well as some minor performance decreases. [1] ppa:dgadomski/pyperf (python2.7 - 2.7.14-2ubuntu3~lp1638695~4) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1638695 Title: Python 2.7.12 performance regression Status in python2.7 package in Ubuntu: Fix Released Status in python2.7 source package in Xenial: Confirmed Bug description: I work on the OpenStack-Ansible project and we've noticed that testing jobs on 16.04 take quite a bit longer to complete than on 14.04. They complete within an hour on 14.04 but they normally take 90 minutes or more on 16.04. We use the same version of Ansible with both versions of Ubuntu. After more digging, I tested python performance (using the 'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12). There is a significant performance difference between each version of python. That is detailed in a spreadsheet[0]. I began using perf to dig into the differences when running the python performance module and when using Ansible playbooks. CPU migrations (as measured by perf) are doubled in Ubuntu 16.04 when running the same python workloads. I tried changing some of the kerne.sched sysctl configurables but they had very little effect on the results. I compiled python 2.7.12 from source on 14.04 and found the performance to be unchanged there. I'm not entirely sure where the problem might be now. We also have a bug open in OpenStack-Ansible[1] that provides additional detail. Thanks in advance for any help you can provide! [0] https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing [1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+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 1719043] Re: Gnome web urlbar very slow to show typed input
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1719043 Title: Gnome web urlbar very slow to show typed input Status in GTK+: Confirmed Status in epiphany-browser package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Fix Committed Status in mutter package in Ubuntu: Triaged Status in gtk+3.0 source package in Artful: Fix Committed Status in gtk+3.0 package in Debian: Fix Released Bug description: Impact == It is very difficult to use the address bar in Epiphany on GNOME on Wayland because after a few characters, the address bar field stops redrawing. (This apparently was triggered by mutter 3.26?) Test Case = sudo apt install epiphany-browser Open the Web app Type a URL into the address bar. Type a lng URL. You should see all the characters you type into the address bar. Regression Potential === This is a minimal patch cherry-picked from GTK 3.22 git master (will be part of future GTK+ 3.22.25). I also pushed this patch to Debian unstable. Original Bug Report === First two characters typed in urlbar show immediately, other characters take up to 30 seconds to appear, or url will appear in full once enter key is pressed. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: epiphany-browser 3.26.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 18:42:19 2017 InstallationDate: Installed on 2017-09-22 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: epiphany-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1719043/+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 1725360] [NEW] Secondary display can not be set
Public bug reported: The position of the secondary display can not be applied with scales of 200% and 300%. Can be modified with scale of 100% after modified some other configuration like Single Display scale. After set a new position of the secondary display (with 100% scale) is not possible to change the scale maintaining the actual position. Using also Nvidia driver 384.90 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 14:02:12 2017 DistUpgraded: 2017-10-20 13:15:46,366 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3978] Subsystem: Lenovo GM107M [GeForce GTX 960M] [17aa:3978] InstallationDate: Installed on 2017-08-23 (57 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file. MachineType: LENOVO 20349 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=0f865fdf-a3ef-4fd1-88f3-80f6ca16ef1c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) dmi.bios.date: 02/11/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN37WW(V2.01) dmi.board.asset.tag: 31900058WIN dmi.board.name: Lenovo Y50-70 Touch dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 Touch dmi.modalias: dmi:bvnLENOVO:bvr9ECN37WW(V2.01):bd02/11/2015:svnLENOVO:pn20349:pvrLenovoY50-70Touch:rvnLENOVO:rnLenovoY50-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY50-70Touch: dmi.product.family: IDEAPAD dmi.product.name: 20349 dmi.product.version: Lenovo Y50-70 Touch dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful 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/1725360 Title: Secondary display can not be set Status in xorg package in Ubuntu: New Bug description: The position of the secondary display can not be applied with scales of 200% and 300%. Can be modified with scale of 100% after modified some other configuration like Single Display scale. After set a new position of the secondary display (with 100% scale) is not possible to change the scale maintaining the actual position. Using also Nvidia driver 384.90 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop
[Touch-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
This is still an issue in Ubuntu 17.10 Though it seems to fix if you restart NetworkManager first before connecting to the VPN. sudo service NetworkManager restart -- 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/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Bug description: [Triage Notes] Apparently fixed on Ubuntu 17.04, nobody caring about LTS versions. Please see wall of text on comment 50 for a long excuse. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1688364] Re: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq
make sure you add --dns-loop-detect to the command line in /etc/init.d/dnsmasq (I added a line with 'DNSMASQ_OPTS="$DNSMASQ_OPTS --dns-loop-detect"') or you still get cycling after a non-existent host is queried, just not 100% cpu utilization like when both dnsmasq and resolved are running at the same time. In this case, loop detect actually works though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1688364 Title: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq Status in dnsmasq package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Status in resolvconf package in Ubuntu: New Bug description: May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 To manage notifications about th
Re: [Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs
On 20.10.2017 [07:09:00 -], Jan Gutter wrote: > I concur with option 2), unnecessary deviation will just cause > confusion. Thank you for confirming that! > Regarding the other buffer sizes, the last time I looked they were > mostly OK. The issue reared its head in this particular case because the > netlink message that previously had a pretty constant per-netdev > response size suddenly had the ability to balloon with "no warning". A > number of workarounds exist (i.e. you have to explicitly ask for the VF > info), but, in this case we actually want the VF info and iproute2 was > just unprepared for the size of it. Ok, that's good to hear. > I guess the core issue is that it's entirely possible for the kernel to > add extra netlink attributes to any query response, iproute2 makes the > assumption that the queries it's making is not necessarily going to > explode with gigabytes of new annotations and 16k will easily fit any > current real-world system. A pragmatic approach would probably be to > handle the "Message Truncated" path with a dynamically sized buffer as > an exceptional case. Yep, I can see how iproute2 itself has to move in lockstep with the kernel, which also means older iproute2 that can run on newer kernels needs periodic updates like this one. > Any fix in iproute2 that "properly" addresses this issue has to be > carefully vetted. Who knows how many inherent races will get exposed if > the ip command doubles in execution time. Yep :) I'm fine with eventually doubling the buffer again statically if that is the conclusion upstream reaches. My guess is that is the simplest solution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1720126 Title: [ip link] Message truncated error for large number of passthrough VFs Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Trusty: New Status in iproute2 source package in Xenial: Confirmed Status in iproute2 source package in Zesty: Fix Released Status in iproute2 package in CentOS: Unknown Bug description: [Impact] When querying a Physical Function netdev with a large amount of VF's (more than 30), the resulting return message can overflow the 16K netlink message buffer. This can be fixed by enabling message peeking on the socket and resizing the buffer on receive, or by simply enlarging the receive buffer. Since there's an upper limit to the number of VF's per PF, it's relatively sane to just enlarge the receive buffer. Please see the attached patch. [Test Case] # Set up 60 VF's on an SR-IOV device ip link show > /dev/null Observe the following: Message truncated Message truncated Message truncated [Regression Potential] 1) Applications relying on the broken behaviour will need to be updated, but it would be a really dubious use case. 2) Increasing the rx buffer size increases the memory footprint (but realistically, this is tiny). 3) Extra processing time is now needed to parse the larger buffer, in the case that a call to "ip link" is on the critical time path of an application, (called multiple times in a tight loop, for example), it would affect load. [Other Info] Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04 = Ubuntu16 system stack@cluster04:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial stack@cluster04:~$ uname -r 4.4.0-93-generic stack@cluster04:~$ apt-cache policy iproute2 iproute2: Installed: 4.3.0-1ubuntu3.16.04.1 Version table: *** 4.3.0-1ubuntu3.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages = Ubuntu14 system: root@boomslang:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.3 LTS Release: 14.04 Codename: trusty root@boomslang:~# uname -r 4.4.0-96-generic root@boomslang:~# apt-cache policy iproute2 iproute2: Installed: 3.12.0-2ubuntu1 Version table: *** 3.12.0-2ubuntu1 0 500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs
On 20.10.2017 [07:18:15 -], Jan Gutter wrote: > I had a look at the two proposals and could not spot any obvious > mistakes: > > - the correct upstream git commit has been cherry-picked > - I don't have any objections to attribution or log messages > > Thanks again for shepherding this one through! You're welcome, I'll upload them both today. Thank you and Monique for filing the SRU template properly! -Nish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1720126 Title: [ip link] Message truncated error for large number of passthrough VFs Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Trusty: New Status in iproute2 source package in Xenial: Confirmed Status in iproute2 source package in Zesty: Fix Released Status in iproute2 package in CentOS: Unknown Bug description: [Impact] When querying a Physical Function netdev with a large amount of VF's (more than 30), the resulting return message can overflow the 16K netlink message buffer. This can be fixed by enabling message peeking on the socket and resizing the buffer on receive, or by simply enlarging the receive buffer. Since there's an upper limit to the number of VF's per PF, it's relatively sane to just enlarge the receive buffer. Please see the attached patch. [Test Case] # Set up 60 VF's on an SR-IOV device ip link show > /dev/null Observe the following: Message truncated Message truncated Message truncated [Regression Potential] 1) Applications relying on the broken behaviour will need to be updated, but it would be a really dubious use case. 2) Increasing the rx buffer size increases the memory footprint (but realistically, this is tiny). 3) Extra processing time is now needed to parse the larger buffer, in the case that a call to "ip link" is on the critical time path of an application, (called multiple times in a tight loop, for example), it would affect load. [Other Info] Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04 = Ubuntu16 system stack@cluster04:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial stack@cluster04:~$ uname -r 4.4.0-93-generic stack@cluster04:~$ apt-cache policy iproute2 iproute2: Installed: 4.3.0-1ubuntu3.16.04.1 Version table: *** 4.3.0-1ubuntu3.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages = Ubuntu14 system: root@boomslang:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.3 LTS Release: 14.04 Codename: trusty root@boomslang:~# uname -r 4.4.0-96-generic root@boomslang:~# apt-cache policy iproute2 iproute2: Installed: 3.12.0-2ubuntu1 Version table: *** 3.12.0-2ubuntu1 0 500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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 1628763] Re: Example of Queue from documentation fails
Oops. I did locate the directory on a backup. As you supposed, I had created queue.py initially to do the test. I re-ran it as 'q.py' to see if that helped, but did not delete the original. So you were right -- name conflict. On Fri, Oct 20, 2017 at 8:06 AM, Kevin O'Gorman wrote: > I no longer have the directory in which I did this trial. However, trying > again in an empty directory, the sample works fine with 3.5. > > On Tue, Oct 10, 2017 at 4:14 AM, Serhiy Storchaka < > 1628...@bugs.launchpad.net> wrote: > >> This looks like there is a queue.py file in the current directory which >> hides the queue module from the stdlib. In Python 2.7 this module is >> named Queue and doesn't conflict with a local file queue.py. >> >> Can you confirm Kevin? >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1628763 >> >> Title: >> Example of Queue from documentation fails >> >> Status in python3-defaults package in Ubuntu: >> New >> >> Bug description: >> Reading https://docs.python.org/3.5/library/multiprocessing.html >> #exchanging-objects-between-processes, I have copy-pasted the code >> into a file. Running it with python3 fails thus: >> >> Traceback (most recent call last): >> File "q.py", line 7, in >> q = Queue() >> File "/usr/lib/python3.5/multiprocessing/context.py", line 100, in >> Queue >> from .queues import Queue >> File "/usr/lib/python3.5/multiprocessing/queues.py", line 20, in >> >> from queue import Empty, Full >> ImportError: cannot import name 'Empty' >> >> >> I will attach the actual code file. >> >> ProblemType: Bug >> DistroRelease: Ubuntu 16.04 >> Package: python3 3.5.1-3 >> ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 >> Uname: Linux 4.4.0-34-generic x86_64 >> NonfreeKernelModules: wl >> ApportVersion: 2.20.1-0ubuntu2.1 >> Architecture: amd64 >> CurrentDesktop: XFCE >> Date: Wed Sep 28 20:54:17 2016 >> InstallationDate: Installed on 2016-08-08 (51 days ago) >> InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 >> (20160719) >> SourcePackage: python3-defaults >> UpgradeStatus: No upgrade log present (probably fresh install) >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+ >> bug/1628763/+subscriptions >> > > > > -- > Kevin O'Gorman > #define QUESTION ((bb) || (!bb)) /* Shakespeare */ > > Please consider the environment before printing this email. > -- Kevin O'Gorman #define QUESTION ((bb) || (!bb)) /* Shakespeare */ Please consider the environment before printing this email. ** Attachment added: "unnamed" https://bugs.launchpad.net/bugs/1628763/+attachment/4979135/+files/unnamed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1628763 Title: Example of Queue from documentation fails Status in python3-defaults package in Ubuntu: New Bug description: Reading https://docs.python.org/3.5/library/multiprocessing.html #exchanging-objects-between-processes, I have copy-pasted the code into a file. Running it with python3 fails thus: Traceback (most recent call last): File "q.py", line 7, in q = Queue() File "/usr/lib/python3.5/multiprocessing/context.py", line 100, in Queue from .queues import Queue File "/usr/lib/python3.5/multiprocessing/queues.py", line 20, in from queue import Empty, Full ImportError: cannot import name 'Empty' I will attach the actual code file. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Sep 28 20:54:17 2016 InstallationDate: Installed on 2016-08-08 (51 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1628763/+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 1725333] Re: do-release-upgrade broked WSL
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1725333 Title: do-release-upgrade broked WSL Status in bash package in Ubuntu: New Bug description: I had Ubuntu 17.04 installed in WSL and decided to upgrade it to 17.10, so I had run do-release-upgrade, as I did before to upgrade to 17.04. Everything was fine before script started upgrading packages. It's started from bash updating, and somehow there is a problem revealed that locale files is missing, and locale-gen can't be run (because of bug in WSL). I've tried to install language-pack-en as was suggested, but problem haven't resolved, any attempt to update leads to this error. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: bash 4.4-2ubuntu1.1 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Fri Oct 20 18:03:30 2017 Dmesg: DpkgTerminalLog: Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ... preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. dpkg: error processing archive /var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack): subprocess new pre-installation script was killed by signal (Aborted), core dumped DuplicateSignature: package:bash:4.4-2ubuntu1.1 Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ... preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. dpkg: error processing archive /var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack): subprocess new pre-installation script was killed by signal (Aborted), core dumped ErrorMessage: subprocess new pre-installation script was killed by signal (Aborted), core dumped RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: bash Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new pre-installation script was killed by signal (Aborted), core dumped UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1725333/+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 1725333] [NEW] do-release-upgrade broked WSL
Public bug reported: I had Ubuntu 17.04 installed in WSL and decided to upgrade it to 17.10, so I had run do-release-upgrade, as I did before to upgrade to 17.04. Everything was fine before script started upgrading packages. It's started from bash updating, and somehow there is a problem revealed that locale files is missing, and locale-gen can't be run (because of bug in WSL). I've tried to install language-pack-en as was suggested, but problem haven't resolved, any attempt to update leads to this error. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: bash 4.4-2ubuntu1.1 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Fri Oct 20 18:03:30 2017 Dmesg: DpkgTerminalLog: Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ... preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. dpkg: error processing archive /var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack): subprocess new pre-installation script was killed by signal (Aborted), core dumped DuplicateSignature: package:bash:4.4-2ubuntu1.1 Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ... preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. dpkg: error processing archive /var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack): subprocess new pre-installation script was killed by signal (Aborted), core dumped ErrorMessage: subprocess new pre-installation script was killed by signal (Aborted), core dumped RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: bash Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new pre-installation script was killed by signal (Aborted), core dumped UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1725333 Title: do-release-upgrade broked WSL Status in bash package in Ubuntu: New Bug description: I had Ubuntu 17.04 installed in WSL and decided to upgrade it to 17.10, so I had run do-release-upgrade, as I did before to upgrade to 17.04. Everything was fine before script started upgrading packages. It's started from bash updating, and somehow there is a problem revealed that locale files is missing, and locale-gen can't be run (because of bug in WSL). I've tried to install language-pack-en as was suggested, but problem haven't resolved, any attempt to update leads to this error. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: bash 4.4-2ubuntu1.1 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Fri Oct 20 18:03:30 2017 Dmesg: DpkgTerminalLog: Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ... preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. dpkg: error processing archive /var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack): subprocess new pre-installation script was killed by signal (Aborted), core dumped DuplicateSignature: package:bash:4.4-2ubuntu1.1 Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ... preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. dpkg: error processing archive /var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack): subprocess new pre-installation script was killed by signal (Aborted), core dumped ErrorMessage: subprocess new pre-installation script was killed by signal (Aborted), core dumped RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: bash Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new pre-installation script was killed by signal (Aborted), core dumped UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1725333/+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 1628763] Re: Example of Queue from documentation fails
I no longer have the directory in which I did this trial. However, trying again in an empty directory, the sample works fine with 3.5. On Tue, Oct 10, 2017 at 4:14 AM, Serhiy Storchaka < 1628...@bugs.launchpad.net> wrote: > This looks like there is a queue.py file in the current directory which > hides the queue module from the stdlib. In Python 2.7 this module is > named Queue and doesn't conflict with a local file queue.py. > > Can you confirm Kevin? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1628763 > > Title: > Example of Queue from documentation fails > > Status in python3-defaults package in Ubuntu: > New > > Bug description: > Reading https://docs.python.org/3.5/library/multiprocessing.html > #exchanging-objects-between-processes, I have copy-pasted the code > into a file. Running it with python3 fails thus: > > Traceback (most recent call last): > File "q.py", line 7, in > q = Queue() > File "/usr/lib/python3.5/multiprocessing/context.py", line 100, in > Queue > from .queues import Queue > File "/usr/lib/python3.5/multiprocessing/queues.py", line 20, in > > from queue import Empty, Full > ImportError: cannot import name 'Empty' > > > I will attach the actual code file. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: python3 3.5.1-3 > ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 > Uname: Linux 4.4.0-34-generic x86_64 > NonfreeKernelModules: wl > ApportVersion: 2.20.1-0ubuntu2.1 > Architecture: amd64 > CurrentDesktop: XFCE > Date: Wed Sep 28 20:54:17 2016 > InstallationDate: Installed on 2016-08-08 (51 days ago) > InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > SourcePackage: python3-defaults > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1628763/+ > subscriptions > -- Kevin O'Gorman #define QUESTION ((bb) || (!bb)) /* Shakespeare */ Please consider the environment before printing this email. ** Attachment added: "unnamed" https://bugs.launchpad.net/bugs/1628763/+attachment/4979094/+files/unnamed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1628763 Title: Example of Queue from documentation fails Status in python3-defaults package in Ubuntu: New Bug description: Reading https://docs.python.org/3.5/library/multiprocessing.html #exchanging-objects-between-processes, I have copy-pasted the code into a file. Running it with python3 fails thus: Traceback (most recent call last): File "q.py", line 7, in q = Queue() File "/usr/lib/python3.5/multiprocessing/context.py", line 100, in Queue from .queues import Queue File "/usr/lib/python3.5/multiprocessing/queues.py", line 20, in from queue import Empty, Full ImportError: cannot import name 'Empty' I will attach the actual code file. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Sep 28 20:54:17 2016 InstallationDate: Installed on 2016-08-08 (51 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: python3-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1628763/+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 1702794] Re: Automatically switch audio devices on connection
Seems this change now also result in: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720519 causing pulseaudio to fail to load on Kubuntu -- 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/1702794 Title: Automatically switch audio devices on connection Status in pulseaudio package in Ubuntu: Fix Released Bug description: This way once a user pairs & connects a bluetooth speaker device pulseaudio will auto switch to it. As it stands now users have to open sound settings & switch manually. It's bad enough that auto discover & connect don't work, (can be scripted thru bluetoothctl), no sense adding to frustration In the ### Automatically load driver modules for Bluetooth hardware section .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.3 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doug 1843 F pulseaudio /dev/snd/controlC0: doug 1843 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 6 20:02:15 2017 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2017-07-04T13:42:27.651527 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1702794/+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 1671952] Re: python program gets segmentation fault
I don't think I can do that. All signs point to a problem that is directly related to the size of the journal. You don't want my 100GB database, and I don't want to fool around finding a script that creates one from scratch hoping it will trigger the same problem. If you can't work from a core dump, it's going to be hard to solve this. On Tue, Oct 10, 2017 at 4:20 AM, Serhiy Storchaka < 1671...@bugs.launchpad.net> wrote: > Please file a bug on the Python bug tracker (https://bugs.python.org/) > and provide a minimal script that reproduces a crash. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1671952 > > Title: > python program gets segmentation fault > > Status in python3-defaults package in Ubuntu: > New > > Bug description: > Running a Python 3 / sqlite3 script that develops a database > representing a game tree, a segmentation fault occurred. > > The program had written 4,910,495 lines of output when it crashed, > redirected to a file. It > appears normal, and its size is about right for the job being > performed. There's nothing > suspicious at the end. > > This is a hobby project, so I can share the entire database and any of > the code you need, but much of it is included in the screen-scraped console > session attached herewith. In particular: > - the command-line > - a gdb stack backtrace of the core dump > - the program being run > - a run of the sqlite3 "pragma integrity_check" that shows the database > is sound > - database .schema output > > CPU is Core i-7, 32 GB RAM. > Code is recursive, but limited by the nature of the problem and > parameters to depth of about 10 calls. Code has been used before, albeit > on a problem with smaller recursive depth and shorter > expected run-time. > db is 18GB on a 12TB RAID partition; plenty of space > kernel is X86-64 4.4.0-66-generic un-fooled-around-with > Python and the sqlite3 package is 3.5.2, straight from the repositories > > I have a backup of the database right after this crash (being > performed as I write this) > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: python3 3.5.1-3 > ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 > Uname: Linux 4.4.0-66-generic x86_64 > NonfreeKernelModules: wl > ApportVersion: 2.20.1-0ubuntu2.5 > Architecture: amd64 > CurrentDesktop: XFCE > Date: Fri Mar 10 13:47:54 2017 > InstallationDate: Installed on 2016-08-08 (214 days ago) > InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > SourcePackage: python3-defaults > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1671952/+ > subscriptions > -- Kevin O'Gorman #define QUESTION ((bb) || (!bb)) /* Shakespeare */ Please consider the environment before printing this email. ** Attachment added: "unnamed" https://bugs.launchpad.net/bugs/1671952/+attachment/4979055/+files/unnamed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1671952 Title: python program gets segmentation fault Status in python3-defaults package in Ubuntu: New Bug description: Running a Python 3 / sqlite3 script that develops a database representing a game tree, a segmentation fault occurred. The program had written 4,910,495 lines of output when it crashed, redirected to a file. It appears normal, and its size is about right for the job being performed. There's nothing suspicious at the end. This is a hobby project, so I can share the entire database and any of the code you need, but much of it is included in the screen-scraped console session attached herewith. In particular: - the command-line - a gdb stack backtrace of the core dump - the program being run - a run of the sqlite3 "pragma integrity_check" that shows the database is sound - database .schema output CPU is Core i-7, 32 GB RAM. Code is recursive, but limited by the nature of the problem and parameters to depth of about 10 calls. Code has been used before, albeit on a problem with smaller recursive depth and shorter expected run-time. db is 18GB on a 12TB RAID partition; plenty of space kernel is X86-64 4.4.0-66-generic un-fooled-around-with Python and the sqlite3 package is 3.5.2, straight from the repositories I have a backup of the database right after this crash (being performed as I write this) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 10 13:47:54 2
[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
Possibly introduced by: https://launchpad.net/ubuntu/+source/pulseaudio/1:10.0-2ubuntu1 * Enable modules that needn't be disabled: - module-role-cork: Now enabled per upstream defaults (LP: #1701688) - module-switch-on-connect: Enabled for seamless hotplugging (LP: #1702794) -- 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/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+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 1688364] Re: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq
I found this workaround (lets you use dnsmasq with NetworkManager instead of reloved and dnsmasq together https://askubuntu.com/questions/898605/how-to-disable-systemd-resolved- and-resolve-dns-with-dnsmasq/899338 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1688364 Title: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq Status in dnsmasq package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Status in resolvconf package in Ubuntu: New Bug description: May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 127.0.0.53 May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com from 127.0.0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1688364/+subscriptions -- Mailing list: https://launchpad.net/~touch-pack
[Touch-packages] [Bug 1725304] Re: package colord 1.3.3-2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1725304 Title: package colord 1.3.3-2 failed to install/upgrade: subprocess new pre- removal script returned error exit status 127 Status in colord package in Ubuntu: New Bug description: when I was updating the ubuntu 17.04 to 17.10 this error was lanched ProblemType: Package DistroRelease: Ubuntu 17.10 Package: colord 1.3.3-2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 08:44:49 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 127 InstallationDate: Installed on 2017-09-29 (20 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: colord Title: package colord 1.3.3-2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1725304/+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 1725304] [NEW] package colord 1.3.3-2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127
Public bug reported: when I was updating the ubuntu 17.04 to 17.10 this error was lanched ProblemType: Package DistroRelease: Ubuntu 17.10 Package: colord 1.3.3-2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 08:44:49 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 127 InstallationDate: Installed on 2017-09-29 (20 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: colord Title: package colord 1.3.3-2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) ** Affects: colord (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1725304 Title: package colord 1.3.3-2 failed to install/upgrade: subprocess new pre- removal script returned error exit status 127 Status in colord package in Ubuntu: New Bug description: when I was updating the ubuntu 17.04 to 17.10 this error was lanched ProblemType: Package DistroRelease: Ubuntu 17.10 Package: colord 1.3.3-2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 08:44:49 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 127 InstallationDate: Installed on 2017-09-29 (20 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: colord Title: package colord 1.3.3-2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1725304/+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 1725295] [NEW] intel graphics G41 not loaded - ubuntu 17.10
Public bug reported: i installed Ubuntu 17.10...although live cd recognized my intel Graphics g41...after i install system on my pc hard disk...the g41 is not recgnized at all leading to very slow and laggy system. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 16:44:45 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Gigabyte Technology Co., Ltd. G41M-ES2L ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=9567769a-462e-45a3-ba49-c4a12bf24b16 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6 dmi.board.name: G41M-ES2L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd11/04/2009:svnGigabyteTechnologyCo.,Ltd.:pnG41M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-ES2L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41M-ES2L dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu wayland-session -- 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/1725295 Title: intel graphics G41 not loaded - ubuntu 17.10 Status in xorg package in Ubuntu: New Bug description: i installed Ubuntu 17.10...although live cd recognized my intel Graphics g41...after i install system on my pc hard disk...the g41 is not recgnized at all leading to very slow and laggy system. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 16:44:45 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Gigabyte Technology Co., Ltd. G41M-ES2L ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=9567769a-462e-45a3-ba49-c4a12bf24b16 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6 dmi.board.name: G41M-ES2L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd11/04/2009:svnGigabyteTechnologyCo.,Ltd.:pnG41M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-ES2L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41M-ES2L dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xor
[Touch-packages] [Bug 1716009] Re: problem with the sound since the latest update
the problem is still there to date - may the proposed update resolve it -- 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/1716009 Title: problem with the sound since the latest update Status in alsa-driver package in Ubuntu: New Bug description: i am with an old intel chipset motherboard having an integrated realtek alc888 sound, and Ubuntu 16.04 Desktop (64-bit); since the latest update there has had no effect when adjusting sound volume from the sound menu on the menu bar and sound settings, and no sound in counter strike 1.6 linux version, also, there has appeared an effect of a sound interruption/break (for less than a second) when switching between applications, however, i can still adjust the sound volume from gnome alsa mixer the latest update includes: snapd-login-service:amd64 libsnapd-glib1:amd64 linux-firmware:amd64 libgd3:amd64 the previous ——: libpackagekit-glib2-16:amd64 gir1.2-packagekitglib-1.0:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716009/+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 1725272] Re: systemd-logind crashed with SIGABRT in log_assert_failed_realm()
*** This bug is a duplicate of bug 1710498 *** https://bugs.launchpad.net/bugs/1710498 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 #1710498, 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/1725272/+attachment/4978703/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725272/+attachment/4978706/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725272/+attachment/4978712/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725272/+attachment/4978714/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725272/+attachment/4978715/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725272/+attachment/4978716/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725272/+attachment/4978717/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1710498 ** 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1725272 Title: systemd-logind crashed with SIGABRT in log_assert_failed_realm() Status in systemd package in Ubuntu: New Bug description: Crash occurred directly after logging in to Gnome session, leaving me on a blank screen for a few seconds, instead of transitioning to the new session. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy systemd systemd: Installed: 234-2ubuntu12 Candidate: 234-2ubuntu12 Version table: *** 234-2ubuntu12 500 500 http://ubuntu.mirror.ac.za/ubuntu artful/main amd64 Packages 500 http://za.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 14:18:33 2017 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5f7 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Nitro AN515-51 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: LANG=en_ZA.UTF-8 LANGUAGE=en_ZA:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=1e48054c-efc5-405b-bcda-4ec7d337b28c ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: log_assert_failed_realm () from /lib/systemd/libsystemd-shared-234.so close_nointr () from /lib/systemd/libsystemd-shared-234.so ?? () ?? () ?? () SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-logind crashed with SIGABRT in log_assert_failed_realm() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 08/22/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_KLS dmi.board.vendor: KBL dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd08/22/2017:svnAcer:pnNitroAN515-51:pvrV1.10:rvnKBL:rnFreed_KLS:rvrV1.10:cvnAcer:ct10:cvrV1.10: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-51 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages P
[Touch-packages] [Bug 1725263] [NEW] screen freezing
Public bug reported: my screen is freezing after some minutes. I have no idea what the problem could be. This Problem does also exist at other BS like windows. So I guess this is a HW problem, but what hardware could cause this problem? Any idea? with kind regards, Gustav ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 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: Fri Oct 20 13:58:37 2017 DistUpgraded: 2017-01-01 17:43:39,218 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:130f] (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Kaveri [Radeon R7 Graphics] [1019:9a18] InstallationDate: Installed on 2016-06-22 (484 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: MEDION D3F3-EM ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic root=UUID=3ec08b5b-6ced-472a-91eb-d3df3b1cfe0b ro nopat vesafb.invalid=1 drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-01-01 (291 days ago) dmi.bios.date: 06/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: D3EMW08.106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: D3F3-EM dmi.board.vendor: MEDION dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDION dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrD3EMW08.106:bd06/09/2014:svnMEDION:pnD3F3-EM:pvr1.0:rvnMEDION:rnD3F3-EM:rvr1.0:cvnMEDION:ct3:cvr: dmi.product.name: D3F3-EM dmi.product.version: 1.0 dmi.sys.vendor: MEDION version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Oct 20 15:57:27 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputDell Dell USB Keyboard KEYBOARD, id 9 inputLogitech USB Optical Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1725263 Title: screen freezing Status in xorg package in Ubuntu: New Bug description: my screen is freezing after some minutes. I have no idea what the problem could be. This Problem does also exist at other BS like windows. So I guess this is a HW problem, but what hardware could cause this problem? Any idea? with kind regards, Gustav ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 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: Fri Oct 20 13:58:37 2017 DistUpgraded: 2017-01-01 17:43:39,218 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:130f] (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Kaveri [Radeon R7 Graphics] [1019:9a18] InstallationDate: Installed on 2016-06-22 (484 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: MEDION D3F3-EM ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, no
[Touch-packages] [Bug 1454450] Re: Bluetooth mouse laggy and erratic
I have a feeling that this is related to bluetooth and wifi coexistence. https://wireless.wiki.kernel.org/en/users/Drivers/iwlwifi#wi- fibluetooth_coexistence In essence, bleutooth and wifi operate on similar (the same) frequencies and will interfere. Normally this is handled in the firmware/kernel, but there are problems. Try this: https://wiki.debian.org/iwlwifi#Troubleshooting -- 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/1454450 Title: Bluetooth mouse laggy and erratic Status in bluez package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves erratically (laggy, jumpy). The problem happens after a few (sometimes one) suspend and resume. I am attaching below some info on my system. Thank you. cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux 02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03) Subsystem: Dell Device [1028:0019] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8001 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:216f Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [2.174367] Bluetooth: Core ver 2.20 [2.174669] Bluetooth: HCI device and connection manager initialized [2.174792] Bluetooth: HCI socket layer initialized [2.174795] Bluetooth: L2CAP socket layer initialized [2.175449] Bluetooth: SCO socket layer initialized [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [3.542421] Bluetooth: BNEP filters: protocol multicast [3.542425] Bluetooth: BNEP socket layer initialized [3.551641] Bluetooth: RFCOMM TTY layer initialized [3.551649] Bluetooth: RFCOMM socket layer initialized [3.551654] Bluetooth: RFCOMM ver 1.11 [ 26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 26.569287] Bluetooth: HIDP socket layer initialized [ 26.576971] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15 [ 26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 72.448281] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16 [ 72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 2994.842547] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17 [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 lmp_ver=06 lmp_subver=220e [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [ 3811.777260] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20 [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option usb_wwan usbserial usbnet mii uas usb_storage hid_generic hidp nvram msr binfmt_misc rfcomm bnep nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal dell_wmi sparse_keymap intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul dell_laptop dcdbas btusb crc32_pclmul bluetooth ghash_clmulni_intel hid_multitouch aesni_intel aes_x86_64 lrw uvcvideo gf128mul videobuf2_vmalloc glue_helper wl(POE) videobuf2_memops ablk_helper videobuf2_core cryptd v4l2_common videodev media joydev i915_bpo serio_raw i915 dell_led rtsx_pci_ms intel_ips memstick snd_hda_codec_realtek snd_soc_rt286 snd_hda_codec_generic cfg80211 snd_soc_core drm_kms_helper mei_me lpc_ich shpchp mei snd_compress snd_hda_intel
[Touch-packages] [Bug 1334916] Re: sshd-ConsoleKit integration patch causes abrupt termination of multichannel sessions
I can confirm the existence of the problem. Occured with Ansible on Ubuntu 16.04.3 LTS (with Ansible 2.4.0.0-1ppa~xenial). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1334916 Title: sshd-ConsoleKit integration patch causes abrupt termination of multichannel sessions Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Trusty: Triaged Bug description: Attached to this report is a small app the reproduces the issue by creating multiple channels within one sessions. (I fist hit this issue using JSCH library) Following information is printed to stdout if sshd is launched with -d flags (I've modified the sshd code to print PIDs next to debug level): debug3(7526): monitor_read: checking request 156 debug3(7526): mm_answer_consolekit_register entering debug1(7526): session_by_tty: session 0 tty /dev/pts/1 debug1(7573): server_input_channel_req: channel 2 request pty-req reply 1 debug1(7573): session_by_channel: session 2 channel 2 debug1(7573): session_input_channel_req: session 2 req pty-req debug1(7573): Allocating pty. debug3(7573): mm_request_send entering: type 28 debug3(7573): mm_pty_allocate: waiting for MONITOR_ANS_PTY debug3(7573): mm_request_receive_expect entering: type 29 debug3(7573): mm_request_receive entering debug1(7526): Unable to open session: The name org.freedesktop.ConsoleKit was not provided by any .service files debug3(7526): mm_request_send entering: type 157 debug3(7526): mm_request_receive entering debug3(7526): monitor_read: checking request 28 debug3(7526): mm_answer_pty entering debug2(7526): session_new: allocate (allocated 2 max 10) debug3(7526): session_unused: session id 2 unused debug1(7526): session_new: session 2 mm_request_receive_expect: read: rtype 157 != type 29 From the log, it looks as if two processes use the same set of pipes to communicate to the monitor, one of them is sending MONITOR_REQ_CONSOLEKIT_REGISTER, while another MONITOR_REQ_PTY, and because they use same set of pipes, and because both processes use same pipe FDs, monitor reply is sometimes delivered to the wrong process. I can reproduce the failure 90% of time using attached app, which expects first argument to be host name, second - login and the third - password, that are defaulted to ubuntu:ubuntu@localhost: $ ./ssh-multisession Connecting to localhost...Done! Authenticating as ubuntu...Done. Starting channel 0 Starting channel 1 ssh_channel_request_pty()=-1: Socket error: disconnected Starting channel 2 ssh_channel_open_session()=-1: Writing packet: error on socket (or connection closed): Operation now in progress Starting channel 3 The same script works fine if sshd is compiled without consolekit.patch: ./ssh-multisession debian-host debian debian Connecting to 172.17.162.237...Done! Authenticating as debian...Done. Starting channel 0 Starting channel 1 Starting channel 2 Starting channel 3 Starting channel 4 Starting channel 5 Starting channel 6 Starting channel 7 Starting channel 8 Starting channel 9 P.S. To compile a test app one needs to have libssh-dev package installed on your system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1334916/+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 1725247] Re: apport-gtk crashed with SIGSEGV
*** This bug is a duplicate of bug 1552577 *** https://bugs.launchpad.net/bugs/1552577 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 #1552577, 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/1725247/+attachment/4978494/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725247/+attachment/4978496/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725247/+attachment/4978500/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725247/+attachment/4978501/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725247/+attachment/4978502/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725247/+attachment/4978503/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725247/+attachment/4978504/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1552577 apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) ** 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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1725247 Title: apport-gtk crashed with SIGSEGV Status in apport package in Ubuntu: New Bug description: Logged into Ubuntu 17.10 after upgrading. Received this messages right away. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: apport-gtk 2.20.7-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashReports: 640:1000:118:7071255:2017-10-20 11:58:57.119010448 +0200:2017-10-20 11:58:58.119010448 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash 664:1000:118:0:2017-10-20 13:27:44.683255171 +0200:2017-10-20 13:27:44.683255171 +0200:/var/crash/_usr_share_skypeforlinux_skypeforlinux.1000.upload 640:1000:118:1761472:2017-10-20 13:27:43.595255851 +0200:2017-10-20 13:27:44.595255851 +0200:/var/crash/_usr_share_skypeforlinux_skypeforlinux.1000.crash CurrentDesktop: Unity:Unity7 Date: Fri Oct 20 11:58:52 2017 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2016-02-13 (615 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7f108a1120a9:mov(%rbx),%rdi PC (0x7f108a1120a9) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1725247/+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 1725251] Re: package cups-daemon 2.2.2-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1725251 Title: package cups-daemon 2.2.2-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: I ran sudo apt --fix-broken install because my fuse wasn't working and when Restarted i got these errors with cups ProblemType: Package DistroRelease: Ubuntu 17.04 Package: cups-daemon 2.2.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CupsErrorLog: E [20/Oct/2017:11:49:33 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. E [20/Oct/2017:12:20:03 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. W [20/Oct/2017:12:20:29 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Dell-MFP-Laser-3115cn-Gray..\' already exists W [20/Oct/2017:12:20:29 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Dell-MFP-Laser-3115cn-RGB..\' already exists E [20/Oct/2017:12:30:56 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. Date: Wed Oct 18 17:15:12 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-01-04 (1384 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) Lpstat: device for Canon-MP220-series: usb://Canon/MP220%20series?serial=B0CF72&interface=1 device for Dell-MFP-Laser-3115cn: usb://Dell/MFP%20Laser%203115cn?serial=0927165472&interface=1 device for HP-Officejet-6700: hp:/net/Officejet_6700?zc=HP10604B4F9713 MachineType: Dell Inc. Studio 1555 Papersize: a4 PpdFiles: Dell-MFP-Laser-3115cn: Generic PostScript Printer HP-Officejet-6700: HP Officejet 6700, hpcups 3.16.3 Canon-MP220-series: Canon MP220 series - CUPS+Gutenprint v5.2.11 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic root=UUID=af6c06a0-fc5c-4e17-8c90-0c80d9182578 ro resume=UUID=471b7201-0278-487d-91c6-426e479fdd5f quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic root=UUID=af6c06a0-fc5c-4e17-8c90-0c80d9182578 ro resume=UUID=471b7201-0278-487d-91c6-426e479fdd5f quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: cups Title: package cups-daemon 2.2.2-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to zesty on 2017-08-09 (72 days ago) dmi.bios.date: 04/23/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0C234M dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/23/2009:svnDellInc.:pnStudio1555:pvrA06:rvnDellInc.:rn0C234M:rvrA06:cvnDellInc.:ct8:cvrA06: dmi.product.name: Studio 1555 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.cups: # Cups configure options # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf # LOAD_LP_MODULE=yes mtime.conffile..etc.default.cups: 2014-08-14T15:22:10.720387 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1725251/+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 1725251] [NEW] package cups-daemon 2.2.2-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: I ran sudo apt --fix-broken install because my fuse wasn't working and when Restarted i got these errors with cups ProblemType: Package DistroRelease: Ubuntu 17.04 Package: cups-daemon 2.2.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CupsErrorLog: E [20/Oct/2017:11:49:33 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. E [20/Oct/2017:12:20:03 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. W [20/Oct/2017:12:20:29 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Dell-MFP-Laser-3115cn-Gray..\' already exists W [20/Oct/2017:12:20:29 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Dell-MFP-Laser-3115cn-RGB..\' already exists E [20/Oct/2017:12:30:56 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. Date: Wed Oct 18 17:15:12 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-01-04 (1384 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) Lpstat: device for Canon-MP220-series: usb://Canon/MP220%20series?serial=B0CF72&interface=1 device for Dell-MFP-Laser-3115cn: usb://Dell/MFP%20Laser%203115cn?serial=0927165472&interface=1 device for HP-Officejet-6700: hp:/net/Officejet_6700?zc=HP10604B4F9713 MachineType: Dell Inc. Studio 1555 Papersize: a4 PpdFiles: Dell-MFP-Laser-3115cn: Generic PostScript Printer HP-Officejet-6700: HP Officejet 6700, hpcups 3.16.3 Canon-MP220-series: Canon MP220 series - CUPS+Gutenprint v5.2.11 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic root=UUID=af6c06a0-fc5c-4e17-8c90-0c80d9182578 ro resume=UUID=471b7201-0278-487d-91c6-426e479fdd5f quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic root=UUID=af6c06a0-fc5c-4e17-8c90-0c80d9182578 ro resume=UUID=471b7201-0278-487d-91c6-426e479fdd5f quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: cups Title: package cups-daemon 2.2.2-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to zesty on 2017-08-09 (72 days ago) dmi.bios.date: 04/23/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0C234M dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/23/2009:svnDellInc.:pnStudio1555:pvrA06:rvnDellInc.:rn0C234M:rvrA06:cvnDellInc.:ct8:cvrA06: dmi.product.name: Studio 1555 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.cups: # Cups configure options # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf # LOAD_LP_MODULE=yes mtime.conffile..etc.default.cups: 2014-08-14T15:22:10.720387 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages zesty -- 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/1725251 Title: package cups-daemon 2.2.2-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: I ran sudo apt --fix-broken install because my fuse wasn't working and when Restarted i got these errors with cups ProblemType: Package DistroRelease: Ubuntu 17.04 Package: cups-daemon 2.2.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CupsErrorLog: E [20/Oct/2017:11:49:33 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. E [20/Oct/2017:12:20:03 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. W [20/Oct/2017:12:20:29 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Dell-MFP-Laser-3115cn-Gray..\' already exists W [20/Oct/2017:12:20:29 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Dell-MFP-Laser-3115cn-RGB..\' already exists E [20/Oct/2017:12:30:56 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. Date: Wed Oct 18 17:15:12 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-01-04 (1384 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) Lpstat: device for Canon-MP220-series: usb://Canon/MP220%20series?serial=B0CF7
[Touch-packages] [Bug 1718869] Re: Migrate to hunspell-en-us in libreoffice-dictionaries
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879199 ** Bug watch added: Debian Bug tracker #879199 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879199 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hunspell-en-us in Ubuntu. https://bugs.launchpad.net/bugs/1718869 Title: Migrate to hunspell-en-us in libreoffice-dictionaries Status in hunspell-en-us package in Ubuntu: New Status in libreoffice-dictionaries package in Ubuntu: New Status in hunspell-en-us package in Debian: New Status in libreoffice-dictionaries package in Debian: Won't Fix Bug description: libreoffice-dictionaries upstream ships hunspell-en-us, which is properly maintained and is newer than the one currently in Debian and Ubuntu (20070829-6ubuntu3). Please consider migrating to the one in libreoffice-dictionaries. The other English variants (British, Australian and others) are already provided by libreoffice- dictionaries and are more up-to-date than the US variant. Debian bugs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874519 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795159 Inside the source of libreoffice-dictionaries in Debian, I can find en_US.aff and en_US.dic but there is not a built package for them. https://sources.debian.net/src/libreoffice-dictionaries/1:5.2.5-1/dictionaries/en/ See this README from the Libreoffice/dictionaries git, https://cgit.freedesktop.org/libreoffice/dictionaries/tree/en/README_en_US.txt It seems that this is now dead, https://sourceforge.net/projects/hunspell/files/Spelling%20dictionaries/en_US/ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hunspell-en-us 20070829-6ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 09:43:32 2017 InstallationDate: Installed on 2017-09-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) PackageArchitecture: all SourcePackage: hunspell-en-us UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hunspell-en-us/+bug/1718869/+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 1725133] Re: Window buttons don't have paddings
** Package changed: ubuntu => ubuntu-themes (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1725133 Title: Window buttons don't have paddings Status in ubuntu-themes package in Ubuntu: New Bug description: Window buttons don't have paddings in the Ambiance GNOME theme of Ubuntu 17.10. The Chrome window has such buttons for example. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1725133/+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 1725133] [NEW] Window buttons don't have paddings
You have been subscribed to a public bug: Window buttons don't have paddings in the Ambiance GNOME theme of Ubuntu 17.10. The Chrome window has such buttons for example. Screenshot attached. ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: artful -- Window buttons don't have paddings https://bugs.launchpad.net/bugs/1725133 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes 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 1725220] Re: packagekitd crashed with SIGSEGV in gst_mini_object_unref()
*** This bug is a duplicate of bug 1720694 *** https://bugs.launchpad.net/bugs/1720694 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 #1720694, 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/1725220/+attachment/4978274/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1725220/+attachment/4978276/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1725220/+attachment/4978280/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1725220/+attachment/4978281/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1725220/+attachment/4978282/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1725220/+attachment/4978283/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1725220/+attachment/4978284/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1720694 ** 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 packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1725220 Title: packagekitd crashed with SIGSEGV in gst_mini_object_unref() Status in packagekit package in Ubuntu: New Bug description: crash in the background, working on Eclipse IDE in the foreground, not sure if it's related though. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: packagekit 1.1.7-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 12:10:55 2017 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/lib/packagekit/packagekitd SegvAnalysis: Segfault happened at: 0x7f69413466e0 : mov 0x8(%rbx),%edi PC (0x7f69413466e0) ok source "0x8(%rbx)" (0x2a413236313038) not located in a known VMA region (needed readable region)! destination "%edi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: packagekit StacktraceTop: gst_mini_object_unref () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 GstMatcher::~GstMatcher() () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so AptIntf::providesCodec(PkgList&, char**) () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so ?? () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so ?? () Title: packagekitd crashed with SIGSEGV in gst_mini_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1725220/+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 803824] Re: Can't change the gtkfilechooser view
** Changed in: gtk Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/803824 Title: Can't change the gtkfilechooser view Status in GTK+: In Progress Status in gtk+3.0 package in Ubuntu: Triaged Bug description: When using File open in an application the Nautilus File Dialog shows up. It has severe shortcomings (see attached screenshot): (1) Hidden files show or don't show based on the selection made in Nautilus earlier. No UI (e.g. at (2)) is provided to toggle (Ctrl+H seems to work) (3) display is always in detail mode Ctrl1-3 or Ctlr+- to alter the display don't work. Show/Hide hidden files is available through keyboard shortcuts or rightclick, so a UI element is a nice-to-have. The lack of display settings (e.g. specify columns like in the main window) like icons/list/details is a usability issue. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/803824/+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 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.
sounds good, if we just use latest modemmanager, it will be easier to apply further fix in the future. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1693756 Title: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication. Status in ModemManager: New Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in modemmanager package in Ubuntu: Confirmed Bug description: # issue: * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 1.4.12-1ubuntu1 on xenial. - but works well on on Yakkety. # investgation: * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried install followed packages from Yakkety ppa on Xenial and wwan card works on 1st boot but failed after 2nd boot sometimes. - libmbim-glib4_1.14.0-1_amd64.deb - libmbim-glib-dev_1.14.0-1_amd64.deb - libmbim-proxy_1.14.0-1_amd64.deb - libmbim-utils_1.14.0-1_amd64.deb - libqmi-glib5_1.16.0-1_amd64.deb - libqmi-proxy_1.16.0-1_amd64.deb * different from ModemManager --debug - In passed case, it received message from /dev/cdc-wdm1 after send "Read max control message size from descriptors file: 4096" , but not happens to failed case. So, it prints "[mm-port-probe.c:261] mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in failed case. - passed case: http://paste.ubuntu.com/24664908/ - failed case: http://paste.ubuntu.com/24664910/ # Plan: * let the newer version packages could also works well on Xenial. * find out needed patches on newer version packages. * packport needed patches to older version packages on Xenial. # environment information: * modinfo cdc_mbim for original kernel module: http://paste.ubuntu.com/24662359/ - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 4.4.0 and yakkety kernel 4.8.0. * uname -r: 4.4.0-73-generic * lsusb -v: http://paste.ubuntu.com/24662332/ FCC authentication reference: * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html * https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704 To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1693756/+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 1686189] Re: External monitor connecting problem on Intel graphics card
Thanks for your testing. The blank screen issue was always there, right? I think use modesetting driver instead of intel DDX should fix the issue. You can either use xorg.config or "apt purge xserver-xorg-video-intel" to switch to modesetting driver. -- 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/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+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