[Desktop-packages] [Bug 1988754]
I have confirmed that this bug is still present in version 24.2. When inserting a page break followed by undo in the sample document there is a crash. -- 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/1988754 Title: libreoffice writer crashes when edit the page break Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: New Bug description: LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 22.04.1 and also in LinuxMint 21. I have tried also using LibreOffice from ppa and it still crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1988754/+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 2023322]
Hi Craig and Thomas (and Emil if you're still around): if you're still encountering problems with NVIDIA graphics, please report new a bug and leave a comment here linking to the new bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: GTK internal browser does not render with Nvidia drivers Status in Webkit: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-online-accounts package in Ubuntu: Invalid Status in webkit2gtk package in Ubuntu: Fix Released Status in yelp package in Ubuntu: Invalid Status in webkit2gtk package in Debian: Fix Released Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:
[Desktop-packages] [Bug 2046221] Re: Get help with matrix does not lead to ubuntu support
Marking as wishlist per request from OP in IRC ** Changed in: ubuntu-docs (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/2046221 Title: Get help with matrix does not lead to ubuntu support Status in gnome-user-docs package in Ubuntu: Fix Committed Status in ubuntu-docs package in Ubuntu: Confirmed Bug description: Ubuntu-desktop 24.04 development branch @ 12/12/2024 [Current case] Yelp/get more help/Get help with matrix leads only to the Gnome contributors matrix channel [Wishlist] Please also add a section that leads to the Ubuntu support matrix channel(s) #ubuntu-matrix so this can benefit ubuntu support and grow the interest of new users ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: yelp 42.2-1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Dec 12 08:55:49 2023 InstallationDate: Installed on 2023-11-09 (33 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: yelp UpgradeStatus: Upgraded to noble on 2023-11-09 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/2046221/+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 2043407] Re: icons-notifications-counter keeps active after program closes
Setting as wishlist per request from OP. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Wishlist -- 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/2043407 Title: icons-notifications-counter keeps active after program closes Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu desktop 24.04 development branch @ 13/11/2023 with kernel 6.5.0-10-generic With the new icons-notifications-counter enabled the program counts like expected until notification area has been readed and cleaned, the count disappears from the dock icon. But when the program closes, the count number remains active on a pinned icon on the dock would it not be better to remove the count when program closes? ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell-extension-ubuntu-dock 87ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 13 17:50:40 2023 InstallationDate: Installed on 2023-11-09 (4 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to noble on 2023-11-09 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2043407/+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 2042823] Re: Login blank background (gray) after update
Indeed when I unplug the TV HDMI, the login screen appears. Additionally (awesome :D) my HDMI audio is also working with this update! I'll track the bug you mentioned but at least I have this workaround. -- 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/2042823 Title: Login blank background (gray) after update Status in gnome-shell package in Ubuntu: Incomplete Bug description: Today I booted up and the update manager came to inform me I had updates (system was recently updated). I chose to do them because I'm having issues with HDMI audio (and audio in general, only headset via USB works) and it is an NVIDIA GPU. However after reboot, the login screen is just blank with only the gray background. It is still the GUI but just no login box/logo/anything else. I chose xorg as the issue but I'm not certain of it. Not sure how to troubleshoot this as I'm unfamiliar with the inner workings of this. I have since attempted to reinstall the NVIDIA drivers using apt purge ~nnvidia and then reinstalling with ubuntu-drivers autoinstall, as well as reinstalling ubuntu-desktop and related components. I can still log in via terminal. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..05.00.0: Error: path was not a regular file. .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 535.129.03 Thu Oct 19 18:56:32 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Nov 6 11:14:02 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-88-generic, x86_64: installed virtualbox/6.1.38, 6.2.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA102 [GeForce RTX 3080 Lite Hash Rate] [10de:2216] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GA102 [GeForce RTX 3080 Lite Hash Rate] [1043:882e] InstallationDate: Installed on 2021-11-03 (732 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=34735887-8417-4547-843c-9b9b6b7cfbd8 ro quiet splash radeon.audio=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4201 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VIII HERO (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4201:bd04/26/2022:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIIHERO(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 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:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042823/+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 2042823] Re: Login blank background (gray) after update
Indeed I have my TV plugged in as well (even though it is not turned on) via HDMI. That sounds like a plausible bug indeed. I'll try disconnecting the TV and rebooting. -- 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/2042823 Title: Login blank background (gray) after update Status in gnome-shell package in Ubuntu: Incomplete Bug description: Today I booted up and the update manager came to inform me I had updates (system was recently updated). I chose to do them because I'm having issues with HDMI audio (and audio in general, only headset via USB works) and it is an NVIDIA GPU. However after reboot, the login screen is just blank with only the gray background. It is still the GUI but just no login box/logo/anything else. I chose xorg as the issue but I'm not certain of it. Not sure how to troubleshoot this as I'm unfamiliar with the inner workings of this. I have since attempted to reinstall the NVIDIA drivers using apt purge ~nnvidia and then reinstalling with ubuntu-drivers autoinstall, as well as reinstalling ubuntu-desktop and related components. I can still log in via terminal. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..05.00.0: Error: path was not a regular file. .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 535.129.03 Thu Oct 19 18:56:32 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Nov 6 11:14:02 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-88-generic, x86_64: installed virtualbox/6.1.38, 6.2.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA102 [GeForce RTX 3080 Lite Hash Rate] [10de:2216] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GA102 [GeForce RTX 3080 Lite Hash Rate] [1043:882e] InstallationDate: Installed on 2021-11-03 (732 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=34735887-8417-4547-843c-9b9b6b7cfbd8 ro quiet splash radeon.audio=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4201 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VIII HERO (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4201:bd04/26/2022:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIIHERO(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 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:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042823/+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 2008355] Re: Unable to set fractional scaling on three monitor setup
I found this article. I did not work for me completely but it might help someone: https://devicetests.com/set-different-scaling-multi-monitors- gnome -- 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/2008355 Title: Unable to set fractional scaling on three monitor setup Status in gnome-control-center package in Ubuntu: New Bug description: I have three monitors: one 4K (3840x2160) display and two 2560x1440. I've tried setting fractional scaling to 150% on the 4K display in gnome control center (ubuntu 22.10), but it does not work. It works fine when I disconnect some displays, leaving only the 4K or 4k and one 2560. However, when all three are connected the apply button is disabled and the following message appears: "Changes Cannot be Applied. This could be due to hardware limitations." When gnome-control-center is started from terminal it shows the following warning: ``` (gnome-control-center:12235): display-cc-panel-WARNING **: 18:42:27.389: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjacent ``` thought it doesn't seem to be the case. After some digging I've found a workaround, executing the following commands seems to do what the control panel does: ``` xrdb -m
[Desktop-packages] [Bug 2008355] Re: Unable to set fractional scaling on three monitor setup
I have the same problem. Is there an easier way to use fractional scaling when using three screens? -- 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/2008355 Title: Unable to set fractional scaling on three monitor setup Status in gnome-control-center package in Ubuntu: New Bug description: I have three monitors: one 4K (3840x2160) display and two 2560x1440. I've tried setting fractional scaling to 150% on the 4K display in gnome control center (ubuntu 22.10), but it does not work. It works fine when I disconnect some displays, leaving only the 4K or 4k and one 2560. However, when all three are connected the apply button is disabled and the following message appears: "Changes Cannot be Applied. This could be due to hardware limitations." When gnome-control-center is started from terminal it shows the following warning: ``` (gnome-control-center:12235): display-cc-panel-WARNING **: 18:42:27.389: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjacent ``` thought it doesn't seem to be the case. After some digging I've found a workaround, executing the following commands seems to do what the control panel does: ``` xrdb -m
[Desktop-packages] [Bug 2023322]
(In reply to Thomas Zajic from comment #56) > Is this the same bug that is being discussed here? No, because the problem here is specific to GTK 4 and has been around for years. That is, since you didn't have this problem with 2.40, this bug is not your bug. You're probably hitting either bug #259644 or bug #261874, depending on whether or not you see those KMS DRM_IOCTL_MODE_CREATE_DUMB error messages. Please confirm. (In reply to Kdwk from comment #55) > Copied over from the duplicate bug, my setup is the following: > > Tested with: Epiphany Technology Preview/ WebKitGTK 2.41.6; Nvidia RTX 4070 > (driver version 535, via Universal Blue Nvidia Image) > > No web view is rendered. Blank screen. > > Console output: > [kdwk@fedora ~]$ flatpak run org.gnome.Epiphany.Devel > KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied > Failed to create GBM buffer of size 1148x893: Permission denied > KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied > Failed to create GBM buffer of size 1148x893: Permission denied > KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied > Failed to create GBM buffer of size 1148x893: Permission denied > Failed to create EGL images for DMABufs with file descriptors -1, -1 and -1 > [reply] [−] Comment 1 This issue is now tracked in bug #259644. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: Unable to setup Google Online Accounts with Nvidia drivers Status in Webkit: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in webkit2gtk package in Ubuntu: Incomplete Status in webkit2gtk package in Debian: Confirmed Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
[Desktop-packages] [Bug 1741074]
[Olivier has left Canonical](https://phabricator.services.mozilla.com/D140803#5731628) and the patch has been taken over by :bandali. I'm therefore re-assigning the bug for clarity. Also, considering that the majority of the work is in extension code, I'm moving the bug to WebExtensions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: In Progress Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: In Progress Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Status in plasma-browser-integration package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. [Workaround] If you're using Ubuntu 22.04 LTS, you can install GNOME Shell extensions with this app. sudo apt install gnome-shell-extension-manager To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+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 2025538] Re: Unrequested kernel update
This kernel creates problems for me as well, with rootless podman commands. See Bug #2026620 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-nvidia-5.19/+bug/2025538/+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 1992688] Re: firefox deb not installed
FYI, if a user has a 22.04 install where they have explicitly removed snapd/firefox this will add them back. Not sure if this was a consideration in the fix/testing. Also, the apt resolver is pulling in snapd while holding ubuntu-desktop back during staging which made finding the cause of the snapd/firefox installation a bit hard to track down since no packages upgraded in the same unattended-upgrades operation had dependencies on them. (thread: https://hachyderm.io/@rcj4747/110667685702206834) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in firefox source package in Jammy: Invalid Status in ubuntu-meta source package in Jammy: Fix Released Bug description: Impact -- Applications which use x-www-browser to launch a browser will not work on a freshly installed Ubuntu 22.04 system as the firefox deb (which provides x-www-browser) is not installed. Test Plan - 1) Install Ubuntu 22.04.2 using an amd64 desktop iso image 2) Open a terminal 3) Run x-www-browser www.ubuntu.com 4) Observe a command not found message which recommends installing firefox Installing of a daily build of Ubuntu 22.04 with -proposed enabled and ubuntu-desktop version 1.481.1 will not exhibit the above problem. Where problems could occur -- Other Info -- I tested an upgrade from Ubuntu 20.04 to Ubuntu 22.04 and the firefox deb was not removed during the upgrade process so upgrades are a non-issue. Original Description Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+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 2025662] [NEW] mutter pauses for multiple seconds at random times
Public bug reported:
Hi, I have this weird bug in mutter (44.2-0ubuntu1) which seems to
correlate with uptime - if I kill mutter the problem seems to go away
for a few days, although killing mutter is very inconvenient because all
applications are also killed even with session persistence.
Upon strace analysis it can be seen that when the pauses are happening
there is a specific trace involving GEM operations happening immediately
after a ~1 second epoll expires.
During this state the entire UI is paused - video does not update, mouse
cursor does not move, keypresses have no response. However, input
events are "queued" so that when the pause ends, the mouse instantly
warps across the screen, and if a key was down at the time the pause
began, the key is repeated hundreds of times since it seems that the
key-up event is only processed when the "pause" ends.
The system is up to date 23.04 and mutter is using the Intel HD 530
integrated graphics. I do not believe this issue happened before 23.04
was released, although it has been intermittent and persistent since
that time.
Attached a strace with timestamps which provides an example of a multi-
second pause. Using grep -A1 epoll_wait you can see the instances of
the GEM operations during the pause. Eventually at around 09:40:57
local time in the trace the "pause" ended.
Example of an instance of the GEM operation trace after a ~1 second
epoll timeout:
[pid 686436] 09:40:54.750468 poll([{fd=3, events=POLLOUT}], 1, 5) = 1 ([{fd=3,
revents=POLLOUT}])
[pid 686436] 09:40:54.750719 epoll_wait(8, [], 256, 671) = 0
[pid 686436] 09:40:55.422886 ioctl(11, DRM_IOCTL_SYNCOBJ_DESTROY,
0x7ffce0975140) = 0
[pid 686436] 09:40:55.423213 ioctl(11, DRM_IOCTL_I915_GEM_EXECBUFFER2,
0x7ffce09751d0) = 0
[pid 686436] 09:40:55.423525 ioctl(11, DRM_IOCTL_I915_GEM_MADVISE,
0x7ffce0975098) = 0
[pid 686436] 09:40:55.423642 ioctl(11, DRM_IOCTL_SYNCOBJ_WAIT, 0x7ffce0974ef0)
= 0
[pid 686436] 09:40:55.423876 ioctl(11, DRM_IOCTL_I915_GEM_MADVISE,
0x7ffce0974fec) = 0
[pid 686436] 09:40:55.423971 ioctl(11, DRM_IOCTL_SYNCOBJ_CREATE,
0x7ffce0975100) = 0
[pid 686436] 09:40:55.424218 writev(45,
[{iov_base="#\221\360s\0\0\0\0\2\0\0\0\204\v \4\3\0\200\3s\213\0\0\243\v
\4\244\v \4", iov_len=32}], 1) = 32
[pid 686436] 09:40:55.424471 writev(45,
[{iov_base="#\221\360s\2\0\0\0\1\0\0\2\204\v
\4\3\0\200\3r\213\0\0\376S\340\252\37\2\0\0\311uf\0\0\0\0\0", iov_len=40}], 1)
= 40
[pid 686436] 09:40:55.424810 poll([{fd=3, events=POLLOUT}], 1, 5) = 1 ([{fd=3,
revents=POLLOUT}])
[pid 686436] 09:40:55.425150 epoll_wait(8, [], 256, 0) = 0
These pauses are often 10-15 seconds in length but can also be much
longer. I have observed it happening even with the screen locked
(screen lock unresponsive until pause ends).
FD 8 in the trace is anon_inode:[eventpoll] and FD 11 is
/dev/dri/renderD129, the Intel HD 530 DRI device.
Kernel is 6.2.0-24-generic from the distribution.
** Affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "strace.txt"
https://bugs.launchpad.net/bugs/2025662/+attachment/5683579/+files/strace.txt
** Description changed:
Hi, I have this weird bug in mutter which seems to correlate with uptime
- if I kill mutter the problem seems to go away for a few days, although
killing mutter is very inconvenient because all applications are also
killed even with session persistence.
Upon strace analysis it can be seen that when the pauses are happening
there is a specific trace involving GEM operations happening immediately
- after a 1 second epoll expires.
+ after a ~1 second epoll expires.
During this state the entire UI is paused - video does not update, mouse
cursor does not move, keypresses have no response. However, input
events are "queued" so that when the pause ends, the mouse instantly
warps across the screen, and if a key was down at the time the pause
began, the key is repeated hundreds of times since it seems that the
key-up event is only processed when the "pause" ends.
The system is up to date 23.04 and mutter is using the Intel HD 530
integrated graphics. I do not believe this issue happened before 23.04
was released, although it has been intermittent and persistent since
that time.
Attached a strace with timestamps which provides an example of a multi-
second pause. Using grep -A1 epoll_wait you can see the instances of
the GEM operations during the pause. Eventually at around 09:40:57
local time in the trace the "pause" ended.
- Example of an instance of the GEM operation trace after a 1 second epoll
- timeout:
+ Example of an instance of the GEM operation trace after a ~1 second
+ epoll timeout:
[pid 686436] 09:40:54.750468 poll([{fd=3, events=POLLOUT}], 1, 5) = 1
([{fd=3, revents=POLLOUT}])
[pid 686436] 09:40:54.750719 epoll_wait(8, [], 256, 671) = 0
[pid 686436] 09:40:55.422886 ioctl(11, DRM_IOCTL_SYNCOBJ_DESTROY,
0x7ffce0975140) = 0
[pid 686436]
[Desktop-packages] [Bug 1959747]
Did anybody try to start with a clean profile restoring previous and reproduce the error? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1959747 Title: [upstream] Very high CPU and slow responsiveness in Thunderbird 91-102 Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Very high CPU and slow responsiveness in Thunderbird 91.5.0 and later. Just moving the mouse cursor over a message list results in 365% CPU for me. I had to set this in the config editor to fix it: gfx.webrender.force-disabled = TRUE Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1730423 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1959747/+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 2017907] Re: cups-browsed high CPU usage
By stracing, I can see poll() being called in a busy loop with a timeout of 0. The backtrace for these bad poll() calls points to glib (this is a version rebuilt with nostrip and noopt: Thread 1 "cups-browsed" hit Breakpoint 4, __GI___poll (fds=0x555875c39f20, nfds=2, timeout=0) at ../sysdeps/unix/sysv/linux/poll.c:27 27 in ../sysdeps/unix/sysv/linux/poll.c (gdb) bt #0 __GI___poll (fds=0x555875c39f20, nfds=2, timeout=0) at ../sysdeps/unix/sysv/linux/poll.c:27 #1 0x7fe75bb690ee in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe75bb0dbdf in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x555875aa9d41 in main (argc=1, argv=0x7fffa0d9efd8) at daemon/cups-browsed.c:14077 The two fds being polled in this busy loop are: lrwx-- 1 cups-browsed lpadmin 64 May 1 14:29 5 -> 'anon_inode:[eventfd]' lrwx-- 1 cups-browsed lpadmin 64 May 1 14:29 6 -> 'socket:[9085882]' -- 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/2017907 Title: cups-browsed high CPU usage Status in cups-filters package in Ubuntu: Confirmed Bug description: Hi, Using Lunar wifi connected to an enterprise network. cups-browsed uses a lot of CPU %, I need to kill it to save my battery. 2.0rc1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2017907/+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 1959747]
(In reply to Fabian Rodriguez:MagicFab from comment #13) > I see at least two reports confirming this in Mozilla Thunderbird support, > including Windows, Mac and GNU/Linux - and I have the same problem (TB 91.1.2 > on Windows 10). > > This makes Thunderbird slow to the point it can't be used normally. > > A possible workaround was mentioned here : > https://support.mozilla.org/en-US/questions/1347196#answer-1435915 > > > If I go to preferences --> config editor and search for the entries: > > > >gfx.webrender.all > >gfx.webrender.force-disabled > > > > Switch the first one to false (it was already switched to false) and the > > second one to true (I switched this one manually) > > everything works smooths and no cpu usage jumps happen. > > I suggest raising importance/severity. People upgrading seldom backup their > Thunderbird profile and when this happens, all the usual "Thunderbird is > slow" are being tried without a solution, bringing a user closer to stop > using Thunderbird and go to other options. > > A few references to people reporting this problem : > > * https://support.mozilla.org/en-US/questions/1347196 > * https://support.mozilla.org/en-US/questions/1351874 The mentioned parameter (gfx...force-disabled) is gone from configuration in 102 . Reinstating the parm helps some but doesn't fix the 100% CPU utilization. (5.15.0-52-generic #58~20.04.1-Ubuntu SMP on Intel Core i7-2760QM) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1959747 Title: [upstream] Very high CPU and slow responsiveness in Thunderbird 91-102 Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Very high CPU and slow responsiveness in Thunderbird 91.5.0 and later. Just moving the mouse cursor over a message list results in 365% CPU for me. I had to set this in the config editor to fix it: gfx.webrender.force-disabled = TRUE Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1730423 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1959747/+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 1959747]
> Perhaps it's not actually realted to webrender, I just assumed that because > disabling it solved problems in the past. +1. Webrender on/off does not matter here at all. Maybe also worth mentioning: I am on a 10th gen Intel GPU with 6.0.9-zen1-1-zen kernel Boring workaround: Switch to classic view and move the reading pane up until the message list is snappy enough -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1959747 Title: [upstream] Very high CPU and slow responsiveness in Thunderbird 91-102 Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Very high CPU and slow responsiveness in Thunderbird 91.5.0 and later. Just moving the mouse cursor over a message list results in 365% CPU for me. I had to set this in the config editor to fix it: gfx.webrender.force-disabled = TRUE Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1730423 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1959747/+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 1959747]
> It seems that the high CPU usage and slow UI update is worse when the message list is big and the window is big. If I make it that only 10 rows are visible, it seems to be faster. Here is a profile of the mouse moving around a large message list. I can confirm exactly this! Working on a 2 screen setup: main screen: 3840x2160 secondary:2560x1440 Arch Linux, Swaywm. Usually all clients (windows) are maximized. Thunderbird on the main screen has a very bad performance. It is everything else than fun to work with.. :( As soon as i move thunderbird to the second screen (or switch to floating an make it smaller) the performance increases significantly. It seems like only the email list is affected. Folder tree for example is fine.. It's been a long time now and kinda renders thunderbird more or less unusable for me. Is there anything I can do to get this fixed? Happy to provide more information if needed! Thanks for effort :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1959747 Title: [upstream] Very high CPU and slow responsiveness in Thunderbird 91 Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Very high CPU and slow responsiveness in Thunderbird 91.5.0. Just moving the mouse cursor over a message list results in 365% CPU for me. I had to set this in the config editor to fix it: gfx.webrender.force-disabled = TRUE Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1730423 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1959747/+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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Xubuntu 22.04.1 after upgrading from 20.04 In order to get multiple Windows 10 systems to "discover" the samba shares on two different Xubuntu systems, I had to re-enable SMB1 protocol on all the Windows systems. Microsoft apparently keeps disabling this on system updates. As reported above, old Windows mapped drive assignments made to Ubuntu samba shares have continued to work over time, but new shares cannot be seen unless SMB1 is enabled. of course, this should all just work using newer secure protocols. For a significant piece of server software, the fact that this hasn't been addressed long ago is a real mystery. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+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 951585] Re: gvfsd-afp consumes 100% of processor cycles
A bug from 2012, still affects me in 2022 on Ubuntu 22.04 and Linux Mint 21, using gvfs 1.48.2-0ubuntu1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/951585 Title: gvfsd-afp consumes 100% of processor cycles Status in gvfs package in Ubuntu: Confirmed Bug description: Happens on an irregular basis on 12.04 and I think I've experienced it on 11.10. For no reason gvfsd-afp starts up. Cooling fan kicks in, system becomes laggy. Easily cured using system monitor and killing the process. Someone on the Ubuntu Forum asked if I have a Mac on the network and the answer is yes, an iMac and there are shares on that machine I can access. Have experienced this issue on my Acer Aspire 5742 and Compaq Mini 110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/951585/+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 1988847] Re: Add a direct link to the irc support channel list
Marking as wishlist per request from OP on Libera ** Changed in: yelp (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1988847 Title: Add a direct link to the irc support channel list Status in yelp package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 @ 6/9/2022 [Current Case] When launching the gnome Yelp icon under category 'Get more help'/community support the user is forwarded to https://ubuntu.com/support/community-support and needs to click 4 times to actualy get to the irc channel list to get support [Wislist] Please add a more direct link towards the Ubuntu irc support channels from inside Yelp/get more help so the user can get a better support experience. The Yelp icon is on the Ubuntu-desktops dock by default, so this could benefit to a quick irc help ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yelp 42.1-1 Uname: Linux 5.17.7-051707-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 6 14:56:22 2022 SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1988847/+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 1983144] Re: Make thunderbird recognize irc: system-handler
setting as WISHLIST per request from OP on#ubuntu-discuss ** Changed in: thunderbird (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1983144 Title: Make thunderbird recognize irc: system-handler Status in thunderbird package in Ubuntu: New Bug description: Ubuntu 22.04 @ 29/07/2022 Current case: Thunderbird is installed by default on ubuntu and has a built-in chat/irc client but when clicking irc/ircs links on a browser system-handler does not recognize thunderbird as default irc client Wishlist: Please make Thunderbird open irc links to open with its built-in chat client so users can find their favorite irc (support) channels easy ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:91.11.0+build2-0ubuntu0.22.04.1 Uname: Linux 5.17.7-051707-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1007 F pulseaudio BuildID: 20220628000715 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Jul 29 20:25:54 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IpRoute: default via 192.168.1.1 dev enp1s0f1 proto dhcp metric 100 default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev enp1s0f1 scope link metric 1000 192.168.1.0/24 dev enp1s0f1 proto kernel scope link src 192.168.1.34 metric 100 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.63 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 Profile0PrefSources: prefs.js Profile0Prefs: extensions.lastAppVersion: "91.11.0" (prefs.js) network.trr.blocklist_cleanup_done: true (prefs.js) Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=91.11.0/20220628000715 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1983144/+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 1982688] Re: Make poweroff, logout and restart icons able to drag on dock
marking WISHLIST per request from OP on #ubuntu-discuss. ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist -- 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/1982688 Title: Make poweroff, logout and restart icons able to drag on dock Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 22.04 desktop @ 24/07/2022 Current situation: the power-off, reboot and logout icons are now searchable in application launcher but they cannot be dragged onto the dock Wishlist: please make these icons physical to be able to drag onto the dock so users can fastly power-off logout and restart their systems ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 Uname: Linux 5.17.7-051707-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jul 24 11:29:51 2022 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1982688/+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 1877038]
I can't give you an estimate but this is my current work item. The priority of this meta bug wasn't reflecting that, my apologies. -- 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/1877038 Title: [upstream] Firefox lacks FIDO2 support with Yubikeys Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: Ubuntu LTS versions affected. "Passwordless" authentications with Yubikeys using Firefox don't work with FIDO2. Tested both with the yubikey software packages from the bionic/universe repo and those from the vendor https://www.yubico.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1877038/+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 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
Has anybody checked if this happens only when upgrading from 21.10 to 22.04? -- 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/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in evince package in Ubuntu: Confirmed Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+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 1974254] Re: Probles with Clutter
Tim, I followed your advice and yes, that fixed most of the problems I was having. Apparently there was a system update that required a reboot, but there was an error and it just said all updates applied. This has occurred on the past couple of updates that didn't have too many changes, but something clearly got screwed up. I should have done this reboot myself, but I've become too comfortable believing the package manager. I won't make that mistake again. So that appears to resolve the issue. Thanks to you and Erich for your feedback. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clutter-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1974254 Title: Probles with Clutter Status in clutter-gtk package in Ubuntu: Invalid Bug description: Running Xubuntu 20.04.4 I've started seeing all sorts of programs failing in the last week apparently due to clutter. This includes Geeqie and Cheese, and possibly Zoom, although I haven't tracked down the problem there. For example, when I try to start geeqie, I get: Can't initialize clutter-gtk. Start geeqie with the option: --disable-clutter When I try to run cheese I get: (cheese:1207183): Clutter-CRITICAL **: 17:54:24.432: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. ** (cheese:1207183): ERROR **: 17:54:24.432: cheese-application.vala:89: Unable to initialize libcheese-gtk Trace/BPT trap(coredump) In researching the problem I ran across this article: https://blogs.gnome.org/clutter/ Now, I have no idea what clutter is/does, but it seems to now be retired. Was the package removal back-ported to earlier releases of Ubuntu? The gir1.2-gtkclutter-1.0, gir1-clutter-1.0 and gstreamer1.0-clutter-3.0 packages are still installed. Any guidelines here? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clutter-gtk/+bug/1974254/+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 1974254] Re: Probles with Clutter
I will follow up elsewhere, but I would really like to understand the disposition of clutter, given the site I reported that says it is now gone. What is actually happening here? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clutter-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1974254 Title: Probles with Clutter Status in clutter-gtk package in Ubuntu: Invalid Bug description: Running Xubuntu 20.04.4 I've started seeing all sorts of programs failing in the last week apparently due to clutter. This includes Geeqie and Cheese, and possibly Zoom, although I haven't tracked down the problem there. For example, when I try to start geeqie, I get: Can't initialize clutter-gtk. Start geeqie with the option: --disable-clutter When I try to run cheese I get: (cheese:1207183): Clutter-CRITICAL **: 17:54:24.432: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. ** (cheese:1207183): ERROR **: 17:54:24.432: cheese-application.vala:89: Unable to initialize libcheese-gtk Trace/BPT trap(coredump) In researching the problem I ran across this article: https://blogs.gnome.org/clutter/ Now, I have no idea what clutter is/does, but it seems to now be retired. Was the package removal back-ported to earlier releases of Ubuntu? The gir1.2-gtkclutter-1.0, gir1-clutter-1.0 and gstreamer1.0-clutter-3.0 packages are still installed. Any guidelines here? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clutter-gtk/+bug/1974254/+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 1974254] Re: Probles with Clutter
??? Can you be more specific. I am fully patched on 20.04.4 and I still get the same error reports from geeqie and cheese. Both worked until very recently and neither package was updated in quite some time. The developer of geeqie reported that he saw the same problem. Then he didn't! I am also finding a lot of other stable applications have stopped working such as openshot and kdenlive video editors, although these are Qt apps. Possibly there is a deeper underlying problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clutter-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1974254 Title: Probles with Clutter Status in clutter-gtk package in Ubuntu: Invalid Bug description: Running Xubuntu 20.04.4 I've started seeing all sorts of programs failing in the last week apparently due to clutter. This includes Geeqie and Cheese, and possibly Zoom, although I haven't tracked down the problem there. For example, when I try to start geeqie, I get: Can't initialize clutter-gtk. Start geeqie with the option: --disable-clutter When I try to run cheese I get: (cheese:1207183): Clutter-CRITICAL **: 17:54:24.432: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. ** (cheese:1207183): ERROR **: 17:54:24.432: cheese-application.vala:89: Unable to initialize libcheese-gtk Trace/BPT trap(coredump) In researching the problem I ran across this article: https://blogs.gnome.org/clutter/ Now, I have no idea what clutter is/does, but it seems to now be retired. Was the package removal back-ported to earlier releases of Ubuntu? The gir1.2-gtkclutter-1.0, gir1-clutter-1.0 and gstreamer1.0-clutter-3.0 packages are still installed. Any guidelines here? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clutter-gtk/+bug/1974254/+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 1900347] Re: Doesn't import gpg keys Doesn't export armored (asc) gpg keys
Thanks for letting me know. Larry. On Fri, 20 May 2022 18:37:50 - Sebastien Bacher <1900...@bugs.launchpad.net> wrote: > it's fixed in the current version > > ** Changed in: seahorse (Ubuntu) >Status: Fix Committed => Fix Released > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1900347 Title: Doesn't import gpg keys Doesn't export armored (asc) gpg keys Status in seahorse: Fix Released Status in seahorse package in Ubuntu: Fix Released Bug description: Very similar to bug # 1577198. Seahorse (Passwords and Keys) won't import gpg keys. But if I double click on the gpg key in the file manager it will show as imported after I restart Seahorse. After keys are imported (using the double click method or CLI) they can only be exported as binary keys i.e. keyname.pgp. If I try the option to export as a keyname.asc version (armored) I only get the same binary key. Everything works fine with gpg in a terminal. This is with a fresh install of 20.04.1, Seahorse 3.36-1 with Seahorse-daemon and Seahorse-nautilis installed. The Gnupg version is 2.2.19 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: seahorse 3.36-1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 18 11:32:13 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-10-09 (8 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/1900347/+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 1974254] Re: Probles with Clutter
I wasn't sure of the package so I left field blank. I went back and added clutter-gtk. Hope that helps. ** Also affects: clutter-gtk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clutter-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1974254 Title: Probles with Clutter Status in Ubuntu: New Status in clutter-gtk package in Ubuntu: New Bug description: Running Xubuntu 20.04.4 I've started seeing all sorts of programs failing in the last week apparently due to clutter. This includes Geeqie and Cheese, and possibly Zoom, although I haven't tracked down the problem there. For example, when I try to start geeqie, I get: Can't initialize clutter-gtk. Start geeqie with the option: --disable-clutter When I try to run cheese I get: (cheese:1207183): Clutter-CRITICAL **: 17:54:24.432: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. ** (cheese:1207183): ERROR **: 17:54:24.432: cheese-application.vala:89: Unable to initialize libcheese-gtk Trace/BPT trap(coredump) In researching the problem I ran across this article: https://blogs.gnome.org/clutter/ Now, I have no idea what clutter is/does, but it seems to now be retired. Was the package removal back-ported to earlier releases of Ubuntu? The gir1.2-gtkclutter-1.0, gir1-clutter-1.0 and gstreamer1.0-clutter-3.0 packages are still installed. Any guidelines here? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1974254/+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 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER
Just to make sure the note is here, my home directory is not in /home at all, but located under /u which is a mount point for an external volume on another disk. I experienced the same problem trying to run a snap. Whatever the solution, it should be generalized to any $HOME location. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1776800 Title: Unable to start snap applications if user's home directory is not /home/$USER Status in snapd: In Progress Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Confirmed Bug description: Users with home directories in /home/$USER can run snap application, but users in /home/users/$USER can't. nate@WorkstationC:~$ snap --version snap2.32.8+18.04 snapd 2.32.8+18.04 series 16 ubuntu 18.04 kernel 4.15.0-22-generic nate@WorkstationC:~$ echo $HOME /home/users/nate nate@WorkstationC:~$ which hello-world /snap/bin/hello-world nate@WorkstationC:~$ hello-world cannot create nate data directory: /home/users/nate/snap/hello-world/27: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776800/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Promotion from -proposed sure would be nice. I see verification has been done but a update excuses shows an netplan.io regression[1]. I'm not sure if the test is flaky but I see that seb retried it a few times[2] last week and it failed consistently, so maybe not. I'm just curious if there's any status on the test failure. (Also, I started writing this thinking it had been a month but it's been less than a week and I can't tell time. I know it wouldn't be promoted with less than a week in -proposed anyway.) [1] https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#wpa [2] https://autopkgtest.ubuntu.com/packages/netplan.io/jammy/arm64 -- 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/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Thank you Seb, I had the issue reported in this bug in a WeWork today (first time connecting since updating to Jammy) and the package in -proposed resolved the issue for me as well. -- 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/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1972070] Re: gdk-pixbuf does not support saving as gif
** Description changed: Hello, I'm getting this message then I try to save a rotated GIF image in Image Viewer: "This build of gdk-pixbuf does not support saving the image format: gif" - Is write support for GIF dropped for any reason? - - Description: Ubuntu 22.04 LTS Release: 22.04 libgdk-pixbuf-2.0-0: - Installed: 2.42.8+dfsg-1 - Candidate: 2.42.8+dfsg-1 - Version table: - *** 2.42.8+dfsg-1 500 + Installed: 2.42.8+dfsg-1 + Candidate: 2.42.8+dfsg-1 + Version table: + *** 2.42.8+dfsg-1 500 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1972070 Title: gdk-pixbuf does not support saving as gif Status in gdk-pixbuf package in Ubuntu: New Bug description: Hello, I'm getting this message then I try to save a rotated GIF image in Image Viewer: "This build of gdk-pixbuf does not support saving the image format: gif" Description: Ubuntu 22.04 LTS Release: 22.04 libgdk-pixbuf-2.0-0: Installed: 2.42.8+dfsg-1 Candidate: 2.42.8+dfsg-1 Version table: *** 2.42.8+dfsg-1 500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1972070/+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 1972070] [NEW] gdk-pixbuf does not support saving as gif
Public bug reported: Hello, I'm getting this message then I try to save a rotated GIF image in Image Viewer: "This build of gdk-pixbuf does not support saving the image format: gif" Is write support for GIF dropped for any reason? Description:Ubuntu 22.04 LTS Release:22.04 libgdk-pixbuf-2.0-0: Installed: 2.42.8+dfsg-1 Candidate: 2.42.8+dfsg-1 Version table: *** 2.42.8+dfsg-1 500 ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1972070 Title: gdk-pixbuf does not support saving as gif Status in gdk-pixbuf package in Ubuntu: New Bug description: Hello, I'm getting this message then I try to save a rotated GIF image in Image Viewer: "This build of gdk-pixbuf does not support saving the image format: gif" Is write support for GIF dropped for any reason? Description: Ubuntu 22.04 LTS Release: 22.04 libgdk-pixbuf-2.0-0: Installed: 2.42.8+dfsg-1 Candidate: 2.42.8+dfsg-1 Version table: *** 2.42.8+dfsg-1 500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1972070/+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 1900347] Current status
Dear Mr. Bacher, I am a linux novice. You responded to a bug report I made in Oct 20, 2020. On February 26, 2021 there was a updated report posted here: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1900347 So has this bug been fixed? If so were would the fixed package be? If not when and how do bugs like this get resolved? Thanks, Larry C. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1900347 Title: Doesn't import gpg keys Doesn't export armored (asc) gpg keys Status in seahorse: Unknown Status in seahorse package in Ubuntu: Fix Committed Bug description: Very similar to bug # 1577198. Seahorse (Passwords and Keys) won't import gpg keys. But if I double click on the gpg key in the file manager it will show as imported after I restart Seahorse. After keys are imported (using the double click method or CLI) they can only be exported as binary keys i.e. keyname.pgp. If I try the option to export as a keyname.asc version (armored) I only get the same binary key. Everything works fine with gpg in a terminal. This is with a fresh install of 20.04.1, Seahorse 3.36-1 with Seahorse-daemon and Seahorse-nautilis installed. The Gnupg version is 2.2.19 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: seahorse 3.36-1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 18 11:32:13 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-10-09 (8 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/1900347/+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 1966581] Re: Launcher screenshot UI cannot be added to dock
Importance set to WISHLIST per request on #ubuntu-bugs-announce ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist -- 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/1966581 Title: Launcher screenshot UI cannot be added to dock Status in gnome-shell package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 development branch @ 27/03/2022 The new gnome-shell built-in screenshot UI has a launcher when you search it from start/applications, but the icon cannot be dragged or added to the dock This wishlist is for novice users that might not be familiar with the prt scr button and might benefit a launcher from the dock, like gnome-screenshot did before. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 27 13:38:44 2022 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: [modified] mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2021-10-23T19:12:47.175230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966581/+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 1944113]
*** Bug 147832 has been marked as a duplicate of this bug. *** -- 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/1944113 Title: Many UI elements (list box, drop down) don't work at all in kf5 environment Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Many UI elements (list box, drop down) don't work at all in kf5 environment. This makes LO unusable. For example, try to insert a table from standard toolbar in LO Writer – nothing inserted. Same happens with other drop down elements (styles, font family, font size, font color, font highlight, etc). Bug reports at LO's bug tracker: https://bugs.documentfoundation.org/show_bug.cgi?id=144037 https://bugs.documentfoundation.org/show_bug.cgi?id=144562 https://gerrit.libreoffice.org/c/core/+/122116 Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.11.0-34-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz Memory: 7,7 GiB Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3 Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+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 1672139]
Likewise, my gratitude for this simple and useful feature. Now if only
someone could make a pdf viewer that would print pdfs as well as does
Edge, without losing lines and the bottom of the page and other
features, I would be totally happy with Firefox. I will post this as a
separate bug.
--
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/1672139
Title:
Add "Open Enclosing Folder" context menu to search results of
bookmarks in the Library window (link to view/open containing folder,
parent folder button)
Status in Mozilla Firefox:
Fix Released
Status in firefox package in Ubuntu:
Confirmed
Bug description:
Firefox is great. It has bookmarks.
But it is impossible to open bookmark's folder in search results.
Steps to reproduce:
1. Open Firefox
2. Open its Bookmark Manager ()
3. Search for bookmark
4. Try to find its folder with right-click menu.
5. It is impossible to find bookmark's folder.
Expected results:
Firefox is mature, so it is expected that user can find bookmark's folder.
For example Google Chrome has "Show in folder" menu option.
Note: original bug was reported 8 years ago, but it is not fixed.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firefox 52.0+build2-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.13.0-110.157~precise1-generic 3.13.11-ckt39
Uname: Linux 3.13.0-110-generic x86_64
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.13.0-110-generic.
ApportVersion: 2.0.1-0ubuntu17.15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nikolay8420 F pulseaudio
BuildID: 20170303013352
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d18000 irq 46'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,10431507,00100100
HDA:80862806,80860101,0010'
Controls : 24
Simple ctrls : 9
Channel: Unavailable
Date: Sun Mar 12 13:59:45 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64
(20140204)
IpRoute:
default via 192.168.3.1 dev wlan3 proto static
169.254.0.0/16 dev wlan3 scope link metric 1000
192.168.3.0/24 dev wlan3 proto kernel scope link src 192.168.3.6 metric
2
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
Locales: extensions.sqlite corrupt or missing
MarkForUpload: True
MostRecentCrashID: bp-a82bbe13-104c-487f-84dc-178712170311
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources:
prefs.js
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
[Profile]/extensions/swappr...@mahendra.com/defaults/preferences/prefs.js
[Profile]/extensions/{e36db930-f18d-4449-b45f-e286cfb9e03a}/defaults/preferences/markingcollection-prefs.js
[Profile]/extensions/tabletoo...@mingyi.org/defaults/preferences/tt_defaults.js
Profiles: Profile0 (Default) - LastVersion=52.0/20170303013352 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/12/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX32A.216
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX32A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX32A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1672139/+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 1672139]
That's exciting. Thank you. Since v93 just installed on my PC today,
hopefully v95 is not too far in the future.
--
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/1672139
Title:
Add "Open Enclosing Folder" context menu to search results of
bookmarks in the Library window (link to view/open containing folder,
parent folder button)
Status in Mozilla Firefox:
Fix Released
Status in firefox package in Ubuntu:
Confirmed
Bug description:
Firefox is great. It has bookmarks.
But it is impossible to open bookmark's folder in search results.
Steps to reproduce:
1. Open Firefox
2. Open its Bookmark Manager ()
3. Search for bookmark
4. Try to find its folder with right-click menu.
5. It is impossible to find bookmark's folder.
Expected results:
Firefox is mature, so it is expected that user can find bookmark's folder.
For example Google Chrome has "Show in folder" menu option.
Note: original bug was reported 8 years ago, but it is not fixed.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firefox 52.0+build2-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.13.0-110.157~precise1-generic 3.13.11-ckt39
Uname: Linux 3.13.0-110-generic x86_64
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.13.0-110-generic.
ApportVersion: 2.0.1-0ubuntu17.15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nikolay8420 F pulseaudio
BuildID: 20170303013352
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d18000 irq 46'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,10431507,00100100
HDA:80862806,80860101,0010'
Controls : 24
Simple ctrls : 9
Channel: Unavailable
Date: Sun Mar 12 13:59:45 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64
(20140204)
IpRoute:
default via 192.168.3.1 dev wlan3 proto static
169.254.0.0/16 dev wlan3 scope link metric 1000
192.168.3.0/24 dev wlan3 proto kernel scope link src 192.168.3.6 metric
2
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
Locales: extensions.sqlite corrupt or missing
MarkForUpload: True
MostRecentCrashID: bp-a82bbe13-104c-487f-84dc-178712170311
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources:
prefs.js
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
[Profile]/extensions/swappr...@mahendra.com/defaults/preferences/prefs.js
[Profile]/extensions/{e36db930-f18d-4449-b45f-e286cfb9e03a}/defaults/preferences/markingcollection-prefs.js
[Profile]/extensions/tabletoo...@mingyi.org/defaults/preferences/tt_defaults.js
Profiles: Profile0 (Default) - LastVersion=52.0/20170303013352 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/12/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX32A.216
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX32A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX32A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1672139/+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 1672139]
This has been a long-standing issue and I am pleased to see it is now
actively being work. Can someone suggest when this might be complete
and what version of Firefox might contain this useful change?
--
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/1672139
Title:
Add "Open Enclosing Folder" context menu to search results of
bookmarks in the Library window (link to view/open containing folder,
parent folder button)
Status in Mozilla Firefox:
In Progress
Status in firefox package in Ubuntu:
Confirmed
Bug description:
Firefox is great. It has bookmarks.
But it is impossible to open bookmark's folder in search results.
Steps to reproduce:
1. Open Firefox
2. Open its Bookmark Manager ()
3. Search for bookmark
4. Try to find its folder with right-click menu.
5. It is impossible to find bookmark's folder.
Expected results:
Firefox is mature, so it is expected that user can find bookmark's folder.
For example Google Chrome has "Show in folder" menu option.
Note: original bug was reported 8 years ago, but it is not fixed.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firefox 52.0+build2-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.13.0-110.157~precise1-generic 3.13.11-ckt39
Uname: Linux 3.13.0-110-generic x86_64
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.13.0-110-generic.
ApportVersion: 2.0.1-0ubuntu17.15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nikolay8420 F pulseaudio
BuildID: 20170303013352
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d18000 irq 46'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,10431507,00100100
HDA:80862806,80860101,0010'
Controls : 24
Simple ctrls : 9
Channel: Unavailable
Date: Sun Mar 12 13:59:45 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64
(20140204)
IpRoute:
default via 192.168.3.1 dev wlan3 proto static
169.254.0.0/16 dev wlan3 scope link metric 1000
192.168.3.0/24 dev wlan3 proto kernel scope link src 192.168.3.6 metric
2
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
Locales: extensions.sqlite corrupt or missing
MarkForUpload: True
MostRecentCrashID: bp-a82bbe13-104c-487f-84dc-178712170311
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources:
prefs.js
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
[Profile]/extensions/swappr...@mahendra.com/defaults/preferences/prefs.js
[Profile]/extensions/{e36db930-f18d-4449-b45f-e286cfb9e03a}/defaults/preferences/markingcollection-prefs.js
[Profile]/extensions/tabletoo...@mingyi.org/defaults/preferences/tt_defaults.js
Profiles: Profile0 (Default) - LastVersion=52.0/20170303013352 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/12/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX32A.216
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX32A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX32A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1672139/+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 1943342] Re: Several seconds for icons to appear and dissappear from the dock
The same problem is happening, so there's no doubt it's a Dash To Dock bug. -- 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/1943342 Title: Several seconds for icons to appear and dissappear from the dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: The icons take several seconds to appear and disappear from the dock. The dock has been showing this behavior from time to time without apparently reason since day zero. show-mounts is set to false. Description:Ubuntu 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1943342/+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 1943342] Re: Several seconds for icons to appear and dissappear from the dock
I'm going to do what you've written and I'll post if the problem is still taking place or not. -- 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/1943342 Title: Several seconds for icons to appear and dissappear from the dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: The icons take several seconds to appear and disappear from the dock. The dock has been showing this behavior from time to time without apparently reason since day zero. show-mounts is set to false. Description:Ubuntu 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1943342/+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 1943342] Re: Several seconds for icons to appear and dissappear from the dock
Yes, I have. -- 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/1943342 Title: Several seconds for icons to appear and dissappear from the dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: The icons take several seconds to appear and disappear from the dock. The dock has been showing this behavior from time to time without apparently reason since day zero. show-mounts is set to false. Description:Ubuntu 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1943342/+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 1943342] [NEW] Several seconds for icons to appear and dissappear from the dock
Public bug reported: The icons take several seconds to appear and disappear from the dock. The dock has been showing this behavior from time to time without apparently reason since day zero. show-mounts is set to false. Description:Ubuntu 21.04 ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: appear delay dock icons seconds ** Description changed: The icons take several seconds to appear and disappear from the dock. - The dock has been showing his behavior from time to time without + The dock has been showing this behavior from time to time without apparently reason since day zero. show-mounts is set to false. ** Description changed: The icons take several seconds to appear and disappear from the dock. The dock has been showing this behavior from time to time without apparently reason since day zero. show-mounts is set to false. + + Description:Ubuntu 21.04 -- 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/1943342 Title: Several seconds for icons to appear and dissappear from the dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: The icons take several seconds to appear and disappear from the dock. The dock has been showing this behavior from time to time without apparently reason since day zero. show-mounts is set to false. Description:Ubuntu 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1943342/+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 1672139]
I disagree. "Open containing folder" is common terminology and makes it
clear that you are opening the folder that contains the bookmark you are
examining. This is how Chrome does it. I also use a fabulous file
manager called Directory Opus that uses the same terminology.
--
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/1672139
Title:
Add "Open Enclosing Folder" context menu to search results of
bookmarks in the Library window (link to view/open containing folder,
parent folder button)
Status in Mozilla Firefox:
In Progress
Status in firefox package in Ubuntu:
Confirmed
Bug description:
Firefox is great. It has bookmarks.
But it is impossible to open bookmark's folder in search results.
Steps to reproduce:
1. Open Firefox
2. Open its Bookmark Manager ()
3. Search for bookmark
4. Try to find its folder with right-click menu.
5. It is impossible to find bookmark's folder.
Expected results:
Firefox is mature, so it is expected that user can find bookmark's folder.
For example Google Chrome has "Show in folder" menu option.
Note: original bug was reported 8 years ago, but it is not fixed.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firefox 52.0+build2-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.13.0-110.157~precise1-generic 3.13.11-ckt39
Uname: Linux 3.13.0-110-generic x86_64
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.13.0-110-generic.
ApportVersion: 2.0.1-0ubuntu17.15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nikolay8420 F pulseaudio
BuildID: 20170303013352
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d18000 irq 46'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,10431507,00100100
HDA:80862806,80860101,0010'
Controls : 24
Simple ctrls : 9
Channel: Unavailable
Date: Sun Mar 12 13:59:45 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64
(20140204)
IpRoute:
default via 192.168.3.1 dev wlan3 proto static
169.254.0.0/16 dev wlan3 scope link metric 1000
192.168.3.0/24 dev wlan3 proto kernel scope link src 192.168.3.6 metric
2
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
Locales: extensions.sqlite corrupt or missing
MarkForUpload: True
MostRecentCrashID: bp-a82bbe13-104c-487f-84dc-178712170311
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources:
prefs.js
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
[Profile]/extensions/swappr...@mahendra.com/defaults/preferences/prefs.js
[Profile]/extensions/{e36db930-f18d-4449-b45f-e286cfb9e03a}/defaults/preferences/markingcollection-prefs.js
[Profile]/extensions/tabletoo...@mingyi.org/defaults/preferences/tt_defaults.js
Profiles: Profile0 (Default) - LastVersion=52.0/20170303013352 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/12/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX32A.216
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX32A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX32A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1672139/+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 1672139]
I am so glad to hear this is now being worked. Thank you.
As for a name, how about the term Chrome uses when you right click a URL
bookmark in your library, which is "Show in Folder." I am not sure how
you wish to implement, but if you just open Chrome I think it does it
well. I'm not as happy with their bookmarks mgr as with the FFox
Library, but the "show in folder" feature works nicely. When you click
it, you just move to the folder containing the bookmark in question.
The folder is highlighted in the folder tree and all bookmarks in the
highlighted folder, including the one you are interested in, are shown.
Check it out. I would vote for that for Ffox.
--
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/1672139
Title:
Add "Open Enclosing Folder" context menu to search results of
bookmarks in the Library window (link to view/open containing folder,
parent folder button)
Status in Mozilla Firefox:
In Progress
Status in firefox package in Ubuntu:
Confirmed
Bug description:
Firefox is great. It has bookmarks.
But it is impossible to open bookmark's folder in search results.
Steps to reproduce:
1. Open Firefox
2. Open its Bookmark Manager ()
3. Search for bookmark
4. Try to find its folder with right-click menu.
5. It is impossible to find bookmark's folder.
Expected results:
Firefox is mature, so it is expected that user can find bookmark's folder.
For example Google Chrome has "Show in folder" menu option.
Note: original bug was reported 8 years ago, but it is not fixed.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firefox 52.0+build2-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.13.0-110.157~precise1-generic 3.13.11-ckt39
Uname: Linux 3.13.0-110-generic x86_64
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.13.0-110-generic.
ApportVersion: 2.0.1-0ubuntu17.15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nikolay8420 F pulseaudio
BuildID: 20170303013352
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d18000 irq 46'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,10431507,00100100
HDA:80862806,80860101,0010'
Controls : 24
Simple ctrls : 9
Channel: Unavailable
Date: Sun Mar 12 13:59:45 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64
(20140204)
IpRoute:
default via 192.168.3.1 dev wlan3 proto static
169.254.0.0/16 dev wlan3 scope link metric 1000
192.168.3.0/24 dev wlan3 proto kernel scope link src 192.168.3.6 metric
2
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
Locales: extensions.sqlite corrupt or missing
MarkForUpload: True
MostRecentCrashID: bp-a82bbe13-104c-487f-84dc-178712170311
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources:
prefs.js
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
[Profile]/extensions/swappr...@mahendra.com/defaults/preferences/prefs.js
[Profile]/extensions/{e36db930-f18d-4449-b45f-e286cfb9e03a}/defaults/preferences/markingcollection-prefs.js
[Profile]/extensions/tabletoo...@mingyi.org/defaults/preferences/tt_defaults.js
Profiles: Profile0 (Default) - LastVersion=52.0/20170303013352 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/12/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX32A.216
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX32A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX32A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1672139/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to :
[Desktop-packages] [Bug 1931312] [NEW] i386 version of libpipewire-0.3 for Ubuntu Focal 20.04
Public bug reported: Hi, I updated the packages today and one of them was Steam. When trying to open Steam, it is reported missing to install 32-bit version of libpipewire-0.3.so.0 luzfcb@fabio-pc:~ $ STEAM_RUNTIME=0 steam Running Steam on focal 20.04 64-bit STEAM_RUNTIME is disabled by the user Error: You are missing the following 32-bit libraries, and Steam may not run: libpipewire-0.3.so.0 I did a brief search and saw that there is no 32bit version of pipewire 0.3 release. https://packages.ubuntu.com/search?arch=i386=pipewire luzfcb@fabio-pc:~ $ sudo apt-get install libpipewire-0.3-0:i386 [sudo] senha para luzfcb: Lendo listas de pacotes... Pronto Construindo árvore de dependências Lendo informação de estado... Pronto E: Impossível encontrar o pacote libpipewire-0.3-0:i386 E: Couldn't find any package by glob 'libpipewire-0.3-0' E: Não foi possível encontrar o pacote através da expressão regular 'libpipewire-0.3-0' Are there any plans to fix this and make life for the few people still trying to play games using Linux less difficult? Yes or no, thanks for your hard work. ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1931312 Title: i386 version of libpipewire-0.3 for Ubuntu Focal 20.04 Status in pipewire package in Ubuntu: New Bug description: Hi, I updated the packages today and one of them was Steam. When trying to open Steam, it is reported missing to install 32-bit version of libpipewire-0.3.so.0 luzfcb@fabio-pc:~ $ STEAM_RUNTIME=0 steam Running Steam on focal 20.04 64-bit STEAM_RUNTIME is disabled by the user Error: You are missing the following 32-bit libraries, and Steam may not run: libpipewire-0.3.so.0 I did a brief search and saw that there is no 32bit version of pipewire 0.3 release. https://packages.ubuntu.com/search?arch=i386=pipewire luzfcb@fabio-pc:~ $ sudo apt-get install libpipewire-0.3-0:i386 [sudo] senha para luzfcb: Lendo listas de pacotes... Pronto Construindo árvore de dependências Lendo informação de estado... Pronto E: Impossível encontrar o pacote libpipewire-0.3-0:i386 E: Couldn't find any package by glob 'libpipewire-0.3-0' E: Não foi possível encontrar o pacote através da expressão regular 'libpipewire-0.3-0' Are there any plans to fix this and make life for the few people still trying to play games using Linux less difficult? Yes or no, thanks for your hard work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1931312/+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 1672139]
Is there any way to up the priority on this issue? Bookmarks in general
work great; much better than Chrome, but darn it, this one item is a
terribly annoying feature, i.e. not easily being able to find the folder
in which a bookmark is located. Yes, I know there is a work around that
sometimes works and sometimes doesn't but it sure it a nuisance to use.
Anyway, great program and thank you for what you do.
--
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/1672139
Title:
Add "Open Enclosing Folder" context menu to search results of
bookmarks in the Library window (link to view/open containing folder,
parent folder button)
Status in Mozilla Firefox:
Confirmed
Status in firefox package in Ubuntu:
Confirmed
Bug description:
Firefox is great. It has bookmarks.
But it is impossible to open bookmark's folder in search results.
Steps to reproduce:
1. Open Firefox
2. Open its Bookmark Manager ()
3. Search for bookmark
4. Try to find its folder with right-click menu.
5. It is impossible to find bookmark's folder.
Expected results:
Firefox is mature, so it is expected that user can find bookmark's folder.
For example Google Chrome has "Show in folder" menu option.
Note: original bug was reported 8 years ago, but it is not fixed.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firefox 52.0+build2-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.13.0-110.157~precise1-generic 3.13.11-ckt39
Uname: Linux 3.13.0-110-generic x86_64
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.13.0-110-generic.
ApportVersion: 2.0.1-0ubuntu17.15
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nikolay8420 F pulseaudio
BuildID: 20170303013352
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d18000 irq 46'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,10431507,00100100
HDA:80862806,80860101,0010'
Controls : 24
Simple ctrls : 9
Channel: Unavailable
Date: Sun Mar 12 13:59:45 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64
(20140204)
IpRoute:
default via 192.168.3.1 dev wlan3 proto static
169.254.0.0/16 dev wlan3 scope link metric 1000
192.168.3.0/24 dev wlan3 proto kernel scope link src 192.168.3.6 metric
2
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
Locales: extensions.sqlite corrupt or missing
MarkForUpload: True
MostRecentCrashID: bp-a82bbe13-104c-487f-84dc-178712170311
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources:
prefs.js
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
[Profile]/extensions/swappr...@mahendra.com/defaults/preferences/prefs.js
[Profile]/extensions/{e36db930-f18d-4449-b45f-e286cfb9e03a}/defaults/preferences/markingcollection-prefs.js
[Profile]/extensions/tabletoo...@mingyi.org/defaults/preferences/tt_defaults.js
Profiles: Profile0 (Default) - LastVersion=52.0/20170303013352 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/12/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX32A.216
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX32A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX32A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1672139/+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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Regarding my previous comment, disregard the issue about Windows 10 having problems accessing the Samba shares. This turned out to be a strange password problem with samba. Resetting the user's password to the same value that it already was immediately cleared the issue and all windows machines could once again see the shares. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Just to add another voice to the crowd, I'm on Xubuntu 20.04 and I just
ran across this problem myself.
I am using the Nemo file browser, but the same thing occurs with
Nautilus and Thunar. I didn't notice the problem for a long while
because I had three legacy Windows machines on the network (all running
Windows 10 at this point) and had made file browser bookmarks to the
important shares long ago. These bookmarks have continued to work to
this day without issue. I got a new Windows 10 machine a few weeks ago
and was having the problem everyone reports of not being able to connect
("Failed to retrieve share list from server") on the new machine, even
though all the existing bookmarks were still functioning file. All of
the Windows 10 machines were able to see one another without problem.
Then I ran across this thread and tried Bloodyiron's suggestion of
killing the gvfsd-smb-browse process. Immediately I was able to connect
to the new machine using Nemo. I quickly created some needed bookmarks
to the important shares and now I can communicate using the file browser
and expect the new bookmarks to be as reliable as the others. So I
would suggest this bookmark method to others as a workaround.
This supports Craig W's comment about the difference between discovery
and browsing. When I run "smbclient -L // -U ", it
reports all of the shares on the target, whether Windows or Linux, with
the closing message: "SMB1 disabled -- no workgroup available" as
expected.
Unfortunately, this is only a one-way solution. All of the legacy
Windows 10 machines can see and access the Samba shares on the Xubuntu
box, but I haven't yet figured out a way to get the new Windows machine
to access these same shares, with or without gvfsd-smb-browse running.
Every connection attempt is rejected and I haven't found useful messages
in the logs. If I figure out a solution, I'll post here, and I'm open
to suggestions.
I agree with the general sentiment that for a service as important as
this, there isn't any real excuse for this thing dragging out for two
years as it has.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1828107
Title:
gvfs can't list shares from smb servers that disabled SMB1
Status in gvfs:
Unknown
Status in gvfs package in Ubuntu:
Triaged
Bug description:
After bug #1778322 is fixed (just needs a gvfs rebuild with newer
samba), samba machines will start to show up again in the "windows
network" tab in nautilus. But if a server has disabled the SMB1
protocol, nautilus will show an error when that server is clicked on,
instead of showing the shares list.
Even with SMB1 disabled, it should still be technically possible to
get a share list, since smbclient can do it:
andreas@nsnx:~$ nmblookup -A 192.168.122.101
Looking up status of 192.168.122.101
D-NO-SMB1 <00> - B
D-NO-SMB1 <03> - B
D-NO-SMB1 <20> - B
..__MSBROWSE__. <01> - B
WORKGROUP <00> - B
WORKGROUP <1d> - B
WORKGROUP <1e> - B
MAC Address = 00-00-00-00-00-00
andreas@nsnx:~$ smbclient -L 192.168.122.101 -N
WARNING: The "syslog" option is deprecated
Sharename Type Comment
- ---
print$ Disk Printer Drivers
pub_no_smb1 Disk
IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu))
Reconnecting with SMB1 for workgroup listing.
protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
Failed to connect with SMB1 -- no workgroup available
andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m
NT1
WARNING: The "syslog" option is deprecated
protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE
andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m
SMB2
WARNING: The "syslog" option is deprecated
Try "help" to get a list of possible commands.
smb: \> dir
. D0 Fri May 3 18:16:38 2019
.. D0 Fri May 3 18:15:24 2019
hello.txt N 21 Fri May 3 18:16:12 2019
hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019
20509264 blocks of size 1024. 13121800 blocks
available
To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1828107/+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 1470730] Re: [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line in/Line out on docking station doesn't work
I can confirm. This is still existing for me on: - Ubuntu 20.04.2 - Linux 5.8.0-44-generic - HP-EliteBook-840-G6 - HP UltraSlim Dock 2013 - Realtek ALC215 I tried almost all steps described here and in other places. Without any luck. If I use hdajacksensetest with plugged jack in dock I get: $ hdajacksensetest -c 0 -a Pin 0x12 (Not connected): present = No Pin 0x13 (Not connected): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x16 (Not connected): present = Yes Pin 0x17 (Not connected): present = No Pin 0x18 (Not connected): present = No Pin 0x19 (Black Mic, Right side): present = No Pin 0x1a (Not connected): present = Yes Pin 0x1b (Not connected): present = No Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x21 (Black Headphone, Right side): present = No If I use hdajacksensetest with unplugged jack in dock I get: $ hdajacksensetest -c 0 -a Pin 0x12 (Not connected): present = No Pin 0x13 (Not connected): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x16 (Not connected): present = No Pin 0x17 (Not connected): present = No Pin 0x18 (Not connected): present = No Pin 0x19 (Black Mic, Right side): present = No Pin 0x1a (Not connected): present = Yes Pin 0x1b (Not connected): present = No Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x21 (Black Headphone, Right side): present = No Which leads me to the assumption pin 0x16 is the one Iam looking for. I tried to hdajackretask it but got: "tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy" I followed the steps to temporary disable pulseaudio as suggested in different posts. But trying to hdajackretask now, it always freezes the tool (ubuntu shows the "force quit" dialog every now and then) when I click on "Apply now" and after entering my password. After killing it computer stays busy a lot and all sound devices are gone. Having a look at alsamixer also fails then: $ alsamixer alsamixer - cannot open mixer: No such file or directory After reboot everything is back in place. But still no output on the jack of the dock. After investing some hours of try and error i found this: https://ubuntuforums.org/showthread.php?t=2392730 So I tried to simply overwrite my pin 0x16 with "Dock line out". It seems to work. At least I get a file stored in /lib/firmware/: $ cat /lib/firmware/hda-jack-retask.fw [codec] 0x10ec0215 0x103c854d 0 [pincfg] 0x12 0x4000 0x13 0x41f0 0x14 0x90170110 0x16 0x220140b0 0x17 0x41f0 0x18 0x41f0 0x19 0x04a11040 0x1a 0x41f0 0x1b 0x41f0 0x1d 0x4061 0x1e 0x41f0 0x21 0x04211020 And one in /etc/modprobe.d/: $ cat /etc/modprobe.d/hda-jack-retask.conf # This file was added by the program 'hda-jack-retask'. # If you want to revert the changes made by this program, you can simply erase this file and reboot your computer. options snd-hda-intel patch=hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw Which makes me confident that at least hdajackretask did its job. But now I dont have sound at all. If I use hdajacksensetest with plugged jack in dock now I get: $ hdajacksensetest -c 0 -a Pin 0x12 (Not connected): present = No Pin 0x13 (Not connected): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x16 (Not connected): present = Yes Pin 0x17 (Not connected): present = No Pin 0x18 (Not connected): present = No Pin 0x19 (Black Mic, Right side): present = No Pin 0x1a (Not connected): present = Yes Pin 0x1b (Not connected): present = No Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x21 (Black Headphone, Right side): present = No Which is exactly the same as before. I also tried the approach from Gijs with the "Advanced options". Same result. Would appreciate help on that. -- 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/1470730 Title: [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line in/Line out on docking station doesn't work Status in alsa-driver package in Ubuntu: Expired Bug description: When I plug in external speakers to line in/line out combo on the laptop the internal speakers are turned off but when I plug the speakers into the docking station (HP UltraSlim Dock 2013 EURO, D9Y32AA) music keeps playing in the internal speakers. Similar behaviour (nothing happens) is experienced with microphone connected to line in on docking station. ### Expected behaviour Plugging in external speakers to docking station should turn off sound from laptop internal speakers. Plugging in microphone to line in on docking station should switch from "internal microphone" to "microphone" in Ubuntu sound settings. ### Current behaviour Sound keeps playing in internal speakers when plugging in ex
[Desktop-packages] [Bug 1918190] Re: Enabling/Disabling VPN crashes window manager
@3v1n0 (Marco Trevisan) has pointed out
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1651 as a
possible fix
** Description changed:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description: Ubuntu Hirsute Hippo (development branch)
Release: 21.04
$ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk
-F= '{print $2}'
wayland
$ apt-cache policy network-manager
network-manager:
Installed: 1.30.0-1ubuntu1
Candidate: 1.30.0-1ubuntu1
Version table:
*** 1.30.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
$ apt-cache policy gnome-shell
gnome-shell:
- Installed: 3.38.3-3ubuntu1
- Candidate: 3.38.3-3ubuntu1
- Version table:
- *** 3.38.3-3ubuntu1 500
- 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
- 100 /var/lib/dpkg/status
+ Installed: 3.38.3-3ubuntu1
+ Candidate: 3.38.3-3ubuntu1
+ Version table:
+ *** 3.38.3-3ubuntu1 500
+ 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
+ 100 /var/lib/dpkg/status
+
+ $ dpkg-query -W|grep mutter
+ gir1.2-mutter-7:amd64 3.38.3-3ubuntu1
+ libmutter-7-0:amd64 3.38.3-3ubuntu1
+ mutter3.38.3-3ubuntu1
+ mutter-common 3.38.3-3ubuntu1
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 8 14:12:44 2021
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2017-04-21 (1416 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
RebootRequiredPkgs:
libssl1.1
libssl1.1
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.30.0 connected started full enabled enabled
disabled enabled enabled
** Also affects: mutter (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/1918190
Title:
Enabling/Disabling VPN crashes window manager
Status in gnome-shell package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Status in network-manager package in Ubuntu:
New
Bug description:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description: Ubuntu Hirsute Hippo (development branch)
Release: 21.04
$ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk
-F= '{print $2}'
wayland
$ apt-cache policy network-manager
network-manager:
Installed: 1.30.0-1ubuntu1
Candidate: 1.30.0-1ubuntu1
Version table:
*** 1.30.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
$ apt-cache policy gnome-shell
gnome-shell:
Installed: 3.38.3-3ubuntu1
Candidate: 3.38.3-3ubuntu1
Version table:
*** 3.38.3-3ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
$ dpkg-query -W|grep mutter
gir1.2-mutter-7:amd64 3.38.3-3ubuntu1
libmutter-7-0:amd64 3.38.3-3ubuntu1
mutter3.38.3-3ubuntu1
mutter-common 3.38.3-3ubuntu1
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 8 14:12:44 2021
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2017-04-21 (1416 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
RebootRequiredPkgs:
libssl1.1
libssl1.1
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.30.0
[Desktop-packages] [Bug 1918190] Re: Enabling/Disabling VPN crashes window manager
As a workaround for anyone, you can use nmcli to bring up a VPN
connection.
Run `nmcli c` to get a list of connections, once you have the name you
can enable it with `nmcli c up $name` or disable it with `nmcli c down
$name`.
--
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/1918190
Title:
Enabling/Disabling VPN crashes window manager
Status in gnome-shell package in Ubuntu:
New
Status in network-manager package in Ubuntu:
New
Bug description:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description: Ubuntu Hirsute Hippo (development branch)
Release: 21.04
$ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk
-F= '{print $2}'
wayland
$ apt-cache policy network-manager
network-manager:
Installed: 1.30.0-1ubuntu1
Candidate: 1.30.0-1ubuntu1
Version table:
*** 1.30.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
$ apt-cache policy gnome-shell
gnome-shell:
Installed: 3.38.3-3ubuntu1
Candidate: 3.38.3-3ubuntu1
Version table:
*** 3.38.3-3ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 8 14:12:44 2021
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2017-04-21 (1416 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
RebootRequiredPkgs:
libssl1.1
libssl1.1
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.30.0 connected started full enabled enabled
disabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918190/+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 1918190] Re: Enabling/Disabling VPN crashes window manager
This looks to be around the time of the issue where I disabled a VPN
connection (from syslog):
Mar 8 14:11:54 splat gnome-shell[677801]: **
Mar 8 14:11:54 splat gnome-shell[677801]:
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
assertion failed: (!clutter_actor_get_reactive (actor))
Mar 8 14:11:54 splat gnome-shell[677801]: Bail out!
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
assertion failed: (!clutter_actor_get_reactive (actor))
Mar 8 14:11:54 splat gnome-shell[677801]: GNOME Shell crashed with signal 6
Mar 8 14:11:54 splat gnome-shell[677801]: == Stack trace for context
0x556edc56f150 ==
Mar 8 14:11:54 splat gnome-shell[677801]: #0 556edea1ffc0 i
resource:///org/gnome/shell/ui/popupMenu.js:390 (1162dc8fad80 @ 138)
Mar 8 14:11:54 splat gnome-shell[677801]: #1 556edea1ff18 i
resource:///org/gnome/shell/ui/status/network.js:1429 (2ab06bf803d0 @ 171)
Mar 8 14:11:54 splat gnome-shell[677801]: #2 556edea1fe80 i
resource:///org/gnome/shell/ui/status/network.js:171 (2ab06bf82560 @ 111)
Mar 8 14:11:54 splat gnome-shell[677801]: #3 7ffef0da2770 b
self-hosted:850 (b5d5c736d80 @ 454)
Mar 8 14:11:54 splat gnome-shell[677801]: #4 556edea1fde0 i
resource:///org/gnome/shell/ui/popupMenu.js:411 (1162dc8face0 @ 56)
Mar 8 14:11:54 splat gnome-shell[677801]: #5 556edea1fd48 i
resource:///org/gnome/shell/ui/popupMenu.js:398 (1162dc8fad30 @ 41)
Mar 8 14:11:54 splat gnome-shell[677801]: #6 556edea1fca8 i
resource:///org/gnome/shell/ui/popupMenu.js:138 (1162dc8fb4c0 @ 88)
Mar 8 14:11:54 splat systemd[1]: Starting Network Manager Script Dispatcher
Service...
Mar 8 14:11:54 splat dbus-daemon[1286]: [system] Successfully activated
service 'org.freedesktop.nm_dispatcher'
** Attachment added: "journal"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1918190/+attachment/5474636/+files/journal
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description: Ubuntu Hirsute Hippo (development branch)
Release: 21.04
$ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk
-F= '{print $2}'
wayland
$ apt-cache policy network-manager
network-manager:
- Installed: 1.30.0-1ubuntu1
- Candidate: 1.30.0-1ubuntu1
+ Installed: 1.30.0-1ubuntu1
+ Candidate: 1.30.0-1ubuntu1
+ Version table:
+ *** 1.30.0-1ubuntu1 500
+ 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
+ 100 /var/lib/dpkg/status
+
+ $ apt-cache policy gnome-shell
+ gnome-shell:
+ Installed: 3.38.3-3ubuntu1
+ Candidate: 3.38.3-3ubuntu1
Version table:
- *** 1.30.0-1ubuntu1 500
+ *** 3.38.3-3ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 8 14:12:44 2021
IfupdownConfig:
- # interfaces(5) file used by ifup(8) and ifdown(8)
- auto lo
- iface lo inet loopback
+ # interfaces(5) file used by ifup(8) and ifdown(8)
+ auto lo
+ iface lo inet loopback
InstallationDate: Installed on 2017-04-21 (1416 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
RebootRequiredPkgs:
- libssl1.1
- libssl1.1
+ libssl1.1
+ libssl1.1
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.30.0 connected started full enabled enabled
disabled enabled enabled
+ RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
+ running 1.30.0 connected started full enabled enabled
disabled enabled enabled
--
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/1918190
Title:
Enabling/Disabling VPN crashes window manager
Status in gnome-shell package in Ubuntu:
New
Status in network-manager package in Ubuntu:
New
Bug description:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description:
[Desktop-packages] [Bug 1918190] [NEW] Enabling/Disabling VPN crashes window manager
Public bug reported:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description:Ubuntu Hirsute Hippo (development branch)
Release:21.04
$ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk -F=
'{print $2}'
wayland
$ apt-cache policy network-manager
network-manager:
Installed: 1.30.0-1ubuntu1
Candidate: 1.30.0-1ubuntu1
Version table:
*** 1.30.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 8 14:12:44 2021
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2017-04-21 (1416 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
RebootRequiredPkgs:
libssl1.1
libssl1.1
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.30.0 connected started full enabled enabled
disabled enabled enabled
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug hirsute wayland-session
--
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/1918190
Title:
Enabling/Disabling VPN crashes window manager
Status in network-manager package in Ubuntu:
New
Bug description:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description: Ubuntu Hirsute Hippo (development branch)
Release: 21.04
$ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk
-F= '{print $2}'
wayland
$ apt-cache policy network-manager
network-manager:
Installed: 1.30.0-1ubuntu1
Candidate: 1.30.0-1ubuntu1
Version table:
*** 1.30.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 8 14:12:44 2021
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2017-04-21 (1416 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404)
RebootRequiredPkgs:
libssl1.1
libssl1.1
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.30.0 connected started full enabled enabled
disabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1918190/+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 1917926] Re: Window focus issues for Xorg sessions in 3.38.3-3ubuntu1
I'm using xorg because wayland has bug #1918189 (can't share terminals in Google Meet) blocking me from using wayland as a daily driver. -- 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/1917926 Title: Window focus issues for Xorg sessions in 3.38.3-3ubuntu1 Status in mutter package in Ubuntu: Triaged Bug description: I switched to an Xorg session in hirsute today after upgrading gnome- shell and mutter packages which just hit the release package. There are very strange focus issues. Clicking on a window doesn't raise it to the front, alt-tab seems to only switch between a subset of the one windows. It's impossible to move windows with the mouse and resizing does not work. This occurred with: gnome-shell=3.38.3-3ubuntu1 mutter=3.38.3-3ubuntu1 Downgrading these packages fixed it: gnome-shell=3.38.3-2ubuntu2 mutter=3.38.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+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 1918189] [NEW] Can not share gnome-terminal in Google Meet under xwayland
Public bug reported: When running xwayland in Hirsute I am unable to share gnome-terminal windows from Google Meet. In Google Meet running in Chrome v89.0.4389.82 when I select the share a window I do not see my gnome- terminal windows listed as an option to share. Here is what I am running with, I can provide additional package info $ lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 $ apt-cache policy xwayland xwayland: Installed: 2:1.20.10-3ubuntu3 Candidate: 2:1.20.10-3ubuntu3 Version table: *** 2:1.20.10-3ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status I'd be nice to be able to use wayland and have features on par with xorg and right now I have to do this because of bug #1917926 making xorg unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xwayland 2:1.20.10-3ubuntu3 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:03:30 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.5, 5.10.0-14-generic, x86_64: installed v4l2loopback, 0.12.5, 5.8.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1416 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7 RebootRequiredPkgs: libssl1.1 libssl1.1 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.M0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.M0:bd01/23/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.4-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.3.4-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Mon Oct 15 10:44:00 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.1-3ubuntu2 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute reproducible single-occurrence ubuntu wayland-session -- 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/1918189 Title: Can not share gnome-terminal in Google Meet under xwayland Status in xorg-server package in Ubuntu: New Bug description: When running xwayland in Hirsute I am unable to share gnome-terminal windows from Google Meet. In Google Meet running in Chrome v89.0.4389.82 when I select the share a window I do not see my gnome- terminal windows listed as an option to share. Here is what I am running with, I can provide additional package info $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ apt-cache policy xwayland xwayland: Installed: 2:1.20.10-3ubuntu3 Candidate: 2:1.20.10-3ubuntu3 Version table: ***
[Desktop-packages] [Bug 1909788] [NEW] Synaptics touchpad not recognized
Public bug reported: Laptop model: Clevo P650RS-G Touchpad make: Synaptics lsb_release: 20.04.1 LTS libinput version: 0.29.0-1 The touchpad refuses to work even in Ubuntu Live boot, but it is operational in Windows 10. In previous releases, I've been able to add "i8042.reset" to the grub configuration to make the touchpad work sporadically, but that fails completely now. The touchpad does not show up in xinput or the synaptics driver. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-libinput 0.29.0-1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 31 19:27:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu InstallationDate: Installed on 2020-12-31 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Eluktronics Inc P650RS-G ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=d03f6b5f-4057-4b19-87d8-95f4b9a1b567 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.05 dmi.board.asset.tag: Tag 12345 dmi.board.name: P650RS-G dmi.board.vendor: Eluktronics Inc dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Eluktronics Inc dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd10/18/2016:svnEluktronicsInc:pnP650RS-G:pvrNotApplicable:rvnEluktronicsInc:rnP650RS-G:rvrNotApplicable:cvnEluktronicsInc:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P650RS-G dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Eluktronics Inc version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "/proc/bus/input/devices" https://bugs.launchpad.net/bugs/1909788/+attachment/5448464/+files/devices -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1909788 Title: Synaptics touchpad not recognized Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: Laptop model: Clevo P650RS-G Touchpad make: Synaptics lsb_release: 20.04.1 LTS libinput version: 0.29.0-1 The touchpad refuses to work even in Ubuntu Live boot, but it is operational in Windows 10. In previous releases, I've been able to add "i8042.reset" to the grub configuration to make the touchpad work sporadically, but that fails completely now. The touchpad does not show up in xinput or the synaptics driver. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-libinput 0.29.0-1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 31 19:27:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu InstallationDate: Installed on 2020-12-31 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Eluktronics Inc P650RS-G ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=d03f6b5f-4057-4b19-87d8-95f4b9a1b567 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.05 dmi.board.asset.tag: Tag 12345 dmi.board.name: P650RS-G dmi.board.vendor: Eluktronics Inc dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag
[Desktop-packages] [Bug 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)
On my system, I have a consistent Deny on cups-browsed --capable, one example from 281300Z November 2020 being: Nov 28 13:00:24 hotrodgpc-desktop kernel: [ 52.928672] audit: type=1400 audit(1606597224.111:54): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=1496 comm ="cups-browsed" capability=23 capname="sys_nice" I have set cups-browsed to complain mode in AppArmor pending the bugfix. --- ubuntu® 20.04.1-LTS AMD64 AuthenticAMD® Athlon64® 3500+ / 3.3 GiB memory AuthenticAMD® RS780 GPU GNOME 3.36.3 -- 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/1897369 Title: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE) Status in cups package in Ubuntu: Confirmed Bug description: In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents `/usr/sbin/cups-browsed` to change its nice value. $ sudo dmesg | grep apparmor [541870.509461] audit: type=1400 audit(1600898428.089:60): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=62030 comm="cups-browsed" capability=23 capname="sys_nice" [628298.779668] audit: type=1400 audit(1600984854.115:61): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=66850 comm="cups-browsed" capability=23 capname="sys_nice" [714667.424963] audit: type=1400 audit(1601071220.527:62): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=76828 comm="cups-browsed" capability=23 capname="sys_nice" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369/+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 1900347] Re: Doesn't import gpg keys Doesn't export armored (asc) gpg keys
On Mon, 19 Oct 2020 09:46:44 - Sebastien Bacher <1900...@bugs.launchpad.net> wrote: > Thank you for your bug report, when you write 'won't import', what do > you do and what error do you get exacly? is it raising an error > dialog? action as if it was importing but the content is missing? > could you also provide some details on the gpg you are trying to > import (dsa, rsa, length) > > ** Changed in: seahorse (Ubuntu) >Importance: Undecided => Low > > ** Changed in: seahorse (Ubuntu) >Status: New => Incomplete > I hope this is not too contorted. I tried 3 keys, a RSA 2048 key created in 2012, a DSA 1024 key created in 2007, and a RSA 2048 key created in 2019. The "Import Key" menu option in Seahorse wont import either a binary nor an armored (asc) version for any of these keys. For either key version of any key an error message pops up "The information in this key has not yet been verified" and underneath the message are the details of the key. In the upper right corner "Import" appears and clicking on it does nothing. The key is not imported. In the file manager window a double click of the asc version of the key or using the menu choice "Open with Import Key" will import the key. A message apperars "the key blaa blaa has been imported". And infact it has. With the binary version of the key "keyfile.pgp" nothing works, no error message no nothing. This binary version can be imported using a terminal. As was noted in the other bug report, the sucessfully added keys are only listed after Seahorse is stopped and restarted. And finally Seahorse menu option "Export" will only export a binary version of keys even thought one of the choices is to export the key as an armored ".asc" version. I hope this is clear and detailed enough. Larry -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1900347 Title: Doesn't import gpg keys Doesn't export armored (asc) gpg keys Status in seahorse package in Ubuntu: Incomplete Bug description: Very similar to bug # 1577198. Seahorse (Passwords and Keys) won't import gpg keys. But if I double click on the gpg key in the file manager it will show as imported after I restart Seahorse. After keys are imported (using the double click method or CLI) they can only be exported as binary keys i.e. keyname.pgp. If I try the option to export as a keyname.asc version (armored) I only get the same binary key. Everything works fine with gpg in a terminal. This is with a fresh install of 20.04.1, Seahorse 3.36-1 with Seahorse-daemon and Seahorse-nautilis installed. The Gnupg version is 2.2.19 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: seahorse 3.36-1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 18 11:32:13 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-10-09 (8 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1900347/+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 1900347] [NEW] Doesn't import gpg keys Doesn't export armored (asc) gpg keys
Public bug reported: Very similar to bug # 1577198. Seahorse (Passwords and Keys) won't import gpg keys. But if I double click on the gpg key in the file manager it will show as imported after I restart Seahorse. After keys are imported (using the double click method or CLI) they can only be exported as binary keys i.e. keyname.pgp. If I try the option to export as a keyname.asc version (armored) I only get the same binary key. Everything works fine with gpg in a terminal. This is with a fresh install of 20.04.1, Seahorse 3.36-1 with Seahorse- daemon and Seahorse-nautilis installed. The Gnupg version is 2.2.19 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: seahorse 3.36-1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 18 11:32:13 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-10-09 (8 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: seahorse (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 seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1900347 Title: Doesn't import gpg keys Doesn't export armored (asc) gpg keys Status in seahorse package in Ubuntu: New Bug description: Very similar to bug # 1577198. Seahorse (Passwords and Keys) won't import gpg keys. But if I double click on the gpg key in the file manager it will show as imported after I restart Seahorse. After keys are imported (using the double click method or CLI) they can only be exported as binary keys i.e. keyname.pgp. If I try the option to export as a keyname.asc version (armored) I only get the same binary key. Everything works fine with gpg in a terminal. This is with a fresh install of 20.04.1, Seahorse 3.36-1 with Seahorse-daemon and Seahorse-nautilis installed. The Gnupg version is 2.2.19 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: seahorse 3.36-1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 18 11:32:13 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-10-09 (8 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1900347/+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 1880191] Re: usb_modeswitch 2.5.2 segfault
Here it is: Starting program: /usr/sbin/usb_modeswitch -W -v 05c6 -p 1000 -K [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Take all parameters from the command line * usb_modeswitch: handle USB devices with multiple modes * Version 2.5.2 (C) Josua Dietze 2017 * Based on libusb1/libusbx ! PLEASE REPORT NEW CONFIGURATIONS ! DefaultVendor= 0x05c6 DefaultProduct= 0x1000 StandardEject=1 [New Thread 0x77d58700 (LWP 4900)] Look for default devices ... found USB ID 17ef:481d found USB ID 0781:5567 found USB ID 1d6b:0002 found USB ID 1d6b:0001 found USB ID 1d6b:0001 found USB ID 1d6b:0001 found USB ID 05c6:1000 vendor ID matched product ID matched found USB ID 1d6b:0002 found USB ID 1d6b:0001 found USB ID 1d6b:0001 found USB ID 1d6b:0001 Found devices in default mode (1) Access device 006 on bus 001 Get the current device configuration ... Current configuration number is 1 Use interface number 0 with class 8 Use endpoints 0x01 (out) and 0x81 (in) USB description data (for identification) Error: could not get description string "serial number" - Manufacturer: Qualcomm, Incorporated Product: Qualcomm CDMA Technologies MSM Serial No.: read error - Sending standard EJECT sequence Looking for active drivers ... Thread 1 "usb_modeswitch" received signal SIGSEGV, Segmentation fault. 0x9771 in detachDrivers () at usb_modeswitch.c:1478 1478usb_modeswitch.c: No such file or directory. (gdb) bt #0 0x9771 in detachDrivers () at usb_modeswitch.c:1478 #1 0x7109 in main (argc=, argv=) at usb_modeswitch.c:737 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1880191 Title: usb_modeswitch 2.5.2 segfault Status in usb-modeswitch package in Ubuntu: Incomplete Bug description: The version that is shipped with Ubuntu 20.04 x64 segfaults: Starting program: /usr/sbin/usb_modeswitch -W -v 05c6 -p 1000 -K [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Take all parameters from the command line * usb_modeswitch: handle USB devices with multiple modes * Version 2.5.2 (C) Josua Dietze 2017 * Based on libusb1/libusbx ! PLEASE REPORT NEW CONFIGURATIONS ! DefaultVendor= 0x05c6 DefaultProduct= 0x1000 StandardEject=1 [New Thread 0x77d58700 (LWP 16370)] Look for default devices ... found USB ID 05ac:8406 found USB ID 1d6b:0003 found USB ID 05ac:0291 found USB ID 05ac:828f found USB ID 0a5c:4500 found USB ID 05c6:1000 vendor ID matched product ID matched found USB ID 0781:5567 found USB ID 1d6b:0002 Found devices in default mode (1) Access device 015 on bus 001 Get the current device configuration ... Current configuration number is 1 Use interface number 0 with class 8 Use endpoints 0x01 (out) and 0x81 (in) USB description data (for identification) Error: could not get description string "serial number" - Manufacturer: Qualcomm, Incorporated Product: Qualcomm CDMA Technologies MSM Serial No.: read error - Sending standard EJECT sequence Looking for active drivers ... libusb: error [_open_sysfs_attr] open /sys/bus/usb/devices/1-2/bConfigurationValue failed ret=-1 errno=2 Thread 1 "usb_modeswitch" received signal SIGSEGV, Segmentation fault. 0x9771 in ?? () (gdb) bt #0 0x9771 in ?? () #1 0x7109 in ?? () #2 0x77dd10b3 in __libc_start_main (main=0x6820, argc=7, argv=0x7fffe098, init=, fini=, rtld_fini=, stack_end=0x7fffe088) at ../csu/libc-start.c:308 #3 0x7bde in ?? () I tried to compile latest available version: usb- modeswitch-2.6.0.tar.bz2 (md5: be73dcc84025794081a1d4d4e5a75e4c) and it does not crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1880191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
I'm able to switch to 125% after switching to nouveau driver and restarting. The only issue I'm experiencing is a smaller cursor when using snap' Telegram Desktop, but it seems to be a bug on their side. -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Same issue with GeForce 920M with nvidia drivers (ASUS TP-300LJ). -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880986] [NEW] Unreasonable "Black Over Print" default value for Ricoh C261SFNw introduced in Focal
Public bug reported: After the Focal upgrade, my Ricoh laser printer began printing solid black over every page. The image was still legible but the page looked like a sheet of carbon paper with massive black toner waste. The problem was a new printer option "Black Over Print" which surfaced in Focal and defaulted to "On". It had to be turned "Off" to restore the previous behavior. Please determine why "On" was chosen as a reasonable default for this option, because it's not :-) ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1880986 Title: Unreasonable "Black Over Print" default value for Ricoh C261SFNw introduced in Focal Status in system-config-printer package in Ubuntu: New Bug description: After the Focal upgrade, my Ricoh laser printer began printing solid black over every page. The image was still legible but the page looked like a sheet of carbon paper with massive black toner waste. The problem was a new printer option "Black Over Print" which surfaced in Focal and defaulted to "On". It had to be turned "Off" to restore the previous behavior. Please determine why "On" was chosen as a reasonable default for this option, because it's not :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1880986/+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 1880492] Re: nautilus takes a long time to shut down
per request in #ubuntu-bugs: setting to Triaged, adding upstream bug, setting importance to Low. ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/423 Importance: Unknown Status: Unknown ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: Confirmed => Triaged -- 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/1880492 Title: nautilus takes a long time to shut down Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: Start nautilus from the command line. Immediately close the open window with Ctrl-W. (this took me less than a second) The nautilus window closes immediately, but nautilus takes 13.5 sec to shut down: jlquinn@cerberus:~$ time nautilus Nautilus-Share-Message: 23:12:39.682: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) real 0m13.557s user 0m0.900s sys 0m0.103s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-102.103-generic 4.15.18 Uname: Linux 4.15.0-102-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 24 23:11:42 2020 InstallationDate: Installed on 2016-05-30 (1455 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-09-17 (616 days ago) usr_lib_nautilus: gnome-mplayer 1.0.9-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1880492/+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 1762215] Re: wvdial crashes after upgrade to bionic 18.04
This is still reproducible in Bionic 18.04, but not on the latest Focal 20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wvdial in Ubuntu. https://bugs.launchpad.net/bugs/1762215 Title: wvdial crashes after upgrade to bionic 18.04 Status in wvdial package in Ubuntu: New Status in wvdial package in Debian: Fix Released Bug description: Since upgrading Ubuntu from 17.10 to 18.04 wvdial is crashing with the following error message when connection is established: # wvdial 3gconnect --> WvDial: Internet dialer version 1.61 --> Initializing modem. --> Sending: ATZ ATZ OK --> Sending: ATQ0 V1 E1 S0=0 +FCLASS=0 ATQ0 V1 E1 S0=0 +FCLASS=0 OK --> Sending: AT+CGDCONT=1,"IP","internet" AT+CGDCONT=1,"IP","internet" OK --> Modem initialized. --> Sending: ATDT*99# --> Waiting for carrier. ATDT*99# CONNECT 2100 --> Carrier detected. Starting PPP immediately. --> Starting pppd at Sun Apr 8 18:50:07 2018 --> Pid of pppd: 7400 wvdial: utils/wvtask.cc:303: static int WvTaskMan::yield(int): Assertion `*current_task->stack_magic == WVTASK_MAGIC' failed. Aborted (core dumped) The connection is still established. It happens after pppd is already started. On 17.10 I did not encounter this issue. Package version: $ apt policy wvdial wvdial: Installed: 1.61-4.1build1 Candidate: 1.61-4.1build1 Version table: *** 1.61-4.1build1 500 500 http://se.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status It happens also on Debian. See the following for more details: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863039 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wvdial/+bug/1762215/+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 1850201] Re: Memory usage grows when locking/unlocking the screen
I'm also seeing a steady growth in gnome-shell's memory usage over time. I have extensions installed that don't appear to be required by Ubuntu 20.04 (meaning if I try to 'apt remove' them, apt wants to remove 'ubuntu-deskop', too). Here's the listing of my relevant extensions directories: $ ls -l /usr/share/gnome-shell/extensions/ total 12 drwxr-xr-x 2 root root 4096 Apr 27 09:35 'desktop-icons@csoriano'/ drwxr-xr-x 3 root root 4096 Apr 27 09:28 'ubuntu-appindicat...@ubuntu.com'/ drwxr-xr-x 3 root root 4096 Apr 27 09:31 'ubuntu-d...@ubuntu.com'/ $ ls -l ~/.local/share/gnome-shell/extensions/ total 0 $ Over time I find that gnome-shell's reported memory usage per 'top' steadily climbs. Today it was showing 3.1g before I finally logged out of the machine and back in again. I wish I had more information to share, but at this time, I don't. Will report back if/when I do, though. -- 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/1850201 Title: Memory usage grows when locking/unlocking the screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Many times after logging in gnome-shell uses 600-800MB of memory, and also slows down quite a bit (e.g., 20-30 seconds waiting for login). Only after multiple resets (Alt+F2 r) drops the memory usage below 200MB. I use my computer mainly for work, and the above phenomenon is quite disturbing. After a couple of hours of work memory usage is growing over 400MB again, and sometimes the reset (Alt+F2 r) doesn't help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest Ubuntu also behaves similarly. This is an old issue, it was present in 18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all of them suffer with this problem. Anyone can check this with the "gnome-shell memory monitor" gnome-shell extension. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Oct 28 20:28:38 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-04 (297 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850201/+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 1850201] Re: Memory usage grows when locking/unlocking the screen
I meant to say, "I have *no* extensions installed that don't..." -- 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/1850201 Title: Memory usage grows when locking/unlocking the screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Many times after logging in gnome-shell uses 600-800MB of memory, and also slows down quite a bit (e.g., 20-30 seconds waiting for login). Only after multiple resets (Alt+F2 r) drops the memory usage below 200MB. I use my computer mainly for work, and the above phenomenon is quite disturbing. After a couple of hours of work memory usage is growing over 400MB again, and sometimes the reset (Alt+F2 r) doesn't help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest Ubuntu also behaves similarly. This is an old issue, it was present in 18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all of them suffer with this problem. Anyone can check this with the "gnome-shell memory monitor" gnome-shell extension. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Oct 28 20:28:38 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-04 (297 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850201/+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 1877007] Re: The chromium package broken
Adjusting package to chromium-browser. Thank you for opening this bug and helping make Ubuntu better. Can you please tell us what is wrong? You opened a bug against a browser, set the package to the Linux kernel, and did not give us any explanations on what would be broken. ** Package changed: linux (Ubuntu) => chromium-browser (Ubuntu) ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1877007 Title: The chromium package broken Status in chromium-browser package in Ubuntu: Incomplete Bug description: he following packages will be upgraded: chromium-browser 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/48.3 kB of archives. After this operation, 230 MB disk space will be freed. Do you want to continue? [Y/n] y Preconfiguring packages ... (Reading database ... 410692 files and directories currently installed.) Preparing to unpack .../chromium-browser_80.0.3987.163-0ubuntu1_amd64.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ==> Installing the chromium snap Progress: [ 14%] [..] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: norah 2690 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 08:47:12 2020 HibernationDevice: RESUME=UUID=ae9d7101-3e17-4133-ac4b-c4b858d77858 InstallationDate: Installed on 2017-09-02 (976 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 90E8CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2016 dmi.bios.vendor: LENOVO dmi.bios.version: M05KT54A dmi.board.name: SKYBAY dmi.board.vendor: LENOVO dmi.board.version: NOK dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrM05KT54A:bd02/24/2016:svnLENOVO:pn90E8CTO1WW:pvrYangTianM4900c-00:rvnLENOVO:rnSKYBAY:rvrNOK:cvnLENOVO:ct3:cvr: dmi.product.family: YangTianM4900c-00 dmi.product.name: 90E8CTO1WW dmi.product.sku: LENOVO_MT_90E8_BU_LENOVO_FM_YangTianM4900c-00 dmi.product.version: YangTianM4900c-00 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877007/+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 1849119] Re: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to install/upgrade: error: snap "chromium" has "install-snap" change in progress
An user called chirag patel solves the problem and posted it on Medium:
https://medium.com/@chiragpatel_52497/unable-to-install-package-name-
snap-package-name-has-install-snap-change-in-progress-b6768f2ce81d
This solves the problem:
Snap is probably still working on something in the background (or at
least it thinks so). Open a terminal and run snap changes so see a list
of ongoing changes.
$ snap changes ... 123 Doing 2018-04-28T10:40:11Z - Install "foo"
snap ...
You can abort ongoing change(s):
$ sudo snap abort 123
Then you should be able to successfully install chromium-brownser
through the software center.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1849119
Title:
package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
install/upgrade: error: snap "chromium" has "install-snap" change in
progress
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
Showing system error
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
AptOrdering:
chromium-browser:amd64: Install
NULL: ConfigurePending
Architecture: amd64
Date: Mon Oct 21 18:05:24 2019
ErrorMessage: new chromium-browser package pre-installation script subprocess
returned error exit status 10
InstallationDate: Installed on 2019-10-21 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.19.7ubuntu2
apt 1.9.4
Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.120
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
Snap.ChromiumVersion:
mkdir: cannot create directory '/run/user/0': Permission denied
Chromium 77.0.3865.120 snap
SourcePackage: chromium-browser
Title: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
install/upgrade: new chromium-browser package pre-installation script
subprocess returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849119/+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 1870988] [NEW] Xorg crashed with SIGABRT
Public bug reported: I'm not exactly sure what triggered this bug however, I was installing wire, session-desktop and a few minutes beforehand I uninstalled wire. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 15:29:29 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.4, 5.4.0-21-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GT216M [NVS 5100M] [10de:0a2c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT216M [NVS 5100M] [103c:1521] InstallationDate: Installed on 2020-04-05 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Hewlett-Packard HP EliteBook 8540p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=07ef73e3-6724-4de6-af31-bbb7c81944c9 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/xorg/modules/libglamoregl.so Title: Xorg crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 11/11/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CVD Ver. F.60 dmi.board.name: 1521 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 32.36 dmi.chassis.asset.tag: NG00162275 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CVDVer.F.60:bd11/11/2015:svnHewlett-Packard:pnHPEliteBook8540p:pvr:rvnHewlett-Packard:rn1521:rvrKBCVersion32.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8540p dmi.product.sku: NU486AV dmi.sys.vendor: Hewlett-Packard separator: 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.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: xorg-server (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash focal ubuntu ** Information type changed from Private to Public -- 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/1870988 Title: Xorg crashed with SIGABRT Status in xorg-server package in Ubuntu: New Bug description: I'm not exactly sure what triggered this bug however, I was installing wire, session-desktop and a few minutes beforehand I uninstalled wire. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 15:29:29 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.4, 5.4.0-21-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GT216M [NVS 5100M] [10de:0a2c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT216M [NVS 5100M] [103c:1521] InstallationDate: Installed on 2020-04-05 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Hewlett-Packard HP EliteBook 8540p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none
[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Facing the same problem with an HP Spectre X360, I tested several distributions and several different kernel versions. I also followed several guides explaining how the problem could be solved, but none worked for me. What I find curious is that in Ubuntu 19.10 and 20.04 in live mode the microphone works perfectly (both internal and the headset). I copied the contents of the alsa-base.conf file from live and overwrote that of the distribution, but it also didn't work. Tested with kernel: 5.0x, 5.3.x, 5.4.x, 5.5x (family 4.x bring other problems for my hardware) I was also able to use an external microphone using a USB adapter. -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1757375] Re: Desktop unable to Suspend when Inactive
Still a major laptop usability problem in eoan. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-desktop-privileges in Ubuntu. https://bugs.launchpad.net/bugs/1757375 Title: Desktop unable to Suspend when Inactive Status in policykit-desktop-privileges package in Ubuntu: Confirmed Bug description: On Ubuntu 16.04 and later versions (Xfce/Xubuntu) the power-manager is unable to suspend the system when the user is inactive. A PK user- agent dialog is presented for the user to authenticate first - and as this action occurs specifically when the user is idle and away the PC can end up having an unplanned loss of power when the battery is exhausted. /var/log/auth.log shows: polkitd(authority=local): Operator of unix-session:c2 FAILED to authenticate to gain authorization for action org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power- manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c- f7631ecd0b46] (owned by unix-user:tj) The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry to allow Suspend. Currently it only has an entry for hibernate. Adding the following stanza solves the issue: [Enable suspend by default in logind] Identity=unix-user:* Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit ResultActive=yes ResultInactive=yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+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 73244] Re: Crash when closing firefox after "open with" and having still opened the file
reverting to Triaged per request from PaulW2U. ** Changed in: firefox (Ubuntu) Status: Fix Released => Triaged -- 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/73244 Title: Crash when closing firefox after "open with" and having still opened the file Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: 1. Click on a .deb link 2. Select "open with package installer" 3. click install package after downloaded 4. close firefox (because you don't need it anymore) 5. Enter your password for sudo 6. package manager crashes because the deb file was deleted in the moment you closed firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/73244/+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 1866616] Re: 2nd display stopped working
Attaching the 2nd display via DisplayPort rather than DVI allows me to use it again, so I happen to have a solution, but not everyone may be so lucky. -- 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/1866616 Title: 2nd display stopped working Status in xorg package in Ubuntu: New Bug description: The 2nd display (attached to DVI) has stopped being detected but is used by bios and grub (output ceases once the spinning boot animation starts). I was away for a week but it was working prior to leaving. I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd monitor should be. 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 06:13:23 2020 DistUpgraded: 2020-01-31 09:33:31,151 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1052 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-01-31 (37 days ago) dmi.bios.date: 01/23/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.M0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.M0:bd01/23/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. 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 20.0.0-1ubuntu1 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 xserver.bootTime: Mon Oct 15 10:44:00 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.1-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1866616/+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 1866616] [NEW] 2nd display stopped working
Public bug reported: The 2nd display (attached to DVI) has stopped being detected but is used by bios and grub (output ceases once the spinning boot animation starts). I was away for a week but it was working prior to leaving. I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd monitor should be. 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 06:13:23 2020 DistUpgraded: 2020-01-31 09:33:31,151 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1052 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-01-31 (37 days ago) dmi.bios.date: 01/23/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.M0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.M0:bd01/23/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. 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 20.0.0-1ubuntu1 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 xserver.bootTime: Mon Oct 15 10:44:00 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.1-3ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug champagne focal regression reproducible ubuntu ** Description changed: The 2nd display (attached to DVI) has stopped being detected but is used by bios and grub (output ceases once the spinning boot animation starts). I was away for a week but it was working prior to leaving. - I've notices that Xorg.0.log shows fbdev rather than amdgpu in use (as - it had in the past). + I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd + monitor should be. 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 06:13:23 2020 DistUpgraded: 2020-01-31 09:33:31,151 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) -Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] + Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) + Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1052 days ago) InstallationMedia:
[Desktop-packages] [Bug 1866616] Re: 2nd display stopped working
The log shows "open /dev/dri/card0: No such file or directory" but it does exist: $ ls -l /dev/dri/card0 crw-rw+ 1 root render 226, 0 Mar 9 06:12 /dev/dri/card0 Unplugging the display from DVI-D-0 and plugging it back in does not result in showing up in xrandr output. -- 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/1866616 Title: 2nd display stopped working Status in xorg package in Ubuntu: New Bug description: The 2nd display (attached to DVI) has stopped being detected but is used by bios and grub (output ceases once the spinning boot animation starts). I was away for a week but it was working prior to leaving. I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd monitor should be. 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 06:13:23 2020 DistUpgraded: 2020-01-31 09:33:31,151 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 470 [1682:9470] InstallationDate: Installed on 2017-04-21 (1052 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-01-31 (37 days ago) dmi.bios.date: 01/23/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.M0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.M0:bd01/23/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. 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 20.0.0-1ubuntu1 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 xserver.bootTime: Mon Oct 15 10:44:00 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.1-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1866616/+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 1865169] Re: volume and light not working in Gnome Shell 3.35
reverting to Fix Committed as requested ** Changed in: gnome-shell (Ubuntu) Status: Fix Released => 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/1865169 Title: volume and light not working in Gnome Shell 3.35 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Committed Bug description: After upgrading to GNOME shell 3.35, the speaker icon in top bar is missing and both volume and light sliders are set to 0. Changing volume and light from keyboard works, but has no effect in gnome shell dropdown. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-16.19-generic 5.4.22 Uname: Linux 5.4.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 18:57:54 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (118 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1865169/+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 694407] Re: [ICH - SiS SI7012] Playback problem
This was an old problem many years ago, I am suprised that I got this
notification now especially as I am now using 18.04LTS and 19.10.
On 05/03/2020 07:01, Marcus Tomlinson wrote:
> This release of Ubuntu is no longer receiving maintenance updates. If
> this is still an issue on a maintained version of Ubuntu please let us
> know.
>
> ** Changed in: alsa-driver (Ubuntu)
> Status: Confirmed => Incomplete
>
--
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/694407
Title:
[ICH - SiS SI7012] Playback problem
Status in alsa-driver package in Ubuntu:
Incomplete
Bug description:
No sound after initial opening of Diablo II when running under Wine
Ubuntu 10.04 LTS
Wine 1.2
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-26.48-generic 2.6.32.24+drm33.11
Uname: Linux 2.6.32-26-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: SI7012 [SiS SI7012], device 0: Intel ICH [SiS SI7012]
Subdevices: 0/1
Subdevice #0: subdevice #0
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: adrian 1332 F pulseaudio
adrian21093 F winecfg.exe
/dev/snd/pcmC0D0p: adrian 1332 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'SI7012'/'SiS SI7012 with AD1888 at irq 18'
Mixer name : 'Analog Devices AD1888'
Components : 'AC97a:41445368'
Controls : 45
Simple ctrls : 31
Date: Sat Dec 25 22:37:22 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.2)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SelectedCard: 0 SI7012 ICH - SiS SI7012
SourcePackage: alsa-driver
Symptom: audio
Title: [ICH - SiS SI7012] Playback problem
dmi.bios.date: 10/08/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: 760GXK8MC
dmi.board.vendor: WinFast
dmi.chassis.type: 3
dmi.modalias:
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/08/2005:svn:pn:pvr:rvnWinFast:rn760GXK8MC:rvr:cvn:ct3:cvr:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/694407/+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 1865263] Re: [Focal] xkb-data 2.29-1 breaks AZERTY keyboard
I can confirm this. This morning after upgrading I found myself with a US keyboard layout without realizing why, and with no way to get back to my own, not from dpkg/reconfigure keyboard/configuration nor from localectl. (those are supposed to be hyphens, yeah) The funny thing is that in gnome/terminal my layout is fully recognized, it-s just firefox and some other app that do not play nice. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1865263 Title: [Focal] xkb-data 2.29-1 breaks AZERTY keyboard Status in xkeyboard-config: Unknown Status in x11-xkb-utils package in Ubuntu: In Progress Bug description: Running : Ubuntu GNOME session 20.04 up to date GNOME Shell + Mutter 3.35.91 Wayland session French language configuration (fr in kb config files) AZERTY keyboard Upgrading from 2.26-2ubuntu4 to 2.29-1 caused my French AZERTY keyboard to be QWERTY. If I run : setxkbmap fr in a terminal, then everything becomes ok again. The issue is not present in GNOME Terminal but is present in Synaptic or Firefox e.g., I guess it could be X/Wayland apps difference ? Anyway, downgrading to xkb-data 2.26-2ubuntu4 did solve the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1865263/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed
Daniel.. anything else i should try to equip you with more info to debug this? Thanks. -- 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/1864781 Title: System with GeForce GT 520 failed to boot when nvidia-390 was installed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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.2 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/nvidia-graphics-drivers-340/+bug/1864781/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed
1. Added to /etc/X11/Xwrapper.config : needs_root_rights = yes (as instructed in bug 1716857. 2. Open terminal, input "sudo apt install nvidia-driver-390". 3. After installation complete, input "systemctl reboot" to reboot. 4. Screen went blank on reboot, cursor blinking at around the top left corner. 5. Pressed Alt Ctrl F2 to bring up tty2, then input "sudo apt-get remove --purge nvidia-*" to remove nvidia driver. 6. After removal complete, input "systemctl reboot" to reboot. 7. Reboot OK. System OK with Nouveau driver. 8. Ran journalctl to generate attached Summary: bug 1716857 didn't help. ** Attachment added: "boot-1.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331457/+files/boot-1.txt -- 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/1864781 Title: System with GeForce GT 520 failed to boot when nvidia-390 was installed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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.2 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/nvidia-graphics-drivers-340/+bug/1864781/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed
to add, after step 4: 4a. i waited a little longer and noticed a jagged dialogue window popped up (attached). i tried to input my password, but neither mouse nor keyboard was functional. i waited again, and later proceeded to resume at step 5. ** Attachment added: "dialogue box.jpeg" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331458/+files/dialogue%20box.jpeg -- 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/1864781 Title: System with GeForce GT 520 failed to boot when nvidia-390 was installed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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.2 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/nvidia-graphics-drivers-340/+bug/1864781/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed
thanks in advance -- 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/1864781 Title: System with GeForce GT 520 failed to boot when nvidia-390 was installed Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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.2 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/linux/+bug/1864781/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed
** Attachment added: "boot-4.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331432/+files/boot-4.txt -- 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/1864781 Title: System with GeForce GT 520 failed to boot when nvidia-390 was installed Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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.2 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/linux/+bug/1864781/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed
** Attachment added: "boot-2.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331430/+files/boot-2.txt -- 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/1864781 Title: System with GeForce GT 520 failed to boot when nvidia-390 was installed Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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.2 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/linux/+bug/1864781/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed
** Attachment added: "boot-5.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331433/+files/boot-5.txt -- 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/1864781 Title: System with GeForce GT 520 failed to boot when nvidia-390 was installed Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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.2 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/linux/+bug/1864781/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed
Thanks Daniel... i did what you requested. Following is a recap of the process, FYI: 1. System running Nouveau driver. All OK. 2. Open terminal, input "sudo apt install nvidia-driver-390". 3. After installation complete, input "systemctl reboot" to reboot. 4. Screen went blank on reboot, cursor blinking at around the top left corner. 5. Pressed Alt Ctrl F2 to bring up tty2, then input "sudo apt-get remove --purge nvidia-*" to remove nvidia driver. 6. After removal complete, input "systemctl reboot" to reboot. 7. Reboot OK. System OK with Nouveau driver. 8. Ran journalctl 5 times to generate the attached 5 files. Here are the 5 journals. Thanks. ** Attachment added: "boot-1.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331429/+files/boot-1.txt -- 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/1864781 Title: System with GeForce GT 520 failed to boot when nvidia-390 was installed Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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.2 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/linux/+bug/1864781/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed
** Attachment added: "boot-3.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1864781/+attachment/5331431/+files/boot-3.txt -- 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/1864781 Title: System with GeForce GT 520 failed to boot when nvidia-390 was installed Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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.2 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/linux/+bug/1864781/+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 1864781] [NEW] Xorg freeze
Public bug reported: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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.2 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 bug freeze nvidia ubuntu -- 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/1864781 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias:
[Desktop-packages] [Bug 1861453] [NEW] The chromium-browser snap package fails to run
Public bug reported: Xubuntu 19.10 chromium-browser 79.0.3945.79-0ubuntu0.19.10.2 Transitional package - chromium-browser -> chromium snap Chromium worked fine before the upgrade to 19.10. There has been a transition to snap packaging. My first attempt to launch the browser results in: % chromium-browser 2020/01/30 11:12:47.911841 cmd_run.go:529: WARNING: XAUTHORITY environment value is not a clean path: "/x/u/jeff/.Xauthority" cannot perform operation: mount --rbind /home /tmp/snap.rootfs_MDsNgD//home: Permission denied % dmesg | grep DENIED (just showing one typical message) [827635.380132] audit: type=1400 audit(1580411567.940:87): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="/snap/core/8268/usr/lib/snapd/snap-confine" name="/tmp/snap.rootfs_MDsNgD/home/" pid=2968 comm="snap-confine" srcname="/x/u/" flags="rw, rbind" The home directory is: /u/jeff The home directory is actually resides on an external drive mounted on /x with /u being a symlink to /x/u % cd / % ls -l home u lrwxrwxrwx 1 root root 1 Jan 2 2015 home -> u lrwxrwxrwx 1 root root 3 Nov 30 2017 u -> x/u %echo $XAUTHORITY /u/jeff/.Xauthority Applications should not care about these sorts of mounts and linkages, but they now appear to be very sensitive to them. What needs to be done to make this work? BTW, I think this move to SNAP is a disaster and completely the wrong way to go. Let's please stick with a single .deb packaging strategy which has proven itself. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: 19.10 chromium snap xubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1861453 Title: The chromium-browser snap package fails to run Status in chromium-browser package in Ubuntu: New Bug description: Xubuntu 19.10 chromium-browser 79.0.3945.79-0ubuntu0.19.10.2 Transitional package - chromium-browser -> chromium snap Chromium worked fine before the upgrade to 19.10. There has been a transition to snap packaging. My first attempt to launch the browser results in: % chromium-browser 2020/01/30 11:12:47.911841 cmd_run.go:529: WARNING: XAUTHORITY environment value is not a clean path: "/x/u/jeff/.Xauthority" cannot perform operation: mount --rbind /home /tmp/snap.rootfs_MDsNgD//home: Permission denied % dmesg | grep DENIED (just showing one typical message) [827635.380132] audit: type=1400 audit(1580411567.940:87): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="/snap/core/8268/usr/lib/snapd/snap-confine" name="/tmp/snap.rootfs_MDsNgD/home/" pid=2968 comm="snap-confine" srcname="/x/u/" flags="rw, rbind" The home directory is: /u/jeff The home directory is actually resides on an external drive mounted on /x with /u being a symlink to /x/u % cd / % ls -l home u lrwxrwxrwx 1 root root 1 Jan 2 2015 home -> u lrwxrwxrwx 1 root root 3 Nov 30 2017 u -> x/u %echo $XAUTHORITY /u/jeff/.Xauthority Applications should not care about these sorts of mounts and linkages, but they now appear to be very sensitive to them. What needs to be done to make this work? BTW, I think this move to SNAP is a disaster and completely the wrong way to go. Let's please stick with a single .deb packaging strategy which has proven itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1861453/+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 1335558] Re: lexmark e230 needs usb-no-reattach-default=true
Hi, If it's related to this bug, then it could be that it needs an entry in: /usr/share/cups/usb/org.cups.usb-quirks You will need to get the correct usb IDs from lsusb. Quoting from the file I mentioned: # To get the USB vendor and product IDs for a given printer, run the "lsusb" # command, which will show something like the following: # # Bus 002 Device 003: ID ab21:34dc Acme Example Printer # # The "ab21:34dc" is the vendor and product ID, separated by a colon. Append the info you get at the end of the file. Save it. Turn off your printer. Then turn it on again. -- 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/1335558 Title: lexmark e230 needs usb-no-reattach-default=true Status in cups package in Ubuntu: Confirmed Bug description: Hi, This printer requires usb-no-reattach-default=true option otherwise, it will print gibberish after successfully completing its first print job after being powered on. $ lsusb Bus 002 Device 004: ID 043d:009a Lexmark International, Inc. This is similar to bug #1084164, but with a different Lexmark Laser printer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1335558/+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 1075923] Re: nautilus hangs copying large directories from a samba share
Still a problem on Eoan. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1075923 Title: nautilus hangs copying large directories from a samba share Status in gvfs: Fix Released Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Precise: Confirmed Status in gvfs source package in Raring: Fix Released Bug description: Impact: copies from/to samba share often end up hanging Test case: - visit a smb location in nautilus - copies data from/to it (some non trivial directories makes the issues easier to trigger) - the copy should complete without hanging Regression potentiel: Check that nautilus is still working correctly and than you don't have issues copying data from/to remote locations --- Problem === Copying files to and from samba shares (this includes Windows shares) is unreliable in Ubuntu 12.10 and Ubuntu 13.04 when using nautilus' integrated samba client (gvfs-smb): The copy randomly hangs after a few files or a few GB. Workaround == Until gvfs-smb is fixed, use the kernel samba client (cifs) that works reliably, is faster, but needs some terminal commands to get going: # sudo -s # mkdir /mnt/cifs # mount -t cifs -o user=YOUR_SAMBA_USER -o uid=YOUR_LINUX_USER "//SAMBA_SERVER/SAMBA_SHARE" /mnt/cifs It will ask for you password, you can then access the shared files at /mnt/cifs. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1075923/+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 1842161] Re: api hack or virus i think idk
Thank you for opening this bug and helping make Ubuntu better. Can you explain what is wrong? "idk how to show you" means we also do not know what to look for... ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1842161 Title: api hack or virus i think idk Status in xorg package in Ubuntu: Incomplete Bug description: idk how to show you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.394 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 30 23:56:28 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Device [196e:0f00] LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Inspiron 546 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0F896N dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/12/2009:svnDellInc.:pnInspiron546:pvr:rvnDellInc.:rn0F896N:rvrA03:cvnDellInc.:ct3:cvr: dmi.product.name: Inspiron 546 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1842161/+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 1822181] Re: Ubuntu 18.10 broke dual-screen dual-desktop configuration
I am VERY interested in continuing work on this. I'm now running 19.04 and the problem persists. I cannot change the status so please update it. There has been a long running discussion on the Xfce buglist which you can review here: https://bugzilla.xfce.org/show_bug.cgi?id=15116 The problem seems to be that the move to gtk3 is the source of the condition as it has dropped support for multiple monitors. Olivier Fourdan is maintaining xfwm4 and he has apparently done something internally that allows X11-aware applications to be launched on a separate display (:0.1) in addition to the native display (:0.0), but none of the other Xfce components such as the panel, desktop, etc have the ability to run more than one instance on the main display. In this forum discussion: https://forum.xfce.org/viewtopic.php?pid=50336#p50336 member gert pointed to this patch in the gtk3 repository that seems to indicate that multi-screen support has been added back into the toolkit. https://github.com/xfce- mirror/xfwm4/commit/b52c2f5b740434803342c471d4dcb5dd62eb99a1 However, this patched version of gtk has not yet made it into a Ubuntu distribution. Losing multi-headed independent desktop support has been a terrible step backwards for Ubuntu. Please look into this more closely and make sure that the 19.10 release gets the tools required to get this capability restored. I'll provide additional info if necessary. However, as an end0user in this arena, I don't have more insights into the interactions of the display components making up the various desktop environments. On a couple of other forums, I asked whether there was another flavor of Ubuntu that was properly supporting multiple screens. I received zero replies. Multiple independent desktops is critical (as opposed to Xinerama mode) so that material can be displayed statically on one display while changing workspaces on the other screen. ** Bug watch added: Xfce Bugzilla #15116 https://bugzilla.xfce.org/show_bug.cgi?id=15116 -- 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/1822181 Title: Ubuntu 18.10 broke dual-screen dual-desktop configuration Status in xorg-server package in Ubuntu: Won't Fix Bug description: I'm running Xubuntu. I finally reported this problem to the Xfce group and received this response: "As arandr/xrandr does not detect correctly your 2nd screen, this seems that it is not related directly to Xfce, but a bug in Xubuntu stack. Can you please open a bug on Xubuntu project if the issue is still present for you?" Thus this bug report. I've been running Xubuntu for years with two monitors, each running an independent xfce4 desktop -- i.e., configured without Xinerama. This has worked fine for every upgrade through 18.04. When upgrading to 18.10, something significant changed and the the second monitor (display :0.1) was disabled. After much reading and work, I have only been able to restore some extremely hobbled functionality. I am unable to get a second xfce4-desktop, panel or window manager running on the second screen. I have assembled detailed screenshots and command output at the following link: http://smallthoughts.com/xfce/xfce.html I'm using an NVIDIA Quadro K-4000 graphics card and no hardware changes were made between 18.04 and 18.10. The nvidia-settings tool reports both monitors active (as configured in /etc/X11/xorg.conf) but the xfce4-display-settings and aarandr tools each show only one display (although xrandr can be forced to report on the second display. See full documentation at the above link.) What changed in the latest release, and what needs to be done to get the second monitor running a second desktop once again? I have been struggling with this for many months now and it has severely impacted the use of my system. As a new release of Ubuntu in coming, I would appreciate it if this could be prioritized and addressed as quickly as possible. I will provide additional information upon request. P.S.: There is really no documentation available on running multiple desktops on separate screens when Xinerama is not used to tie the screens together into a single desktop. This is a common configuration and I would like to request that as part of the solution to this problem, the setup steps be documented and this multi-desktop configuration be made a standard part of the development and testing process for each Ubuntu release. 13-> lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1822181/+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 1827790] Re: Dell XPS 13 9380 - Screen flashes
On the basis of 3 of us deeming that the symptoms of the other bug are different to the ones described in this bug, I have removed the duplicate link. I hope that's OK. If it helps narrow it down, it seems that we all have the non-touch 1080p version, and all notice it much more when Night Light is enabled. ** This bug is no longer a duplicate of bug 1826125 Dell XPS 13 9380 flickering (Whiskey Lake) -- 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/1827790 Title: Dell XPS 13 9380 - Screen flashes Status in xorg package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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/xorg/+bug/1827790/+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 1827790] Re: Dell XPS 13 9380 - Screen flashes
*** This bug is a duplicate of bug 1826125 *** https://bugs.launchpad.net/bugs/1826125 I agree with mactyr that this should not be a duplicate of that bug. The flaw that I see is not what is shown in those videos. There is no glitching, it is the whole screen flashing brighter, and is why I used the word "flashes" in the title, as opposed to "flickers" or "glitches". -- 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/1827790 Title: Dell XPS 13 9380 - Screen flashes Status in xorg package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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/xorg/+bug/1827790/+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 810065] Re: "@#S*" Characters are overlap with each other in Tamil Terminal
The bug is still present in gnome-terminal on Ubuntu 18.04. Instead of printing like the one below ஜூன் 2019 ஞா தி செ பு வி வெ ச the font printed on screen appear like the one shown in the attached "gnome-terminal-tamil-print.png" ** Attachment added: "The picture shows how the font is rendered in gnome-terminal" https://bugs.launchpad.net/ubuntu/+source/vte/+bug/810065/+attachment/5272396/+files/gnome-terminal-tamil-print.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/810065 Title: "@#S*" Characters are overlap with each other in Tamil Terminal Status in vte package in Ubuntu: Confirmed Bug description: Bug Description: Characters such as ~!@#$%^&*() are not displayed correctly in Terminal when Tamil Language is used. These characters overlap each other (see picture1). See picture2 for asterisk character overlapping with alphabets in Terminal and not overlapping in gedit. Expected output: In GNOME terminal, the "@#S*" characters should not overlap. lsb_release -rd output: Description: Ubuntu 10.10 Release: 10.10 ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-terminal 2.32.0-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.35-30.54-generic 2.6.35.13 Uname: Linux 2.6.35-30-generic x86_64 Architecture: amd64 Date: Wed Jul 13 13:39:33 2011 ExecutablePath: /usr/bin/gnome-terminal InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007.1) ProcEnviron: LANGUAGE=ta:ta_IN:en_US:en LANG=ta_IN.utf8 SHELL=/bin/bash SourcePackage: gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/810065/+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
