[Desktop-packages] [Bug 1874191] Re: Brightness setting too high
** Package changed: zsys (Ubuntu) => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1874191 Title: Brightness setting too high Status in gnome-settings-daemon package in Ubuntu: New Bug description: Hi, the default brightness setting of the live should be selected at 75%. 100% is annoying. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1874191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
** No longer affects: gnome-control-center (Ubuntu) ** No longer affects: gnome-shell (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values Status in mutter package in Ubuntu: In Progress Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: When the nvidia driver is installed, the screen turns off when trying to set some fractional scaling values like 150%. And it stays off even after rebooting and logging in again. And from ssh I can see there's no current mode set anymore (just like in bug 1869750): $ xrandr Screen 0: minimum 8 x 8, current 960 x 600, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 connected primary (normal left inverted right x axis y axis) 1920x1200 59.95 + 59.88 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 17 15:51:15 2020 InstallationDate: Installed on 2020-02-03 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874191] [NEW] Brightness setting too high
Public bug reported: Hi, the default brightness setting of the live should be selected at 75%. 100% is annoying. Thank you. ** Affects: zsys (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1874191 Title: Brightness setting too high Status in zsys package in Ubuntu: New Bug description: Hi, the default brightness setting of the live should be selected at 75%. 100% is annoying. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1874191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871960] Re: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam-modules:amd64
This bug was fixed in the package pango1.0 - 1.44.7-2ubuntu4 --- pango1.0 (1.44.7-2ubuntu4) focal; urgency=medium * Backport some Debian changes to try to fix upgrade issues (lp: #1871960) [ Simon McVittie ] * d/shlibs.local: Upgrade all binary packages in lockstep. Like many projects where one source package builds multiple binary packages, Pango has private headers that share non-public interfaces between its binary packages. Upgrading one binary package from this source without upgrading the others is not something that its upstream developers are ever going to test or support, and neither should we. (Closes: #958017) * libpango-1.0-0: Add Breaks on older libpango*-1.0-0. This should ensure that buster users can't get a broken partial upgrade by upgrading only libpango-1.0-0, but not the others, from 1.42.x to 1.44.x. -- Sebastien Bacher Tue, 21 Apr 2020 18:02:31 +0200 ** Changed in: pango1.0 (Ubuntu Focal) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1871960 Title: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam- modules:amd64 Status in libgtk3-perl package in Ubuntu: Confirmed Status in pango1.0 package in Ubuntu: Fix Released Status in libgtk3-perl source package in Focal: Confirmed Status in pango1.0 source package in Focal: Fix Released Bug description: I was updating ubuntu to the 20.04 version. Not all packages were updated. I receive new errors every few seconds. what should I do? Thanks safi ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.1.8-3.6ubuntu2.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 Date: Fri Apr 10 00:36:08 2020 ErrorMessage: pre-dependency problem - not installing libpam-modules:amd64 InstallationDate: Installed on 2019-12-28 (102 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1ubuntu1 SourcePackage: pam Title: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam-modules:amd64 UpgradeStatus: Upgraded to focal on 2020-04-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgtk3-perl/+bug/1871960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
Hi Olivier, Many thanks for starting that back up! I have install Chromium from the candidate/vaapi channel and the HW acceleration is working for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04
Looks like it was fixed as https://gitlab.gnome.org/GNOME/mutter/-/issues/1113 in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1206 That fix is in mutter 3.36.2 (which is not in Ubuntu yet). ** Changed in: mutter (Ubuntu Focal) Status: Fix Released => Fix Committed ** No longer affects: libreoffice (Ubuntu) ** No longer affects: libreoffice (Ubuntu Eoan) ** No longer affects: libreoffice (Ubuntu Focal) ** No longer affects: codelite (Ubuntu) ** No longer affects: codelite (Ubuntu Eoan) ** No longer affects: codelite (Ubuntu Focal) ** No longer affects: codeblocks (Ubuntu) ** No longer affects: codeblocks (Ubuntu Eoan) ** No longer affects: codeblocks (Ubuntu Focal) ** Changed in: mutter Status: Fix Released => Unknown ** Changed in: mutter Remote watch: gitlab.gnome.org/GNOME/mutter/issues #919 => gitlab.gnome.org/GNOME/mutter/-/issues #1113 ** Tags added: fixed-in-3.36.2 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 Status in LibreOffice: Confirmed Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Eoan: Triaged Status in mutter source package in Focal: Fix Committed Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
I've opened a new bug report: Bug #1874178 I'll mark myself as not affected by this one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: Confirmed Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04
In case anyone lands on the wrong bug, as often happens, please see also bug 1872527. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 Status in LibreOffice: Confirmed Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Eoan: Triaged Status in mutter source package in Focal: Fix Committed Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874178] [NEW] Unlocking existing session needs two attempts after selecting Switch User
Public bug reported: This has been occurring during the Xubuntu post-install test. It's not the same as Bug #1776475, as it's not necessary to have logged in as another user (or even for another user to exist) for the problem to happen. My sequence of actions is: *Create new user. *Open a program (usually Thunar or Terminal). *Lock session. *Click on "Switch User". <-- This is all that's necessary to trigger it. *Enter password to unlock my own session. *Then there's a delay and screen goes black, then the unlock prompt appears again. *The second time, my session unlocks. This particular report is from a QEMU/KVM vm, but it's also been happening on a bare-metal install. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 22 15:30:29 2020 InstallationDate: Installed on 2020-04-22 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200421) ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm-256color PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1874178 Title: Unlocking existing session needs two attempts after selecting Switch User Status in lightdm package in Ubuntu: New Bug description: This has been occurring during the Xubuntu post-install test. It's not the same as Bug #1776475, as it's not necessary to have logged in as another user (or even for another user to exist) for the problem to happen. My sequence of actions is: *Create new user. *Open a program (usually Thunar or Terminal). *Lock session. *Click on "Switch User". <-- This is all that's necessary to trigger it. *Enter password to unlock my own session. *Then there's a delay and screen goes black, then the unlock prompt appears again. *The second time, my session unlocks. This particular report is from a QEMU/KVM vm, but it's also been happening on a bare-metal install. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 22 15:30:29 2020 InstallationDate: Installed on 2020-04-22 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200421) ProcEnviron: LANGUAGE=en_NZ:en TERM=xterm-256color PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1874178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874049] Re: Gnome-shell block
Please start with uninstalling these extensions, then restart and see if the problem persists: 'gnom...@panacier.gmail.com', 'sensory-percept...@harlemsquirrel.github.io', 'temperature@xtranophilist', 'disk-space-us...@atareao.es', 'openweather-extens...@jenslody.de', 'move_cl...@rmy.pobox.com', 'dash-to-pa...@jderose9.github.com', 'gsconn...@andyholmes.github.io', 'sound-output-device-choo...@kgshank.net', 'easyscreenc...@iacopodeenosee.gmail.com', 'arc-m...@linxgem33.com', 'dash-to-d...@micxgx.gmail.com', 'd...@rastersoft.com', We need to try without extensions as a first step because so many bugs are caused by extensions. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1874049 Title: Gnome-shell block Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have gnome-shell blocked, when I click on any part of the shell: dock, menu etc ... nothing happens. I can only switch between windows with alt + tab. This is not the first time it happens, it has done so by replicating these steps: Virtual manager with OS started, taken the GNOME screenshot tool on Ubuntu (host), I select the screenshot (select area to be captured) I select a part of the screen on Virtual Manager, at this point the whole shell freezes, becomes non-clickable. I hope the explanation is understandable and helpful to improve Ubuntu. Thank you ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 12:53:28 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1874049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871281] Re: Latest snap channel not showing
This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.15 --- gnome-software (3.28.1-0ubuntu4.18.04.15) bionic; urgency=medium * debian/patches/0011-Support-snap-channels.patch: - Fix latest/* channels not showing versions (LP: #1871281) -- Robert Ancell Tue, 07 Apr 2020 15:28:58 +1200 ** Changed in: gnome-software (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: gnome-software (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1871281 Title: Latest snap channel not showing Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Released Status in gnome-software source package in Eoan: Fix Released Bug description: [Impact] Due to a code change for channel names in snapd gnome-software in bionic doesn't show versions in the 'latest/*' channels. Solution is to backport changes that always use the full name for channels to avoid this problem. Noticed in https://forum.snapcraft.io/t/track-request-v6-for-postman/13425/9 [Test Case] 1. Open GNOME Software 2. Search for the 'postman' snap Expected result: latest/stable channel shown with version like 7.21.1 Observed result: No version shown in for latest/* channels. [Regression potential] Risk of introducing new bugs in relation to channels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1871281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870270] Re: gnome-shell crashed with SIGSEGV in dri_flush_front_buffer() from intel_flush_front() from intel_glFlush()
** Also affects: mutter (CentOS) via https://bugs.centos.org/view.php?id=17275 Importance: Unknown Status: Unknown ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Bionic) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu Eoan) Status: New => Fix Released ** Changed in: mutter (Ubuntu Focal) Status: New => Fix Released ** Changed in: mutter (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Focal) Importance: Undecided => Medium ** No longer affects: gnome-shell (Ubuntu) ** No longer affects: gnome-shell (Ubuntu Bionic) ** No longer affects: gnome-shell (Ubuntu Eoan) ** No longer affects: gnome-shell (Ubuntu Focal) ** Changed in: mutter (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870270 Title: gnome-shell crashed with SIGSEGV in dri_flush_front_buffer() from intel_flush_front() from intel_glFlush() Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Confirmed Status in mutter source package in Eoan: Fix Released Status in mutter source package in Focal: Fix Released Status in mutter package in CentOS: Unknown Bug description: [Impact] gnome-shell crashes a lot on bionic: https://errors.ubuntu.com/problem/3841a5bc586bc3f532d2313a35f51e511772751f [Test Case] ** Someone who can reproduce the crash please fill this in ** [Regression Potential] Low. The same fix has been released to newer versions already for most of a year. [Other Info] gnome shell crashed / froze while switching keyboard layouts. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.13 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Mar 31 22:47:45 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1571973788 InstallationDate: Installed on 2020-03-13 (19 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /var/lib/gdm3 SegvAnalysis: Segfault happened at: 0x7fedbfa22393:jmpq *%rax PC (0x7fedbfa22393) ok source "*%rax" (0xfffaffed90151620) not located in a known VMA region (needed readable region)! SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgbm.so.1 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871281] Re: Latest snap channel not showing
This bug was fixed in the package gnome-software - 3.30.6-2ubuntu10.19.10.1 --- gnome-software (3.30.6-2ubuntu10.19.10.1) eoan; urgency=medium * debian/patches/0011-Support-snap-channels.patch: - Fix latest/* channels not showing versions (LP: #1871281) -- Robert Ancell Wed, 08 Apr 2020 16:33:47 +1200 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1871281 Title: Latest snap channel not showing Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Released Status in gnome-software source package in Eoan: Fix Released Bug description: [Impact] Due to a code change for channel names in snapd gnome-software in bionic doesn't show versions in the 'latest/*' channels. Solution is to backport changes that always use the full name for channels to avoid this problem. Noticed in https://forum.snapcraft.io/t/track-request-v6-for-postman/13425/9 [Test Case] 1. Open GNOME Software 2. Search for the 'postman' snap Expected result: latest/stable channel shown with version like 7.21.1 Observed result: No version shown in for latest/* channels. [Regression potential] Risk of introducing new bugs in relation to channels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1871281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873401] Re: Gnome Shell lock-up on GPU hotplug
** Summary changed: - xorg lock-up on GPU hotplug + Gnome Shell lock-up on GPU hotplug ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873401 Title: Gnome Shell lock-up on GPU hotplug Status in mutter package in Ubuntu: New Bug description: Discovered when testing EVDI-backed screen (https://github.com/DisplayLink/evdi). While adding new device /dev/dri/cardX xorg locks, it can be observed by the cursors that stop blinking or menus not responding. Sometimes it is just a short (1-2 sec.) pause, but sometimes (hard to state the exact reproduction rate, rather rarely) the screen stops completely. Interestingly enough, if using HW cursor, it moves fine. Keyboard is at least partially functional, as it's possible to "bail out" to tty with C-A-Fx and kill the session. Anything else is difficult to check, as nothing really happens on the screen, it just remains frozen. When adding 4 GPUs at once (e.g. via config in /etc/modprobe.d according to https://support.displaylink.com/knowledgebase/articles/1843660-screen-freezes-after-opening-an-application-only). Haven't checked other numbers yet, to be done soon. The problem occurs, when adding the devices, not enabling their associated screens/reading EDID or anything like that. Also, to be checked with UDL, similar behaviour is expected, but due to the fact that it adds only a single device at a time reproducing "complete" freeze might be difficult. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.8-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 09:24:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:060d] Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d] InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200415) MachineType: Dell Inc. Dell Precision M3800 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=e0a7aba8-1c09-4367-9d6b-c74b73017fb4 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/25/2018:svnDellInc.:pnDellPrecisionM3800:pvrA12:rvnDellInc.:rnDellPrecisionM3800:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.sku: Dell Precision M3800 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861609] Re: [focal] Xorg crashed with assertion failure (usually in a VM) at [privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from
It's certainly possible something has fixed it, like maybe the recent update to Xorg 1.20.8. Can anyone else confirm? ** Changed in: xorg-server (Ubuntu) Status: Fix Released => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1861609 Title: [focal] Xorg crashed with assertion failure (usually in a VM) at [privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRIMoveBuffersHelper Status in xorg-server package in Ubuntu: Incomplete Bug description: Xorg crashed with assertion failure (usually in a VM): privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. and call stack comes from DRIMoveBuffersHelper WORKAROUND Select 'Ubuntu on Wayland' on the login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1861609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
Tracking in: https://errors.ubuntu.com/problem/cfae777005d1d918049ddbf3ad3977adc2e272b0 ** Description changed: + https://errors.ubuntu.com/problem/cfae777005d1d918049ddbf3ad3977adc2e272b0 + + --- + problem with Ubuntu software centre ver.3.35.2 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.90-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 10 00:28:42 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-06 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcCmdline: gnome-control-center SegvAnalysis: - Segfault happened at: 0x55db27c2df87 : mov 0x3f8(%rax),%rax - PC (0x55db27c2df87) ok - source "0x3f8(%rax)" (0x03f8) not located in a known VMA region (needed readable region)! - destination "%rax" ok + Segfault happened at: 0x55db27c2df87 : mov 0x3f8(%rax),%rax + PC (0x55db27c2df87) ok + source "0x3f8(%rax)" (0x03f8) not located in a known VMA region (needed readable region)! + destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: - cc_panel_get_title_widget () - ?? () - ?? () - g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 - ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 + cc_panel_get_title_widget () + ?? () + ?? () + g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 + ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/cfae777005d1d918049ddbf3ad3977adc2e272b0 --- problem with Ubuntu software centre ver.3.35.2 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.90-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 10 00:28:42 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-06 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x55db27c2df87 : mov 0x3f8(%rax),%rax PC (0x55db27c2df87) ok source "0x3f8(%rax)" (0x03f8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: cc_panel_get_title_widget () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1862553/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874169] [NEW] dist-upgrade in focal: dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Public bug reported: I have been running focal out of date for a few weeks; today I upgraded everything, and had trouble while doing the update. Hopefully this is helpful: sarnold@millbarge:~$ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: brz libpython3-stdlib libreoffice libreoffice-base libreoffice-base-core libreoffice-base-drivers libreoffice-calc libreoffice-common libreoffice-core libreoffice-draw libreoffice-impress libreoffice-math libreoffice-report-builder-bin libreoffice-style-tango libreoffice-writer libtalloc2 python3 python3-apt python3-breezy python3-cairo python3-cffi-backend python3-dbus python3-distutils python3-dulwich python3-gdbm python3-gi python3-gi-cairo python3-gpg python3-lib2to3 python3-libapparmor python3-libvirt python3-libxml2 python3-minimal python3-netifaces python3-psutil python3-pycurl python3-pyrsistent python3-setproctitle python3-simplejson python3-systemd python3-talloc python3-uno python3-wrapt python3-yaml unattended-upgrades ure 0 upgraded, 0 newly installed, 0 to remove and 46 not upgraded. sarnold@millbarge:~$ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: libapt-pkg5.90 libboost-date-time1.67.0 libboost-locale1.67.0 libboost-system1.67.0 libboost-thread1.67.0 libpoppler90 libpython3.7 Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: uno-libs3 The following NEW packages will be installed: libboost-locale1.71.0 libjuh-java libjurt-java libridl-java libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3 libuno-salhelpergcc3-3 libunoloader-java python3.8 python3.8-minimal uno-libs-private The following packages will be upgraded: brz libpython3-stdlib libreoffice libreoffice-base libreoffice-base-core libreoffice-base-drivers libreoffice-calc libreoffice-common libreoffice-core libreoffice-draw libreoffice-impress libreoffice-math libreoffice-report-builder-bin libreoffice-style-tango libreoffice-writer libtalloc2 python3 python3-apt python3-breezy python3-cairo python3-cffi-backend python3-dbus python3-distutils python3-dulwich python3-gdbm python3-gi python3-gi-cairo python3-gpg python3-lib2to3 python3-libapparmor python3-libvirt python3-libxml2 python3-minimal python3-netifaces python3-psutil python3-pycurl python3-pyrsistent python3-setproctitle python3-simplejson python3-systemd python3-talloc python3-uno python3-wrapt python3-yaml unattended-upgrades ure 46 upgraded, 13 newly installed, 1 to remove and 0 not upgraded. Need to get 89.0 MB of archives. After this operation, 15.1 MB disk space will be freed. Do you want to continue? [Y/n] Get:1 http://wopr/ubuntu focal/main amd64 ure amd64 1:6.4.2-0ubuntu3 [1,221 kB] Get:2 http://wopr/ubuntu focal/main amd64 python3-uno amd64 1:6.4.2-0ubuntu3 [127 kB] Get:3 http://wopr/ubuntu focal/main amd64 libreoffice-style-tango all 1:6.4.2-0ubuntu3 [1,248 kB] Get:4 http://wopr/ubuntu focal/universe amd64 libreoffice-base amd64 1:6.4.2-0ubuntu3 [1,467 kB] Get:5 http://wopr/ubuntu focal/main amd64 libreoffice-calc amd64 1:6.4.2-0ubuntu3 [7,187 kB] Get:6 http://wopr/ubuntu focal/main amd64 libreoffice-draw amd64 1:6.4.2-0ubuntu3 [2,858 kB] Get:7 http://wopr/ubuntu focal/main amd64 libreoffice-impress amd64 1:6.4.2-0ubuntu3 [1,074 kB] Get:8 http://wopr/ubuntu focal/main amd64 libreoffice-core amd64 1:6.4.2-0ubuntu3 [31.6 MB] Get:9 http://wopr/ubuntu focal/main amd64 libreoffice-common all 1:6.4.2-0ubuntu3 [23.5 MB] Get:10 http://wopr/ubuntu focal/main amd64 libreoffice-writer amd64 1:6.4.2-0ubuntu3 [8,590 kB] Get:11 http://wopr/ubuntu focal/universe amd64 libreoffice-base-drivers amd64 1:6.4.2-0ubuntu3 [511 kB] Get:12 http://wopr/ubuntu focal/universe amd64 libreoffice-report-builder-bin amd64 1:6.4.2-0ubuntu3 [790 kB] Get:13 http://wopr/ubuntu focal/main amd64 libreoffice-math amd64 1:6.4.2-0ubuntu3 [402 kB] Get:14 http://wopr/ubuntu focal/universe amd64 libreoffice amd64 1:6.4.2-0ubuntu3 [12.6 kB] Get:15 http://wopr/ubuntu focal/main amd64 libreoffice-base-core amd64 1:6.4.2-0ubuntu3 [769 kB] Get:16 http://wopr/ubuntu focal/main amd64 libuno-sal3 amd64 1:6.4.2-0ubuntu3 [150 kB] Get:17 http://wopr/ubuntu focal/main amd64 libuno-salhelpergcc3-3 amd64 1:6.4.2-0ubuntu3 [16.0 kB] Get:18 http://wopr/ubuntu focal/main amd64 libuno-cppu3 amd64 1:6.4.2-0ubuntu3 [88.6 kB] Get:19 http://wopr/ubuntu focal/main amd64 uno-libs-private amd64 1:6.4.2-0ubuntu3 [226 kB] Get:20 http://wopr/ubuntu focal/main amd64 libuno-cppuhelpergcc3-3 amd64 1:6.4.2-0ubuntu3 [273 kB] Get:21 http://wopr/ubuntu focal/main amd64 libuno-purpenvhelpergcc3-3 amd64 1:6.4.2-0ubuntu3 [15.2 kB] Get:22 http://wopr/ubuntu focal/main amd64 libboost-loca
[Desktop-packages] [Bug 1871281] Update Released
The verification of the Stable Release Update for gnome-software has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1871281 Title: Latest snap channel not showing Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Released Status in gnome-software source package in Eoan: Fix Released Bug description: [Impact] Due to a code change for channel names in snapd gnome-software in bionic doesn't show versions in the 'latest/*' channels. Solution is to backport changes that always use the full name for channels to avoid this problem. Noticed in https://forum.snapcraft.io/t/track-request-v6-for-postman/13425/9 [Test Case] 1. Open GNOME Software 2. Search for the 'postman' snap Expected result: latest/stable channel shown with version like 7.21.1 Observed result: No version shown in for latest/* channels. [Regression potential] Risk of introducing new bugs in relation to channels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1871281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873321] Re: The Show Applications button should be clickable in the corner or bottom of the screen
I don't think High was appropriate here. It's an enhancement, not a bug. ** Tags added: fixed-in-dash-to-dock-69 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1873321 Title: The Show Applications button should be clickable in the corner or bottom of the screen Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Bug description: After one of the recent updates, clicking the Show Applications button in the very corner of the screen and at its bottom edge doesn't work. This bug applies in the cases of left and right positions of the dock and there is no this bug in the case of bottom position. This issue is very annoying since the mouse pointer runs at the very corner of the screen in vast majority of cases as you intent to press the Show Apps button. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 20:34:32 2020 InstallationDate: Installed on 2019-04-25 (356 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1873321/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
I have the hardware and the interest so I will do some debugging of this soon. ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: When the nvidia driver is installed, the screen turns off when trying to set some fractional scaling values like 150%. And it stays off even after rebooting and logging in again. And from ssh I can see there's no current mode set anymore (just like in bug 1869750): $ xrandr Screen 0: minimum 8 x 8, current 960 x 600, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 connected primary (normal left inverted right x axis y axis) 1920x1200 59.95 + 59.88 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 17 15:51:15 2020 InstallationDate: Installed on 2020-02-03 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 597056] Re: HP Touchsmart 600-1005xt No sound from Internal Speakers
Hello, I have Ubuntu 18.04 installed on my HP touchsmart 600. Audio still doesn't work either the internal speakers, or if I connect outside speakers through 3.5mm audio jack. A USB headset works though and I can listen to YouTube using it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/597056 Title: HP Touchsmart 600-1005xt No sound from Internal Speakers Status in alsa-driver package in Ubuntu: Incomplete Bug description: Found there is no internal speaker output from hp touchsmart 600-1005xt in all releases of Ubuntu 8.04 to 10.04LTS (64bit) with updated alsa-base (on 1.0.22.1 in Lucid now). All outputs & inputs work except the Internal speakers. I Checked all alsamixer levels, I have also noticed the nodeid's it seem to be mapped 0x15 - 0x0d - 0x03 (21 - 13 - 3) for internal speakers which gives same results (no audio) in osx Applehda.kext. The Headphone nodeid's of 0x14 - 0x0c - 0x02 (20 - 12 - 2) seem to work in all Ubuntu Dists & OSx as well. Windows 7 Driver everything works of course. Is Bios sending wrong pin configs for internal audio? if so what would the resolution be? here is my alsa-information from alsa-info.sh attached, My only guess is the pin configs how do you change them in alsa driver & how could I get the correct ones if the bios was sending wrong pathmaps? I should also note I've tried most of the model flags in alsa-base.conf in the alc888 documentation & rebooted countless times, model=auto shows the internal speaker but sound comes out headphones plug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/597056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874155] [NEW] package emacs-lucid (not installed) failed to install/upgrade: installed emacs-lucid package post-installation script subprocess returned error exit status 1
Public bug reported: ProblemType: Package DistroRelease: Ubuntu 19.10 Package: emacs-lucid (not installed) Uname: Linux 4.4.178chromium-g4245c5e1 x86_64 ApportVersion: 2.20.11-0ubuntu8.8 AptOrdering: emacs-gtk:amd64: Purge emacs-lucid:amd64: Install NULL: ConfigurePending NULL: PurgePending NULL: ConfigurePending Architecture: amd64 Date: Tue Apr 21 15:35:15 2020 ErrorMessage: installed emacs-lucid package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: emacs Title: package emacs-lucid (not installed) failed to install/upgrade: installed emacs-lucid package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2020-04-20 (0 days ago) ** Affects: emacs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs in Ubuntu. https://bugs.launchpad.net/bugs/1874155 Title: package emacs-lucid (not installed) failed to install/upgrade: installed emacs-lucid package post-installation script subprocess returned error exit status 1 Status in emacs package in Ubuntu: New Bug description: ProblemType: Package DistroRelease: Ubuntu 19.10 Package: emacs-lucid (not installed) Uname: Linux 4.4.178chromium-g4245c5e1 x86_64 ApportVersion: 2.20.11-0ubuntu8.8 AptOrdering: emacs-gtk:amd64: Purge emacs-lucid:amd64: Install NULL: ConfigurePending NULL: PurgePending NULL: ConfigurePending Architecture: amd64 Date: Tue Apr 21 15:35:15 2020 ErrorMessage: installed emacs-lucid package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: emacs Title: package emacs-lucid (not installed) failed to install/upgrade: installed emacs-lucid package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2020-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1874155/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
I also have the same problem, regards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866841] Re: [SRU] Add chrome-gnome-shell to the recommends of gnome-shell-extension-prefs
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866841 Title: [SRU] Add chrome-gnome-shell to the recommends of gnome-shell- extension-prefs Status in gnome-shell package in Ubuntu: In Progress Bug description: [Impact] * Since GNOME 3.36, Shell Extensions can no longer be installed using GNOME Software (Ubuntu Software), instead there was a new Extensions (gnome-shell-extension-prefs) application prepared to replace this functionality. However, this application itself does not support installing new extensions, instead, it opens a web browser with a extensions.gnome.org website that allows browsing and installing new extensions. This website depends on a chrome-gnome-shell package that provides GNOME Shell integration (connector) for Firefox, Chrome, Chromium and other web browsers for this functionality. Without this connector, it is not possible to install Shell Extensions on Ubuntu 20.04. * In this SRU, I want to propose adding this chrome-gnome-shell package to recommends of the gnome-shell-extension-prefs package. However, since the gnome-shell-extension-prefs package is in a main repository and chrome-gnome-shell is in universe, it would be probably also needed to first move the gnome-shell-extension-prefs package to universe. [Test Case] * Install the "gnome-shell-extension-prefs" (Extensions) application. * Open the "Extensions" application, click the "i" button in the window header, click the "extensions.gnome.org" link. * In the web browser window, click on link inside the blue notification on extensions.gnome.org to install a browser extension (frontend for the connector), then refresh the page. * After this, a red notification appears on the web page telling the user that host connector is not running. [Regression Potential] * Without the chrome-gnome-shell package installed, it is not possible to install Shell Extensions on Ubuntu 20.04. [Other Info] * More information: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871960] Re: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam-modules:amd64
I tested an upgrade from Bionic to Focal with -proposed enabled (I had to remove the disabling of -proposed in DistUpgradeController.py) and did not encounter any of the following error messages: GLib-GObject-WARNING **: specified class size for type 'PangoCairoFcFont' is smaller than the parent type's 'PangoFcFont' class size at /usr/lib/x86_64-linux-gnu/perl5/5.30/Glib/Object/Introspection.pm line 67. GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed at /usr/lib/x86_64-linux-gnu/perl5/5.30/Glib/Object/Introspection.pm line 67. GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed at /usr/lib/x86_64-linux-gnu/perl5/5.30/Glib/Object/Introspection.pm line 67. GLib-GObject-CRITICAL **: g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed at /usr/lib/x86_64-linux-gnu/perl5/5.30/Glib/Object/Introspection.pm line 67. I had seen them when I tried upgrading the same virtual machine when -proposed was not enabled. Attached you'll find my apt-term.log from the successful upgrade. ** Attachment added: "apt-term.log" https://bugs.launchpad.net/ubuntu/+source/libgtk3-perl/+bug/1871960/+attachment/5357734/+files/apt-term.log ** Also affects: pango1.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: pango1.0 (Ubuntu Focal) Status: New => Confirmed ** Changed in: pango1.0 (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: pango1.0 (Ubuntu Focal) Milestone: None => ubuntu-20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1871960 Title: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam- modules:amd64 Status in libgtk3-perl package in Ubuntu: Confirmed Status in pango1.0 package in Ubuntu: Confirmed Status in libgtk3-perl source package in Focal: Confirmed Status in pango1.0 source package in Focal: Confirmed Bug description: I was updating ubuntu to the 20.04 version. Not all packages were updated. I receive new errors every few seconds. what should I do? Thanks safi ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.1.8-3.6ubuntu2.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 Date: Fri Apr 10 00:36:08 2020 ErrorMessage: pre-dependency problem - not installing libpam-modules:amd64 InstallationDate: Installed on 2019-12-28 (102 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1ubuntu1 SourcePackage: pam Title: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam-modules:amd64 UpgradeStatus: Upgraded to focal on 2020-04-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgtk3-perl/+bug/1871960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1871011] Re: USB scanning broken on focal --> hpmud and ippusbxd conflict
I did not do anything special, I just grep'd the syslog it was there. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Tue, 21 Apr 2020, Bartosz Kosiorek wrote: > Date: Tue, 21 Apr 2020 10:27:24 - > From: Bartosz Kosiorek <1871...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1871011] Re: USB scanning broken on focal --> hpmud and ippusbxd > conflict > > I have the similar issues with USB detection after upgrade to Ubuntu 20.04 on > my scanners (HP Laser MFP 135a - smfp backend and HP OfficeJet 4630 - hpaio > backend). > WIth > > The hpaio scanner is detected on USB, but it is not able to communicate > (xsane, scanimage, simple-scan). Only scanning by network is working > correctly. > > With HP Laser MFP 135a - smfp, it is not able to detect it on usb port. > > I would like to investigate this issue further. > How did you enabled logs to investigate this issue? > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1873748). > https://bugs.launchpad.net/bugs/1871011 > > Title: > USB scanning broken on focal --> hpmud and ippusbxd conflict > > Status in HPLIP: > Invalid > Status in hplip package in Ubuntu: > Incomplete > > Bug description: > On Ubuntu 20.04 focal (with -proposed enabled). HPLIP=3.20.3. > > Previously there was a libmtp (udev) bug erroneously detecting HP > printers as mtp devices. This was fixed. Now, I can try to scan-- from > both simple-scan and hp-scan, hplip errors out: > > > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found > interface conf=0, iface=1, altset=0, index=1 > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active > kernel driver on interface=1 ret=0 > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid > claim_interface 7/1/2: Device or resource busy > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found > interface conf=0, iface=0, altset=1, index=3 > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active > kernel driver on interface=0 ret=0 > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid > claim_interface 7/1/4: Device or resource busy > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found > interface conf=0, iface=3, altset=0, index=9 > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active > kernel driver on interface=3 ret=0 > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid > claim_interface ff/4/1: Device or resource busy > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found > interface conf=0, iface=0, altset=0, index=11 > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active > kernel driver on interface=0 ret=0 > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid > claim_interface ff/cc/0: Device or resource busy > > Printer/scanner is an Officejet 4635. Scanning previously worked just > fine a few months ago. Regression? > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hplip/+bug/1871011/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1871011 Title: USB scanning broken on focal --> hpmud and ippusbxd conflict Status in HPLIP: Invalid Status in hplip package in Ubuntu: Incomplete Bug description: On Ubuntu 20.04 focal (with -proposed enabled). HPLIP=3.20.3. Previously there was a libmtp (udev) bug erroneously detecting HP printers as mtp devices. This was fixed. Now, I can try to scan-- from both simple-scan and hp-scan, hplip errors out: Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=1, altset=0, index=1 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=1 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/2: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=1, index=3 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/4: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=3, altset=0, index=9 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=3 ret
[Desktop-packages] [Bug 1866841] Re: [SRU] Move gnome-shell-extension-prefs to universe and add chrome-gnome-shell to its recommends
gnome-shell-extension-prefs is now in universe. That makes the remainder of this bug a simple SRU candidate. I uploaded this change to the focal queue earlier today. It will need to be manually approved to be accepted into Ubuntu 20.04 LTS. ** Summary changed: - [SRU] Move gnome-shell-extension-prefs to universe and add chrome-gnome-shell to its recommends + [SRU] Add chrome-gnome-shell to the recommends of gnome-shell-extension-prefs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866841 Title: [SRU] Add chrome-gnome-shell to the recommends of gnome-shell- extension-prefs Status in gnome-shell package in Ubuntu: In Progress Bug description: [Impact] * Since GNOME 3.36, Shell Extensions can no longer be installed using GNOME Software (Ubuntu Software), instead there was a new Extensions (gnome-shell-extension-prefs) application prepared to replace this functionality. However, this application itself does not support installing new extensions, instead, it opens a web browser with a extensions.gnome.org website that allows browsing and installing new extensions. This website depends on a chrome-gnome-shell package that provides GNOME Shell integration (connector) for Firefox, Chrome, Chromium and other web browsers for this functionality. Without this connector, it is not possible to install Shell Extensions on Ubuntu 20.04. * In this SRU, I want to propose adding this chrome-gnome-shell package to recommends of the gnome-shell-extension-prefs package. However, since the gnome-shell-extension-prefs package is in a main repository and chrome-gnome-shell is in universe, it would be probably also needed to first move the gnome-shell-extension-prefs package to universe. [Test Case] * Install the "gnome-shell-extension-prefs" (Extensions) application. * Open the "Extensions" application, click the "i" button in the window header, click the "extensions.gnome.org" link. * In the web browser window, click on link inside the blue notification on extensions.gnome.org to install a browser extension (frontend for the connector), then refresh the page. * After this, a red notification appears on the web page telling the user that host connector is not running. [Regression Potential] * Without the chrome-gnome-shell package installed, it is not possible to install Shell Extensions on Ubuntu 20.04. [Other Info] * More information: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873937] Re: nvidia-340 prevents booting into single user mode under Ubuntu 20.04
This bug doesn't exist on the same hardware (a 2008 MacPro with Mac ROM'd GTX680) under current Ubuntu 19.10 with the nvidia-340 package installed. In that case, booting the default 5.3.0-46-generic kernel in single user mode produces the expected prompt. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1873937 Title: nvidia-340 prevents booting into single user mode under Ubuntu 20.04 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Steps to reproduce this bug... 1) Install the current nvidia-340 340.108-0ubuntu2 package. 2) Reboot to confirm nvidia graphics drivers are functional. 3) Reboot and edit the default kernel options to have 'single' before 'quiet splash' 4) Boot the edited kernel options The single user mode is broken under 20.04 with the nvidia 340 drivers. A black screen appears with no single user prompts. If you remove the nvidia-340 package and reboot, single user mode works as expected under the nouveau drivers. I have confirmed with current Ubuntu 18.04 that this bug with the nvidia-340 drivers doesn't exist and single user mode works properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1873937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873658] Re: Deb Files are not associated with an application that manages packages
There is no update available yet that will fix this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Invalid Status in desktop-file-utils source package in Focal: Confirmed Status in gdebi source package in Focal: Invalid Bug description: When you download a DEB file within 20.04 Ubuntu Beta and you double click it the file is opened by the archive manager. I would expect the installer to open the file just like in previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874148] [NEW] "I wish I knew how to quit you!"
Public bug reported: I've just installed Ubuntu 20.04 LTS and gnome-initial-setup has launched and I don't want to answer all these questions so I went to application's title bar in gnome-shell and clicked "Welcome to Ubuntu" under that I saw a "Quit" option. However, when I click "Quit" nothing happens. ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: New ** Tags: champagne focal ** Tags added: champagne focal ** Summary changed: - I wish I knew how to quit you! + "I wish I knew how to quit you!" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1874148 Title: "I wish I knew how to quit you!" Status in gnome-initial-setup package in Ubuntu: New Bug description: I've just installed Ubuntu 20.04 LTS and gnome-initial-setup has launched and I don't want to answer all these questions so I went to application's title bar in gnome-shell and clicked "Welcome to Ubuntu" under that I saw a "Quit" option. However, when I click "Quit" nothing happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1874148/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873658] Re: Deb Files are not associated with an application that manages packages
** Also affects: desktop-file-utils (Ubuntu Focal) Importance: High Assignee: Ken VanDine (ken-vandine) Status: Confirmed ** Also affects: gdebi (Ubuntu Focal) Importance: High Status: Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Invalid Status in desktop-file-utils source package in Focal: Confirmed Status in gdebi source package in Focal: Invalid Bug description: When you download a DEB file within 20.04 Ubuntu Beta and you double click it the file is opened by the archive manager. I would expect the installer to open the file just like in previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
Thanks. It does look to me that the keyboard issue is probably separate and certainly warrants a bug, in particular if it is a regression and those 2-in-1s switched fine with Ubuntu 19.10. But I am just a mere user here, @vanvugt will know. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873658] Re: Deb Files are not associated with an application that manages packages
Please ignore last comment. Now brings up software centre and says Failed to install File - Not Supported. ** Attachment added: "Screen Grab" https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1873658/+attachment/5357720/+files/Capture2.PNG -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Invalid Bug description: When you download a DEB file within 20.04 Ubuntu Beta and you double click it the file is opened by the archive manager. I would expect the installer to open the file just like in previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873658] Re: Deb Files are not associated with an application that manages packages
Seems to have been fixed with an update this evening? ** Attachment added: "Screen Grab" https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1873658/+attachment/5357719/+files/Capture.PNG -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Invalid Bug description: When you download a DEB file within 20.04 Ubuntu Beta and you double click it the file is opened by the archive manager. I would expect the installer to open the file just like in previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
Yes, I think your definition is correct. This bug is/should be primarily about the virtual keyboard not appearing when using the Xorg session, even though all (ACPI) events for tablet mode are handled properly. It seems to work fine within the Wayland session and it worked fine in Xorg in previous Ubuntu releases. And we have a second issue, which causes similar issues also under Wayland. It happens when 2-in-1 devices don't switch to tablet mode under Ubuntu. This issue was also introduced with GNOME 3.36/Ubuntu 20.04. It would probably be a good idea to open another bug report for each unsupported device, I guess? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772683] Re: [snap] Cannot sign a document, gpg keys are not listed
Hi, I see the same on Version: 6.0.7.3 Build ID: 1:6.0.7-0ubuntu0.18.04.10 on Ubuntu 18.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1772683 Title: [snap] Cannot sign a document, gpg keys are not listed Status in LibreOffice: Won't Fix Status in libreoffice package in Ubuntu: Triaged Bug description: (initially reported on the forum: https://forum.snapcraft.io/t /libreoffice-snap-missing-features-and-known-bugs/3920/10) Libreoffice 6.0.4.2 (64, candidate channel). Steps to reproduce: 1) snap run libreoffice.writer 2) write something, then save the document (anywhere) on disk 3) Open the File menu, then Digital Signatures > Digital Signatures… 4) in the dialog, click "Sign Document…" Expected result: your GPG keys are listed Current result: no keys are listed To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1772683/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856624]
[Bugbug](https://github.com/mozilla/bugbug/) thinks this bug should
belong to this component, but please revert this change in case of
error.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1856624
Title:
Firefox freezes temporarily at 100% CPU when Chromium is opened
Status in Mozilla Firefox:
New
Status in firefox package in Ubuntu:
Confirmed
Bug description:
When Firefox is open, and I open Chromium, many features of Firefox
fail to work for several seconds. (To reproduce, start with neither
Firefox nor Chromium open; open Firefox, and allow one or more web
pages to load; then open Chromium; the issue starts a second or two
after Chromium is opened.) This is a temporary issue, lasting for
several seconds; the length of time it lasts appears to depend on how
many open tabs have been viewed since Firefox opened (on my computer,
around 10 seconds with 1 tab having been viewed, around a minute with
10 tabs having been viewed). This reproduces even when running Firefox
as `firefox -safe-mode`.
While the issue is ongoing (i.e. starting around a second after Chromium is
open, and persisting for typically tens of seconds), some features of Firefox
work, but most do not:
- Scrolling the current tab short distances succeeds, showing the expected
text on the page.
- Scrolling the current tab long distances (several screeenfuls) causes the
page to be "cut off" past a certain point, with only a blank background
rendering.
- Moving the mouse cursor over a link does not change the mouse cursor
(expected behaviour, and behaviour while the issue is not ongoing, is for it to
change to a hand shape).
- Changing tab causes the resulting page not to display: rather, a grey
background is displayed, and sometimes a loading spinner.
- Changing tab back then causes the original page not to render, as if it
were new, despite the fact it was correctly displayed earlier.
- The address bar functions as normal; the issue does not appear to affect
address bar functionality.
Additionally, while the issue is ongoing, Firefox uses 100% CPU.
At some point after the issue in question starts, it stops, and all
Firefox features return to normal (including any missing or
incorrectly rendered page content, which renders again when the issue
ends).
The trigger is specifically the act of opening Chromium: Firefox can
function just fine once the issue ends, even if Chromium is still
open, and functions just fine if Chromium is opened first.
I have an (unconfirmed) theory that opening Chromium is causing some
operation within Firefox to become very slow, using up all the CPU
time, and the other observed misbehaviours within Firefox are a
consequence of how slowly it is running; however, I've listed them all
anyway in case it provides clarity into what the specific nature of
the bug is.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 71.0+build5-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ais523 1800 F pulseaudio
BuildID: 20191205184924
Channel: Unavailable
CurrentDesktop: X-Cinnamon
Date: Tue Dec 17 00:29:10 2019
ExecutablePath: /usr/lib/firefox/firefox
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Français Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2019-11-11 (35 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
IpRoute:
default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
169.254.0.0/16 dev wlp2s0 scope link metric 1000
192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric
600
MostRecentCrashID: bp-935fd166-3720-454f-8fe5-0a1752140227
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:722
PrefSources: prefs.js
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, user)
XDG_RUNTIME_DIR=
LANG=en_GB.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=71.0/20191205184924 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.1
dmi.board.name: 0DDKKC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.
[Desktop-packages] [Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
Thanks. So it seems as follows, correct? This here bug report refers only to running under Xorg in Focal, where ... - the OSK does not work at all on the properly supported devices (at least the ones listed), - neither per autosummon nor on demand by swiping, - regardless of a physical keyboard not being available. This is a regression compared to Eoan. However the OSK is working in Focal as expected [1] on Wayland, on supported devices where the physical keyboard gets properly disabled. As far as I know, it is not expected for autosummon to work for KeePassXC etc., but in this case I can summon on demand in Wayland by swiping from bottom of screen. (But can't under Xorg) [1] It seems it is expected that even in Wayland the OSK is only available when the physical keyboard is disabled, according to discussion on this gnome-shell report: "On Screen Keyboard shows up on Wayland despite there is a physical keyboard" https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 The above gnome-shell #2353 is linked from the gnome-shell report that seems to be related to the issue in this here bug, as @esjarc mentioned in the duplicate Bug #1874017, i.e.: "OSK isn't activated without physical keyboard" https://gitlab.gnome.org/GNOME/gnome-shell/issues/2378 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2353 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
** No longer affects: gnome-shell (Ubuntu) ** Project changed: gnome-shell => ubuntu-translations ** No longer affects: ubuntu-translations ** Bug watch removed: gitlab.gnome.org/GNOME/gnome-shell/-/issues #447 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/447 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxau in Ubuntu. https://bugs.launchpad.net/bugs/1559650 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() Status in libxau package in Ubuntu: Fix Released Status in libxau source package in Bionic: Fix Committed Status in libxau source package in Eoan: Fix Released Status in libxau source package in Focal: Fix Released Bug description: [Impact] gnome-shell crashes a lot. Over 38000 times in bionic so far: https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7 [Test Case] None known yet. Just keeping an eye on the above link for regressions. [Regression Potential] Low. The same fix has been released to newer distros for the past 2 years already. [Other Info] ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Mar 16 17:15:11 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-13 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb $0x0,(%r12) PC (0x7f1ff33f46ab) ok source "$0x0" ok destination "(%r12)" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at vsnprintf_chk.c:55 ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34 XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6 XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxau/+bug/1559650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
@mario-vukelic I am sorry, I forgot to mention this information in my previous comments. Lenovo ThinkPad L390 Yoga: Keyboard, keyboard backlight and touchpad get disabled HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet: Keyboard, backlight and touchpad don't get disabled I wouldn't be surprised if it doesn't work on the latter two devices because of the unsupported tablet mode. Just tested it again and for some reason it worked on the L390 Yoga now? But it only seems to work in native Wayland applications (gedit, Firefox, Shell are working at the moment; Brave, KeePassXC, VirtualBox aren't). Xwayland and Xorg are still problematic. It is really interesting that it does work on the L390 Yoga now, as it definitely didn't work the last couple of months (not even in the Shell overview) and earlier today ... I will definitely watch this more closely now. Since earlier today I rebooted the L390 Yoga a couple of times. Other than that I haven't changed anything, unattended-upgrades has not even installed updates since yesterday (according to the log files). Hopefully this isn't one of the issues that only happens sporadically ... The other two devices are still unchanged. At least we now have the same symptoms (for now?) on all of the properly supported devices. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866574] Re: Update to 1.56
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1866574 Title: Update to 1.56 Status in snapd-glib package in Ubuntu: Fix Released Status in snapd-glib source package in Bionic: Confirmed Status in snapd-glib source package in Eoan: Fix Committed Status in snapd-glib source package in Focal: Fix Released Bug description: [Impact] A newer snapd-glib is available that adds support for new features in snapd. snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates [Test Case] The reverse depends of snapd-glib should continue to function, this is currently: - gnome-software - gnome-initial-setup - pulseaudio [Regression Potential] Any new release has a risk of introducing bugs, this is mitigated by automatic regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1866574/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874130] [NEW] lirc fails to install because of a missing /etc/lirc/lirc_options.conf - Ubuntu 20.04
Public bug reported: Hello, I have tried to install lirc on a fresh Kubuntu 20.04 Release Candidate installation on a AMD Athlon X2 system. The installation failed, with a half installed lirc package. This is leaving apt-get / apt in a state, that makes it impossible to install other packages or updates anymore, as it first tries to finish the lirc installation. This is leaving the system in a state, where further software changes or the usage of lirc are not possible. After using Google to find a solution for the problem, I found this bug report about lirc on Debian bugs website: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932779 The suggested workaround is to creating the file lirc_options.conf and to continue the failed installation (which worked on my system) via: sudo cp /etc/lirc/lirc_options.conf.dist /etc/lirc/lirc_options.conf sudo apt-get install lirc This worked on my installation brought the system back into a state, where further software installations or updates via apt-get / apt work again. Ubuntu version: user1@AthlonX2:lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 package information: user1@AthlonX2:/etc/lirc$ apt-cache policy lirc lirc: Installiert: 0.10.1-6.1 Installationskandidat: 0.10.1-6.1 Versionstabelle: *** 0.10.1-6.1 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status Terminal output during the failing installation via apt-get install: user1@AthlonX2:/etc/lirc$ LC_ALL=C sudo apt-get install lirc Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libftdi1-2 liblirc0 Suggested packages: lirc-compat-remotes lirc-drv-irman lirc-doc lirc-x setserial ir-keytable Recommended packages: gir1.2-vte The following NEW packages will be installed: libftdi1-2 liblirc0 lirc 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/571 kB of archives. After this operation, 2897 kB of additional disk space will be used. Do you want to continue? [Y/n] y Selecting previously unselected package libftdi1-2:amd64. (Reading database ... 360984 files and directories currently installed.) Preparing to unpack .../libftdi1-2_1.4-2build2_amd64.deb ... Unpacking libftdi1-2:amd64 (1.4-2build2) ... Selecting previously unselected package liblirc0:amd64. Preparing to unpack .../liblirc0_0.10.1-6.1_amd64.deb ... Unpacking liblirc0:amd64 (0.10.1-6.1) ... Selecting previously unselected package lirc. Preparing to unpack .../lirc_0.10.1-6.1_amd64.deb ... Unpacking lirc (0.10.1-6.1) ... Setting up liblirc0:amd64 (0.10.1-6.1) ... Setting up libftdi1-2:amd64 (1.4-2build2) ... Setting up lirc (0.10.1-6.1) ... Job for lircd.service failed because a fatal signal was delivered causing the control process to dump core. See "systemctl status lircd.service" and "journalctl -xe" for details. invoke-rc.d: initscript lircd, action "start" failed. * lircd.service - Flexible IR remote input/output application support Loaded: loaded (/lib/systemd/system/lircd.service; disabled; vendor preset: enabled) Active: failed (Result: core-dump) since Tue 2020-04-21 20:05:34 CEST; 16ms ago TriggeredBy: * lircd.socket Docs: man:lircd(8) http://lirc.org/html/configure.html Process: 12249 ExecStart=/usr/sbin/lircd --nodaemon (code=dumped, signal=SEGV) Main PID: 12249 (code=dumped, signal=SEGV) Apr 21 20:05:33 Madlen-Zimmer systemd[1]: Starting Flexible IR remote input/output application support... Apr 21 20:05:33 Madlen-Zimmer lircd[12249]: Warning: cannot open /etc/lirc/lirc_options.conf Apr 21 20:05:33 Madlen-Zimmer lircd-0.10.1[12249]: Info: lircd: Opening log, level: Info Apr 21 20:05:33 Madlen-Zimmer lircd-0.10.1[12249]: Notice: Version: lircd 0.10.1 Apr 21 20:05:33 Madlen-Zimmer lircd-0.10.1[12249]: Notice: System info: Linux Madlen-Zimmer 5.4.0-25-generic #29-Ubuntu SMP Fri Apr 17 15:06:57 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Apr 21 20:05:34 Madlen-Zimmer systemd[1]: lircd.service: Main process exited, code=dumped, status=11/SEGV Apr 21 20:05:34 Madlen-Zimmer systemd[1]: lircd.service: Failed with result 'core-dump'. Apr 21 20:05:34 Madlen-Zimmer systemd[1]: Failed to start Flexible IR remote input/output application support. dpkg: error processing package lirc (--configure): installed lirc package post-installation script subprocess returned error exit status 1 Processing triggers for systemd (245.4-4ubuntu1) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for libc-bin (2.31-0ubuntu9) ... Errors were encountered while processing: lirc E: Sub-process /usr/bin/dpkg returned an error code (1) user1@AthlonX2:/etc/lirc$ Terminal output during copying the file and inishing the installation: user1@AthlonX2:/etc/lirc$ sudo cp /etc/lirc/lirc_options.conf.backup1 /etc/lirc/lirc_options.conf user1@AthlonX2:/etc/lirc$ s
[Desktop-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
This bug was fixed in the package ubiquity - 20.04.15 --- ubiquity (20.04.15) focal; urgency=medium [ Dimitri John Ledkov ] * check-kernels: install the right nvidia modules for the OEM kernel. (LP: #1873867) [ Iain Lane ] * language, partman, prepare: Factor out sensible-browser launching and use it (LP: #1874070) -- Dimitri John Ledkov Tue, 21 Apr 2020 16:07:58 +0100 ** Changed in: ubiquity (Ubuntu Focal) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Committed Status in linux source package in Focal: Incomplete Status in nvidia-graphics-drivers-440 source package in Focal: Fix Released Status in ubiquity source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Confirmed Status in ubuntu-meta source package in Focal: Fix Committed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846882] Re: Thunderbird crashes when clicking on enigmail menu item while composing a message in a Unity session
This bug was fixed in the package thunderbird -
1:68.7.0+build1-0ubuntu0.16.04.2
---
thunderbird (1:68.7.0+build1-0ubuntu0.16.04.2) xenial; urgency=medium
* Ignore comment nodes in menu definitions, thus preventing a crash when
using the enigmail extension in conjuction with the global menu
(LP: #1846882)
- debian/patches/unity-menubar.patch
-- Olivier Tilloy Fri, 17 Apr 2020
17:00:33 +0200
** Changed in: thunderbird (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1846882
Title:
Thunderbird crashes when clicking on enigmail menu item while
composing a message in a Unity session
Status in thunderbird package in Ubuntu:
Fix Released
Bug description:
Thunderbird 1:68.1.1+build1-0ubuntu1 On Ubuntu 19.10 fully updated.
When writing an email, upon clicking on Enigmail in the menu bar,
Thunderbird crashes.
I contacted Enigmail’s lead dev about the issue who wrote:
"…but even if the crash is initiated by Enigmail, the cause is
certainly in Thunderbird. Enigmail is purely JavaScript and XUL - and by
definition of the programming languages, these two cannot crash
Thunderbird."
I tried Thunderbird 68.1.1 from Mozilla’s site, and can’t
reproduce the problem with it.
Here is Thunderbird’s log upon crashing:
AdapterDeviceID: 0x1912
AdapterDriverVendor: mesa/i965
AdapterDriverVersion: 19.3.0.0
AdapterVendorID: 0x8086
Add-ons:
%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D:68.1.1,%7B847b3a00-7ab1-11d4-8f02-006008948af5%7D:2.1.2,antidote7_linux_thunderbird_102%40druide.com:10.1.30,en-CA%40dictionaries.addons.mozilla.org:3.1.0,fr-dicollecte%40dictionaries.addons.mozilla.org:6.3.1webext,wetransfer%40extensions.thunderbird.net:2.0.0,thunderbird-compact-dark%40mozilla.org:1.0,google%40search.mozilla.org:1.0,bing%40search.mozilla.org:1.0,amazon%40search.mozilla.org:1.1,ddg%40search.mozilla.org:1.0,qwant%40search.mozilla.org:1.0,wikipedia%40search.mozilla.org:1.0,twitter%40search.mozilla.org:1.0,langpack-fr%40thunderbird.mozilla.org:68.0,wetransfer%40extensions.thunderbird.net:2.0.0
BuildID: 20191001201558
ContentSandboxCapabilities: 119
ContentSandboxCapable: 1
ContentSandboxLevel: 0
CrashTime: 1570225903
EventLoopNestingLevel: 1
FramePoisonBase: 9223372036600930304
FramePoisonSize: 4096
InstallTime: 1570020285
IsWayland: 0
Notes: Ubuntu Eoan Ermine (development
branch)FP(D00-L1000-W-T000) WR? WR- OMTP? OMTP+3
ProductID: {3550f703-e582-4d05-9a08-453d09bdfdc6}
ProductName: Thunderbird
ReleaseChannel: release
SafeMode: 0
SecondsSinceLastCrash: 383
StartupCrash: 0
StartupTime: 1570225565
ThreadIdNameMapping: 20357:"Gecko_IOThread",20358:"JS
Watchdog",20359:"JS Helper",20360:"JS Helper",20361:"JS
Helper",20362:"JS Helper",20363:"Link Monitor",20364:"Socket
Thread",20372:"Timer",20373:"Cache2
I/O",20375:"DataStorage",20376:"Cookie",20379:"GMPThread",20380:"Worker
Launcher",20381:"SoftwareVsyncThread",20382:"Compositor",20383:"ImgDecoder
#1",20384:"ImageIO",20390:"ImageBridgeChild",20391:"IPDL
Background",20392:"DOM Worker",20394:"HTML5
Parser",20397:"StyleThread#1",20396:"StyleThread#0",20398:"StyleThread#2",20401:"mozStorage
#1",20407:"localStorage DB",20408:"ImgDecoder #2",20410:"Cache
I/O",20411:"DNS Resolver #1",20412:"URL Classifier",20413:"Classifier
Update",20415:"QuotaManager IO",20426:"DNS Resolver #2",20427:"DNS
Resolver #3",20429:"ImgDecoder #3",20439:"mozStorage #3",20452:"DOM
Worker",20467:"mozStorage #5",20468:"mozStorage #6",20469:"mozStorage
#7",20479:"DOM Worker",20500:"mozStorage #8",27048:"StreamTrans #18",
Throttleable: 1
UptimeTS: 337.7284093
Vendor:
Version: 68.1.1
useragent_locale: fr
This is what I get when running Thunderbird from the console and after
the crash occurred:
1570277554871 addons.xpi WARNCan't get modified time of
/usr/lib/thunderbird/features/wetrans...@extensions.thunderbird.net
1570277554912 addons.xpi-utilsWARNupdateMetadata: Add-on
wetrans...@extensions.thunderbird.net is invalid: [Exception... "Component
returned failure code: 0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST)
[nsIFile.isFile]" nsresult: "0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST)"
location: "JS frame :: resource://gre/modules/addons/XPIInstall.jsm :: get ::
line 235" data: no] Stack trace:
get()@resource://gre/modules/addons/XPIInstall.jsm:235
syncLoadManifest()@resource://gre/modules/addons/XPIInstall.jsm:745
updateMetadata()@resource://gre/modules/addons/XPIDatabase.jsm:2821
updateExistingAddon()@resource://gre/modules/addons/XPIDatabase.jsm:3036
processFileChanges()@resource://gre/modules/addons/XPIDatabase.jsm:3125
checkForChanges()@resource://gre/modules/addons/XPIProvider.jsm:2946
startup()@resource://gre/modules/addons/XPIProvide
[Desktop-packages] [Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
@esjarc, does the keyboard get disabled when you fold your machines? It does on mine, as it should be. I'm just wondering where the difference comes from -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1
pulseaudio 1:11.1-1ubuntu7.5 with the new dependency was republished in bug #1781428 ** Summary changed: - pulseaudio now depends on libsnapd-glib1 which recommends snapd + pulseaudio now depends on libsnapd-glib1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1856054 Title: pulseaudio now depends on libsnapd-glib1 Status in pulseaudio package in Ubuntu: Won't Fix Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874107] Re: qt theming issue: error 6 in libgdk-x11-2.0.so
** Changed in: gtk+2.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1874107 Title: qt theming issue: error 6 in libgdk-x11-2.0.so Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: As for related bug https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1874102 , theming a qt application with the "gtk2" theme causes the app to crash with segfault: ``` segfault at 114 ip 7f0439c6caa5 sp 7fff05b55770 error 6 in libgdk-x11-2.0.so.0.2400.32[7f0439c36000+5e000] ``` Also the following code is available: ``` Code: 64 24 10 4c 8d 6c 24 40 e8 d8 fe ff ff 31 f6 48 8d 5c 24 38 48 89 c7 31 c0 e8 77 c9 fc ff 31 d2 48 8d 35 0e fe ff ff 48 89 ef 80 14 01 00 00 01 00 00 00 49 89 c7 48 89 a8 d8 00 00 00 e8 12 ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk2.0-0 2.24.32-4ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Apr 21 18:08:47 2020 InstallationDate: Installed on 2020-04-03 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1874107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1781428] Re: please enable snap mediation support
** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1781428 Title: please enable snap mediation support Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Released Status in pulseaudio source package in Bionic: Fix Released Bug description: [Impact] Ubuntu 16.10 added rudimentary snap support to disable audio recording if the connecting process was a snap. By Ubuntu 18.04, something changed in the build resulting in 'Enable Snappy support: no' with audio recording no longer being mediated by pulseaudio (access to the pulseaudio socket continued to be mediated by snapd's apparmor policy). This resulted in any application with the pulseaudio interface connected to be able to also record. Ubuntu 16.04 never had mediation patches and always allowed recording when the pulseaudio interface was connected. To correct this situation but not regress existing behavior, Ubuntu 19.04's pulseaudio was updated patch to allow playback to all connected clients (snaps or not), record by classic snaps (see bug 1787324) and record by strict mode snaps if either the pulseaudio or new-in-snapd-2.41 audio-record interfaces were connected. With this change, snapd is in a position to migrate snaps to the new audio- playback and audio-record interfaces and properly mediate audio recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio- interface-deprecation/13418). The patch to pulseaudio consists of adding a module, enabling it in default.pa and then when it is enabled, pulseaudio when faced with a record operation will, when the connecting process is a snap (ie, its security label (ie, apparmor label) starts with 'snap.'), query snapd via its control socket to ask if the snap is classic and if not, whether the pulseaudio or audio-record interfaces are connected. Adjusting pulseaudio in the manner does not require coordination with any release of snapd. It does need a newer version of snapd-glib, which was recently updated to 1.49 in the last SRU. [Test Case] IMPORTANT: if updating pulseaudio while the session is running, either need to reboot for the test or kill pulseaudio so it can restart with the new snap policy For unconfined applications: $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes For confined, non-snap applications: $ sudo apt-get install evince $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav && echo yes $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes" yes For classic snaps: $ sudo snap install test-snapd-classic-confinement --classic $ snap run --shell test-snapd-classic-confinement $ cat /proc/self/attr/current # verify we are classic confined snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain) $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes $ exit # out of snap run --shell For strict snaps with pulseaudio: $ sudo snap install test-snapd-pulseaudio --edge $ sudo snap connect test-snapd-pulseaudio:pulseaudio $ snap connections test-snapd-pulseaudio Interface Plug Slot Notes pulseaudio test-snapd-pulseaudio:pulseaudio :pulseaudio - $ test-snapd-pulseaudio.play --help # ensure SNAP dirs are created ... $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd- pulseaudio/common/ $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav && echo yes xcb_connection_has_error() returned true yes (note, the xcb_connection_has_error() message is due to the x11 interface not being connected which is unrelated to mediation. x11 is left out to ensure that just audio-playback/audio-record are tested) $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass ... ^Cyes $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes ... yes For strict snaps with audio-playback/audio-record: $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04 $ sudo snap install test-snapd-audio-record --edge $ snap connections test-snapd-audio-record # record not connected Interface PlugSlot Notes audio-playback test-snapd-audio-record:audio-playback :audio-playback - audio-record
[Desktop-packages] [Bug 1778317] Re: Owncloud always ask for password at startup
** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1778317 Title: Owncloud always ask for password at startup Status in gnome-shell-extension-appindicator package in Ubuntu: Incomplete Bug description: At startup, ownCloud client always ask for password with the following message: Please enter ownCloud password: User: Account: x...@xxx.xx Click here to request an app password from the web interface. Reading from keychain failed with error: 'No keychain service available' I think ownCloud can't get password from gnome-keyring or something like this... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1778317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1780709] Re: Boot duration is very long
** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1780709 Title: Boot duration is very long Status in gnome-shell-extension-appindicator package in Ubuntu: Incomplete Bug description: When my laptop starts, it took a very long time. I CTRL-F2, and I discovered the following message: "a start job is running for snappy daemon" Boot sequence seems to be stuck up a long time with this deamon. I'm using Ubuntu 18.04 LTS always up to date. My laptop is a HP Elitebook 8470p To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1780709/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
This bug was fixed in the package nvidia-graphics-drivers-440 - 440.82+really.440.64-0ubuntu5 --- nvidia-graphics-drivers-440 (440.82+really.440.64-0ubuntu5) focal; urgency=medium * Reverse the order of the versions of nvidia-dkms-440 in the dependency list, so that apt will default to the real package instead of picking an lrm package at "random" which won't necessarily match the target kernel. LP: #1873867. -- Steve Langasek Tue, 21 Apr 2020 08:17:20 -0700 ** Changed in: nvidia-graphics-drivers-440 (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Committed Status in linux source package in Focal: Incomplete Status in nvidia-graphics-drivers-440 source package in Focal: Fix Released Status in ubiquity source package in Focal: Confirmed Status in ubuntu-drivers-common source package in Focal: Confirmed Status in ubuntu-meta source package in Focal: Fix Committed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874120] [NEW] package chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error
Public bug reported: error appeared when opening chrome ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAEaTDjAQEBAQkXAQOAMBt47umEpVVImyYSUFQBAQEBAQEBAQEBAQEBAQEBAjqAGHE4LUBYLEUA3w0RAAAe/QAwTBhkCgAKICAgICAg/ABFVDIyMjFJCiAgICAg/wBBU1VTMjAxMzAzMDEKAEI= modes: 1920x1080 DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: Date: Tue Apr 21 23:33:33 2020 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-03-28 (1851 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Load-Avg-1min: 3.38 Load-Processes-Running-Percent: 0.2% MachineType: ASUSTeK COMPUTER INC. ET2221I-B85 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=e54296a0-874c-412b-9fc6-092c89bdfa74 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-04-21 (0 days ago) dmi.bios.date: 11/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: ET2221I-B85 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0503:bd11/05/2013:svnASUSTeKCOMPUTERINC.:pnET2221I-B85:pvr0503:rvnASUSTeKCOMPUTERINC.:rnET2221I-B85:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: All-In-One dmi.product.name: ET2221I-B85 dmi.product.version: 0503 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1874120 Title: package chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: New Bug description: error appeared when opening chrome ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAEaTDjAQEBAQkXAQOAMBt47umEpVVImyYSUFQBAQEBAQEBAQEBAQEBAQEBAjqAGHE4LUBYLEUA3w0RAAAe/QAwTBhkCgAKICAgICAg/ABFVDIyMjFJCiAgICAg/wBBU1VTMjAxMzAzMDEKAEI= modes: 1920x1080 DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: Date: Tue Apr 21 23:33:33 2020 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-03-28 (1851 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Load-Avg-1min: 3.38 Load-Processes-Running-Percent: 0.2% MachineType: ASUSTeK COMPUTER INC. ET2221I-B85 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=e54296a0-874c-412b-9fc6-092c89bdfa74 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-04-21
[Desktop-packages] [Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
>From the upstream bug report (https://gitlab.gnome.org/GNOME/gnome- control-center/-/issues/401), there's an even simpler way to reproduce: $ gnome-control-center info-overview $ gnome-control-center online-accounts add google ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #401 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/401 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/401 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: In Progress Bug description: problem with Ubuntu software centre ver.3.35.2 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.90-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 10 00:28:42 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-06 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x55db27c2df87 : mov 0x3f8(%rax),%rax PC (0x55db27c2df87) ok source "0x3f8(%rax)" (0x03f8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: cc_panel_get_title_widget () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1862553/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872917] Re: Laptop does not recognize it's charging
Found out that my laptops charging port is (partially) broken and will be changed by guarantee. The laptop is actually charging but with a extremely low power, that's why it shows such long batery lifetimes. This bug can be closed. Windows reported discharging state, too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1872917 Title: Laptop does not recognize it's charging Status in upower package in Ubuntu: Incomplete Bug description: I'm using a pretty new Lenovo Thinkpad X1 Extreme G2. Since a few days, the laptop does not recognize that its charging all the time. It's showing the battery icon and a percent number. This must be broken a couple of days or weeks ago, this was working when I installed Ubuntu 19.10. It does not depend from dock or directly connecting the AC adapter. Incredibly long battery life time is shown, see screenshot. (laptop was connected to AC during this) This is a problem because for example firmware upgrades does not work because they require "AC-connected state". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1872917/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874112] [NEW] gdm conffile prompt during bionic to focal upgrade
Public bug reported: Doing some test upgrade, doing a new bionic install (autologin enabled from the installer) and upgrading, switching to focal directly without using it, the upgrade displays that config file change prompt --- /etc/gdm3/custom.conf 2020-04-21 17:30:22.379041984 +0200 +++ /etc/gdm3/custom.conf.dpkg-new 2019-10-07 18:23:07.0 +0200 @@ -3,13 +3,12 @@ # See /usr/share/gdm/gdm.schemas for a list of available options. [daemon] -AutomaticLoginEnable=true -AutomaticLogin=ubuntu - -# Uncoment the line below to force the login screen to use Xorg +# Uncomment the line below to force the login screen to use Xorg #WaylandEnable=false # Enabling automatic login +# AutomaticLoginEnable = true +# AutomaticLogin = user1 # Enabling timed login # TimedLoginEnable = true ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: iso-testing ** Tags added: iso-testing ** Description changed: - Doing some test upgrade, doing a new bionic install and upgrading, - switching to focal directly without using it, the upgrade displays that - config file change prompt + Doing some test upgrade, doing a new bionic install (autologin enabled + from the installer) and upgrading, switching to focal directly without + using it, the upgrade displays that config file change prompt --- /etc/gdm3/custom.conf 2020-04-21 17:30:22.379041984 +0200 +++ /etc/gdm3/custom.conf.dpkg-new2019-10-07 18:23:07.0 +0200 @@ -3,13 +3,12 @@ - # See /usr/share/gdm/gdm.schemas for a list of available options. - - [daemon] + # See /usr/share/gdm/gdm.schemas for a list of available options. + + [daemon] -AutomaticLoginEnable=true -AutomaticLogin=ubuntu - -# Uncoment the line below to force the login screen to use Xorg +# Uncomment the line below to force the login screen to use Xorg - #WaylandEnable=false - - # Enabling automatic login + #WaylandEnable=false + + # Enabling automatic login +# AutomaticLoginEnable = true +# AutomaticLogin = user1 - - # Enabling timed login - # TimedLoginEnable = true + + # Enabling timed login + # TimedLoginEnable = true -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1874112 Title: gdm conffile prompt during bionic to focal upgrade Status in gdm3 package in Ubuntu: New Bug description: Doing some test upgrade, doing a new bionic install (autologin enabled from the installer) and upgrading, switching to focal directly without using it, the upgrade displays that config file change prompt --- /etc/gdm3/custom.conf 2020-04-21 17:30:22.379041984 +0200 +++ /etc/gdm3/custom.conf.dpkg-new2019-10-07 18:23:07.0 +0200 @@ -3,13 +3,12 @@ # See /usr/share/gdm/gdm.schemas for a list of available options. [daemon] -AutomaticLoginEnable=true -AutomaticLogin=ubuntu - -# Uncoment the line below to force the login screen to use Xorg +# Uncomment the line below to force the login screen to use Xorg #WaylandEnable=false # Enabling automatic login +# AutomaticLoginEnable = true +# AutomaticLogin = user1 # Enabling timed login # TimedLoginEnable = true To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1874112/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874003] Re: cant log into network
Some more info can be found in this bug https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1873997 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1874003 Title: cant log into network Status in network-manager package in Ubuntu: Incomplete Bug description: Running Ubuntu Mate 20.04 2020-04-20 ISO live session, sometimes i'm not able to log into detected wireless networks. See screenshot for error message. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: MATE Date: Tue Apr 21 05:29:48 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d IpRoute: LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200420) ProcEnviron: SHELL=/bin/bash LANG=C.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Wired connection 1 c072d14c-3f17-3a1d-9679-9929ecc4d6cb ethernet 0 never yes -999 no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- /run/NetworkManager/system-connections/Wired connection 1.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- ---- enp4s0 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- ---- 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.22.10 disconnected started none enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1874003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874109] Re: No permission to access directory on storage device
** Package changed: ubuntu => udisks2 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1874109 Title: No permission to access directory on storage device Status in udisks2 package in Ubuntu: New Bug description: I try to mkdir new directory but always error mkdir: cannot create directory ‘test’: Read-only file system. I try to use chmod but still error, I check with ls command show drwxrwxrwx. please help. thank you. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: udisks2 2.8.4-1 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 70-snap.gitkraken.rules 70-snap.insomnia.rules 70-snap.whatsdesk.rules 70-snap.spotify.rules 70-snap.mpv.rules Date: Tue Apr 21 22:21:27 2020 InstallationDate: Installed on 2020-02-03 (77 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: AXIOO NEON RNW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=5afe1fee-ebd1-4a05-9bd1-fdebb1113820 ro quiet splash vt.handoff=7 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: NEON RNW dmi.board.vendor: AXIOO dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/05/2013:svnAXIOO:pnNEONRNW:pvrNotApplicable:rvnAXIOO:rnNEONRNW:rvrV3.0:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NEON RNW dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: AXIOO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1874109/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874109] [NEW] No permission to access directory on storage device
You have been subscribed to a public bug: I try to mkdir new directory but always error mkdir: cannot create directory ‘test’: Read-only file system. I try to use chmod but still error, I check with ls command show drwxrwxrwx. please help. thank you. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: udisks2 2.8.4-1 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 70-snap.gitkraken.rules 70-snap.insomnia.rules 70-snap.whatsdesk.rules 70-snap.spotify.rules 70-snap.mpv.rules Date: Tue Apr 21 22:21:27 2020 InstallationDate: Installed on 2020-02-03 (77 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: AXIOO NEON RNW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=5afe1fee-ebd1-4a05-9bd1-fdebb1113820 ro quiet splash vt.handoff=7 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: NEON RNW dmi.board.vendor: AXIOO dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/05/2013:svnAXIOO:pnNEONRNW:pvrNotApplicable:rvnAXIOO:rnNEONRNW:rvrV3.0:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NEON RNW dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: AXIOO ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- No permission to access directory on storage device https://bugs.launchpad.net/bugs/1874109 You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870270] Re: gnome-shell crashed with SIGSEGV in dri_flush_front_buffer() from intel_flush_front() from intel_glFlush()
This may be related to this bug I filed on CentOS. https://bugs.centos.org/view.php?id=17275 I can reproduce my crash consistently. ** Bug watch added: bugs.centos.org/ #17275 https://bugs.centos.org/view.php?id=17275 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870270 Title: gnome-shell crashed with SIGSEGV in dri_flush_front_buffer() from intel_flush_front() from intel_glFlush() Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Incomplete Status in gnome-shell source package in Eoan: Fix Released Status in gnome-shell source package in Focal: Fix Released Bug description: [Impact] gnome-shell crashes a lot on bionic: https://errors.ubuntu.com/problem/3841a5bc586bc3f532d2313a35f51e511772751f [Test Case] ** Someone who can reproduce the crash please fill this in ** [Regression Potential] Low. The same fix has been released to newer versions already for most of a year. [Other Info] gnome shell crashed / froze while switching keyboard layouts. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.13 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Mar 31 22:47:45 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1571973788 InstallationDate: Installed on 2020-03-13 (19 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /var/lib/gdm3 SegvAnalysis: Segfault happened at: 0x7fedbfa22393:jmpq *%rax PC (0x7fedbfa22393) ok source "*%rax" (0xfffaffed90151620) not located in a known VMA region (needed readable region)! SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgbm.so.1 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
I'm attaching a simple python script that automates the reproduction of the bug: 1) In a terminal window, run "gnome-control-center info-overview" 2) In another terminal window, run the attached script 3) Observe how the gnome-control-center process crashed in the first terminal window ** Attachment added: "launch-gcc-oa-add-ubuntu-sso.py" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862553/+attachment/5357631/+files/launch-gcc-oa-add-ubuntu-sso.py -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() Status in gnome-control-center package in Ubuntu: In Progress Bug description: problem with Ubuntu software centre ver.3.35.2 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.90-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 10 00:28:42 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-06 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x55db27c2df87 : mov 0x3f8(%rax),%rax PC (0x55db27c2df87) ok source "0x3f8(%rax)" (0x03f8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: cc_panel_get_title_widget () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862553/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubiquity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: In Progress Status in ubiquity package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Committed Status in linux source package in Focal: Incomplete Status in nvidia-graphics-drivers-440 source package in Focal: In Progress Status in ubiquity source package in Focal: Confirmed Status in ubuntu-drivers-common source package in Focal: Confirmed Status in ubuntu-meta source package in Focal: Fix Committed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
This was originally worked around by https://gitlab.gnome.org/GNOME /gnome-control-center/-/commit/f5d601d3b023e6d869f40415e1e31aebfb7b1d01, but for some reason this workaround is no longer working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() Status in gnome-control-center package in Ubuntu: In Progress Bug description: problem with Ubuntu software centre ver.3.35.2 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.90-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 10 00:28:42 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-06 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x55db27c2df87 : mov 0x3f8(%rax),%rax PC (0x55db27c2df87) ok source "0x3f8(%rax)" (0x03f8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: cc_panel_get_title_widget () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862553/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1756837] Re: Dock doesn't show badge count, if new notifications arrived when screen locked
It' is really fixed? Just tested on Ubuntu 20.04 RC, package gnome- shell-extension-ubuntu-dock 67ubuntu20.04.5 and doesn't see any difference. Badges still disappear after screen lock. Tested with Telegram. Thunderbird since version 68 (not sure exactly) does not use badges anymore. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1756837 Title: Dock doesn't show badge count, if new notifications arrived when screen locked Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Gnome Shell disables extensions on screen lock. If, for example, new mail will arrived in Thunderbird during screen locked, no badges will be shown on unlock. Also, lock/unlock screen while badges displayed will clear them. So, in current implementation, badges looks very unreliable to rely on them, and looks more a mess than a feature. Solution may be adding a user space daemon, which interact with applications even when dock extension is disabled, and provide badges information for dock. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 12:11:45 2018 PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to bionic on 2017-10-24 (145 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1756837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871913] Re: super key does not work with secondary keyboard layout
xev for primary layout: KeymapNotify event, serial 38, synthetic NO, window 0x0, keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 FocusOut event, serial 38, synthetic NO, window 0x4e1, mode NotifyGrab, detail NotifyNonlinear FocusIn event, serial 38, synthetic NO, window 0x4e1, mode NotifyUngrab, detail NotifyNonlinear --- xev for secondary layout: KeymapNotify event, serial 38, synthetic NO, window 0x0, keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 FocusOut event, serial 38, synthetic NO, window 0x4e1, mode NotifyGrab, detail NotifyAncestor FocusIn event, serial 38, synthetic NO, window 0x4e1, mode NotifyUngrab, detail NotifyAncestor what is the difference between NotifyNonlinear and NotifyAncestor? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871913 Title: super key does not work with secondary keyboard layout Status in budgie-desktop package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When keyboard layout is set on Persian, pressing Super does not open Activities overview. It just works when the input is set on English. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:02:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (159 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1871913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
nvidia-driver-440 also currently has this dependency: nvidia-dkms-440 (= 440.64-0ubuntu3) | nvidia-dkms-440 (= 440.82+really.440.64-0ubuntu4) The first branch is satisfied by the lrm packages and the second branch is satisfied by the real nvidia-dkms-440 package, which means that apt install nvidia will always select some lrm provider but not necessarily the one that matches your kernel. We should reverse this order so that apt picks the "safe" default of the real nvidia-dkms package. This will become obsolete with the next upload of nvidia, since the real and virtual package versions will again line up. ** Also affects: ubuntu-meta (Ubuntu Focal) Importance: Undecided Status: Fix Committed ** Also affects: ubiquity (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: Incomplete ** Also affects: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided Assignee: Alberto Milone (albertomilone) Status: Confirmed ** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-440 (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: In Progress Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Committed Status in linux source package in Focal: Incomplete Status in nvidia-graphics-drivers-440 source package in Focal: In Progress Status in ubiquity source package in Focal: New Status in ubuntu-drivers-common source package in Focal: Confirmed Status in ubuntu-meta source package in Focal: Fix Committed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874107] Re: qt theming issue: error 6 in libgdk-x11-2.0.so
# Symple application failing
import sys
from PySide2.QtWidgets import QApplication, QDialog, QLineEdit, QPushButton
class Form(QDialog):
def __init__(self, parent=None):
super(Form, self).__init__(parent)
self.setWindowTitle("My Form")
if __name__ == '__main__':
# Create the Qt Application
app = QApplication(sys.argv)
app.setStyle('gtk2')
# Create and show the form
form = Form()
form.show()
# Run the main Qt loop
sys.exit(app.exec_())
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1874107
Title:
qt theming issue: error 6 in libgdk-x11-2.0.so
Status in gtk+2.0 package in Ubuntu:
New
Bug description:
As for related bug
https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1874102 ,
theming a qt application with the "gtk2" theme causes the app to crash with
segfault:
```
segfault at 114 ip 7f0439c6caa5 sp 7fff05b55770 error 6 in
libgdk-x11-2.0.so.0.2400.32[7f0439c36000+5e000]
```
Also the following code is available:
```
Code: 64 24 10 4c 8d 6c 24 40 e8 d8 fe ff ff 31 f6 48 8d 5c 24 38 48 89 c7 31
c0 e8 77 c9 fc ff 31 d2 48 8d 35 0e fe ff ff 48 89 ef 80 14 01 00 00 01 00
00 00 49 89 c7 48 89 a8 d8 00 00 00 e8 12
```
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libgtk2.0-0 2.24.32-4ubuntu4
ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
Uname: Linux 5.4.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Tue Apr 21 18:08:47 2020
InstallationDate: Installed on 2020-04-03 (17 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
SourcePackage: gtk+2.0
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1874107/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874107] Re: qt theming issue: error 6 in libgdk-x11-2.0.so
You need the following packages to run the script: sudo apt install libpyside2-py3-5.14 python3-pyside2.qtcore python3-pyside2.qtuitools python3-pyside2.qtwidgets qt5-style-plugins qt5-gtk2-platformtheme -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1874107 Title: qt theming issue: error 6 in libgdk-x11-2.0.so Status in gtk+2.0 package in Ubuntu: New Bug description: As for related bug https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1874102 , theming a qt application with the "gtk2" theme causes the app to crash with segfault: ``` segfault at 114 ip 7f0439c6caa5 sp 7fff05b55770 error 6 in libgdk-x11-2.0.so.0.2400.32[7f0439c36000+5e000] ``` Also the following code is available: ``` Code: 64 24 10 4c 8d 6c 24 40 e8 d8 fe ff ff 31 f6 48 8d 5c 24 38 48 89 c7 31 c0 e8 77 c9 fc ff 31 d2 48 8d 35 0e fe ff ff 48 89 ef 80 14 01 00 00 01 00 00 00 49 89 c7 48 89 a8 d8 00 00 00 e8 12 ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk2.0-0 2.24.32-4ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Apr 21 18:08:47 2020 InstallationDate: Installed on 2020-04-03 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1874107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874107] [NEW] qt theming issue: error 6 in libgdk-x11-2.0.so
Public bug reported: As for related bug https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1874102 , theming a qt application with the "gtk2" theme causes the app to crash with segfault: ``` segfault at 114 ip 7f0439c6caa5 sp 7fff05b55770 error 6 in libgdk-x11-2.0.so.0.2400.32[7f0439c36000+5e000] ``` Also the following code is available: ``` Code: 64 24 10 4c 8d 6c 24 40 e8 d8 fe ff ff 31 f6 48 8d 5c 24 38 48 89 c7 31 c0 e8 77 c9 fc ff 31 d2 48 8d 35 0e fe ff ff 48 89 ef 80 14 01 00 00 01 00 00 00 49 89 c7 48 89 a8 d8 00 00 00 e8 12 ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk2.0-0 2.24.32-4ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Apr 21 18:08:47 2020 InstallationDate: Installed on 2020-04-03 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1874107 Title: qt theming issue: error 6 in libgdk-x11-2.0.so Status in gtk+2.0 package in Ubuntu: New Bug description: As for related bug https://bugs.launchpad.net/ubuntu/+source/qtstyleplugins-src/+bug/1874102 , theming a qt application with the "gtk2" theme causes the app to crash with segfault: ``` segfault at 114 ip 7f0439c6caa5 sp 7fff05b55770 error 6 in libgdk-x11-2.0.so.0.2400.32[7f0439c36000+5e000] ``` Also the following code is available: ``` Code: 64 24 10 4c 8d 6c 24 40 e8 d8 fe ff ff 31 f6 48 8d 5c 24 38 48 89 c7 31 c0 e8 77 c9 fc ff 31 d2 48 8d 35 0e fe ff ff 48 89 ef 80 14 01 00 00 01 00 00 00 49 89 c7 48 89 a8 d8 00 00 00 e8 12 ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk2.0-0 2.24.32-4ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Apr 21 18:08:47 2020 InstallationDate: Installed on 2020-04-03 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1874107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861609] Re: [focal] Xorg crashed with assertion failure (usually in a VM) at [privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from
I reinstall focal from scratch and the issue is gone. ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1861609 Title: [focal] Xorg crashed with assertion failure (usually in a VM) at [privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRIMoveBuffersHelper Status in xorg-server package in Ubuntu: Fix Released Bug description: Xorg crashed with assertion failure (usually in a VM): privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. and call stack comes from DRIMoveBuffersHelper WORKAROUND Select 'Ubuntu on Wayland' on the login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1861609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
The crash is caused by the GOA panel being disposed prematurely, in get_all_providers_cb: user_data (the panel) is being g_autoptr'd, and as a consequence it is destroyed when exiting the scope of the callback. This appears to be an unwanted regression/side effect of https://gitlab.gnome.org/GNOME/gnome-control- center/-/commit/5579314a38aa3aa26e8f833661fe898d31f327f7. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() Status in gnome-control-center package in Ubuntu: In Progress Bug description: problem with Ubuntu software centre ver.3.35.2 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.90-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 10 00:28:42 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-06 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x55db27c2df87 : mov 0x3f8(%rax),%rax PC (0x55db27c2df87) ok source "0x3f8(%rax)" (0x03f8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: cc_panel_get_title_widget () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862553/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819375] Re: Unable to launch applications from Nautilus by visiting /usr/share/applications and clicking on icon of application
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1819375 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1819375 Title: Unable to launch applications from Nautilus by visiting /usr/share/applications and clicking on icon of application Status in nautilus package in Ubuntu: Opinion Bug description: Steps to reproduce: 1. Install Ubuntu 19.04 2. Open Nautilus 3. Navigate to /usr/share/applications 4. Try to click on some application icon to launch it Expected results: 1. Application icons are shown 2. User can launch application by clicking on its icon Actual results: 1. Application icons are not shown 2. The *.desktop file is opened in Gedit instead of launching. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.31.90-1ubuntu2 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Mar 10 23:22:33 2019 GsettingsChanges: SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1819375/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873582] Re: Unable to launch applications by clicking on desktop-files inside /usr/share/applications
*** This bug is a duplicate of bug 1819375 *** https://bugs.launchpad.net/bugs/1819375 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1873582 Title: Unable to launch applications by clicking on desktop-files inside /usr/share/applications Status in nautilus package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 20.04 LTS 2. Open Nautilus 3. Navigate to /usr/share/applications 4. Click on any desktop-file Expected results: * Nautilus launched the application from selected desktop-file Actual results: * Nautilus opened desktop-file in the text editor, the application is not launched ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sat Apr 18 20:32:33 2020 GsettingsChanges: b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type', 'RabbitVCS::age_column', 'RabbitVCS::author_column', 'RabbitVCS::revision_column', 'RabbitVCS::status_column']" SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1873582/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873582] Re: Unable to launch applications by clicking on desktop-files inside /usr/share/applications
*** This bug is a duplicate of bug 1819375 *** https://bugs.launchpad.net/bugs/1819375 ** This bug has been marked a duplicate of bug 1819375 Unable to launch applications from Nautilus by visiting /usr/share/applications and clicking on icon of application -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1873582 Title: Unable to launch applications by clicking on desktop-files inside /usr/share/applications Status in nautilus package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 20.04 LTS 2. Open Nautilus 3. Navigate to /usr/share/applications 4. Click on any desktop-file Expected results: * Nautilus launched the application from selected desktop-file Actual results: * Nautilus opened desktop-file in the text editor, the application is not launched ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sat Apr 18 20:32:33 2020 GsettingsChanges: b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type', 'RabbitVCS::age_column', 'RabbitVCS::author_column', 'RabbitVCS::revision_column', 'RabbitVCS::status_column']" SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1873582/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
And then people are surprised why Linux community is no negative to Snap. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865824] Re: Upgrade to 20.04 removes saved fingerprints
** Also affects: ubuntu-release-notes Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1865824 Title: Upgrade to 20.04 removes saved fingerprints Status in Release Notes for Ubuntu: New Status in fprintd package in Ubuntu: Confirmed Bug description: 18.04 Ubuntu MATE upgraded to 20.04 Ubuntu MATE on 2 March 2020. T430N Upgrade competes and reboots. Upon reboot login screen appears and there is no prompt to login using fingerprint scanner. After login using password the user needs to: run fprintd-enroll and fingerprints are enrolled. On logout/reboot login using fingerprint scanner is available. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fprintd 1.90.1-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: MATE Date: Mon Mar 2 22:21:29 2020 InstallationDate: Installed on 2019-12-05 (88 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: fprintd UpgradeStatus: Upgraded to focal on 2020-03-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1865824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
Thank you for this extra information. This allowed to narrow down the bug you experienced to a simplified, shorter bug scenario. I was suspecting that this may not be the same bug. > It's not necessary to actually log in as the other user. The bug discussed here only happens when the user is already logged in. May I suggest that you open a new bug report with details of a minimal reproducible case? Thank you for your attention. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: Confirmed Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874091] [NEW] ubuntu-release-upgrader should use ubuntu-drivers and migrate people from nvidia-dkms to l-r-m
Public bug reported: ubuntu-release-upgrader should use ubuntu-drivers and migrate people from nvidia-dkms to l-r-m. ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu) Milestone: None => ubuntu-20.04.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1874091 Title: ubuntu-release-upgrader should use ubuntu-drivers and migrate people from nvidia-dkms to l-r-m Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: ubuntu-release-upgrader should use ubuntu-drivers and migrate people from nvidia-dkms to l-r-m. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1874091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873658] Re: Deb Files are not associated with an application that manages packages
** Summary changed: - Deb Files are not opened by the installer 20.04 + Deb Files are not associated with an application that manages packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Invalid Bug description: When you download a DEB file within 20.04 Ubuntu Beta and you double click it the file is opened by the archive manager. I would expect the installer to open the file just like in previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
The situation isn't clear but from the current report we decided it's not a rls target atm ** Tags removed: champagne ** Tags added: rls-ff-notfixing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: When the nvidia driver is installed, the screen turns off when trying to set some fractional scaling values like 150%. And it stays off even after rebooting and logging in again. And from ssh I can see there's no current mode set anymore (just like in bug 1869750): $ xrandr Screen 0: minimum 8 x 8, current 960 x 600, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 connected primary (normal left inverted right x axis y axis) 1920x1200 59.95 + 59.88 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 17 15:51:15 2020 InstallationDate: Installed on 2020-02-03 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873658] Re: Deb Files are not opened by the installer 20.04
** Changed in: gdebi (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Invalid Bug description: When you download a DEB file within 20.04 Ubuntu Beta and you double click it the file is opened by the archive manager. I would expect the installer to open the file just like in previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
** Merge proposal linked: https://code.launchpad.net/~ubuntu-installer/ubiquity/+git/ubiquity/+merge/382677 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861609] Re: [focal] Xorg crashed with assertion failure (usually in a VM) at [privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from
The issue got no recent duplicate, could it be fixed with the newest xorg? is anyone still seing the issue? ** Tags removed: rls-ff-incoming ** Tags added: rls-ff-notfixing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1861609 Title: [focal] Xorg crashed with assertion failure (usually in a VM) at [privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRIMoveBuffersHelper Status in xorg-server package in Ubuntu: Confirmed Bug description: Xorg crashed with assertion failure (usually in a VM): privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. and call stack comes from DRIMoveBuffersHelper WORKAROUND Select 'Ubuntu on Wayland' on the login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1861609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861609] Re: [focal] Xorg crashed with assertion failure (usually in a VM) at [privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from
tagging rls-ff-notfixing for now since it's not clear it's still an issue -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1861609 Title: [focal] Xorg crashed with assertion failure (usually in a VM) at [privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRIMoveBuffersHelper Status in xorg-server package in Ubuntu: Confirmed Bug description: Xorg crashed with assertion failure (usually in a VM): privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. and call stack comes from DRIMoveBuffersHelper WORKAROUND Select 'Ubuntu on Wayland' on the login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1861609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869086] Re: Firmware upgrade always notifies to reboot the device even on immediate failure
** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1869086 Title: Firmware upgrade always notifies to reboot the device even on immediate failure Status in snap-store: Triaged Status in gnome-software package in Ubuntu: Triaged Status in gnome-software source package in Focal: Triaged Bug description: If the firmware update request fails because of a network error or because the AC power is not plugged, or any other problem, gnome- software shows an error in an in-app notification, while sends a resident notification to gnome-shell that requests the user to restart the system, even if this is not really required. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1869086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873658] Re: Deb Files are not opened by the installer 20.04
** Changed in: desktop-file-utils (Ubuntu) Assignee: (unassigned) => Ken VanDine (ken-vandine) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not opened by the installer 20.04 Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Bug description: When you download a DEB file within 20.04 Ubuntu Beta and you double click it the file is opened by the archive manager. I would expect the installer to open the file just like in previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873658] Re: Deb Files are not opened by the installer 20.04
** Also affects: desktop-file-utils (Ubuntu) Importance: Undecided Status: New ** Changed in: desktop-file-utils (Ubuntu) Status: New => Confirmed ** Changed in: desktop-file-utils (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not opened by the installer 20.04 Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Bug description: When you download a DEB file within 20.04 Ubuntu Beta and you double click it the file is opened by the archive manager. I would expect the installer to open the file just like in previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872715] Re: 5.1 audio does not work properly [To Be Filled By O.E.M., Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] Playback problem
** Description changed: Hello, I am using Ubuntu 19.10 with 5.1 surround speakers. I tried to configure 5.1 surround, but it still doesn't work. I also installed Pulse audio. Here is the info about my soundcard: # aplay -l Lista PLAYBACK de dispozitive placa 0: PCH [HDA Intel PCH], dispozitiv 0: ALC892 Analog [ALC892 Analog] - subdispozitive: 0/1 - Subdispozitiv #0: subdevice #0 + subdispozitive: 0/1 + Subdispozitiv #0: subdevice #0 placa 1: NVidia [HDA NVidia], dispozitiv 3: HDMI 0 [HDMI 0] - subdispozitive: 1/1 - Subdispozitiv #0: subdevice #0 + subdispozitive: 1/1 + Subdispozitiv #0: subdevice #0 placa 1: NVidia [HDA NVidia], dispozitiv 7: HDMI 1 [HDMI 1] - subdispozitive: 1/1 - Subdispozitiv #0: subdevice #0 + subdispozitive: 1/1 + Subdispozitiv #0: subdevice #0 placa 1: NVidia [HDA NVidia], dispozitiv 8: HDMI 2 [HDMI 2] - subdispozitive: 1/1 - Subdispozitiv #0: subdevice #0 + subdispozitive: 1/1 + Subdispozitiv #0: subdevice #0 placa 1: NVidia [HDA NVidia], dispozitiv 9: HDMI 3 [HDMI 3] - subdispozitive: 1/1 - Subdispozitiv #0: subdevice #0 + subdispozitive: 1/1 + Subdispozitiv #0: subdevice #0 See 'lscpi -v' output attached. - $ speaker-test -c6 -l1 -twav speaker-test 1.1.9 Playback device is default Stream parameters are 48000Hz, S16_LE, 6 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 32 to 349525 Period size range from 10 to 116509 Using max buffer size 349524 Periods = 4 was set period_size = 87381 was set buffer_size = 349524 - 0 - Față stânga - 4 - Centru - 1 - Față dreapta - 3 - Spate dreapta - 2 - Spate stânga - 5 - LFE + 0 - Față stânga + 4 - Centru + 1 - Față dreapta + 3 - Spate dreapta + 2 - Spate stânga + 5 - LFE Timp per Perioada = 8,733519 - - I tried the test below and instead of center speaker, right speaker plays two times and the subwoofer do not work at all. + I tried the test below and instead of center speaker, right speaker + plays two times and the subwoofer do not work at all. Please let me know what other details you need. Thank you! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: lucian 1257 F pulseaudio - /dev/snd/controlC0: lucian 1257 F pulseaudio - /dev/snd/pcmC0D0p: lucian 1257 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: lucian 1257 F pulseaudio + /dev/snd/controlC0: lucian 1257 F pulseaudio + /dev/snd/pcmC0D0p: lucian 1257 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 16:46:45 2020 InstallationDate: Installed on 2019-03-30 (380 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=ro_RO.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=ro_RO.UTF-8 + SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: Only some of outputs are working Title: [To Be Filled By O.E.M., Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.30 dmi.board.name: B150 Pro4/3.1 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.30:bd11/21/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150Pro4/3.1:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-17T14:42:34.178435 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1872715 Title: 5.1 audio does not work properly [To Be Filled By O.E.M., Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: Hello
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04
I am on a Ubuntu 20.04 with mutter 3.36.1 and this bug still affects me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 Status in LibreOffice: Confirmed Status in Mutter: Fix Released Status in codeblocks package in Ubuntu: Confirmed Status in codelite package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in codeblocks source package in Eoan: Confirmed Status in codelite source package in Eoan: Confirmed Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Status in codeblocks source package in Focal: Confirmed Status in codelite source package in Focal: Confirmed Status in libreoffice source package in Focal: Triaged Status in mutter source package in Focal: Fix Released Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
The default value was 0 minutes. I set it to one minute and it made no difference. Incidentally, it seems that clicking on the "Switch user" button is enough to trigger the problem. I did this because I couldn't remember whether or not I'd added another user (I hadn't at that point). It's not necessary to actually log in as the other user. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: Confirmed Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
** Changed in: pulseaudio (Ubuntu) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1532226] Re: No menu bar in gtk apps on fresh boot
it is possible to get all menu/s back by: sudo apt purge .\*bamf.\* and restart window manager. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1532226 Title: No menu bar in gtk apps on fresh boot Status in BAMF: New Status in Release Notes for Ubuntu: Fix Released Status in bamf package in Ubuntu: Fix Released Status in bamf source package in Xenial: Fix Released Bug description: Seen here in fresh 16.04 install using 01/07/16 image. Around 35% of fresh boots or restarts results in no menus in unity panel for most apps, notable exceptions are firefox & thunderbird A log out/in restores functionality. When this occurs there is nothing in any of the ~/.cache/upstart logs of obvious note Test case: fresh install, no changes Do a number of restarts from system settings, using either restart > restart or shutdown > restart, here randomly picked one or the other What happens here: around 35% of the time the login has no menus in the unity panel for most apps. To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1532226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866841] Re: [SRU] Move gnome-shell-extension-prefs to universe and add chrome-gnome-shell to its recommends
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866841 Title: [SRU] Move gnome-shell-extension-prefs to universe and add chrome- gnome-shell to its recommends Status in gnome-shell package in Ubuntu: In Progress Bug description: [Impact] * Since GNOME 3.36, Shell Extensions can no longer be installed using GNOME Software (Ubuntu Software), instead there was a new Extensions (gnome-shell-extension-prefs) application prepared to replace this functionality. However, this application itself does not support installing new extensions, instead, it opens a web browser with a extensions.gnome.org website that allows browsing and installing new extensions. This website depends on a chrome-gnome-shell package that provides GNOME Shell integration (connector) for Firefox, Chrome, Chromium and other web browsers for this functionality. Without this connector, it is not possible to install Shell Extensions on Ubuntu 20.04. * In this SRU, I want to propose adding this chrome-gnome-shell package to recommends of the gnome-shell-extension-prefs package. However, since the gnome-shell-extension-prefs package is in a main repository and chrome-gnome-shell is in universe, it would be probably also needed to first move the gnome-shell-extension-prefs package to universe. [Test Case] * Install the "gnome-shell-extension-prefs" (Extensions) application. * Open the "Extensions" application, click the "i" button in the window header, click the "extensions.gnome.org" link. * In the web browser window, click on link inside the blue notification on extensions.gnome.org to install a browser extension (frontend for the connector), then refresh the page. * After this, a red notification appears on the web page telling the user that host connector is not running. [Regression Potential] * Without the chrome-gnome-shell package installed, it is not possible to install Shell Extensions on Ubuntu 20.04. [Other Info] * More information: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
Hi Jane @irihapeti. Thank you for reporting. The settings "delay locking after screensaver for..." that was in "Power Manager" settings, tab "Security" may correspond to what exists in 20.04 in "Screensaver" settings, tab "Lock Screen", and renamed to "Lock the screen after the screen saver is active for..." Can you report the current value? (presumably zero) And set it to one minute to see if it fixes your problem? Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: Confirmed Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia
** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873867 Title: ubuntu-drivers changes kernel flavour when installing nvidia Status in linux package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: $ dpkg-query -W linux-image-* linux-image-5.4.0-25-generic 5.4.0-25.29 linux-image-generic-hwe-20.04 5.4.0.25.31 $ ubuntu-drivers list nvidia-driver-390 nvidia-driver-435 nvidia-driver-440 $ sudo ubuntu-drivers install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 Suggested packages: fdutils linux-doc | linux-source-5.4.0 linux-tools linux-headers-5.4.0-25-lowlatency Recommended packages: libnvidia-compute-440:i386 libnvidia-decode-440:i386 libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 libnvidia-gl-440:i386 The following NEW packages will be installed: libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440 linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency linux-modules-nvidia-440-5.4.0-25-lowlatency linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 screen-resolution-extra xserver-xorg-video-nvidia-440 0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded. I was expecting for it to pick linux-modules-nvidia-440-generic- hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04 As if it sorted things and picked last one? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1532226] Re: No menu bar in gtk apps on fresh boot
error happened again. all installed GUI applications do not have menu. Distributor ID: Ubuntu Description:Ubuntu 19.10 Release:19.10 Codename: eoan display manager: gdm3 window manager: xfce4 kernel: Linux vhdx127 5.3.0-46-generic #38-Ubuntu SMP Fri Mar 27 17:37:05 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1532226 Title: No menu bar in gtk apps on fresh boot Status in BAMF: New Status in Release Notes for Ubuntu: Fix Released Status in bamf package in Ubuntu: Fix Released Status in bamf source package in Xenial: Fix Released Bug description: Seen here in fresh 16.04 install using 01/07/16 image. Around 35% of fresh boots or restarts results in no menus in unity panel for most apps, notable exceptions are firefox & thunderbird A log out/in restores functionality. When this occurs there is nothing in any of the ~/.cache/upstart logs of obvious note Test case: fresh install, no changes Do a number of restarts from system settings, using either restart > restart or shutdown > restart, here randomly picked one or the other What happens here: around 35% of the time the login has no menus in the unity panel for most apps. To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1532226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
@mario-vukelic I just tested it again with my devices (just to be sure) and I have this issue under Wayland and Xorg independently of the screen rotation (laptop + tablet mode). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873052] Re: GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps another not scaled cursor mid screen
** Changed in: mutter (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873052 Title: GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps another not scaled cursor mid screen Status in Mutter: Fix Released Status in mutter package in Ubuntu: Triaged Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874051] Re: Crackling headphone output after waking up from sleep
Do note that audio is flawless right after boot, this only happens if the laptop is placed into suspend and then resumed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1874051 Title: Crackling headphone output after waking up from sleep Status in alsa-driver package in Ubuntu: New Bug description: I have performed a fresh install of Ubuntu 18.04.4, Ubuntu 19.10, and Ubuntu 20.04, as well as Fedora 31 and all of them have this issue with this audio codec. On Windows 10, sound plays perfectly when waking from sleep, whereas on Ubuntu there is this strange 'crackling' sound that occurs when some playback is happening. Laptop is the HP Pavilion x360 Convertible 14-ba0xx. This issue seems very similar but it looks like no one is fixing it: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183 (I can confirm Erikas' solution in the above bug thread works, there is no more crackling on resume from suspend) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jkelol111 1825 F pulseaudio /dev/snd/pcmC0D0p: jkelol111 1825 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 19:17:10 2020 InstallationDate: Installed on 2020-04-21 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulseAudioLog: Apr 21 09:32:13 BrokenHingeLaptop dbus-daemon[1006]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=124 pid=1196 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 21 09:32:28 BrokenHingeLaptop systemd[1165]: pulseaudio.service: Succeeded. Apr 21 09:32:38 BrokenHingeLaptop systemd[1165]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [HP Pavilion x360 Convertible 14-ba0xx, Realtek ALC295, Black Headphone Out, Left] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 830F dmi.board.vendor: HP dmi.board.version: 31.25 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd05/03/2019:svnHP:pnHPPavilionx360Convertible14-ba0xx:pvrType1ProductConfigId:rvnHP:rn830F:rvr31.25:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-ba0xx dmi.product.sku: 2GV24PA#UUF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874051/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874051] [NEW] Crackling headphone output after waking up from sleep
Public bug reported: I have performed a fresh install of Ubuntu 18.04.4, Ubuntu 19.10, and Ubuntu 20.04, as well as Fedora 31 and all of them have this issue with this audio codec. On Windows 10, sound plays perfectly when waking from sleep, whereas on Ubuntu there is this strange 'crackling' sound that occurs when some playback is happening. Laptop is the HP Pavilion x360 Convertible 14-ba0xx. This issue seems very similar but it looks like no one is fixing it: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183 (I can confirm Erikas' solution in the above bug thread works, there is no more crackling on resume from suspend) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jkelol111 1825 F pulseaudio /dev/snd/pcmC0D0p: jkelol111 1825 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 19:17:10 2020 InstallationDate: Installed on 2020-04-21 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulseAudioLog: Apr 21 09:32:13 BrokenHingeLaptop dbus-daemon[1006]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=124 pid=1196 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 21 09:32:28 BrokenHingeLaptop systemd[1165]: pulseaudio.service: Succeeded. Apr 21 09:32:38 BrokenHingeLaptop systemd[1165]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [HP Pavilion x360 Convertible 14-ba0xx, Realtek ALC295, Black Headphone Out, Left] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 830F dmi.board.vendor: HP dmi.board.version: 31.25 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd05/03/2019:svnHP:pnHPPavilionx360Convertible14-ba0xx:pvrType1ProductConfigId:rvnHP:rn830F:rvr31.25:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-ba0xx dmi.product.sku: 2GV24PA#UUF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic eoan focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1874051 Title: Crackling headphone output after waking up from sleep Status in alsa-driver package in Ubuntu: New Bug description: I have performed a fresh install of Ubuntu 18.04.4, Ubuntu 19.10, and Ubuntu 20.04, as well as Fedora 31 and all of them have this issue with this audio codec. On Windows 10, sound plays perfectly when waking from sleep, whereas on Ubuntu there is this strange 'crackling' sound that occurs when some playback is happening. Laptop is the HP Pavilion x360 Convertible 14-ba0xx. This issue seems very similar but it looks like no one is fixing it: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183 (I can confirm Erikas' solution in the above bug thread works, there is no more crackling on resume from suspend) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jkelol111 1825 F pulseaudio /dev/snd/pcmC0D0p: jkelol111 1825 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 19:17:10 2020 InstallationDate: Installed on 2020-04-21 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulseAudioLog: Apr 21 09:32:13 BrokenHingeLaptop dbus-daemon[1006]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=124 pid=1196 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
