[Desktop-packages] [Bug 1869605] Re: Please remove mozjs60; superseded by mozjs68
Removing packages from focal: mozjs60 60.8.0-2ubuntu5 in focal libmozjs-60-0 60.8.0-2ubuntu5 in focal amd64 libmozjs-60-0 60.8.0-2ubuntu5 in focal arm64 libmozjs-60-0 60.8.0-2ubuntu5 in focal armhf libmozjs-60-0 60.8.0-2ubuntu5 in focal ppc64el libmozjs-60-0 60.8.0-2ubuntu5 in focal s390x libmozjs-60-dev 60.8.0-2ubuntu5 in focal amd64 libmozjs-60-dev 60.8.0-2ubuntu5 in focal arm64 libmozjs-60-dev 60.8.0-2ubuntu5 in focal armhf libmozjs-60-dev 60.8.0-2ubuntu5 in focal ppc64el libmozjs-60-dev 60.8.0-2ubuntu5 in focal s390x Comment: deprecated in favor of mozjs68; library with no reverse-dependencies; build-depends on python2. Debian bug #937087, LP: #1869605. 1 package successfully removed. ** Changed in: mozjs60 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mozjs60 in Ubuntu. https://bugs.launchpad.net/bugs/1869605 Title: Please remove mozjs60; superseded by mozjs68 Status in mozjs60 package in Ubuntu: Fix Released Bug description: Please remove mozjs60 from Ubuntu focal. The supported version is mozjs68 (It is the JavaScript engine from Firefox LTS). mozjs60 has no remaining reverse dependencies in focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozjs60/+bug/1869605/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
Cool. Also keep in mind there are multiple different standards for 4-ring plugs. And no guarantee your headset and computer use the same standard :/ https://www.cablechick.com.au/blog/understanding-trrs-and-audio-jacks/ -- 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/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Triaged Status in pulseaudio source package in Bionic: Triaged Status in pulseaudio source package in Focal: Triaged Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
Weird. I can't find an exactly matching upstream bug. And the closest fix I can find was mutter!1029 which was released in 3.35.90 already. Regardless, the original reporter says it is fixed AND the ubuntu error tracker says the crash hasn't occurred since version 3.34.1. If you experience any similar crashes in the near future then those might be bug 1864326 (fixed in 3.36.1 coming soon). ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released -- 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/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b gnome-shell crashes with this bug every time that: * I am editing a file in geany * I open the Find window (CTRL-F) and it opens on another monitor * I type in some un-findable text in the find window and press ENTER (or click the Next button) The system beeps to indicate that the text isn't found, but then crashes. Note especially that the find window must be on the other monitor - if it's on the same monitor as geany, gnome-shell doesn't crash. (Note: I originally thought that if I moved the find window to the other window and then searched, gnome-shell crashed, but I think what happens is a) I open the window, b) I move it, search for something, and it works, c) I close it and re-open it - it then opens on the other monitor and searching will crash gnome-shell.) gnome-shell restarts, but the crash causes data loss, as most of the running applications don't reappear when it restarts. In case it's relevant, I have a laptop screen set at 2048x1152 and an external monitor configured to be above it at 2560x1440. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 Uname: Linux 5.4.0-050400rc4-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 10:37:36 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1570619894 InstallationDate: Installed on 2019-07-01 (112 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/rocko ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849249/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
I think 3 stripes = 4 rings, and we are talking the same thing, I will make it more clear ** Description changed: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] - 1. Insert 3-ring headset into front audio port (headset icon) + 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 -- 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/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Triaged Status in pulseaudio source package in Bionic: Triaged Status in pulseaudio source package in Focal: Triaged Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1772588] Re: Remove obsolete X11 drivers from the archive
I was thinking about this bug yesterday, and yes I'll file a bug on Debian to remove these. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Incomplete Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: New Status in xserver-xorg-input-elographics package in Ubuntu: New Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: New Status in xserver-xorg-input-void package in Ubuntu: New Status in xserver-xorg-video-ast package in Ubuntu: Triaged Status in xserver-xorg-video-geode package in Ubuntu: New Status in xserver-xorg-video-mach64 package in Ubuntu: New Status in xserver-xorg-video-neomagic package in Ubuntu: New Status in xserver-xorg-video-r128 package in Ubuntu: New Status in xserver-xorg-video-savage package in Ubuntu: New Status in xserver-xorg-video-siliconmotion package in Ubuntu: New Status in xserver-xorg-video-sisusb package in Ubuntu: New Status in xserver-xorg-video-tdfx package in Ubuntu: New Status in xserver-xorg-video-trident package in Ubuntu: New Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+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 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
This is fixed for me in gnome-shell 3.36.0-2ubuntu2, thanks! -- 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/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b gnome-shell crashes with this bug every time that: * I am editing a file in geany * I open the Find window (CTRL-F) and it opens on another monitor * I type in some un-findable text in the find window and press ENTER (or click the Next button) The system beeps to indicate that the text isn't found, but then crashes. Note especially that the find window must be on the other monitor - if it's on the same monitor as geany, gnome-shell doesn't crash. (Note: I originally thought that if I moved the find window to the other window and then searched, gnome-shell crashed, but I think what happens is a) I open the window, b) I move it, search for something, and it works, c) I close it and re-open it - it then opens on the other monitor and searching will crash gnome-shell.) gnome-shell restarts, but the crash causes data loss, as most of the running applications don't reappear when it restarts. In case it's relevant, I have a laptop screen set at 2048x1152 and an external monitor configured to be above it at 2560x1440. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 Uname: Linux 5.4.0-050400rc4-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 10:37:36 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1570619894 InstallationDate: Installed on 2019-07-01 (112 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/rocko ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849249/+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
Interesting you should bring that up so I played around with middle click, right click and Ctrl+V Although it can produce different paste results, it's not the issue I am having I don't think. The issue is that it's taking more than one copy function to actually copy to the clipboard to have something new to paste from some applications. Whichever clipboard that is. For example I can copy from Firefox and paste to a text editor. I can go copy text from Master PDF Editor by Ctrl+C twice. Ctrl+V or right click pastes the text from Master PDF Editor. Middle mouse click pastes text from Firefox still. I can copy new text in Master PDF Editor by Ctrl+C twice and paste the new text. Middle click continues to paste the text from Firefox until I copy some new text in firefox. The middle click one seems to work just fine to paste from firefox. One copy one paste. It may work OK in other applications too I don't know. But it apparently doesn't work at all in some others like Master PDF Editor, while two Ctrl+C's does work in these other applications. I'm dumb about this. I guess the X11 one works fine if it works at all in the application you are copying from? And the other one does not work reliably without doing Ctrl+C twice in some applications you are copying from. I don't know. But it is certainly going to be April in a few minutes. -- 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 codelite package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released 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 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=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 1869549] Re: [nvidia] Whenever a sound needs to be played the screen blanks out
If you find the flashing is especially worse on Nvidia then that might relate to bug 1869750 so it will also be interesting to see if the update to 3.36.1 makes a difference. ** Package changed: linux (Ubuntu) => gnome-shell (Ubuntu) ** Package changed: nvidia-graphics-drivers-435 (Ubuntu) => mutter (Ubuntu) -- 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/1869549 Title: [nvidia] Whenever a sound needs to be played the screen blanks out Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Whenever a sound needs to be played the screen blanks out for a second, then the screen comes back on, and the sound plays. Examples of sounds are when I press Tab on the terminal, and there are no possible completions, or when I press the down button on the terminal, and there are no further lines below, then it blanks out, comes back, and then plays the "ding" tone telling me there are no further completions or lines. However, after one blank-out, if I keep pressing the down button, the sounds play normally without blanking out for a short time. After that period, it repeats again on doing something that would cause the sound to be played again. I'm on a relatively new HP Pavilion CS3006TX, running 20.04 Focal Fossa (Development branch) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 29 09:05:04 2020 DistUpgraded: 2020-03-28 14:50:01,253 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-42-generic, x86_64: installed nvidia, 435.21, 5.4.0-18-generic, x86_64: installed virtualbox, 6.1.4, 5.3.0-42-generic, x86_64: installed virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:86e2] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:86e2] InstallationDate: Installed on 2019-11-30 (119 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03bc Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cs3xxx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5ee3ea75-c293-4350-b4ea-e81ef28c7f78 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-03-28 (0 days ago) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86E2 dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.03:bd08/23/2019:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:rvnHP:rn86E2:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs3xxx dmi.product.sku: 8LX85PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core
[Desktop-packages] [Bug 1869549] [NEW] [nvidia] Whenever a sound needs to be played the screen blanks out
You have been subscribed to a public bug: Whenever a sound needs to be played the screen blanks out for a second, then the screen comes back on, and the sound plays. Examples of sounds are when I press Tab on the terminal, and there are no possible completions, or when I press the down button on the terminal, and there are no further lines below, then it blanks out, comes back, and then plays the "ding" tone telling me there are no further completions or lines. However, after one blank-out, if I keep pressing the down button, the sounds play normally without blanking out for a short time. After that period, it repeats again on doing something that would cause the sound to be played again. I'm on a relatively new HP Pavilion CS3006TX, running 20.04 Focal Fossa (Development branch) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 29 09:05:04 2020 DistUpgraded: 2020-03-28 14:50:01,253 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-42-generic, x86_64: installed nvidia, 435.21, 5.4.0-18-generic, x86_64: installed virtualbox, 6.1.4, 5.3.0-42-generic, x86_64: installed virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:86e2] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:86e2] InstallationDate: Installed on 2019-11-30 (119 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03bc Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cs3xxx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5ee3ea75-c293-4350-b4ea-e81ef28c7f78 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-03-28 (0 days ago) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86E2 dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.03:bd08/23/2019:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:rvnHP:rn86E2:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs3xxx dmi.product.sku: 8LX85PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal nvidia reproducible ubuntu -- [nvidia] Whenever a sound needs to be played the screen blanks out https://bugs.launchpad.net/bugs/1869549 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list:
[Desktop-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
> 1. Insert 3-ring headset into front audio port (headset icon) Is that right? Unless it's a strange-shaped 3-ring plug I think you will find it needs to have 4 rings to be a working (stereo) headset. -- 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/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Triaged Status in pulseaudio source package in Bionic: Triaged Status in pulseaudio source package in Focal: Triaged Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 3-ring headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1869905] Re: OnlyShowIn and NotShowIn not properly honored
Note the fix only exists on master (3.37), not in 3.36. ** Tags added: focal ** Tags added: fixed-in-3.37.0 fixed-upstream -- 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/1869905 Title: OnlyShowIn and NotShowIn not properly honored Status in gnome-shell package in Ubuntu: Fix Committed Bug description: glib provides g_app_info_should_show to determine if a desktop file should be shown in the app grid based on OnlyShowIn and NotShowIn using XDG_CURRENT_DESKTOP. This isn't being honored in gnome-shell when NotShowIn=ubuntu:GNOME or OnlyShowIn=ubuntu:GNOME and XDG_CURRENT_DESKTOP is ubuntu:GNOME. glib does have tests for this that are still passing and @seb128 wrote a simple test case to show the glib API does the right thing. The snap-store snap in the beta channel provides two desktop files, one to be displayed when XDG_CURRENT_DESKTOP is ubuntu:GNOME and one for when it isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869905/+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 1868529] Re: Stretched image previews on desktop
** Summary changed: - Stretched picture or pdf preview icon on desktop + Stretched image previews on desktop ** Bug watch added: gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues #190 https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/190 ** Also affects: gnome-shell-extension-desktop-icons via https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/190 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1868529 Title: Stretched image previews on desktop Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: After upgrade to 20.04 desktop previews of pictures and documents became stretched. The regular previews in Nautilus have normal sizes. See attached pic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-desktop-icons 19.10.2+git20200223-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 23 11:44:13 2020 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1868529/+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 1869042] Re: all monitor scaling fails due to overlapping monitors
** Tags added: nvidia ** Summary changed: - all monitor scaling fails due to overlapping monitors + [nvidia] all monitor scaling fails due to overlapping monitors -- 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/1869042 Title: [nvidia] all monitor scaling fails due to overlapping monitors Status in NVIDIA Drivers Ubuntu: New Status in mutter package in Ubuntu: Incomplete Bug description: After an upgrade with focal-proposed this morning, I am unable to set any scaling for any of my monitors without the monitor turning blank for 15 seconds and reverting to 100% scaling. I am using X11 with gnome and proprietary nvidia drivers on Focal. I have 3 monitors attached, all 4K, and my usual setup is to enable fractional scaling, and set all 3 monitors to 150% scaling. Now however, I cannot change the monitors to use any scaling, and even if I disconnect 2 of the monitors to only have a single monitor I still cannot use scaling. Finally note I am just using the Settings window, I haven't fiddled with xrandr at all manually. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Uname: Linux 5.4.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 11:24:05 2020 InstallationDate: Installed on 2019-07-05 (264 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1869042/+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 1869974] Re: gnome-shell: virtual desktops broken as windows appear on every desktop, regardless of where they are placed
*** This bug is a duplicate of bug 1868911 *** https://bugs.launchpad.net/bugs/1868911 ** This bug has been marked a duplicate of bug 1868911 Exiting overview causes windows from other workspaces to be visible -- 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/1869974 Title: gnome-shell: virtual desktops broken as windows appear on every desktop, regardless of where they are placed Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Released Bug description: gnome-shell: virtual desktops broken as windows appear on every desktop, regardless of where they are placed On focal, with gnome-shell 3.36.0-2ubuntu1 and 3.36.0-2ubuntu2, if you open a few applications, such as gnome-disks, nautilus and firefox, then move a window to a different virtual desktop, and switch to it, all windows are found to be on the virtual desktop. No matter what you do, all windows will be present, breaking virtual desktops. Attached is a screencast demonstrating the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869974/+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 1869945] Re: design flaw: application menu.
*** This bug is a duplicate of bug 968213 *** https://bugs.launchpad.net/bugs/968213 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 968213, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** This bug has been marked a duplicate of bug 968213 Too many icons in Gnome Shell Activities Overview require ellipses -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1869945 Title: design flaw: application menu. Status in gnome-shell package in Ubuntu: New Bug description: Bad design. The inscriptions do not fit into their places in the application menu. Look at the attachment. Плохой дизайн. Надписи не вписываются в свои места в меню приложений. Смотрите вложение. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 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.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 12:06:39 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2020-03-30 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. VMware Virtual USB Mouse Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=1ed2509c-6bde-4abc-80f6-2cf45bec3d55 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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/gnome-shell/+bug/1869945/+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 1869565] Re: Login loop with fresh 19.10 install
If were using Nvidia before then the problem might have been bug 1845801. Since this bug won't be used anymore I will close it now. ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Invalid -- 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/1869565 Title: Login loop with fresh 19.10 install Status in gdm3 package in Ubuntu: Invalid Bug description: On a fresh clean 19.10 install, a login loop evolves after a couple of reboots. The gdm package is likely the culprit. None of the recommendations in https://askubuntu.com/questions/1182506/login-loop-with-fresh-19-10-install fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1869565/+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 1866368] Re: gnome-shell crashed with SIGSEGV in wl_resource_get_version(resource=0x0)
The Ubuntu error tracker is showing no occurrences of this crash outside of version 3.35.91-1ubuntu2 so let's assume it's fixed. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released -- 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/1866368 Title: gnome-shell crashed with SIGSEGV in wl_resource_get_version(resource=0x0) Status in gnome-shell package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/d34d7337a4c810ce28fed5c01b0caf7ac53f8b8c --- I had two crashes in a row, in both instances I was moving a Firefox tab from one window out to a new window with drag and drop. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 16:16:03 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: wl_resource_get_version () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGSEGV in wl_resource_get_version() UpgradeStatus: Upgraded to focal on 2019-08-24 (195 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866368/+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 1869974] Re: gnome-shell: virtual desktops broken as windows appear on every desktop, regardless of where they are placed
Oops, sorry. I rebooted my machine and the problem does not reproduce, since I installed 3.36.0-2ubuntu2 and hadn't rebooted. ** Changed in: gnome-shell (Ubuntu Focal) Status: Incomplete => Fix Released ** Tags removed: champagne -- 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/1869974 Title: gnome-shell: virtual desktops broken as windows appear on every desktop, regardless of where they are placed Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Released Bug description: gnome-shell: virtual desktops broken as windows appear on every desktop, regardless of where they are placed On focal, with gnome-shell 3.36.0-2ubuntu1 and 3.36.0-2ubuntu2, if you open a few applications, such as gnome-disks, nautilus and firefox, then move a window to a different virtual desktop, and switch to it, all windows are found to be on the virtual desktop. No matter what you do, all windows will be present, breaking virtual desktops. Attached is a screencast demonstrating the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869974/+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 1869913] Re: "Click or press a key to unlock" string not translated into french
That's odd. The source code suggests the French translation has existed since at least version 3.35.92. ** No longer affects: gdm3 (Ubuntu) -- 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/1869913 Title: "Click or press a key to unlock" string not translated into french Status in gnome-shell package in Ubuntu: New Bug description: On the lockscreen, the "Click or press a key to unlock" string is not translated, at least in french. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 14:56:11 2020 InstallationDate: Installed on 2019-02-21 (404 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-03-20 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869913/+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 1869913] Re: "Click or press a key to unlock" string not translated into french
>From commit d90a79fe7a: +msgid "Click or press a key to unlock" +msgstr "Cliquer ou appuyer sur une touche pour déverrouiller" -- 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/1869913 Title: "Click or press a key to unlock" string not translated into french Status in gnome-shell package in Ubuntu: New Bug description: On the lockscreen, the "Click or press a key to unlock" string is not translated, at least in french. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 14:56:11 2020 InstallationDate: Installed on 2019-02-21 (404 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-03-20 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869913/+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 1869916] Re: Password field stretches to full password width on login and lock screens
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2423 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2423 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2423 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Committed ** Tags added: fixed-in-3.36.1 fixed-upstream -- 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/1869916 Title: Password field stretches to full password width on login and lock screens Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Committed Bug description: In 20.04, on both the login screen and the lock screen, when the password is long, after pressing enter the password field will stretch to the right to show the entire password. To test, lock the screen and input a long string of characters into the password field and press enter. Attaching photo of what it looks like. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869916/+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 1793496] Re: scaling changes when closing/re-opening the lid
** Tags added: bionic focal -- 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/1793496 Title: scaling changes when closing/re-opening the lid Status in Mutter: Fix Released Status in mutter package in Ubuntu: Triaged Status in mutter source package in Bionic: Confirmed Status in mutter source package in Focal: Triaged Bug description: scaling changes when closing/re-opening the lid. Seen in bionic. Mz scaling is set to 100%, but the laptop is considered highdpi by mutter, and during suspend/resume it changes back to default ignoring settings. $ xprop -spy -root RESOURCE_MANAGER [...] RESOURCE_MANAGER(STRING) = "*customization:\t-color\nXft.dpi:\t192\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t48\nXcursor.theme:\tDMZ-White\n" RESOURCE_MANAGER(STRING) = "*customization:\t-color\nXft.dpi:\t96\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t24\nXcursor.theme:\tDMZ-White\n" xrandr Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192 eDP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 309mm x 174mm 2560x1440 60.00*+ 59.9959.9959.9659.95 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1793496/+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 1869916] Re: Password field stretches to full password width on login and lock screens
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1869916 Title: Password field stretches to full password width on login and lock screens Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Committed Bug description: In 20.04, on both the login screen and the lock screen, when the password is long, after pressing enter the password field will stretch to the right to show the entire password. To test, lock the screen and input a long string of characters into the password field and press enter. Attaching photo of what it looks like. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869916/+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 1869737] Re: Folders in applications menu are broken in smaller screens
** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2549 Importance: Unknown Status: Unknown -- 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/1869737 Title: Folders in applications menu are broken in smaller screens Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: When using a smaller screen resolution like 1366x768, opening and closing a folder inside the applications menu breaks the scaling of the icons and number of pages. Icons either become very small or disappear and the number of pages shows more pages than it should. The bug did not occur when using a 1920x1080 display. I've also recorded a little video: https://youtu.be/v98TfvBaxqk ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 11:22:30 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-28 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-28 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869737/+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
Yes, X11 and GNOME have two separate clipboards. This has been true for as long as I remember (though not saying it's a good thing)... To paste from the X11 one use your middle mouse button. To paste from the GNOME one use Ctrl+V or a right-click context menu. -- 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 codelite package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released 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 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=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 1866275] Re: Password overlay dialogue breaks during screen lock while overlay present
** No longer affects: gnome-shell (Ubuntu Focal) -- 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/1866275 Title: Password overlay dialogue breaks during screen lock while overlay present Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: If you have a password overlay dialogue box present on your screen, for example, trying to mount an encrypted disk image from gnome-disks, or trying to unlock an ssh key, if the lock screen appears while the dialogue is in place, after unlocking the screen, you can still enter your password into the dialogue and the action still happens (mounting the disk image, unlocking the ssh key), but the dialogue box gets stuck and does not disappear. Steps for reproducing: 1) In gnome-disks, make a small 10mb disk image, select ext4 and luks. Set a trivial password. 2) Attempt to mount the encrypted disk image 3) When the password unlock dialogue appears, lock your screen (super + L) 4) Wake the screen up, unlock computer 5) Enter password into existing dialogue 6) The dialogue now cannot be dismissed. Logs: Mar 06 12:46:36 ubuntu0 udisksd[749]: Set up loop device /dev/loop5 (backed by /home/ubuntu/Documents/diskimage.img) Mar 06 12:46:37 ubuntu0 systemd[1]: fprintd.service: Succeeded. Mar 06 12:46:40 ubuntu0 dbus-daemon[703]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.307' (uid=1000 pid=1506 comm="> Mar 06 12:46:40 ubuntu0 systemd[1]: Starting Fingerprint Authentication Daemon... Mar 06 12:46:40 ubuntu0 dbus-daemon[703]: [system] Successfully activated service 'net.reactivated.Fprint' Mar 06 12:46:40 ubuntu0 systemd[1]: Started Fingerprint Authentication Daemon. Mar 06 12:46:40 ubuntu0 gdm-password][1921]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: No such file or directory Mar 06 12:46:43 ubuntu0 gnome-shell[1506]: JS WARNING: [resource:///org/gnome/shell/gdm/authPrompt.js 316]: reference to undefined property "_defaultButtonWellActor" Mar 06 12:46:43 ubuntu0 gdm-password][1921]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: No such file or directory Mar 06 12:46:43 ubuntu0 gdm-password][1921]: gkr-pam: unlocked login keyring Mar 06 12:46:43 ubuntu0 NetworkManager[706]: [1583452003.9911] agent-manager: agent[69f92bd444c1b400,:1.307/org.gnome.Shell.NetworkAgent/1000]: agent registered Mar 06 12:46:43 ubuntu0 dbus-daemon[1259]: [session uid=1000 pid=1259] Activating service name='org.freedesktop.FileManager1' requested by ':1.50' (uid=1000 pid=1506 comm="/usr/bin/gn> Mar 06 12:46:44 ubuntu0 dbus-daemon[1259]: [session uid=1000 pid=1259] Activating service name='org.gnome.Nautilus' requested by ':1.50' (uid=1000 pid=1506 comm="/usr/bin/gnome-shell > Mar 06 12:46:44 ubuntu0 gnome-shell[1506]: Unable to mount volume 10.0 MB Encrypted: Gio.IOErrorEnum: An operation is already pending Mar 06 12:46:51 ubuntu0 udisksd[749]: Unlocked device /dev/loop5 as /dev/dm-3 Mar 06 12:46:51 ubuntu0 kernel: EXT4-fs (dm-3): mounted filesystem without journal. Opts: (null) Mar 06 12:53:50 ubuntu0 gnome-shell[1506]: JS WARNING: [resource:///org/gnome/shell/ui/unlockDialog.js 762]: reference to undefined property "_authPrompt" Mar 06 12:53:50 ubuntu0 gnome-shell[1506]: JS ERROR: TypeError: this._authPrompt is undefined _escape@resource:///org/gnome/shell/ui/unlockDialog.js:762:13 Version info: - Ubuntu 20.04 - gnome-shell 3.35.91-1ubuntu2 Attached is a screencast demonstrating each of the steps for reproducing. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1866275/+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 1869974] Re: gnome-shell: virtual desktops broken as windows appear on every desktop, regardless of where they are placed
I believe this was fixed yesterday in 3.36.0-2ubuntu2. To confirm if this is a different problem please: 1. Run this command to automatically attach system info: apport-collect 1869974 2. Run this command: dpkg -l > packages.txt and attach the file 'packages.txt' to this bug. Also please remember to log out/in again since yesterday's update :) ** Changed in: gnome-shell (Ubuntu Focal) 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/1869974 Title: gnome-shell: virtual desktops broken as windows appear on every desktop, regardless of where they are placed Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell source package in Focal: Incomplete Bug description: gnome-shell: virtual desktops broken as windows appear on every desktop, regardless of where they are placed On focal, with gnome-shell 3.36.0-2ubuntu1 and 3.36.0-2ubuntu2, if you open a few applications, such as gnome-disks, nautilus and firefox, then move a window to a different virtual desktop, and switch to it, all windows are found to be on the virtual desktop. No matter what you do, all windows will be present, breaking virtual desktops. Attached is a screencast demonstrating the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869974/+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 1847712] Re: Desktop icons vanishing when in Activities Overview is jarring and looks ugly
** No longer affects: gnome-shell (Ubuntu Focal) -- 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/1847712 Title: Desktop icons vanishing when in Activities Overview is jarring and looks ugly Status in gnome-shell package in Ubuntu: Triaged Bug description: Desktop icons vanishing and reappearing when in Activities Overview is jarring and looks ugly. Suggestions: * Don't hide them in AO, because they will be well shaded anyway; or * Fade them out and in smoothly. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-desktop-icons 19.01.4-1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Fri Oct 11 14:24:42 2019 InstallationDate: Installed on 2019-05-02 (162 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons 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/1847712/+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 1865379] Re: Raspberry Pi 4 fails to wake at login prompt
Hello, I have not forgotten about this.
1.) Does not exist.
2.) I've already reported.
I will have to apply the patch outlined in 3.) and cause the crash
again. However, this system uses an SD card, and the first system had a
corrupted boot partition after crashing a series of times. This crash
might prevent me from collecting the data the crash creates.
I will give it a shot.
--
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/1865379
Title:
Raspberry Pi 4 fails to wake at login prompt
Status in linux package in Ubuntu:
Confirmed
Status in xorg-server package in Ubuntu:
Incomplete
Bug description:
Raspberry Pi 4 running Ubuntu server 20.04 Focal (and perhaps 19.10
Eoan) fails to wake from sleep when no user is logged in and the
screen is sitting at the gdm login prompt.
This has happened on two different systems. One system uses the
official RPi 7 inch touchscreen via (LCD DSI Display Connector). The
other system has a 10 inch non-touchscreen from SunFounder via (Micro
HDMI).
Nothing wakes the Pi: Keyboard, mouse, or touchscreen.
After a user logs in and the screen locks on sleep the system wakes
just fine with a lock screen.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
Uname: Linux 5.4.0-1001-raspi2 armv7l
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
Date: Sun Mar 1 20:03:12 2020
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: Upgraded to focal on 2020-02-28 (2 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
GsettingsChanges:
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
Package: gnome-shell 3.35.91-1ubuntu2
PackageArchitecture: armhf
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
Tags: focal uec-images third-party-packages
Uname: Linux 5.4.0-1001-raspi2 armv7l
UpgradeStatus: Upgraded to focal on 2020-02-28 (20 days ago)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
GsettingsChanges:
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities',
'Sundry', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
Package: gnome-shell 3.35.91-1ubuntu2
PackageArchitecture: armhf
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
Tags: focal uec-images third-party-packages
Uname: Linux 5.4.0-1001-raspi2 armv7l
UpgradeStatus: Upgraded to focal on 2020-01-12 (69 days ago)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: XFCE
DistUpgraded: 2020-01-11 19:42:56,183 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroRelease: Ubuntu 20.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8086:0808 Intel Corp.
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Package: xorg-server (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M
video=HDMI-A-1:1280x800@60 smsc95xx.macaddr=DC:A6:32:1F:4B:D2
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
Tags: focal uec-images ubuntu reproducible
Uname: Linux
[Desktop-packages] [Bug 1856376] Re: "Dummy Output" -- built-in audio not detected
@dogmatic69, Please refer to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869799 -- 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/1856376 Title: "Dummy Output" -- built-in audio not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: I no longer seem to be getting audio on my laptop, and only "Dummy Output" shows up in the sound settings dialog. This sounds similar to LP #1781294 (including the same PCI device), though that seems to have been marked expired. alex@tapada:~$ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Lenovo Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 64, IRQ 159 Memory at 2ffb028000 (64-bit, non-prefetchable) [size=16K] Memory at 2ffb00 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl alex@tapada:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 23:38:35 2019 InstallationDate: Installed on 2019-08-31 (104 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET68W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T22:15:32.867642 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856376/+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 1869814] Re: ubuntu-docs build failure - possible solution
Thanks Shaun! It's indeed that bug. Why am I not surprised when seeing
that you filed it? :)
I grabbed a Fedora patch and submitted a Debian merge request:
https://salsa.debian.org/xml-sgml-team/libxml2/-/merge_requests/3
It looks pretty spot on, don't you think? At least, with that patch
applied I can build ubuntu-docs 19.10.2 successfully again. A syntax
error in one of the Chinese translations is reported as warnings as
expected.
** Changed in: libxml2 (Ubuntu)
Importance: Undecided => Medium
** Changed in: libxml2 (Ubuntu)
Status: New => In Progress
** Changed in: libxml2 (Ubuntu)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
Status in itstool package in Ubuntu:
Invalid
Status in libxml2 package in Ubuntu:
In Progress
Status in ubuntu-docs package in Ubuntu:
Fix Committed
Bug description:
ubuntu-docs failed to build during the second Focal Fossa test
rebuild:
https://launchpad.net/ubuntu/+archive/test-
rebuild-20200327-focal/+build/18982738
It was itstool which failed to generate the localized zh_CN pages. If
dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
excluding the Chinese pages is apparently not an acceptable solution.
The itstool package in focal {build-,}depends on python3. I built
itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
built fine without modifications:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages
So the root cause seems to lie neither in ubuntu-docs nor itstool. I
would suspect that python3-libxml2 is buggy, but since itstool was
built against python2 in eoan, it's hard to tell if it's a regression.
Would building itstool against python2 be an acceptable workaround in
focal?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1869981] [NEW] Printer notification every day at midnight
Public bug reported: Every day, all my 20.04 machines get a notification that the printer in my house has been detected. The printer works fine and is already added. So not sure why I need to be told repeatedly that I have a printer on the network? (see screenshot) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Wed Apr 1 00:00:31 2020 InstallationDate: Installed on 2020-03-01 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/ MachineType: LENOVO 20BV001BUK Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: JBET73WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV001BUK dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV001BUK dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-04-01 00-01-14.png" https://bugs.launchpad.net/bugs/1869981/+attachment/5343944/+files/Screenshot%20from%202020-04-01%2000-01-14.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1869981 Title: Printer notification every day at midnight Status in cups package in Ubuntu: New Bug description: Every day, all my 20.04 machines get a notification that the printer in my house has been detected. The printer works fine and is already added. So not sure why I need to be told repeatedly that I have a printer on the network? (see screenshot) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Wed Apr 1 00:00:31 2020 InstallationDate: Installed on 2020-03-01 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/ MachineType: LENOVO 20BV001BUK Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: JBET73WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV001BUK dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV001BUK dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1869981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1869979] [NEW] liborc-0.4.so doesn't exist after install
Public bug reported: If you apt install liborc-0.4-0, there is no liborc-0.4.so file in /usr/lib/x86_64-linux-gnu/ There IS a liborc-0.4.so.0 file that is a link to iborc-0.4.so.0.28.0, but there is no link with name liborc-0.4.so pointing to that same file. I don't know if this is a bug or expected behavior, but it does trigger issues with other packages, such as out-of-tree modules for GNURadio: https://github.com/bastibl/gr-foo/issues/24#issuecomment-606925453 Those can be fixed with a simple symlink. If this is a problem with the build system of the other project (i.e., it should have picked up the so.0 file), my apologies and please close the issue. Thanks. System details: Description: Ubuntu 18.04.4 LTS Release: 18.04 Version: liborc-0.4-0 Installed: 1:0.4.28-1 Summary: I expect there to be a .so file by the name of the library somewhere on the system after installing. There is not one, but instead, the name I expect with a .so.0 extension exists, but there is no symlink with the expected name. ** Affects: orc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to orc in Ubuntu. https://bugs.launchpad.net/bugs/1869979 Title: liborc-0.4.so doesn't exist after install Status in orc package in Ubuntu: New Bug description: If you apt install liborc-0.4-0, there is no liborc-0.4.so file in /usr/lib/x86_64-linux-gnu/ There IS a liborc-0.4.so.0 file that is a link to iborc-0.4.so.0.28.0, but there is no link with name liborc-0.4.so pointing to that same file. I don't know if this is a bug or expected behavior, but it does trigger issues with other packages, such as out-of-tree modules for GNURadio: https://github.com/bastibl/gr-foo/issues/24#issuecomment-606925453 Those can be fixed with a simple symlink. If this is a problem with the build system of the other project (i.e., it should have picked up the so.0 file), my apologies and please close the issue. Thanks. System details: Description: Ubuntu 18.04.4 LTS Release: 18.04 Version: liborc-0.4-0 Installed: 1:0.4.28-1 Summary: I expect there to be a .so file by the name of the library somewhere on the system after installing. There is not one, but instead, the name I expect with a .so.0 extension exists, but there is no symlink with the expected name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/orc/+bug/1869979/+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] Autopkgtest regression report (snapd-glib/1.56-0ubuntu0.19.10.1)
All autopkgtests for the newly accepted snapd-glib (1.56-0ubuntu0.19.10.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: snapd-glib/1.56-0ubuntu0.19.10.1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#snapd-glib [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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 1869974] Re: gnome-shell: virtual desktops broken as windows appear on every desktop, regardless of where they are placed
Attached is a screencast demonstrating the problem. ** Attachment added: "Screencast of virtual desktops breaking" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869974/+attachment/5343942/+files/Screencast%20from%2001-04-20%2011%3A08%3A18.webm -- 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/1869974 Title: gnome-shell: virtual desktops broken as windows appear on every desktop, regardless of where they are placed Status in gnome-shell package in Ubuntu: New Status in gnome-shell source package in Focal: New Bug description: gnome-shell: virtual desktops broken as windows appear on every desktop, regardless of where they are placed On focal, with gnome-shell 3.36.0-2ubuntu1 and 3.36.0-2ubuntu2, if you open a few applications, such as gnome-disks, nautilus and firefox, then move a window to a different virtual desktop, and switch to it, all windows are found to be on the virtual desktop. No matter what you do, all windows will be present, breaking virtual desktops. Attached is a screencast demonstrating the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869974/+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 1869974] [NEW] gnome-shell: virtual desktops broken as windows appear on every desktop, regardless of where they are placed
Public bug reported: gnome-shell: virtual desktops broken as windows appear on every desktop, regardless of where they are placed On focal, with gnome-shell 3.36.0-2ubuntu1 and 3.36.0-2ubuntu2, if you open a few applications, such as gnome-disks, nautilus and firefox, then move a window to a different virtual desktop, and switch to it, all windows are found to be on the virtual desktop. No matter what you do, all windows will be present, breaking virtual desktops. Attached is a screencast demonstrating the bug. ** Affects: gnome-shell (Ubuntu) Importance: High Status: New ** Affects: gnome-shell (Ubuntu Focal) Importance: High Status: New ** Tags: champagne focal ** Also affects: gnome-shell (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Focal) Importance: Undecided => High ** Tags added: champagne focal -- 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/1869974 Title: gnome-shell: virtual desktops broken as windows appear on every desktop, regardless of where they are placed Status in gnome-shell package in Ubuntu: New Status in gnome-shell source package in Focal: New Bug description: gnome-shell: virtual desktops broken as windows appear on every desktop, regardless of where they are placed On focal, with gnome-shell 3.36.0-2ubuntu1 and 3.36.0-2ubuntu2, if you open a few applications, such as gnome-disks, nautilus and firefox, then move a window to a different virtual desktop, and switch to it, all windows are found to be on the virtual desktop. No matter what you do, all windows will be present, breaking virtual desktops. Attached is a screencast demonstrating the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869974/+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 1869737] Re: Folders in applications menu are broken in smaller screens
Reported on the upstream gitlab issue #2549 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2549 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2549 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2549 -- 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/1869737 Title: Folders in applications menu are broken in smaller screens Status in gnome-shell package in Ubuntu: New Bug description: When using a smaller screen resolution like 1366x768, opening and closing a folder inside the applications menu breaks the scaling of the icons and number of pages. Icons either become very small or disappear and the number of pages shows more pages than it should. The bug did not occur when using a 1920x1080 display. I've also recorded a little video: https://youtu.be/v98TfvBaxqk ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 11:22:30 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-28 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-28 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869737/+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 1869970] [NEW] yaru: Long passwords cause lock screen and gdm password boxes to expand
Public bug reported: yaru: Long passwords cause lock screen and gdm password boxes to expand On focal, with yaru-theme 20.04.4, if the user has a very long password, the small password box will expand for a split second once the user presses the enter key to accept the password. I believe this bug is an incomplete fix of bug 1865563. To reproduce: set a long password, such as: "thisisaverylongpassword" Then lock, and log in. Attached is a screencast of the problem. ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Affects: yaru-theme (Ubuntu Focal) Importance: Undecided Status: New ** Tags: champagne focal ** Also affects: yaru-theme (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1869970 Title: yaru: Long passwords cause lock screen and gdm password boxes to expand Status in yaru-theme package in Ubuntu: New Status in yaru-theme source package in Focal: New Bug description: yaru: Long passwords cause lock screen and gdm password boxes to expand On focal, with yaru-theme 20.04.4, if the user has a very long password, the small password box will expand for a split second once the user presses the enter key to accept the password. I believe this bug is an incomplete fix of bug 1865563. To reproduce: set a long password, such as: "thisisaverylongpassword" Then lock, and log in. Attached is a screencast of the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1869970/+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 1772588] Re: Remove obsolete X11 drivers from the archive
Timo, these appear not to have been removed yet in Debian, despite Buster being out. Will you file for removals in Debian, or should we carry these into another Ubuntu LTS? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Incomplete Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: New Status in xserver-xorg-input-elographics package in Ubuntu: New Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: New Status in xserver-xorg-input-void package in Ubuntu: New Status in xserver-xorg-video-ast package in Ubuntu: Triaged Status in xserver-xorg-video-geode package in Ubuntu: New Status in xserver-xorg-video-mach64 package in Ubuntu: New Status in xserver-xorg-video-neomagic package in Ubuntu: New Status in xserver-xorg-video-r128 package in Ubuntu: New Status in xserver-xorg-video-savage package in Ubuntu: New Status in xserver-xorg-video-siliconmotion package in Ubuntu: New Status in xserver-xorg-video-sisusb package in Ubuntu: New Status in xserver-xorg-video-tdfx package in Ubuntu: New Status in xserver-xorg-video-trident package in Ubuntu: New Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+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
Hello Robert, or anyone else affected, Accepted snapd-glib into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/snapd- glib/1.56-0ubuntu0.19.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: snapd-glib (Ubuntu Eoan) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- 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 1856376] Re: "Dummy Output" -- built-in audio not detected
Sound has been working for me on 19.10 but stopped working a few weeks back after an update. -- 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/1856376 Title: "Dummy Output" -- built-in audio not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: I no longer seem to be getting audio on my laptop, and only "Dummy Output" shows up in the sound settings dialog. This sounds similar to LP #1781294 (including the same PCI device), though that seems to have been marked expired. alex@tapada:~$ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Lenovo Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 64, IRQ 159 Memory at 2ffb028000 (64-bit, non-prefetchable) [size=16K] Memory at 2ffb00 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl alex@tapada:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 23:38:35 2019 InstallationDate: Installed on 2019-08-31 (104 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET68W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T22:15:32.867642 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856376/+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 1869755] Re: No web browser launches in Ubuntu 20.04
== Title = nautilus crashed with signal 5 in g_thread_new() -- 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/1869755 Title: No web browser launches in Ubuntu 20.04 Status in firefox package in Ubuntu: Invalid Bug description: I am getting a segmentation fault when I attempt to launch any web browser: $uname -ar Linux 5.4.0-18-generic #22-Ubuntu SMP Sat Mar 7 18:13:06 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Segmentation errors Web Content[8352]: segfault at 0 ip 7f2157d07742 sp 7ffda17b9bb0 error 6 in libxul.so[7f2156f62000+489e000] Mar 29 20:53:56 localhost kernel: [23017.036763] Code: 48 3b 44 24 10 75 0d b0 01 48 83 c4 18 5b 41 5e 41 5f 5d c3 e8 7f af 25 ff 48 8d 05 51 87 7a 04 48 8b 0d 81 be d5 05 48 89 01 04 25 00 00 00 00 cb 01 00 00 e8 c6 3e 26 ff 66 2e 0f 1f 84 00 Mar 29 20:53:56 localhost kernel: [23017.464295] traps: firefox[8297] trap int3 ip:7f8f2feaf0d5 sp:7ffe63b051f0 error:0 in libglib-2.0.so.0.6400.1[7f8f2fe73000+84000] Mar 29 20:56:30 localhost kernel: [23171.349753] rfkill: input handler enabled Mar 29 20:56:34 localhost kernel: [23175.671063] ibus-ui-gtk3[6013]: segfault at 7ffe4caeafd0 ip 7f6661e1bfa2 sp 7ffe4caeaed0 error 6 in libc-2.31.so[7f6661dc4000+178000] Mar 29 20:56:34 localhost kernel: [23175.671074] Code: 31 c0 8b 87 c0 00 00 00 48 89 fb 85 c0 0f 85 05 02 00 00 c7 87 c0 00 00 00 ff ff ff ff 48 8d 84 24 20 01 00 00 48 8d 7c 24 20 <48> 89 9c 24 00 01 00 00 66 48 0f 6e c0 48 8d 84 24 20 21 00 00 c7 Mar 30 06:09:53 localhost kernel: [30608.774632] traps: bijiben-shell-s[6791] trap int3 ip:7f78bc38f0d5 sp:7ffc61c652c0 error:0 in libglib-2.0.so.0.6400.1[7f78bc353000+84000] Mar 30 06:09:54 localhost kernel: [30608.874646] traps: nautilus[6777] trap int3 ip:7feefe0c90d5 sp:7ffc5978d400 error:0 in libglib-2.0.so.0.6400.1[7feefe08d000+84000] Mar 30 06:10:15 localhost kernel: [30629.848436] brave[6882]: segfault at 18 ip 55a0be321f27 sp 7fff3aa5ca20 error 4 in brave[55a0b99d8000+7824000] Mar 30 06:10:15 localhost kernel: [30629.848447] Code: 48 83 ec 78 4c 89 c3 49 89 cf 49 89 f4 49 89 fd 89 55 d4 f6 05 d9 c3 5e 03 19 4c 89 4d b0 0f 85 2b 02 00 00 31 c0 48 89 45 c8 <49> 8b 45 18 48 89 45 b8 48 8d 35 af 8e 9b fa 48 8d 15 cd b5 ac fa Mar 30 06:10:16 localhost kernel: [30631.629120] traps: brave[6910] trap int3 ip:55c49796accf sp:7ffedc8b31e0 error:0 in brave[55c4949f5000+7824000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1869755/+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 1807557] Re: Poor keyboard accessibility in the initial setup
The keyboard navigation issue has been fixed in newer Ubuntu versions ** Changed in: gnome-initial-setup (Ubuntu) Status: In Progress => Fix Released -- 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/1807557 Title: Poor keyboard accessibility in the initial setup Status in gnome-initial-setup package in Ubuntu: Fix Released Bug description: I'm not a perfectly sighted user, but I have decent eyesight. However, on a 1080p ThinkPad screen, I have a hard time distinguishing which button is the default in a dialog box. There is a 1px wide orange border around the default button, bit it's not easy to notice, at all. In addition, in the Welcome dialog that asks about sending information to Canonical, it's impossible to use the keyboard to navigate to the "No" choice. I need to use the keyboard because neither the touchpad nor the trackpoint work - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-initial-setup 3.28.0-2ubuntu6.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 8 23:28:07 2018 ExecutablePath: /usr/lib/gnome-initial-setup/gnome-initial-setup InstallationDate: Installed on 2018-12-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1807557/+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 1868360] Re: No superuser access window after upgrade to 20.04
On 2020-03-31 20:32, Igor Zubarev wrote: > It doesn't work in Software and Updates when I push checkboxes in > Other software. That sounds like bug #1727908. Would it be ok with you to make this bug a duplicate of that other one, or do you see similar failures to prompt for a password elsewhere? -- 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/1868360 Title: No superuser access window after upgrade to 20.04 Status in gnome-control-center package in Ubuntu: Incomplete Bug description: After I upgraded to Ubuntu 20.04 I couldn't change settings which required superuser access. For example program sources, users etc. If I try to change I get no modal window with superuser password. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 21 09:37:05 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to focal on 2020-03-12 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1868360/+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 1869905] Re: OnlyShowIn and NotShowIn not properly honored
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- 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/1869905 Title: OnlyShowIn and NotShowIn not properly honored Status in gnome-shell package in Ubuntu: Fix Committed Bug description: glib provides g_app_info_should_show to determine if a desktop file should be shown in the app grid based on OnlyShowIn and NotShowIn using XDG_CURRENT_DESKTOP. This isn't being honored in gnome-shell when NotShowIn=ubuntu:GNOME or OnlyShowIn=ubuntu:GNOME and XDG_CURRENT_DESKTOP is ubuntu:GNOME. glib does have tests for this that are still passing and @seb128 wrote a simple test case to show the glib API does the right thing. The snap-store snap in the beta channel provides two desktop files, one to be displayed when XDG_CURRENT_DESKTOP is ubuntu:GNOME and one for when it isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869905/+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 1868085] Re: Bug related to the new kernel version 5.3.0-42-generic
I confirm the ACPI problems using the sof drivers starting from 5.3.0-40, is there something i can use to debug back from sleep issue ? -- 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/1868085 Title: Bug related to the new kernel version 5.3.0-42-generic Status in alsa-driver package in Ubuntu: Incomplete Bug description: Hi all, After an update of Ubuntu kernel (version 5.3.0-42-generic) I can't have sound any more. No soundcards are detected any I have a "dummy output" in the sound pannel in settings. Furthermore I can't resume from sleep anymore. Output of ALSA Information script: !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Wed Mar 18 14:46:19 UTC 2020 !!Linux Distribution !!-- Ubuntu 18.04.4 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=bionic !!DMI Information !!--- Manufacturer: HP Product Name: HP ZBook 15u G6 Product Version: Firmware Version: R70 Ver. 01.03.04 Board Vendor: HP Board Name:8549 !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI000C:00/status 15 /sys/bus/acpi/devices/HPIC000C:00/status 15 /sys/bus/acpi/devices/HPQ6001:00/status15 /sys/bus/acpi/devices/IFX0785:00/status15 /sys/bus/acpi/devices/INT3400:00/status15 /sys/bus/acpi/devices/INT3403:00/status15 /sys/bus/acpi/devices/INT3403:01/status15 /sys/bus/acpi/devices/INT340E:00/status15 /sys/bus/acpi/devices/INT34BB:00/status15 /sys/bus/acpi/devices/INT3F0D:00/status15 /sys/bus/acpi/devices/LNXPOWER:00/status 15 /sys/bus/acpi/devices/LNXPOWER:02/status 1 /sys/bus/acpi/devices/LNXPOWER:03/status 1 /sys/bus/acpi/devices/LNXPOWER:05/status 1 /sys/bus/acpi/devices/LNXPOWER:06/status 1 /sys/bus/acpi/devices/LNXPOWER:07/status 1 /sys/bus/acpi/devices/LNXPOWER:08/status 1 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0B00:00/status15 /sys/bus/acpi/devices/PNP0C02:00/status3 /sys/bus/acpi/devices/PNP0C02:01/status3 /sys/bus/acpi/devices/PNP0C02:05/status3 /sys/bus/acpi/devices/PNP0C09:00/status15 /sys/bus/acpi/devices/PNP0C0A:00/status31 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PRP1:00/status 11 /sys/bus/acpi/devices/SYNA3092:00/status 15 /sys/bus/acpi/devices/USBC000:00/status15 /sys/bus/acpi/devices/device:04/status 15 /sys/bus/acpi/devices/device:27/status 15 /sys/bus/acpi/devices/device:28/status 15 /sys/bus/acpi/devices/device:4c/status 15 !!Kernel Information !!-- Kernel release:5.3.0-42-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-42-generic Library version:1.1.3 Utilities version: 1.1.3 !!Loaded ALSA modules !!--- !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- --- no soundcards --- !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:9dc8] (rev 11) Subsystem: Hewlett-Packard Company Device [103c:8549] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 !!Loaded sound module options !!--- !!ALSA Device nodes !!- crw-rw 1 root audio 116, 1 Mar 18 14:45 /dev/snd/seq crw-rw 1 root audio 116, 33 Mar 18 14:44 /dev/snd/timer !!Aplay/Arecord output !! APLAY aplay:
[Desktop-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
I see this issue in focal. Nothing happens if I try to enable or disable a source in the "Other Software" tab by clicking a checkbox. I get the same error message as mentioned in comment #2 if I start software- properties-gtk in terminal. Adding or removing sources works, but not enabling/disabling them. ** Tags added: focal -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Confirmed Status in software-properties source package in Bionic: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+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 1869945] [NEW] design flaw: application menu.
Public bug reported: Bad design. The inscriptions do not fit into their places in the application menu. Look at the attachment. Плохой дизайн. Надписи не вписываются в свои места в меню приложений. Смотрите вложение. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 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.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 12:06:39 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2020-03-30 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. VMware Virtual USB Mouse Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=1ed2509c-6bde-4abc-80f6-2cf45bec3d55 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan fonts ubuntu ** Attachment added: "Снимок экрана от 2020-03-31 12-00-57.png" https://bugs.launchpad.net/bugs/1869945/+attachment/5343903/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202020-03-31%2012-00-57.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1869945 Title: design flaw: application menu. Status in xorg package in Ubuntu: New Bug description: Bad design. The inscriptions do not fit into their places in the application menu. Look at the attachment. Плохой дизайн. Надписи не вписываются в свои места в меню приложений. Смотрите вложение. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 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.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 12:06:39 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2020-03-30 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. VMware Virtual USB Mouse Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=1ed2509c-6bde-4abc-80f6-2cf45bec3d55 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00
[Desktop-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution
So in general, syntax errors in translations just cause a warning, and
the original text is used. itstool only errors on syntax if you pass
--strict, and yelp.m4 doesn't even give you a way to pass --strict.
There's a chance this is itstool's fault. You do still have to do memory
management with libxml2's Python bindings, so stuff like double frees in
application code is possible. But since this crash happens during error
reporting for a language with many-byte UTF-8 chars, and since it
weirdly only happens with Python 3, I suspect it's this libxml2 bug:
https://bugzilla.gnome.org/show_bug.cgi?id=789714
** Bug watch added: bugzilla.gnome.org/ #789714
https://bugzilla.gnome.org/show_bug.cgi?id=789714
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
Status in itstool package in Ubuntu:
Invalid
Status in libxml2 package in Ubuntu:
New
Status in ubuntu-docs package in Ubuntu:
Fix Committed
Bug description:
ubuntu-docs failed to build during the second Focal Fossa test
rebuild:
https://launchpad.net/ubuntu/+archive/test-
rebuild-20200327-focal/+build/18982738
It was itstool which failed to generate the localized zh_CN pages. If
dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
excluding the Chinese pages is apparently not an acceptable solution.
The itstool package in focal {build-,}depends on python3. I built
itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
built fine without modifications:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages
So the root cause seems to lie neither in ubuntu-docs nor itstool. I
would suspect that python3-libxml2 is buggy, but since itstool was
built against python2 in eoan, it's hard to tell if it's a regression.
Would building itstool against python2 be an acceptable workaround in
focal?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1869940] [NEW] No networks available/visible after suspend
Public bug reported: WiFI network disconnected and no networks visible after resume from suspend. Had to reboot the machine to get networking (WiFI) back up and running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 21:18:43 2020 InstallationDate: Installed on 2020-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) IpRoute: default via 192.168.1.1 dev wlp59s0 proto dhcp metric 600 169.254.0.0/16 dev wlp59s0 scope link metric 1000 192.168.1.0/24 dev wlp59s0 proto kernel scope link src 192.168.1.30 metric 600 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 DORIAN 2c3f821d-0865-4747-974a-2f861ee0dc38 wifi 1585682245 tis 31 mar 2020 21:17:25 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp59s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /etc/NetworkManager/system-connections/DORIAN.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp59s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 DORIAN 2c3f821d-0865-4747-974a-2f861ee0dc38 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp59s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1869940 Title: No networks available/visible after suspend Status in network-manager package in Ubuntu: New Bug description: WiFI network disconnected and no networks visible after resume from suspend. Had to reboot the machine to get networking (WiFI) back up and running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 21:18:43 2020 InstallationDate: Installed on 2020-03-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) IpRoute: default via 192.168.1.1 dev wlp59s0 proto dhcp metric 600 169.254.0.0/16 dev wlp59s0 scope link metric 1000 192.168.1.0/24 dev wlp59s0 proto kernel scope link src 192.168.1.30 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME DORIAN 2c3f821d-0865-4747-974a-2f861ee0dc38 wifi 1585682245 tis 31 mar 2020 21:17:25 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp59s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /etc/NetworkManager/system-connections/DORIAN.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp59s0 wifi connected full limited
[Desktop-packages] [Bug 1869913] Re: "Click or press a key to unlock" string not translated into french
Thanks for reporting. I couldn't find "Click or press a key to unlock" among the translatable strings for gdm3, looks like it might be in gnome-shell instead https://translations.launchpad.net/ubuntu/focal/+source/gnome- shell/+pots/gnome-shell/fr/453/+translate. The good news is that has been recently translated. I am not sure how often they are updated, but I believe this should make it into a new language pack version before release of 20.04. (Judging by the release schedule https://wiki.ubuntu.com/FocalFossa/ReleaseSchedule the deadline for language packs is April 16th, but I would expect to see it in an update sooner) -- 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/1869913 Title: "Click or press a key to unlock" string not translated into french Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: On the lockscreen, the "Click or press a key to unlock" string is not translated, at least in french. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 14:56:11 2020 InstallationDate: Installed on 2019-02-21 (404 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-03-20 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1869913/+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 1869913] Re: "Click or press a key to unlock" string not translated into french
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1869913 Title: "Click or press a key to unlock" string not translated into french Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: On the lockscreen, the "Click or press a key to unlock" string is not translated, at least in french. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 14:56:11 2020 InstallationDate: Installed on 2019-02-21 (404 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-03-20 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1869913/+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 1753263] Re: GNOME Power Statistics shows nothing on Ubuntu 18.04
** Changed in: gnome-power-manager (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-power-manager (Ubuntu) Assignee: (unassigned) => Aung Aung (dawsanyee186) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1753263 Title: GNOME Power Statistics shows nothing on Ubuntu 18.04 Status in gnome-power-manager package in Ubuntu: Incomplete Bug description: GNOME Power Statistics shows nothing on Ubuntu 18.04, just the "cannot enable timerstats" error. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1753263/+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 1730231] Re: Nautilus opens for every mediafile a seperate player when selecting a group of files and pressing Enter
** Changed in: nautilus Status: Unknown => New -- 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/1730231 Title: Nautilus opens for every mediafile a seperate player when selecting a group of files and pressing Enter Status in Nautilus: New Status in nautilus package in Ubuntu: Triaged Bug description: Expected behavior: The Player selected as standard opens with a playlist of the (media)files. (This is what actually happens if you select an application with the open with ... dialog) What happens: Nautilus launches for each file a separate instance of the standard-application. Example: 10 mp3 files selected opens 10 player-windows of audacious, qmmp, vlc, mpv or what ever is selected as standard. (I did try all of the named programs) This happens only if the group of files is open via pressing Return or selecting 'open' in context-menu. It does not happen when selecting an application via 'open with ...' in context-menu. Same behavior with groups of png or jpg files and photo-viewers. Reconstruction: 1. Open Nautilus 2. Set a mediaplayer as standard-application for mp3-files. 3. Open a group of mp3-files by selecting them and pressing 'Enter' or using the 'Open'-Item in the context-menu ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Nov 5 21:02:23 2017 InstallationDate: Installed on 2017-10-28 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1730231/+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 1868360] Re: No superuser access window after upgrade to 20.04
Very strange. It doesn't work in Software and Updates when I push checkboxes in Other software. But works in Control Center-> Users when click Unlock. Also I remember that before last update it worked also in Software and Updates -- 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/1868360 Title: No superuser access window after upgrade to 20.04 Status in gnome-control-center package in Ubuntu: Incomplete Bug description: After I upgraded to Ubuntu 20.04 I couldn't change settings which required superuser access. For example program sources, users etc. If I try to change I get no modal window with superuser password. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 21 09:37:05 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to focal on 2020-03-12 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1868360/+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 1869905] Re: OnlyShowIn and NotShowIn not properly honored
Handled as per https://gitlab.gnome.org/GNOME/gnome- shell/-/merge_requests/1156 ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** 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/1869905 Title: OnlyShowIn and NotShowIn not properly honored Status in gnome-shell package in Ubuntu: In Progress Bug description: glib provides g_app_info_should_show to determine if a desktop file should be shown in the app grid based on OnlyShowIn and NotShowIn using XDG_CURRENT_DESKTOP. This isn't being honored in gnome-shell when NotShowIn=ubuntu:GNOME or OnlyShowIn=ubuntu:GNOME and XDG_CURRENT_DESKTOP is ubuntu:GNOME. glib does have tests for this that are still passing and @seb128 wrote a simple test case to show the glib API does the right thing. The snap-store snap in the beta channel provides two desktop files, one to be displayed when XDG_CURRENT_DESKTOP is ubuntu:GNOME and one for when it isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869905/+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 1864644] Re: I get logged out immediately after login to an X session (QXL Xorg driver on kernel 5.4)
Yes, this is fixed in today's build of Focal Fossa. The bug can be closed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1864644 Title: I get logged out immediately after login to an X session (QXL Xorg driver on kernel 5.4) Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in xserver-xorg-video-qxl package in Ubuntu: Invalid Status in systemd source package in Focal: Fix Released Status in xserver-xorg-video-qxl source package in Focal: Invalid Bug description: I just installed ubuntu 20.04 in a virtual machine and did 'apt-get update;apt-get upgrade' to get current (using Ctl-Alt-F2 to get a non-X session). After that, I tried logging in to a gnome session, and got logged out during login processing. This happened a few times; then I installed xfce4, rebooted, and got the same behaviour (logout during login processing) while trying to log in to an xfce session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 Date: Tue Feb 25 12:06:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2020-02-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=14c5cf63-466a-44d5-add6-bd5fc486c067 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-eoan dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-eoan:cvnQEMU:ct1:cvrpc-i440fx-eoan: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-eoan dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 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+git20190815-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/systemd/+bug/1864644/+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 1869924] [NEW] High power consumption by Intel iGPU on Skylake+
Public bug reported: There is an outstanding regression in i915 that breaks the RC6 power state for Intel iGPUs on Skylake and newer. This bug was fixed upstream in Linux 5.5. I submitted a backport of the fix for 5.4 upstream [1]. My cover letter [2] describes the issue: The first bug, fixed by "drm/i915/gt: Schedule request retirement when timeline idles" upstream, is very high power consumption by i915 hardware due to an old commit that broke the RC6 power state for the iGPU on Skylake+. On my laptop, a Dell Precision 5540 with an i9-9880H, the idle power consumption of my laptop with this commit goes down from 10 W to 2 W, saving a massive 8 W of power. On other Skylake+ laptops I tested, this commit reduced idle power consumption by at least a few watts. The difference in power consumption can be observed by running `powertop` while disconnected from the charger, or by using the intel-undervolt tool [1] and running `intel-undervolt measure` which doesn't require being disconnected from the charger. The psys measurement from intel-undervolt is the one of interest. Backporting this commit was not trivial due to i915's high rate of churn, but the backport didn't require changing any code from the original commit; it only required moving code around and not altering some #includes. [1] https://lore.kernel.org/stable/20200330033057.2629052-3-sul...@kerneltoast.com/ [2] https://lore.kernel.org/stable/20200330033057.2629052-1-sul...@kerneltoast.com/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Incomplete ** Also affects: linux Importance: Undecided Status: New ** No longer affects: lightdm (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Description changed: There is an outstanding regression in i915 that breaks the RC6 power state for Intel iGPUs on Skylake and newer. This bug was fixed upstream in Linux 5.5. I submitted a backport of the fix for 5.4 upstream [1]. My cover letter [2] describes the issue: - The first bug, fixed by - "drm/i915/gt: Schedule request retirement when timeline idles" upstream, is very - high power consumption by i915 hardware due to an old commit that broke the RC6 - power state for the iGPU on Skylake+. On my laptop, a Dell Precision 5540 with - an i9-9880H, the idle power consumption of my laptop with this commit goes down - from 10 W to 2 W, saving a massive 8 W of power. On other Skylake+ laptops I - tested, this commit reduced idle power consumption by at least a few watts. The - difference in power consumption can be observed by running `powertop` while - disconnected from the charger, or by using the intel-undervolt tool [1] and - running `intel-undervolt measure` which doesn't require being disconnected from - the charger. The psys measurement from intel-undervolt is the one of interest. + The first bug, fixed by "drm/i915/gt: Schedule request retirement when timeline idles" upstream, is very high power consumption by i915 hardware due to an old commit that broke the RC6 power state for the iGPU on Skylake+. On my laptop, a Dell Precision 5540 with an i9-9880H, the idle power consumption of my laptop with this commit goes down from 10 W to 2 W, saving a massive 8 W of power. On other Skylake+ laptops I tested, this commit reduced idle power consumption by at least a few watts. The difference in power consumption can be observed by running `powertop` while disconnected from the charger, or by using the intel-undervolt tool [1] and running `intel-undervolt measure` which doesn't require being disconnected from the charger. The psys measurement from intel-undervolt is the one of interest. - Backporting this commit was not trivial due to i915's high rate of churn, but - the backport didn't require changing any code from the original commit; it only - required moving code around and not altering some #includes. - + Backporting this commit was not trivial due to i915's high rate of + churn, but the backport didn't require changing any code from the + original commit; it only required moving code around and not altering + some #includes. [1] https://lore.kernel.org/stable/20200330033057.2629052-3-sul...@kerneltoast.com/ [2] https://lore.kernel.org/stable/20200330033057.2629052-1-sul...@kerneltoast.com/ -- 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/1869924 Title: High power consumption by Intel iGPU on Skylake+ Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: There is an outstanding regression in i915 that breaks the RC6 power state for Intel iGPUs on Skylake
[Desktop-packages] [Bug 1869591] Re: After install the window 'ready to go' is locked
This bug was fixed in the package gnome-initial-setup - 3.36.0-1ubuntu4 --- gnome-initial-setup (3.36.0-1ubuntu4) focal; urgency=medium * debian/patches/0001-Add-Ubuntu-mode-with-special-pages.patch: - use ubuntu-software to browse available softwares, fallback to using gnome-software if it's missing (lp: #1869591) -- Sebastien Bacher Tue, 31 Mar 2020 17:27:03 +0200 ** Changed in: gnome-initial-setup (Ubuntu) Status: Triaged => Fix Released -- 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/1869591 Title: After install the window 'ready to go' is locked Status in gnome-initial-setup package in Ubuntu: Fix Released Bug description: Just installed from Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) gnome-initial-setup shows the window 'ready to go' the window can not be moved on screen and click on 'Open software now' has no effect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-initial-setup 3.36.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 29 17:14:57 2020 ExecutablePath: /usr/libexec/gnome-initial-setup InstallationDate: Installed on 2020-03-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1869591/+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 1869652] Re: 1:6.4.2-0ubuntu2 breaks universe enabled ISO builds where libreoffice is seeded
This bug was fixed in the package libreoffice - 1:6.4.2-0ubuntu3 --- libreoffice (1:6.4.2-0ubuntu3) focal; urgency=medium * Prevent -nogui and non -nogui mix up (LP: #1869652) -- Rico Tzschichholz Mon, 30 Mar 2020 10:16:03 +0200 ** Changed in: libreoffice (Ubuntu) Status: In Progress => Fix Released -- 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/1869652 Title: 1:6.4.2-0ubuntu2 breaks universe enabled ISO builds where libreoffice is seeded Status in libreoffice package in Ubuntu: Fix Released Bug description: 1:6.4.2-0ubuntu2 breaks Focal ISO builds where libreoffice is seeded e.g. https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/focal/ubuntu-mate/+build/209527 https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/focal/kubuntu/+build/209553 https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/focal/xubuntu/+build/209524 The following packages have unmet dependencies: libreoffice-core : Conflicts: libreoffice-core-nogui but 1:6.4.2-0ubuntu2 is to be installed libreoffice-core-nogui : Conflicts: libreoffice-core but 1:6.4.2-0ubuntu2 is to be installed Breaks: libreoffice-calc but 1:6.4.2-0ubuntu2 is to be installed Breaks: libreoffice-gtk3 but 1:6.4.2-0ubuntu2 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869652/+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 1730231] Re: Nautilus opens for every mediafile a seperate player when selecting a group of files and pressing Enter
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #117 https://gitlab.gnome.org/GNOME/nautilus/issues/117 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/117 Importance: Unknown Status: Unknown -- 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/1730231 Title: Nautilus opens for every mediafile a seperate player when selecting a group of files and pressing Enter Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: Expected behavior: The Player selected as standard opens with a playlist of the (media)files. (This is what actually happens if you select an application with the open with ... dialog) What happens: Nautilus launches for each file a separate instance of the standard-application. Example: 10 mp3 files selected opens 10 player-windows of audacious, qmmp, vlc, mpv or what ever is selected as standard. (I did try all of the named programs) This happens only if the group of files is open via pressing Return or selecting 'open' in context-menu. It does not happen when selecting an application via 'open with ...' in context-menu. Same behavior with groups of png or jpg files and photo-viewers. Reconstruction: 1. Open Nautilus 2. Set a mediaplayer as standard-application for mp3-files. 3. Open a group of mp3-files by selecting them and pressing 'Enter' or using the 'Open'-Item in the context-menu ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Nov 5 21:02:23 2017 InstallationDate: Installed on 2017-10-28 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1730231/+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 1869923] [NEW] lightdm crashes on login to system 20.04
Public bug reported: Ubuntu MATE 20.04 updated 03312020 Hesitation on login to system Login successful System reports error and crash file located in /var/crash ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu3.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-0ubuntu21 Architecture: amd64 CurrentDesktop: MATE Date: Tue Mar 31 11:13:52 2020 InstallationDate: Installed on 2019-12-13 (109 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20191213) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.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 third-party-packages -- 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/1869923 Title: lightdm crashes on login to system 20.04 Status in lightdm package in Ubuntu: New Bug description: Ubuntu MATE 20.04 updated 03312020 Hesitation on login to system Login successful System reports error and crash file located in /var/crash ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu3.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-0ubuntu21 Architecture: amd64 CurrentDesktop: MATE Date: Tue Mar 31 11:13:52 2020 InstallationDate: Installed on 2019-12-13 (109 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20191213) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.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/1869923/+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 1869897] Re: missing ssh prompt to touch yubikey device when using gnome
** Description changed: I can't exactly pinpoint which gnome package is responsible for this. It might be gnome-keyring. Let's go with gnome-shell first. - TL;DR openssh 8.2p1 in focal has support for U2F authentication. This is - a new feature we will highlight in the release notes and a blog post. + openssh 8.2p1[1] in focal has support for U2F authentication. This is a + new feature we will highlight in the release notes and a blog post. You can create a keypair and the authentication only succeeds if you have the u2f hardware device plugged in, and touch it at the moment of authentication. In a console only env, it works like this: """ andreas@nsnx:~$ env|grep SSH andreas@nsnx:~$ ssh -i .ssh/id_ecdsa_sk 10.0.100.75 Confirm user presence for key ECDSA-SK SHA256:bS6vX6b+Bp8Xu/LF4Gw10dV0Y6AkjFPjPoO5q0A546M Welcome to Ubuntu Focal Fossa (development branch) (GNU/Linux 5.4.0-21-generic x86_64) ... Last login: Tue Mar 31 13:35:44 2020 from 10.0.100.1 """ The "Confirm" prompt is asking the user to touch the hardware device (a yubikey in this case). If I use openssh's ssh-agent, it still works as expected and I see that prompt: """ andreas@nsnx:~$ env|grep SSH andreas@nsnx:~$ eval $(ssh-agent) Agent pid 68267 andreas@nsnx:~$ env|grep SSH SSH_AUTH_SOCK=/tmp/ssh-75OwXd9gR6tq/agent.68252 SSH_AGENT_PID=68267 andreas@nsnx:~$ ssh -i .ssh/id_ecdsa_sk 10.0.100.75 Warning: Permanently added '10.0.100.75' (ECDSA) to the list of known hosts. Confirm user presence for key ECDSA-SK SHA256:bS6vX6b+Bp8Xu/LF4Gw10dV0Y6AkjFPjPoO5q0A546M Welcome to Ubuntu Focal Fossa (development branch) (GNU/Linux 5.4.0-21-generic x86_64) (...) Last login: Tue Mar 31 14:33:18 2020 from 10.0.100.1 """ But with "gnome's ssh-agent" (I'm waving my hands here a bit), it just stalls. The prompt is swallowed by something. Here I opened a new gnome terminal in my existing focal desktop session: """ andreas@nsnx:~$ env|grep SSH SSH_AUTH_SOCK=/run/user/1000/keyring/ssh SSH_AGENT_PID=4655 andreas@nsnx:~$ ssh -i .ssh/id_ecdsa_sk 10.0.100.75 """ It only moves forward if I touch the device, which is expected. But the "Confirm user presence" prompt is nowhere to be seen. I'm not sure how gnome-keyring interacts with ssh-agent. I see it is spawned by gnome-keyring-daemon: 4556 ?Sl 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login 6449 ?S 0:00 \_ /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh But the PID referenced by the SSH_AGENT_PID shell variable above points to another copy, spawned by gnome-session-binary: 4583 tty3 Sl+0:00 \_ /usr/libexec/gnome-session-binary --systemd --systemd --session=ubuntu 4655 ?Ss 0:00 \_ /usr/bin/ssh-agent /usr/bin/im-launch env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session --systemd --session=ubuntu In any case, the actual prompt "Confirm user presence for key" comes from openssh code: ./ssh-agent.c:"Confirm user presence for key %s %s", ./sshconnect2.c: "Confirm user presence for key %s %s", My guess is that the gnome wrapper, whatever it is, is not expecting that prompt. + + 1. https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869897 + + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 11:29:06 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-13 (169 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-30 (60 days ago) -- 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/1869897 Title: missing ssh prompt to touch yubikey device when using gnome Status in gnome-shell package in Ubuntu: New Bug description: I can't exactly pinpoint which gnome package is responsible for this. It might be gnome-keyring. Let's go with gnome-shell first. openssh 8.2p1[1] in focal has support for U2F authentication. This is a new feature we will highlight in the release notes and a blog post. You can create a keypair and the authentication only succeeds if you have the u2f hardware device plugged in, and touch it at the moment of authentication. In a console only env, it works like this: """ andreas@nsnx:~$ env|grep SSH andreas@nsnx:~$ ssh -i .ssh/id_ecdsa_sk 10.0.100.75 Confirm user presence for key ECDSA-SK
[Desktop-packages] [Bug 1869920] [NEW] no sound
Public bug reported: cat /proc/asound/cards cat /proc/asound/cards 0 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xffb64000 irq 43 1 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xffb6 irq 16 aplay /usr/share/sounds/alsa/Front_Center.wav ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave aplay: main:788: Fehler beim Öffnen des Gerätes: Datei oder Verzeichnis nicht gefunden lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 apt-cache policy pkgname N: Paket pkgname kann nicht gefunden werden. http://alsa-project.org/db/?f=faeda5de343b2d29e504e3ba0e8fdc20818d5f02 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: klaus 14375 F alsamixer CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Mar 31 18:41:50 2020 InstallationDate: Installed on 2018-07-05 (635 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to bionic on 2018-09-01 (577 days ago) dmi.bios.date: 10/27/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.name: QC5000-ITX/PH dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd10/27/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnQC5000-ITX/PH:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1869920 Title: no sound Status in alsa-driver package in Ubuntu: New Bug description: cat /proc/asound/cards cat /proc/asound/cards 0 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xffb64000 irq 43 1 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xffb6 irq 16 aplay /usr/share/sounds/alsa/Front_Center.wav ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave aplay: main:788: Fehler beim Öffnen des Gerätes: Datei oder Verzeichnis nicht gefunden lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 apt-cache policy pkgname N: Paket pkgname kann nicht gefunden werden. http://alsa-project.org/db/?f=faeda5de343b2d29e504e3ba0e8fdc20818d5f02 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: klaus 14375 F alsamixer CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Mar 31 18:41:50 2020 InstallationDate: Installed on 2018-07-05 (635 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to bionic on 2018-09-01 (577 days ago) dmi.bios.date: 10/27/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.name: QC5000-ITX/PH dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd10/27/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnQC5000-ITX/PH:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1869920/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1869916] Re: Password field stretches to full password width on login and lock screens
** Tags added: focal ** Package changed: ubuntu => gnome-shell (Ubuntu) -- 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/1869916 Title: Password field stretches to full password width on login and lock screens Status in gnome-shell package in Ubuntu: New Bug description: In 20.04, on both the login screen and the lock screen, when the password is long, after pressing enter the password field will stretch to the right to show the entire password. To test, lock the screen and input a long string of characters into the password field and press enter. Attaching photo of what it looks like. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869916/+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 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
*** This bug is a duplicate of bug 1688018 *** https://bugs.launchpad.net/bugs/1688018 It is impressive how quick there was response and still this and related bug (#1688018) is abandoned for more than 3 years ... > On March 23, 2020 3:08:07 AM PDT, Kiruahxh <1671...@bugs.launchpad.net> wrote: > >*** This bug is a duplicate of bug 1688018 *** > > https://bugs.launchpad.net/bugs/1688018 > > > >It affects me too on Ubuntu 19.04 using OpenConnect VPN > > Ubuntu 19.04 has reached end of life and is no longer supported. Please > upgrade. -- 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/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 Status in network-manager package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: Invalid Bug description: I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS. After recent upgrade of network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution of VPN's server hostnames does not work. Roll back to version 1.2.2-0ubuntu0.16.04.4 solves the problem. Steps for reproducing: 1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 2. connect to VPN via network-manager applet 3. nslookop servername.internal --> ** server can't find servername.internal: NXDOMAIN 4. disconnect from VPN via network-manager applet 5. roll back network-manager via command: sudo apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 6. restart network-manager via sudo service network-manager restart 7. connect to VPN via network-manager applet 8. nslookop servername.internal --> the server is resolved correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 9 19:49:55 2017 InstallationDate: Installed on 2015-10-05 (520 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+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 1869042] Re: all monitor scaling fails due to overlapping monitors
Alberto, do you know what could trigger this? ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Also affects: nvidia-drivers-ubuntu Importance: Undecided Status: 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/1869042 Title: all monitor scaling fails due to overlapping monitors Status in NVIDIA Drivers Ubuntu: New Status in mutter package in Ubuntu: Incomplete Bug description: After an upgrade with focal-proposed this morning, I am unable to set any scaling for any of my monitors without the monitor turning blank for 15 seconds and reverting to 100% scaling. I am using X11 with gnome and proprietary nvidia drivers on Focal. I have 3 monitors attached, all 4K, and my usual setup is to enable fractional scaling, and set all 3 monitors to 150% scaling. Now however, I cannot change the monitors to use any scaling, and even if I disconnect 2 of the monitors to only have a single monitor I still cannot use scaling. Finally note I am just using the Settings window, I haven't fiddled with xrandr at all manually. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Uname: Linux 5.4.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 11:24:05 2020 InstallationDate: Installed on 2019-07-05 (264 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1869042/+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 1869916] [NEW] Password field stretches to full password width on login and lock screens
You have been subscribed to a public bug: In 20.04, on both the login screen and the lock screen, when the password is long, after pressing enter the password field will stretch to the right to show the entire password. To test, lock the screen and input a long string of characters into the password field and press enter. Attaching photo of what it looks like. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- Password field stretches to full password width on login and lock screens https://bugs.launchpad.net/bugs/1869916 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell 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 1863463] Re: Firefox 75 requires nodejs >= 10.19
** Tags added: patch -- 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/1863463 Title: Firefox 75 requires nodejs >= 10.19 Status in firefox package in Ubuntu: Confirmed Status in nodejs package in Ubuntu: In Progress Bug description: Firefox trunk, to become version 75.0 in April 2020, has bumped its nodejs requirement to 10.19 (https://bugzilla.mozilla.org/show_bug.cgi?id=1547823). Firefox 75 Beta starts on March 9th. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1863463/+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 1869159] Re: Opening a pdf from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment
That's seems to be fixed in latest version, probably through this modification: * d/apparmor-profile.abstraction: Allow running dash/bash with inherited AppArmor profile. GDesktopAppInfo in GLib 2.64.x uses a one-line shell script to carry out some setup when launching .desktop files, for example as a URL handler. (Closes: #954013) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1869159 Title: Opening a pdf from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment Status in evince package in Ubuntu: Incomplete Bug description: Opening a pdf file from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment" and the file won't open. When opening the file from its location in Nautilus, that works properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 10:17:17 2020 InstallationDate: Installed on 2019-02-21 (398 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-03-20 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1869159/+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 1800763] Re: After installing the package with version 340.107, the system won't start
I know 18.10 is already unsupported, but I guess it applies to later versions as well. The solution to this is to make gdm use Xorg instead of Wayland. In file /etc/gdm3/custom.conf uncomment the line WaylandEnable=false -- 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/1800763 Title: After installing the package with version 340.107, the system won't start Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: On Ubuntu 18.10, after installing the 340.107 driver, the system hangs with the last line showing [OK] Started GNOME Display Manager. I'm not able to change to another TTY, the system is completely locked. After forced restart, entered recovery mode, with root terminal, and removed the driver, and then the systems starts using the Nouveau drivers. The GPU is a nVidia GeForce 9500GT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1800763/+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 1869913] [NEW] "Click or press a key to unlock" string not translated into french
Public bug reported: On the lockscreen, the "Click or press a key to unlock" string is not translated, at least in french. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 14:56:11 2020 InstallationDate: Installed on 2019-02-21 (404 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-03-20 (11 days ago) ** Affects: gdm3 (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 gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1869913 Title: "Click or press a key to unlock" string not translated into french Status in gdm3 package in Ubuntu: New Bug description: On the lockscreen, the "Click or press a key to unlock" string is not translated, at least in french. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 14:56:11 2020 InstallationDate: Installed on 2019-02-21 (404 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-03-20 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1869913/+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 1869902] Re: foomatic-rip extremely slow on focal for PostScript input files - may affect printing
** Also affects: cups-filters (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1869902 Title: foomatic-rip extremely slow on focal for PostScript input files - may affect printing Status in cups-filters package in Ubuntu: New Status in ghostscript package in Ubuntu: New Bug description: "ghostscript -sDEVICE=bbox" is used to compute the "BoundingBox" of an input file. On focal with ghostscript 9.50~dfsg-5ubuntu3 this is extremely slow for PostScript files (~factor 6 compared to bionic). This may affect printing as e.g. foomatic-rip is using this approach when rendering such a file. Example with a simple (one page) PostScript test page: ghostscript 9.50 on focal: > time gs -q -dNOPAUSE -dBATCH -sDEVICE=bbox testprint.ps real0m16,493s > time gs -q -dNOPAUSE -dBATCH -sDEVICE=bbox -r4000 testprint.ps real0m17,071s > time gs -q -dNOPAUSE -dBATCH -sDEVICE=bbox -r1200 testprint.ps real0m0,980s ghostscript 9.26~dfsg+0-0ubuntu0.18.04.12 on bionic: > time gs -q -dNOPAUSE -dBATCH -sDEVICE=bbox testprint.ps real0m2,697s > time gs -q -dNOPAUSE -dBATCH -sDEVICE=bbox -r4000 testprint.ps real0m2,604s > time gs -q -dNOPAUSE -dBATCH -sDEVICE=bbox -r1200 testprint.ps real0m1,029s As one can see, the default resolution for computing the BoundingBox is 4000dpi. While on bionic the time is basically linear, on focal this takes much longer. Surprisingly for PDF this is no problem at all. I'm not an expert for ghostscript internals, but by strace-ing the beast it seems that 9.26 mallocs a 300MB memory area while 9.50 only allocates at max ~30MB. Maybe this is a problem with internal memory management when the rendered page doesn't fit in the allocated area at high resolutions? Obviously I don't know if this is an upstream bug or a problem with the Ubuntu build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1869902/+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 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
Lenovo Ideapad 300 15Ibr - With Linux microphone work with strong noise and very hard to hear me. But with Windows 7 microphone worked perfect. I tried all of the solutions from this topic - nothing helps -- 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/1596381 Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256 speakers work, it's just the mic not working. sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200 sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0 8 lines make mic working until reboot. thx a lot for ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio CasperVersion: 1.376 CurrentDesktop: Unity Date: Sun Jun 26 23:56:46 2016 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 2 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1596381/+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 1869905] Re: OnlyShowIn and NotShowIn not properly honored
Install the snap-store snap from the beta channel and $ gcc onlyshowin.c -o onlyshowin `pkg-config --cflags --libs gio- unix-2.0` $ grep NotShow /var/lib/snapd/desktop/applications/snap-store_snap-store.desktop NotShowIn=ubuntu $ ./onlyshowin snap-store_snap-store.desktop Display of snap-store_snap-store.desktop in ubuntu:GNOME is false ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- 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/1869905 Title: OnlyShowIn and NotShowIn not properly honored Status in gnome-shell package in Ubuntu: New Bug description: glib provides g_app_info_should_show to determine if a desktop file should be shown in the app grid based on OnlyShowIn and NotShowIn using XDG_CURRENT_DESKTOP. This isn't being honored in gnome-shell when NotShowIn=ubuntu:GNOME or OnlyShowIn=ubuntu:GNOME and XDG_CURRENT_DESKTOP is ubuntu:GNOME. glib does have tests for this that are still passing and @seb128 wrote a simple test case to show the glib API does the right thing. The snap-store snap in the beta channel provides two desktop files, one to be displayed when XDG_CURRENT_DESKTOP is ubuntu:GNOME and one for when it isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869905/+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 1869905] Re: OnlyShowIn and NotShowIn not properly honored
But gnome-shell is listing the entry -- 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/1869905 Title: OnlyShowIn and NotShowIn not properly honored Status in gnome-shell package in Ubuntu: New Bug description: glib provides g_app_info_should_show to determine if a desktop file should be shown in the app grid based on OnlyShowIn and NotShowIn using XDG_CURRENT_DESKTOP. This isn't being honored in gnome-shell when NotShowIn=ubuntu:GNOME or OnlyShowIn=ubuntu:GNOME and XDG_CURRENT_DESKTOP is ubuntu:GNOME. glib does have tests for this that are still passing and @seb128 wrote a simple test case to show the glib API does the right thing. The snap-store snap in the beta channel provides two desktop files, one to be displayed when XDG_CURRENT_DESKTOP is ubuntu:GNOME and one for when it isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869905/+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 1869905] [NEW] OnlyShowIn and NotShowIn not properly honored
Public bug reported: glib provides g_app_info_should_show to determine if a desktop file should be shown in the app grid based on OnlyShowIn and NotShowIn using XDG_CURRENT_DESKTOP. This isn't being honored in gnome-shell when NotShowIn=ubuntu:GNOME or OnlyShowIn=ubuntu:GNOME and XDG_CURRENT_DESKTOP is ubuntu:GNOME. glib does have tests for this that are still passing and @seb128 wrote a simple test case to show the glib API does the right thing. The snap-store snap in the beta channel provides two desktop files, one to be displayed when XDG_CURRENT_DESKTOP is ubuntu:GNOME and one for when it isn't. ** Affects: gnome-shell (Ubuntu) Importance: High Status: New ** Tags: rls-ff-incoming ** Attachment added: "glib test case" https://bugs.launchpad.net/bugs/1869905/+attachment/5343824/+files/onlyshowin.c ** Tags added: rls-ff-incoming -- 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/1869905 Title: OnlyShowIn and NotShowIn not properly honored Status in gnome-shell package in Ubuntu: New Bug description: glib provides g_app_info_should_show to determine if a desktop file should be shown in the app grid based on OnlyShowIn and NotShowIn using XDG_CURRENT_DESKTOP. This isn't being honored in gnome-shell when NotShowIn=ubuntu:GNOME or OnlyShowIn=ubuntu:GNOME and XDG_CURRENT_DESKTOP is ubuntu:GNOME. glib does have tests for this that are still passing and @seb128 wrote a simple test case to show the glib API does the right thing. The snap-store snap in the beta channel provides two desktop files, one to be displayed when XDG_CURRENT_DESKTOP is ubuntu:GNOME and one for when it isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869905/+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
Fun fact: today, after many hours of failed copy/paste with Ubuntu 19.10, things have changed. Copy/paste works perfectly well in LibreOffice and any other software. But if I copy a text in a software and paste it in another software, the text pasted is *different*. For example, I can copy "word1" in Firefox and then paste "word1" in LibreOffice (it works). Then I copy "word2" in LibreOffice and paste "word2" in LibreOffice (it works). Then I paste "word1" in Firefox (it's weird!). At this point, I paste "word2" in LibreOffice and "word1" in Firefox. -- 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 codelite package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released 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 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=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 1869902] [NEW] foomatic-rip extremely slow on focal for PostScript input files - may affect printing
Public bug reported: "ghostscript -sDEVICE=bbox" is used to compute the "BoundingBox" of an input file. On focal with ghostscript 9.50~dfsg-5ubuntu3 this is extremely slow for PostScript files (~factor 6 compared to bionic). This may affect printing as e.g. foomatic-rip is using this approach when rendering such a file. Example with a simple (one page) PostScript test page: ghostscript 9.50 on focal: > time gs -q -dNOPAUSE -dBATCH -sDEVICE=bbox testprint.ps real0m16,493s > time gs -q -dNOPAUSE -dBATCH -sDEVICE=bbox -r4000 testprint.ps real0m17,071s > time gs -q -dNOPAUSE -dBATCH -sDEVICE=bbox -r1200 testprint.ps real0m0,980s ghostscript 9.26~dfsg+0-0ubuntu0.18.04.12 on bionic: > time gs -q -dNOPAUSE -dBATCH -sDEVICE=bbox testprint.ps real0m2,697s > time gs -q -dNOPAUSE -dBATCH -sDEVICE=bbox -r4000 testprint.ps real0m2,604s > time gs -q -dNOPAUSE -dBATCH -sDEVICE=bbox -r1200 testprint.ps real0m1,029s As one can see, the default resolution for computing the BoundingBox is 4000dpi. While on bionic the time is basically linear, on focal this takes much longer. Surprisingly for PDF this is no problem at all. I'm not an expert for ghostscript internals, but by strace-ing the beast it seems that 9.26 mallocs a 300MB memory area while 9.50 only allocates at max ~30MB. Maybe this is a problem with internal memory management when the rendered page doesn't fit in the allocated area at high resolutions? Obviously I don't know if this is an upstream bug or a problem with the Ubuntu build. ** Affects: ghostscript (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1869902 Title: foomatic-rip extremely slow on focal for PostScript input files - may affect printing Status in ghostscript package in Ubuntu: New Bug description: "ghostscript -sDEVICE=bbox" is used to compute the "BoundingBox" of an input file. On focal with ghostscript 9.50~dfsg-5ubuntu3 this is extremely slow for PostScript files (~factor 6 compared to bionic). This may affect printing as e.g. foomatic-rip is using this approach when rendering such a file. Example with a simple (one page) PostScript test page: ghostscript 9.50 on focal: > time gs -q -dNOPAUSE -dBATCH -sDEVICE=bbox testprint.ps real0m16,493s > time gs -q -dNOPAUSE -dBATCH -sDEVICE=bbox -r4000 testprint.ps real0m17,071s > time gs -q -dNOPAUSE -dBATCH -sDEVICE=bbox -r1200 testprint.ps real0m0,980s ghostscript 9.26~dfsg+0-0ubuntu0.18.04.12 on bionic: > time gs -q -dNOPAUSE -dBATCH -sDEVICE=bbox testprint.ps real0m2,697s > time gs -q -dNOPAUSE -dBATCH -sDEVICE=bbox -r4000 testprint.ps real0m2,604s > time gs -q -dNOPAUSE -dBATCH -sDEVICE=bbox -r1200 testprint.ps real0m1,029s As one can see, the default resolution for computing the BoundingBox is 4000dpi. While on bionic the time is basically linear, on focal this takes much longer. Surprisingly for PDF this is no problem at all. I'm not an expert for ghostscript internals, but by strace-ing the beast it seems that 9.26 mallocs a 300MB memory area while 9.50 only allocates at max ~30MB. Maybe this is a problem with internal memory management when the rendered page doesn't fit in the allocated area at high resolutions? Obviously I don't know if this is an upstream bug or a problem with the Ubuntu build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1869902/+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 1868919] Re: Cheese refuses to use webcam
Hi, can we please untag this from 'incomplete' as I believe it should have all the debug data needed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1868919 Title: Cheese refuses to use webcam Status in cheese package in Ubuntu: Incomplete Bug description: Hi, I have a USB webcam attached to my ubuntu machine: Bus 001 Device 002: ID 0c45:600d Microdia TwinkleCam USB camera this device uses gspca_sonixb: gilbahat@meadow:~$ lsmod | grep gspca gspca_sonixb 20480 0 gspca_main 24576 1 gspca_sonixb videobuf2_vmalloc 20480 1 gspca_main videobuf2_v4l2 24576 1 gspca_main videobuf2_common 49152 2 gspca_main,videobuf2_v4l2 videodev 225280 4 gspca_main,videobuf2_v4l2,videobuf2_common,gspca_sonixb the device passes v4l2 tests: $ v4l2-ctl -d /dev/video0 --all Driver Info: Driver name : sonixb Card type: USB camera Bus info : usb-:00:14.0-1 Driver version : 5.4.24 Capabilities : 0x8521 Video Capture Read/Write Streaming Extended Pix Format Device Capabilities Device Caps : 0x0521 Video Capture Read/Write Streaming Extended Pix Format Priority: 2 Video input : 0 (sonixb: ok) Format Video Capture: Width/Height : 352/288 Pixel Format : 'S910' (GSPCA SN9C10X) Field : None Bytes per Line: 352 Size Image: 126720 Colorspace: sRGB Transfer Function : Default (maps to sRGB) YCbCr/HSV Encoding: Default (maps to ITU-R 601) Quantization : Default (maps to Full Range) Flags : Streaming Parameters Video Capture: Frames per second: invalid (0/0) Read buffers : 2 User Controls brightness 0x00980900 (int): min=0 max=255 step=1 default=127 value=127 flags=slider exposure 0x00980911 (int): min=0 max=1023 step=1 default=66 value=66 flags=inactive gain_automatic 0x00980912 (bool) : default=1 value=1 flags=update gain 0x00980913 (int): min=0 max=31 step=1 default=15 value=15 flags=inactive the device even works with vlc when opened as a v4l2 capture device and picture is detected and displayed. however, cheese just insists there is no webcam installed, even when run with -d /dev/video0 on the command line. system details: $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 $ dpkg -l | grep cheese ii cheese 3.34.0-1build1 amd64tool to take pictures and videos from your webcam expected behaviour: /dev/video0 appears on the list of usable devices and cheese uses it observed behaviour: cheese complains about no video devices being available. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-23 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: cheese 3.34.0-1build1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 Tags: focal gstreamer-error Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/09/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0074.2018.0709.1332 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-413 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0074.2018.0709.1332:bd07/09/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-413:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1868919/+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 1005140] Re: libreoffice and firefox don't respect text zoom settings
As per comment #14, also marking invalid re Firefox component of bug report. ** Changed in: firefox (Ubuntu) Status: Incomplete => Invalid -- 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/1005140 Title: libreoffice and firefox don't respect text zoom settings Status in firefox package in Ubuntu: Invalid Status in libreoffice package in Ubuntu: Invalid Bug description: I am on Ubuntu 12.10 Quantal 64bit. System settings -> Universal Access -> View gives the user(possible view impaired one) the opportunity to adjust the system wide text size. Good thing! But the standard programs like Firefox or LibreOffice are not adjusted by this central settings as far as their menues are affected. So, the user experience for view impaired users is that they have to bring their heads everytime they start to use one of this standard programs direct to the screen and search for the menue zoom settings in those programs, which is a strange task for them. Expected: With the Universal Access -> View text size settings it should be possible to adjust also the menu size in the not canonical standard program in the unity launcher panel, which are Firefox and LibreOffice. -- Please mark this ticket as wish. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.4.0-3.8-generic 3.4.0 Uname: Linux 3.4.0-3-generic x86_64 ApportVersion: 2.1-0ubuntu1 Architecture: amd64 Date: Sun May 27 13:24:45 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120510) ProcEnviron: PATH=(custom, no username) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 indicator-datetime 0.3.94-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1005140/+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 1863463] Re: Firefox 75 requires nodejs >= 10.19
** Changed in: nodejs (Ubuntu) Status: Confirmed => In Progress -- 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/1863463 Title: Firefox 75 requires nodejs >= 10.19 Status in firefox package in Ubuntu: Confirmed Status in nodejs package in Ubuntu: In Progress Bug description: Firefox trunk, to become version 75.0 in April 2020, has bumped its nodejs requirement to 10.19 (https://bugzilla.mozilla.org/show_bug.cgi?id=1547823). Firefox 75 Beta starts on March 9th. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1863463/+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 1869876] Re: totem crashed with SIGSEGV in g_mount_spec_get()
*** This bug is a duplicate of bug 1860235 *** https://bugs.launchpad.net/bugs/1860235 ** This bug has been marked a duplicate of bug 1860235 totem crashed with SIGSEGV in g_mount_spec_get() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1869876 Title: totem crashed with SIGSEGV in g_mount_spec_get() Status in Totem: Unknown Status in totem package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/totem/-/issues/411 --- I don't know how it happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu2 Uname: Linux 5.6.0-050600-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 19:29:08 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (484 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7f981803dd09 : mov (%rbx),%rdi PC (0x7f981803dd09) ok source "(%rbx)" (0x7000700070006) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 totem_pl_parser_parse_with_base () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (484 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1869876/+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 1863463] Re: Firefox 75 requires nodejs >= 10.19
I merged nodejs 10.19.0~dfsg-3 from Debian unstable, successfully built and passed autopkgtests for all architectures in a PPA. Attaching here the debdiff for sponsoring, it is also available at https://people.canonical.com/~osomon/sponsoring/nodejs-10.19.0/. ** Patch added: "nodejs-10.17.0-to-10.19.0.debdiff" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1863463/+attachment/5343819/+files/nodejs-10.17.0-to-10.19.0.debdiff -- 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/1863463 Title: Firefox 75 requires nodejs >= 10.19 Status in firefox package in Ubuntu: Confirmed Status in nodejs package in Ubuntu: In Progress Bug description: Firefox trunk, to become version 75.0 in April 2020, has bumped its nodejs requirement to 10.19 (https://bugzilla.mozilla.org/show_bug.cgi?id=1547823). Firefox 75 Beta starts on March 9th. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1863463/+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 1866368] Re: gnome-shell crashed with SIGSEGV in wl_resource_get_version(resource=0x0)
Thanks Rocko. I had this bug too. It used to happen systematically when I moved a Firefox tab over a LibreOffice Writer window. So now, after the gnome-shell 3.36.0-2ubuntu2 update, I tried again and failed to make it crash. Seems fixed. -- 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/1866368 Title: gnome-shell crashed with SIGSEGV in wl_resource_get_version(resource=0x0) Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/d34d7337a4c810ce28fed5c01b0caf7ac53f8b8c --- I had two crashes in a row, in both instances I was moving a Firefox tab from one window out to a new window with drag and drop. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 16:16:03 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: wl_resource_get_version () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGSEGV in wl_resource_get_version() UpgradeStatus: Upgraded to focal on 2019-08-24 (195 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866368/+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 1869897] [NEW] missing ssh prompt to touch yubikey device when using gnome
Public bug reported: I can't exactly pinpoint which gnome package is responsible for this. It might be gnome-keyring. Let's go with gnome-shell first. TL;DR openssh 8.2p1 in focal has support for U2F authentication. This is a new feature we will highlight in the release notes and a blog post. You can create a keypair and the authentication only succeeds if you have the u2f hardware device plugged in, and touch it at the moment of authentication. In a console only env, it works like this: """ andreas@nsnx:~$ env|grep SSH andreas@nsnx:~$ ssh -i .ssh/id_ecdsa_sk 10.0.100.75 Confirm user presence for key ECDSA-SK SHA256:bS6vX6b+Bp8Xu/LF4Gw10dV0Y6AkjFPjPoO5q0A546M Welcome to Ubuntu Focal Fossa (development branch) (GNU/Linux 5.4.0-21-generic x86_64) ... Last login: Tue Mar 31 13:35:44 2020 from 10.0.100.1 """ The "Confirm" prompt is asking the user to touch the hardware device (a yubikey in this case). If I use openssh's ssh-agent, it still works as expected and I see that prompt: """ andreas@nsnx:~$ env|grep SSH andreas@nsnx:~$ eval $(ssh-agent) Agent pid 68267 andreas@nsnx:~$ env|grep SSH SSH_AUTH_SOCK=/tmp/ssh-75OwXd9gR6tq/agent.68252 SSH_AGENT_PID=68267 andreas@nsnx:~$ ssh -i .ssh/id_ecdsa_sk 10.0.100.75 Warning: Permanently added '10.0.100.75' (ECDSA) to the list of known hosts. Confirm user presence for key ECDSA-SK SHA256:bS6vX6b+Bp8Xu/LF4Gw10dV0Y6AkjFPjPoO5q0A546M Welcome to Ubuntu Focal Fossa (development branch) (GNU/Linux 5.4.0-21-generic x86_64) (...) Last login: Tue Mar 31 14:33:18 2020 from 10.0.100.1 """ But with "gnome's ssh-agent" (I'm waving my hands here a bit), it just stalls. The prompt is swallowed by something. Here I opened a new gnome terminal in my existing focal desktop session: """ andreas@nsnx:~$ env|grep SSH SSH_AUTH_SOCK=/run/user/1000/keyring/ssh SSH_AGENT_PID=4655 andreas@nsnx:~$ ssh -i .ssh/id_ecdsa_sk 10.0.100.75 """ It only moves forward if I touch the device, which is expected. But the "Confirm user presence" prompt is nowhere to be seen. I'm not sure how gnome-keyring interacts with ssh-agent. I see it is spawned by gnome-keyring-daemon: 4556 ?Sl 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login 6449 ?S 0:00 \_ /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh But the PID referenced by the SSH_AGENT_PID shell variable above points to another copy, spawned by gnome-session-binary: 4583 tty3 Sl+0:00 \_ /usr/libexec/gnome-session-binary --systemd --systemd --session=ubuntu 4655 ?Ss 0:00 \_ /usr/bin/ssh-agent /usr/bin/im-launch env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session --systemd --session=ubuntu In any case, the actual prompt "Confirm user presence for key" comes from openssh code: ./ssh-agent.c: "Confirm user presence for key %s %s", ./sshconnect2.c:"Confirm user presence for key %s %s", My guess is that the gnome wrapper, whatever it is, is not expecting that prompt. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 11:29:06 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-13 (169 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-30 (60 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne focal ** Description changed: I can't exactly pinpoint which gnome package is responsible for this. It might be gnome-keyring. Let's go with gnome-shell first. - TL;DR openssh 8.2p1 in focal has support for U2F authentication. You can - create a keypair and the authentication only succeeds if you have the - u2f hardware device plugged in, and touch it at the moment of + TL;DR openssh 8.2p1 in focal has support for U2F authentication. This is + a new feature we will highlight in the release notes and a blog post. + + You can create a keypair and the authentication only succeeds if you + have the u2f hardware device plugged in, and touch it at the moment of authentication. In a console only env, it works like this: """ andreas@nsnx:~$ env|grep SSH andreas@nsnx:~$ ssh -i .ssh/id_ecdsa_sk 10.0.100.75 Confirm user presence for key ECDSA-SK SHA256:bS6vX6b+Bp8Xu/LF4Gw10dV0Y6AkjFPjPoO5q0A546M Welcome to Ubuntu Focal Fossa (development branch) (GNU/Linux 5.4.0-21-generic x86_64) ... Last login: Tue Mar 31 13:35:44 2020 from 10.0.100.1 """ The "Confirm" prompt is asking the user to touch the hardware device (a yubikey in this case). - - If I use openssh's
[Desktop-packages] [Bug 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
** Also affects: wpa (Ubuntu Focal) Importance: Medium Status: Triaged ** Tags removed: champagne -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1867908 Title: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length Status in wpa package in Ubuntu: Triaged Status in wpa source package in Focal: Triaged Bug description: Some wifi adapters kept asking for a password when MAC address randomization was enabled. I reported this to Realtek, and they gave me a patch for wpa_supplicant, which fixes the issue. I asked Realtek to report this upstream to wpasupplicant, and they did, the commit is: http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563 It would be very nice to cherrypick that for Focal. I uploaded it as a merge request below, and I tested that it fixes the issue with adapters based on the following chipsets: ath9k, rtl8812au, rtl88x2bu and rtl8821cu To reproduce this: Ubuntu's network-manager defaults to "MAC randomization disabled", I think as a workaround to this specific issue. This is defined in two places: - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf - Some specific drivers in /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. With these, the problem happens in around 10% of the cases. To be able to reproduce it in 100% of the cases, it's best to remove these Ubuntu workarounds. So: - Set "wifi.scan-rand-mac-address=yes" in /etc/NetworkManager/NetworkManager.conf - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. - systemctl stop network-manager - killall wpa_supplicant - systemctl start network-manager Then insert a USB wifi adapter that results in a big name with 15 characters like wlx74ee2ae2436a and try to connect to a wifi network. It will keep asking for a password. Then apply the patch, run the 3 commands above to restart network- manager, and verify that it can now connect properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1867908/+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 1869561] Re: Libreoffice Help does not work
** Tags removed: rls-ff-incoming -- 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/1869561 Title: Libreoffice Help does not work Status in libreoffice package in Ubuntu: Confirmed Status in libreoffice source package in Focal: Confirmed Bug description: In the latest PPA release of Libreoffice, the Help does not work. IN version 6.3.5.2 it is OK. I the version below it returns an error. Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu0.19.10.3 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: x11; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded The Error is: Object not accessible. The object cannot be accessed due to insufficient user rights. The Help used to open the help in a browser window. This latest version seems to try to open the old type of local help (rather than using a browser). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869561/+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 1868019] Re: [FFe] Add method to enable fractional scaling
This bug was fixed in the package gnome-control-center - 1:3.36.1-1ubuntu2 --- gnome-control-center (1:3.36.1-1ubuntu2) focal; urgency=medium [ Robert Ancell ] * debian/patches/ubuntu-scaling-option.patch: - display: Allow fractional scaling to be enabled (lp: #1868019) -- Sebastien Bacher Tue, 31 Mar 2020 11:31:20 +0200 ** Changed in: gnome-control-center (Ubuntu Focal) Status: Triaged => Fix Released -- 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/1868019 Title: [FFe] Add method to enable fractional scaling Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Released Bug description: [Impact] Fractional scaling is currently requires enabling an experimental feature in Mutter to use it. We would like this feature to be easily enabled by users. A lot of modern hardware supports high DPI displays and these are often not usable without some form of fractional scaling. [Test Case] 1. Open Settings 2. Select Displays panels Expected result: Scale can be set to fractional values (e.g. 125%). There is a UI control to enable fractional scaling (disabled by default). Observed result: Scale can only be set to multiples of 100% unless the feature was enabled. No UI control is shown for Fractional scaling. [Regressional Potential] New UI code risks introducing new bugs. Users enabling fractional scaling may trigger new bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1868019/+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 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()
Il mar 31 mar 2020, 12:30 Sebastien Bacher ha scritto: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Please answer these questions: > * Is this reproducible? Sorry i don't know > * If so, what specific steps should we take to recreate this bug? > > This will help us to find and resolve the problem. > > ** Changed in: ibus (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1869484 > > Title: > ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold() > > Status in ibus package in Ubuntu: > Incomplete > > Bug description: > i don't know what's happened > > ProblemType: Crash > DistroRelease: Ubuntu 20.04 > Package: ibus 1.5.22-2ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 > Uname: Linux 5.4.0-18-generic x86_64 > ApportVersion: 2.20.11-0ubuntu21 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Fri Mar 27 23:00:56 2020 > ExecutablePath: /usr/libexec/ibus-ui-gtk3 > InstallationDate: Installed on 2018-08-07 (598 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > ProcCmdline: /usr/libexec/ibus-ui-gtk3 > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=it_IT.UTF-8 >SHELL=/bin/bash > Signal: 6 > SourcePackage: ibus > StacktraceTop: >?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 >g_assertion_message_expr () from > /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 >?? () >?? () >?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 > Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr() > UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > separator: > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1869484/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1869484 Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold() Status in ibus package in Ubuntu: Incomplete Bug description: i don't know what's happened ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.22-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 23:00:56 2020 ExecutablePath: /usr/libexec/ibus-ui-gtk3 InstallationDate: Installed on 2018-08-07 (598 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcCmdline: /usr/libexec/ibus-ui-gtk3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: ibus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1869484/+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 1869561] Re: Libreoffice Help does not work
** Tags added: rls-ff-incoming ** Changed in: libreoffice (Ubuntu) Importance: Undecided => High ** Also affects: libreoffice (Ubuntu Focal) Importance: High Assignee: Heather Ellsworth (hellsworth) Status: Confirmed -- 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/1869561 Title: Libreoffice Help does not work Status in libreoffice package in Ubuntu: Confirmed Status in libreoffice source package in Focal: Confirmed Bug description: In the latest PPA release of Libreoffice, the Help does not work. IN version 6.3.5.2 it is OK. I the version below it returns an error. Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu0.19.10.3 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: x11; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded The Error is: Object not accessible. The object cannot be accessed due to insufficient user rights. The Help used to open the help in a browser window. This latest version seems to try to open the old type of local help (rather than using a browser). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869561/+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 1868409] Re: gnome-{calculator, logs, characters} snaps not removed after the equivalent APT packages are installed on 20.04, and gnome-software APT package not replaced by sna
Hi Naël, yes that's correct. If you wish not to use update-manager,
correcting this will need to be done manually as you've described.
** Also affects: update-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: update-manager (Ubuntu)
Status: New => Triaged
** Changed in: update-manager (Ubuntu)
Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)
** No longer affects: ubuntu-meta (Ubuntu)
** No longer affects: gnome-logs (Ubuntu)
** No longer affects: gnome-characters (Ubuntu)
** No longer affects: gnome-calculator (Ubuntu)
** Changed in: update-manager (Ubuntu)
Importance: Undecided => High
** Changed in: update-manager (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-characters in Ubuntu.
https://bugs.launchpad.net/bugs/1868409
Title:
gnome-{calculator,logs,characters} snaps not removed after the
equivalent APT packages are installed on 20.04, and gnome-software APT
package not replaced by snap-store
Status in update-manager package in Ubuntu:
In Progress
Bug description:
I'm trialing the development release of Ubuntu 20.04, installed in
December and kept up-to-date by regularly running apt full-upgrade.
I understand from [1] that 20.04 will ship
gnome-{calculator,logs,characters} as APT packages rather than snap
apps, and gnome-software as a snap app (called snap-store) rather than
an APT package.
Following an apt full-upgrade in late February, I now have:
* both the snap and the APT versions of gnome-{calculator,logs,characters}
* still only the APT version of gnome-software, no snap-store
Is this normal? A user in the #ubuntu+1 IRC channel reports that a
fresh install of the development release:
* only features the APT versions of gnome-{calculator,logs,characters}
* features the snap-store (but also the APT version of gnome-software)
Are users of older installs of the development release supposed to
manually uninstall the snap versions of
gnome-{calculator,logs,characters} and manually install the snap-
store?
[1] https://discourse.ubuntu.com/t/is-ubuntu-software-going-to-be-
remove-for-snap-snap-store/14542
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1868409/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
This bug was fixed in the package pango1.0 - 1.44.7-2ubuntu2 --- pango1.0 (1.44.7-2ubuntu2) focal; urgency=medium * debian/control.in: - version the provide, that seems needed for some of those closed source softwares (lp: #1869716) -- Sebastien Bacher Mon, 30 Mar 2020 20:58:10 +0200 ** Changed in: pango1.0 (Ubuntu) Status: Fix Committed => 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/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Fix Released Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
** Changed in: pulseaudio (Ubuntu Bionic) Status: New => Triaged ** Changed in: pulseaudio (Ubuntu Focal) Status: New => Triaged ** Changed in: pulseaudio (Ubuntu Bionic) Assignee: (unassigned) => hugh chao (hugh712) ** Changed in: pulseaudio (Ubuntu Focal) Assignee: (unassigned) => hugh chao (hugh712) -- 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/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Triaged Status in pulseaudio source package in Bionic: Triaged Status in pulseaudio source package in Focal: Triaged Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 3-ring headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1869747] Re: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.
It looks like the stacktrace mentions AMDGPU related functions. For the record, I have three graphics devices in this box currently, one from each vendor to allow easily testing apps on each: nVidia, AMD, and Intel. The displays are currently only connected to the nVidia card's outputs. -- 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/1869747 Title: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related. Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I am unsure where the problem stems, but changes since the 25th have caused my system to fail to initialise the Xorg display. The console remains operational for debugging. I am currently using ZFS snapshots to use the system as it was on the 25th of March 2020 because that is the last snapshot before this issue. This bug was captured using ubuntu-bug when booted into the broken (i.e. not working) latest snapshot of my filesystem. The versions of packages from the not broken (i.e. correctly working) earlier snapshot of my filesystem are: libnvidia-cfg1-440:amd64 440.64-0ubuntu2 libnvidia-common-440 440.64-0ubuntu2 libnvidia-compute-440:amd64 440.64-0ubuntu2 libnvidia-compute-440:i386 440.64-0ubuntu2 libnvidia-decode-440:amd64 440.64-0ubuntu2 libnvidia-decode-440:i386440.64-0ubuntu2 libnvidia-encode-440:amd64 440.64-0ubuntu2 libnvidia-encode-440:i386440.64-0ubuntu2 libnvidia-fbc1-440:amd64 440.64-0ubuntu2 libnvidia-fbc1-440:i386 440.64-0ubuntu2 libnvidia-gl-440:amd64 440.64-0ubuntu2 libnvidia-gl-440:i386440.64-0ubuntu2 libnvidia-ifr1-440:amd64 440.64-0ubuntu2 libnvidia-ifr1-440:i386 440.64-0ubuntu2 nvidia-compute-utils-440 440.64-0ubuntu2 nvidia-dkms-440 440.64-0ubuntu2 nvidia-driver-440440.64-0ubuntu2 nvidia-kernel-common-440 440.64-0ubuntu2 nvidia-kernel-source-440 440.64-0ubuntu2 nvidia-prime 0.8.14 nvidia-settings 440.64-0ubuntu1 nvidia-utils-440 440.64-0ubuntu2 xserver-xorg-video-nvidia-440440.64-0ubuntu2 $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-3ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 Date: Mon Mar 30 15:49:12 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes InstallationDate: Installed on 2020-03-03 (26 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7176ku@/vmlinuz-5.4.0-18-generic root=ZFS=rpool/ROOT/ubuntu_7176ku ro quiet splash intel_iommu=on vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22g dmi.board.asset.tag: Default string dmi.board.name: Z170X-UD5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF22g:bd03/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170X-UD5 TH dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
[Desktop-packages] [Bug 1866368] Re: gnome-shell crashed with SIGSEGV in wl_resource_get_version(resource=0x0)
I think this might be fixed in gnome-shell 3.36.0-2ubuntu2 - I can't reproduce my duplicate bug https://bugs.launchpad.net/bugs/1868418 anymore. -- 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/1866368 Title: gnome-shell crashed with SIGSEGV in wl_resource_get_version(resource=0x0) Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/d34d7337a4c810ce28fed5c01b0caf7ac53f8b8c --- I had two crashes in a row, in both instances I was moving a Firefox tab from one window out to a new window with drag and drop. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 16:16:03 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: wl_resource_get_version () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGSEGV in wl_resource_get_version() UpgradeStatus: Upgraded to focal on 2019-08-24 (195 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866368/+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 1869835] Re: Login screen randomly reverts my default keyboard layout to en-US
Seems annoying but we are rls-ff-notfixing for now since there is only one report, we will revisit if other users hit the problem though ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1869835 Title: Login screen randomly reverts my default keyboard layout to en-US Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: I have seen that happening randomly during the 20.04 development cycle, and I think more often in the last week or so, but never consistently: when I turn on my laptop, on the GDM greeter screen the keyboard layout that's selected is en-US, instead of my default preference (fr-bépo). To give an example of the randomness, this is what I did this morning: 1) Cold booted my laptop, selected my user, typed my password, login got denied, looked at the keyboard layout indicator and realized it was en-US instead of fr-bépo 2) Selected fr-bépo in the indicator, typed my password again and successfully logged in (and indicator in the session remained fr-bépo as expected) 3) From the menu, rebooted laptop 4) On the GDM login screen, keyboard layout indicator was reverted to en-US, again 5) Changed indicator to fr-bépo, logged in, used gnome-terminal and apt to dist-upgrade, then rebooted laptop from menu 6) This time on the GDM login screen, my default preference (fr-bépo) was selected ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 31 07:16:14 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (1367 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-01-12 (78 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869835/+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 1869635] Re: the menu "Dash to Dock Settings" is visible
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Triaged -- 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/1869635 Title: the menu "Dash to Dock Settings" is visible Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: When the user performs a right-button mouse click on the "Show Applications" button of the Ubuntu Dock then a "Dash to Dock Settings" menu option appears as shown in the attached image. Normally, this menu option is only available on the original "Dash to Dock" GNOME shell extension used as the basis for the Ubuntu Dock and it should not be visible or functional on the Ubuntu Dock itself. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 02:31:58 2020 InstallationDate: Installed on 2020-02-12 (46 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-03-27 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1869635/+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 1869814] Re: ubuntu-docs build failure - possible solution
Thanks Sebastien!
Or https://gitlab.gnome.org/GNOME/libxml2/issues/64 (which is not yet
closed).
@Boyuan: Well, it does scream loudly in the sense that the build fails.
I wouldn't blame the build system in this case. It has worked in a
sensible and robust way for many years. The segfault issue only happens
with python3-libxml2, not with python-libxml2. And I have the impression
(not yet confirmed) that the segfault only happens for XML syntax errors
in Chinese translations; for similar errors in non-Chinese translations
it only prints a warning and moves on (which is the desired behavior).
** Bug watch added: gitlab.gnome.org/GNOME/libxml2/issues #64
https://gitlab.gnome.org/GNOME/libxml2/issues/64
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
Status in itstool package in Ubuntu:
Invalid
Status in libxml2 package in Ubuntu:
New
Status in ubuntu-docs package in Ubuntu:
Fix Committed
Bug description:
ubuntu-docs failed to build during the second Focal Fossa test
rebuild:
https://launchpad.net/ubuntu/+archive/test-
rebuild-20200327-focal/+build/18982738
It was itstool which failed to generate the localized zh_CN pages. If
dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
excluding the Chinese pages is apparently not an acceptable solution.
The itstool package in focal {build-,}depends on python3. I built
itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
built fine without modifications:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages
So the root cause seems to lie neither in ubuntu-docs nor itstool. I
would suspect that python3-libxml2 is buggy, but since itstool was
built against python2 in eoan, it's hard to tell if it's a regression.
Would building itstool against python2 be an acceptable workaround in
focal?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1866194] Re: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker
As another work around (for those of us doing online lectures to avoid spread of Covid-19) you can use this gnome extension. https://extensions.gnome.org/extension/906/sound-output-device-chooser/ -- 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/1866194 Title: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker Status in PulseAudio: New Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Focal: In Progress Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1866194/+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
