[Touch-packages] [Bug 1777514] Re: gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() from ... _mesa_glsl_release_builtin_functions() from _mesa_destroy_shader_compiler_caches()
** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1777514 Title: gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() from ... _mesa_glsl_release_builtin_functions() from _mesa_destroy_shader_compiler_caches() from _mesa_destroy_shader_compiler() from one_time_fini() from __run_exit_handlers() from exit() Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.1-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/c1f46d2d92c2be5d4c6d68c44ef0817ccea8ccab 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/gnome-shell/+bug/1777514/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
@vorlon, I can't get it work Tested that: [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. Downloaded: initramfs-tools_0.130ubuntu10_all.deb initramfs-tools-bin_0.130ubuntu10_amd64.deb initramfs-tools-core_0.130ubuntu10_all.deb done : dpkg -i *.deb 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 30 second delay still there /etc/initramfs-tools/conf.d/resume still exists If the file `/etc/initramfs-tools/conf.d/resume` is deleted manually, it is not re-created by update-initramfs -u -- 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/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: In Progress Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 430697] Re: exmh-bg dying, becoming a zombie
Thank you for reporting this bug to Ubuntu. Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010. 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: exmh (Ubuntu) Status: Confirmed => Invalid ** Changed in: xorg (Ubuntu) Status: Confirmed => Invalid -- 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/430697 Title: exmh-bg dying, becoming a zombie Status in exmh package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Bug description: Binary package hint: exmh When starting exmh configured to auto inc, the background process exmh-bg is started correctly, after some seconds the backbroung process dies and becomes a zombie, afterwards auto inc doesn't work any more (as would be expected). This is on AMD64 Jaunty with all updates installed. bodo@sakura:~$ lsb_release -rd Description: Ubuntu 9.04 Release: 9.04 bodo@sakura:~$ apt-cache policy exmh exmh: Installed: 1:2.7.2-16 Candidate: 1:2.7.2-16 Version table: *** 1:2.7.2-16 0 500 http://de.archive.ubuntu.com jaunty/universe Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exmh/+bug/430697/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu Artful) Status: New => Confirmed -- 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/1768610 Title: leftover conffile forces GNOME is software rendering Status in nux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: In Progress Status in nux source package in Xenial: Fix Committed Status in xorg source package in Xenial: Confirmed Status in nux source package in Artful: Fix Committed Status in xorg source package in Artful: Confirmed Status in nux source package in Bionic: Fix Committed Status in xorg source package in Bionic: In Progress Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777565] [NEW] pulseaudio seems to have crashed
Public bug reported: always showing mute symbol on desktop ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Jun 19 10:04:59 2018 InstallationDate: Installed on 2018-03-29 (82 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: FCKT72AUS dmi.board.vendor: LENOVO dmi.board.version: NOK dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrFCKT72AUS:bd08/04/2015:svnLENOVO:pn10ASA06WIH:pvrThinkCentreE73:rvnLENOVO:rn:rvrNOK:cvnLENOVO:ct3:cvr: dmi.product.name: 10ASA06WIH dmi.product.version: ThinkCentre E73 dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1777565 Title: pulseaudio seems to have crashed Status in pulseaudio package in Ubuntu: New Bug description: always showing mute symbol on desktop ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Jun 19 10:04:59 2018 InstallationDate: Installed on 2018-03-29 (82 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: FCKT72AUS dmi.board.vendor: LENOVO dmi.board.version: NOK dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrFCKT72AUS:bd08/04/2015:svnLENOVO:pn10ASA06WIH:pvrThinkCentreE73:rvnLENOVO:rn:rvrNOK:cvnLENOVO:ct3:cvr: dmi.product.name: 10ASA06WIH dmi.product.version: ThinkCentre E73 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1777565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu Xenial) Status: New => Confirmed -- 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/1768610 Title: leftover conffile forces GNOME is software rendering Status in nux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: In Progress Status in nux source package in Xenial: Fix Committed Status in xorg source package in Xenial: Confirmed Status in nux source package in Artful: Fix Committed Status in xorg source package in Artful: Confirmed Status in nux source package in Bionic: Fix Committed Status in xorg source package in Bionic: In Progress Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering
** Package changed: mesa (Ubuntu) => xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Status: New => In Progress ** Changed in: xorg (Ubuntu Bionic) Status: Confirmed => In Progress -- 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/1768610 Title: leftover conffile forces GNOME is software rendering Status in nux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: In Progress Status in nux source package in Xenial: Fix Committed Status in xorg source package in Xenial: Confirmed Status in nux source package in Artful: Fix Committed Status in xorg source package in Artful: Confirmed Status in nux source package in Bionic: Fix Committed Status in xorg source package in Bionic: In Progress Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu Bionic) Status: New => Confirmed -- 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/1768610 Title: leftover conffile forces GNOME is software rendering Status in nux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: In Progress Status in nux source package in Xenial: Fix Committed Status in xorg source package in Xenial: Confirmed Status in nux source package in Artful: Fix Committed Status in xorg source package in Artful: Confirmed Status in nux source package in Bionic: Fix Committed Status in xorg source package in Bionic: In Progress Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering Status in nux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: In Progress Status in nux source package in Xenial: Fix Committed Status in xorg source package in Xenial: Confirmed Status in nux source package in Artful: Fix Committed Status in xorg source package in Artful: Confirmed Status in nux source package in Bionic: Fix Committed Status in xorg source package in Bionic: In Progress Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777565] Re: pulseaudio seems to have crashed
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your bug report is missing crash details. In order to debug a crash we will need a crash report. To create one, please follow these steps: 1. If you are not running a future development release of Ubuntu then apply the workaround from bug 994921. 2. If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport. 3. If the crash is in Xorg then uncomment this option from /etc/gdm3/custom.conf: # Additionally lets the X server dump core if it crashes #Enable=true 4. Reboot. 5. Reproduce the crash. 6. Look in /var/crash for crash files and when found, run: ubuntu-bug /var/crash/YOURFILE.crash 7. Add a comment here telling us the ID of the new bug that was created in step 6. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments, and doing so is also a security risk for yourself. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1777565 Title: pulseaudio seems to have crashed Status in pulseaudio package in Ubuntu: Incomplete Bug description: always showing mute symbol on desktop ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Jun 19 10:04:59 2018 InstallationDate: Installed on 2018-03-29 (82 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2015 dmi.bios.vendor: LENOVO dmi.bios.version: FCKT72AUS dmi.board.vendor: LENOVO dmi.board.version: NOK dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrFCKT72AUS:bd08/04/2015:svnLENOVO:pn10ASA06WIH:pvrThinkCentreE73:rvnLENOVO:rn:rvrNOK:cvnLENOVO:ct3:cvr: dmi.product.name: 10ASA06WIH dmi.product.version: ThinkCentre E73 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1777565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777567] [NEW] package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: Could not able to upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 19 10:11:16 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 DpkgHistoryLog: Start-Date: 2018-06-19 10:09:53 Requested-By: anandharaj (1001) Install: alsa-base:amd64 (1.0.25+dfsg-0ubuntu5, automatic), pulseaudio:amd64 (1:11.1-1ubuntu7.1, automatic), ubuntu-desktop:amd64 (1.417), pulseaudio-module-bluetooth:amd64 (1:11.1-1ubuntu7.1, automatic) Upgrade: fonts-beng-extra:amd64 (1.0-6, 1.0-6ubuntu0.1), fonts-deva-extra:amd64 (3.0-4, 3.0-4ubuntu0.1), libwebkit2gtk-4.0-37:amd64 (2.20.2-0ubuntu0.18.04.1, 2.20.3-0ubuntu0.18.04.1), fonts-orya-extra:amd64 (2.0-5, 2.0-5ubuntu0.1), gir1.2-webkit2-4.0:amd64 (2.20.2-0ubuntu0.18.04.1, 2.20.3-0ubuntu0.18.04.1), fonts-gujr-extra:amd64 (1.0-6, 1.0-6ubuntu0.1), libjavascriptcoregtk-4.0-18:amd64 (2.20.2-0ubuntu0.18.04.1, 2.20.3-0ubuntu0.18.04.1), gir1.2-javascriptcoregtk-4.0:amd64 (2.20.2-0ubuntu0.18.04.1, 2.20.3-0ubuntu0.18.04.1) Remove: linux-image-extra-4.4.0-127-generic:amd64 (4.4.0-127.153) ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-08-23 (664 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-from-proposed -- 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/1777567 Title: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Could not able to upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 19 10:11:16 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 DpkgHistoryLog: Start-Date: 2018-06-19 10:09:53 Requested-By: anandharaj (1001) Install: alsa-base:amd64 (1.0.25+dfsg-0ubuntu5, automatic), pulseaudio:amd64 (1:11.1-1ubuntu7.1, automatic), ubuntu-desktop:amd64 (1.417), pulseaudio-module-bluetooth:amd64 (1:11.1-1ubuntu7.1, automatic) Upgrade: fonts-beng-extra:amd64 (1.0-6, 1.0-6ubuntu0.1), fonts-deva-extra:amd64 (3.0-4, 3.0-4ubuntu0.1), libwebkit2gtk-4.0-37:amd64 (2.20.2-0ubuntu0.18.04.1, 2.20.3-0ubuntu0.18.04.1), fonts-orya-extra:amd64 (2.0-5, 2.0-5ubuntu0.1), gir1.2-webkit2-4.0:amd64 (2.20.2-0ubuntu0.18.04.1, 2.20.3-0ubuntu0.18.04.1), fonts-gujr-extra:amd64 (1.0-6, 1.0-6ubuntu0.1), libjavascriptcoregtk-4.0-18:amd64 (2.20.2-0ubuntu0.18.04.1, 2.20.3-0ubuntu0.18.04.1), gir1.2-javascriptcoregtk-4.0:amd64 (2.20.2-0ubuntu0.18.04.1, 2.20.3-0ubuntu0.18.04.1) Remove: linux-image-extra-4.4.0-127-generic:amd64 (4.4.0-127.153) ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-08-23 (664 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install)
[Touch-packages] [Bug 1777567] Re: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1777567 Title: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Could not able to upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 19 10:11:16 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 DpkgHistoryLog: Start-Date: 2018-06-19 10:09:53 Requested-By: anandharaj (1001) Install: alsa-base:amd64 (1.0.25+dfsg-0ubuntu5, automatic), pulseaudio:amd64 (1:11.1-1ubuntu7.1, automatic), ubuntu-desktop:amd64 (1.417), pulseaudio-module-bluetooth:amd64 (1:11.1-1ubuntu7.1, automatic) Upgrade: fonts-beng-extra:amd64 (1.0-6, 1.0-6ubuntu0.1), fonts-deva-extra:amd64 (3.0-4, 3.0-4ubuntu0.1), libwebkit2gtk-4.0-37:amd64 (2.20.2-0ubuntu0.18.04.1, 2.20.3-0ubuntu0.18.04.1), fonts-orya-extra:amd64 (2.0-5, 2.0-5ubuntu0.1), gir1.2-webkit2-4.0:amd64 (2.20.2-0ubuntu0.18.04.1, 2.20.3-0ubuntu0.18.04.1), fonts-gujr-extra:amd64 (1.0-6, 1.0-6ubuntu0.1), libjavascriptcoregtk-4.0-18:amd64 (2.20.2-0ubuntu0.18.04.1, 2.20.3-0ubuntu0.18.04.1), gir1.2-javascriptcoregtk-4.0:amd64 (2.20.2-0ubuntu0.18.04.1, 2.20.3-0ubuntu0.18.04.1) Remove: linux-image-extra-4.4.0-127-generic:amd64 (4.4.0-127.153) ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-08-23 (664 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess 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/initramfs-tools/+bug/1777567/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering
Added scripts in in x11-common (debdiff) and nux-tools (see attached MPs) ** Patch added: "xorg.debdiff" https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+attachment/5154156/+files/xorg.debdiff -- 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/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in nux source package in Xenial: Fix Committed Status in mesa source package in Artful: New Status in nux source package in Artful: Fix Committed Status in mesa source package in Bionic: New Status in nux source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering
** Merge proposal linked: https://code.launchpad.net/~3v1n0/nux/+git/nux/+merge/348193 -- 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/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in nux source package in Xenial: Fix Committed Status in mesa source package in Artful: New Status in nux source package in Artful: Fix Committed Status in mesa source package in Bionic: New Status in nux source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751673] Re: nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- 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/1751673 Title: nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Status in network-manager package in Ubuntu: Expired Bug description: running 18.04 this message is spamming into syslog: > nm-applet[3607]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.8.4-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Feb 26 01:16:49 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-09-28 (1611 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) IpRoute: default via 192.168.1.1 dev wlan1 proto static metric 600 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.34 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-01-12 (44 days ago) modified.conffile..etc.polkit-1.localauthority.50-local.d.org.freedesktop.NetworkManager.pkla: [deleted] nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan1 wifi connected /org/freedesktop/NetworkManager/Devices/3 k2l 7df024b1-9b89-4f95-84c1-03188bb67f77 /org/freedesktop/NetworkManager/ActiveConnection/1 EC:88:92:02:17:7D btdisconnected /org/freedesktop/NetworkManager/Devices/4 -- -- -- eth1 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1751673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 433231] Re: xorg: directory "/usr/share/fonts/X11/cyrillic" does not exist.
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017. Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011. 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: xorg (Ubuntu) Status: Triaged => Invalid -- 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/433231 Title: xorg: directory "/usr/share/fonts/X11/cyrillic" does not exist. Status in X.Org X server: Invalid Status in xorg package in Ubuntu: Invalid Bug description: Hello, I run on Kubuntu Karmic 64, 2.6.31-10-genericx86 64 In my log are this error: Avertissement The directory "/usr/share/fonts/X11/cyrillic" does not exist. [lspci] 01:00.0 VGA compatible controller [0300]: nVidia Corporation G92 [GeForce 9800 GTX] [10de:0612] (rev a2) Subsystem: ASUSTeK Computer Inc. Device [1043:82a6] To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/433231/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 555870] Re: Gamma values are not being set properly after a second fade out resulting in a black screen
** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/555870 Title: Gamma values are not being set properly after a second fade out resulting in a black screen Status in GNOME Screensaver: Expired Status in NULL Project: Invalid Status in xorg package in Ubuntu: Invalid Bug description: Binary package hint: gnome-screensaver When running the test-fade app in gnome-screensaver the gamma values are improperly being set after the second fade, resulting in a permenant black screen until manual adjustment of the gamma values. Steps to reproduce: get the gnome-screensaver source and build it cd /path/to/gnome-screensaver/src/ ./test-fade it will attempt to fade twice, after the first fade and restore the second fade will not come back unless you manually fix the gamma values with a command such as xrandr --output LVDS1 --gamma 1:1:1 Here is a script to reproduce and automatically adjust fix the gamma values afterwards so its usable with one machine, you have to manually move the cursor or hit a key after each fade. #!/bin/bash ./test-fade sleep 10 xrandr --output LVDS1 --gamma 1:1:1 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-screensaver 2.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 Architecture: i386 Date: Mon Apr 5 13:08:59 2010 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-screensaver WindowManager: metacity To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/555870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 555298] Re: [RV250] black screen when switching users
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013. 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: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/555298 Title: [RV250] black screen when switching users Status in xserver-xorg-driver-ati: Unknown Status in xorg package in Ubuntu: Invalid Bug description: Binary package hint: xorg When switching users in Lucid, often X will freeze up and just give me a black screen with blinking cursor. When I try to go to the current session with Ctrl+Alt+F7,8,9,etc. I either get black, distorted or a non-responsive unlock screen. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xorg 1:7.5+3ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 Architecture: i386 CurrentDmesg: [ 13.377233] usb 3-2: usbfs: interface 0 claimed by usblp while 'usb' sets config #1 [ 19.436009] eth1: no IPv6 routers present [ 45.528055] end_request: I/O error, dev fd0, sector 0 [ 45.612036] end_request: I/O error, dev fd0, sector 0 Date: Sun Apr 4 21:08:10 2010 DkmsStatus: Error: [Errno 2] Bestand of map bestaat niet InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318) MachineType: HP Pavilion 06 DF168A-ABH T170. ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=1ed36f90-6dd8-4916-8da8-acd31abccb32 ro quiet splash ProcEnviron: LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: xorg dmi.bios.date: 07/16/2003 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 3.23 dmi.board.name: MS-6577 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 030 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr3.23:bd07/16/2003:svnHPPavilion06:pnDF168A-ABHT170.:pvr03Y0211RE101XENO4:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-6577:rvr030:cvn:ct3:cvr: dmi.product.name: DF168A-ABH T170. dmi.product.version: 03Y0211RE101XENO4 dmi.sys.vendor: HP Pavilion 06 glxinfo: Error: [Errno 2] Bestand of map bestaat niet system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-19-generic [lspci] 00:00.0 Host bridge [0600]: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface [8086:2560] (rev 03) Subsystem: Micro-Star International Co., Ltd. Device [1462:5770] 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon RV250 If [Radeon 9000] [1002:4966] (rev 01) Subsystem: ATI Technologies Inc Device [1002:2002] To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/555298/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 592550] Re: setxkbmap fills in /var/lib/xkb
Please tell us if this bug still affects you and if so what Ubuntu version it is in. ** Changed in: xorg (Ubuntu) Status: Triaged => Incomplete ** Changed in: x11-xkb-utils (Ubuntu) Status: Confirmed => Incomplete ** Changed in: xorg-server Importance: Low => Undecided ** Changed in: xorg-server Status: Won't Fix => New ** Changed in: xorg-server Remote watch: freedesktop.org Bugzilla #65319 => None ** Project changed: xorg-server => ubuntu ** No longer affects: 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/592550 Title: setxkbmap fills in /var/lib/xkb Status in x11-xkb-utils package in Ubuntu: Incomplete Status in xorg package in Ubuntu: Incomplete Bug description: Binary package hint: x11-xkb-utils using setxkbmap with different mappings silently fills in /var/lib/xkb with xkm files when are these files purged !! ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xkb-utils/+bug/592550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 13912] Re: Mouse and touchpad don't work well together
** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/13912 Title: Mouse and touchpad don't work well together Status in xorg package in Ubuntu: Invalid Bug description: When the touchpad and USB mouse on my laptop are both enabled, neither gets initialised properly. After booting and logging in, the pointer seems to get stuck to the first widget it is clicked on in each window. For example, I can drag a box on the desktop, but then I can't activate any icons by clicking on them. If I open a calculator, the first button I click on works, but then none of the others even receive "enter" signals. Strangely, after clicking the middle mouse button everything works perfectly. If I disable the USB mouse in xorg.conf the touchpad works fine. Attempting to disable the touchpad doesn't seem to work - it just starts acting like a regular mouse, and sends data to /dev/input/mice. I'm running a recent version of Hoary: * linux-image-2.6.10-4-k7 Version: 2.6.10-27 * xserver-common, xserver-xorg, xorg-common Version: 6.8.2-2 * xorg-driver-synaptics Version: 0.13.6-0ubuntu4 My laptop is a Compaq Presario 700. The mouse is a Logitech iFeel mouse. I'll attach my xorg.conf and xorg log files, and dmesg output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/13912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 12720] Re: vertical scroll needs time
** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/12720 Title: vertical scroll needs time Status in xorg package in Ubuntu: Invalid Bug description: ..when starting up X, it just doesn't work. After a time I use X the scrolling starts working. I managed to get it work once after like 3 seconds, I was tapping at the upper right corner, seems that turns it on (sometimes, or just coincidence). Option "Protocol" "auto-dev" Option "SHMConfig" "on" Option "RightEdge" "5980" Option "BottomEdge""4300" Option "CircularScrolling" "1" Option "RTCornerButton""3" Option "RBCornerButton""2" Option "CircScrollTrigger" "3" this is what I use, I can live with it but someone may have a clue. Just for info, there is a new driver (0.14) available with many new features, upgrade is actually recommended. (I use the hoary version) regards, nanophase To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/12720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 33075] Re: Dell Inspiron 8200 Nvidia proprietary driver causes display errors (vertical lines on the right, and mirror effect on the bottom)[Workaround Available]
** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/33075 Title: Dell Inspiron 8200 Nvidia proprietary driver causes display errors (vertical lines on the right, and mirror effect on the bottom)[Workaround Available] Status in xorg package in Ubuntu: Invalid Bug description: Using nvidia proprietary driver on a Dell Inspiron 8200 with a Samsung 1600x1200 screen, the desktop is only shown on about the top left 4/5 of the screen, with multicolor vertical lines on the right and a mirror of the top part of the desktop at the bottom of the screen. The desktop is shown in full, only it's shrinked to 4/5 of its size. Using the free nv driver, everything is ok except I'd be happy if it was snappier :) [Workaround] See comment #4 to set a customized edid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/33075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 12723] Re: Synaptic touchpad wrong middle-click under touch
** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/12723 Title: Synaptic touchpad wrong middle-click under touch Status in xorg package in Ubuntu: Invalid Bug description: When touching the touchpad, the result is like if I do a middle-click instead of a right-click. The laptop is a HP Pavilion dv1000. I sent an email to the mailing list explaining this and I found that I need to do: synclient TapButton2=1 in order to make it do the left-click. Let me know what output files would you like to have. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/12723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 35794] Re: TV out is broken with VT1621 chip
** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/35794 Title: TV out is broken with VT1621 chip Status in X.Org X server: Invalid Status in xorg package in Ubuntu: Invalid Bug description: I have a EPIA V-1 board which uses a trident cyberblade/i1 with a VIA VT1621 to do tv-out over the composite connector. The trident_drv.so in xserver-xorg-driver-trident is broken and displays noise on the screen (it looks as if the refresh rate is totally wrong or as if it is sending NTSC data when I have actually asked for PAL). The driver from http://www.blackfiveservices.co.uk/EPIATVOut.shtml gets it right - although you have to get tvtool from the same site and turn on PAL output once the xserver has loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/35794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 136853] Re: Screen blanks and freezes after a few minutes of idling, possibly due to broken DPMS
** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/136853 Title: Screen blanks and freezes after a few minutes of idling, possibly due to broken DPMS Status in xf86-video-siliconmotion: Invalid Status in xorg package in Ubuntu: Invalid Bug description: Since switching to Gutsy to verify whether the packages I maintain still operate as expected, I have noticed that after a few minutes of idle operation, the screen goes blank and cannot be returned to normal. The only way to get screen content again is to reboot, which is possible either by pressing the ACPI-enabled power button or a remote SSH connection. Broken DPMS is suspected, although I have no way of confirming this. Purposely downgrading xserver-xorg-core and anything that depend on it, then pining it to that version, while keeping all the rest of the packages to Gutsy versions solves it, which suggests something related to X.org upgrade from 1.2 to 1.3 might be at play. Note: someone on #ltsp mentions a similar situation using xserver- xorg-video-amd, yet the exact same AMD driver doesn't exhibit this behavior when compiled and used with earlier X releases. To manage notifications about this bug go to: https://bugs.launchpad.net/xf86-video-siliconmotion/+bug/136853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 125670] Re: Scroll of synaptics touchpad stop working suddenly
** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/125670 Title: Scroll of synaptics touchpad stop working suddenly Status in XOrg-Driver-Synaptics: Fix Released Status in xorg package in Ubuntu: Invalid Bug description: Binary package hint: xorg-driver-synaptics After some time i log into KDE the scroll of my synaptics touchpad stop working and only work again if I switch to VT (console - control + alt + f1 for instance) and then come back to X. That's extremely annoying for me since I'm always needing to use the touchpad. Some info: I: Bus=0011 Vendor=0002 Product=0007 Version= N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio4/input0 S: Sysfs=/class/input/input9 H: Handlers=mouse1 event8 ts1 B: EV=b B: KEY=6420 0 7 0 0 0 0 0 0 0 0 B: ABS=1103 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-driver-synaptics/+bug/125670/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 148117] Re: [r128] Rage 128: Unsuitable videomode autoselected
** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/148117 Title: [r128] Rage 128: Unsuitable videomode autoselected Status in X.org xf86-video-r128: Invalid Status in xorg package in Ubuntu: Invalid Bug description: Binary package hint: xserver-xorg-video-ati I tested Ubunti 7.10-beta-desktop-i386 on my PCs. At one PC the X-Server was not able to start, and i saw only the commandline. This PC has a ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS connected to a Belinea 108080 CRT-Display. I tried to start the X-Server at the commandline an got errormessages, the X-Server didn't start: auth: creating new authority file /home/ubuntu/.serverauth.20130 xauth: creating new authority file /home/ubuntu/.Xauthority xauth: creating new authority file /home/ubuntu/.Xauthority X Window System Version 1.3.0 Release Date: 19 April 2007 X Protocol Version 11, Revision 0, Release 1.3 Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0.dfsg-12ubuntu6) Current Operating System: Linux ubuntu 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 Build Date: 21 September 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 1 21:58:06 2007 (==) Using config file: "/etc/X11/xorg.conf" (II) Module already built-in (II) Module already built-in (II) Module already built-in (EE) R128(0): No DFP detected (II) Module already built-in (EE) R128(0): (Ron = 12288) + (Rloop = 17) >= (Roff = 10752) Fatal server error: AddScreen/ScreenInit failed for driver 0 XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processed) with 0 events remaining. *** The /etc/X11/xorg.conf: *** # xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Files" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "de" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "ZAxisMapping" "4 5" Option "Emulate3Buttons" "true" EndSection Section "InputDevice" Driver "wacom" Identifier "stylus" Option "Device""/dev/input/wacom" Option "Type" "stylus" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection Section "InputDevice" Driver "wacom" Identifier "eraser" Option "Device""/dev/input/wacom" Option "Type" "eraser" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection Section "InputDevice" Driver "wacom" Identifier "cursor" Option "Device""/dev/input/wacom" Option "Type" "cursor" Option "ForceDevice" "ISDV4" # Tablet PC ONLY EndSection Section "Device" Identifier "ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS" Driver "ati" BusID "PCI:1:0:0" EndSection Section "Monitor" Identifier "108080" Option "DPMS" EndSection
[Touch-packages] [Bug 214442] Re: Time out error with r128 and some games
** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/214442 Title: Time out error with r128 and some games Status in X.org xf86-video-r128: Won't Fix Status in xorg package in Ubuntu: Invalid Bug description: Binary package hint: xserver-xorg-video-ati Some 3D games exit abruptly on an ATI Rage 128 Pro. Occurs at both 16 and 24bpp depths. Does not affect all games. Terminal message: Error: Rage 128 timed out... exiting Workarounds: Chromium - none Armagetron Advanced - Turn off floor and object textures. Similar report on Mandriva: http://fixunix.com/mandriva/123547-3d-rage-driver-crashing-mandriva-one-2007-spring.html Possible freedesktop.org bug reference in Mandriva report: http://bugs.freedesktop.org/show_bug.cgi?id=9379 [Chromium] ATTENTION!! Could not load alAttenuationScale ERROR!! <> alGetError() = Invalid Value alAttenuationScale == 0. Kludge it. ...startup complete. high scores: 01/01/2000 nobody 25 01/01/2000 nobody 20 01/01/2000 nobody 15 01/01/2000 nobody 10 01/01/2000 nobody 5 Error: Rage 128 timed out... exiting [New Thread 0xb56cbb90 (LWP 5730)] Program exited with code 0377. [armagetronad (gdb) run Starting program: /usr/games/armagetronad.real --datadir /usr/share/games/armagetronad --configdir /etc/armagetronad --userconfigdir /home/administrator/.armagetronad --vardir /home/administrator/.armagetronad/var --userdatadir /home/administrator/.armagetronad/data [Thread debugging using libthread_db enabled] [New Thread 0xb741a720 (LWP 5868)] [New Thread 0xb72d1b90 (LWP 5871)] [Thread 0xb72d1b90 (LWP 5871) exited] [New Thread 0xb72d1b90 (LWP 5872)] Error: Rage 128 timed out... exiting [Thread 0xb72d1b90 (LWP 5872) exited] Program exited with code 0377. (gdb) backtrace full No stack. [lspci] 00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT82C598 [Apollo MVP3] [1106:0598] (rev 04) Subsystem: VIA Technologies, Inc. MVP3 ISA Bridge [1106:] 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS [1002:5046] (prog-if 00 [VGA controller]) Subsystem: ATI Technologies Inc Unknown device [1002:0404] To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-r128/+bug/214442/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 318325] Re: [X1100] flickering after resume from ram
This bug is too old to work with and the related Ubuntu versions are past end of life. Tommy: If you or others experience problems then please log new bugs. ** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/318325 Title: [X1100] flickering after resume from ram Status in xorg package in Ubuntu: Invalid Bug description: Binary package hint: xserver-xorg-video-radeon System : Ubuntu 8.10 (up to date) GPU : ATI express X1100 Video driver : radeon Steps to reproduce : - put the computer on standby - resume from ram => the screen will flicker while CPU activity is not high workaround : - just launch an infinite loop that consume CPU : $ while true; do echo >/dev/null; done => the screen won't flicker while the CPU is use (even if only one core is being used) There isn't error either in Xorg, xsession logs or in dmesg after resuming. Notice that this trouble doesn't occured with fglrx driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/318325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 374041] Re: Letters (fonts) sometimes gray instead of black
Thank you for reporting this bug to Ubuntu. Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010. 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: xorg (Ubuntu) Status: New => Invalid -- 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/374041 Title: Letters (fonts) sometimes gray instead of black Status in xorg package in Ubuntu: Invalid Bug description: Sometimes, text is rendered light gray-ish instead of black. That applies to some buttons, menu lables, even to text in different web browsers. My font rendering is set to "best form", but other settings gave the same result. Now I set it to "black and white" but I kinda doubt that works. The fun thing is, that sometimes when the text has to be redrawn (e.g. because a window moved over it and off again), the text is fine, again. lsb_release -rd: Description: Ubuntu 9.04 Release: 9.04 The whole thing is running on an iBook G4: Linux version 2.6.28-6-powerpc (buildd@adare) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #20-Ubuntu Fri Apr 17 08:30:40 UTC 2009 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/374041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1775676] Re: file is not showing in a good format
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! ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1775676 Title: file is not showing in a good format Status in xorg package in Ubuntu: Incomplete Bug description: all my files are not shpoing well ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Thu Jun 7 18:55:36 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:172a] InstallationDate: Installed on 2018-05-26 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=ff2e3855-9d5d-4ca8-abf2-661b693284ca ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.20 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.20:bd09/05/2011:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.32:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.1-0~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.1-0~b~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1775676/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering
** Merge proposal linked: https://code.launchpad.net/~3v1n0/nux/+git/nux/+merge/348192 -- 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/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in nux source package in Xenial: Fix Committed Status in mesa source package in Artful: New Status in nux source package in Artful: Fix Committed Status in mesa source package in Bionic: New Status in nux source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777560] [NEW] package python-setuptools 39.0.1-2 failed to install/upgrade: installed python-setuptools package post-installation script subprocess returned error exit status 12
Public bug reported: I NEED HELP ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python-setuptools 39.0.1-2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: firefox-locale-en:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Jun 18 20:11:49 2018 Dependencies: python-pkg-resources 39.0.1-2 ErrorMessage: installed python-setuptools package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2018-05-30 (20 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] Arquivo ou diretório inexistente: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: python-setuptools Title: package python-setuptools 39.0.1-2 failed to install/upgrade: installed python-setuptools package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-setuptools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1777560 Title: package python-setuptools 39.0.1-2 failed to install/upgrade: installed python-setuptools package post-installation script subprocess returned error exit status 127 Status in python-setuptools package in Ubuntu: New Bug description: I NEED HELP ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python-setuptools 39.0.1-2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: firefox-locale-en:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Jun 18 20:11:49 2018 Dependencies: python-pkg-resources 39.0.1-2 ErrorMessage: installed python-setuptools package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2018-05-30 (20 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] Arquivo ou diretório inexistente: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: python-setuptools Title: package python-setuptools 39.0.1-2 failed to install/upgrade: installed python-setuptools package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1777560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777554] Re: package libkmod2:amd64 22-1ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1777554 Title: package libkmod2:amd64 22-1ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in kmod package in Ubuntu: New Bug description: tried to update using apt-get update and apt-get install .. but to no effect. I even tried apt-get -f install but it failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkmod2:amd64 22-1ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Tue Jun 19 08:02:40 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: Setting up libc6:amd64 (2.23-0ubuntu10) ... dpkg: error processing package libkmod2:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-06-17 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.10ubuntu1 SourcePackage: kmod Title: package libkmod2:amd64 22-1ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1777554/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777554] [NEW] package libkmod2:amd64 22-1ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: tried to update using apt-get update and apt-get install .. but to no effect. I even tried apt-get -f install but it failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkmod2:amd64 22-1ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Tue Jun 19 08:02:40 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: Setting up libc6:amd64 (2.23-0ubuntu10) ... dpkg: error processing package libkmod2:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-06-17 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.10ubuntu1 SourcePackage: kmod Title: package libkmod2:amd64 22-1ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kmod (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 kmod in Ubuntu. https://bugs.launchpad.net/bugs/1777554 Title: package libkmod2:amd64 22-1ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in kmod package in Ubuntu: New Bug description: tried to update using apt-get update and apt-get install .. but to no effect. I even tried apt-get -f install but it failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkmod2:amd64 22-1ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Tue Jun 19 08:02:40 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: Setting up libc6:amd64 (2.23-0ubuntu10) ... dpkg: error processing package libkmod2:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-06-17 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.10ubuntu1 SourcePackage: kmod Title: package libkmod2:amd64 22-1ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1777554/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758589] Re: The wifi will be disconnected and the only thing I can do is to reboot the laptop
@Kai-Heng Feng, seems that your solution should be OK. Thank you for your help! -- 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/1758589 Title: The wifi will be disconnected and the only thing I can do is to reboot the laptop Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: First of all, I am not sure whether it's true that this is a bug of network-manager, but it is true that this should be a bug related with network (wifi connection). Here is the issue: Every time after I login into the account, about 20 minutes later, the wifi will be disconnected automatically. I even cannot reconnect the wifi manually, the only thing that I can do is to reboot the laptop. After login again, wifi can be connected (but through manual way). By the way, during the period of wifi disconnection, I checked the "Wi-Fi Networks" by click "Select Network" in order to try to reconnect it manually. But I found that there is only one SSID which previously the laptop connected to. However, I was definitely sure that there should be more than one SSID being showed in the wifi list. Even for this only one SSID, like I mentioned before, I cannot reconnect manually unless I reboot the system. Finally, I set the wifi to be connected automatically after I login to the system, however, it just can't. I can only connect to the wifi manually after I login to the system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 19:02:12 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-01-15 (68 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 172.24.16.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 172.24.16.0/20 dev wlp4s0 proto kernel scope link src 172.24.16.69 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTIONCON-UUID CON-PATH wlp4s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 WolfieNet-Secure eb45c742-ba31-4f31-acf2-13a2768bcc29 /org/freedesktop/NetworkManager/ActiveConnection/5 enp5s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled disabled --- ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kevin 1217 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-01-15 (70 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 172.24.16.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 172.24.16.0/20 dev wlp4s0 proto kernel scope link src 172.24.16.148 metric 600 MachineType: Lenovo F31 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false NonfreeKernelModules: nvidia Package: network-manager 1.10.6-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=02a1b417-5beb-4eae-82cb-e3063372bf6d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic package-from-proposed Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No
[Touch-packages] [Bug 1777514] Re: gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() from ... _mesa_glsl_release_builtin_functions()
** Summary changed: - /usr/bin/gnome-shell:corrupted double-linked list + gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() from ... _mesa_glsl_release_builtin_functions() ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Summary changed: - gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() from ... _mesa_glsl_release_builtin_functions() + gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() from ... _mesa_glsl_release_builtin_functions() from _mesa_destroy_shader_compiler_caches() from _mesa_destroy_shader_compiler() from one_time_fini() from __run_exit_handlers() from exit() -- 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/1777514 Title: gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() from ... _mesa_glsl_release_builtin_functions() from _mesa_destroy_shader_compiler_caches() from _mesa_destroy_shader_compiler() from one_time_fini() from __run_exit_handlers() from exit() Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.1-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/c1f46d2d92c2be5d4c6d68c44ef0817ccea8ccab 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/gnome-shell/+bug/1777514/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777425] Re: Skype snap segfaults GNOME Shell on Wayland
Unfortunately I am unable to get the necessary information from your crash file. Please report it formally using the command: ubuntu-bug _usr_bin_Xwayland.1000.crash and then let us know the ID of the new bug. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete ** Changed in: wayland (Ubuntu) Status: Confirmed => Incomplete ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1777425 Title: Skype snap segfaults GNOME Shell on Wayland Status in gnome-shell package in Ubuntu: Incomplete Status in wayland package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: The Skype snap segfaults GNOME Shell on Wayland, crashing the session and sending the user back to the login screen. ``` $ snap info skype tracking: stable refresh-date: today at 11:31 BST installed: 8.22.0.2 (33) 143MB classic $ snap version snap2.33 snapd 2.33 series 16 ubuntu 18.04 kernel 4.15.0-23-generic $ snap info core tracking: beta refresh-date: 10 days ago, at 18:50 BST installed: 16-2.33(4830) 91MB core ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Jun 18 12:15:54 2018 DistUpgraded: 2018-04-22 07:24:16,565 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2017-08-03 (318 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 2347GU8 MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=ce8cd4c6-3ada-4004-acbf-e169ca40b394 ro quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: Upgraded to bionic on 2018-04-22 (57 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GU8 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1777425/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in nux source package in Xenial: Fix Committed Status in mesa source package in Artful: New Status in nux source package in Artful: Fix Committed Status in mesa source package in Bionic: New Status in nux source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10
** Changed in: xorg (Ubuntu) Importance: Medium => Low ** Changed in: xorg (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1770306 Title: X display is black after 18.04 upgrade from 17.10 Status in xorg package in Ubuntu: New Bug description: I can manually start lightdm, and that will give me a login screen, Unfortunately, most of the desktop environments crash after login. Only plasma gives me a little bit of clients, though even plasma complains All shell packages missing And Vboxclient warning Under 17.10, I successfully used Wayland WORKAROUND: Use GNOME Flashback (Metacity). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Wed May 9 19:15:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0665] InstallationDate: Installed on 2015-05-18 (1087 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash i915.i915_enable_rc6=1 vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10
I did not install the image, just ran it from the USB stick. By default, it does not not have a login screen, since there is a single user, I believe. I added a second user, and logged in to that user, which was successful. But this may be different from what I see on my long-installed system. Does the default use lightdm? I didn't check. -- 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/1770306 Title: X display is black after 18.04 upgrade from 17.10 Status in xorg package in Ubuntu: Incomplete Bug description: I can manually start lightdm, and that will give me a login screen, Unfortunately, most of the desktop environments crash after login. Only plasma gives me a little bit of clients, though even plasma complains All shell packages missing And Vboxclient warning Under 17.10, I successfully used Wayland WORKAROUND: Use GNOME Flashback (Metacity). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Wed May 9 19:15:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0665] InstallationDate: Installed on 2015-05-18 (1087 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash i915.i915_enable_rc6=1 vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773167] Re: [Intel HDMI LPE driver] Audio is not working; pulseaudio consumes 100% of a single CPU core
Launchpad has imported 64 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=100488. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-03-30T15:59:25+00:00 Tanu Kaskinen wrote: It was reported[1] on alsa-devel that PulseAudio gets killed when trying to use the Intel HDMI LPE driver that was introduced in kernel version 4.11. That probably happens due to excessive CPU use in the IO thread. It's not known what causes the high CPU use, but the discussion revealed some definite shortcomings in PulseAudio when HDMI's underlying hw device is hw:x,0. There are two bugs: 1) PulseAudio assumes that if the front:x device doesn't work but hw:x,0 does, then hw:x,0 is an analog stereo device. 2) PulseAudio assumes that HDMI devices are always mapped to certain hw:x,y devices, the first one being hw:x,3. When this assumption doesn't hold, jack detection and ELD reading don't work. For the first bug, I propose trying hw:x,0 for analog stereo only if everything else fails, so if e.g. hdmi:x,0 is successfully opened, hw:x,0 won't be used. For the second bug, I propose removing the hardcoded device numbers, and instead query the device number from an open PCM handle. That's not reliable for all PCM devices, but Takashi expects it to work for HDMI devices. It's not obvious what would be the best way to modify the profile and path configuration syntax to support the new features. I'll prepare a more detailed proposal when I get around to it. My impression is that the HDMI LPE driver will be widely used, so I think this should be fixed with high priority (I'll mark this as a release blocker). [1] http://mailman.alsa-project.org/pipermail/alsa- devel/2017-March/118903.html Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1773167/comments/0 On 2017-04-24T15:09:00+00:00 Tanu Kaskinen wrote: I sent a patch for the first bug: https://patchwork.freedesktop.org/patch/152433/ The patch is simpler than I first thought: it doesn't change the configuration syntax at all. It just moves the hw:x,0 handling from the analog-stereo mapping to a new unknown-stereo mapping that is marked as a fallback, that is, it's used only when nothing else works. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1773167/comments/1 On 2017-05-31T05:53:02+00:00 Arun Raghavan wrote: Do we need to call the second part of the bug an 11.0 blocker? Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1773167/comments/2 On 2017-06-04T22:52:05+00:00 Tanu Kaskinen wrote: Yes, I think making the jack detection work is important. I understand this[1] message from Takashi so that we should avoid using the device when the monitor isn't plugged in, and for that we need working jack detection. [1] http://mailman.alsa-project.org/pipermail/alsa- devel/2017-March/119087.html Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1773167/comments/3 On 2017-06-12T15:47:17+00:00 Tanu Kaskinen wrote: Patches submitted: https://patchwork.freedesktop.org/series/25656/ Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1773167/comments/4 On 2017-07-25T16:37:22+00:00 Bugzilla-x wrote: What is the expected behaviour with those patches? For me, on a Surface 3 (CherryTrail) with the patches applied on top of PA 10.0, PulseAudio doesn't crash, but I get no sound from the internal speakers when HDMI is not plugged in. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1773167/comments/5 On 2017-07-25T22:06:43+00:00 Tanu Kaskinen wrote: What does "pactl list" print when it's not working? Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1773167/comments/6 On 2017-07-25T22:08:01+00:00 Tanu Kaskinen wrote: (In reply to Bastien Nocera from comment #5) > What is the expected behaviour with those patches? The expected behaviour is that everything works perfectly (apart from PulseAudio getting killed, but you don't seem to be suffering from that). Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1773167/comments/7 On 2017-08-03T03:04:04+00:00 Tanu Kaskinen wrote: Bastien, do
[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10
Kevin Dalley, to clarify your comment: >"I tried the cdimage mentioned above, and it works. What does that ultimately suggest? I didn't have a login screen for the cdimage, of course." You said the image works, but you don't have a login screen. Not having a login screen would be considered not working. Could you please clarify? -- 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/1770306 Title: X display is black after 18.04 upgrade from 17.10 Status in xorg package in Ubuntu: Incomplete Bug description: I can manually start lightdm, and that will give me a login screen, Unfortunately, most of the desktop environments crash after login. Only plasma gives me a little bit of clients, though even plasma complains All shell packages missing And Vboxclient warning Under 17.10, I successfully used Wayland WORKAROUND: Use GNOME Flashback (Metacity). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Wed May 9 19:15:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0665] InstallationDate: Installed on 2015-05-18 (1087 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash i915.i915_enable_rc6=1 vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1479310] Re: Card symbols in the monospace font are wider than single character should be
** Package changed: ubuntu-font-family-sources (Ubuntu) => ubuntu-font- family -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/1479310 Title: Card symbols in the monospace font are wider than single character should be Status in Ubuntu Font Family: New Bug description: Using font Ubuntu mono regular symbols ♣♦♥♠♧♢♡♤ are rendered about 1.5 times wider than monospace character wide is. That causes it to cover next character making it very hard to read. Those characters are U2660-U2667. Screenshot from gnome terminal showing the problem follows. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ttf-ubuntu-font-family 0.80-0ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jul 29 14:02:35 2015 Dependencies: InstallationDate: Installed on 2011-11-02 (1365 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: Upgraded to vivid on 2015-05-02 (87 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-font-family/+bug/1479310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1646860] Re: Startup sound is better disabled
** No longer affects: hundredpapercuts ** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu) ** Project changed: lightdm => unity-greeter -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1646860 Title: Startup sound is better disabled Status in Unity Greeter: Confirmed Status in unity-greeter package in Ubuntu: Triaged Bug description: I would like to suggest disabling the startup sound. It does nothing of use, and frequently it wakes up people who are sleeping. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30 Uname: Linux 4.4.0-51-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Dec 2 15:46:46 2016 InstallationDate: Installed on 2016-05-02 (213 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter allow-guest=false SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.pam.d.lightdm: [modified] mtime.conffile..etc.pam.d.lightdm: 2016-11-06T20:03:03.153118 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-greeter/+bug/1646860/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770306] Re: X display is black after 18.04 upgrade from 17.10
Finally getting back to this. My notes on setting enable_rc6 aren't very good. I may have started using it as a possible way to extend battery life, as mentioned here. I don't notice a difference now that I have removed it. https://askubuntu.com/questions/93654/why-does-my-computer-get-less- battery-life-with-ubuntu-compared-to-windows#38194 I tried the cdimage mentioned above, and it works. What does that ultimately suggest? I didn't have a login screen for the cdimage, of course. -- 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/1770306 Title: X display is black after 18.04 upgrade from 17.10 Status in xorg package in Ubuntu: Incomplete Bug description: I can manually start lightdm, and that will give me a login screen, Unfortunately, most of the desktop environments crash after login. Only plasma gives me a little bit of clients, though even plasma complains All shell packages missing And Vboxclient warning Under 17.10, I successfully used Wayland WORKAROUND: Use GNOME Flashback (Metacity). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Wed May 9 19:15:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0665] InstallationDate: Installed on 2015-05-18 (1087 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash i915.i915_enable_rc6=1 vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777502] [NEW] 'file -r' returns invalid option
Public bug reported: Attempting to use the '-r' option returns 'invalid option' although '-r' is listed in the usage and man page: $file -b -N -L -k -r s.fits file: invalid option -- 'r' Usage: file [-bchikLlNnprsvz0] [--apple] [--mime-encoding] [--mime-type] [-e testname] [-F separator] [-f namefile] [-m magicfiles] file ... file -C [-m magicfiles] file [--help] Expected behaviour: '-r' works or is removed from usage (prefer the former as removing it will break a lot of things). Ubuntu release: Description:Ubuntu 14.04.5 LTS Release:14.04 Package version: file: Installed: 1:5.14-2ubuntu3.4 Candidate: 1:5.14-2ubuntu3.4 Version table: *** 1:5.14-2ubuntu3.4 0 501 http://pl.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 501 http://pl.archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 1:5.14-2ubuntu3 0 501 http://pl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ** Affects: file (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1777502 Title: 'file -r' returns invalid option Status in file package in Ubuntu: New Bug description: Attempting to use the '-r' option returns 'invalid option' although '-r' is listed in the usage and man page: $file -b -N -L -k -r s.fits file: invalid option -- 'r' Usage: file [-bchikLlNnprsvz0] [--apple] [--mime-encoding] [--mime-type] [-e testname] [-F separator] [-f namefile] [-m magicfiles] file ... file -C [-m magicfiles] file [--help] Expected behaviour: '-r' works or is removed from usage (prefer the former as removing it will break a lot of things). Ubuntu release: Description:Ubuntu 14.04.5 LTS Release:14.04 Package version: file: Installed: 1:5.14-2ubuntu3.4 Candidate: 1:5.14-2ubuntu3.4 Version table: *** 1:5.14-2ubuntu3.4 0 501 http://pl.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 501 http://pl.archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 1:5.14-2ubuntu3 0 501 http://pl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1777502/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770682] Re: Scanner driver failed to install. package libperl5.26 5.26.1-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: perl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1770682 Title: Scanner driver failed to install. package libperl5.26 5.26.1-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 Status in perl package in Ubuntu: Confirmed Bug description: HP 1510 PSC scanner driver failed to install ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libperl5.26 5.26.1-6 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri May 11 18:01:31 2018 DuplicateSignature: package:libperl5.26:5.26.1-6 Unpacking libperl5.26:i386 (5.26.1-6) ... dpkg: error processing archive /tmp/apt-dpkg-install-bTjSsG/30-libperl5.26_5.26.1-6_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 InstallationDate: Installed on 2018-05-02 (8 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: perl Title: package libperl5.26 5.26.1-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1770682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764965] Re: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster
@Markus could you please click on the "Affects mee too" link above the bug report, just under the title? Thanks :) ** Tags added: alsa-driver artful audacity bionic -- 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/1764965 Title: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recording applications (audacity, arecord, gnome-sound-recorder) record extremely slowly (at what seems to be 0,1x speed), which means that at playback the sound is played at a very high pitch and much faster than the original. To help you understand the issue, I've attached an archive containing two files recorded at the same time, one with arecord -f cd and the other with a stand-alone Olympus recorder. A video of Audacity's behavior when trying to record is also available: https://youtu.be/Fe20eQNvZVA Look at the seconds hand of the xclock and how much it is moving before Audacity is done recording one second of audio. Things I've already tried: * Purging and reinstalling Audacity * Purging and reinstalling Pulseaudio following the guide on the Ubuntu Wiki * Running audacity with this command: Exec=env PULSE_LATENCY_MSEC=30 audacity as suggested on AskUbuntu * Reinstalling Ubuntu on a new hard disk * Running audacity on a live CD (in Ubuntu version 16.04.3, 17.10.1, 18.04 daily and Xubuntu 17.10.1, 18.04) The machine is a Ryzen 5 1600 with an ASUS X370 Prime motherboard. The problem can be reproduced as follows: * Boot a live DVD of Ubuntu/Xubuntu 16.04.3, 17.10.1, 18.04 (versions I've tested with) * Install audacity via the terminal * Start recording, microphone is connected to the rear microphone jack. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacopo 2417 F pulseaudio /dev/snd/controlC0: jacopo 2417 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 18 09:35:50 2018 InstallationDate: Installed on 2018-03-03 (45 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_Type: None of the above Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1764965/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615144] Re: BUG: unable to handle kernel NULL pointer dereference
can you please test with a kernel that is Ubuntu-4.4.0-37.56 or later
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1615144
Title:
BUG: unable to handle kernel NULL pointer dereference
Status in apparmor package in Ubuntu:
Incomplete
Bug description:
The latest update from the Xenial InRelease repository makes the
following processes consume 100% CPU:
thermald(1.5-2ubuntu2)
imap(Dovecot 1:2.2.22-1ubuntu2)
imap-login (Dovecot 1:2.2.22-1ubuntu2)
and eventualy (after 1-2 minutes) render the system completely unresponsive.
"NMI watchdog: Watchdog detected hard LOCKUP on cpu 0".
I was able to recreate the problem on my test system, so whatever is
missing in this report should be easy to simulate on another system.
All apparmor profiles are standard.
# aa-status
apparmor module is loaded.
49 profiles are loaded.
13 profiles are in enforce mode.
/sbin/dhclient
/usr/bin/freshclam
/usr/lib/NetworkManager/nm-dhcp-client.action
/usr/lib/NetworkManager/nm-dhcp-helper
/usr/lib/chromium-browser/chromium-browser//browser_java
/usr/lib/chromium-browser/chromium-browser//browser_openjdk
/usr/lib/chromium-browser/chromium-browser//sanitized_helper
/usr/lib/connman/scripts/dhclient-script
/usr/sbin/clamd
/usr/sbin/mysqld
/usr/sbin/named
/usr/sbin/ntpd
/usr/sbin/tcpdump
36 profiles are in complain mode.
/usr/lib/chromium-browser/chromium-browser
/usr/lib/chromium-browser/chromium-browser//chromium_browser_sandbox
/usr/lib/chromium-browser/chromium-browser//lsb_release
/usr/lib/chromium-browser/chromium-browser//xdgsettings
/usr/lib/dovecot/anvil
/usr/lib/dovecot/auth
/usr/lib/dovecot/config
/usr/lib/dovecot/deliver
/usr/lib/dovecot/dict
/usr/lib/dovecot/dovecot-lda
/usr/lib/dovecot/dovecot-lda///usr/sbin/sendmail
/usr/lib/dovecot/imap
/usr/lib/dovecot/imap-login
/usr/lib/dovecot/lmtp
/usr/lib/dovecot/log
/usr/lib/dovecot/managesieve
/usr/lib/dovecot/managesieve-login
/usr/lib/dovecot/pop3
/usr/lib/dovecot/pop3-login
/usr/lib/dovecot/ssl-params
/usr/sbin/avahi-daemon
/usr/sbin/dnsmasq
/usr/sbin/dnsmasq//libvirt_leaseshelper
/usr/sbin/dovecot
/usr/sbin/identd
/usr/sbin/mdnsd
/usr/sbin/nmbd
/usr/sbin/nscd
/usr/sbin/smbd
/usr/sbin/smbldap-useradd
/usr/sbin/smbldap-useradd///etc/init.d/nscd
/usr/{sbin/traceroute,bin/traceroute.db}
/{usr/,}bin/ping
klogd
syslog-ng
syslogd
25 processes have profiles defined.
5 processes are in enforce mode.
/usr/bin/freshclam (2942)
/usr/sbin/clamd (3080)
/usr/sbin/mysqld (3767)
/usr/sbin/named (3634)
/usr/sbin/ntpd (3468)
20 processes are in complain mode.
/usr/lib/dovecot/anvil (3827)
/usr/lib/dovecot/auth (3845)
/usr/lib/dovecot/auth (4503)
/usr/lib/dovecot/config (3830)
/usr/lib/dovecot/imap (6139)
/usr/lib/dovecot/imap (6952)
/usr/lib/dovecot/imap-login (3826)
/usr/lib/dovecot/imap-login (3832)
/usr/lib/dovecot/imap-login (6048)
/usr/lib/dovecot/imap-login (7924)
/usr/lib/dovecot/imap-login (12248)
/usr/lib/dovecot/imap-login (12740)
/usr/lib/dovecot/imap-login (12816)
/usr/lib/dovecot/imap-login (14112)
/usr/lib/dovecot/imap-login (14508)
/usr/lib/dovecot/imap-login (14533)
/usr/lib/dovecot/log (3828)
/usr/lib/dovecot/managesieve-login (12794)
/usr/lib/dovecot/ssl-params (4498)
/usr/sbin/dovecot (3816)
0 processes are unconfined but have a profile defined.
# uname -r
4.4.0-34-generic
# apt-get install apparmor
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
apparmor-profiles-extra apparmor-docs apparmor-utils
The following packages will be upgraded:
apparmor
1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 446 kB of archives.
After this operation, 4,096 B of additional disk space will be used.
Get:1 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 apparmor
amd64 2.10.95-0ubuntu2.2 [446 kB]
Fetched 446 kB in 0s (4,172 kB/s)
Preconfiguring packages ...
(Reading database ... 115108 files and directories currently installed.)
Preparing to unpack .../apparmor_2.10.95-0ubuntu2.2_amd64.deb ...
Unpacking apparmor (2.10.95-0ubuntu2.2) over (2.10.95-0ubuntu2) ...
Processing triggers for systemd (229-4ubuntu7) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up apparmor (2.10.95-0ubuntu2.2) ...
Installing new version of config file
/etc/apparmor.d/abstractions/dbus-session-strict ...
update-rc.d: warning: start and stop
[Touch-packages] [Bug 1615144] Re: BUG: unable to handle kernel NULL pointer dereference
Profile state should never crash apparmor.
The userspace no matter it state should never be able to crash the
kernel. Profiles go through a verification process before the kernel
will make them available.
The "half" configured state may mean that not all apparmor profiles are
loaded, or that some of the userspace functions aren't available but
that should never result in a kernel oops.
The userspace obviously got far enough along to replace some policy and
from the kernel trace we can see that apparmor oopsed during profile
replacement, after the profile has been verified and it is being
activated kernel side.
I believe this bug is already fixed by commit
57d3b8969c47b1dabeb9d122a88df2c14d4f1b9f UBUNTU: SAUCE: apparmor: fix
vec_unique for vectors larger than 8
which was released in Ubuntu-4.4.0-37.56
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1615144
Title:
BUG: unable to handle kernel NULL pointer dereference
Status in apparmor package in Ubuntu:
Incomplete
Bug description:
The latest update from the Xenial InRelease repository makes the
following processes consume 100% CPU:
thermald(1.5-2ubuntu2)
imap(Dovecot 1:2.2.22-1ubuntu2)
imap-login (Dovecot 1:2.2.22-1ubuntu2)
and eventualy (after 1-2 minutes) render the system completely unresponsive.
"NMI watchdog: Watchdog detected hard LOCKUP on cpu 0".
I was able to recreate the problem on my test system, so whatever is
missing in this report should be easy to simulate on another system.
All apparmor profiles are standard.
# aa-status
apparmor module is loaded.
49 profiles are loaded.
13 profiles are in enforce mode.
/sbin/dhclient
/usr/bin/freshclam
/usr/lib/NetworkManager/nm-dhcp-client.action
/usr/lib/NetworkManager/nm-dhcp-helper
/usr/lib/chromium-browser/chromium-browser//browser_java
/usr/lib/chromium-browser/chromium-browser//browser_openjdk
/usr/lib/chromium-browser/chromium-browser//sanitized_helper
/usr/lib/connman/scripts/dhclient-script
/usr/sbin/clamd
/usr/sbin/mysqld
/usr/sbin/named
/usr/sbin/ntpd
/usr/sbin/tcpdump
36 profiles are in complain mode.
/usr/lib/chromium-browser/chromium-browser
/usr/lib/chromium-browser/chromium-browser//chromium_browser_sandbox
/usr/lib/chromium-browser/chromium-browser//lsb_release
/usr/lib/chromium-browser/chromium-browser//xdgsettings
/usr/lib/dovecot/anvil
/usr/lib/dovecot/auth
/usr/lib/dovecot/config
/usr/lib/dovecot/deliver
/usr/lib/dovecot/dict
/usr/lib/dovecot/dovecot-lda
/usr/lib/dovecot/dovecot-lda///usr/sbin/sendmail
/usr/lib/dovecot/imap
/usr/lib/dovecot/imap-login
/usr/lib/dovecot/lmtp
/usr/lib/dovecot/log
/usr/lib/dovecot/managesieve
/usr/lib/dovecot/managesieve-login
/usr/lib/dovecot/pop3
/usr/lib/dovecot/pop3-login
/usr/lib/dovecot/ssl-params
/usr/sbin/avahi-daemon
/usr/sbin/dnsmasq
/usr/sbin/dnsmasq//libvirt_leaseshelper
/usr/sbin/dovecot
/usr/sbin/identd
/usr/sbin/mdnsd
/usr/sbin/nmbd
/usr/sbin/nscd
/usr/sbin/smbd
/usr/sbin/smbldap-useradd
/usr/sbin/smbldap-useradd///etc/init.d/nscd
/usr/{sbin/traceroute,bin/traceroute.db}
/{usr/,}bin/ping
klogd
syslog-ng
syslogd
25 processes have profiles defined.
5 processes are in enforce mode.
/usr/bin/freshclam (2942)
/usr/sbin/clamd (3080)
/usr/sbin/mysqld (3767)
/usr/sbin/named (3634)
/usr/sbin/ntpd (3468)
20 processes are in complain mode.
/usr/lib/dovecot/anvil (3827)
/usr/lib/dovecot/auth (3845)
/usr/lib/dovecot/auth (4503)
/usr/lib/dovecot/config (3830)
/usr/lib/dovecot/imap (6139)
/usr/lib/dovecot/imap (6952)
/usr/lib/dovecot/imap-login (3826)
/usr/lib/dovecot/imap-login (3832)
/usr/lib/dovecot/imap-login (6048)
/usr/lib/dovecot/imap-login (7924)
/usr/lib/dovecot/imap-login (12248)
/usr/lib/dovecot/imap-login (12740)
/usr/lib/dovecot/imap-login (12816)
/usr/lib/dovecot/imap-login (14112)
/usr/lib/dovecot/imap-login (14508)
/usr/lib/dovecot/imap-login (14533)
/usr/lib/dovecot/log (3828)
/usr/lib/dovecot/managesieve-login (12794)
/usr/lib/dovecot/ssl-params (4498)
/usr/sbin/dovecot (3816)
0 processes are unconfined but have a profile defined.
# uname -r
4.4.0-34-generic
# apt-get install apparmor
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
apparmor-profiles-extra apparmor-docs apparmor-utils
The following packages will be upgraded:
apparmor
1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get
[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock
Thanks for the confirmation @Thorsten! Now to get some maintainer eyes on it... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1651818 Title: busybox-initramfs needs different compile options to work with cryptroot-unlock Status in busybox package in Ubuntu: Confirmed Status in cryptsetup package in Ubuntu: Confirmed Bug description: The cryptroot-unlock script in the cryptsetup package does not work in initramfs. It fails because "ps -e" is not available in busybox for initramfs. When building the package with CONFIG_DESKTOP=y CONFIG_EXTRA_COMPAT=y the needed commands (ps, grep) with parameter are there and it works. Tetsted on Ubuntu GNOME 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
Same issue on a Lenovo T480s. I tried to apply this without any success : https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c -- 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/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: Connection to open or WPA secured wifi works without any issues. Connection to WPA2/PEAP fails. Repeatedly asks for username/password. Possible gnome-shell integration issue. The system was updated from Xenial to Bionic in mid-January. At that time this WPA2/PEAP setup worked without any issues. With the updates coming in the last week of January / First February week - the bug was experienced. 1) ➜ syncthing git:(master) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) - up to date packages [code] ➜ cat /etc/apt/sources.list |egrep -v '^#' deb http://cz.archive.ubuntu.com/ubuntu/ bionic main restricted deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates main restricted deb http://cz.archive.ubuntu.com/ubuntu/ bionic universe deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates universe deb http://cz.archive.ubuntu.com/ubuntu/ bionic multiverse deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates multiverse deb http://security.ubuntu.com/ubuntu/ bionic-security multiverse main universe restricted [/code] Note: # some pkg version related to problem might be from proposed-updates repo 2b) [code] dpkg -l |egrep -i 'network manager|networkm|libnm' ii gir1.2-networkmanager-1.0:amd641.8.4-1ubuntu4 amd64GObject introspection data for the libnm-glib/libnm-util library ii gir1.2-nm-1.0:amd641.8.4-1ubuntu4 amd64GObject introspection data for the libnm library ii gir1.2-nmgtk-1.0:amd64 1.8.10-2ubuntu1 amd64GObject introspection data for libnm-gtk ii libnm-glib-vpn1:amd64 1.8.4-1ubuntu4 amd64network management framework (GLib VPN shared library) ii libnm-glib4:amd64 1.8.4-1ubuntu4 amd64network management framework (GLib shared library) ii libnm-gtk0:amd64 1.8.10-2ubuntu1 amd64library for wireless and mobile dialogs (libnm-glib version) ii libnm-util2:amd64 1.8.4-1ubuntu4 amd64network management framework (shared library) ii libnm0:amd64 1.8.4-1ubuntu4 amd64GObject-based client library for NetworkManager ii libnma0:amd64 1.8.10-2ubuntu1 amd64library for wireless and mobile dialogs (libnm version) ii libproxy1-plugin-networkmanager:amd64 0.4.15-0ubuntu1 amd64automatic proxy configuration management library (Network Manager plugin) ii network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu4 all NetworkManager configuration to enable connectivity checking ii strongswan-nm 5.6.1-2ubuntu1 amd64strongSwan plugin to interact with NetworkManager ii wpasupplicant 2:2.6-15ubuntu2 amd64client support for WPA and WPA2 (IEEE 802.11i) [/code] 3,4) Connection to open or WPA secured wifi works withou any issues. Connection to WPA2/PLEAP (without cert, just with username/password fails). Although wifi layer get's is associated the client (network-manager) possibly due to bug deauthenticate itself without establishing an IP connection. Connect to network. 5) Logs (syslog/kernel) Core moments: [code] Feb 12 09:19:02 dontpanic NetworkManager[1125]: [1518423542.9125] keyfile: update /etc/NetworkManager/system-connections/WiFi (82c55e94-907a-458a-ae31-8cbd75db0fa5,"WiFi") Feb 12 09:19:02 dontpanic gnome-shell[4284]: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed and ... Feb 12 09:19:02 dontpanic NetworkManager[1125]: [1518423542.9450] device (wlp4s0): Activation: (wifi) connection 'WiFi' has
[Touch-packages] [Bug 1777476] Re: non-installable in chroots without udev installed due to bad postinst file
reuploaded with command -v udevadm >/dev/null && udevadm trigger --subsystem-match=rfkill -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1777476 Title: non-installable in chroots without udev installed due to bad postinst file Status in rfkill package in Ubuntu: Fix Released Status in rfkill source package in Xenial: In Progress Status in rfkill source package in Artful: Won't Fix Bug description: [Impact] packages using rfkill in build-dependencies are not installable. [Test Case] Install rfkill in a chroot without udev installed Unpacking rfkill (0.5-1ubuntu3) ... Setting up rfkill (0.5-1ubuntu3) ... /var/lib/dpkg/info/rfkill.postinst: 5: /var/lib/dpkg/info/rfkill.postinst: udevadm: not found dpkg: error processing package rfkill (--configure): subprocess installed post-installation script returned error exit status 127 [Regression Potential] * None, udev is already installed in user machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1777476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777476] Re: non-installable in chroots without udev installed due to bad postinst file
command -v didn't work correctly, lets go for: if [ -x /sbin/udevadm ]; then udevadm trigger --subsystem-match=rfkill fi -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1777476 Title: non-installable in chroots without udev installed due to bad postinst file Status in rfkill package in Ubuntu: Fix Released Status in rfkill source package in Xenial: In Progress Status in rfkill source package in Artful: Won't Fix Bug description: [Impact] packages using rfkill in build-dependencies are not installable. [Test Case] Install rfkill in a chroot without udev installed Unpacking rfkill (0.5-1ubuntu3) ... Setting up rfkill (0.5-1ubuntu3) ... /var/lib/dpkg/info/rfkill.postinst: 5: /var/lib/dpkg/info/rfkill.postinst: udevadm: not found dpkg: error processing package rfkill (--configure): subprocess installed post-installation script returned error exit status 127 [Regression Potential] * None, udev is already installed in user machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1777476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1659719] Re: ssh can't call a binary from a snap without the full path
I'm very reluctant to reconfigure openssh for this; it feels like a layering violation, and a regression of all the work we did way back when to avoid having to change umpteen packages when we want to change the default command search path. How about something like adding a pam_snap session module that would add itself to PATH in the PAM environment if needed, and plug that in via /usr/share/pam-configs/ ? You'd want to discuss that sort of thing with Steve Langasek, I expect, but it seems nicer than changing the configuration of individual PAM-using services. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1659719 Title: ssh can't call a binary from a snap without the full path Status in Snappy: Fix Committed Status in livecd-rootfs package in Ubuntu: Fix Committed Status in openssh package in Ubuntu: New Status in snapd package in Ubuntu: Confirmed Bug description: ssh can't call a binary from a snap, it will only work using the full path. Let's say I have the hello snap installed in 192.168.122.24. Then: elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello elopio@192.168.122.24's password: bash: hello: command not found elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello elopio@192.168.122.24's password: Hello, world! To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659719/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777476] Re: non-installable in chroots without udev installed due to bad postinst file
Some discussion here: https://irclogs.ubuntu.com/2018/06/18/%23ubuntu- release.html#t16:00 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1777476 Title: non-installable in chroots without udev installed due to bad postinst file Status in rfkill package in Ubuntu: Fix Released Status in rfkill source package in Xenial: In Progress Status in rfkill source package in Artful: Won't Fix Bug description: [Impact] packages using rfkill in build-dependencies are not installable. [Test Case] Install rfkill in a chroot without udev installed Unpacking rfkill (0.5-1ubuntu3) ... Setting up rfkill (0.5-1ubuntu3) ... /var/lib/dpkg/info/rfkill.postinst: 5: /var/lib/dpkg/info/rfkill.postinst: udevadm: not found dpkg: error processing package rfkill (--configure): subprocess installed post-installation script returned error exit status 127 [Regression Potential] * None, udev is already installed in user machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1777476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777479] [NEW] RFE: add "allow-unauthenticated" option to add-apt-repository
Public bug reported: The apt command has an "--allow-unauthenticated" option. It would be great to add "--allow-unauthenticated" to "add-apt- repository" as well. This could add the "[trusted=yes]" option to the /etc/apt/sources.list.d/my_trusted_repo.list definition. Like so: deb [trusted=yes] https://example.com/ bionic main ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- 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/1777479 Title: RFE: add "allow-unauthenticated" option to add-apt-repository Status in software-properties package in Ubuntu: New Bug description: The apt command has an "--allow-unauthenticated" option. It would be great to add "--allow-unauthenticated" to "add-apt- repository" as well. This could add the "[trusted=yes]" option to the /etc/apt/sources.list.d/my_trusted_repo.list definition. Like so: deb [trusted=yes] https://example.com/ bionic main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1777479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock
@Trent Nelson: thanks for the patch! I applied it and it's working flawlessly! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1651818 Title: busybox-initramfs needs different compile options to work with cryptroot-unlock Status in busybox package in Ubuntu: Confirmed Status in cryptsetup package in Ubuntu: Confirmed Bug description: The cryptroot-unlock script in the cryptsetup package does not work in initramfs. It fails because "ps -e" is not available in busybox for initramfs. When building the package with CONFIG_DESKTOP=y CONFIG_EXTRA_COMPAT=y the needed commands (ps, grep) with parameter are there and it works. Tetsted on Ubuntu GNOME 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777476] Re: non-installable in chroots without udev installed due to bad postinst file
the problem is: it already has a runtime dependency on systemd, why doesn't it automagically add udev? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1777476 Title: non-installable in chroots without udev installed due to bad postinst file Status in rfkill package in Ubuntu: Fix Released Status in rfkill source package in Xenial: In Progress Status in rfkill source package in Artful: Won't Fix Bug description: [Impact] packages using rfkill in build-dependencies are not installable. [Test Case] Install rfkill in a chroot without udev installed Unpacking rfkill (0.5-1ubuntu3) ... Setting up rfkill (0.5-1ubuntu3) ... /var/lib/dpkg/info/rfkill.postinst: 5: /var/lib/dpkg/info/rfkill.postinst: udevadm: not found dpkg: error processing package rfkill (--configure): subprocess installed post-installation script returned error exit status 127 [Regression Potential] * None, udev is already installed in user machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1777476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777476] Re: non-installable in chroots without udev installed due to bad postinst file
also changing the line to: udevadm trigger --subsystem-match=rfkill || true fixes the issue, giving a warning during installation -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1777476 Title: non-installable in chroots without udev installed due to bad postinst file Status in rfkill package in Ubuntu: Fix Released Status in rfkill source package in Xenial: In Progress Status in rfkill source package in Artful: Won't Fix Bug description: [Impact] packages using rfkill in build-dependencies are not installable. [Test Case] Install rfkill in a chroot without udev installed Unpacking rfkill (0.5-1ubuntu3) ... Setting up rfkill (0.5-1ubuntu3) ... /var/lib/dpkg/info/rfkill.postinst: 5: /var/lib/dpkg/info/rfkill.postinst: udevadm: not found dpkg: error processing package rfkill (--configure): subprocess installed post-installation script returned error exit status 127 [Regression Potential] * None, udev is already installed in user machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1777476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777476] Re: non-installable in chroots without udev installed due to bad postinst file
Do we really need to add a dependency here? Why not silently do nothing if udevadm isn't available? That'd fix your chroot case, right? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1777476 Title: non-installable in chroots without udev installed due to bad postinst file Status in rfkill package in Ubuntu: Fix Released Status in rfkill source package in Xenial: In Progress Status in rfkill source package in Artful: Won't Fix Bug description: [Impact] packages using rfkill in build-dependencies are not installable. [Test Case] Install rfkill in a chroot without udev installed Unpacking rfkill (0.5-1ubuntu3) ... Setting up rfkill (0.5-1ubuntu3) ... /var/lib/dpkg/info/rfkill.postinst: 5: /var/lib/dpkg/info/rfkill.postinst: udevadm: not found dpkg: error processing package rfkill (--configure): subprocess installed post-installation script returned error exit status 127 [Regression Potential] * None, udev is already installed in user machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1777476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777476] [NEW] non-installable in chroots without udev installed due to bad postinst file
Public bug reported: [Impact] packages using rfkill in build-dependencies are not installable. [Test Case] Install rfkill in a chroot without udev installed Unpacking rfkill (0.5-1ubuntu3) ... Setting up rfkill (0.5-1ubuntu3) ... /var/lib/dpkg/info/rfkill.postinst: 5: /var/lib/dpkg/info/rfkill.postinst: udevadm: not found dpkg: error processing package rfkill (--configure): subprocess installed post-installation script returned error exit status 127 [Regression Potential] * None, udev is already installed in user machines ** Affects: rfkill (Ubuntu) Importance: High Assignee: LocutusOfBorg (costamagnagianfranco) Status: Fix Released ** Affects: rfkill (Ubuntu Xenial) Importance: Undecided Status: In Progress ** Affects: rfkill (Ubuntu Artful) Importance: Undecided Status: Won't Fix ** Changed in: rfkill (Ubuntu) Status: New => Fix Released ** Changed in: rfkill (Ubuntu) Importance: Undecided => High ** Changed in: rfkill (Ubuntu) Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco) ** Also affects: rfkill (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: rfkill (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: rfkill (Ubuntu Artful) Status: New => Won't Fix ** Changed in: rfkill (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1777476 Title: non-installable in chroots without udev installed due to bad postinst file Status in rfkill package in Ubuntu: Fix Released Status in rfkill source package in Xenial: In Progress Status in rfkill source package in Artful: Won't Fix Bug description: [Impact] packages using rfkill in build-dependencies are not installable. [Test Case] Install rfkill in a chroot without udev installed Unpacking rfkill (0.5-1ubuntu3) ... Setting up rfkill (0.5-1ubuntu3) ... /var/lib/dpkg/info/rfkill.postinst: 5: /var/lib/dpkg/info/rfkill.postinst: udevadm: not found dpkg: error processing package rfkill (--configure): subprocess installed post-installation script returned error exit status 127 [Regression Potential] * None, udev is already installed in user machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1777476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777476] Re: non-installable in chroots without udev installed due to bad postinst file
Artful is mostly EOL Package is removed in Bionic. I consider enough fixing Xenial only -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1777476 Title: non-installable in chroots without udev installed due to bad postinst file Status in rfkill package in Ubuntu: Fix Released Status in rfkill source package in Xenial: In Progress Status in rfkill source package in Artful: Won't Fix Bug description: [Impact] packages using rfkill in build-dependencies are not installable. [Test Case] Install rfkill in a chroot without udev installed Unpacking rfkill (0.5-1ubuntu3) ... Setting up rfkill (0.5-1ubuntu3) ... /var/lib/dpkg/info/rfkill.postinst: 5: /var/lib/dpkg/info/rfkill.postinst: udevadm: not found dpkg: error processing package rfkill (--configure): subprocess installed post-installation script returned error exit status 127 [Regression Potential] * None, udev is already installed in user machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1777476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764965] Re: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster
Here the same issue with Kubuntu 18.04. on a Asus Prime Z370-A. I hope for fixing this problem. -- 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/1764965 Title: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recording applications (audacity, arecord, gnome-sound-recorder) record extremely slowly (at what seems to be 0,1x speed), which means that at playback the sound is played at a very high pitch and much faster than the original. To help you understand the issue, I've attached an archive containing two files recorded at the same time, one with arecord -f cd and the other with a stand-alone Olympus recorder. A video of Audacity's behavior when trying to record is also available: https://youtu.be/Fe20eQNvZVA Look at the seconds hand of the xclock and how much it is moving before Audacity is done recording one second of audio. Things I've already tried: * Purging and reinstalling Audacity * Purging and reinstalling Pulseaudio following the guide on the Ubuntu Wiki * Running audacity with this command: Exec=env PULSE_LATENCY_MSEC=30 audacity as suggested on AskUbuntu * Reinstalling Ubuntu on a new hard disk * Running audacity on a live CD (in Ubuntu version 16.04.3, 17.10.1, 18.04 daily and Xubuntu 17.10.1, 18.04) The machine is a Ryzen 5 1600 with an ASUS X370 Prime motherboard. The problem can be reproduced as follows: * Boot a live DVD of Ubuntu/Xubuntu 16.04.3, 17.10.1, 18.04 (versions I've tested with) * Install audacity via the terminal * Start recording, microphone is connected to the rear microphone jack. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacopo 2417 F pulseaudio /dev/snd/controlC0: jacopo 2417 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 18 09:35:50 2018 InstallationDate: Installed on 2018-03-03 (45 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_Type: None of the above Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1764965/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615144] Re: BUG: unable to handle kernel NULL pointer dereference
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1615144
Title:
BUG: unable to handle kernel NULL pointer dereference
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
The latest update from the Xenial InRelease repository makes the
following processes consume 100% CPU:
thermald(1.5-2ubuntu2)
imap(Dovecot 1:2.2.22-1ubuntu2)
imap-login (Dovecot 1:2.2.22-1ubuntu2)
and eventualy (after 1-2 minutes) render the system completely unresponsive.
"NMI watchdog: Watchdog detected hard LOCKUP on cpu 0".
I was able to recreate the problem on my test system, so whatever is
missing in this report should be easy to simulate on another system.
All apparmor profiles are standard.
# aa-status
apparmor module is loaded.
49 profiles are loaded.
13 profiles are in enforce mode.
/sbin/dhclient
/usr/bin/freshclam
/usr/lib/NetworkManager/nm-dhcp-client.action
/usr/lib/NetworkManager/nm-dhcp-helper
/usr/lib/chromium-browser/chromium-browser//browser_java
/usr/lib/chromium-browser/chromium-browser//browser_openjdk
/usr/lib/chromium-browser/chromium-browser//sanitized_helper
/usr/lib/connman/scripts/dhclient-script
/usr/sbin/clamd
/usr/sbin/mysqld
/usr/sbin/named
/usr/sbin/ntpd
/usr/sbin/tcpdump
36 profiles are in complain mode.
/usr/lib/chromium-browser/chromium-browser
/usr/lib/chromium-browser/chromium-browser//chromium_browser_sandbox
/usr/lib/chromium-browser/chromium-browser//lsb_release
/usr/lib/chromium-browser/chromium-browser//xdgsettings
/usr/lib/dovecot/anvil
/usr/lib/dovecot/auth
/usr/lib/dovecot/config
/usr/lib/dovecot/deliver
/usr/lib/dovecot/dict
/usr/lib/dovecot/dovecot-lda
/usr/lib/dovecot/dovecot-lda///usr/sbin/sendmail
/usr/lib/dovecot/imap
/usr/lib/dovecot/imap-login
/usr/lib/dovecot/lmtp
/usr/lib/dovecot/log
/usr/lib/dovecot/managesieve
/usr/lib/dovecot/managesieve-login
/usr/lib/dovecot/pop3
/usr/lib/dovecot/pop3-login
/usr/lib/dovecot/ssl-params
/usr/sbin/avahi-daemon
/usr/sbin/dnsmasq
/usr/sbin/dnsmasq//libvirt_leaseshelper
/usr/sbin/dovecot
/usr/sbin/identd
/usr/sbin/mdnsd
/usr/sbin/nmbd
/usr/sbin/nscd
/usr/sbin/smbd
/usr/sbin/smbldap-useradd
/usr/sbin/smbldap-useradd///etc/init.d/nscd
/usr/{sbin/traceroute,bin/traceroute.db}
/{usr/,}bin/ping
klogd
syslog-ng
syslogd
25 processes have profiles defined.
5 processes are in enforce mode.
/usr/bin/freshclam (2942)
/usr/sbin/clamd (3080)
/usr/sbin/mysqld (3767)
/usr/sbin/named (3634)
/usr/sbin/ntpd (3468)
20 processes are in complain mode.
/usr/lib/dovecot/anvil (3827)
/usr/lib/dovecot/auth (3845)
/usr/lib/dovecot/auth (4503)
/usr/lib/dovecot/config (3830)
/usr/lib/dovecot/imap (6139)
/usr/lib/dovecot/imap (6952)
/usr/lib/dovecot/imap-login (3826)
/usr/lib/dovecot/imap-login (3832)
/usr/lib/dovecot/imap-login (6048)
/usr/lib/dovecot/imap-login (7924)
/usr/lib/dovecot/imap-login (12248)
/usr/lib/dovecot/imap-login (12740)
/usr/lib/dovecot/imap-login (12816)
/usr/lib/dovecot/imap-login (14112)
/usr/lib/dovecot/imap-login (14508)
/usr/lib/dovecot/imap-login (14533)
/usr/lib/dovecot/log (3828)
/usr/lib/dovecot/managesieve-login (12794)
/usr/lib/dovecot/ssl-params (4498)
/usr/sbin/dovecot (3816)
0 processes are unconfined but have a profile defined.
# uname -r
4.4.0-34-generic
# apt-get install apparmor
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
apparmor-profiles-extra apparmor-docs apparmor-utils
The following packages will be upgraded:
apparmor
1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 446 kB of archives.
After this operation, 4,096 B of additional disk space will be used.
Get:1 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 apparmor
amd64 2.10.95-0ubuntu2.2 [446 kB]
Fetched 446 kB in 0s (4,172 kB/s)
Preconfiguring packages ...
(Reading database ... 115108 files and directories currently installed.)
Preparing to unpack .../apparmor_2.10.95-0ubuntu2.2_amd64.deb ...
Unpacking apparmor (2.10.95-0ubuntu2.2) over (2.10.95-0ubuntu2) ...
Processing triggers for systemd (229-4ubuntu7) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up apparmor (2.10.95-0ubuntu2.2) ...
Installing new version of config file
[Touch-packages] [Bug 1777438] Re: Empty Packages file breaks apt updating
Empty Packages files work just fine, e.g. cosmic-updates is empty and works. Check whether your Release file is correct, listing the uncompressed file as 0 bytes and debug with -o Debug::Acquire::http=1 and/or -o Debug::pkgAcquire::Worker=1 why the file is being downloaded and that fails. ** Changed in: apt (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1777438 Title: Empty Packages file breaks apt updating Status in apt package in Ubuntu: Incomplete Bug description: I maintain an internal repository for wheezy, jessie, trusty, xenial an bionic. With bionic started to see an issue that apt-get update waits for a long time and eventually fails with: Reading package lists... Done W: Failed to fetch https://my_repo_url/dists/bionic/myrepo/binary-i386/Packages Undetermined Error [IP: 1.2.3.4 443] W: Some index files failed to download. They have been ignored, or old ones used instead. I don't have packages in binary-i386 but I do in binary-amd64. The reason seems to be that Packages file is empty (as created by dpkg- scanpackages), since if I manually add just "#" to the file, updating works again. Empty Packages -file works in previous versions, so this seems to be a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1777438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
not foundation team but looking at the issue a) Difference is much smaller but difference between memory and SSD is still very large. b) its only triggering a read/cache of files that would be read anyways. I have quite a bit starting up on boot and if I'm reading correctly there are 2400 file and they are mostly small executables and conf files. c) As noted the cached list is smaller than 90k files More importantly in the messages I see here and for me skimming my log the messages seem to mostly be '..' or a list of individual directories in the /sys filesystem. Its weird but not useful to judge what's being cached. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761834] Re: Right-click doesn't work
Same issue with a new Dell Inspiron 5000 and Ubuntu 18.04 Xorg -- 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/1761834 Title: Right-click doesn't work Status in xorg package in Ubuntu: Confirmed Bug description: I decided to try out the beta for 18.04 from 17.10. Upon upgrading, I discovered that right-clicking no longer works on my trackpad, and right-clicks are handled as left-clicks would be. Two-finger right click does not work either. If I plug in a mouse with a physical right button, right clicking does work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 6 11:26:00 2018 DistUpgraded: 2018-04-06 11:14:08,949 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.14.15-041415-generic, x86_64: installed bbswitch, 0.8, 4.15.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4] InstallationDate: Installed on 2017-05-04 (337 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. XPS 15 9550 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic root=UUID=62d6bfc3-82e2-4ca2-9255-8dae5ad9b117 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-04-06 (0 days ago) dmi.bios.date: 08/21/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd08/21/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1659719] Re: ssh can't call a binary from a snap without the full path
** Also affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1659719 Title: ssh can't call a binary from a snap without the full path Status in Snappy: Fix Committed Status in livecd-rootfs package in Ubuntu: Fix Committed Status in openssh package in Ubuntu: New Status in snapd package in Ubuntu: Confirmed Bug description: ssh can't call a binary from a snap, it will only work using the full path. Let's say I have the hello snap installed in 192.168.122.24. Then: elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello elopio@192.168.122.24's password: bash: hello: command not found elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello elopio@192.168.122.24's password: Hello, world! To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659719/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777445] Re: /snap/bin isn't in PATH in a non-interactive shell, eg. via ssh
*** This bug is a duplicate of bug 1659719 *** https://bugs.launchpad.net/bugs/1659719 ** Also affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1777445 Title: /snap/bin isn't in PATH in a non-interactive shell, eg. via ssh Status in openssh package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: snapd 2.32.9 On a fresh VM (eg. Bionic), if from another machine I type: ssh 'echo $PATH' /snap/bin doesn't appear. This causes, for example when I'm running lxd from the snap: ssh 'lxc profile set default ...' to fail. This is similar but I think subtly different from bug 1771858 since I don't think systemd will sit between ssh and its child non-interactive session, so to fix this case do we need to hook into ssh eg. via PAM? Or edit /etc/environment. I think some proposed fixes for bug 1771858 won't fix this case so I'm filing this separately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1777445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
I filed bug 1777445 for the non-interactive ssh case. -- 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/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Won't Fix Status in snapd source package in Cosmic: Confirmed Status in systemd source package in Cosmic: Won't Fix Bug description: This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. Specifically, this is evident by e.g. $ systemd-run env. Or any other daemons that spawn shell scripts (e.g. cloud-init metadata acquired shell hooks, etc.). Since v232 systemd provides support for environment generators, snapd should package/ship a snippet that injects the correct snapd path into systemd environment. E.g.: $ sudo mkdir -p /usr/lib/systemd/system-environment-generators $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \ sudo tee /usr/lib/systemd/system-environment-generators/90-snapd Something similar can be done for user-environment-generators too. Note that user-environment-generators can generate unique variables per user. Note please use /usr/lib path, as it appears that /lib/systemd path is not working atm. Will check if that needs to be fixed up. systemd in xenial does not support system-environment-generators, thus we probably need to upload a patch to change the DEFAULT_PATH compiled in default there. [Testcase] $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
A related issue is that "ssh " currently fails because /snap/bin isn't in PATH. In that case, sshd sets PATH via pam_env. I'm not sure if a systemd environment generator will help with this use case or not. -- 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/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Won't Fix Status in snapd source package in Cosmic: Confirmed Status in systemd source package in Cosmic: Won't Fix Bug description: This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. Specifically, this is evident by e.g. $ systemd-run env. Or any other daemons that spawn shell scripts (e.g. cloud-init metadata acquired shell hooks, etc.). Since v232 systemd provides support for environment generators, snapd should package/ship a snippet that injects the correct snapd path into systemd environment. E.g.: $ sudo mkdir -p /usr/lib/systemd/system-environment-generators $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \ sudo tee /usr/lib/systemd/system-environment-generators/90-snapd Something similar can be done for user-environment-generators too. Note that user-environment-generators can generate unique variables per user. Note please use /usr/lib path, as it appears that /lib/systemd path is not working atm. Will check if that needs to be fixed up. systemd in xenial does not support system-environment-generators, thus we probably need to upload a patch to change the DEFAULT_PATH compiled in default there. [Testcase] $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772859] Re: Network Manager is not able to manage the devices on Ubuntu 18.04
> We added interfaces to the file /etc/network/interfaces. > So NM is not able to manage the interfaces updated in the said file. > When we removed the interfaces from the above file, It started working. > > Is this approach correct ?? Yes. NetworkManager, as shipped in Ubuntu, comes with multiple plugins and has networkd/ifupdown co-operation enabled by default. Out of the box, NetworkManager will not manage any regular eth devices that are already managed by somebody else which includes networkd and ifupdown. One should only ever configure one device using one of the technologies, as usually, multiple configurations of the same device using different stacks is an indication of a configuration mistake. For the eth devices, we currently prefer networkd, over NM. And the preference of wifi/3g/4g/lte-like adhoc devices is with NM, over other stacks. If you are exercising testing of various stacks, do ensure you cleanup systems to a pristine state, without any configs, for any of the stacks first, before proceeding automating using a specific network stack. Removing or not installing netplan, should not be required to achieve what you want. All Ubuntu systems should have ubuntu-minimal meta- package installed, which means netplan.io package should be left installed too. Remvoing / not-installing ubuntu-minimal, may result in upgrade and runtime issues, as such systems are harder to correctly support. Please evaluate and ensure that ubuntu-minimal is installed in your case. Given NetworkManager usage, it shouldn't add too much cruft, if installed without recommends. -- 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/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1777438] [NEW] Empty Packages file breaks apt updating
Public bug reported: I maintain an internal repository for wheezy, jessie, trusty, xenial an bionic. With bionic started to see an issue that apt-get update waits for a long time and eventually fails with: Reading package lists... Done W: Failed to fetch https://my_repo_url/dists/bionic/myrepo/binary-i386/Packages Undetermined Error [IP: 1.2.3.4 443] W: Some index files failed to download. They have been ignored, or old ones used instead. I don't have packages in binary-i386 but I do in binary-amd64. The reason seems to be that Packages file is empty (as created by dpkg- scanpackages), since if I manually add just "#" to the file, updating works again. Empty Packages -file works in previous versions, so this seems to be a regression. ** Affects: 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1777438 Title: Empty Packages file breaks apt updating Status in apt package in Ubuntu: New Bug description: I maintain an internal repository for wheezy, jessie, trusty, xenial an bionic. With bionic started to see an issue that apt-get update waits for a long time and eventually fails with: Reading package lists... Done W: Failed to fetch https://my_repo_url/dists/bionic/myrepo/binary-i386/Packages Undetermined Error [IP: 1.2.3.4 443] W: Some index files failed to download. They have been ignored, or old ones used instead. I don't have packages in binary-i386 but I do in binary-amd64. The reason seems to be that Packages file is empty (as created by dpkg- scanpackages), since if I manually add just "#" to the file, updating works again. Empty Packages -file works in previous versions, so this seems to be a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1777438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock
pls fix this! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1651818 Title: busybox-initramfs needs different compile options to work with cryptroot-unlock Status in busybox package in Ubuntu: Confirmed Status in cryptsetup package in Ubuntu: Confirmed Bug description: The cryptroot-unlock script in the cryptsetup package does not work in initramfs. It fails because "ps -e" is not available in busybox for initramfs. When building the package with CONFIG_DESKTOP=y CONFIG_EXTRA_COMPAT=y the needed commands (ps, grep) with parameter are there and it works. Tetsted on Ubuntu GNOME 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1708375] Re: Add support for purple-telegram (telepathy-haze)
** Tags removed: bionic
** Tags added: cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-mission-
control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1708375
Title:
Add support for purple-telegram (telepathy-haze)
Status in telepathy-mission-control-5 package in Ubuntu:
Confirmed
Bug description:
When using purple telegram through telepathy-haze, it requires
following permissions:
# for purple telegram
/etc/telegram-purple/server.tglpub r,
/usr/lib/purple-2*/ r,
/usr/lib/purple-2/*.somr,
/usr/share/locale/*/LC_MESSAGES/*.mo r,
/usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
@{HOME}/.purple/telegram-purple/** rw,
@{HOME}/.telegram-purple/** rw,
under /usr/lib/telepathy/telepathy-* section. See issue
https://github.com/majn/telegram-purple/issues/346 for more details.
I have attached the necessary patch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777425] Re: Skype snap segfaults GNOME Shell on Wayland
See also bug 1760487 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1777425 Title: Skype snap segfaults GNOME Shell on Wayland Status in gnome-shell package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: The Skype snap segfaults GNOME Shell on Wayland, crashing the session and sending the user back to the login screen. ``` $ snap info skype tracking: stable refresh-date: today at 11:31 BST installed: 8.22.0.2 (33) 143MB classic $ snap version snap2.33 snapd 2.33 series 16 ubuntu 18.04 kernel 4.15.0-23-generic $ snap info core tracking: beta refresh-date: 10 days ago, at 18:50 BST installed: 16-2.33(4830) 91MB core ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Jun 18 12:15:54 2018 DistUpgraded: 2018-04-22 07:24:16,565 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2017-08-03 (318 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 2347GU8 MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=ce8cd4c6-3ada-4004-acbf-e169ca40b394 ro quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: Upgraded to bionic on 2018-04-22 (57 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GU8 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1777425/+subscriptions -- Mailing list: https://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 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser
Canonical doesn't bother fixing anything. They are too busy breaking new
stuff. They expect __you__ to fix it for them.
On 06/18/2018 06:01 AM, Jon wrote:
> Ah, ok, that explains why it didn't work..
>
> Does anyone have any idea when 14.04LTS is going to get a patch? It's been
> months with nothing in sight.
>
> I thought installing an LTS meant issues would get some attention. Really
> enjoying the Linux experience overall but the lack of urgency in addressing
> a bug which is so annoying (used to work fine until one of the official
> updates broke the functionality) makes me hesitant to move more computing
> onto this platform.
>
> On Mon, 18 Jun 2018, 10:41 Colin Leroy, wrote:
>
>> Hi Jon,
>>
>> My PPA only provides packages for 16.04, because that's what we use at
>> work.
>>
>> --
>> You received this bug notification because you are subscribed to a
>> duplicate bug report (1694129).
>> https://bugs.launchpad.net/bugs/1714518
>>
>> Title:
>>GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
>>shares in file chooser
>>
>> Status in GTK+:
>>Fix Released
>> Status in gtk+3.0 package in Ubuntu:
>>Fix Released
>> Status in gtk+3.0 source package in Trusty:
>>Triaged
>> Status in gtk+3.0 source package in Xenial:
>>Triaged
>> Status in gtk+3.0 source package in Artful:
>>Triaged
>>
>> Bug description:
>>Steps to reproduce:
>>1. Install any Gtk3 application such as Firefox or Chromium which use
>> modern file-chooser dialog.
>>2. Mount network location through fstab or file-manager ("smb://" =
>> SMB/CIFS, "sftp://; = SFTP/SSH and so on)
>>3. Try to save/open file to/from the remote location from Gtk3
>> application.
>>
>>Expected results:
>>* user is able to find network folder and save/open file to/from it with
>> GtkFileChooser dialog
>>
>>Actual results:
>>* user is unable to find network folder and save/open file to/from it
>> with GtkFileChooser dialog and many user applications are affected
>>
>>-
>>Original bug description is below:
>>
>>GTK+3 doesn't show FUSE network shares in file chooser - it used to do
>>so in GTK+2, and the GTK+3 documentation still mentions it should do
>>it.
>>
>>In the mean time, every user of every application switching to GTK+3
>>-- including Chromium, at some point between 58 and 60 -- (a change
>>which happened in 16.04 LTS!!), loses the functionality to open or
>>save directly to a network share.
>>
>>I had chosen 16.04 LTS for deploying our workstations at work, and my 50
>> users have been suddenly unable to do a simple operation they have to do
>> dozens of times a day.
>>They now have to "buffer" these files to their local filesystem when
>> saving them and before uploading them, and then copy them to the company's
>> network shares.
>>They were already a little bit grumpy when it stopped working with
>> Firefox, and are now really side-eyeing me when they apply updates and find
>> Chromium broken.
>>
>>I have reported the bug upstream and provided a patch to fix this. I
>>hope you'll be able and willing to include it to Ubuntu's GTK+3
>>package.
>>
>>Thanks in advance.
>>
>>Colin
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/gtk/+bug/1714518/+subscriptions
>>
--
Roland Hughes, President
Logikal Solutions
(630)-205-1593
http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.johnsmith-book.com
http://www.logikalblog.com
http://www.interestingauthors.com/blog
http://lesedi.us/
http://onedollarcontentstore.com
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1714518
Title:
GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
shares in file chooser
Status in GTK+:
Fix Released
Status in gtk+3.0 package in Ubuntu:
Fix Released
Status in gtk+3.0 source package in Trusty:
Triaged
Status in gtk+3.0 source package in Xenial:
Triaged
Status in gtk+3.0 source package in Artful:
Triaged
Bug description:
Steps to reproduce:
1. Install any Gtk3 application such as Firefox or Chromium which use modern
file-chooser dialog.
2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS,
"sftp://; = SFTP/SSH and so on)
3. Try to save/open file to/from the remote location from Gtk3 application.
Expected results:
* user is able to find network folder and save/open file to/from it with
GtkFileChooser dialog
Actual results:
* user is unable to find network folder and save/open file to/from it with
GtkFileChooser dialog and many user applications are affected
-
Original bug description is below:
GTK+3 doesn't show FUSE network
[Touch-packages] [Bug 1777425] Re: Skype snap segfaults GNOME Shell on Wayland
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1777425 Title: Skype snap segfaults GNOME Shell on Wayland Status in gnome-shell package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: The Skype snap segfaults GNOME Shell on Wayland, crashing the session and sending the user back to the login screen. ``` $ snap info skype tracking: stable refresh-date: today at 11:31 BST installed: 8.22.0.2 (33) 143MB classic $ snap version snap2.33 snapd 2.33 series 16 ubuntu 18.04 kernel 4.15.0-23-generic $ snap info core tracking: beta refresh-date: 10 days ago, at 18:50 BST installed: 16-2.33(4830) 91MB core ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Jun 18 12:15:54 2018 DistUpgraded: 2018-04-22 07:24:16,565 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2017-08-03 (318 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 2347GU8 MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=ce8cd4c6-3ada-4004-acbf-e169ca40b394 ro quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: Upgraded to bionic on 2018-04-22 (57 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GU8 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1777425/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777425] Re: Skype snap segfaults GNOME Shell on Wayland
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1777425 Title: Skype snap segfaults GNOME Shell on Wayland Status in gnome-shell package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: The Skype snap segfaults GNOME Shell on Wayland, crashing the session and sending the user back to the login screen. ``` $ snap info skype tracking: stable refresh-date: today at 11:31 BST installed: 8.22.0.2 (33) 143MB classic $ snap version snap2.33 snapd 2.33 series 16 ubuntu 18.04 kernel 4.15.0-23-generic $ snap info core tracking: beta refresh-date: 10 days ago, at 18:50 BST installed: 16-2.33(4830) 91MB core ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Jun 18 12:15:54 2018 DistUpgraded: 2018-04-22 07:24:16,565 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2017-08-03 (318 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 2347GU8 MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=ce8cd4c6-3ada-4004-acbf-e169ca40b394 ro quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: Upgraded to bionic on 2018-04-22 (57 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GU8 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1777425/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777425] Re: Skype snap segfaults GNOME Shell on Wayland
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wayland (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1777425 Title: Skype snap segfaults GNOME Shell on Wayland Status in gnome-shell package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: The Skype snap segfaults GNOME Shell on Wayland, crashing the session and sending the user back to the login screen. ``` $ snap info skype tracking: stable refresh-date: today at 11:31 BST installed: 8.22.0.2 (33) 143MB classic $ snap version snap2.33 snapd 2.33 series 16 ubuntu 18.04 kernel 4.15.0-23-generic $ snap info core tracking: beta refresh-date: 10 days ago, at 18:50 BST installed: 16-2.33(4830) 91MB core ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Jun 18 12:15:54 2018 DistUpgraded: 2018-04-22 07:24:16,565 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2017-08-03 (318 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 2347GU8 MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=ce8cd4c6-3ada-4004-acbf-e169ca40b394 ro quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: Upgraded to bionic on 2018-04-22 (57 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GU8 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1777425/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777425] Re: Skype snap segfaults GNOME Shell on Wayland
I used `ubuntu-bug xwayland` to file this bug and apparently has filed it against xorg-server. Skype doesn't crash the X11 session, however. ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags added: wayland -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1777425 Title: Skype snap segfaults GNOME Shell on Wayland Status in gnome-shell package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: The Skype snap segfaults GNOME Shell on Wayland, crashing the session and sending the user back to the login screen. ``` $ snap info skype tracking: stable refresh-date: today at 11:31 BST installed: 8.22.0.2 (33) 143MB classic $ snap version snap2.33 snapd 2.33 series 16 ubuntu 18.04 kernel 4.15.0-23-generic $ snap info core tracking: beta refresh-date: 10 days ago, at 18:50 BST installed: 16-2.33(4830) 91MB core ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Jun 18 12:15:54 2018 DistUpgraded: 2018-04-22 07:24:16,565 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2017-08-03 (318 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 2347GU8 MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=ce8cd4c6-3ada-4004-acbf-e169ca40b394 ro quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: Upgraded to bionic on 2018-04-22 (57 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GU8 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1777425/+subscriptions -- Mailing list: https://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 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser
Ah, ok, that explains why it didn't work..
Does anyone have any idea when 14.04LTS is going to get a patch? It's been
months with nothing in sight.
I thought installing an LTS meant issues would get some attention. Really
enjoying the Linux experience overall but the lack of urgency in addressing
a bug which is so annoying (used to work fine until one of the official
updates broke the functionality) makes me hesitant to move more computing
onto this platform.
On Mon, 18 Jun 2018, 10:41 Colin Leroy, wrote:
> Hi Jon,
>
> My PPA only provides packages for 16.04, because that's what we use at
> work.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1694129).
> https://bugs.launchpad.net/bugs/1714518
>
> Title:
> GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
> shares in file chooser
>
> Status in GTK+:
> Fix Released
> Status in gtk+3.0 package in Ubuntu:
> Fix Released
> Status in gtk+3.0 source package in Trusty:
> Triaged
> Status in gtk+3.0 source package in Xenial:
> Triaged
> Status in gtk+3.0 source package in Artful:
> Triaged
>
> Bug description:
> Steps to reproduce:
> 1. Install any Gtk3 application such as Firefox or Chromium which use
> modern file-chooser dialog.
> 2. Mount network location through fstab or file-manager ("smb://" =
> SMB/CIFS, "sftp://; = SFTP/SSH and so on)
> 3. Try to save/open file to/from the remote location from Gtk3
> application.
>
> Expected results:
> * user is able to find network folder and save/open file to/from it with
> GtkFileChooser dialog
>
> Actual results:
> * user is unable to find network folder and save/open file to/from it
> with GtkFileChooser dialog and many user applications are affected
>
> -
> Original bug description is below:
>
> GTK+3 doesn't show FUSE network shares in file chooser - it used to do
> so in GTK+2, and the GTK+3 documentation still mentions it should do
> it.
>
> In the mean time, every user of every application switching to GTK+3
> -- including Chromium, at some point between 58 and 60 -- (a change
> which happened in 16.04 LTS!!), loses the functionality to open or
> save directly to a network share.
>
> I had chosen 16.04 LTS for deploying our workstations at work, and my 50
> users have been suddenly unable to do a simple operation they have to do
> dozens of times a day.
> They now have to "buffer" these files to their local filesystem when
> saving them and before uploading them, and then copy them to the company's
> network shares.
> They were already a little bit grumpy when it stopped working with
> Firefox, and are now really side-eyeing me when they apply updates and find
> Chromium broken.
>
> I have reported the bug upstream and provided a patch to fix this. I
> hope you'll be able and willing to include it to Ubuntu's GTK+3
> package.
>
> Thanks in advance.
>
> Colin
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gtk/+bug/1714518/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1714518
Title:
GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
shares in file chooser
Status in GTK+:
Fix Released
Status in gtk+3.0 package in Ubuntu:
Fix Released
Status in gtk+3.0 source package in Trusty:
Triaged
Status in gtk+3.0 source package in Xenial:
Triaged
Status in gtk+3.0 source package in Artful:
Triaged
Bug description:
Steps to reproduce:
1. Install any Gtk3 application such as Firefox or Chromium which use modern
file-chooser dialog.
2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS,
"sftp://; = SFTP/SSH and so on)
3. Try to save/open file to/from the remote location from Gtk3 application.
Expected results:
* user is able to find network folder and save/open file to/from it with
GtkFileChooser dialog
Actual results:
* user is unable to find network folder and save/open file to/from it with
GtkFileChooser dialog and many user applications are affected
-
Original bug description is below:
GTK+3 doesn't show FUSE network shares in file chooser - it used to do
so in GTK+2, and the GTK+3 documentation still mentions it should do
it.
In the mean time, every user of every application switching to GTK+3
-- including Chromium, at some point between 58 and 60 -- (a change
which happened in 16.04 LTS!!), loses the functionality to open or
save directly to a network share.
I had chosen 16.04 LTS for deploying our workstations at work, and my 50
users have been suddenly unable to do a simple operation they have to do dozens
of times a day.
They now have to "buffer" these
[Touch-packages] [Bug 1773213] Re: U1 login dialog missing link to the privacy policy
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1773213 Title: U1 login dialog missing link to the privacy policy Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Bionic: Fix Committed Bug description: The U1 login for g-o-a is missing a link to the privacy policy. [Impact] * No way to view the privacy policy for Ubuntu One [Test Case] * Open gnome-control-center * Select "Online Accounts" on the left * Select "Ubuntu Single Sign-On" under "Add an account" * Not you should see a link to open the Privacy Policy on the bottom left of the dialog. * Verify when clicking the window a browser window opens with our data privacy page [Regression Potential] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1773213/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773213] Re: U1 login dialog missing link to the privacy policy
I can confirm this is working as intended. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1773213 Title: U1 login dialog missing link to the privacy policy Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Bionic: Fix Committed Bug description: The U1 login for g-o-a is missing a link to the privacy policy. [Impact] * No way to view the privacy policy for Ubuntu One [Test Case] * Open gnome-control-center * Select "Online Accounts" on the left * Select "Ubuntu Single Sign-On" under "Add an account" * Not you should see a link to open the Privacy Policy on the bottom left of the dialog. * Verify when clicking the window a browser window opens with our data privacy page [Regression Potential] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1773213/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags removed: verification-needed-artful verification-needed-bionic ** Tags added: verification-done-artful verification-done-bionic -- 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/1768905 Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Incomplete Status in menu package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in menu source package in Xenial: Fix Committed Status in apt source package in Artful: Confirmed Status in menu source package in Artful: Fix Committed Status in apt source package in Bionic: Confirmed Status in menu source package in Bionic: Fix Committed Status in menu package in Debian: New Bug description: [Impact] Breaks some upgrades, depending on install order. [Test case] N/A. After consultation with the dpkg maintainer and investigating the situation, it's reasonably safe to assume that noawait is the right thing to do: * the intended use for the trigger is to run _after_ packages with .menu files are configured, not before; therefore * the file trigger is triggered manually from the postinst again, discussion has been that the file trigger is not actually needed. [Regression potential] Menu might not be updated correctly [Original bug report] I get this error when I update to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: menu 2.1.47ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 16:51:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-11 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: menu Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser
Hi Jon,
My PPA only provides packages for 16.04, because that's what we use at
work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1714518
Title:
GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
shares in file chooser
Status in GTK+:
Fix Released
Status in gtk+3.0 package in Ubuntu:
Fix Released
Status in gtk+3.0 source package in Trusty:
Triaged
Status in gtk+3.0 source package in Xenial:
Triaged
Status in gtk+3.0 source package in Artful:
Triaged
Bug description:
Steps to reproduce:
1. Install any Gtk3 application such as Firefox or Chromium which use modern
file-chooser dialog.
2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS,
"sftp://; = SFTP/SSH and so on)
3. Try to save/open file to/from the remote location from Gtk3 application.
Expected results:
* user is able to find network folder and save/open file to/from it with
GtkFileChooser dialog
Actual results:
* user is unable to find network folder and save/open file to/from it with
GtkFileChooser dialog and many user applications are affected
-
Original bug description is below:
GTK+3 doesn't show FUSE network shares in file chooser - it used to do
so in GTK+2, and the GTK+3 documentation still mentions it should do
it.
In the mean time, every user of every application switching to GTK+3
-- including Chromium, at some point between 58 and 60 -- (a change
which happened in 16.04 LTS!!), loses the functionality to open or
save directly to a network share.
I had chosen 16.04 LTS for deploying our workstations at work, and my 50
users have been suddenly unable to do a simple operation they have to do dozens
of times a day.
They now have to "buffer" these files to their local filesystem when saving
them and before uploading them, and then copy them to the company's network
shares.
They were already a little bit grumpy when it stopped working with Firefox,
and are now really side-eyeing me when they apply updates and find Chromium
broken.
I have reported the bug upstream and provided a patch to fix this. I
hope you'll be able and willing to include it to Ubuntu's GTK+3
package.
Thanks in advance.
Colin
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1714518/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu Bionic) Status: New => Confirmed -- 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/1768905 Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Incomplete Status in menu package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in menu source package in Xenial: Fix Committed Status in apt source package in Artful: Confirmed Status in menu source package in Artful: Fix Committed Status in apt source package in Bionic: Confirmed Status in menu source package in Bionic: Fix Committed Status in menu package in Debian: New Bug description: [Impact] Breaks some upgrades, depending on install order. [Test case] N/A. After consultation with the dpkg maintainer and investigating the situation, it's reasonably safe to assume that noawait is the right thing to do: * the intended use for the trigger is to run _after_ packages with .menu files are configured, not before; therefore * the file trigger is triggered manually from the postinst again, discussion has been that the file trigger is not actually needed. [Regression potential] Menu might not be updated correctly [Original bug report] I get this error when I update to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: menu 2.1.47ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 16:51:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-11 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: menu Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773316] Re: Object of different cache passed as argument to apt_pkg.DepCache method
This bug was fixed in the package python-apt - 1.6.1 --- python-apt (1.6.1) unstable; urgency=medium * apt: Fix typing errors to get CI pass again * apt.Cache: Remap objects when reopening cache (LP: #1773316) * apt_pkg.DepCache: Raise CacheMismatchError if argument belongs to diff. cache * Set branch to 1.6.y and adjust travis CI to run against stable releases * travis CI / Dockerfile: Pin mypy to 0.600 to prevent future changes breaking CI * utils/get_debian_mirrors.py: Get data from salsa -- Julian Andres Klode Wed, 06 Jun 2018 15:14:59 -0700 ** Changed in: python-apt (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Won't Fix Status in python-apt source package in Bionic: Fix Released Status in update-manager source package in Bionic: Won't Fix Status in python-apt source package in Cosmic: Fix Released Status in update-manager source package in Cosmic: Won't Fix Bug description: [Impact] python-apt 1.6 raises an exception when objects of an old cache are passed to a apt_pkg.DepCache methods for a different cache. Prior to that, those would either segfault, succeed, or silently operate on a different object, as they use package/version ids, and e.g. two different packages in the old and new cache might have the same id. With 1.6.1, we introduce a remapping algorithm that remaps objects of apt.Cache() when calling apt.Cache.open(), allowing old objects to be used after reopening, as long as they exist in the new cache. If they don't exist in the new cache, apt_pkg.CacheMismatchError will be raised from the apt_pkg layer. [Test case] import apt c=apt.Cache() p=c["apt"] c.open() p.mark_install() [Regression potential] Could be remapping to wrong items which would cause us to install a wrong version, for example. Compared to pre-bionic, bionic is a regression already, though, and any regression caused here is less important than what we have now. [Original bug report] The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 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/python-apt/+bug/1773316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu Xenial) Status: New => Confirmed -- 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/1768905 Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Incomplete Status in menu package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in menu source package in Xenial: Fix Committed Status in apt source package in Artful: Confirmed Status in menu source package in Artful: Fix Committed Status in apt source package in Bionic: Confirmed Status in menu source package in Bionic: Fix Committed Status in menu package in Debian: New Bug description: [Impact] Breaks some upgrades, depending on install order. [Test case] N/A. After consultation with the dpkg maintainer and investigating the situation, it's reasonably safe to assume that noawait is the right thing to do: * the intended use for the trigger is to run _after_ packages with .menu files are configured, not before; therefore * the file trigger is triggered manually from the postinst again, discussion has been that the file trigger is not actually needed. [Regression potential] Menu might not be updated correctly [Original bug report] I get this error when I update to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: menu 2.1.47ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 16:51:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-11 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: menu Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu Artful) Status: New => Confirmed -- 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/1768905 Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Incomplete Status in menu package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in menu source package in Xenial: Fix Committed Status in apt source package in Artful: Confirmed Status in menu source package in Artful: Fix Committed Status in apt source package in Bionic: Confirmed Status in menu source package in Bionic: Fix Committed Status in menu package in Debian: New Bug description: [Impact] Breaks some upgrades, depending on install order. [Test case] N/A. After consultation with the dpkg maintainer and investigating the situation, it's reasonably safe to assume that noawait is the right thing to do: * the intended use for the trigger is to run _after_ packages with .menu files are configured, not before; therefore * the file trigger is triggered manually from the postinst again, discussion has been that the file trigger is not actually needed. [Regression potential] Menu might not be updated correctly [Original bug report] I get this error when I update to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: menu 2.1.47ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 16:51:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-11 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: menu Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
I have not heard about any regressions in proposed, so I think we should start releasing the update for bionic and artful now and watch out for those in the release pocket. If we don't see issues with that, we can then roll out xenial next week to give it some more time to mature in a less used release. -- 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/1768905 Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Incomplete Status in menu package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in menu source package in Xenial: Fix Committed Status in apt source package in Artful: Confirmed Status in menu source package in Artful: Fix Committed Status in apt source package in Bionic: Confirmed Status in menu source package in Bionic: Fix Committed Status in menu package in Debian: New Bug description: [Impact] Breaks some upgrades, depending on install order. [Test case] N/A. After consultation with the dpkg maintainer and investigating the situation, it's reasonably safe to assume that noawait is the right thing to do: * the intended use for the trigger is to run _after_ packages with .menu files are configured, not before; therefore * the file trigger is triggered manually from the postinst again, discussion has been that the file trigger is not actually needed. [Regression potential] Menu might not be updated correctly [Original bug report] I get this error when I update to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: menu 2.1.47ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 16:51:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-11 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: menu Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css
This bug was fixed in the package gnome-control-center - 1:3.28.1-0ubuntu1.18.04.1 --- gnome-control-center (1:3.28.1-0ubuntu1.18.04.1) bionic; urgency=medium * debian/patches/0001-shell-Don-t-set-per-panel-icon.patch, debian/patches/0002-shell-Icon-name-helper-returns-symbolic-name.patch, debian/patches/0003-thunderbolt-new-panel-for-device-management.patch, debian/patches/0004-thunderbolt-move-to-the-Devices-page.patch: - backport the new upstream "thunderbolt" panel (same patches as fedora is using). Also change to not use per panel icons but just the settings one, that's the right thing to do and avoid issues when some panels like the thunderbolt one don't have a symbolic icon. (lp: #1773378) * debian/patches/git_select_panel.patch: - "Only try to select an existing panel on startup", otherwise it's possible to hit a segfault (lp: #1773382) [ Andrea Azzarone ] * debian/patches/git_invalid_dereferencing.patch: - Avoid dereferencing invalid pointer (lp: #1759468) -- Sebastien Bacher Fri, 25 May 2018 15:51:57 +0200 ** Changed in: gnome-control-center (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1759468 Title: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css_node_validate_internal Status in gnome-control-center package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Fix Released Bug description: * Impact gnome-control-center sometimes hits a segfault * Test case - Check if the e.u.c reports stop with the new version or - Open GNOME Control Center - Go to Devices->Display panel - Close the window - Open GNOME Control Center again (in overview mode) the settings should open without error * Regression potential check the panels can be opened without error and that switching between them works as well -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.28.0-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/6b1f4dd86167bf5eb53ddca8469b5084208ddd22 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/gnome-control-center/+bug/1759468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css
Since this is an errors.u.c based bug I will release it as is (since I don't see any occurrences of the crash for the -proposed version), but next time please be sure to always include some information about the testing as otherwise the verification might not be accepted. We're looking for things like: package version used and what tests have been performed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1759468 Title: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css_node_validate_internal Status in gnome-control-center package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Fix Released Bug description: * Impact gnome-control-center sometimes hits a segfault * Test case - Check if the e.u.c reports stop with the new version or - Open GNOME Control Center - Go to Devices->Display panel - Close the window - Open GNOME Control Center again (in overview mode) the settings should open without error * Regression potential check the panels can be opened without error and that switching between them works as well -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.28.0-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/6b1f4dd86167bf5eb53ddca8469b5084208ddd22 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/gnome-control-center/+bug/1759468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759468] Update Released
The verification of the Stable Release Update for gnome-control-center 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 gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1759468 Title: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css_node_validate_internal Status in gnome-control-center package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Fix Released Bug description: * Impact gnome-control-center sometimes hits a segfault * Test case - Check if the e.u.c reports stop with the new version or - Open GNOME Control Center - Go to Devices->Display panel - Close the window - Open GNOME Control Center again (in overview mode) the settings should open without error * Regression potential check the panels can be opened without error and that switching between them works as well -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.28.0-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/6b1f4dd86167bf5eb53ddca8469b5084208ddd22 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/gnome-control-center/+bug/1759468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773316] Update Released
The verification of the Stable Release Update for python-apt 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 python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Won't Fix Status in python-apt source package in Bionic: Fix Released Status in update-manager source package in Bionic: Won't Fix Status in python-apt source package in Cosmic: Fix Released Status in update-manager source package in Cosmic: Won't Fix Bug description: [Impact] python-apt 1.6 raises an exception when objects of an old cache are passed to a apt_pkg.DepCache methods for a different cache. Prior to that, those would either segfault, succeed, or silently operate on a different object, as they use package/version ids, and e.g. two different packages in the old and new cache might have the same id. With 1.6.1, we introduce a remapping algorithm that remaps objects of apt.Cache() when calling apt.Cache.open(), allowing old objects to be used after reopening, as long as they exist in the new cache. If they don't exist in the new cache, apt_pkg.CacheMismatchError will be raised from the apt_pkg layer. [Test case] import apt c=apt.Cache() p=c["apt"] c.open() p.mark_install() [Regression potential] Could be remapping to wrong items which would cause us to install a wrong version, for example. Compared to pre-bionic, bionic is a regression already, though, and any regression caused here is less important than what we have now. [Original bug report] The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 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/python-apt/+bug/1773316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1
** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/1777099 Title: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1 Status in OEM Priority Project: New Status in systemd: Fix Released Status in systemd package in Ubuntu: Triaged Bug description: refer to https://github.com/systemd/systemd/issues/6908 we need that solution to make NVIDIA dGPU switching works. impacted issue: https://bugs.launchpad.net/somerville/+bug/1774326 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1777099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
I have the same issue with (a clean/full wipe/ fresh install) Ubuntu 18.04 on a Dell XPS 15 9550. Previously, on Ubuntu 16.04 downgrading wpa_supplicant to version 2.1 helped resolve this. See here: https://askubuntu.com/questions/690032 /after-upgrade-to-15-10-wifi-to-a-corporate-network-wpa2-is-not-working- anymore However, downgrading further then 2.6 is as far as I know not possible on Ubuntu 18.04, see my related question: https://askubuntu.com/questions/1046810/cannot-downgrade-wpa-supplicant- to-fix-wifi-connection-to-a-corporate-network-w -- 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/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: Connection to open or WPA secured wifi works without any issues. Connection to WPA2/PEAP fails. Repeatedly asks for username/password. Possible gnome-shell integration issue. The system was updated from Xenial to Bionic in mid-January. At that time this WPA2/PEAP setup worked without any issues. With the updates coming in the last week of January / First February week - the bug was experienced. 1) ➜ syncthing git:(master) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) - up to date packages [code] ➜ cat /etc/apt/sources.list |egrep -v '^#' deb http://cz.archive.ubuntu.com/ubuntu/ bionic main restricted deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates main restricted deb http://cz.archive.ubuntu.com/ubuntu/ bionic universe deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates universe deb http://cz.archive.ubuntu.com/ubuntu/ bionic multiverse deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates multiverse deb http://security.ubuntu.com/ubuntu/ bionic-security multiverse main universe restricted [/code] Note: # some pkg version related to problem might be from proposed-updates repo 2b) [code] dpkg -l |egrep -i 'network manager|networkm|libnm' ii gir1.2-networkmanager-1.0:amd641.8.4-1ubuntu4 amd64GObject introspection data for the libnm-glib/libnm-util library ii gir1.2-nm-1.0:amd641.8.4-1ubuntu4 amd64GObject introspection data for the libnm library ii gir1.2-nmgtk-1.0:amd64 1.8.10-2ubuntu1 amd64GObject introspection data for libnm-gtk ii libnm-glib-vpn1:amd64 1.8.4-1ubuntu4 amd64network management framework (GLib VPN shared library) ii libnm-glib4:amd64 1.8.4-1ubuntu4 amd64network management framework (GLib shared library) ii libnm-gtk0:amd64 1.8.10-2ubuntu1 amd64library for wireless and mobile dialogs (libnm-glib version) ii libnm-util2:amd64 1.8.4-1ubuntu4 amd64network management framework (shared library) ii libnm0:amd64 1.8.4-1ubuntu4 amd64GObject-based client library for NetworkManager ii libnma0:amd64 1.8.10-2ubuntu1 amd64library for wireless and mobile dialogs (libnm version) ii libproxy1-plugin-networkmanager:amd64 0.4.15-0ubuntu1 amd64automatic proxy configuration management library (Network Manager plugin) ii network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu4 all NetworkManager configuration to enable connectivity checking ii strongswan-nm 5.6.1-2ubuntu1 amd64strongSwan plugin to interact with NetworkManager ii wpasupplicant 2:2.6-15ubuntu2 amd64client support for WPA and WPA2 (IEEE 802.11i) [/code] 3,4) Connection to open or WPA secured wifi works withou any issues. Connection to WPA2/PLEAP (without cert, just with username/password fails). Although wifi layer get's is associated the client (network-manager) possibly due to bug deauthenticate itself without establishing an IP connection. Connect to network. 5) Logs (syslog/kernel) Core moments: [code] Feb 12 09:19:02 dontpanic NetworkManager[1125]: [1518423542.9125] keyfile: update
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
It's indeed a big mystery when one of the maybe most serious bugs in 18.04 is marked as fixed while it clearly is not -- 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
