[Bug 2038916] Re: php8.2-apcu fails with " undefined symbol: php_strlcpy"
Thanks comment #4, it works. Why hasn't this bug been fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038916 Title: php8.2-apcu fails with " undefined symbol: php_strlcpy" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-apcu/+bug/2038916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056706] Re: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0"
One of my VM's is affected too, running under Xen with XCP-ng. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056706 Title: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970871] [NEW] Misbehaving context menu in autohide dock mode
Public bug reported: Steps to reproduce: Configure Ubuntu-dock to be a dock with auto hide enabled. Also move it to the lower edge of the screen. Have any application overlapping with the dock for triggering the auto hide. Move mouse to lower screen edge to show dock, then right click on any application icon, open the apps context menu and move the cursor up to any of the context menu entry and click it. What happens: As soon as you click at a context menu item, the dock auto hides and the whole context menu window moves down and aligns with the lower edge of the screen which leads to selecting a wrong menu item above the selected one. Reproducible. Does not happen if no overlapping window triggers the dock to hide. What should happen: The context menu shouldn't move at all while the cursor is interacting with it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 08:04:40 2022 InstallationDate: Installed on 2022-04-23 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970871 Title: Misbehaving context menu in autohide dock mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1970871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970090] Re: Backintime not launching because of python error
** Description changed: - Expectations: App launches and create an application windows. + Expectation: App launches and create an application window. What happens: App does not launch. Terminal output: backintime-qt Traceback (most recent call last): - File "/usr/share/backintime/qt/app.py", line 35, in - import qttools - File "/usr/share/backintime/qt/qttools.py", line 47, in - import snapshots - File "/usr/share/backintime/common/snapshots.py", line 34, in - import config - File "/usr/share/backintime/common/config.py", line 32, in - import tools - File "/usr/share/backintime/common/tools.py", line 1802, in - class OrderedSet(collections.MutableSet): + File "/usr/share/backintime/qt/app.py", line 35, in + import qttools + File "/usr/share/backintime/qt/qttools.py", line 47, in + import snapshots + File "/usr/share/backintime/common/snapshots.py", line 34, in + import config + File "/usr/share/backintime/common/config.py", line 32, in + import tools + File "/usr/share/backintime/common/tools.py", line 1802, in + class OrderedSet(collections.MutableSet): AttributeError: module 'collections' has no attribute 'MutableSet' ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: backintime-qt 1.2.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 24 11:54:26 2022 InstallationDate: Installed on 2022-04-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash SourcePackage: backintime UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970090 Title: Backintime not launching because of python error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/1970090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821237] Re: Monitors cycle on and off repeatedly when session is locked
Current releases are not affected any more. 22.04 works as intended. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821237 Title: Monitors cycle on and off repeatedly when session is locked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1821237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970090] [NEW] Backintime not launching because of python error
Public bug reported: Expectations: App launches and create an application windows. What happens: App does not launch. Terminal output: backintime-qt Traceback (most recent call last): File "/usr/share/backintime/qt/app.py", line 35, in import qttools File "/usr/share/backintime/qt/qttools.py", line 47, in import snapshots File "/usr/share/backintime/common/snapshots.py", line 34, in import config File "/usr/share/backintime/common/config.py", line 32, in import tools File "/usr/share/backintime/common/tools.py", line 1802, in class OrderedSet(collections.MutableSet): AttributeError: module 'collections' has no attribute 'MutableSet' ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: backintime-qt 1.2.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 24 11:54:26 2022 InstallationDate: Installed on 2022-04-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: backintime UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: backintime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970090 Title: Backintime not launching because of python error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/1970090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918916] Re: undefined reference to `FT_Palette_Select' and `FT_Get_Color_Glyph_Layer'
This was caused by the android sdk installing its own version of freetype2... ** Changed in: qtwebengine-opensource-src (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918916 Title: undefined reference to `FT_Palette_Select' and `FT_Get_Color_Glyph_Layer' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebengine-opensource-src/+bug/1918916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918916] Re: undefined reference to `FT_Palette_Select' and `FT_Get_Color_Glyph_Layer'
Sorry, this is because the android SDK have installed it's own version of freetype2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918916 Title: undefined reference to `FT_Palette_Select' and `FT_Get_Color_Glyph_Layer' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebengine-opensource-src/+bug/1918916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918916] [NEW] undefined reference to `FT_Palette_Select' and `FT_Get_Color_Glyph_Layer'
Public bug reported: Hi, I'm having some problems with running and building nextcloud-desktop and have tracked it to libqt5webenginecore5. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu > lsb_release -rd Description:Ubuntu 20.10 Release:20.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center > apt-cache policy libqt5webenginecore5 libqt5webenginecore5: Installed: 5.14.2+dfsg1-5 Candidate: 5.14.2+dfsg1-5 Version table: *** 5.14.2+dfsg1-5 500 500 http://dk.archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I expected to be able run and compile applications using libqt5webenginecore5. 4) What happened instead If I run nextcloud-desktop or try to compile it myself, I get these errors. /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5.14.2: undefined reference to `FT_Palette_Select' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5.14.2: undefined reference to `FT_Get_Color_Glyph_Layer' collect2: error: ld returned 1 exit status >From what I can tell it has something to do with linking to freetype2: https://www.freetype.org/freetype2/docs/reference/ft2-color_management.html#ft_palette_select It is a fresh minimal install of Kubuntu 20.10. libqt5webenginecore5:amd64 is version: 5.14.2+dfsg1-5. ** Affects: qtwebengine-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918916 Title: undefined reference to `FT_Palette_Select' and `FT_Get_Color_Glyph_Layer' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebengine-opensource-src/+bug/1918916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918310] [NEW] evince doesn't represent transparency in PDFs
Public bug reported: Transparency in pdfs isn't represented by the standard checkered, gray pattern. Instead evince just sets the background to white. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918310 Title: evince doesn't represent transparency in PDFs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1918310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905200] Re: Ubuntu-dock in Wayland slow
Please mark this bug as duplicate of Bug #1874578 Saw the bug report to late. Issue immediately vanishes after hiding mounted devices in the dock with: gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts false -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905200 Title: Ubuntu-dock in Wayland slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1905200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874578] Re: [wayland] dock has very long load time when show-mounts is enabled
I can confirm this bug an completely vanilla 20.04 and 20.10 installs on two completely different machines. Long startup for icons to appear at boot, non favourite apps will appear with delay and moving apps will also have a big delay to appear in the new order. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874578 Title: [wayland] dock has very long load time when show-mounts is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1874578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905200] [NEW] Ubuntu-dock in Wayland slow
Public bug reported: Only in Ubuntu's wayland session, on 20.04 and 20.10: App icons will appear with a massive delay (~10 seconds) after launching an app currently not in the favorites. Also moving pinned icons within the dock will only appear in the new location after a similar long time span. Otherwise the dock works without delays. I could see this behavior on two completely different machines. No problems in the default Xorg session. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 21:46:23 2020 InstallationDate: Installed on 2020-11-22 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905200 Title: Ubuntu-dock in Wayland slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1905200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905173] [NEW] Calibre crashes at launch
Public bug reported: Calibre crashes at every launch, tested on two machines. Traceback (most recent call last): File "/usr/bin/calibre", line 20, in sys.exit(calibre()) File "/usr/lib/calibre/calibre/gui_launch.py", line 73, in calibre main(args) File "/usr/lib/calibre/calibre/gui2/main.py", line 543, in main listener = create_listener() File "/usr/lib/calibre/calibre/gui2/main.py", line 514, in create_listener return Listener(address=gui_socket_address()) File "/usr/lib/calibre/calibre/utils/ipc/server.py", line 110, in __init__ self._listener._unlink.cancel() AttributeError: 'NoneType' object has no attribute 'cancel' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: calibre 4.99.4+dfsg+really4.12.0-1build1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 15:16:26 2020 InstallationDate: Installed on 2020-11-22 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/fish SourcePackage: calibre UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: calibre (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905173 Title: Calibre crashes at launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1905173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902675] [NEW] package shim-signed 1.40.4+15+1552672080.a4a1fbe-0ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: This bug started when i tried to install an Opencv package called "opencv2/nonfree/nonfree.hpp" for C++. I tried installing following the package following the steps in the answer in this thread "https://stackoverflow.com/questions/28525810/fatal-error-opencv2 -nonfree-nonfree-hpp-no-such-file-or-directory". I have Opencv version 4.2 installed. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: shim-signed 1.40.4+15+1552672080.a4a1fbe-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootEFIContents: BOOTX64.CSV grub.cfg grubx64.efi mmx64.efi shimx64.efi CasperMD5CheckResult: skip Date: Mon Nov 2 16:16:53 2020 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2020-09-22 (41 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SecureBoot: 6 0 0 0 1 SourcePackage: shim-signed Title: package shim-signed 1.40.4+15+1552672080.a4a1fbe-0ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902675 Title: package shim-signed 1.40.4+15+1552672080.a4a1fbe-0ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1902675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900396] [NEW] netstat man-page does not explain -t|--tcp, -u|--udp or -w|--raw
Public bug reported: I tried looking up `netstat -tlnp` on https://explainshell.com, but there was no explanation for `-t`. It turns out that at least `-t|--tcp`, `-u|--udp` and `-w|--raw` aren't documented in the man-page (http://manpages.ubuntu.com/manpages/precise/en/man8/netstat.8.html). ** Affects: net-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900396 Title: netstat man-page does not explain -t|--tcp, -u|--udp or -w|--raw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1900396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1895202] Re: touchpad suddenly not detected, appearing as PS/2 mouse in devices
FWIW, I do this dance after boot and the touchpad works... ➜ ~ sudo modprobe psmouse [sudo] passord for ole: ➜ ~ sudo rmmod psmouse ➜ ~ sudo modprobe psmouse Sincerely, Ole ons. 23. sep. 2020 kl. 23:29 skrev Ole Morten Heggebakken Amundsen < ole.morten.amund...@gmail.com>: > The problem persists on 5.4.0-48 sadly, I still need to select advanced in > grub, selecting 5.4.0-42 for the touchpad to work. > > *➜ ~ xinput --list* > > *5.4.0-42* > > ⎡ Virtual core pointer id=2 [master pointer (3)] > ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] > ⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [slave pointer (2)] > ⎜ ↳ TPPS/2 Elan TrackPoint id=12 [slave pointer (2)] > ⎣ Virtual core keyboard id=3 [master keyboard (2)] > ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] > ↳ Power Button id=6 [slave keyboard (3)] > ↳ Video Bus id=7 [slave keyboard (3)] > ↳ Sleep Button id=8 [slave keyboard (3)] > ↳ Integrated Camera: Integrated C id=9 [slave keyboard (3)] > ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)] > ↳ ThinkPad Extra Buttons > > *5.4.0-48* > > ⎡ Virtual core pointer id=2 [master pointer (3)] > ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] > ⎜ ↳ Synaptics TM3418-002 id=12 [slave pointer (2)] > ⎜ ↳ PS/2 Generic Mouse id=13 [slave pointer (2)] > ⎣ Virtual core keyboard id=3 [master keyboard (2)] > ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] > ↳ Power Button id=6 [slave keyboard (3)] > ↳ Video Bus id=7 [slave keyboard (3)] > ↳ Sleep Button id=8 [slave keyboard (3)] > ↳ Integrated Camera: Integrated C id=9 [slave keyboard (3)] > ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)] > ↳ ThinkPad Extra Buttons id=11 [slave keyboard (3)] > > *➜ ~ cat /var/log/Xorg.0.log | grep -i synaptics* > > *5.4.0-42* > > [16.093] (II) config/udev: Adding input device SynPS/2 Synaptics > TouchPad (/dev/input/event5) > [16.093] (**) SynPS/2 Synaptics TouchPad: Applying InputClass > "libinput touchpad catchall" > [16.093] (II) Using input driver 'libinput' for 'SynPS/2 Synaptics > TouchPad' > [16.094] (**) SynPS/2 Synaptics TouchPad: always reports core events > [16.095] (II) event5 - SynPS/2 Synaptics TouchPad: is tagged by udev > as: Touchpad > [16.095] (II) event5 - SynPS/2 Synaptics TouchPad: device is a > touchpad > [16.096] (II) event5 - SynPS/2 Synaptics TouchPad: device removed > [16.096] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics > TouchPad" (type: TOUCHPAD, id 11) > [16.096] (**) SynPS/2 Synaptics TouchPad: (accel) selected scheme > none/0 > [16.096] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: > 2.000 > [16.096] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration > threshold: 4 > [16.097] (II) event5 - SynPS/2 Synaptics TouchPad: is tagged by udev > as: Touchpad > [16.098] (II) event5 - SynPS/2 Synaptics TouchPad: device is a > touchpad > [16.098] (II) config/udev: Adding input device SynPS/2 Synaptics > TouchPad (/dev/input/mouse0) > [23.216] (II) event5 - SynPS/2 Synaptics TouchPad: device removed > > *5.4.0-48* > > [12.467] (II) config/udev: Adding input device Synaptics TM3418-002 > (/dev/input/event9) > [12.467] (**) Synaptics TM3418-002: Applying InputClass "libinput > touchpad catchall" > [12.467] (II) Using input driver 'libinput' for 'Synaptics TM3418-002' > [12.468] (**) Synaptics TM3418-002: always reports core events > [12.469] (II) event9 - Synaptics TM3418-002: is tagged by udev as: > Touchpad > [12.470] (II) event9 - Synaptics TM3418-002: device is a touchpad > [12.470] (II) event9 - Synaptics TM3418-002: device removed > [12.470] (II) XINPUT: Adding extended input device "Synaptics > TM3418-002" (type: TOUCHPAD, id 12) > [12.470] (**) Synaptics TM3418-002: (accel) selected scheme none/0 > [12.470] (**) Synaptics TM3418-002: (accel) acceleration factor: 2.000 > [12.470] (**) Synaptics TM3418-002: (accel) acceleration threshold: 4 > [12.471] (II) event9 - Synaptics TM3418-002: is tagged by udev as: > Touchpad > [12.472] (II) event9 - Synaptics TM3418-002: device is a touchpad
Re: [Bug 1895202] Re: touchpad suddenly not detected, appearing as PS/2 mouse in devices
The problem persists on 5.4.0-48 sadly, I still need to select advanced in grub, selecting 5.4.0-42 for the touchpad to work. *➜ ~ xinput --list* *5.4.0-42* ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [slave pointer (2)] ⎜ ↳ TPPS/2 Elan TrackPoint id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Sleep Button id=8 [slave keyboard (3)] ↳ Integrated Camera: Integrated C id=9 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)] ↳ ThinkPad Extra Buttons *5.4.0-48* ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Synaptics TM3418-002 id=12 [slave pointer (2)] ⎜ ↳ PS/2 Generic Mouse id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Sleep Button id=8 [slave keyboard (3)] ↳ Integrated Camera: Integrated C id=9 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)] ↳ ThinkPad Extra Buttons id=11 [slave keyboard (3)] *➜ ~ cat /var/log/Xorg.0.log | grep -i synaptics* *5.4.0-42* [16.093] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event5) [16.093] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "libinput touchpad catchall" [16.093] (II) Using input driver 'libinput' for 'SynPS/2 Synaptics TouchPad' [16.094] (**) SynPS/2 Synaptics TouchPad: always reports core events [16.095] (II) event5 - SynPS/2 Synaptics TouchPad: is tagged by udev as: Touchpad [16.095] (II) event5 - SynPS/2 Synaptics TouchPad: device is a touchpad [16.096] (II) event5 - SynPS/2 Synaptics TouchPad: device removed [16.096] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 11) [16.096] (**) SynPS/2 Synaptics TouchPad: (accel) selected scheme none/0 [16.096] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000 [16.096] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4 [16.097] (II) event5 - SynPS/2 Synaptics TouchPad: is tagged by udev as: Touchpad [16.098] (II) event5 - SynPS/2 Synaptics TouchPad: device is a touchpad [16.098] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0) [23.216] (II) event5 - SynPS/2 Synaptics TouchPad: device removed *5.4.0-48* [12.467] (II) config/udev: Adding input device Synaptics TM3418-002 (/dev/input/event9) [12.467] (**) Synaptics TM3418-002: Applying InputClass "libinput touchpad catchall" [12.467] (II) Using input driver 'libinput' for 'Synaptics TM3418-002' [12.468] (**) Synaptics TM3418-002: always reports core events [12.469] (II) event9 - Synaptics TM3418-002: is tagged by udev as: Touchpad [12.470] (II) event9 - Synaptics TM3418-002: device is a touchpad [12.470] (II) event9 - Synaptics TM3418-002: device removed [12.470] (II) XINPUT: Adding extended input device "Synaptics TM3418-002" (type: TOUCHPAD, id 12) [12.470] (**) Synaptics TM3418-002: (accel) selected scheme none/0 [12.470] (**) Synaptics TM3418-002: (accel) acceleration factor: 2.000 [12.470] (**) Synaptics TM3418-002: (accel) acceleration threshold: 4 [12.471] (II) event9 - Synaptics TM3418-002: is tagged by udev as: Touchpad [12.472] (II) event9 - Synaptics TM3418-002: device is a touchpad [12.472] (II) config/udev: Adding input device Synaptics TM3418-002 (/dev/input/mouse0) [33.395] (II) event9 - Synaptics TM3418-002: device removed ons. 23. sep. 2020, 20:15 skrev Russ McGill <1895...@bugs.launchpad.net>: > Kernel 5.4.0-48 fixes the problem. The TouchPad is recognized correctly > and touch pad, buttons, and track point work. Thank you. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1895202 > > Title: > touchpad suddenly not detected, appearing as PS/2 mouse in devices > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > I can't even recall making any upgrades. Lenovo X1 Extreme. > > ~ xinput --list > ⎡ Virtual
[Bug 1895202] [NEW] touchpad suddenly not detected, appearing as PS/2 mouse in devices
Public bug reported: I can't even recall making any upgrades. Lenovo X1 Extreme. ~ xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Synaptics TM3418-002 id=12 [slave pointer (2)] ⎜ ↳ PS/2 Generic Mouseid=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Button id=8[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=9[slave keyboard (3)] ↳ AT Raw Set 2 keyboard id=10 [slave keyboard (3)] ↳ ThinkPad Extra Buttonsid=11 [slave keyboard (3)] ➜ ~ cat /var/log/Xorg.0.log | grep -i synaptics [12.190] (II) config/udev: Adding input device Synaptics TM3418-002 (/dev/input/event7) [12.190] (**) Synaptics TM3418-002: Applying InputClass "libinput touchpad catchall" [12.190] (II) Using input driver 'libinput' for 'Synaptics TM3418-002' [12.190] (**) Synaptics TM3418-002: always reports core events [12.192] (II) event7 - Synaptics TM3418-002: is tagged by udev as: Touchpad [12.193] (II) event7 - Synaptics TM3418-002: device is a touchpad [12.194] (II) event7 - Synaptics TM3418-002: device removed [12.194] (II) XINPUT: Adding extended input device "Synaptics TM3418-002" (type: TOUCHPAD, id 12) [12.194] (**) Synaptics TM3418-002: (accel) selected scheme none/0 [12.194] (**) Synaptics TM3418-002: (accel) acceleration factor: 2.000 [12.194] (**) Synaptics TM3418-002: (accel) acceleration threshold: 4 [12.195] (II) event7 - Synaptics TM3418-002: is tagged by udev as: Touchpad [12.195] (II) event7 - Synaptics TM3418-002: device is a touchpad [12.196] (II) config/udev: Adding input device Synaptics TM3418-002 (/dev/input/mouse0) [34.235] (II) event7 - Synaptics TM3418-002: device removed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ole2093 F pulseaudio /dev/snd/controlC0: ole2093 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 10 21:45:53 2020 InstallationDate: Installed on 2019-03-30 (530 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20MFCTO1WW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=37b4f683-cd0d-4eb9-b05a-973790230aa4 ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET48W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW 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: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET48W(1.30):bd05/15/2020:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal ** Attachment added: "devices list as instructed" https://bugs.launchpad.net/bugs/1895202/+attachment/5409482/+files/devices -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895202 Title: touchpad suddenly not detected, appearing as PS/2 mouse in devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879153] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1879153/+attachment/5373728/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879153 Title: amdgpu prevents poweroff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879153] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1879153/+attachment/5373732/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879153 Title: amdgpu prevents poweroff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879153] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1879153/+attachment/5373727/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879153 Title: amdgpu prevents poweroff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879153] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1879153/+attachment/5373730/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879153 Title: amdgpu prevents poweroff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879153] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1879153/+attachment/5373726/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879153 Title: amdgpu prevents poweroff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879153] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1879153/+attachment/5373723/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879153 Title: amdgpu prevents poweroff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879153] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1879153/+attachment/5373722/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879153 Title: amdgpu prevents poweroff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879153] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1879153/+attachment/5373729/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879153 Title: amdgpu prevents poweroff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879153] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1879153/+attachment/5373725/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879153 Title: amdgpu prevents poweroff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879153] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1879153/+attachment/5373724/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879153 Title: amdgpu prevents poweroff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879153] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1879153/+attachment/5373731/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879153 Title: amdgpu prevents poweroff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879153] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1879153/+attachment/5373718/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879153 Title: amdgpu prevents poweroff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879153] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1879153/+attachment/5373720/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879153 Title: amdgpu prevents poweroff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879153] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1879153/+attachment/5373721/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879153 Title: amdgpu prevents poweroff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879153] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1879153/+attachment/5373719/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879153 Title: amdgpu prevents poweroff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879153] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1879153/+attachment/5373717/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879153 Title: amdgpu prevents poweroff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879153] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1879153/+attachment/5373715/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879153 Title: amdgpu prevents poweroff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879153] Re: amdgpu prevents poweroff
apport information ** Tags added: apport-collected ** Description changed: Turning off Kubuntu 20.04 stops short of actually powering off the machine. The monitors goes into suspend mode, but PC is still powered on and I have to hold the power button in to turn it off. I initially suspected an ACPI problem, but I found these two errors in /var/log/syslog after turning the computer on again: May 16 02:46:53 desktop kernel: [475329.688676] [ cut here ] May 16 02:46:53 desktop kernel: [475329.688765] WARNING: CPU: 4 PID: 1152 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_hwseq.c:1848 dcn20_setup_gsl_group_as_lock+0x80/0x200 [amdgpu] May 16 02:46:53 desktop kernel: [475329.688766] Modules linked in: uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev ccm xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc rfcomm aufs cmac algif_hash algif_skcipher overlay af_alg bnep snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_hda_codec_realtek snd_pcm_dmaengine nls_iso8859_1 snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel intel_rapl_msr snd_usb_audio snd_intel_dspcfg snd_hda_codec snd_usbmidi_lib snd_hda_core mc mei_hdcp snd_hwdep snd_pcm intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi snd_seq_midi_event kvm iwlmvm May 16 02:46:53 desktop kernel: [475329.688783] mac80211 intel_cstate libarc4 snd_rawmidi intel_rapl_perf wmi_bmof snd_seq intel_wmi_thunderbolt btusb snd_seq_device btrtl iwlwifi snd_timer btbcm btintel snd bluetooth joydev input_leds mei_me ecdh_generic soundcore ecc intel_pch_thermal ie31200_edac cfg80211 mei acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel amdgpu amd_iommu_v2 aesni_intel crypto_simd gpu_sched i2c_algo_bit ttm drm_kms_helper cryptd glue_helper syscopyarea sysfillrect sysimgblt nvme fb_sys_fops i2c_i801 drm e1000e ahci nvme_core libahci wmi video pinctrl_cannonlake pinctrl_intel May 16 02:46:53 desktop kernel: [475329.688801] CPU: 4 PID: 1152 Comm: Xorg Tainted: GW 5.4.0-29-generic #33-Ubuntu May 16 02:46:53 desktop kernel: [475329.688801] Hardware name: Gigabyte Technology Co., Ltd. Z390 I AORUS PRO WIFI/Z390 I AORUS PRO WIFI-CF, BIOS F5 03/14/2019 May 16 02:46:53 desktop kernel: [475329.688879] RIP: 0010:dcn20_setup_gsl_group_as_lock+0x80/0x200 [amdgpu] May 16 02:46:53 desktop kernel: [475329.61] Code: 84 d2 74 48 84 c0 75 26 48 8b 87 10 03 00 00 0f b6 80 70 02 00 00 a8 01 0f 84 dc 00 00 00 a8 02 74 56 a8 04 0f 84 f7 00 00 00 <0f> 0b 0f 0b 48 8b 45 e0 65 48 33 04 25 28 00 00 00 0f 85 56 01 00 May 16 02:46:53 desktop kernel: [475329.62] RSP: 0018:bd3c81567558 EFLAGS: 00010202 May 16 02:46:53 desktop kernel: [475329.63] RAX: 0007 RBX: 978c9de001b8 RCX: May 16 02:46:53 desktop kernel: [475329.63] RDX: 0001 RSI: 978c9de001b8 RDI: 9791c8d5 May 16 02:46:53 desktop kernel: [475329.64] RBP: bd3c815675a0 R08: bd3c81567554 R09: May 16 02:46:53 desktop kernel: [475329.64] R10: 9791c876 R11: R12: 0001 May 16 02:46:53 desktop kernel: [475329.65] R13: 0001 R14: 9791c8d5 R15: 978c9de001b8 May 16 02:46:53 desktop kernel: [475329.66] FS: 7fe19eb9ca80() GS:9791ddb0() knlGS: May 16 02:46:53 desktop kernel: [475329.67] CS: 0010 DS: ES: CR0: 80050033 May 16 02:46:53 desktop kernel: [475329.67] CR2: 563d34cbeff0 CR3: 00088a80c006 CR4: 003606e0 May 16 02:46:53 desktop kernel: [475329.68] Call Trace: May 16 02:46:53 desktop kernel: [475329.688959] dcn20_pipe_control_lock.part.0+0x112/0x1f0 [amdgpu] May 16 02:46:53 desktop kernel: [475329.689026] dcn20_pipe_control_lock+0x1c/0x20 [amdgpu] May 16 02:46:53 desktop kernel: [475329.689087] dc_stream_set_cursor_position+0x128/0x160 [amdgpu] May 16 02:46:53 desktop kernel: [475329.689152] handle_cursor_update.isra.0+0x226/0x300 [amdgpu] May 16 02:46:53 desktop kernel: [475329.689217] amdgpu_dm_commit_cursors.isra.0+0x60/0x80 [amdgpu] May 16 02:46:53 desktop kernel: [475329.689281] amdgpu_dm_commit_planes.constprop.0+0x66d/0xa00 [amdgpu] May 16 02:46:53 desktop kernel: [475329.689283] ? __kmalloc_node+0x259/0x320 May 16 02:46:53 desktop kernel: [475329.689347] ?
[Bug 1879153] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1879153/+attachment/5373716/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879153 Title: amdgpu prevents poweroff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879153] [NEW] amdgpu prevents poweroff
Public bug reported: Turning off Kubuntu 20.04 stops short of actually powering off the machine. The monitors goes into suspend mode, but PC is still powered on and I have to hold the power button in to turn it off. I initially suspected an ACPI problem, but I found these two errors in /var/log/syslog after turning the computer on again: May 16 02:46:53 desktop kernel: [475329.688676] [ cut here ] May 16 02:46:53 desktop kernel: [475329.688765] WARNING: CPU: 4 PID: 1152 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_hwseq.c:1848 dcn20_setup_gsl_group_as_lock+0x80/0x200 [amdgpu] May 16 02:46:53 desktop kernel: [475329.688766] Modules linked in: uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev ccm xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc rfcomm aufs cmac algif_hash algif_skcipher overlay af_alg bnep snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_hda_codec_realtek snd_pcm_dmaengine nls_iso8859_1 snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel intel_rapl_msr snd_usb_audio snd_intel_dspcfg snd_hda_codec snd_usbmidi_lib snd_hda_core mc mei_hdcp snd_hwdep snd_pcm intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_seq_midi snd_seq_midi_event kvm iwlmvm May 16 02:46:53 desktop kernel: [475329.688783] mac80211 intel_cstate libarc4 snd_rawmidi intel_rapl_perf wmi_bmof snd_seq intel_wmi_thunderbolt btusb snd_seq_device btrtl iwlwifi snd_timer btbcm btintel snd bluetooth joydev input_leds mei_me ecdh_generic soundcore ecc intel_pch_thermal ie31200_edac cfg80211 mei acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel amdgpu amd_iommu_v2 aesni_intel crypto_simd gpu_sched i2c_algo_bit ttm drm_kms_helper cryptd glue_helper syscopyarea sysfillrect sysimgblt nvme fb_sys_fops i2c_i801 drm e1000e ahci nvme_core libahci wmi video pinctrl_cannonlake pinctrl_intel May 16 02:46:53 desktop kernel: [475329.688801] CPU: 4 PID: 1152 Comm: Xorg Tainted: GW 5.4.0-29-generic #33-Ubuntu May 16 02:46:53 desktop kernel: [475329.688801] Hardware name: Gigabyte Technology Co., Ltd. Z390 I AORUS PRO WIFI/Z390 I AORUS PRO WIFI-CF, BIOS F5 03/14/2019 May 16 02:46:53 desktop kernel: [475329.688879] RIP: 0010:dcn20_setup_gsl_group_as_lock+0x80/0x200 [amdgpu] May 16 02:46:53 desktop kernel: [475329.61] Code: 84 d2 74 48 84 c0 75 26 48 8b 87 10 03 00 00 0f b6 80 70 02 00 00 a8 01 0f 84 dc 00 00 00 a8 02 74 56 a8 04 0f 84 f7 00 00 00 <0f> 0b 0f 0b 48 8b 45 e0 65 48 33 04 25 28 00 00 00 0f 85 56 01 00 May 16 02:46:53 desktop kernel: [475329.62] RSP: 0018:bd3c81567558 EFLAGS: 00010202 May 16 02:46:53 desktop kernel: [475329.63] RAX: 0007 RBX: 978c9de001b8 RCX: May 16 02:46:53 desktop kernel: [475329.63] RDX: 0001 RSI: 978c9de001b8 RDI: 9791c8d5 May 16 02:46:53 desktop kernel: [475329.64] RBP: bd3c815675a0 R08: bd3c81567554 R09: May 16 02:46:53 desktop kernel: [475329.64] R10: 9791c876 R11: R12: 0001 May 16 02:46:53 desktop kernel: [475329.65] R13: 0001 R14: 9791c8d5 R15: 978c9de001b8 May 16 02:46:53 desktop kernel: [475329.66] FS: 7fe19eb9ca80() GS:9791ddb0() knlGS: May 16 02:46:53 desktop kernel: [475329.67] CS: 0010 DS: ES: CR0: 80050033 May 16 02:46:53 desktop kernel: [475329.67] CR2: 563d34cbeff0 CR3: 00088a80c006 CR4: 003606e0 May 16 02:46:53 desktop kernel: [475329.68] Call Trace: May 16 02:46:53 desktop kernel: [475329.688959] dcn20_pipe_control_lock.part.0+0x112/0x1f0 [amdgpu] May 16 02:46:53 desktop kernel: [475329.689026] dcn20_pipe_control_lock+0x1c/0x20 [amdgpu] May 16 02:46:53 desktop kernel: [475329.689087] dc_stream_set_cursor_position+0x128/0x160 [amdgpu] May 16 02:46:53 desktop kernel: [475329.689152] handle_cursor_update.isra.0+0x226/0x300 [amdgpu] May 16 02:46:53 desktop kernel: [475329.689217] amdgpu_dm_commit_cursors.isra.0+0x60/0x80 [amdgpu] May 16 02:46:53 desktop kernel: [475329.689281] amdgpu_dm_commit_planes.constprop.0+0x66d/0xa00 [amdgpu] May 16 02:46:53 desktop kernel: [475329.689283] ? __kmalloc_node+0x259/0x320 May 16 02:46:53 desktop kernel: [475329.689347] ? dc_resource_state_copy_construct+0x11a/0x150 [amdgpu] May 16 02:46:53 desktop kernel: [475329.689414]
[Bug 1866611] Re: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6
This seems to have been caused by the patch 0180-Stop-accepting- certificates-signed-using-SHA1-at-sec.patch. I've re-built 1.1.1c-1ubuntu4 (apt source openssl; cd openssl1.1.1c; dpkg-buildpackage --no-sign; sudo apt install ../libssl1.1_1.1.1c- 1ubuntu4_amd64.deb), which makes my VPN work again. I've tried putting different things into /etc/ssl/openssl.conf, but `CipherString = DEFAULT:@SECLEVEL=0` (or any variation I can think of) makes it work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866611 Title: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1866611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866611] [NEW] OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6
Public bug reported: After upgrading openssl on my Focal-install this morning (upgrade openssl:amd64 1.1.1d-2ubuntu3 1.1.1d-2ubuntu6 per /var/log/dpkg.log), my OpenVPN tunnel refuses to connect to our corporate VPN (from /var/log/syslog): corp-laptop nm-openvpn[4688]: VERIFY ERROR: depth=0, error=CA signature digest algorithm too weak: C=DK, ST=None, L=Copenhagen, O=XX, OU=XX, CN=XX, emailAddress=XX corp-laptop nm-openvpn[4688]: OpenSSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed I'm told we're running a SHA1-signed CA, which we're guessing has been deprecated somewhere between -2ubuntu3 and -2ubuntu6. The changelog for -2ubuntu4 mentions importing some upstream changes, but isn't more specific than that: https://changelogs.ubuntu.com/changelogs/pool/main/o/openssl/openssl_1.1 .1d-2ubuntu4/changelog As a work-around, the internet suggests two work-arounds (neither of which has worked for me): 1) Adding the following to /etc/defaults/openssl: OPTARGS="--tls-cipher DEFAULT:@SECLEVEL=0" 2) Adding the following to /etc/ssl/openssl.conf: CipherString= :@SECLEVEL=1 I also tried rolling back the package, but the old version doesn't seem to be available: $ sudo apt install openssl=1.1.1d-2ubuntu3 ... E: Version '1.1.1d-2ubuntu3' for 'openssl' was not found I am no SSL-expert and would appreciate any pointers to get around this. (Our network-dept. does not have the bandwidth to roll over our CA on short notice, so I will need some other way to move ahead). ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: openvpn sha1 ** Tags added: openvpn ** Tags added: sha1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866611 Title: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1866611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800719] Re: missing conf files noted on apt upgrade after distribution upgrade
Upgraded from 16.04.5 to 18.04.3 and have noticed the same symptom -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800719 Title: missing conf files noted on apt upgrade after distribution upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1800719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G
Done, please reference https://bugs.freedesktop.org/show_bug.cgi?id=112288 ** Bug watch added: freedesktop.org Bugzilla #112288 https://bugs.freedesktop.org/show_bug.cgi?id=112288 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848900 Title: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G
My machine is mainly running as file server at the moment and I don't want to play around with kernels. I used to build kernels in the past and I remember how hard it is to get one that works. I'll wait till there's a fix in the main-line kernel. They can't release LTS 20.04 with this bug so it must come soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848900 Title: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G
Re: "unsigned" I figured it out, however, my boot partition is UEFI, so I probably can't use an unsigned image. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848900 Title: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G
@kaihengfegn I guess I need this one: linux-image- unsigned-5.4.0-050400rc7-generic_5.4.0-050400rc7.201911102031_amd64.deb as well as the corresponding headers and modules. but what does "unsigned" mean? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848900 Title: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624541] Re: blank screen with amdgpu on [AMD/ATI] Topaz XT [Radeon R7 M260/M265]
Possible duplicate of Bug #1848900 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624541 Title: blank screen with amdgpu on [AMD/ATI] Topaz XT [Radeon R7 M260/M265] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1624541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G
I experience the same on a Ryzen 5 2400G APU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848900 Title: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833512] [NEW] Wifi password dialog popup don't take more the 20 ASCII-encoded characters
Public bug reported: The max pass-phrase length for a WPA2-PSK, has a limit of 63 ASCII- encoded characters The password fields, in the dialog to write the pass-phrase for the Wifi network you are connecting to, is limiting this to 20 characters. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 09:59:57 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-06-19 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.1.1 dev enp0s25 proto dhcp metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.169 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s25 ethernet connected full limited /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 cb8f8bbb-c98f-3fcd-8212-fdf5d6425ab1 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0 wifi disconnected limited limited /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Description changed: The max pass-phrase length for a WPA2-PSK, has a limit of 63 ASCII- encoded characters The password fields, in the dialog to write the pass-phrase for the Wifi - network you are connecting to is limiting this to 20 characters. + network you are connecting to, is limiting this to 20 characters. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 09:59:57 2019 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2019-06-19 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: - default via 192.168.1.1 dev enp0s25 proto dhcp metric 100 - 169.254.0.0/16 dev enp0s25 scope link metric 1000 - 192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.169 metric 100 + default via 192.168.1.1 dev enp0s25 proto dhcp metric 100 + 169.254.0.0/16 dev enp0s25 scope link metric 1000 + 192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.169 metric 100 NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: - DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH - enp0s25 ethernet connected full limited /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 cb8f8bbb-c98f-3fcd-8212-fdf5d6425ab1 /org/freedesktop/NetworkManager/ActiveConnection/1 - wlp3s0 wifi disconnected limited limited /org/freedesktop/NetworkManager/Devices/3 -- -- -- - lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- + DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH
[Bug 1781699] Re: DHCPv6 server crashes regularly (bionic)
I have tested the -server package on Bionic and I haven't had any crashes yet. Typically in my environment it would have crashed after one hour or two hours the latest. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781699 Title: DHCPv6 server crashes regularly (bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1781699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736222] Re: speech-dispatcher distorts all sound
I was wrong, speech-dispatcher is just not installed on TW by default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736222 Title: speech-dispatcher distorts all sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736222] Re: speech-dispatcher distorts all sound
It may be that it's fixed in most recent version. I am atm using OpenSUSE Tumbleweed and it's the first time since 3-4 years that i do not get this error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736222 Title: speech-dispatcher distorts all sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756226] Re: nvidia-driver-390 fails to start GUI
...:~$ apt-cache policy nvidia-390 nvidia-390: Installeret: 390.87-0ubuntu0~gpu18.04.2 Kandidat:390.87-0ubuntu0~gpu18.04.2 .:~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installeret: 1:0.5.2.3 Kandidat:1:0.5.2.3 I seem be having this issue ? how can i verify? if i nvidia active i get black screen with a cursor indicated in top left, and i hear the ubunti logon sound. and then nothing. i have to do: sudo prime-select intel to get back in to GUI please help -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756226 Title: nvidia-driver-390 fails to start GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1756226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 277281] Re: pptp does not start automatically in Intrepid
This bug is still Undecided in the pptp-linux project, however, the comment above says the bug will not be fixed but another applet is available in KDE4 for Kubuntu 9.10. Please set to "Won't Fix" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/277281 Title: pptp does not start automatically in Intrepid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/knetworkmanager/+bug/277281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820048] Re: Samba share not automounted
Please add information on what Ubuntu distribution you experienced this problem, and what "resolve package" and version that solved it. Thanks! ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820048 Title: Samba share not automounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1820048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821439] Re: speech-dispatcher produces sound errors in Firefox
I am sorry, i found an earlier bugreport. So feel free to close this bug as duplicate. Original Bugreport: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821439 Title: speech-dispatcher produces sound errors in Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1821439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736222] Re: speech-dispatcher distorts all sound
This affects Ubuntu 18.10 as well. Gets triggered every time while a YT video is playing and i open a website in firefox in special reading view. Overkill in KDE because the sound error starts when checking mails in kmail or refreshing akkregator. Removing speech-dispatcher "solves" the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736222 Title: speech-dispatcher distorts all sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821439] Re: speech-dispatcher produces sound errors in Firefox
** Summary changed: - speech-dispatcher triggers sound errors in Firefox while playing media and using + speech-dispatcher produces sound errors in Firefox -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821439 Title: speech-dispatcher produces sound errors in Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1821439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821237] Re: Monitors cycle on and off repeatedly when session is locked
It seems that there is a difference in behaviour between Xorg and Wayland session. Xorg produces the on/off display cycling, but under Wayland the lock screen works exactly as expected. ** Description changed: System: Ubuntu Desktop 18.10 with GNOME. Fresh installation. - - Package: Unknown + Package: ubuntu-session/cosmic,cosmic,now 3.30.0-0ubuntu4 all Expected behaviour: Locking the session via Superkey+L turns connected monitors off after short period of time and puts them into sleep mode. What happens: Session gets locked, but Ubuntu seems to be unable to keep both of my monitors in sleepmode. Both monitors are blackened shortly after locking the session, displaying sort of "no signal, going to sleep", but are getting turned on a few seconds later to show the Gnome lock screen. Then they are turned off and repeating "no signal, going to sleep". This cycle repeats untill the session gets unlocked or the PC goes fully to sleep. Disabling extensions and removing all USB devices didn't change this behaviour. Previously used KDE which handled lock screens as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821237 Title: Monitors cycle on and off repeatedly when session is locked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1821237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821439] [NEW] speech-dispatcher triggers sound errors in Firefox while playing media and using
Public bug reported: Ubuntu Gnome 18.10 Expected behaviour: Play media content in different tab in Firefox while viewing a page in Firefox' readingview (that option given in the URL-bar for a text version of a site) What happens: As soon as i open the website in Firefox special readingview, all sounds from the media tab starts to make crackling sounds. Workaround: Close Firefox and don't use reading view. Second workaround: Removing packet "speech-dispatcher" completly remove this issue. This issue is extra annoying in Kubuntu as it starts as soon as i open one of the PIM applications, i.e. kmail or akkregator. Seems to be cross-distribution as i experienced it on OpenSUSE Leap 15 / Tumbleweed KDE and could be resolved by removing speech-dispatcher packet. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: speech-dispatcher (not installed) ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 23 09:09:17 2019 InstallationDate: Installed on 2019-03-17 (5 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: speech-dispatcher UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: speech-dispatcher (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821439 Title: speech-dispatcher triggers sound errors in Firefox while playing media and using To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1821439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821237] [NEW] Monitors cycle on and off repeatedly when session is locked
Public bug reported: System: Ubuntu Desktop 18.10 with GNOME. Fresh installation. Package: Unknown Expected behaviour: Locking the session via Superkey+L turns connected monitors off after short period of time and puts them into sleep mode. What happens: Session gets locked, but Ubuntu seems to be unable to keep both of my monitors in sleepmode. Both monitors are blackened shortly after locking the session, displaying sort of "no signal, going to sleep", but are getting turned on a few seconds later to show the Gnome lock screen. Then they are turned off and repeating "no signal, going to sleep". This cycle repeats untill the session gets unlocked or the PC goes fully to sleep. Disabling extensions and removing all USB devices didn't change this behaviour. Previously used KDE which handled lock screens as expected. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821237 Title: Monitors cycle on and off repeatedly when session is locked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1821237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1753518] Re: package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
Experiencing this on 18.04 as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753518 Title: package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1753518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777049] [NEW] gnome-twitch crashes when starting a stream
Public bug reported:
Gnome-twitch doesn't work on Ubuntu 18.04 as it always crashes when
starting a stream. The player backend has no influence over the
behaviour.
Example terminal output (personal informations edited out):
[04:43:04] Message - GNOME-Twitch : {GtApp:370} Startup, running version '0.4.1'
[04:43:04] Message - GNOME-Twitch : {GtApp:339} Activate
[04:43:04] Message - GNOME-Twitch : {GtPlayer:132} Loading chat settings
[04:43:04] Message - GNOME-Twitch : {GtPlayer:999} Loaded player backend 'MPV
OpenGL player backend'
[04:43:04] Message - GNOME-Twitch : {GtPlayerBackendMpvOpenGL:401} Init
[04:43:04] Message - GNOME-Twitch : {GtApp:147} Succesfully fetched oauth info
with name 'xx', id 'xxx' and oauth token 'x'
[04:43:05] Message - GNOME-Twitch : {GtApp:182} Succesfully fetched user info
with name 'xxx', id '' and oauth token 'x'
[04:43:05] Message - GNOME-Twitch : {GtFollowsManager:519} Loaded '21' follows
from Twitch
[04:43:06] Message - GNOME-Twitch : {GtPlayer:1310} Opening stream 'ninja' with
quality 'source'
[04:43:06] Warning - GNOME-Twitch : {GtTwitch:336} Received unsuccessful
response from url 'http://api.twitch.tv/api/channels/ninja/access_token' with
code '400' and body '{"error":"Bad Request","status":400,"message":"Requests
must be made over SSL"}'
[04:43:06] Warning - GNOME-Twitch : {GtTwitch:594} Error getting stream access
token for channel 'ninja' because: Received unsuccessful response from url
'http://api.twitch.tv/api/channels/ninja/access_token' with code '400' and body
'{"error":"Bad Request","status":400,"message":"Requests must be made over
SSL"}'
Speicherzugriffsfehler (Speicherabzug geschrieben)
[German for Memory access error]
** Affects: gnome-twitch (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Gnome-twitch doesn't work on Ubuntu 18.04 as it always crashes when
- starting a stream.
+ starting a stream. The player backend has no influence over the
+ behaviour.
Example terminal output (personal informations edited out):
[04:43:04] Message - GNOME-Twitch : {GtApp:370} Startup, running version
'0.4.1'
[04:43:04] Message - GNOME-Twitch : {GtApp:339} Activate
[04:43:04] Message - GNOME-Twitch : {GtPlayer:132} Loading chat settings
[04:43:04] Message - GNOME-Twitch : {GtPlayer:999} Loaded player backend 'MPV
OpenGL player backend'
[04:43:04] Message - GNOME-Twitch : {GtPlayerBackendMpvOpenGL:401} Init
[04:43:04] Message - GNOME-Twitch : {GtApp:147} Succesfully fetched oauth
info with name 'xx', id 'xxx' and oauth token 'x'
[04:43:05] Message - GNOME-Twitch : {GtApp:182} Succesfully fetched user info
with name 'xxx', id '' and oauth token 'x'
[04:43:05] Message - GNOME-Twitch : {GtFollowsManager:519} Loaded '21'
follows from Twitch
[04:43:06] Message - GNOME-Twitch : {GtPlayer:1310} Opening stream 'ninja'
with quality 'source'
[04:43:06] Warning - GNOME-Twitch : {GtTwitch:336} Received unsuccessful
response from url 'http://api.twitch.tv/api/channels/ninja/access_token' with
code '400' and body '{"error":"Bad Request","status":400,"message":"Requests
must be made over SSL"}'
[04:43:06] Warning - GNOME-Twitch : {GtTwitch:594} Error getting stream
access token for channel 'ninja' because: Received unsuccessful response from
url 'http://api.twitch.tv/api/channels/ninja/access_token' with code '400' and
body '{"error":"Bad Request","status":400,"message":"Requests must be made over
SSL"}'
Speicherzugriffsfehler (Speicherabzug geschrieben)
[German for Memory access error]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777049
Title:
gnome-twitch crashes when starting a stream
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-twitch/+bug/1777049/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772654] [NEW] Ubuntu 14.04 (or something) crashed on installation from USB stick
Public bug reported: Not much to add ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.18.8.12 ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CasperVersion: 1.340.2 Date: Tue May 22 14:50:29 2018 InstallCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubiquity-2.18.8.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772654 Title: Ubuntu 14.04 (or something) crashed on installation from USB stick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1772654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72
I'm also having this exact same issue with the same specs as Никита. 2012 R2, Hyper-v, Gen1. VM: Ubuntu Server 16.04.03LTS, kernel - 4.4.0-112-generic, 2 disks. linux-cloud-tools-virtual-lts-xenial 4.4.0.112.118 linux-tools-virtual-lts-xenial 4.4.0.112.118 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679898 Title: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1679898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692365] [NEW] package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
Public bug reported: I had installed gnome classic and also (to test it) the Mate desktop. I like Gnome classic best so I uninstalled the Mate desktop. And now this avari package is missing. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun May 21 23:32:35 2017 DuplicateSignature: package:avahi-dnsconfd:0.6.32~rc+dfsg-1ubuntu2 Removing avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2) ... Job for avahi-daemon.socket canceled. dpkg: error processing package avahi-dnsconfd (--remove): subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-05-20 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: avahi Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: avahi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692365 Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1692365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658345] Re: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10
I'm also having this problem. Touchpad mostly works in the Basic setting in BIOS/UEFI, but when I'm on Advanced, the touchpad doesn't even show up in xinput. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1658345 Title: Touchpad not recognized on Lenovo Ideapad Flex 4 running Ubuntu 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1596325] Re: Add Roboto Slab to fonts-roboto
And Roboto Mono as well perhaps? https://fonts.google.com/specimen/Roboto+Mono -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1596325 Title: Add Roboto Slab to fonts-roboto To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-roboto/+bug/1596325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1678264] Re: Xubuntu crashed on installation. Couldn't install bootloder, fatal error.
I got it working by formatting the USB stick as a DD image instead of an ISO image and then reinstalling the newly created linux partition. Thanks for the help though, it will come in handy if I ever have to reinstall the system! 2017-04-01 12:17 GMT+02:00 apt-ghetto <1678...@bugs.launchpad.net>: > You try to install Xubuntu in BIOS mode and choose as target for Grub a > disk with GPT as partition table. > > You have also an EFI-System-Partition on this disk, so it is probable, > that you have a Windows installed in EFI mode. To get a dualboot you > have to start the installer also in EFI mode. > > If you like to install Xubuntu in BIOS mode, either you create a > "bios_grub"-partition or you choose another disk with MBR/MSDOS as > partition table as target for Grub. > > ** Changed in: grub-installer (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1678264 > > Title: > Xubuntu crashed on installation. Couldn't install bootloder, fatal > error. > > Status in grub-installer package in Ubuntu: > Incomplete > > Bug description: > Description: Ubuntu 16.04.2 LTS > Release: 16.04 > > Expected Xubuntu to install, it didn't. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: ubiquity 2.21.63.3 [modified: lib/partman/automatically_ > partition/question] > ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 > Uname: Linux 4.8.0-36-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.5 > Architecture: amd64 > CasperVersion: 1.376.2 > Date: Fri Mar 31 19:31:44 2017 > InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper > only-ubiquity initrd=/casper/initrd.lz quiet splash --- nomodeset > LiveMediaBuild: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 > (20170215) > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 > SourcePackage: grub-installer > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub-installer/ > +bug/1678264/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678264 Title: Xubuntu crashed on installation. Couldn't install bootloder, fatal error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1678264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678264] [NEW] Xubuntu crashed on installation. Couldn't install bootloder, fatal error.
Public bug reported: Description:Ubuntu 16.04.2 LTS Release:16.04 Expected Xubuntu to install, it didn't. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.3 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CasperVersion: 1.376.2 Date: Fri Mar 31 19:31:44 2017 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash --- nomodeset LiveMediaBuild: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.3 xenial xubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678264 Title: Xubuntu crashed on installation. Couldn't install bootloder, fatal error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1678264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643169] [NEW] package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Setting up click (0.4.45.1+16.10.20160916-0ubuntu1) ... Cannot start click due to a conflict with a different locally-installed Python 'click' package. Remove it using Python packaging tools and try again. dpkg: error processing package click (--configure): subprocess installed post-installation script returned error exit status 1 Setting up click-apparmor (0.3.17) ... Cannot start click due to a conflict with a different locally-installed Python 'click' package. Remove it using Python packaging tools and try again. dpkg: error processing package click-apparmor (--configure): subprocess installed post-installation script returned error exit status 1 Setting up url-dispatcher:amd64 (0.1+16.10.20160816.1-0ubuntu1) ... Cannot start click due to a conflict with a different locally-installed Python 'click' package. Remove it using Python packaging tools and try again. dpkg: error processing package url-dispatcher:amd64 (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of ubuntu-app-launch: ubuntu-app-launch depends on click-apparmor; however: Package click-apparmor is not configured yet. dpkg: error processing package ubuntu-app-launch (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of ubuntu-system-settings: ubuntu-system-settings depends on click | ubuntu-snappy-cli; however: Package click is not configured yet. Package ubuntu-snappy-cli is not installed. dpkg: error processing package ubuntu-system-settings (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of url-dispatcher-tools: url-dispatcher-tools depends on url-dispatcher (= 0.1+16.10.20160816.1-0ubuntu1); however: Package url-dispatcher:amd64 is not configured yet. dpkg: error processing package url-dispatcher-tools (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configurationNo apport report written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already of ubuntu-app-launch-tools: ubuntu-app-launch-tools depends on ubuntu-app-launch (= 0.9+16.10.20160928-0ubuntu1); however: Package ubuntu-app-launch is not configured yet. dpkg: error processing package ubuntu-app-launch-tools (--configure): dependency problems - leaving unconfigured Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ... Cannot start click due to a conflict with a different locally-installed Python 'click' package. Remove it using Python packaging tools and try again. dpkg: error processing package libunity-scopes1.0:amd64 (--configure): subprocess installed post-installation script returned error exit status 1 No apport report written because MaxReports is reached already dpkg: dependency problems prevent configuration of ubuntu-system-settings-online-accounts: ubuntu-system-settings-online-accounts depends on ubuntu-system-settings; however: Package ubuntu-system-settings is not configured yet. dpkg: error processing package ubuntu-system-settings-online-accounts (--configure): dependency problems - leaving unconfigured No apport report written because MaxReports is reached already dpkg: dependency problems prevent configuration of unity8: unity8 depends on ubuntu-system-settings (>= 0.4); however: Package ubuntu-system-settings is not configured yet. dpkg: error processing package unity8 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of account-plugin-ubuntuone: account-plugin-ubuntuone depends on ubuntu-system-settings-online-accounts; however: Package ubuntu-system-settings-online-accounts is not configured yet. dpkg: error processing package account-plugin-ubuntuone (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of unity-plugin-scopes:amd64: unity-plugin-scopes:amd64 depends on libunity-scopes1.0; however: Package libunity-scopes1.0:amd64 is not configured yet. No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already dpkg:
[Bug 1632363] Re: snapd fail on boot
`journalctl -u snapd.service` -- Logs begin at Thu 2016-10-27 13:49:19 UTC, end at Thu 2016-10-27 14:00:54 UTC. -- Oct 27 14:00:45 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:47 localhost.localdomain snapd[1823]: error: internal error: could not unmarshal state entr Oct 27 14:00:47 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, statu Oct 27 14:00:47 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:47 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:48 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:48 localhost.localdomain snapd[1833]: error: internal error: could not unmarshal state entr Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, statu Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:48 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:48 localhost.localdomain snapd[1840]: error: internal error: could not unmarshal state entr Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, statu Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:49 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:49 localhost.localdomain snapd[1848]: error: internal error: could not unmarshal state entr Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, statu Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:49 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:50 localhost.localdomain snapd[1855]: error: internal error: could not unmarshal state entr Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, statu Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Start request repeated too quickly. Oct 27 14:00:50 localhost.localdomain systemd[1]: Failed to start Snappy daemon. `journalctl -u snapd.boot-ok.service` -- Logs begin at Thu 2016-10-27 13:49:19 UTC, end at Thu 2016-10-27 14:00:54 UTC. -- Oct 27 14:00:53 localhost.localdomain systemd[1]: Starting Notify bootloader that boot was successful... Oct 27 14:00:54 localhost.localdomain snap[1874]: error: can not SyncBoot, failed to make ubuntu-core active: snap not active Oct 27 14:00:54 localhost.localdomain systemd[1]: snapd.boot-ok.service: Main process exited, code=exited, status=1/FAILURE Oct 27 14:00:54 localhost.localdomain systemd[1]: Failed to start Notify bootloader that boot was successful. Oct 27 14:00:54 localhost.localdomain systemd[1]: snapd.boot-ok.service: Unit entered failed state. Oct 27 14:00:54 localhost.localdomain systemd[1]: snapd.boot-ok.service: Failed with result 'exit-code'. `journalctl -u snapd.socket` -- Logs begin at Thu 2016-10-27 13:49:19 UTC, end at Thu 2016-10-27 14:00:54 UTC. -- Oct 27 13:49:40 localhost.localdomain systemd[1]: Starting Socket activation for snappy daemon. Oct 27 13:49:40 localhost.localdomain systemd[1]: Listening on Socket activation for snappy daemon. Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.socket: Unit entered failed state. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632363 Title: snapd fail on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1632363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632363] Re: snapd fail on boot
-- Logs begin at Thu 2016-10-27 13:49:19 UTC, end at Thu 2016-10-27 14:13:13 UTC. -- Oct 27 14:00:45 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:47 localhost.localdomain snapd[1823]: error: internal error: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int Oct 27 14:00:47 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE Oct 27 14:00:47 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:47 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:48 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:48 localhost.localdomain snapd[1833]: error: internal error: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:48 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:48 localhost.localdomain snapd[1840]: error: internal error: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE Oct 27 14:00:48 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:49 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:49 localhost.localdomain snapd[1848]: error: internal error: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:49 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:49 localhost.localdomain systemd[1]: Started Snappy daemon. Oct 27 14:00:50 localhost.localdomain snapd[1855]: error: internal error: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Unit entered failed state. Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Failed with result 'exit-code'. Oct 27 14:00:50 localhost.localdomain systemd[1]: snapd.service: Start request repeated too quickly. Oct 27 14:00:50 localhost.localdomain systemd[1]: Failed to start Snappy daemon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632363 Title: snapd fail on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1632363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604606] Re: snapd fails to start due to: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int
*** This bug is a duplicate of bug 1632363 *** https://bugs.launchpad.net/bugs/1632363 ** This bug has been marked a duplicate of bug 1632363 snapd fail on boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1604606 Title: snapd fails to start due to: could not unmarshal state entry "snaps": json: cannot unmarshal string into Go value of type int To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1604606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632363] Re: snapd fail on boot
The image was working fine, and although the sheer amount of experimentation and reinstalls makes my memory foggy, I do believe this particular install had gone through a ubuntu-core update without any issues. What caused the issue in the first place is a real networking issue. I had placed the install within a DMZ that was wrongly configured, so the clients of the subnet was unable to get a lease on an IP-address. It was left on this subnet for quite some time and over several boots. It now has internet access again, but the snap daemon fails continuously. For what reason I'm unsure. I've seen different reports of snap daemon failing because it starts before networking in the boot process, maybe I'm suffering the same problem. This bug then, would have surfaced due to a longer period of no network access for unknown reasons. @Michael I'm unfamiliar with journalctl and have yet to manage to get any form of relevant info from a query. Maybe you could help me with some suggestions as to what to search for in the journal? @Oliver The image is from https://people.canonical.com/~mvo/all-snaps/obsolete/, it was downloaded on the 19th of September. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632363 Title: snapd fail on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1632363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632363] [NEW] snapd fail on boot
Public bug reported: `lsb_release -rd` Description:Ubuntu 16.04 LTS Release:16.04 Running the BBB version of snappy ubuntu core. unable to attain package version. any snap command is met by "error: cannot list snaps: cannot communicate with server: Get http://localhost/v2/snaps?sources=local: dial unix /run/snapd.socket: connect: connection refused" with a few variation in the URL `systemctl list-units` shows that snapd.boot-ok.service snapd. service snapd.socket has failed to load. ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: ubuntu-core -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632363 Title: snapd fail on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1632363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592696] Re: snaps don't work with encrypted home: failed to create user data directory. errmsg: Permission denied
I also ran into this problem trying out the htop snap. After removing the snap I installed htop via apt, but it still failed with the same message: $ htop failed to create user data directory. errmsg: Permission denied $ which htop /usr/bin/htop Enabling xenial-proposed and running apt upgrade fixed the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592696 Title: snaps don't work with encrypted home: failed to create user data directory. errmsg: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1592696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575655] Re: the network indicator shows the wrong status
Can confirm that that workaround works for me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575655 Title: the network indicator shows the wrong status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1575655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580786] [NEW] abnormal CPU-usage
Public bug reported: Logged into my computer and Xorg was using 100% -140% of CPU ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 23:16:08 2016 InstallationDate: Installed on 2016-04-08 (33 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580786 Title: abnormal CPU-usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1580786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575655] Re: the network indicator shows the wrong status
Yeah, I'd like to add that this definitely happens after suspend for me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575655 Title: the network indicator shows the wrong status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1575655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575655] [NEW] the network indicator shows the wrong status
Public bug reported: Description:Ubuntu 16.04 LTS Release:16.04 indicator-applet: Installed: (none) Candidate: 12.10.2+15.04.20141127.2-0ubuntu1 Version table: 12.10.2+15.04.20141127.2-0ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages The network indicator sometimes shows the icon for wired connections and sometimes claims wifi without connection even though I'm consistently connected over wifi. I don't mean to say that it switches between these two or that always is wrong. But sometimes my connected to wifi symbol changes to wired. Other times it will change to the no connection wifi. The info is correct on boot, but switches over time, possibly after suspension. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: indicator-applet (not installed) 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 CurrentDesktop: Unity Date: Wed Apr 27 14:54:42 2016 InstallationDate: Installed on 2016-04-08 (18 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) SourcePackage: indicator-applet UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575655 Title: the network indicator shows the wrong status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1575655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574562] [NEW] Segfault on missing From field
Public bug reported: The bug was fixed in opendmarc version 1.2.1, but is still there in opendmarc 1.2 in Ubuntu 14.04. https://sourceforge.net/p/opendmarc/tickets/72/ Causes opendmarc to crash when no from field is specified. ** Affects: opendmarc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574562 Title: Segfault on missing From field To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opendmarc/+bug/1574562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567445] Re: ubi-prepare failed with exit code 255
However choosing to not enable third-party repos and not download along side installation seems to have solved the issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567445 Title: ubi-prepare failed with exit code 255 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1567445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567445] Re: ubi-prepare failed with exit code 255
I have the same issue, although checking or unchecking secure boot has no effect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567445 Title: ubi-prepare failed with exit code 255 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1567445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1561235] [NEW] Installation crashed
Public bug reported: During the installation there was an IO error. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubiquity 2.21.37 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.365 Date: Wed Mar 23 23:40:36 2016 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu-gnome.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.37 ubuntu-gnome wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561235 Title: Installation crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1561235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"
I'm still not sure what we're looking at here, especially if the original message this bug deals with has anything to do with the other described buggy behaviour here, which are: random freezes, display flickering, not working external displays etc. I watched the development of the comments in this bug really closely (not at least because of my own interests being affected as well) and there hasn't been any real progress in investigating this issue(s) further. I think this is not least caused by the complexity and variatons of issues regarding graphics. IMHO this leads to three taks which has to be done: 1. Identifiying distinct issues and filing distinct bug reports while being aware of possible duplicates. 2. If you're affected and feeling confident in providing more information, investigate those distinct issues further and provide proper amounts of logs/traces etc. possbile related to those distinct issues. 3. Pushing those issues to the proper upstream bugtrackes. (For me this is one of the hardest parts, since I'm not sure which parts play a role here, e.g. kernel, display manager etc.) When I look at my own logs (attached) my issue still looks like a kernel problem. I've tested the 4.5RC7, the origial message is gone, but my external display (connected to DP of my advanced lenovo dock) stays black if the T450s is docked while booting. If I undock after boot and then dock it again, the system freezes totally and syslog is showing some serious kernel issues. The only way to cirumvent this behaviour is to boot undocked and then dock when the system is fully booted. I'm currently using this workaround in my daily work to see if there are other issues. I think I will file a bug report on bugs.freedesktop.org later. ** Attachment added: "Syslog portion from plugging to dock until crash" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/+attachment/4595095/+files/syslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488719 Title: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1488719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"
Yes this patch is in the mainline kernel v4.5-rc1-wily. But I think regarding our problem here it does only what it says: shut up the messages. I just tested it, got a [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun at boot time now (related: https://bugzilla.kernel.org/show_bug.cgi?id=95461), while the [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! are gone. With external monitor connected things getting worse, gdm isn't able to use the monitor correctly and crashes from time to time. Looks like there are now other i915 bugs (maybe regression?) more urgent. Personally I will stick to 4.4 until I've got time to investigate this further with a clean install of ubuntu to eliminate the possibility that I'm looking at completely unrelated issues here. ** Bug watch added: Linux Kernel Bug Tracker #95461 http://bugzilla.kernel.org/show_bug.cgi?id=95461 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488719 Title: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1488719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"
I have to revice my comment from January 4th. The error is gone without external display connected with 4.4.0 rc7 for me too, still occuring with ext. display connected. I'm not sure what I was looking at, maybe booted the wrong kernel, stupid me. Since yesterday 4.4.0 rc8 is released, same behaviour without external display connected, error is gone. I will check rc8 with external display connected later this day when I'm at home. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488719 Title: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1488719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"
Tested 4.4.0 RC7 on Thinkpad T450s with i7-5600U. Error is still present like before, the log message is present with and without ext. display connected, although still much higher frequency of log msgs with ext. display connected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488719 Title: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1488719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"
@joakimkoed Yes this seems to be an upstream issue, see (updated) related freedesktop bug above, with no (working) fix released yet. I can confirm the behaviour with an without connected external monitor (already confirmed for 4.2. 0-16 genirc, can also confirm for 4.3.3-040303-generic). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488719 Title: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1488719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"
Bug 80896 is closed with fix released (which isn't fixing the issue), but there is another one open on freedesktop bugtracker. ** Bug watch added: freedesktop.org Bugzilla #92084 https://bugs.freedesktop.org/show_bug.cgi?id=92084 ** Changed in: linux Importance: High => Unknown ** Changed in: linux Status: Fix Released => Unknown ** Changed in: linux Remote watch: freedesktop.org Bugzilla #80896 => freedesktop.org Bugzilla #92084 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488719 Title: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1488719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"
Maybe I don't get it, but: Is the fix only shutting up the kernel messages or is this fixing the cause? I'm expiriencing this messages on a Lenovo T450 (20BX011GE) running 15.10 with 4.2.0-16-generic kernel. I see this messages wether external monitor is connected or not, although with much higher frequency with external monitor connected (dp via dock). It seems like this messages is related to random GDM crashes. I tried to reproduce this behaviour, but I've got no clue when this is happening so far. I will try to investigate this further. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488719 Title: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!" To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1488719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
Seems like there is already a bug filed for the [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)! kernel message: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500751 Title: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
I can confirm that the solution from #56 solves the problem with the dm- crypt password on boot, but there seem to be issues left. Still a lot of [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! in the kernel log. No system freezes so far, but I've only tested this for a few minutes. Should I open a new bug for this or should we extend this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500751 Title: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
I can confirm that 3.19.0-31-generic #36~RevertsV2 works without any of the issues. @rolfinator (seb2): Yes I have the same issues with the 3.19.0-30 kernel stated in the initial post (plus some random system freezes, except the workaround "boot -> wait for dm-crypt passphrase, which can't be entered --> reboot --> enter passphrase" works on 3.19.0-30, but system freezes remain afterwards). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500751 Title: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
The kernel from comment #46 didn't resolves the bug. The issue remains and even the reboot-workaround don't do the trick. When I disable splash then I can enter the passphrase, but afterwards the boot hangs with the kernel-log repeatedly stating [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! So it's almost the same behaviour as with the 3.19.0-30 kernel. Thanks for your work so far and if you need any further information please let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500751 Title: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
I can confirm comment #44. Running 3.19.0-29-generic #31~lp1500751Commit90dcba7ee works fine for me on Thinkpad T450s. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500751 Title: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1503572] Re: Crypt Login freeze and random system freeze
I can confirm this behaviour for my T450s runnig 15.04 with 3.19.0-30 kernel. Using the same workaround to input my dm-crypt password. Only one system freeze so far, kernel log also stating repeatedly [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control interrupt lied (SDE)! But I can't confirm this issue for 3.19.0-28-generic kernel. Currently using this kernel as fallback and everything seems to work fine. Please let me know if you need further information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1503572 Title: Crypt Login freeze and random system freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1503572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440157] Re: WARNING **: Could not connect to geoname lookup server: Operation was cancelled
Confirmed #10 working. Thanks sa-yu! Why is this not in the repos already? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1440157 Title: WARNING **: Could not connect to geoname lookup server: Operation was cancelled To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1440157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 349469] Re: debconf: DbDriver config: /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
I got this error on Ubuntu 14.04 after the Add printer driver-thingie crashed while trying to add openprinting-gutenprint. I tried many things including the suggestions here but the solution was to sudo apt-get install openprinting-gutenprint --reinstall The problem was that the program was half-installed so apt-get install and apt-get remove both failed. So did apt-get upgrade. I found my solution here: http://askubuntu.com/questions/245477/half-installed- package-error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver config: /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ambasa/+bug/349469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
