[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Uncommenting "WaylandEnable=false " worked. Removing gdm3 did not work, I just got redirected to a tty3 login shell. Thanks again -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
I just tested this. It worked for me as well. Thanks, Nebojša. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799038] Re: Ubuntu 18.10 does not suspend on lid close
Please compare "/sys/kernel/debug/wakeup_sources" before/after suspend. -- 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/1799038 Title: Ubuntu 18.10 does not suspend on lid close Status in systemd package in Ubuntu: New Bug description: After an upgrade to Ubuntu 18.10 suspend to RAM due to closing the lid on notebooks does not work any more. The machine goes to suspend mode but wakes up immediately due to some events (can be network, or others). In 18.04 this issue was fixed (we had the same situation with any version since 14.04). Seems a regression. Mitigation reports suggesting to change /etc/systemd/logind.conf are WRONG. The changes do NOTHING. One might spare the time to experiment. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 11:55:48 2018 InstallationDate: Installed on 2018-04-30 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.systemd.logind.conf: 2018-10-20T22:01:57.469491 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799038/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799844] Re: dose not work rite
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1799844 Title: dose not work rite Status in Ubuntu: Incomplete Bug description: WILL NOT UNINSTAL ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Oct 24 19:59:39 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:fde0] Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:fde0] InstallationDate: Installed on 2018-03-07 (231 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: TOSHIBA Satellite C655 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=61e48a6a-7e5a-4c7e-aa64-e126e56af5b5 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.70 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.70:bd07/07/2011:svnTOSHIBA:pnSatelliteC655:pvrPSC08U-03C01K:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Satellite C655 dmi.product.sku: Montevina_Fab dmi.product.version: PSC08U-03C01K dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 xserver.bootTime: Sat Mar 17 11:24:42 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5760 vendor CMO xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1799844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720698] Re: Different height for headerbar in one app
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: ubuntu-themes Status: Confirmed => Won't Fix ** Changed in: ubuntu-themes (Ubuntu) Status: Confirmed => Won't Fix -- 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/1720698 Title: Different height for headerbar in one app Status in Ubuntu theme: Won't Fix Status in ubuntu-themes package in Ubuntu: Won't Fix Bug description: Ubuntu 17.10 Beta running live from USB I admit I have no idea how that "top bar" decoration of windows is called. Is it "tittle bar" or "tool bar"? Anyway I'm talking about that dark part with minimize and close buttons on it. I noticed the height of that bar is different if there's no additional buttons and different if there is an extra button or two. For example in the Settings app go to Details and switch between Users and Default Application tabs. When you're in Users tab you will see Add User button in the top bar. There's no button in the top bar of Default Application. When you switch between those two tabs you will notice that the top bar for Users tab has bigger height. And that gives visually unpleasant effect of interface jumping up and down when switching tabs. Short video attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1720698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799625] Re: Enable journald support
** Bug watch added: Red Hat Bugzilla #1315239 https://bugzilla.redhat.com/show_bug.cgi?id=1315239 ** Also affects: fedora via https://bugzilla.redhat.com/show_bug.cgi?id=1315239 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1799625 Title: Enable journald support Status in qtbase-opensource-src package in Ubuntu: New Status in qtbase-opensource-src package in Debian: Unknown Status in Fedora: Unknown Bug description: ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1799625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799869] [NEW] ubuntu-bug (a.k.a. apport-bug) not working in Xubuntu
Public bug reported: Sorry for using Ubuntu to report an Xubuntu bug, but the problem is exactly that bug reporting is not working for me in Xubuntu. When I tried to create what eventually became bug 1799868 here on Xubuntu, as soon as the web browser (Chrome) came up, it waas reporting a problem in Launchpad ad said it would soon be fixed. After a week, I tried the same thing on Ubnutu and reported the bug there a few minutes ago. It fails the same way on both ubuntu-bug apport ubutnu-bug coreutils I'm sure there's info you want about the failing system: at least including - Xubuntu 18.04.1, 64-bit all up-to-date Core i7 32GB RAM If there's anything else, let me know. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.4 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 24 20:38:19 2018 PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-08-19 (66 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2017-05-02T14:12:29.908000 ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1799869 Title: ubuntu-bug (a.k.a. apport-bug) not working in Xubuntu Status in apport package in Ubuntu: New Bug description: Sorry for using Ubuntu to report an Xubuntu bug, but the problem is exactly that bug reporting is not working for me in Xubuntu. When I tried to create what eventually became bug 1799868 here on Xubuntu, as soon as the web browser (Chrome) came up, it waas reporting a problem in Launchpad ad said it would soon be fixed. After a week, I tried the same thing on Ubnutu and reported the bug there a few minutes ago. It fails the same way on both ubuntu-bug apport ubutnu-bug coreutils I'm sure there's info you want about the failing system: at least including - Xubuntu 18.04.1, 64-bit all up-to-date Core i7 32GB RAM If there's anything else, let me know. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.4 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 24 20:38:19 2018 PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-08-19 (66 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2017-05-02T14:12:29.908000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1799869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799869] Re: ubuntu-bug (a.k.a. apport-bug) not working in Xubuntu
This very likely seems like a Launchpad problem, not an apport problem. Do you recall the exact text used? ** Changed in: apport (Ubuntu) Status: New => Incomplete -- 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/1799869 Title: ubuntu-bug (a.k.a. apport-bug) not working in Xubuntu Status in apport package in Ubuntu: Incomplete Bug description: Sorry for using Ubuntu to report an Xubuntu bug, but the problem is exactly that bug reporting is not working for me in Xubuntu. When I tried to create what eventually became bug 1799868 here on Xubuntu, as soon as the web browser (Chrome) came up, it waas reporting a problem in Launchpad ad said it would soon be fixed. After a week, I tried the same thing on Ubnutu and reported the bug there a few minutes ago. It fails the same way on both ubuntu-bug apport ubutnu-bug coreutils I'm sure there's info you want about the failing system: at least including - Xubuntu 18.04.1, 64-bit all up-to-date Core i7 32GB RAM If there's anything else, let me know. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.4 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 24 20:38:19 2018 PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-08-19 (66 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2017-05-02T14:12:29.908000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1799869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799868] [NEW] seq command has problems near its max integer
Public bug reported: I can use seq(1) to generate sequences of large numbers if I use the default increment: $ seq 170141183460469231731687303715884105721 170141183460469231731687303715884105725 170141183460469231731687303715884105721 170141183460469231731687303715884105722 170141183460469231731687303715884105723 170141183460469231731687303715884105724 170141183460469231731687303715884105725 $ However, if I use an increment of 2 (which should stop 2 short of the max int,) it starts with the max integer+1 (2^127) and outputs it forever: $ seq 170141183460469231731687303715884105721 2 170141183460469231731687303715884105725 | less 170141183460469231731687303715884105728 170141183460469231731687303715884105728 170141183460469231731687303715884105728 170141183460469231731687303715884105728 . . . ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 24 20:17:15 2018 SourcePackage: coreutils UpgradeStatus: Upgraded to bionic on 2018-08-19 (66 days ago) ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1799868 Title: seq command has problems near its max integer Status in coreutils package in Ubuntu: New Bug description: I can use seq(1) to generate sequences of large numbers if I use the default increment: $ seq 170141183460469231731687303715884105721 170141183460469231731687303715884105725 170141183460469231731687303715884105721 170141183460469231731687303715884105722 170141183460469231731687303715884105723 170141183460469231731687303715884105724 170141183460469231731687303715884105725 $ However, if I use an increment of 2 (which should stop 2 short of the max int,) it starts with the max integer+1 (2^127) and outputs it forever: $ seq 170141183460469231731687303715884105721 2 170141183460469231731687303715884105725 | less 170141183460469231731687303715884105728 170141183460469231731687303715884105728 170141183460469231731687303715884105728 170141183460469231731687303715884105728 . . . ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 24 20:17:15 2018 SourcePackage: coreutils UpgradeStatus: Upgraded to bionic on 2018-08-19 (66 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1799868/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
*** This bug is a duplicate of bug 520546 *** https://bugs.launchpad.net/bugs/520546 This still happens on ubuntu 18.10. sudo kbd_mode -s does work. -- 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/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in console-setup package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1508146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2
This still happens on ubuntu 18.10. sudo kbd_mode -s does work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt-f2 switches to virtual terminal 2 Status in console-cyrillic package in Ubuntu: Invalid Status in console-setup package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-cyrillic/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799868] Re: seq command has problems near its max integer
It's worse than I thought. Increments of 2 fail even when aa factor of 100 away from the limit: kevin@plato-x:~$ seq 170141183460469231731687303715884105721 1 170141183460469231731687303715884105725 | head -10 170141183460469231731687303715884105721 170141183460469231731687303715884105722 170141183460469231731687303715884105723 170141183460469231731687303715884105724 170141183460469231731687303715884105725 kevin@plato-x:~$ seq 1701411834604692317316873037158841051 2 1701411834604692317316873037158841055 | head -10 1701411834604692317282285392020635648 1701411834604692317282285392020635648 1701411834604692317282285392020635648 1701411834604692317282285392020635648 1701411834604692317282285392020635648 1701411834604692317282285392020635648 1701411834604692317282285392020635648 1701411834604692317282285392020635648 1701411834604692317282285392020635648 1701411834604692317282285392020635648 kevin@plato-x:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1799868 Title: seq command has problems near its max integer Status in coreutils package in Ubuntu: New Bug description: I can use seq(1) to generate sequences of large numbers if I use the default increment: $ seq 170141183460469231731687303715884105721 170141183460469231731687303715884105725 170141183460469231731687303715884105721 170141183460469231731687303715884105722 170141183460469231731687303715884105723 170141183460469231731687303715884105724 170141183460469231731687303715884105725 $ However, if I use an increment of 2 (which should stop 2 short of the max int,) it starts with the max integer+1 (2^127) and outputs it forever: $ seq 170141183460469231731687303715884105721 2 170141183460469231731687303715884105725 | less 170141183460469231731687303715884105728 170141183460469231731687303715884105728 170141183460469231731687303715884105728 170141183460469231731687303715884105728 . . . ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 24 20:17:15 2018 SourcePackage: coreutils UpgradeStatus: Upgraded to bionic on 2018-08-19 (66 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1799868/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799738] Re: dose not work rite
*** This bug is a duplicate of bug 1799844 *** https://bugs.launchpad.net/bugs/1799844 ** This bug has been marked a duplicate of bug 1799844 dose not work rite -- 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/1799738 Title: dose not work rite Status in xorg package in Ubuntu: New Bug description: dose not work rite ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Oct 24 11:36:58 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:fde0] Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:fde0] InstallationDate: Installed on 2018-03-07 (231 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: TOSHIBA Satellite C655 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=61e48a6a-7e5a-4c7e-aa64-e126e56af5b5 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.70 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.70:bd07/07/2011:svnTOSHIBA:pnSatelliteC655:pvrPSC08U-03C01K:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Satellite C655 dmi.product.sku: Montevina_Fab dmi.product.version: PSC08U-03C01K dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 xserver.bootTime: Sat Mar 17 11:24:42 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5760 vendor CMO xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799747] Re: Xorg freeze
*** This bug is a duplicate of bug 1798790 *** https://bugs.launchpad.net/bugs/1798790 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 1798790, 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. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-340 (Ubuntu) ** This bug has been marked a duplicate of bug 1798790 Ubuntu 18.10 login screen never appears when using the Nvidia 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/1799747 Title: Xorg freeze Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I can't run Ubuntu 18.10 with nVidia drivers (340.107). They ran just fine on 18.04, but not on 18.10. The system freezes at start up (the furthest that it gets is 'Starting Gnome Display Manager'). X-org Nouveau driver is working ok, but it's not ideal, I get strange flickering at subtle color gradients... ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 24 18:29:54 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Very infrequently GraphicsCard: NVIDIA Corporation GT215 [GeForce GT 240] [10de:0ca3] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2018-10-23 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=3e2e480d-ea50-412f-88cd-55820becb551 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2209 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q 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.:bvr2209:bd03/11/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1799747/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
I think the main hint is in comment #15: tessa@viper:~$ pacmd list Daemon not responding. This means pulseaudio has either hung, crashed or been killed. Please follow these instructions to see if you can find any evidence of a crash: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment If not, and if the pulseaudio daemon is still running and not responding to 'pacmd list' then please try forcing a crash report with: killall -ABRT pulseaudio -- 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/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793640] Re: [XPS 13 9370, Intel Corporation Sunrise Point-LP HD Audio (rev 21), Speaker, Internal] Pulseaudio fails to detect card
*** This bug is a duplicate of bug 210472 *** https://bugs.launchpad.net/bugs/210472 Thanks! The problem is: ii timidity-daemon 2.14.0-8 all runs TiMidity++ as a system-wide MIDI sequencer which makes this a duplicate of bug 210472. Please just uninstall timidity and timidity-daemon. ** This bug has been marked a duplicate of bug 210472 Timidity daemon doesn't play nice with pulse audio -- 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/1793640 Title: [XPS 13 9370, Intel Corporation Sunrise Point-LP HD Audio (rev 21), Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After upgrading to the 18.10 development version from 18.04 only "Dummy sound" is shown. The speakers are not recognized, but plugging headphones works. The system was working well in 18.04. With: sudo alsa force-reload the speakers start to be shown in the sound system parameters and sound is reproduced through the speakers normally. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Sep 21 07:18:03 2018 InstallationDate: Installed on 2018-04-09 (164 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to cosmic on 2018-09-18 (2 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1767896] Re: Live images with broken seed causes snapd high CPU usage and periodic short GUI freezes
If the problem still happens in the final release of 18.10: http://releases.ubuntu.com/18.10/ubuntu-18.10-desktop-amd64.iso then yes this bug needs to be reopened. Or another one logged. But since you are the original reporter, I would say reopen. ** Changed in: snapd (Ubuntu) Status: Won't Fix => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1767896 Title: Live images with broken seed causes snapd high CPU usage and periodic short GUI freezes Status in OEM Priority Project: Fix Released Status in snapd package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: ThinkPad 25, UEFI mode, Ubuntu 18.04 installed as a _live_ distro in FAT32 partition on SATA SSD in WWAN slot. Grub options allow booting without persistence or with a 256MB persistence file. Only thing "persisted" is TERM in favorites. Without persistence all is well. With persistence snapd uses up to 90% CPU - perhaps more - and cripples the system. Fan runs nearly full speed constantly. I can eliminate the problem by removing snapd - and that persists. Can't kill snapd. PID is constantly changing. 0% fan and low CPU use at idle w/out snapd with persistence, or booted w/out persistence. WORKAROUND: sudo systemctl stop snapd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765686] Re: gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node()
"Incomplete" makes sense to me because it appears the problem stopped happening after 3.28, and not at all in 3.30. We will need more time to verify that's really true: https://errors.ubuntu.com/problem/87e4666825764619cb47f3837f871d88d65dd606 and if so then this is "Fix Released" already. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1765686 Title: gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() Status in glib2.0 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: https://errors.ubuntu.com/problem/87e4666825764619cb47f3837f871d88d65dd606 --- It seems to be reproduceable, if I load a wider filearea with different filesystems (ntfs and ext4) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 20 12:36:08 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-03-23 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7fd13cdc0430 : movsbl (%rdi),%edx PC (0x7fd13cdc0430) ok source "(%rdi)" (0x00ca) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1765686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799858] [NEW] package linux-image-4.4.0-138-generic 4.4.0-138.164 failed to install/upgrade
Public bug reported: package linux-image-4.4.0-138-generic 4.4.0-138.164 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 kernel installations halt while scanning mdadm arrays, eventually timing out and failing ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-138-generic 4.4.0-138.164 ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: darknite 3697 F pulseaudio /dev/snd/controlC0: darknite 3697 F pulseaudio Date: Wed Oct 24 18:03:47 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 HibernationDevice: RESUME=UUID=93c26513-703e-41c7-b051-ce990cb1c75a InstallationDate: Installed on 2014-07-21 (1556 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-137-generic root=UUID=58386e6d-2705-4538-831c-48934ded8dbb ro nomdmonddf nomdmonisw PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: initramfs-tools Title: package linux-image-4.4.0-138-generic 4.4.0-138.164 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.asset.tag: D050995F178D dmi.board.name: 980DE3/U3S3 R2.0 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.00:bd09/18/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn980DE3/U3S3R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1799858 Title: package linux-image-4.4.0-138-generic 4.4.0-138.164 failed to install/upgrade Status in initramfs-tools package in Ubuntu: New Bug description: package linux-image-4.4.0-138-generic 4.4.0-138.164 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 kernel installations halt while scanning mdadm arrays, eventually timing out and failing ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-138-generic 4.4.0-138.164 ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: darknite 3697 F pulseaudio /dev/snd/controlC0: darknite 3697 F pulseaudio Date: Wed Oct 24 18:03:47 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 HibernationDevice: RESUME=UUID=93c26513-703e-41c7-b051-ce990cb1c75a InstallationDate: Installed on 2014-07-21 (1556 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-137-generic root=UUID=58386e6d-2705-4538-831c-48934ded8dbb ro nomdmonddf nomdmonisw PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: initramfs-tools Title: package linux-image-4.4.0-138-generic 4.4.0-138.164 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.asset.tag: D050995F178D dmi.board.name: 980DE3/U3S3 R2.0
[Touch-packages] [Bug 1799858] Re: package linux-image-4.4.0-138-generic 4.4.0-138.164 failed to install/upgrade
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1799858 Title: package linux-image-4.4.0-138-generic 4.4.0-138.164 failed to install/upgrade Status in initramfs-tools package in Ubuntu: New Bug description: package linux-image-4.4.0-138-generic 4.4.0-138.164 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 kernel installations halt while scanning mdadm arrays, eventually timing out and failing ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-138-generic 4.4.0-138.164 ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: darknite 3697 F pulseaudio /dev/snd/controlC0: darknite 3697 F pulseaudio Date: Wed Oct 24 18:03:47 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 HibernationDevice: RESUME=UUID=93c26513-703e-41c7-b051-ce990cb1c75a InstallationDate: Installed on 2014-07-21 (1556 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-137-generic root=UUID=58386e6d-2705-4538-831c-48934ded8dbb ro nomdmonddf nomdmonisw PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: initramfs-tools Title: package linux-image-4.4.0-138-generic 4.4.0-138.164 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.asset.tag: D050995F178D dmi.board.name: 980DE3/U3S3 R2.0 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.00:bd09/18/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn980DE3/U3S3R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1799858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799857] [NEW] sudo -p '' displays a password prompt which it shouldn't
Public bug reported: I have small script that invokes another shell script as root thus: #!/bin/bash echo "mypass" | sudo -p '' -S /usr/StorMan/StorMan.sh when running in 16.04 LTS this didn't display a password prompt which I understand to be correct behaviour. Since upgrading to 18.04.1 LTS the output looks like: amonra@Charon:~$ ./storman [sudo] password for amonra: which as far as I can determine is not correct. Thanks Dave ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sudo 1.8.21p2-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Oct 25 03:07:27 2018 InstallationDate: Installed on 2016-03-28 (940 days ago) InstallationMedia: Ubuntu-Server 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) SourcePackage: sudo UpgradeStatus: Upgraded to bionic on 2018-10-22 (2 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers'] modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README'] ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1799857 Title: sudo -p '' displays a password prompt which it shouldn't Status in sudo package in Ubuntu: New Bug description: I have small script that invokes another shell script as root thus: #!/bin/bash echo "mypass" | sudo -p '' -S /usr/StorMan/StorMan.sh when running in 16.04 LTS this didn't display a password prompt which I understand to be correct behaviour. Since upgrading to 18.04.1 LTS the output looks like: amonra@Charon:~$ ./storman [sudo] password for amonra: which as far as I can determine is not correct. Thanks Dave ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sudo 1.8.21p2-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Oct 25 03:07:27 2018 InstallationDate: Installed on 2016-03-28 (940 days ago) InstallationMedia: Ubuntu-Server 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) SourcePackage: sudo UpgradeStatus: Upgraded to bionic on 2018-10-22 (2 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers'] modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1799857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798839] Re: Canonical Livepatch doesn't appear in "Updates" tab.
It would be nice to have some warning the added security benefits available in 18.04 would be removed upon upgrade to 18.10... 😥 There really needs to be some sort of dialogue box warning the user. -- 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/1798839 Title: Canonical Livepatch doesn't appear in "Updates" tab. Status in software-properties package in Ubuntu: New Bug description: Livepatch was working and appearing fine in 'Software & Updates' until after the upgrade from Ubuntu 18.04 LTS to Ubuntu 18.10; Livepatch does not appear as an option anymore after upgrading. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-gtk 0.96.27 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 19 11:04:03 2018 InstallationDate: Installed on 2018-08-17 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1798839/+subscriptions -- Mailing list: https://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 1798839] Re: Canonical Livepatch doesn't appear in "Updates" tab.
It would be nice to have some warning the added security benefits available in 18.04 would be removed upon upgrade to 18.10... 😥 There really needs to be some sort of dialogue box warning the user. On Mon, Oct 22, 2018, 6:31 PM Matthew Paul Thomas wrote: > I’ve reported bug 1799310 about warning you when an upgrade will result > in Livepatch no longer being available. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1798839 > > Title: > Canonical Livepatch doesn't appear in "Updates" tab. > > Status in software-properties package in Ubuntu: > New > > Bug description: > Livepatch was working and appearing fine in 'Software & Updates' until > after the upgrade from Ubuntu 18.04 LTS to Ubuntu 18.10; Livepatch > does not appear as an option anymore after upgrading. > > ProblemType: Bug > DistroRelease: Ubuntu 18.10 > Package: software-properties-gtk 0.96.27 > ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 > Uname: Linux 4.18.0-10-generic x86_64 > ApportVersion: 2.20.10-0ubuntu13 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Fri Oct 19 11:04:03 2018 > InstallationDate: Installed on 2018-08-17 (63 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > PackageArchitecture: all > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: software-properties > UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1798839/+subscriptions > -- 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/1798839 Title: Canonical Livepatch doesn't appear in "Updates" tab. Status in software-properties package in Ubuntu: New Bug description: Livepatch was working and appearing fine in 'Software & Updates' until after the upgrade from Ubuntu 18.04 LTS to Ubuntu 18.10; Livepatch does not appear as an option anymore after upgrading. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-gtk 0.96.27 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 19 11:04:03 2018 InstallationDate: Installed on 2018-08-17 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1798839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785764] Re: Chrome/Chromium and Image Viewer distort colours if a colour profile is enabled.
@osomon, Just verified both chrome AND chromium (v70) experience this bug. The colours are ugly and dull when a colour profile is active. It's immediately obvious in the Google logo on the search page. And the problem goes away as soon as I remove the colour profile and restart the browser. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Confirmed -- 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/1785764 Title: Chrome/Chromium and Image Viewer distort colours if a colour profile is enabled. Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Using Ubuntu 18.04.1 LTS Running on an i7-6700k with a GTX 1080 Reproducible with nvidia-driver-396 or xserver-xorg-video-nouveau and a single 4K screen (TV) connected via HDMI. The issue: Any dark content displayed by an effected application (e.g. a very dark image or dark themed web page) is much darker than intended making it almost unusable. This only effects applications that are launched when the 4K screen is connected. If i disconnect the 4K screen, launch the app via a different 1080p monitor then reconnect the 4K screen the app remains unaffected. The only apps i have found so far that are effected by this are Google Chrome and Image Viewer. That said this is only noticeable when the app is displaying dark contend so if other apps are affected it may be impossible to tell. The attached screenshot uses a black to white gradient image to clearly demonstrate the issue. Is seems like it may be an issue with colour depth as bellow a certain brightness it just goes strait to black. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1785764/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
:) You're welcome. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799844] [NEW] dose not work rite
Public bug reported: WILL NOT UNINSTAL ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Oct 24 19:59:39 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:fde0] Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:fde0] InstallationDate: Installed on 2018-03-07 (231 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: TOSHIBA Satellite C655 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=61e48a6a-7e5a-4c7e-aa64-e126e56af5b5 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.70 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.70:bd07/07/2011:svnTOSHIBA:pnSatelliteC655:pvrPSC08U-03C01K:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Satellite C655 dmi.product.sku: Montevina_Fab dmi.product.version: PSC08U-03C01K dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 xserver.bootTime: Sat Mar 17 11:24:42 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5760 vendor CMO xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic 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/1799844 Title: dose not work rite Status in xorg package in Ubuntu: New Bug description: WILL NOT UNINSTAL ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Oct 24 19:59:39 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:fde0] Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:fde0] InstallationDate: Installed on 2018-03-07 (231 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: TOSHIBA Satellite C655 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=61e48a6a-7e5a-4c7e-aa64-e126e56af5b5 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.70 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chas
[Touch-packages] [Bug 1767896] Re: Live images with broken seed causes snapd high CPU usage and periodic short GUI freezes
The above "confirmed fixed" link is broken. If you'll pardon another ignorant question: when does this fix show up in distro? Just tried 18.10 and persistence renders live Ubuntu completely unusable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1767896 Title: Live images with broken seed causes snapd high CPU usage and periodic short GUI freezes Status in OEM Priority Project: Fix Released Status in snapd package in Ubuntu: Won't Fix Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: ThinkPad 25, UEFI mode, Ubuntu 18.04 installed as a _live_ distro in FAT32 partition on SATA SSD in WWAN slot. Grub options allow booting without persistence or with a 256MB persistence file. Only thing "persisted" is TERM in favorites. Without persistence all is well. With persistence snapd uses up to 90% CPU - perhaps more - and cripples the system. Fan runs nearly full speed constantly. I can eliminate the problem by removing snapd - and that persists. Can't kill snapd. PID is constantly changing. 0% fan and low CPU use at idle w/out snapd with persistence, or booted w/out persistence. WORKAROUND: sudo systemctl stop snapd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
OMG! Where u were all this time?! Thank you very much! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1657646] Re: Missing thin-provisioning-tools prevents VG with thin pool LV from being (de)activated, but not its creation
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lvm2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1657646 Title: Missing thin-provisioning-tools prevents VG with thin pool LV from being (de)activated, but not its creation Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 package in Debian: New Bug description: Creating a thin pool LV is allowed even when thin-provisioning-tools is not installed. But deactivating or activating that VG fails. Since deactivating the VG usually only happens at reboot, the user might fail to notice this big problem until then. I think the lvconvert tool, used to combine the two "thin LVs" into a thin pool LV, should refuse to run if thin-provisioning-tools, or the needed scripts, aren't installed. Steps to reproduce: root@15-89:~# vgcreate vg /dev/vdb1 Volume group "vg" successfully created root@15-89:~# vgs VG #PV #LV #SN Attr VSize VFree vg 1 0 0 wz--n- 40.00g 40.00g root@15-89:~# lvcreate -n pool0 -l 90%VG vg Logical volume "pool0" created. root@15-89:~# lvcreate -n pool0meta -l 5%VG vg Logical volume "pool0meta" created. root@15-89:~# lvs LVVG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert pool0 vg -wi-a- 36.00g pool0meta vg -wi-a- 2.00g root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 100 Jun 21 14:15 ./ drwxr-xr-x 20 root root3820 Jun 21 14:15 ../ crw--- 1 root root 10, 236 Jun 21 13:15 control lrwxrwxrwx 1 root root 7 Jun 21 14:14 vg-pool0 -> ../dm-0 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0meta -> ../dm-1 root@15-89:~# lvconvert --type thin-pool --poolmetadata vg/pool0meta vg/pool0 WARNING: Converting logical volume vg/pool0 and vg/pool0meta to pool's data and metadata volumes. THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.) Do you really want to convert vg/pool0 and vg/pool0meta? [y/n]: y Converted vg/pool0 to thin pool. root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 120 Jun 21 14:15 ./ drwxr-xr-x 20 root root3840 Jun 21 14:15 ../ crw--- 1 root root 10, 236 Jun 21 13:15 control lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0 -> ../dm-2 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0_tdata -> ../dm-1 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0_tmeta -> ../dm-0 root@15-89:~# lvs -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%S ync Convert [lvol0_pmspare] vg ewi--- 2.00g pool0 vg twi-a-tz-- 36.00g 0.00 0.01 [pool0_tdata] vg Twi-ao 36.00g [pool0_tmeta] vg ewi-ao 2.00g If you now reboot the system, all that is gone: root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 60 Jun 21 14:28 ./ drwxr-xr-x 19 root root3760 Jun 21 14:28 ../ crw--- 1 root root 10, 236 Jun 21 14:28 control The same happens if you deactivate the VG (which the reboot undoubtedly triggers). It fails because of a missing /usr/sbin/thin_check which is provided by the thin-provisioning-tools package: root@15-89:~# vgchange -a n /usr/sbin/thin_check: execvp failed: No such file or directory WARNING: Integrity check of metadata for pool vg/pool0 failed. 0 logical volume(s) in volume group "vg" now active root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 60 Jun 21 14:29 ./ drwxr-xr-x 19 root root3760 Jun 21 14:29 ../ crw--- 1 root root 10, 236 Jun 21 14:28 control To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1657646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1657646] Re: Missing thin-provisioning-tools prevents VG with thin pool LV from being (de)activated, but not its creation
This is related to a problem I've encountered today with lvmcache partitions. >From a fresh Ubuntu 18.04 install, with lvm2 installed, I create an LVM on HDD's with an SSD partitioned to provide cache: lvcreate -n home_lv_root -L 1.2Tb vg0 vgextend vg0 /dev/nvme0n1p6 lvcreate -n home_lv_cache -L 17G vg0 /dev/nvme0n1p6 lvcreate -n home_lv_cachemeta -L 1.6G vg0 /dev/nvme0n1p6 lvconvert --type cache-pool --poolmetadata vg0/home_lv_cachemeta \ vg0/home_lv_cache lvconvert --type cache --cachepool vg0/home_lv_cache vg0/home_lv_root then reboot. The volume vg0/home_lv_root disappears. I try to find it: pvscan vgscan lvscan vgchange -ay The vgchange complains it cannot complete "cache_check". Here lies the problem: /usr/sbin/cache_check is in thin-provisioning- tools So without thin-provisioning-tools it is possible to create an LVM2 volume which disappears on reboot. This suggests that thin-provisioning-tools must be a prerequisite, or that cache_check be moved into package lvm2. This also appears to be related to bug #1423796, if an LVM volume has a cache attached and is required at boot time, boot will fail completely. Creating a cached root volume seemed like a sensible thing to do. This also occurred to me today on a server config, and I moved the OS entirely onto an SSD partition rather than deal with it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1657646 Title: Missing thin-provisioning-tools prevents VG with thin pool LV from being (de)activated, but not its creation Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 package in Debian: New Bug description: Creating a thin pool LV is allowed even when thin-provisioning-tools is not installed. But deactivating or activating that VG fails. Since deactivating the VG usually only happens at reboot, the user might fail to notice this big problem until then. I think the lvconvert tool, used to combine the two "thin LVs" into a thin pool LV, should refuse to run if thin-provisioning-tools, or the needed scripts, aren't installed. Steps to reproduce: root@15-89:~# vgcreate vg /dev/vdb1 Volume group "vg" successfully created root@15-89:~# vgs VG #PV #LV #SN Attr VSize VFree vg 1 0 0 wz--n- 40.00g 40.00g root@15-89:~# lvcreate -n pool0 -l 90%VG vg Logical volume "pool0" created. root@15-89:~# lvcreate -n pool0meta -l 5%VG vg Logical volume "pool0meta" created. root@15-89:~# lvs LVVG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert pool0 vg -wi-a- 36.00g pool0meta vg -wi-a- 2.00g root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 100 Jun 21 14:15 ./ drwxr-xr-x 20 root root3820 Jun 21 14:15 ../ crw--- 1 root root 10, 236 Jun 21 13:15 control lrwxrwxrwx 1 root root 7 Jun 21 14:14 vg-pool0 -> ../dm-0 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0meta -> ../dm-1 root@15-89:~# lvconvert --type thin-pool --poolmetadata vg/pool0meta vg/pool0 WARNING: Converting logical volume vg/pool0 and vg/pool0meta to pool's data and metadata volumes. THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.) Do you really want to convert vg/pool0 and vg/pool0meta? [y/n]: y Converted vg/pool0 to thin pool. root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 120 Jun 21 14:15 ./ drwxr-xr-x 20 root root3840 Jun 21 14:15 ../ crw--- 1 root root 10, 236 Jun 21 13:15 control lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0 -> ../dm-2 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0_tdata -> ../dm-1 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0_tmeta -> ../dm-0 root@15-89:~# lvs -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%S ync Convert [lvol0_pmspare] vg ewi--- 2.00g pool0 vg twi-a-tz-- 36.00g 0.00 0.01 [pool0_tdata] vg Twi-ao 36.00g [pool0_tmeta] vg ewi-ao 2.00g If you now reboot the system, all that is gone: root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 60 Jun 21 14:28 ./ drwxr-xr-x 19 root root3760 Jun 21 14:28 ../ crw--- 1 root root 10, 236 Jun 21 14:28 control The same happens if you deactivate the VG (which the reboot undoubtedly triggers). It fails because of a missing /usr/sbin/thin_check which is provided by the thin-provisioning-tools package: root@15-89:~# vgchange -a n /usr/sbin/thin_check: execvp failed: No such file or directory WARNING: Integrity check of metadata for pool vg/pool0 failed. 0 logical volume(s) in volume group "vg" now active root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 60 Jun 21 14:29 ./ drwxr-xr-x 19
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Please try, in the /etc/gdm3/custom.conf, uncomment WaylandEnable=false and Nvidia driver will work with gdm3. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection
** Also affects: resolvconf (Ubuntu) Importance: Undecided Status: New -- 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/1778946 Title: No dns resolution after closing a vpn/pptp connection Status in network-manager package in Ubuntu: Confirmed Status in ppp package in Ubuntu: New Status in resolvconf package in Ubuntu: New Bug description: step to reproduce set a VPN connection configured to connect a Microsoft vpn server (pptp) internet acces is ok enable the vpn connection using the applet on the top right corner of the desktop internet still ok ping works disable the vpn connection ping doesn't works with a host but works if i specify an ip address ping: xx.net: Nom ou service inconnu As a workaround, i disable the ethernet link and re-enable it name resolution is now ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 18:09:30 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-06-03 (1484 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.0.254 dev eth0 proto dhcp metric 20100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Connexion filaire 1 94806bba-1c68-46b6-87f4-a3aff6dd /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection
** Also affects: ppp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1778946 Title: No dns resolution after closing a vpn/pptp connection Status in network-manager package in Ubuntu: Confirmed Status in ppp package in Ubuntu: New Bug description: step to reproduce set a VPN connection configured to connect a Microsoft vpn server (pptp) internet acces is ok enable the vpn connection using the applet on the top right corner of the desktop internet still ok ping works disable the vpn connection ping doesn't works with a host but works if i specify an ip address ping: xx.net: Nom ou service inconnu As a workaround, i disable the ethernet link and re-enable it name resolution is now ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 18:09:30 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-06-03 (1484 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.0.254 dev eth0 proto dhcp metric 20100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Connexion filaire 1 94806bba-1c68-46b6-87f4-a3aff6dd /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765686] Re: gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node()
** Changed in: glib2.0 (Ubuntu) Status: In Progress => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1765686 Title: gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup_node() Status in glib2.0 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: https://errors.ubuntu.com/problem/87e4666825764619cb47f3837f871d88d65dd606 --- It seems to be reproduceable, if I load a wider filearea with different filesystems (ntfs and ext4) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 20 12:36:08 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-03-23 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7fd13cdc0430 : movsbl (%rdi),%edx PC (0x7fd13cdc0430) ok source "(%rdi)" (0x00ca) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1765686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1760220] Re: ubuntu-bug with program path says as a snap does not belong to a package
** Branch linked: lp:~brian-murray/apport/executable-snap-bin -- 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/1760220 Title: ubuntu-bug with program path says as a snap does not belong to a package Status in apport package in Ubuntu: In Progress Bug description: apport's ui.py file contains the following code: 809 # executable? 810 elif '/' in self.args[0]: 811 pkg = apport.packaging.get_file_package(self.args[0]) 812 if not pkg: 813 optparser.error('%s does not belong to a package.' % self.args[0]) 814 sys.exit(1) 815 self.args = [] 816 self.options.filebug = True 817 self.options.package = pkg This will not provide any useful information about what to do if the 'executable' is provided by a snap. Information similar to https://code.launchpad.net/~juliank/ubuntu/bionic/apport/snap/+merge/342207 should be provided if the path is from a snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1760220/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799807] [NEW] Sphinx documentation no longer available online (apt.alioth.debian.org unavailable)
Public bug reported: While working on the development of a Python package I created (deb-pkg- tools) that uses python-apt and refers to its documentation I noticed that the online documentation seems to have disappeared... This makes it impossible for my project to cross-reference the python- apt documentation, something that used to work fine a few months ago :-(. Here's what Sphinx has to say on the matter: $ make docs Running Sphinx v1.8.1 loading translations [en]... done loading pickled environment... done loading intersphinx inventory from https://apt.alioth.debian.org/python-apt-doc/objects.inv... WARNING: failed to reach any of the inventories with the following issues: WARNING: intersphinx inventory 'https://apt.alioth.debian.org/python-apt-doc/objects.inv' not fetchable due to : ('intersphinx inventory %r not fetchable due to %s: %s', 'https://apt.alioth.debian.org/python-apt-doc/objects.inv', , ConnectionError(...)) When I look at https://readthedocs.org/projects/deb-pkg- tools/builds/6801480/ I can see that in February 2018 this was still working fine, but the domain apt.alioth.debian.org no longer resolves. It might be that the documentation has moved somewhere else, without a redirect in place, however I spent more than an hour looking and couldn't find the new location (if it exists): 1. https://pypi.org/project/python-apt/ links to the broken domain. 2. http://www.sphinx-doc.org/en/master/examples.html also links to the broken domain. Would it be possible to make the Sphinx based documentation on python- apt available online again? Personally I have good experiences with Read The Docs and I'd love to see https://python-apt.readthedocs.io/ be brought into existence 😇. ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1799807 Title: Sphinx documentation no longer available online (apt.alioth.debian.org unavailable) Status in python-apt package in Ubuntu: New Bug description: While working on the development of a Python package I created (deb- pkg-tools) that uses python-apt and refers to its documentation I noticed that the online documentation seems to have disappeared... This makes it impossible for my project to cross-reference the python- apt documentation, something that used to work fine a few months ago :-(. Here's what Sphinx has to say on the matter: $ make docs Running Sphinx v1.8.1 loading translations [en]... done loading pickled environment... done loading intersphinx inventory from https://apt.alioth.debian.org/python-apt-doc/objects.inv... WARNING: failed to reach any of the inventories with the following issues: WARNING: intersphinx inventory 'https://apt.alioth.debian.org/python-apt-doc/objects.inv' not fetchable due to : ('intersphinx inventory %r not fetchable due to %s: %s', 'https://apt.alioth.debian.org/python-apt-doc/objects.inv', , ConnectionError(...)) When I look at https://readthedocs.org/projects/deb-pkg- tools/builds/6801480/ I can see that in February 2018 this was still working fine, but the domain apt.alioth.debian.org no longer resolves. It might be that the documentation has moved somewhere else, without a redirect in place, however I spent more than an hour looking and couldn't find the new location (if it exists): 1. https://pypi.org/project/python-apt/ links to the broken domain. 2. http://www.sphinx-doc.org/en/master/examples.html also links to the broken domain. Would it be possible to make the Sphinx based documentation on python- apt available online again? Personally I have good experiences with Read The Docs and I'd love to see https://python-apt.readthedocs.io/ be brought into existence 😇. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1799807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799807] Re: Sphinx documentation no longer available online (apt.alioth.debian.org unavailable)
For whatever it's worth: I wouldn't mind spending a bit of time trying to set up https://python-apt.readthedocs.io/ based on the git repository at https://git.launchpad.net/ubuntu/+source/python-apt, although I can't tell if this plan will actually work without trying it (for example I don't know if the dependencies of the documentation build will be available in the RTD environment). PS. The "information type" change was unintended, which explains why I reverted it; I didn't realize that my (accidental) mouse click would change the bug report without some form of confirmation... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1799807 Title: Sphinx documentation no longer available online (apt.alioth.debian.org unavailable) Status in python-apt package in Ubuntu: New Bug description: While working on the development of a Python package I created (deb- pkg-tools) that uses python-apt and refers to its documentation I noticed that the online documentation seems to have disappeared... This makes it impossible for my project to cross-reference the python- apt documentation, something that used to work fine a few months ago :-(. Here's what Sphinx has to say on the matter: $ make docs Running Sphinx v1.8.1 loading translations [en]... done loading pickled environment... done loading intersphinx inventory from https://apt.alioth.debian.org/python-apt-doc/objects.inv... WARNING: failed to reach any of the inventories with the following issues: WARNING: intersphinx inventory 'https://apt.alioth.debian.org/python-apt-doc/objects.inv' not fetchable due to : ('intersphinx inventory %r not fetchable due to %s: %s', 'https://apt.alioth.debian.org/python-apt-doc/objects.inv', , ConnectionError(...)) When I look at https://readthedocs.org/projects/deb-pkg- tools/builds/6801480/ I can see that in February 2018 this was still working fine, but the domain apt.alioth.debian.org no longer resolves. It might be that the documentation has moved somewhere else, without a redirect in place, however I spent more than an hour looking and couldn't find the new location (if it exists): 1. https://pypi.org/project/python-apt/ links to the broken domain. 2. http://www.sphinx-doc.org/en/master/examples.html also links to the broken domain. Would it be possible to make the Sphinx based documentation on python- apt available online again? Personally I have good experiences with Read The Docs and I'd love to see https://python-apt.readthedocs.io/ be brought into existence 😇. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1799807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799806] [NEW] ubuntu-bug with a program path that is a symlink doesn't work
Public bug reported: $ ubuntu-bug /usr/bin/vim Usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash file] ubuntu-bug: error: /usr/bin/vim does not belong to a package. [ 2:41PM 10508 ] [ bdmurray@impulse:~ ] $ file /usr/bin/vim /usr/bin/vim: symbolic link to /etc/alternatives/vim [ 2:41PM 10509 ] [ bdmurray@impulse:~ ] $ apt-cache policy apport apport: Installed: 2.20.10-0ubuntu13 Candidate: 2.20.10-0ubuntu13 Version table: *** 2.20.10-0ubuntu13 500 500 http://192.168.10.7/ubuntu cosmic/main amd64 Packages 500 http://192.168.10.7/ubuntu cosmic/main i386 Packages ** Affects: apport (Ubuntu) Importance: Medium Status: Triaged ** Tags: cosmic ** Changed in: apport (Ubuntu) Status: New => Triaged ** Changed in: apport (Ubuntu) Importance: Undecided => Medium ** Tags added: cosmic -- 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/1799806 Title: ubuntu-bug with a program path that is a symlink doesn't work Status in apport package in Ubuntu: Triaged Bug description: $ ubuntu-bug /usr/bin/vim Usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash file] ubuntu-bug: error: /usr/bin/vim does not belong to a package. [ 2:41PM 10508 ] [ bdmurray@impulse:~ ] $ file /usr/bin/vim /usr/bin/vim: symbolic link to /etc/alternatives/vim [ 2:41PM 10509 ] [ bdmurray@impulse:~ ] $ apt-cache policy apport apport: Installed: 2.20.10-0ubuntu13 Candidate: 2.20.10-0ubuntu13 Version table: *** 2.20.10-0ubuntu13 500 500 http://192.168.10.7/ubuntu cosmic/main amd64 Packages 500 http://192.168.10.7/ubuntu cosmic/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1799806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 997217] Re: salsauthd maxes cpu
** Description changed: [Impact] The rimap authentication mechanism in saslauthd can hit a condition where it will start spinning and using all available CPU. This condition can be easily encountered when an authentication is happening and the imap service is being restarted. Furthermore, the saslauthd child process that picked up that authentication request and that is spinning now won't be reaped nor can it service further requests. If all children are left in this state, the authentication service as a whole won't be working anymore. [Test Case] This test can be performed in a LXD or VM. * install the needed packages. mail-stack-delivery is used to have an imap server available on localhost that needs no further configuration. Accept the defaults for all debconf prompts: sudo apt update sudo apt install sasl2-bin mail-stack-delivery * set the password "ubuntu" for the ubuntu user echo ubuntu:ubuntu | sudo chpasswd * start saslauthd like this, with just one child: sudo /usr/sbin/saslauthd -a rimap -O localhost -r -n 1 * restart dovecot sudo service dovecot restart * test saslauthd authentication: $ sudo testsaslauthd -u ubuntu -p ubuntu 0: OK "Success." * Now let's break it. In one terminal watch the output of top: top * in another terminal, run the following: sudo testsaslauthd -u ubuntu -p ubuntu & sleep 1; sudo service dovecot stop * observe in the "top" terminal that saslauthd is consuming a lot of cpu. If that's not happening, try starting dovecot again and adjusting the sleep value in the previous test command, but 1s was enough in all my runs. * start dovecot and repeat the authentication request. Since the only saslauthd child is now spinning, this will block: sudo service dovecot start $ sudo testsaslauthd -u ubuntu -p ubuntu [Regression Potential] + This fix relies on read(2) returning zero bytes when the connection is dropped, and that is clearly documented in its manpage: - * discussion of how regressions are most likely to manifest as a result - of this change. + "On success, the number of bytes read is returned (zero indicates + end of file)," - * It is assumed that any SRU candidate patch is well-tested before - upload and has a low overall risk of regression, but it's important - to make the effort to think about what ''could'' happen in the - event of a regression. + The select manpage also documents such a case being a valid case to + indicate that a socket is ready to be read from, and that it won't + block: - * This both shows the SRU team that the risks have been considered, - and provides guidance to testers in regression-testing the SRU. + "The file descriptors listed in readfds will be watched to see if + characters become available for reading (more precisely, to see if a + read will not block; in particular, a file descriptor is also ready + on end-of-file)" + + This patch is what was used upstream, and is also present in bionic. + + I can't think of regressions specific to this change, other than the + usual risk of rebuilding a widely used library (sasl2) in an environment + different from the one from when xenial was released, i.e., different + libraries available, maybe different system-wide build options, etc. [Other Info] + Trusty is still not accounting for read() returning zero being an end-of-file case, but the loop there has a counter and it eventually exits, not leading to a perpetual spin or high cpu usage (see comment #17 for a brief history on how this fix was dropped in the xenial package). - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance + The fix is simple and could be applied there as well, if the SRU team + prefers. + [Original Description] sasl2-bin version 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu contains a bug that causes heavy cpu utilization, impacting normal operation of one of our mail servers following an upgrade to Ubuntu 12.04. We are running the daemon with the following options: /usr/sbin/saslauthd -a rimap -O our.imap.server -r -m /var/spool/postfix/var/run/saslauthd -n 5 We noticed that users were unable to send mail and that the saslauthd processes were using approximately 100% of each cpu core. An strace of one of the runaway process showed that it was stuck in the following behaviour: select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(
[Touch-packages] [Bug 997217] Re: salsauthd maxes cpu
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/cyrus-sasl2/+git/cyrus-sasl2/+merge/357779 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/997217 Title: salsauthd maxes cpu Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Precise: Won't Fix Status in cyrus-sasl2 source package in Trusty: Invalid Status in cyrus-sasl2 source package in Xenial: In Progress Bug description: [Impact] The rimap authentication mechanism in saslauthd can hit a condition where it will start spinning and using all available CPU. This condition can be easily encountered when an authentication is happening and the imap service is being restarted. Furthermore, the saslauthd child process that picked up that authentication request and that is spinning now won't be reaped nor can it service further requests. If all children are left in this state, the authentication service as a whole won't be working anymore. [Test Case] This test can be performed in a LXD or VM. * install the needed packages. mail-stack-delivery is used to have an imap server available on localhost that needs no further configuration. Accept the defaults for all debconf prompts: sudo apt update sudo apt install sasl2-bin mail-stack-delivery * set the password "ubuntu" for the ubuntu user echo ubuntu:ubuntu | sudo chpasswd * start saslauthd like this, with just one child: sudo /usr/sbin/saslauthd -a rimap -O localhost -r -n 1 * restart dovecot sudo service dovecot restart * test saslauthd authentication: $ sudo testsaslauthd -u ubuntu -p ubuntu 0: OK "Success." * Now let's break it. In one terminal watch the output of top: top * in another terminal, run the following: sudo testsaslauthd -u ubuntu -p ubuntu & sleep 1; sudo service dovecot stop * observe in the "top" terminal that saslauthd is consuming a lot of cpu. If that's not happening, try starting dovecot again and adjusting the sleep value in the previous test command, but 1s was enough in all my runs. * start dovecot and repeat the authentication request. Since the only saslauthd child is now spinning, this will block: sudo service dovecot start $ sudo testsaslauthd -u ubuntu -p ubuntu [Regression Potential] This fix relies on read(2) returning zero bytes when the connection is dropped, and that is clearly documented in its manpage: "On success, the number of bytes read is returned (zero indicates end of file)," The select manpage also documents such a case being a valid case to indicate that a socket is ready to be read from, and that it won't block: "The file descriptors listed in readfds will be watched to see if characters become available for reading (more precisely, to see if a read will not block; in particular, a file descriptor is also ready on end-of-file)" This patch is what was used upstream, and is also present in bionic. I can't think of regressions specific to this change, other than the usual risk of rebuilding a widely used library (sasl2) in an environment different from the one from when xenial was released, i.e., different libraries available, maybe different system-wide build options, etc. [Other Info] Trusty is still not accounting for read() returning zero being an end-of-file case, but the loop there has a counter and it eventually exits, not leading to a perpetual spin or high cpu usage (see comment #17 for a brief history on how this fix was dropped in the xenial package). The fix is simple and could be applied there as well, if the SRU team prefers. [Original Description] sasl2-bin version 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu contains a bug that causes heavy cpu utilization, impacting normal operation of one of our mail servers following an upgrade to Ubuntu 12.04. We are running the daemon with the following options: /usr/sbin/saslauthd -a rimap -O our.imap.server -r -m /var/spool/postfix/var/run/saslauthd -n 5 We noticed that users were unable to send mail and that the saslauthd processes were using approximately 100% of each cpu core. An strace of one of the runaway process showed that it was stuck in the following behaviour: select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
I would say workaround not solution -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 997217] Re: salsauthd maxes cpu
** Description changed: [Impact] The rimap authentication mechanism in saslauthd can hit a condition where it will start spinning and using all available CPU. This condition can be easily encountered when an authentication is happening and the imap service is being restarted. Furthermore, the saslauthd child process that picked up that authentication request and that is spinning now won't be reaped nor can it service further requests. If all children are left in this state, the authentication service as a whole won't be working anymore. [Test Case] This test can be performed in a LXD or VM. * install the needed packages. mail-stack-delivery is used to have an imap server available on localhost that needs no further configuration. Accept the defaults for all debconf prompts: sudo apt update sudo apt install sasl2-bin mail-stack-delivery * set the password "ubuntu" for the ubuntu user echo ubuntu:ubuntu | sudo chpasswd * start saslauthd like this, with just one child: sudo /usr/sbin/saslauthd -a rimap -O localhost -r -n 1 * restart dovecot sudo service dovecot restart * test saslauthd authentication: $ sudo testsaslauthd -u ubuntu -p ubuntu 0: OK "Success." * Now let's break it. In one terminal watch the output of top: top * in another terminal, run the following: sudo testsaslauthd -u ubuntu -p ubuntu & sleep 1; sudo service dovecot stop * observe in the "top" terminal that saslauthd is consuming a lot of cpu. If that's not happening, try starting dovecot again and adjusting - the sleep value in the previous test command. + the sleep value in the previous test command, but 1s was enough in all + my runs. - * repeat the authentication request. Since the only saslauthd child is now spinning, this will block: + * start dovecot and repeat the authentication request. Since the only saslauthd child is now spinning, this will block: + sudo service dovecot start $ sudo testsaslauthd -u ubuntu -p ubuntu - [Regression Potential] * discussion of how regressions are most likely to manifest as a result of this change. * It is assumed that any SRU candidate patch is well-tested before upload and has a low overall risk of regression, but it's important to make the effort to think about what ''could'' happen in the event of a regression. * This both shows the SRU team that the risks have been considered, and provides guidance to testers in regression-testing the SRU. [Other Info] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance [Original Description] sasl2-bin version 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu contains a bug that causes heavy cpu utilization, impacting normal operation of one of our mail servers following an upgrade to Ubuntu 12.04. We are running the daemon with the following options: /usr/sbin/saslauthd -a rimap -O our.imap.server -r -m /var/spool/postfix/var/run/saslauthd -n 5 We noticed that users were unable to send mail and that the saslauthd processes were using approximately 100% of each cpu core. An strace of one of the runaway process showed that it was stuck in the following behaviour: select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 . with further inspection showing that the file descriptor in question was a socket connected to our imap server in CLOSE_WAIT. Browsing saslauthd/auth_rimap.c in the source package for sasl2-bin, we came across the following code, repeated in two locations: while( select (fds, &perm, NULL, NULL, &timeout ) >0 ) { if ( FD_ISSET(s, &perm) ) { ret = read(s, rbuf+rc, sizeof(rbuf)-rc); if ( ret<0 ) { rc = ret; break; } else { rc += ret; } } } It looks like this loop is expected to run until a read error is encountered or the timeout of 1 second is reached. There is no test to check that 0 bytes were read, ind
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Solution found with NVidia support. GDM3 causing Ubuntu 18.10 to "freeze" before login screen After remove GDM3 and LightDM installation Ununtu booted as usually -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1760220] Re: ubuntu-bug with program path says as a snap does not belong to a package
** Changed in: apport (Ubuntu) Status: New => In Progress ** Changed in: apport (Ubuntu) Importance: Undecided => High ** Changed in: apport (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) -- 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/1760220 Title: ubuntu-bug with program path says as a snap does not belong to a package Status in apport package in Ubuntu: In Progress Bug description: apport's ui.py file contains the following code: 809 # executable? 810 elif '/' in self.args[0]: 811 pkg = apport.packaging.get_file_package(self.args[0]) 812 if not pkg: 813 optparser.error('%s does not belong to a package.' % self.args[0]) 814 sys.exit(1) 815 self.args = [] 816 self.options.filebug = True 817 self.options.package = pkg This will not provide any useful information about what to do if the 'executable' is provided by a snap. Information similar to https://code.launchpad.net/~juliank/ubuntu/bionic/apport/snap/+merge/342207 should be provided if the path is from a snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1760220/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 997217] Re: salsauthd maxes cpu
Ok, trusty isn't affected because the loop there has an exit clause: + ret = read(s, rbuf+rc, sizeof(rbuf)-rc); + if ( ret<0 ) { + rc = ret; + break; + } else { + if (ret == 0) { + loopc += 1; + } else { + loopc = 0; + } + if (loopc > sizeof(rbuf)) { // arbitrary chosen value + break; + } That comes from trusty's patch named 0034-fix_dovecot_authentication.patch. So trusty does loop for a bit (sizeof(rbuf) is 1000), but won't get stuck. Someone added the loop counter as a safety net, but didn't change the "ret<0" check into "ret<=0" which would also have fixed this. In precise, that same patch (0034) adds the loop, but *without* an exit clause, hence this bug. Xenial is interesting. Upstream at some point adopted the patch that does *NOT* exit the loop, but the code is so similar that someone decided the patch from the package was already applied and dropped it from the package, reintroducing the bug. To add to the confusion, in xenial that patch file was super slightly renamed from 0034_fix_dovecot_authentication.patch to 0034-fix_dovecot_authentication.patch (can you spot what changed?) and got totally different contents: --- cyrus-sasl2.orig/lib/checkpw.c +++ cyrus-sasl2/lib/checkpw.c @@ -587,16 +587,14 @@ static int read_wait(int fd, unsigned de /* Timeout. */ errno = ETIMEDOUT; return -1; - case +1: - if (FD_ISSET(fd, &rfds)) { - /* Success, file descriptor is readable. */ - return 0; - } - return -1; case -1: if (errno == EINTR || errno == EAGAIN) continue; default: + if (FD_ISSET(fd, &rfds)) { + /* Success, file descriptor is readable. */ + return 0; + } /* Error catch-all. */ return -1; } >From bionic onwards, the upstream version has the loop with no loop counter, but it checks read()'s result for <= 0, not just 0, so it's fixed there. Bottom line, only xenial is currently affected (and precise, but precise is EOL). ** Changed in: cyrus-sasl2 (Ubuntu Trusty) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/997217 Title: salsauthd maxes cpu Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Precise: Won't Fix Status in cyrus-sasl2 source package in Trusty: Invalid Status in cyrus-sasl2 source package in Xenial: Triaged Bug description: [Impact] The rimap authentication mechanism in saslauthd can hit a condition where it will start spinning and using all available CPU. This condition can be easily encountered when an authentication is happening and the imap service is being restarted. Furthermore, the saslauthd child process that picked up that authentication request and that is spinning now won't be reaped nor can it service further requests. If all children are left in this state, the authentication service as a whole won't be working anymore. [Test Case] This test can be performed in a LXD or VM. * install the needed packages. mail-stack-delivery is used to have an imap server available on localhost that needs no further configuration. Accept the defaults for all debconf prompts: sudo apt update sudo apt install sasl2-bin mail-stack-delivery * set the password "ubuntu" for the ubuntu user echo ubuntu:ubuntu | sudo chpasswd * start saslauthd like this, with just one child: sudo /usr/sbin/saslauthd -a rimap -O localhost -r -n 1 * restart dovecot sudo service dovecot restart * test saslauthd authentication: $ sudo testsaslauthd -u ubuntu -p ubuntu 0: OK "Success." * Now let's break it. In one terminal watch the output of top: top * in another terminal, run the following: sudo testsaslauthd -u ubuntu -p ubuntu & sleep 1; sudo service dovecot stop * observe in the "top" terminal that saslauthd is consuming a lot of cpu. If that's not happening, try starting dovecot again and adjusting the sleep value in the previous test command, but 1s was enough in all my runs. * start dovecot and repeat the authentication request. Since the only saslauthd child is now spinning, this will block: sudo service dovecot start $ sudo testsaslauthd -u ubuntu -p ubuntu [Regression Potential] * discussion of how regressions are most likely to manifest as a result of this change. * It is assumed that any SRU candidate patch is well-tested before upload and has a low overall risk of regression, but it's important to make the effort to think about what ''could'' happen in the event of a regression. * This both shows the SRU team that the risks have been cons
[Touch-packages] [Bug 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
** Attachment added: "journal output attached" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+attachment/5205033/+files/journal.txt -- 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/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 997217] Re: salsauthd maxes cpu
I'm unable to trigger this bug when running the test case on trusty, even though the same code is there. I also tried adjusting the sleep. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/997217 Title: salsauthd maxes cpu Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Precise: Won't Fix Status in cyrus-sasl2 source package in Trusty: Triaged Status in cyrus-sasl2 source package in Xenial: Triaged Bug description: [Impact] The rimap authentication mechanism in saslauthd can hit a condition where it will start spinning and using all available CPU. This condition can be easily encountered when an authentication is happening and the imap service is being restarted. Furthermore, the saslauthd child process that picked up that authentication request and that is spinning now won't be reaped nor can it service further requests. If all children are left in this state, the authentication service as a whole won't be working anymore. [Test Case] This test can be performed in a LXD or VM. * install the needed packages. mail-stack-delivery is used to have an imap server available on localhost that needs no further configuration. Accept the defaults for all debconf prompts: sudo apt update sudo apt install sasl2-bin mail-stack-delivery * set the password "ubuntu" for the ubuntu user echo ubuntu:ubuntu | sudo chpasswd * start saslauthd like this, with just one child: sudo /usr/sbin/saslauthd -a rimap -O localhost -r -n 1 * restart dovecot sudo service dovecot restart * test saslauthd authentication: $ sudo testsaslauthd -u ubuntu -p ubuntu 0: OK "Success." * Now let's break it. In one terminal watch the output of top: top * in another terminal, run the following: sudo testsaslauthd -u ubuntu -p ubuntu & sleep 1; sudo service dovecot stop * observe in the "top" terminal that saslauthd is consuming a lot of cpu. If that's not happening, try starting dovecot again and adjusting the sleep value in the previous test command. * repeat the authentication request. Since the only saslauthd child is now spinning, this will block: $ sudo testsaslauthd -u ubuntu -p ubuntu [Regression Potential] * discussion of how regressions are most likely to manifest as a result of this change. * It is assumed that any SRU candidate patch is well-tested before upload and has a low overall risk of regression, but it's important to make the effort to think about what ''could'' happen in the event of a regression. * This both shows the SRU team that the risks have been considered, and provides guidance to testers in regression-testing the SRU. [Other Info] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance [Original Description] sasl2-bin version 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu contains a bug that causes heavy cpu utilization, impacting normal operation of one of our mail servers following an upgrade to Ubuntu 12.04. We are running the daemon with the following options: /usr/sbin/saslauthd -a rimap -O our.imap.server -r -m /var/spool/postfix/var/run/saslauthd -n 5 We noticed that users were unable to send mail and that the saslauthd processes were using approximately 100% of each cpu core. An strace of one of the runaway process showed that it was stuck in the following behaviour: select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 . with further inspection showing that the file descriptor in question was a socket connected to our imap server in CLOSE_WAIT. Browsing saslauthd/auth_rimap.c in the source package for sasl2-bin, we came across the following code, repeated in two locations: while( select (fds, &perm, NULL, NULL, &timeout ) >0 ) { if ( FD_ISSET(s, &perm) ) { ret = read(s, rbuf+rc, sizeof(rbuf)-rc); if ( ret<0 ) { rc = ret;
[Touch-packages] [Bug 1773148] Re: /lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate
This bug was fixed in the package systemd - 229-4ubuntu21.5 --- systemd (229-4ubuntu21.5) xenial; urgency=medium [ Dimitri John Ledkov ] * systemctl: correctly proceed to immediate shutdown if scheduling fails (LP: #1670291) * hwdb: update micmute on Dell laptops. (LP: #1738153) * hwdb: Use wlan keycode for all Dell systems. (LP: #1762385) * units: Disable journald Watchdog (LP: #1773148) [ Mauricio Faria de Oliveira ] * core: Fix for service to enter the 'failed' state (rather than 'inactive') after it repeatedly fails restart. (LP: #1795658) [ Dimitri John Ledkov ] * Disable dh_installinit generation of tmpfiles for the systemd package. (LP: #1748147) -- Dimitri John Ledkov Mon, 08 Oct 2018 16:10:42 +0100 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => 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/1773148 Title: /lib/systemd/systemd- journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * systemd aborts journald, upon watchdog expiry and generates lots of crash reports * it appears that journald is simply stuck in fsync * it has been agreed to disable watchdog timer on journald [Test Case] * watch drop-off of errors w.r.t. watchdog timer [Regression Potential] * Potentially journald does get stuck, and thus is no longer automatically restarted with a sigabrt crash. However, so far, it is not known to do that. [Other Info] * Original bug report The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 237-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1773148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670291] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Fix Released Status in landscape-client source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in landscape-client source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773148] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1773148 Title: /lib/systemd/systemd- journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * systemd aborts journald, upon watchdog expiry and generates lots of crash reports * it appears that journald is simply stuck in fsync * it has been agreed to disable watchdog timer on journald [Test Case] * watch drop-off of errors w.r.t. watchdog timer [Regression Potential] * Potentially journald does get stuck, and thus is no longer automatically restarted with a sigabrt crash. However, so far, it is not known to do that. [Other Info] * Original bug report The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 237-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1773148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
This bug was fixed in the package systemd - 229-4ubuntu21.5 --- systemd (229-4ubuntu21.5) xenial; urgency=medium [ Dimitri John Ledkov ] * systemctl: correctly proceed to immediate shutdown if scheduling fails (LP: #1670291) * hwdb: update micmute on Dell laptops. (LP: #1738153) * hwdb: Use wlan keycode for all Dell systems. (LP: #1762385) * units: Disable journald Watchdog (LP: #1773148) [ Mauricio Faria de Oliveira ] * core: Fix for service to enter the 'failed' state (rather than 'inactive') after it repeatedly fails restart. (LP: #1795658) [ Dimitri John Ledkov ] * Disable dh_installinit generation of tmpfiles for the systemd package. (LP: #1748147) -- Dimitri John Ledkov Mon, 08 Oct 2018 16:10:42 +0100 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => 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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Fix Released Status in landscape-client source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in landscape-client source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738153] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1738153 Title: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial Status in OEM Priority Project: Confirmed Status in OEM Priority Project xenial series: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Artful: Won't Fix Bug description: [Impact] dell-wmi expend the scan code of Microphone mute hotkey from 0x150 to 0x100150, so need to add a new mapping for it. related commit: https://github.com/systemd/systemd/pull/5012 [Test Case] 1. install the udev package which applied patch. 2. check if Microphone mute hotkey works. 3. if it not works, please provide the log of evtest. [Regression Potential] low regression potential, because it just add one more mapping. also affect: LP: #1736352 LP: #1740080 LP: #1734609 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1738153/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738153] Re: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial
This bug was fixed in the package systemd - 229-4ubuntu21.5 --- systemd (229-4ubuntu21.5) xenial; urgency=medium [ Dimitri John Ledkov ] * systemctl: correctly proceed to immediate shutdown if scheduling fails (LP: #1670291) * hwdb: update micmute on Dell laptops. (LP: #1738153) * hwdb: Use wlan keycode for all Dell systems. (LP: #1762385) * units: Disable journald Watchdog (LP: #1773148) [ Mauricio Faria de Oliveira ] * core: Fix for service to enter the 'failed' state (rather than 'inactive') after it repeatedly fails restart. (LP: #1795658) [ Dimitri John Ledkov ] * Disable dh_installinit generation of tmpfiles for the systemd package. (LP: #1748147) -- Dimitri John Ledkov Mon, 08 Oct 2018 16:10:42 +0100 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => 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/1738153 Title: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial Status in OEM Priority Project: Confirmed Status in OEM Priority Project xenial series: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Artful: Won't Fix Bug description: [Impact] dell-wmi expend the scan code of Microphone mute hotkey from 0x150 to 0x100150, so need to add a new mapping for it. related commit: https://github.com/systemd/systemd/pull/5012 [Test Case] 1. install the udev package which applied patch. 2. check if Microphone mute hotkey works. 3. if it not works, please provide the log of evtest. [Regression Potential] low regression potential, because it just add one more mapping. also affect: LP: #1736352 LP: #1740080 LP: #1734609 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1738153/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd
This bug was fixed in the package systemd - 229-4ubuntu21.5 --- systemd (229-4ubuntu21.5) xenial; urgency=medium [ Dimitri John Ledkov ] * systemctl: correctly proceed to immediate shutdown if scheduling fails (LP: #1670291) * hwdb: update micmute on Dell laptops. (LP: #1738153) * hwdb: Use wlan keycode for all Dell systems. (LP: #1762385) * units: Disable journald Watchdog (LP: #1773148) [ Mauricio Faria de Oliveira ] * core: Fix for service to enter the 'failed' state (rather than 'inactive') after it repeatedly fails restart. (LP: #1795658) [ Dimitri John Ledkov ] * Disable dh_installinit generation of tmpfiles for the systemd package. (LP: #1748147) -- Dimitri John Ledkov Mon, 08 Oct 2018 16:10:42 +0100 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => 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/1748147 Title: [SRU] debhelper support override from /etc/tmpfiles.d for systemd Status in debhelper: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in rsyslog package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in debhelper source package in Xenial: Won't Fix Status in rsyslog source package in Xenial: Invalid Status in systemd source package in Xenial: Fix Released Status in debhelper source package in Artful: Won't Fix Status in rsyslog source package in Artful: Invalid Status in systemd source package in Artful: Won't Fix Status in debhelper source package in Bionic: Won't Fix Status in rsyslog source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Released Bug description: [Impact] /var/log's Permission is going back to 755 after upgrading systemd if rsyslog is installed (default) [Resolution] Ensure that dh_installinit does not "helpfully" generate partial systemd-tmpfiles snippets in systemd package postinst. Ensure that a generic systemd-tmpfiles call is done in systemd postinst, which takes into account /all/ configurations, not just some. [Regression Potential] * This fix was already tested in bionic and works well there. * Bad autogenerated calls to systemd-tmpfiles are removed from systemd postinst, and replaced by a call that takes all configs into account, thus this is a very safe thing to do - and simply repeats what is done on boot, thus is as safe as it gets. [Test Case] 1. Launch xenila container 2. ls -latr /var 3. apt install --reinstall systemd 4. ls -latr /var The ownership, group and permissions for /var/log should remain the same. To manage notifications about this bug go to: https://bugs.launchpad.net/debhelper/+bug/1748147/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes
This bug was fixed in the package systemd - 229-4ubuntu21.5 --- systemd (229-4ubuntu21.5) xenial; urgency=medium [ Dimitri John Ledkov ] * systemctl: correctly proceed to immediate shutdown if scheduling fails (LP: #1670291) * hwdb: update micmute on Dell laptops. (LP: #1738153) * hwdb: Use wlan keycode for all Dell systems. (LP: #1762385) * units: Disable journald Watchdog (LP: #1773148) [ Mauricio Faria de Oliveira ] * core: Fix for service to enter the 'failed' state (rather than 'inactive') after it repeatedly fails restart. (LP: #1795658) [ Dimitri John Ledkov ] * Disable dh_installinit generation of tmpfiles for the systemd package. (LP: #1748147) -- Dimitri John Ledkov Mon, 08 Oct 2018 16:10:42 +0100 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => 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/1762385 Title: dell_wmi: Unknown key codes Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Bogus keycode messages produced by the kernel / user annoyance * rfkill keyboard shortcuts not working as intended on some Dell machines [Test Case] * check that there are no spurious kernel messages about unknown keys in journalctl upon RFKill key presses * check that RFKill key presses work correctly and kill/restore RF capabilities [Regression Potential] * The change is scoped to particular SKUs and thus should only affect them * It is related to matching gsd support, which is in-place on xenial and up [Solution] Cherrypick upstream commit https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f [Original Bug report] RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86 /dell-wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1762385/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795658] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1795658 Title: xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently Status in systemd package in Ubuntu: Invalid Status in systemd source package in Xenial: Fix Released Bug description: [Impact] * In case a service unit has repeatedly failed to restart, it should be reported as 'failed' permanently, but currently it's instead reported as 'inactive'. * System monitoring tools that evaluate the status of systemd service units and act upon it (for example: restart service, report permanent failure) are currently misled by information in 'systemctl status .service'. * System management tools based on such information may take wrong and/or sub-optimal actions in the managed systems regarding such service units. * This systemd patch [1] directly addresses this issue (see systemd github PR #3166 [2]), and its code is still effectice in upstream systemd today, without further fixes/changes (the only changes were in doc text and the busname files that were removed, but still without further fixes to this). [Test Case] * This is copied from systemd PR #3166 [2]. * This has been tested by a customer as well, and with its system monitoring and management solution, for interoperability verification. $ cat
[Touch-packages] [Bug 1795658] Re: xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently
This bug was fixed in the package systemd - 229-4ubuntu21.5 --- systemd (229-4ubuntu21.5) xenial; urgency=medium [ Dimitri John Ledkov ] * systemctl: correctly proceed to immediate shutdown if scheduling fails (LP: #1670291) * hwdb: update micmute on Dell laptops. (LP: #1738153) * hwdb: Use wlan keycode for all Dell systems. (LP: #1762385) * units: Disable journald Watchdog (LP: #1773148) [ Mauricio Faria de Oliveira ] * core: Fix for service to enter the 'failed' state (rather than 'inactive') after it repeatedly fails restart. (LP: #1795658) [ Dimitri John Ledkov ] * Disable dh_installinit generation of tmpfiles for the systemd package. (LP: #1748147) -- Dimitri John Ledkov Mon, 08 Oct 2018 16:10:42 +0100 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => 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/1795658 Title: xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently Status in systemd package in Ubuntu: Invalid Status in systemd source package in Xenial: Fix Released Bug description: [Impact] * In case a service unit has repeatedly failed to restart, it should be reported as 'failed' permanently, but currently it's instead reported as 'inactive'. * System monitoring tools that evaluate the status of systemd service units and act upon it (for example: restart service, report permanent failure) are currently misled by information in 'systemctl status .service'. * System management tools based on such information may take wrong and/or sub-optimal actions in the managed systems regarding such service units. * This systemd patch [1] directly addresses this issue (see systemd github PR #3166 [2]), and its code is still effectice in upstream systemd today, without further fixes/changes (the only changes were in doc text and the busname files that were removed, but still without further fixes to this). [Test Case] * This is copied from systemd PR #3166 [2]. * This has been tested by a customer as well, and with its system monitoring and management solution, for interoperability verification. $ cat
[Touch-packages] [Bug 1799038] Re: Ubuntu 18.10 does not suspend on lid close
In journalctl I found that whenever the machine reached suspend target, ACPI kicked in to wake the machine again. kernel: ACPI: Low-level resume complete Today, I put the machine to sleep (using the alt option on the shutdown menu). The machine woke up every two seconds and went to sleep again (for over half an hour). Finally and for no obvious reason, the machine kept sleeping until I woke it up 3 hours later. Weired -- 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/1799038 Title: Ubuntu 18.10 does not suspend on lid close Status in systemd package in Ubuntu: New Bug description: After an upgrade to Ubuntu 18.10 suspend to RAM due to closing the lid on notebooks does not work any more. The machine goes to suspend mode but wakes up immediately due to some events (can be network, or others). In 18.04 this issue was fixed (we had the same situation with any version since 14.04). Seems a regression. Mitigation reports suggesting to change /etc/systemd/logind.conf are WRONG. The changes do NOTHING. One might spare the time to experiment. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 11:55:48 2018 InstallationDate: Installed on 2018-04-30 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.systemd.logind.conf: 2018-10-20T22:01:57.469491 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799038/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 997217] Re: salsauthd maxes cpu
** Description changed: [Impact] The rimap authentication mechanism in saslauthd can hit a condition where it will start spinning and using all available CPU. This condition can be easily encountered when an authentication is happening and the imap service is being restarted. - - Once the saslauthd daemon enters this loop, it stops responding to - authentication requests. [Test Case] This test can be performed in a LXD or VM. * install the needed packages. mail-stack-delivery is used to have an imap server available on localhost that needs no further configuration. Accept the defaults for all debconf prompts: sudo apt update sudo apt install sasl2-bin mail-stack-delivery * set the password "ubuntu" for the ubuntu user echo ubuntu:ubuntu | sudo chpasswd * start saslauthd like this: sudo /usr/sbin/saslauthd -a rimap -O localhost -r -n 5 * restart dovecot sudo service dovecot restart * test saslauthd authentication: $ sudo testsaslauthd -u ubuntu -p ubuntu 0: OK "Success." * Now let's break it. In one terminal watch the output of top: top * in another terminal, run the following: sudo testsaslauthd -u ubuntu -p ubuntu & sleep 1; sudo service dovecot stop * observe in the "top" terminal that saslauthd is consuming a lot of cpu. If that's not happening, try starting dovecot again and adjusting the sleep value in the previous test command. - - * Try authenticating again, while saslauthd is spinning. It should fail: - $ sudo testsaslauthd -u ubuntu -p ubuntu - 0: NO "authentication failed" [Regression Potential] * discussion of how regressions are most likely to manifest as a result of this change. * It is assumed that any SRU candidate patch is well-tested before upload and has a low overall risk of regression, but it's important to make the effort to think about what ''could'' happen in the event of a regression. * This both shows the SRU team that the risks have been considered, and provides guidance to testers in regression-testing the SRU. [Other Info] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance [Original Description] sasl2-bin version 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu contains a bug that causes heavy cpu utilization, impacting normal operation of one of our mail servers following an upgrade to Ubuntu 12.04. We are running the daemon with the following options: /usr/sbin/saslauthd -a rimap -O our.imap.server -r -m /var/spool/postfix/var/run/saslauthd -n 5 We noticed that users were unable to send mail and that the saslauthd processes were using approximately 100% of each cpu core. An strace of one of the runaway process showed that it was stuck in the following behaviour: select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 . with further inspection showing that the file descriptor in question was a socket connected to our imap server in CLOSE_WAIT. Browsing saslauthd/auth_rimap.c in the source package for sasl2-bin, we came across the following code, repeated in two locations: while( select (fds, &perm, NULL, NULL, &timeout ) >0 ) { if ( FD_ISSET(s, &perm) ) { ret = read(s, rbuf+rc, sizeof(rbuf)-rc); if ( ret<0 ) { rc = ret; break; } else { rc += ret; } } } It looks like this loop is expected to run until a read error is encountered or the timeout of 1 second is reached. There is no test to check that 0 bytes were read, indicating that the connection was closed by the remote peer. Since select() will immediately return the size of the set of the partially closed descriptor (1, which is >0), and calls to read() will always yield 0 bytes, there's the potential for execution to get stuck in this non blocking loop and I'm presuming that that's what's happening here. We've not performed any further analysis to prove that this is really w
[Touch-packages] [Bug 1642863] Re: Upgrading unattended-upgrades gives errors and a warning
Debconf executes scripts from /tmp by default but you can try continuing securing the system by changing apt's temp file configuration: https://serverfault.com/questions/72356/how-useful-is-mounting-tmp-noexec Anyway this is definitely not a bug in u-u, maybe a wishlist one for debconf. ** Changed in: unattended-upgrades (Ubuntu) Importance: Low => Wishlist ** Package changed: unattended-upgrades (Ubuntu) => debconf (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1642863 Title: Upgrading unattended-upgrades gives errors and a warning Status in debconf package in Ubuntu: Confirmed Bug description: Ubuntu release == Description: Ubuntu 16.04.1 LTS Release: 16.04 Package version === unattended-upgrades: Installed: 0.90ubuntu0.2 Candidate: 0.90ubuntu0.2 Version table: *** 0.90ubuntu0.2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 0.90 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages What I expected to happen = No error or warning messages during a software upgrade. What happened instead = When an updated version of unattended-upgrades is installed, the following error messages appear because /tmp is mounted noexec for security reasons (see the Securing Debian Manual, section 4.10 at https://www.debian.org/doc/manuals/securing-debian- howto/ch4.en.html#s4.10): Preconfiguring packages ... Can't exec "/tmp/unattended-upgrades.config.5svL0F": Permission denied at /usr/share/perl/5.22/IPC/Open3.pm line 178. open2: exec of /tmp/unattended-upgrades.config.5svL0F configure 0.90ubuntu0.1 failed at /usr/share/perl5/Debconf/ConfModule.pm line 59. Also, the following warning occurs later on: Setting up unattended-upgrades (0.90ubuntu0.2) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.2 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 18 02:36:54 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-01 (17 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "0"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "1"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-11-07T13:58:08.805628 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1642863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 997217] Re: salsauthd maxes cpu
** Description changed: [Impact] - * An explanation of the effects of the bug on users and + The rimap authentication mechanism in saslauthd can hit a condition + where it will start spinning and using all available CPU. This condition + can be easily encountered when an authentication is happening and the + imap service is being restarted. - * justification for backporting the fix to the stable release. - - * In addition, it is helpful, but not required, to include an -explanation of how the upload fixes this bug. + Once the saslauthd daemon enters this loop, it stops responding to + authentication requests. [Test Case] - * detailed instructions how to reproduce the bug + This test can be performed in a LXD or VM. - * these should allow someone who is not familiar with the affected -package to reproduce the bug and verify that the updated package fixes -the problem. + * install the needed packages. mail-stack-delivery is used to have an + imap server available on localhost that needs no further configuration. + Accept the defaults for all debconf prompts: + + sudo apt update + sudo apt install sasl2-bin mail-stack-delivery + + * set the password "ubuntu" for the ubuntu user + echo ubuntu:ubuntu | sudo chpasswd + + * start saslauthd like this: + sudo /usr/sbin/saslauthd -a rimap -O localhost -r -n 5 + + * restart dovecot + sudo service dovecot restart + + * test saslauthd authentication: + $ sudo testsaslauthd -u ubuntu -p ubuntu + 0: OK "Success." + + * Now let's break it. In one terminal watch the output of top: + top + + * in another terminal, run the following: + sudo testsaslauthd -u ubuntu -p ubuntu & sleep 1; sudo service dovecot stop + + * observe in the "top" terminal that saslauthd is consuming a lot of + cpu. If that's not happening, try starting dovecot again and adjusting + the sleep value in the previous test command. + + * Try authenticating again, while saslauthd is spinning. It should fail: + $ sudo testsaslauthd -u ubuntu -p ubuntu + 0: NO "authentication failed" + [Regression Potential] - * discussion of how regressions are most likely to manifest as a result + * discussion of how regressions are most likely to manifest as a result of this change. - * It is assumed that any SRU candidate patch is well-tested before -upload and has a low overall risk of regression, but it's important -to make the effort to think about what ''could'' happen in the -event of a regression. + * It is assumed that any SRU candidate patch is well-tested before + upload and has a low overall risk of regression, but it's important + to make the effort to think about what ''could'' happen in the + event of a regression. - * This both shows the SRU team that the risks have been considered, -and provides guidance to testers in regression-testing the SRU. + * This both shows the SRU team that the risks have been considered, + and provides guidance to testers in regression-testing the SRU. [Other Info] - - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance [Original Description] sasl2-bin version 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu contains a bug that causes heavy cpu utilization, impacting normal operation of one of our mail servers following an upgrade to Ubuntu 12.04. We are running the daemon with the following options: /usr/sbin/saslauthd -a rimap -O our.imap.server -r -m /var/spool/postfix/var/run/saslauthd -n 5 We noticed that users were unable to send mail and that the saslauthd processes were using approximately 100% of each cpu core. An strace of one of the runaway process showed that it was stuck in the following behaviour: select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 . with further inspection showing that the file descriptor in question was a socket connected to our imap server
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Found this opened report related to the nvidia driver https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1795808 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799764] [NEW] python3-lib2to3 is not installable with python3
Public bug reported: python3 from python3-defaults is 3.6.5-3ubuntu1 python3-lib2to3 from python3-stdlib-extensions Depends: python3 (>= 3.6.6-1~) Either python3-stdlib-extensions dep should be lowered, or python3-defaults should be rebuilt. ** Affects: python3-defaults (Ubuntu) Importance: Undecided Assignee: Matthias Klose (doko) Status: New ** Affects: python3-stdlib-extensions (Ubuntu) Importance: Undecided Assignee: Matthias Klose (doko) Status: New ** Also affects: python3-stdlib-extensions (Ubuntu) Importance: Undecided Status: New ** Changed in: python3-defaults (Ubuntu) Assignee: (unassigned) => Matthias Klose (doko) ** Changed in: python3-stdlib-extensions (Ubuntu) Assignee: (unassigned) => Matthias Klose (doko) -- 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/1799764 Title: python3-lib2to3 is not installable with python3 Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: New Bug description: python3 from python3-defaults is 3.6.5-3ubuntu1 python3-lib2to3 from python3-stdlib-extensions Depends: python3 (>= 3.6.6-1~) Either python3-stdlib-extensions dep should be lowered, or python3-defaults should be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1799764/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 997217] Re: salsauthd maxes cpu
** Description changed: + [Impact] + + * An explanation of the effects of the bug on users and + + * justification for backporting the fix to the stable release. + + * In addition, it is helpful, but not required, to include an +explanation of how the upload fixes this bug. + + [Test Case] + + * detailed instructions how to reproduce the bug + + * these should allow someone who is not familiar with the affected +package to reproduce the bug and verify that the updated package fixes +the problem. + + [Regression Potential] + + * discussion of how regressions are most likely to manifest as a result + of this change. + + * It is assumed that any SRU candidate patch is well-tested before +upload and has a low overall risk of regression, but it's important +to make the effort to think about what ''could'' happen in the +event of a regression. + + * This both shows the SRU team that the risks have been considered, +and provides guidance to testers in regression-testing the SRU. + + [Other Info] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance + + + [Original Description] + sasl2-bin version 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu contains a bug that causes heavy cpu utilization, impacting normal operation of one of our mail servers following an upgrade to Ubuntu 12.04. We are running the daemon with the following options: /usr/sbin/saslauthd -a rimap -O our.imap.server -r -m /var/spool/postfix/var/run/saslauthd -n 5 - - We noticed that users were unable to send mail and that the saslauthd processes were using approximately 100% of each cpu core. An strace of one of the runaway process showed that it was stuck in the following behaviour: + We noticed that users were unable to send mail and that the saslauthd + processes were using approximately 100% of each cpu core. An strace of + one of the runaway process showed that it was stuck in the following + behaviour: select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0}) read(8, "", 940)= 0 . - - with further inspection showing that the file descriptor in question was a socket connected to our imap server in CLOSE_WAIT. + with further inspection showing that the file descriptor in question was + a socket connected to our imap server in CLOSE_WAIT. Browsing saslauthd/auth_rimap.c in the source package for sasl2-bin, we came across the following code, repeated in two locations: while( select (fds, &perm, NULL, NULL, &timeout ) >0 ) { -if ( FD_ISSET(s, &perm) ) { - ret = read(s, rbuf+rc, sizeof(rbuf)-rc); - if ( ret<0 ) { - rc = ret; - break; - } else { - rc += ret; - } -} - } + if ( FD_ISSET(s, &perm) ) { + ret = read(s, rbuf+rc, sizeof(rbuf)-rc); + if ( ret<0 ) { + rc = ret; + break; + } else { + rc += ret; + } + } + } - - It looks like this loop is expected to run until a read error is encountered or the timeout of 1 second is reached. There is no test to check that 0 bytes were read, indicating that the connection was closed by the remote peer. Since select() will immediately return the size of the set of the partially closed descriptor (1, which is >0), and calls to read() will always yield 0 bytes, there's the potential for execution to get stuck in this non blocking loop and I'm presuming that that's what's happening here. + It looks like this loop is expected to run until a read error is + encountered or the timeout of 1 second is reached. There is no test to + check that 0 bytes were read, indicating that the connection was closed + by the remote peer. Since select() will immediately return the size of + the set of the partially closed descriptor (1, which is >0), and calls + to read() will always yield 0 bytes, there's the potential for execution + to get stuck in this non blocking loop and I'm presuming that that's + what's hap
[Touch-packages] [Bug 1583537] Re: systemd shutdown writes non-error message to stderr - causes email to be sent despite 'MailOnlyOnError'
I agree that it should be fixed in u-u. Patches are welcome. ** Changed in: unattended-upgrades (Ubuntu) Importance: Medium => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1583537 Title: systemd shutdown writes non-error message to stderr - causes email to be sent despite 'MailOnlyOnError' Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: Calling unattended-upgrade from cron with an Unattended-Upgrade ::Automatic-Reboot-Time of "+5". This causes unattended-upgrades to run: '/sbin/shutdown -r +5' Systemd's shutdown writes an acknowledgement message to stderr: Shutdown scheduled for Wed 2016-05-18 04:37:49 BST, use 'shutdown -c' to cancel. Which cron picks up and emails - but I don't really want to know. Is there any scope for unattended-upgrades to gobble shutdown's stderr message? Or, perhaps this should be logged against systemd, since the shutdown message isn't really an obvious candidate for stderr? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu May 19 11:14:14 2016 PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1583537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599646] Re: E-mail report contains repeated "Reading database ... NN%" lines
Fixed in this commit: https://github.com/mvo5/unattended- upgrades/commit/7c5e5476711fab6b9977116792262e16efe626ec ** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1599646 Title: E-mail report contains repeated "Reading database ... NN%" lines Status in unattended-upgrades package in Ubuntu: Fix Committed Status in apt package in Debian: New Bug description: This concerns unattended-upgrades 0.90 in Xenial. Here is an excerpt from an e-mail report sent out by u-u after the upgrade process is completed: Package installation log: Log started: 2016-07-06 17:24:21 Preconfiguring packages ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 314949 files and directories currently installed.) Preparing to unpack .../tzdata_2016f-0ubuntu0.16.04_all.deb ... Unpacking tzdata (2016f-0ubuntu0.16.04) over (2016d-0ubuntu0.16.04) ... Preparing to unpack .../libgimp2.0_2.8.16-1ubuntu1.1_i386.deb ... All but the last "Reading database ..." line should be elided from the message. As a matter of fact, those lines do not appear in messages mailed out from current Trusty systems (u-u version 0.82.1ubuntu2.4), so this appears to be a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1599646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799738] Re: dose not work rite
** 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/1799738 Title: dose not work rite Status in xorg package in Ubuntu: New Bug description: dose not work rite ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Oct 24 11:36:58 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:fde0] Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated Graphics Controller [1179:fde0] InstallationDate: Installed on 2018-03-07 (231 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: TOSHIBA Satellite C655 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=61e48a6a-7e5a-4c7e-aa64-e126e56af5b5 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 1.70 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.70:bd07/07/2011:svnTOSHIBA:pnSatelliteC655:pvrPSC08U-03C01K:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Satellite C655 dmi.product.sku: Montevina_Fab dmi.product.version: PSC08U-03C01K dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 xserver.bootTime: Sat Mar 17 11:24:42 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5760 vendor CMO xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1525469] Re: package unattended-upgrades 0.82.1ubuntu2.4 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
Reassigning to update-manager since it started the installation, u-u does not seem to be at fault here. ** Package changed: unattended-upgrades (Ubuntu) => update-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1525469 Title: package unattended-upgrades 0.82.1ubuntu2.4 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) Status in update-manager package in Ubuntu: Confirmed Bug description: Installer hung, so I killed it. `ps -eFHw` beforehand said: root 22667 21419 0 1828 5180 1 09:14 pts/20 00:00:00 /usr/bin/dpkg --status-fd 54 --configure ntpdate:i386 libgstreamer-plugins-base1.0-0:i386 python-apt-common:all python3-apt:i386 gnome-desktop3-data:all libgnome-desktop-3-7:i386 gir1.2-gnomedesktop-3.0:i386 gir1.2-gst-plugins-base-1.0:i386 grub-common:i386 grub2-common:i386 grub-pc-bin:i386 grub-pc:i386 gstreamer1.0-alsa:i386 gstreamer1.0-plugins-base:i386 gstreamer1.0-plugins-base-apps:i386 gstreamer1.0-x:i386 python-apt:i386 unattended-upgrades:all root 30641 22667 0 566 556 1 21:41 pts/20 00:00:00 /bin/sh /var/lib/dpkg/info/libc-bin.postinst triggered ldconfig root 30642 30641 0 274 440 1 21:41 pts/20 00:00:00 /sbin/ldconfig.real ProblemType: Package DistroRelease: Ubuntu 14.04 Package: unattended-upgrades 0.82.1ubuntu2.4 ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29 Uname: Linux 3.13.0-71-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Fri Dec 11 21:41:43 2015 DuplicateSignature: package:unattended-upgrades:0.82.1ubuntu2.4:subprocess installed post-installation script was killed by signal (Terminated) ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2014-12-01 (376 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.10 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.82.1ubuntu2.4 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1525469/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778946] Re: No dns resolution after closing a vpn/pptp connection
** Also affects: openvpn-systemd-resolved (Ubuntu) Importance: Undecided Status: New ** No longer affects: openvpn-systemd-resolved (Ubuntu) -- 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/1778946 Title: No dns resolution after closing a vpn/pptp connection Status in network-manager package in Ubuntu: Confirmed Bug description: step to reproduce set a VPN connection configured to connect a Microsoft vpn server (pptp) internet acces is ok enable the vpn connection using the applet on the top right corner of the desktop internet still ok ping works disable the vpn connection ping doesn't works with a host but works if i specify an ip address ping: xx.net: Nom ou service inconnu As a workaround, i disable the ethernet link and re-enable it name resolution is now ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 18:09:30 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-06-03 (1484 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.0.254 dev eth0 proto dhcp metric 20100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Connexion filaire 1 94806bba-1c68-46b6-87f4-a3aff6dd /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799206] Re: SRU: update python3.6 to the new minor release 3.6.7
** Also affects: python3-defaults (Ubuntu) Importance: Undecided Status: New -- 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/1799206 Title: SRU: update python3.6 to the new minor release 3.6.7 Status in python3-defaults package in Ubuntu: New Status in python3.6 package in Ubuntu: Fix Committed Status in python3-defaults source package in Bionic: New Status in python3.6 source package in Bionic: Fix Committed Status in python3-defaults source package in Cosmic: New Status in python3.6 source package in Cosmic: Fix Committed Bug description: SRU: update python3.6 to the new minor release 3.6.7 See LP: #1792143 for the rationale, going one minor release ahead (and planning to do 3.6.8 in January, the last source release from the 3.6 branch). [Impact] Provide the branch updates for the stable 3.6 branch in the LTS release. [Regression Potential] There is regression potential, but this version is in use in 18.10, which didn't show regressions. [Test Case] No regressions in the Python 3.6 test suite, no regressions in the autopkg tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1799206/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1528054] Re: package linux-image-4.2.0-22-generic 4.2.0-22.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/unattended-upgrades exited with return code 1
It is quite strange but it is not an unattended-upgrades bug. Do you still observe it? ** Changed in: unattended-upgrades (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1528054 Title: package linux-image-4.2.0-22-generic 4.2.0-22.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/unattended-upgrades exited with return code 1 Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: I don't know if this related but after this bug occurred every file that I'm saving in any folder is automatically saved as a duplicate in my home folder Thanks for looking , Cheers ProblemType: Package DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-22-generic 4.2.0-22.27 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1200 F pulseaudio m-p2062 F pulseaudio /dev/snd/controlC1: gdm1200 F pulseaudio m-p2062 F pulseaudio Date: Sat Dec 19 11:01:07 2015 DuplicateSignature: package:linux-image-4.2.0-22-generic:4.2.0-22.27:run-parts: /etc/kernel/postinst.d/unattended-upgrades exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/unattended-upgrades exited with return code 1 HibernationDevice: RESUME=UUID=b5646ccc-d6c8-4100-a060-2b1fb4c067be InstallationDate: Installed on 2015-10-04 (76 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic root=UUID=64078dfd-6879-48e5-af45-df8a0b10d603 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-29ubuntu0.2 RfKill: SourcePackage: unattended-upgrades Title: package linux-image-4.2.0-22-generic 4.2.0-22.27 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/unattended-upgrades exited with return code 1 UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0409 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-I dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0409:bd05/31/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-I:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1528054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1543926] Re: package unattended-upgrades 0.86.2ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
This is a bug in smfpd, which is not packaged in Ubuntu. https://www.keypressure.com/blog/what-is-smfpd/ ** Changed in: unattended-upgrades (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1543926 Title: package unattended-upgrades 0.86.2ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in unattended-upgrades package in Ubuntu: Invalid Bug description: it is take by the ipdate. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: unattended-upgrades 0.86.2ubuntu1.1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic i686 ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 Date: Tue Feb 9 07:40:49 2016 DuplicateSignature: package:unattended-upgrades:0.86.2ubuntu1.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-01-23 (17 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.86.2ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1543926/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797415] Re: DNS stops working when disconnecting PPTP VPN on desktop
*** This bug is a duplicate of bug 1778946 *** https://bugs.launchpad.net/bugs/1778946 Yeah, I think so. Thanks. ** This bug has been marked a duplicate of bug 1778946 No dns resolution after closing a vpn/pptp connection -- 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/1797415 Title: DNS stops working when disconnecting PPTP VPN on desktop Status in systemd package in Ubuntu: New Bug description: On Cosmic I was testing some VPN setups. I created a PPTP VPN connection to my server. Everything connected and worked as it should. When I disconnect the VPN, DNS resolution stops working. Looking at "systemd-resolve --status" shows that the correct DNS server is listed for the interface when the connection is torn down, and I can ping it. Doing a nslookup setting the server to the IP address shown in --status shows that DNS resolution is working correctly. resolv.conf says nameserver 127.0.0.53 Restart resolved makes things work again. (Also, restarting Network Manager makes it work again.) Trying to ping a hostname from the cli when in the broken state yields zero output from resolved logs when in debug mode. Almost like it's not even hitting resolved, so this bug could very well be somewhere else. I've checked, and I can ping 127.0.0.1 and the default routes look OK, although there is a route to the VPN server left over. I'm all out of ideas. Any ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1315559] Re: UpgradeStatus can be incorrect
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1315559 Title: UpgradeStatus can be incorrect Status in apport package in Ubuntu: Confirmed Bug description: In the general hook for ubuntu there is the following code: log = '/var/log/dist-upgrade/main.log' if os.path.exists(log): mtime = os.stat(log).st_mtime human_mtime = time.strftime('%Y-%m-%d', time.gmtime(mtime)) delta = time.time() - mtime # Would be nice if this also showed which release was originally installed report['UpgradeStatus'] = 'Upgraded to %s on %s (%d days ago)' % (release_codename, human_mtime, delta / 86400) else: report['UpgradeStatus'] = 'No upgrade log present (probably fresh install)' This does no checking of main.log to see if the upgrade was actually successful, so if someone is reporting a bug about a failed upgrade of ubuntu-release-upgrader they'll have a confusing 'UpgradeStatus' of today for the previous release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1315559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes
Either this change will make the rfkill button work (good), or not (current behaviour). Given the code paths, validating similar SKUs for non-regression is a good enough confidence level that this change doesn't regress other/unrelated machines. It's a low risk to accept this change as is, because the worst case scenario is a no-change in behaviour. The upside is that it may have fixed rfkill button. Also if this change doesn't fix the rfkill buttons on these laptops, it would imply that later releases and upstream master are also still broken and unfixed. -- 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/1762385 Title: dell_wmi: Unknown key codes Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Bogus keycode messages produced by the kernel / user annoyance * rfkill keyboard shortcuts not working as intended on some Dell machines [Test Case] * check that there are no spurious kernel messages about unknown keys in journalctl upon RFKill key presses * check that RFKill key presses work correctly and kill/restore RF capabilities [Regression Potential] * The change is scoped to particular SKUs and thus should only affect them * It is related to matching gsd support, which is in-place on xenial and up [Solution] Cherrypick upstream commit https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f [Original Bug report] RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86 /dell-wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1762385/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689756] Re: package unattended-upgrades 0.90ubuntu0.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29
** Package changed: unattended-upgrades (Ubuntu) => flashplugin-nonfree (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1689756 Title: package unattended-upgrades 0.90ubuntu0.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 Status in flashplugin-nonfree package in Ubuntu: Confirmed Bug description: nothink to add ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.5 ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed May 10 11:25:10 2017 DuplicateSignature: package:unattended-upgrades:0.90ubuntu0.5 Setting up flashplugin-installer (25.0.0.171ubuntu0.16.04.1) ... Can't locate object method "new" via package "Text::Iconv" (perhaps you forgot to load "Text::Iconv"?) at /usr/lib/perl5/5.22.1/Debconf/Encoding.pm line 65. dpkg: error processing package flashplugin-installer (--configure): subprocess installed post-installation script returned error exit status 29 ErrorMessage: subprocess installed post-installation script returned error exit status 29 InstallationDate: Installed on 2017-04-01 (39 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-04-01T21:54:17.006906 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1689756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797415] Re: DNS stops working when disconnecting PPTP VPN on desktop
is this a duplicate of https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1778946 ? -- 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/1797415 Title: DNS stops working when disconnecting PPTP VPN on desktop Status in systemd package in Ubuntu: New Bug description: On Cosmic I was testing some VPN setups. I created a PPTP VPN connection to my server. Everything connected and worked as it should. When I disconnect the VPN, DNS resolution stops working. Looking at "systemd-resolve --status" shows that the correct DNS server is listed for the interface when the connection is torn down, and I can ping it. Doing a nslookup setting the server to the IP address shown in --status shows that DNS resolution is working correctly. resolv.conf says nameserver 127.0.0.53 Restart resolved makes things work again. (Also, restarting Network Manager makes it work again.) Trying to ping a hostname from the cli when in the broken state yields zero output from resolved logs when in debug mode. Almost like it's not even hitting resolved, so this bug could very well be somewhere else. I've checked, and I can ping 127.0.0.1 and the default routes look OK, although there is a route to the VPN server left over. I'm all out of ideas. Any ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470111] Re: package unattended-upgrades 0.83.6ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
The broken dcservice file is not part of Ubuntu. If you still experience the issue please track down the origin and open a bug there. @colan Apport directed you there because it had no better idea, but it is just a script doing pre-processing of crashes. ** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1470111 Title: package unattended-upgrades 0.83.6ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: While new updates were installing, this one update would not install. Issues preventing it to install. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: unattended-upgrades 0.83.6ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 Date: Tue Jun 30 09:22:08 2015 DuplicateSignature: package:unattended-upgrades:0.83.6ubuntu1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-06-22 (7 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.83.6ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1470111/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318834] Re: Applications can no longer access your @gmail.com Online Account
** Description changed: IN start UBUNTU Application can no longer access your dumetz1...@gmail.com Online - Account. Choose online Accounts from the user menu to reinstale access + Account. Choose online Accounts from the user menu to reinstate access to this account. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-control-center- signon in Ubuntu. https://bugs.launchpad.net/bugs/1318834 Title: Applications can no longer access your @gmail.com Online Account Status in gnome-control-center-signon package in Ubuntu: Confirmed Bug description: IN start UBUNTU Application can no longer access your dumetz1...@gmail.com Online Account. Choose online Accounts from the user menu to reinstate access to this account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1318834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777615] Re: OKULAR - can't set print default to duplex
It should be linked/merged to this bug: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173 ** Also affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1777615 Title: OKULAR - can't set print default to duplex Status in okular package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: New Bug description: I filed this bug report with KDE: https://bugs.kde.org/show_bug.cgi?id=395517 They suggested "What you can try to do is open a bug against Ubuntu and ask whether they can backport the commit mentioned in comment 1 to the Qt version in Ubuntu 18.04... " https://wiki.qt.io/Qt_5.12_Release https://codereview.qt-project.org/#/c/226881/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: okular 4:17.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Tue Jun 19 11:57:15 2018 InstallationDate: Installed on 2018-06-15 (3 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: okular UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/okular/+bug/1777615/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes
Thanks. I think that's sufficient justification. -- 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/1762385 Title: dell_wmi: Unknown key codes Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Bogus keycode messages produced by the kernel / user annoyance * rfkill keyboard shortcuts not working as intended on some Dell machines [Test Case] * check that there are no spurious kernel messages about unknown keys in journalctl upon RFKill key presses * check that RFKill key presses work correctly and kill/restore RF capabilities [Regression Potential] * The change is scoped to particular SKUs and thus should only affect them * It is related to matching gsd support, which is in-place on xenial and up [Solution] Cherrypick upstream commit https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f [Original Bug report] RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86 /dell-wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1762385/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738153] Re: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial
Thanks. Out of band Dimitri explained to me that "unknown" isn't really a mapping, which I think is key. -- 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/1738153 Title: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial Status in OEM Priority Project: Confirmed Status in OEM Priority Project xenial series: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd source package in Artful: Won't Fix Bug description: [Impact] dell-wmi expend the scan code of Microphone mute hotkey from 0x150 to 0x100150, so need to add a new mapping for it. related commit: https://github.com/systemd/systemd/pull/5012 [Test Case] 1. install the udev package which applied patch. 2. check if Microphone mute hotkey works. 3. if it not works, please provide the log of evtest. [Regression Potential] low regression potential, because it just add one more mapping. also affect: LP: #1736352 LP: #1740080 LP: #1734609 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1738153/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720364] Re: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS
*** This bug is a duplicate of bug 1683383 *** https://bugs.launchpad.net/bugs/1683383 The same on Ubuntu 18.04 LTS with Gnome. -- 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/1720364 Title: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS Status in MATE Desktop: New Status in ubuntu-mate: New Status in X.Org X server: Confirmed Status in marco package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Status in xorg-hwe-16.04 package in Ubuntu: Confirmed Status in xorg package in Debian: New Bug description: Steps to reproduce: 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 17.10 or 18.04 LTS. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: 1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: marco 1.18.1-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu1 Architecture: i386 CurrentDesktop: MATE Date: Fri Sep 29 16:18:02 2017 InstallationDate: Installed on 2017-08-26 (33 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) SourcePackage: marco UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1720364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777615] Re: OKULAR - can't set print default to duplex
*** This bug is a duplicate of bug 1776173 *** https://bugs.launchpad.net/bugs/1776173 ** This bug has been marked a duplicate of bug 1776173 qt print dialog shipped with bionic ignores printer defaults -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1777615 Title: OKULAR - can't set print default to duplex Status in okular package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: New Bug description: I filed this bug report with KDE: https://bugs.kde.org/show_bug.cgi?id=395517 They suggested "What you can try to do is open a bug against Ubuntu and ask whether they can backport the commit mentioned in comment 1 to the Qt version in Ubuntu 18.04... " https://wiki.qt.io/Qt_5.12_Release https://codereview.qt-project.org/#/c/226881/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: okular 4:17.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Tue Jun 19 11:57:15 2018 InstallationDate: Installed on 2018-06-15 (3 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: okular UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/okular/+bug/1777615/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318834] Re: Applications can no longer access your @gmail.com Online Account
After my most recent Ubuntu 16.04 LTS update (that required both an authorization password request and a post-installation reboot) the following message appears briefly in a small window in the top right corner of the screen after I sign into Ubuntu: "Applications can no longer access your [@ATT.net email address] online account. Choose Online Accounts from the user menu to reinstate access to this account." I looked at Online Accounts. All that currently appears there is my identification as administrator, my Ubuntu sign-on name (not an email address) and my password with a clickable button for viewing my sign on history. Since the only thing unique about the referenced ATT.net email address is that it's the only email address issued to me by AT&T, my Internet provider that I only use for paying my monthly AT&T bill. I doubt that it has ever been listed with my Ubuntu sign-on name. So I have no idea if "Applications can no longer access your [@ATT.net email address] online account." should mean something to me. I'm not entering the AT&T address and password, and not identifying whether or not the account is Administration. I suppose I'll find out soon enough that's a problem. While I'm still a new user of Ubuntu, I'm not a neophyte computer user. It is vexing to encounter these situations. I'd welcome any explanations that clarify what I'm being instructed to do, if anything. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-control-center- signon in Ubuntu. https://bugs.launchpad.net/bugs/1318834 Title: Applications can no longer access your @gmail.com Online Account Status in gnome-control-center-signon package in Ubuntu: Confirmed Bug description: IN start UBUNTU Application can no longer access your dumetz1...@gmail.com Online Account. Choose online Accounts from the user menu to reinstate access to this account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1318834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738153] Re: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial
Please confirm the exact package version tested. What about my question in comment 10? The Regression Potential currently says "it just add one more mapping" but this doesn't appear to be true because a mapping was also removed. -- 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/1738153 Title: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial Status in OEM Priority Project: Confirmed Status in OEM Priority Project xenial series: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd source package in Artful: Won't Fix Bug description: [Impact] dell-wmi expend the scan code of Microphone mute hotkey from 0x150 to 0x100150, so need to add a new mapping for it. related commit: https://github.com/systemd/systemd/pull/5012 [Test Case] 1. install the udev package which applied patch. 2. check if Microphone mute hotkey works. 3. if it not works, please provide the log of evtest. [Regression Potential] low regression potential, because it just add one more mapping. also affect: LP: #1736352 LP: #1740080 LP: #1734609 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1738153/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799747] [NEW] Xorg freeze
Public bug reported: I can't run Ubuntu 18.10 with nVidia drivers (340.107). They ran just fine on 18.04, but not on 18.10. The system freezes at start up (the furthest that it gets is 'Starting Gnome Display Manager'). X-org Nouveau driver is working ok, but it's not ideal, I get strange flickering at subtle color gradients... ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 24 18:29:54 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Very infrequently GraphicsCard: NVIDIA Corporation GT215 [GeForce GT 240] [10de:0ca3] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2018-10-23 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=3e2e480d-ea50-412f-88cd-55820becb551 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2209 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q 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.:bvr2209:bd03/11/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic 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/1799747 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I can't run Ubuntu 18.10 with nVidia drivers (340.107). They ran just fine on 18.04, but not on 18.10. The system freezes at start up (the furthest that it gets is 'Starting Gnome Display Manager'). X-org Nouveau driver is working ok, but it's not ideal, I get strange flickering at subtle color gradients... ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 24 18:29:54 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Very infrequently GraphicsCard: NVIDIA Corporation GT215 [GeForce GT 240] [10de:0ca3] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2018-10-23 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=3e2e480d-ea50-412f-88cd-55820becb551 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2209 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q 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.:bvr2209:bd03/
[Touch-packages] [Bug 1738515] Re: [Precision 5510, Realtek ALC3266, Black Speaker, Internal] No sound at all after plugging in headphones
I have upgraded to Ubuntu 18.04 (bionic) and I am experiencing the same problem. I don't have permission to change the bug status, should I submit another bug report? -- 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/1738515 Title: [Precision 5510, Realtek ALC3266, Black Speaker, Internal] No sound at all after plugging in headphones Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Sound worked before, but after plugging in headphones, sound does not work through either headphones or internal speakers. Sound continues not to work after unplugging headphones. I tried: 1. killall pulseaudio; rm -r ~/.config/pulse/* ; rm -r ~/.pulse* 2. wait 10 seconds 3. reboot Then sound worked in internal speakers, but when I plugged in headphones, I got the same result. I tested the sound using "Test Speakers" in Settings, and by playing youtube videos in Firefox. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: paul 1374 F...m pulseaudio /dev/snd/controlC0: paul 1374 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Dec 15 22:15:26 2017 InstallationDate: Installed on 2017-12-08 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: paul 1374 F...m pulseaudio /dev/snd/controlC0: gdm1055 F pulseaudio paul 1374 F pulseaudio Symptom_Jack: Black Speaker, Internal Symptom_Type: No sound at all Title: [Precision 5510, Realtek ALC3266, Black Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0WVDX2 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd08/11/2017:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0WVDX2:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: Precision 5510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1738515/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771135] Re: unattended upgrades always fail b/c dpkg status database is always locked
*** This bug is a duplicate of bug 1789637 *** https://bugs.launchpad.net/bugs/1789637 Locking across dpkg frontend is being fixed and the fix will be ported back to Xenial. I'm setting this bug as a duplicate of the one tracking the fix of unattended-upgrades. Please follow the state of that bug for the resolution of the reported issue. ** This bug has been marked a duplicate of bug 1789637 Proper support for frontend lock -- 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/1771135 Title: unattended upgrades always fail b/c dpkg status database is always locked Status in apt package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: New Bug description: Hi, (Filing this bug against apt since that contains the systemd timers and cron job to start unattended-upgrades). I'm using unattended-upgrades on several computers. On the one that is on most of the time, updates work as expected. On the ones that are off most of the time, updates are never installed because there is always a "dpkg: error: dpkg status database is locked by another process". Running `unattended-upgrade -d` by hand or using aptitude works fine. I suspect that because these computers are off most of the time, the systemd timers for both apt-daily and apt-daily-upgrade are always run at the same time during boot and resulting in the dpkg database being locked for apt-daily-upgrade. I will try disabling the systemd timers and using the cron job instead to see if that fixes the problem. FYI I also noticed that the cron job will only run when the system is on A/C power, whereas the systemd timers do not seem to have any such check. Thanks. - Felix ubuntu version: 16.04.4 LTS apt version: 1.2.26 unattended-upgrades version: 0.90ubuntu0.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1771135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738153] Re: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial
@racb unknown is a placeholder, which is now assigned to wlan. Without unknown, there would be debugging error kernel messages `unknown key pressed`. So previously we knew the physical key exists and is pressable, but dind't know what it should do, but now we do know what it does. -- 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/1738153 Title: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial Status in OEM Priority Project: Confirmed Status in OEM Priority Project xenial series: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd source package in Artful: Won't Fix Bug description: [Impact] dell-wmi expend the scan code of Microphone mute hotkey from 0x150 to 0x100150, so need to add a new mapping for it. related commit: https://github.com/systemd/systemd/pull/5012 [Test Case] 1. install the udev package which applied patch. 2. check if Microphone mute hotkey works. 3. if it not works, please provide the log of evtest. [Regression Potential] low regression potential, because it just add one more mapping. also affect: LP: #1736352 LP: #1740080 LP: #1734609 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1738153/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes
Thank you for checking that this doesn't introduce a regression on unaffected hardware. Note that we don't currently have a verification for the actual reason this is being SRU'd, which is "rfkill keyboard shortcuts not working as intended on some Dell machines". -- 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/1762385 Title: dell_wmi: Unknown key codes Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Bogus keycode messages produced by the kernel / user annoyance * rfkill keyboard shortcuts not working as intended on some Dell machines [Test Case] * check that there are no spurious kernel messages about unknown keys in journalctl upon RFKill key presses * check that RFKill key presses work correctly and kill/restore RF capabilities [Regression Potential] * The change is scoped to particular SKUs and thus should only affect them * It is related to matching gsd support, which is in-place on xenial and up [Solution] Cherrypick upstream commit https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f [Original Bug report] RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86 /dell-wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1762385/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799663] Re: Headerbars big size in Ambiance and Radiance theme
The attachment "Patch for padding" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1799663 Title: Headerbars big size in Ambiance and Radiance theme Status in Ubuntu theme: New Status in ubuntu-themes package in Ubuntu: New Bug description: In Ubuntu 18.04 (bionic) in Gnome Flashback(Metacity) session headerbars have too big size in Ambiance and Radiance theme. I have resolved this problem by setting in gtk-widgets.ccs file`s section - .titlebar button .titlebutton - padding: 0; .titlebar button.titlebutton { background-clip: padding-box; color: #3d3c37; -gtk-icon-shadow: 0 1px rgba(255, 255, 255, 0.1); box-shadow: none; border: none; padding-left: 0; padding-right: 0; margin: 0; padding: 0px; <---here min-width: 20px; min-height: 20px; background-size: 20px 20px; background-image: -gtk-scaled(url("assets/windowbutton.png"), url("assets/windowbut...@2.png"), url("assets/windowbut...@3.png"), url("assets/windowbut...@4.png")); background-repeat: no-repeat; background-position: center; } As I have seen in light-themes(14.04+16.04.20180326-0ubuntu1) padding: 0; - exists in Ambiance and Radiance theme. .titlebar.header-bar .button.titlebutton { background-clip: padding-box; border: 1px solid #383734; color: #3d3c37; icon-shadow: 0 1px rgba(255, 255, 255, 0.1); border-radius: 9px; padding: 0; <--here box-shadow: none; background-image: linear-gradient(to top, #5a5955, #75746d 50%, #8e8d88); } My OS is: Description: Ubuntu 18.04.1 LTS Release: 18.04 Package: light-themes Version: 16.10+18.04.20180421.1-0ubuntu1 Priority: optional Section: gnome Source: ubuntu-themes Origin: Ubuntu Maintainer: Ubuntu Artwork Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 17,7 MB Depends: gtk2-engines-murrine (>= 0.90.3+git20100810), humanity-icon-theme, ubuntu-mono Homepage: https://launchpad.net/ubuntu-themes Task: ubuntu-desktop, ubuntukylin-desktop Supported: 5y Download-Size: 458 kB APT-Manual-Installed: no Description: Light Themes (Ambiance and Radiance) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1799663/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799702] [NEW] rsyslog fails to bind to tcp socket on restart
Public bug reported: My rsyslog configuration listens on TCP port 514 and is bound to an address on tun0 (created by an openvpn server daemon): module(load="imtcp") input(type="imtcp" port="514" address="10.8.9.1") This machine rebooted (due to unattended upgrades) overnight and when it came back up, rsyslog was not listening on the port. The logs show: Oct 24 03:00:16 foo rsyslogd-2077: Could not create tcp listener, ignoring port 514 bind-address 10.8.9.1. [v8.16.0 try http://www.rsyslog.com/e/2077 ] A restart of rsyslogd was required to address the issue. I'm curious what the right solution to this problem would be, as the bind interface is configuration-dependent. ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1799702 Title: rsyslog fails to bind to tcp socket on restart Status in rsyslog package in Ubuntu: New Bug description: My rsyslog configuration listens on TCP port 514 and is bound to an address on tun0 (created by an openvpn server daemon): module(load="imtcp") input(type="imtcp" port="514" address="10.8.9.1") This machine rebooted (due to unattended upgrades) overnight and when it came back up, rsyslog was not listening on the port. The logs show: Oct 24 03:00:16 foo rsyslogd-2077: Could not create tcp listener, ignoring port 514 bind-address 10.8.9.1. [v8.16.0 try http://www.rsyslog.com/e/2077 ] A restart of rsyslogd was required to address the issue. I'm curious what the right solution to this problem would be, as the bind interface is configuration-dependent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1799702/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790668] Re: /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin/unattended-upgrade@1485:main:do_auto_remove:cache_commit:commit:_fetch_archives
*** This bug is a duplicate of bug 1789637 *** https://bugs.launchpad.net/bugs/1789637 The implementation of the frontend lock in _all_ dpkg frontends can make u-u avoid this crash. Making this bug as a duplicate of the bug tracking the frontend lock implementation for u-u. ** This bug has been marked a duplicate of bug 1789637 Proper support for frontend lock -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1790668 Title: /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin /unattended- upgrade@1485:main:do_auto_remove:cache_commit:commit:_fetch_archives Status in unattended-upgrades package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1, the problem page at https://errors.ubuntu.com/problem/eabb483bd4584c745292dbf0b45214b2f5d75013 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1790668/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
This started happening after installing lubuntu-desktop. Even after removing it, it is still failing to mount. After running "keyctl link @u @s", it works. -- 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/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys Status in ecryptfs-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: ecryptfs-mount-private fails to mount the ecryptfs after the 1st reboot after creating the ecryptfs by ecryptfs-setup-private. After the unsucessful attempt dmesg contains: [ 1265.695388] Could not find key with description: [] [ 1265.695393] process_request_key_err: No key [ 1265.695394] Could not find valid key in user session keyring for sig specified in mount option: [] [ 1265.695395] One or more global auth toks could not properly register; rc = [-2] [ 1265.695396] Error parsing options; rc = [-2] Note: The correct key ID has been replaced in the "". I also accidentally found an workaround - just running ecrytpfs- manager and then the ecryptfs-mount-private (it does not ask for password for the second time and mounts the ecryptfs correctly): host:~$ ecryptfs-manager eCryptfs key management menu --- 1. Add passphrase key to keyring 2. Add public key to keyring 3. Generate new public/private keypair 4. Exit Make selection: 4 host:~$ ls Private/ Access-Your-Private-Data.desktop README.txt host:~$ ecryptfs-mount-private host:~$ ls Private/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
Note: I'm using 18.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/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys Status in ecryptfs-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: ecryptfs-mount-private fails to mount the ecryptfs after the 1st reboot after creating the ecryptfs by ecryptfs-setup-private. After the unsucessful attempt dmesg contains: [ 1265.695388] Could not find key with description: [] [ 1265.695393] process_request_key_err: No key [ 1265.695394] Could not find valid key in user session keyring for sig specified in mount option: [] [ 1265.695395] One or more global auth toks could not properly register; rc = [-2] [ 1265.695396] Error parsing options; rc = [-2] Note: The correct key ID has been replaced in the "". I also accidentally found an workaround - just running ecrytpfs- manager and then the ecryptfs-mount-private (it does not ask for password for the second time and mounts the ecryptfs correctly): host:~$ ecryptfs-manager eCryptfs key management menu --- 1. Add passphrase key to keyring 2. Add public key to keyring 3. Generate new public/private keypair 4. Exit Make selection: 4 host:~$ ls Private/ Access-Your-Private-Data.desktop README.txt host:~$ ecryptfs-mount-private host:~$ ls Private/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1325614] Re: Cannot unlock screen in KDE
I was offsite all day yesterday. I came in today and the lock screen was responsive. Unplugging the monitor seemed to prevent the issue. -- 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/1325614 Title: Cannot unlock screen in KDE Status in lightdm package in Ubuntu: New Status in sddm package in Ubuntu: New Bug description: System Info: Description:Ubuntu 14.04 LTS Release:14.04 Hardware: Lenovo THingpand T430 connected to an external Dell montior; using onboard Intel 4000 HD Configuration: widget-enabled screen locker, desktop effects (OpenGL 3.1). Expected: When screen locks (either through time-out or user request), clicking on the cashew in the top right should permit unlock. What happens: Nothing - it is not possible to unlock the screen. Viable workaround: None. It might be that using "xrandr" for effects doesn't cause the issue, but I haven't had time to fully test. The only option is to force a shutdown and then start, losing all data in open applications. Reboot does not seem to work correctly when the screen can't be unlocked, hangs with black screen when it should show log-in screen. I am more than happy to run any required tests or pull required logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1325614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
That sounds great! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in gnome-settings-daemon package in Ubuntu: Triaged Status in libxkbcommon package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Bug description: There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1740894/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799702] Re: rsyslog attached to OpenVPN-managed tun0 fails to bind to tcp socket on restart
I discussed with slangasek, who said: - The workaround is to either to configure systemd to restart rsyslog when the socket is available, or to have openvpn restart rsyslog when the VPN comes up. - The definitive fix would require rsyslogd to grow netlink support (or be managed by something else that does). For now, I'm working around this by using openvpn config. ** Summary changed: - rsyslog fails to bind to tcp socket on restart + rsyslog attached to OpenVPN-managed tun0 fails to bind to tcp socket on restart -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1799702 Title: rsyslog attached to OpenVPN-managed tun0 fails to bind to tcp socket on restart Status in rsyslog package in Ubuntu: New Bug description: My rsyslog configuration listens on TCP port 514 and is bound to an address on tun0 (created by an openvpn server daemon): module(load="imtcp") input(type="imtcp" port="514" address="10.8.9.1") This machine rebooted (due to unattended upgrades) overnight and when it came back up, rsyslog was not listening on the port. The logs show: Oct 24 03:00:16 foo rsyslogd-2077: Could not create tcp listener, ignoring port 514 bind-address 10.8.9.1. [v8.16.0 try http://www.rsyslog.com/e/2077 ] A restart of rsyslogd was required to address the issue. I'm curious what the right solution to this problem would be, as the bind interface is configuration-dependent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1799702/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps]
I'm seeing what I believe to be the same issue with Visual Studio Code. If I try to start it after logging in using Gnome on Wayland, I find myself looking at a login screen. (If I login to Gnome on Xorg this does not happen.) There is a core file in my home directory There is also a file in /var/crashes hbarta@karakum:~$ ls /var/crash _usr_bin_pulseaudio.1000.crash _usr_bin_Xwayland.1000.crash hbarta@karakum:~$ hbarta@karakum:~$ file core core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from '/usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -d', real uid: 1000, effective uid: 1000, real gid: 1000, effective gid: 1000, execfn: '/usr/bin/Xwayland', platform: 'x86_64' hbarta@karakum:~$ I tried to install debug symbols for Xwayland but cannot. hbarta@karakum:~$ sudo apt install xwayland-dbgsym [sudo] password for hbarta: Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xwayland-dbgsym : Depends: xwayland (= 2:1.19.6-1ubuntu4.1) but 2:1.19.6-1ubuntu4 is to be installed E: Unable to correct problems, you have held broken packages. hbarta@karakum:~$ I have the same problem on Debian Testing but not Fedora 28. (On Debian testing I am not running vs code as a snap.) I would like to use Wayland for the improved monitor scaling so I can use a 1600x1200 eternal monitor with a QHD laptop. If there is any further information I could provide (and I'm sure I'm light in this regard) please let me know. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1754693 Title: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps] Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: U