[Desktop-packages] [Bug 2045863] [NEW] Wireplumber often gets hangs / looping on CPU
Public bug reported: The wireplumber service often gets in a bad state on my hw. It will hang on client connections (applications go weird b/c they can't send audio out) and hog a CPU core. Logs don't say much, the "stopped by signal" is when I issued a `systemctl restart…` ``` -- Boot b88c1ec1804140dca41bbfd5c23f60a7 -- gru 07 08:36:11 michal-laptop systemd[10018]: Started wireplumber.service - Multimedia Service Session Manager. gru 07 08:36:11 michal-laptop wireplumber[10046]: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed? gru 07 08:36:11 michal-laptop wireplumber[10046]: PipeWire's libcamera SPA missing or broken. libcamera not supported. gru 07 08:36:11 michal-laptop wireplumber[10046]: Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera gru 07 08:36:11 michal-laptop wireplumber[10046]: Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera gru 07 08:36:52 michal-laptop wireplumber[10046]: Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera gru 07 08:40:22 michal-laptop wireplumber[10046]: stopped by signal: Zakończony gru 07 08:40:22 michal-laptop systemd[10018]: Stopping wireplumber.service - Multimedia Service Session Manager... gru 07 08:40:22 michal-laptop wireplumber[10046]: disconnected from pipewire gru 07 08:40:22 michal-laptop systemd[10018]: Stopped wireplumber.service - Multimedia Service Session Manager. gru 07 08:40:22 michal-laptop systemd[10018]: wireplumber.service: Consumed 1min 50.259s CPU time. gru 07 08:40:22 michal-laptop systemd[10018]: Started wireplumber.service - Multimedia Service Session Manager. gru 07 08:40:22 michal-laptop wireplumber[22625]: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed? gru 07 08:40:22 michal-laptop wireplumber[22625]: PipeWire's libcamera SPA missing or broken. libcamera not supported. gru 07 08:40:23 michal-laptop wireplumber[22625]: Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera gru 07 08:40:23 michal-laptop wireplumber[22625]: Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera gru 07 08:40:23 michal-laptop wireplumber[22625]: Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera ``` ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: wireplumber 0.4.14-4ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Dec 7 08:40:37 2023 InstallationDate: Installed on 2023-10-06 (61 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004) ProcEnviron: LANG=pl_PL.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=screen-256color XDG_RUNTIME_DIR= SourcePackage: wireplumber UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wireplumber (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wireplumber in Ubuntu. https://bugs.launchpad.net/bugs/2045863 Title: Wireplumber often gets hangs / looping on CPU Status in wireplumber package in Ubuntu: New Bug description: The wireplumber service often gets in a bad state on my hw. It will hang on client connections (applications go weird b/c they can't send audio out) and hog a CPU core. Logs don't say much, the "stopped by signal" is when I issued a `systemctl restart…` ``` -- Boot b88c1ec1804140dca41bbfd5c23f60a7 -- gru 07 08:36:11 michal-laptop systemd[10018]: Started wireplumber.service - Multimedia Service Session Manager. gru 07 08:36:11 michal-laptop wireplumber[10046]: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed? gru 07 08:36:11 michal-laptop wireplumber[10046]: PipeWire's libcamera SPA missing or broken. libcamera not supported. gru 07 08:36:11 michal-laptop wireplumber[10046]: Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera gru 07 08:36:11 michal-laptop wireplumber[10046]: Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera gru 07 08:36:52 michal-laptop wireplumber[10046]: Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera gru 07 08:40:22 michal-laptop wireplumber[10046]: stopped by signal: Zakończony gru 07 08:40:22 michal-laptop systemd[10018]: Stopping wireplumber.service - Multimedia Service Session Manager... gru 07 08:40:22 michal-laptop wireplumber[10046]: disconnected from pipewire gru 07 08:40:22 michal-laptop systemd[10018]: Stopped wireplumber.service -
[Desktop-packages] [Bug 1999830] Re: external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR*
*** This bug is a duplicate of bug 1967707 *** https://bugs.launchpad.net/bugs/1967707 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-525 (Ubuntu) Status: New => Confirmed -- 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/1999830 Title: external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Bug description: - ubuntu 22.04.1 - 5.15.0-56-generic - mutter 42.5-0ubuntu1 - using gdm3 - nvidia Driver Version: 525.60.11 (nvidia-driver-525) - prime select to on-demand - 1 external display, 1 internal LCD ``` Added device '/dev/dri/card1' (nvidia-drm) using non-atomic mode setting. Added device '/dev/dri/card0' (i915) using atomic mode setting. Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card1' Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card0' Dec 15 22:13:34 gnome-shell[3203]: Boot VGA GPU /dev/dri/card0 selected as primary Dec 15 22:13:35 gnome-shell[3203]: Secondary GPU initialization failed (Failed to create gbm_surface: No such file or directory). Falling back to GPU-less > Dec 15 22:13:35 gnome-shell[3203]: Using public X11 display :1, (using :2 for managed services) Dec 15 22:13:35 gnome-shell[3203]: Using Wayland display name 'wayland-0' ``` 0. open a terminal `journalctl -f` 1. Open the display setting, switch to join displays, choose external display as primary. 2. try to change some settings like scale, position of the screen, refresh rate, etc, then applay 3. repeat above step several times After 2 changes the external screen freeze forever. Internal screen is still responsible. On each `Apply` The journal recorded an kernel error about nvidia_drm and flooded with clutter-frame-clock error. ``` Dec 15 22:18:52 gnome-shell[3203]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Dec 15 22:18:52 gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit: Invalid argument Dec 15 22:19:25 gnome-shell[3203]: Failed to allocate onscreen framebuffer for /dev/dri/card1: Failed to create dumb drm buffer: Cannot allocate memory Dec 15 22:19:25 kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to map NvKmsKapiMemory 0x5> Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Dec 15 22:19:26 gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit: Invalid argument Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached ``` one may ignore the drmModeAtomicCommit warning, they are always flooding the log (though it may be related issue) The clutter warning then flood the log forever till reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1999830/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999830] Re: external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR*
*** This bug is a duplicate of bug 1967707 *** https://bugs.launchpad.net/bugs/1967707 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1999830 Title: external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Bug description: - ubuntu 22.04.1 - 5.15.0-56-generic - mutter 42.5-0ubuntu1 - using gdm3 - nvidia Driver Version: 525.60.11 (nvidia-driver-525) - prime select to on-demand - 1 external display, 1 internal LCD ``` Added device '/dev/dri/card1' (nvidia-drm) using non-atomic mode setting. Added device '/dev/dri/card0' (i915) using atomic mode setting. Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card1' Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card0' Dec 15 22:13:34 gnome-shell[3203]: Boot VGA GPU /dev/dri/card0 selected as primary Dec 15 22:13:35 gnome-shell[3203]: Secondary GPU initialization failed (Failed to create gbm_surface: No such file or directory). Falling back to GPU-less > Dec 15 22:13:35 gnome-shell[3203]: Using public X11 display :1, (using :2 for managed services) Dec 15 22:13:35 gnome-shell[3203]: Using Wayland display name 'wayland-0' ``` 0. open a terminal `journalctl -f` 1. Open the display setting, switch to join displays, choose external display as primary. 2. try to change some settings like scale, position of the screen, refresh rate, etc, then applay 3. repeat above step several times After 2 changes the external screen freeze forever. Internal screen is still responsible. On each `Apply` The journal recorded an kernel error about nvidia_drm and flooded with clutter-frame-clock error. ``` Dec 15 22:18:52 gnome-shell[3203]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Dec 15 22:18:52 gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit: Invalid argument Dec 15 22:19:25 gnome-shell[3203]: Failed to allocate onscreen framebuffer for /dev/dri/card1: Failed to create dumb drm buffer: Cannot allocate memory Dec 15 22:19:25 kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to map NvKmsKapiMemory 0x5> Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Dec 15 22:19:26 gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit: Invalid argument Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached ``` one may ignore the drmModeAtomicCommit warning, they are always flooding the log (though it may be related issue) The clutter warning then flood the log forever till reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1999830/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045632] Re: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed
** Bug watch removed: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6767 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6767 -- 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/2045632 Title: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed Status in gnome-shell package in Ubuntu: Incomplete Bug description: While just using my system, GNOME Shell suddenly disappeared and logs shows: déc. 05 09:02:23 portable-alex gnome-shell[4341]: g_closure_unref: assertion 'closure->ref_count > 0' failed déc. 05 09:02:23 portable-alex gnome-shell[4341]: GNOME Shell crashed with signal 11 déc. 05 09:02:23 portable-alex gnome-shell[4341]: == Stack trace for context 0x55996924e410 == déc. 05 09:02:23 portable-alex kernel: traps: JS Helper[4367] general protection fault ip:7fe24f05d21c sp:7fe2339fec80 error:0 in libmozjs-115.so.115.3.0[7fe24ef18000+b73000] ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Dec 5 09:08:03 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-04 (519 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-16 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045754] Re: [A770] Graphics card driver crash
It looks like kwin didn't crash until after the kernel errors started so
let's make this about the kernel errors.
** Summary changed:
- Graphics card driver crash
+ [A770] Graphics card driver crash
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Summary changed:
- [A770] Graphics card driver crash
+ [Arc A770] Graphics card driver crash
** Tags added: i915
--
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/2045754
Title:
[Arc A770] Graphics card driver crash
Status in linux package in Ubuntu:
New
Bug description:
I was just browsing the web when the bottom half of the display became black,
the cursor froze, and everything started flickering.
I think eventually KDE crashed and some terminal messages were shown.
I Ctrl+alt+f3 to a terminal and shut down from there.
The terminal was glitchy with random artifacts but visible.
After reboot everything is working again for now.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Dec 6 12:03:24 2023
DistUpgraded: 2023-11-06 09:55:34,023 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: This is the first time
GraphicsCard:
Intel Corporation DG2 [Arc A770] [8086:56a0] (rev 08) (prog-if 00 [VGA
controller])
Subsystem: Intel Corporation DG2 [Arc A770] [8086:1020]
InstallationDate: Installed on 2022-10-30 (402 days ago)
InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=bcf965e4-1a60-42fe-8033-214524d1908b ro quiet
cryptdevice=UUID=66cc3c7b-e0bd-4535-b634-d56226dd88f1:luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1
root=/dev/mapper/luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2023-11-06 (30 days ago)
dmi.bios.date: 05/18/2023
dmi.bios.release: 16.18
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1618
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING X670E-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1618:bd05/18/2023:br16.18:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUS:rvrRev1.xx: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.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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/linux/+bug/2045754/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045817] Re: [Intel Corporation Raptor Lake PCH CNVi WiFi] Bluetooth issues in Ubuntu 23.10
** Summary changed: - Bluetooth issues in Ubuntu 23.10 + [Intel Corporation Raptor Lake PCH CNVi WiFi] Bluetooth issues in Ubuntu 23.10 ** Package changed: bluez (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2045817 Title: [Intel Corporation Raptor Lake PCH CNVi WiFi] Bluetooth issues in Ubuntu 23.10 Status in linux package in Ubuntu: New Bug description: similar to Bug #2019152, only in 23.10 with 6.5.0-12 thru 6.5.0-14 generic kernels. ❯ uname -a; lsb_release -a Linux lt-obijon.geneseo.com 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 23.10 Release: 23.10 Codename: mantic 2023-12-06T16:03:58,866437-06:00 Bluetooth: hci0: Hardware error 0x0c 2023-12-06T16:03:58,880481-06:00 Bluetooth: hci0: Retrieving Intel exception info failed (-16) 2023-12-06T16:03:58,984885-06:00 iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. 2023-12-06T16:03:58,985010-06:00 iwlwifi :00:14.3: Start IWL Error Log Dump: 2023-12-06T16:03:58,985014-06:00 iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 2023-12-06T16:03:58,985018-06:00 iwlwifi :00:14.3: Loaded firmware version: 83.e8f84e98.0 so-a0-gf-a0-83.ucode 2023-12-06T16:03:58,985021-06:00 iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL 2023-12-06T16:03:58,985025-06:00 iwlwifi :00:14.3: 0x02F0 | trm_hw_status0 2023-12-06T16:03:58,985027-06:00 iwlwifi :00:14.3: 0x | trm_hw_status1 2023-12-06T16:03:58,985029-06:00 iwlwifi :00:14.3: 0x004DB338 | branchlink2 2023-12-06T16:03:58,985032-06:00 iwlwifi :00:14.3: 0x004D119A | interruptlink1 2023-12-06T16:03:58,985034-06:00 iwlwifi :00:14.3: 0x004D119A | interruptlink2 2023-12-06T16:03:58,985036-06:00 iwlwifi :00:14.3: 0x000157E2 | data1 2023-12-06T16:03:58,985038-06:00 iwlwifi :00:14.3: 0x0010 | data2 2023-12-06T16:03:58,985040-06:00 iwlwifi :00:14.3: 0x | data3 2023-12-06T16:03:58,985042-06:00 iwlwifi :00:14.3: 0xCDC0BA9E | beacon time 2023-12-06T16:03:58,985044-06:00 iwlwifi :00:14.3: 0x7C09EDE4 | tsf low 2023-12-06T16:03:58,985046-06:00 iwlwifi :00:14.3: 0x | tsf hi 2023-12-06T16:03:58,985048-06:00 iwlwifi :00:14.3: 0x | time gp1 2023-12-06T16:03:58,985050-06:00 iwlwifi :00:14.3: 0x7C0B338A | time gp2 2023-12-06T16:03:58,985052-06:00 iwlwifi :00:14.3: 0x0001 | uCode revision type 2023-12-06T16:03:58,985054-06:00 iwlwifi :00:14.3: 0x0053 | uCode version major 2023-12-06T16:03:58,985056-06:00 iwlwifi :00:14.3: 0xE8F84E98 | uCode version minor 2023-12-06T16:03:58,985058-06:00 iwlwifi :00:14.3: 0x0370 | hw version 2023-12-06T16:03:58,985060-06:00 iwlwifi :00:14.3: 0x00480002 | board version 2023-12-06T16:03:58,985062-06:00 iwlwifi :00:14.3: 0x8096FD26 | hcmd 2023-12-06T16:03:58,985064-06:00 iwlwifi :00:14.3: 0x0002 | isr0 2023-12-06T16:03:58,985066-06:00 iwlwifi :00:14.3: 0x | isr1 2023-12-06T16:03:58,985068-06:00 iwlwifi :00:14.3: 0x48F04802 | isr2 2023-12-06T16:03:58,985069-06:00 iwlwifi :00:14.3: 0x00C3000C | isr3 2023-12-06T16:03:58,985071-06:00 iwlwifi :00:14.3: 0x | isr4 2023-12-06T16:03:58,985073-06:00 iwlwifi :00:14.3: 0x00B40103 | last cmd Id 2023-12-06T16:03:58,985075-06:00 iwlwifi :00:14.3: 0x000157E2 | wait_event 2023-12-06T16:03:58,985077-06:00 iwlwifi :00:14.3: 0x | l2p_control 2023-12-06T16:03:58,985079-06:00 iwlwifi :00:14.3: 0x | l2p_duration 2023-12-06T16:03:58,985081-06:00 iwlwifi :00:14.3: 0x | l2p_mhvalid 2023-12-06T16:03:58,985083-06:00 iwlwifi :00:14.3: 0x | l2p_addr_match 2023-12-06T16:03:58,985085-06:00 iwlwifi :00:14.3: 0x0018 | lmpm_pmg_sel 2023-12-06T16:03:58,985087-06:00 iwlwifi :00:14.3: 0x | timestamp 2023-12-06T16:03:58,985089-06:00 iwlwifi :00:14.3: 0xB82C | flow_handler 2023-12-06T16:03:58,985169-06:00 iwlwifi :00:14.3: Start IWL Error Log Dump: 2023-12-06T16:03:58,985170-06:00 iwlwifi :00:14.3: Transport status: 0x004A, valid: 7 2023-12-06T16:03:58,985173-06:00 iwlwifi :00:14.3: 0x2010190E | ADVANCED_SYSASSERT 2023-12-06T16:03:58,985176-06:00 iwlwifi :00:14.3: 0x | umac branchlink1 2023-12-06T16:03:58,985178-06:00 iwlwifi :00:14.3: 0x80471ABC | umac branchlink2 2023-12-06T16:03:58,985179-06:00 iwlwifi :00:14.3: 0xC008185C | umac interruptlink1 2023-12-06T16:03:58,985181-06:00 iwlwifi :00:14.3: 0x | umac interruptlink2 2023-12-06T16:03:58,985183-06:00 iwlwifi :00:14.3: 0x0102171C | umac data1 2023-12-06T16:03:58,985185-06:00 iwlwifi
[Desktop-packages] [Bug 2045772] Re: Gnome session freezes a few seconds after starting Meet on Chrome under Wayland
Thanks for the bug report. Since your graphics packages are from an unsupported source "LP-PPA- ernstp-mesarc", we cannot handle bug reports about them here. Please remove that PPA from the system, reboot and then report new bugs for any problems you find. ** Package changed: gnome-shell (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/2045772 Title: Gnome session freezes a few seconds after starting Meet on Chrome under Wayland Status in Ubuntu: Invalid Bug description: Since updating to Ubuntu 23.10, every time I start a Google Meet meeting, with the webcam on, in Chrome under Wayland after a few second of working fine the computer freezes and the screen starts flashing every couple of seconds. I can't do anything else but force restart the computer. This problem only happens in Chrome (not Firefox) under Wayland (it works fine on X11). I understand this may be a bug of Chrome. But the desktop shouldn't have an unrecoverable freeze even if an application crashes. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Dec 6 12:03:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-02 (672 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-29 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2045772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045753] Re: Ubuntu stuck on the boot screen
Thanks for the bug report.
Since you have both an unsupported Nvidia driver and unsupported kernel
installed, I'm going to close this bug.
Please uninstall the Nvidia driver and revert to an Ubuntu-provided
kernel, then reboot and reproduce the problem without 'nomodeset'. Once
you have done that, please reboot again with 'nomodeset' and run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file to a new bug.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
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/2045753
Title:
Ubuntu stuck on the boot screen
Status in Ubuntu:
Invalid
Bug description:
I'm using nomodeset option as a workaround, but I'd prefer a permanent
solution.
I have no idea what I'm doing, so if I'm not specific enough, just ask.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
Uname: Linux 6.5.0-060500-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 6 11:42:55 2023
DistUpgraded: 2023-10-18 10:12:58,820 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
bbswitch/0.8, 6.5.0-060500-generic, x86_64: installed
bbswitch/0.8, 6.5.0-14-generic, x86_64: installed
nvidia/545.29.06, 6.5.0-060500-generic, x86_64: installed
nvidia/545.29.06, 6.5.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02)
(prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620]
[103c:8537]
InstallationDate: Installed on 2020-05-20 (1295 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=pl_PL.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-060500-generic
root=UUID=d81f0b8d-3e0f-4039-a46f-5c1c780cac2c ro quiet splash vt.handoff=7
nomodeset
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
UpgradeStatus: Upgraded to mantic on 2023-10-18 (49 days ago)
dmi.bios.date: 04/27/2020
dmi.bios.release: 11.1
dmi.bios.vendor: HP
dmi.bios.version: R71 Ver. 01.11.01
dmi.board.name: 8537
dmi.board.vendor: HP
dmi.board.version: KBC Version 51.2A.00
dmi.chassis.asset.tag: 5CD0097RK4
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 81.42
dmi.modalias:
dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:br11.1:efr81.42:svnHP:pnHPProBook440G6:pvr:rvnHP:rn8537:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr:sku5PQ09EA#AKD:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 440 G6
dmi.product.sku: 5PQ09EA#AKD
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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/+bug/2045753/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows
Please open a new bug about that because this one is closed. -- 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/1799679 Title: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows Status in Mutter: Fix Released Status in metacity package in Ubuntu: Invalid Status in mutter package in Ubuntu: Opinion Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-410 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-470 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-510 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-515 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Bug description: Nvidia driver causes Xorg to use 100% CPU and shows high lag and stutter... but only when dragging glxgears/glxheads, or any window over them. Other apps do not exhibit the problem. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Wed Oct 24 19:11:15 2018 InstallationDate: Installed on 2018-05-26 (151 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1799679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043538] Re: gnome-shell takes too much ram
Great! Are you referring to indicator-multiload or some other extension? -- 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/2043538 Title: gnome-shell takes too much ram Status in gnome-shell package in Ubuntu: Incomplete Bug description: I had no memory problems with Ubuntu 20.04. After upgrading to Ubuntu 22.04, my 16GB laptop suffered from lack of memory. I upgraded to 48GB (!), and the memory still continues to fill. After a few days, with no program started, 12GB is taken. Gnome-shell alone is taking 17.4% of my 48GB. I guess it is suffering from a memory leak. Description:Ubuntu 22.04.3 LTS gnome-shell: Installé : 42.9-0ubuntu2 Candidat : 42.9-0ubuntu2 Table de version : *** 42.9-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 15 07:04:21 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-31 (75 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu5 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/2043538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045820] Re: firefox snap .desktop missing StartupWMClass
screenshot 2, chatgpt suggestion which contained the fix ** Attachment added: "firefox_bug_2.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+attachment/5726921/+files/firefox_bug_2.png ** Description changed: - I have the mozilla stable version installed using the mozilla binary - method, and snap for the beta channel. The icon is broken, both in the - menu entry and in the panel. That is, there is no icon in menu, and the - generic cog icon in the panel. + this is repost from https://forum.snapcraft.io/t/snap-icons-is-the- + firefox-desktop-file-missing-startupwmclass/37400 + + + I have the mozilla stable version installed using the mozilla binary method, and snap for the beta channel. The icon is broken, both in the menu entry and in the panel. That is, there is no icon in menu, and the generic cog icon in the panel. This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04. That is, I can reproduce this every time. I did snap remove firefox to uninstall, but this file /home/tim/.local/share/applications/firefox_firefox.desktop remains. So I remove it manually, and reinstall. The desktop file for this is now: /var/lib/snapd/desktop/applications/firefox_firefox.desktop It is called Firefox Web Browser in the gnome launcher, and it has an icon. But after launching, it still uses the generic cog icon in the panel. The context menu from this icon has no actions, except to Quit. If I create a second window, both are associated with this icon, which is good. In the Gnome launcher, if you search for an app and if that app is running, the Gnome launcher indicates it with a dot. However, while this works for the mozilla binary, the icon of Firefox Web Browser does not show a dot, even though I have two windows from it open. image - image Fix? From chatgpt help, I see this: image - Add this this line to the .destkop file, near the top, fixed it: StartupWMClass=firefox-beta -- 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/2045820 Title: firefox snap .desktop missing StartupWMClass Status in firefox package in Ubuntu: New Bug description: this is repost from https://forum.snapcraft.io/t/snap-icons-is-the- firefox-desktop-file-missing-startupwmclass/37400 I have the mozilla stable version installed using the mozilla binary method, and snap for the beta channel. The snap icon is broken, both in the menu entry and in the panel. That is, there is no icon in menu, and the generic cog icon in the panel. This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04. That is, I can reproduce this every time. I did snap remove firefox to uninstall, but this file /home/tim/.local/share/applications/firefox_firefox.desktop remains. So I remove it manually, and reinstall. The desktop file for this is now: /var/lib/snapd/desktop/applications/firefox_firefox.desktop It is called Firefox Web Browser in the gnome launcher, and it has an icon. But after launching, it still uses the generic cog icon in the panel. The context menu from this icon has no actions, except to Quit. If I create a second window, both are associated with this icon, which is good. In the Gnome launcher, if you search for an app and if that app is running, the Gnome launcher indicates it with a dot. However, while this works for the mozilla binary, the icon of Firefox Web Browser (installed with snap) does not show a dot, even though I have two windows from it open. image: see attachment firefox_bug_0.png image: see attachment firefox_bug_1.png Fix? From chatgpt help, I see this: image: see attachment firefox_bug_3.png Add this line to the snap .destkop file, near the top, fixed it: StartupWMClass=firefox-beta Therefore my suggestion is that the .desktop file have a channel- dependent StartupWMClass value set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045820] Re: firefox snap .desktop missing StartupWMClass
screen shot of icon problem ** Attachment added: "firefox_bug_0.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+attachment/5726922/+files/firefox_bug_0.png ** Description changed: this is repost from https://forum.snapcraft.io/t/snap-icons-is-the- firefox-desktop-file-missing-startupwmclass/37400 - - I have the mozilla stable version installed using the mozilla binary method, and snap for the beta channel. The icon is broken, both in the menu entry and in the panel. That is, there is no icon in menu, and the generic cog icon in the panel. + I have the mozilla stable version installed using the mozilla binary + method, and snap for the beta channel. The icon is broken, both in the + menu entry and in the panel. That is, there is no icon in menu, and the + generic cog icon in the panel. This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04. That is, I can reproduce this every time. I did snap remove firefox to uninstall, but this file /home/tim/.local/share/applications/firefox_firefox.desktop remains. So I remove it manually, and reinstall. The desktop file for this is now: /var/lib/snapd/desktop/applications/firefox_firefox.desktop It is called Firefox Web Browser in the gnome launcher, and it has an icon. But after launching, it still uses the generic cog icon in the panel. The context menu from this icon has no actions, except to Quit. If I create a second window, both are associated with this icon, which is good. In the Gnome launcher, if you search for an app and if that app is running, the Gnome launcher indicates it with a dot. However, while this works for the mozilla binary, the icon of Firefox Web Browser does not show a dot, even though I have two windows from it open. - image + image: see attachment firefox_bug_0.png - image + image: see attachment firefox_bug_1.png Fix? From chatgpt help, I see this: - image + image: see attachment firefox_bug_3.png Add this this line to the .destkop file, near the top, fixed it: StartupWMClass=firefox-beta ** Description changed: this is repost from https://forum.snapcraft.io/t/snap-icons-is-the- firefox-desktop-file-missing-startupwmclass/37400 I have the mozilla stable version installed using the mozilla binary - method, and snap for the beta channel. The icon is broken, both in the - menu entry and in the panel. That is, there is no icon in menu, and the - generic cog icon in the panel. + method, and snap for the beta channel. The snap icon is broken, both in + the menu entry and in the panel. That is, there is no icon in menu, and + the generic cog icon in the panel. This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04. That is, I can reproduce this every time. I did snap remove firefox to uninstall, but this file /home/tim/.local/share/applications/firefox_firefox.desktop remains. So I remove it manually, and reinstall. The desktop file for this is now: /var/lib/snapd/desktop/applications/firefox_firefox.desktop It is called Firefox Web Browser in the gnome launcher, and it has an icon. But after launching, it still uses the generic cog icon in the panel. The context menu from this icon has no actions, except to Quit. If I create a second window, both are associated with this icon, which is good. In the Gnome launcher, if you search for an app and if that app is running, the Gnome launcher indicates it with a dot. However, while this works for the mozilla binary, the icon of Firefox Web Browser does not show a dot, even though I have two windows from it open. image: see attachment firefox_bug_0.png image: see attachment firefox_bug_1.png Fix? From chatgpt help, I see this: image: see attachment firefox_bug_3.png Add this this line to the .destkop file, near the top, fixed it: StartupWMClass=firefox-beta ** Description changed: this is repost from https://forum.snapcraft.io/t/snap-icons-is-the- firefox-desktop-file-missing-startupwmclass/37400 I have the mozilla stable version installed using the mozilla binary method, and snap for the beta channel. The snap icon is broken, both in the menu entry and in the panel. That is, there is no icon in menu, and the generic cog icon in the panel. This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04. That is, I can reproduce this every time. I did snap remove firefox to uninstall, but this file /home/tim/.local/share/applications/firefox_firefox.desktop remains. So I remove it manually, and reinstall. The desktop file for this is now: /var/lib/snapd/desktop/applications/firefox_firefox.desktop It is called Firefox Web Browser in the gnome launcher, and it has an icon. But after launching, it still uses the generic cog icon in the panel. The context
[Desktop-packages] [Bug 2045820] [NEW] firefox snap .desktop missing StartupWMClass
Public bug reported: this is repost from https://forum.snapcraft.io/t/snap-icons-is-the- firefox-desktop-file-missing-startupwmclass/37400 I have the mozilla stable version installed using the mozilla binary method, and snap for the beta channel. The snap icon is broken, both in the menu entry and in the panel. That is, there is no icon in menu, and the generic cog icon in the panel. This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04. That is, I can reproduce this every time. I did snap remove firefox to uninstall, but this file /home/tim/.local/share/applications/firefox_firefox.desktop remains. So I remove it manually, and reinstall. The desktop file for this is now: /var/lib/snapd/desktop/applications/firefox_firefox.desktop It is called Firefox Web Browser in the gnome launcher, and it has an icon. But after launching, it still uses the generic cog icon in the panel. The context menu from this icon has no actions, except to Quit. If I create a second window, both are associated with this icon, which is good. In the Gnome launcher, if you search for an app and if that app is running, the Gnome launcher indicates it with a dot. However, while this works for the mozilla binary, the icon of Firefox Web Browser (installed with snap) does not show a dot, even though I have two windows from it open. image: see attachment firefox_bug_0.png image: see attachment firefox_bug_1.png Fix? >From chatgpt help, I see this: image: see attachment firefox_bug_3.png Add this line to the snap .destkop file, near the top, fixed it: StartupWMClass=firefox-beta Therefore my suggestion is that the .desktop file have a channel- dependent StartupWMClass value set. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot 1" https://bugs.launchpad.net/bugs/2045820/+attachment/5726920/+files/firefox_bug_1.png -- 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/2045820 Title: firefox snap .desktop missing StartupWMClass Status in firefox package in Ubuntu: New Bug description: this is repost from https://forum.snapcraft.io/t/snap-icons-is-the- firefox-desktop-file-missing-startupwmclass/37400 I have the mozilla stable version installed using the mozilla binary method, and snap for the beta channel. The snap icon is broken, both in the menu entry and in the panel. That is, there is no icon in menu, and the generic cog icon in the panel. This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04. That is, I can reproduce this every time. I did snap remove firefox to uninstall, but this file /home/tim/.local/share/applications/firefox_firefox.desktop remains. So I remove it manually, and reinstall. The desktop file for this is now: /var/lib/snapd/desktop/applications/firefox_firefox.desktop It is called Firefox Web Browser in the gnome launcher, and it has an icon. But after launching, it still uses the generic cog icon in the panel. The context menu from this icon has no actions, except to Quit. If I create a second window, both are associated with this icon, which is good. In the Gnome launcher, if you search for an app and if that app is running, the Gnome launcher indicates it with a dot. However, while this works for the mozilla binary, the icon of Firefox Web Browser (installed with snap) does not show a dot, even though I have two windows from it open. image: see attachment firefox_bug_0.png image: see attachment firefox_bug_1.png Fix? From chatgpt help, I see this: image: see attachment firefox_bug_3.png Add this line to the snap .destkop file, near the top, fixed it: StartupWMClass=firefox-beta Therefore my suggestion is that the .desktop file have a channel- dependent StartupWMClass value set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045817] Re: Bluetooth issues in Ubuntu 23.10
** Package changed: ubuntu => bluez (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2045817 Title: Bluetooth issues in Ubuntu 23.10 Status in bluez package in Ubuntu: New Bug description: similar to Bug #2019152, only in 23.10 with 6.5.0-12 thru 6.5.0-14 generic kernels. ❯ uname -a; lsb_release -a Linux lt-obijon.geneseo.com 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 23.10 Release: 23.10 Codename: mantic 2023-12-06T16:03:58,866437-06:00 Bluetooth: hci0: Hardware error 0x0c 2023-12-06T16:03:58,880481-06:00 Bluetooth: hci0: Retrieving Intel exception info failed (-16) 2023-12-06T16:03:58,984885-06:00 iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. 2023-12-06T16:03:58,985010-06:00 iwlwifi :00:14.3: Start IWL Error Log Dump: 2023-12-06T16:03:58,985014-06:00 iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 2023-12-06T16:03:58,985018-06:00 iwlwifi :00:14.3: Loaded firmware version: 83.e8f84e98.0 so-a0-gf-a0-83.ucode 2023-12-06T16:03:58,985021-06:00 iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL 2023-12-06T16:03:58,985025-06:00 iwlwifi :00:14.3: 0x02F0 | trm_hw_status0 2023-12-06T16:03:58,985027-06:00 iwlwifi :00:14.3: 0x | trm_hw_status1 2023-12-06T16:03:58,985029-06:00 iwlwifi :00:14.3: 0x004DB338 | branchlink2 2023-12-06T16:03:58,985032-06:00 iwlwifi :00:14.3: 0x004D119A | interruptlink1 2023-12-06T16:03:58,985034-06:00 iwlwifi :00:14.3: 0x004D119A | interruptlink2 2023-12-06T16:03:58,985036-06:00 iwlwifi :00:14.3: 0x000157E2 | data1 2023-12-06T16:03:58,985038-06:00 iwlwifi :00:14.3: 0x0010 | data2 2023-12-06T16:03:58,985040-06:00 iwlwifi :00:14.3: 0x | data3 2023-12-06T16:03:58,985042-06:00 iwlwifi :00:14.3: 0xCDC0BA9E | beacon time 2023-12-06T16:03:58,985044-06:00 iwlwifi :00:14.3: 0x7C09EDE4 | tsf low 2023-12-06T16:03:58,985046-06:00 iwlwifi :00:14.3: 0x | tsf hi 2023-12-06T16:03:58,985048-06:00 iwlwifi :00:14.3: 0x | time gp1 2023-12-06T16:03:58,985050-06:00 iwlwifi :00:14.3: 0x7C0B338A | time gp2 2023-12-06T16:03:58,985052-06:00 iwlwifi :00:14.3: 0x0001 | uCode revision type 2023-12-06T16:03:58,985054-06:00 iwlwifi :00:14.3: 0x0053 | uCode version major 2023-12-06T16:03:58,985056-06:00 iwlwifi :00:14.3: 0xE8F84E98 | uCode version minor 2023-12-06T16:03:58,985058-06:00 iwlwifi :00:14.3: 0x0370 | hw version 2023-12-06T16:03:58,985060-06:00 iwlwifi :00:14.3: 0x00480002 | board version 2023-12-06T16:03:58,985062-06:00 iwlwifi :00:14.3: 0x8096FD26 | hcmd 2023-12-06T16:03:58,985064-06:00 iwlwifi :00:14.3: 0x0002 | isr0 2023-12-06T16:03:58,985066-06:00 iwlwifi :00:14.3: 0x | isr1 2023-12-06T16:03:58,985068-06:00 iwlwifi :00:14.3: 0x48F04802 | isr2 2023-12-06T16:03:58,985069-06:00 iwlwifi :00:14.3: 0x00C3000C | isr3 2023-12-06T16:03:58,985071-06:00 iwlwifi :00:14.3: 0x | isr4 2023-12-06T16:03:58,985073-06:00 iwlwifi :00:14.3: 0x00B40103 | last cmd Id 2023-12-06T16:03:58,985075-06:00 iwlwifi :00:14.3: 0x000157E2 | wait_event 2023-12-06T16:03:58,985077-06:00 iwlwifi :00:14.3: 0x | l2p_control 2023-12-06T16:03:58,985079-06:00 iwlwifi :00:14.3: 0x | l2p_duration 2023-12-06T16:03:58,985081-06:00 iwlwifi :00:14.3: 0x | l2p_mhvalid 2023-12-06T16:03:58,985083-06:00 iwlwifi :00:14.3: 0x | l2p_addr_match 2023-12-06T16:03:58,985085-06:00 iwlwifi :00:14.3: 0x0018 | lmpm_pmg_sel 2023-12-06T16:03:58,985087-06:00 iwlwifi :00:14.3: 0x | timestamp 2023-12-06T16:03:58,985089-06:00 iwlwifi :00:14.3: 0xB82C | flow_handler 2023-12-06T16:03:58,985169-06:00 iwlwifi :00:14.3: Start IWL Error Log Dump: 2023-12-06T16:03:58,985170-06:00 iwlwifi :00:14.3: Transport status: 0x004A, valid: 7 2023-12-06T16:03:58,985173-06:00 iwlwifi :00:14.3: 0x2010190E | ADVANCED_SYSASSERT 2023-12-06T16:03:58,985176-06:00 iwlwifi :00:14.3: 0x | umac branchlink1 2023-12-06T16:03:58,985178-06:00 iwlwifi :00:14.3: 0x80471ABC | umac branchlink2 2023-12-06T16:03:58,985179-06:00 iwlwifi :00:14.3: 0xC008185C | umac interruptlink1 2023-12-06T16:03:58,985181-06:00 iwlwifi :00:14.3: 0x | umac interruptlink2 2023-12-06T16:03:58,985183-06:00 iwlwifi :00:14.3: 0x0102171C | umac data1 2023-12-06T16:03:58,985185-06:00 iwlwifi :00:14.3: 0xDEADBEEF | umac data2 2023-12-06T16:03:58,985187-06:00 iwlwifi :00:14.3: 0xDEADBEEF | umac data3 2023-12-06T16:03:58,985189-06:00 iwlwifi :00:14.3: 0x0053 | umac
[Desktop-packages] [Bug 2045817] [NEW] Bluetooth issues in Ubuntu 23.10
You have been subscribed to a public bug: similar to Bug #2019152, only in 23.10 with 6.5.0-12 thru 6.5.0-14 generic kernels. ❯ uname -a; lsb_release -a Linux lt-obijon.geneseo.com 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 23.10 Release: 23.10 Codename: mantic 2023-12-06T16:03:58,866437-06:00 Bluetooth: hci0: Hardware error 0x0c 2023-12-06T16:03:58,880481-06:00 Bluetooth: hci0: Retrieving Intel exception info failed (-16) 2023-12-06T16:03:58,984885-06:00 iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. 2023-12-06T16:03:58,985010-06:00 iwlwifi :00:14.3: Start IWL Error Log Dump: 2023-12-06T16:03:58,985014-06:00 iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 2023-12-06T16:03:58,985018-06:00 iwlwifi :00:14.3: Loaded firmware version: 83.e8f84e98.0 so-a0-gf-a0-83.ucode 2023-12-06T16:03:58,985021-06:00 iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL 2023-12-06T16:03:58,985025-06:00 iwlwifi :00:14.3: 0x02F0 | trm_hw_status0 2023-12-06T16:03:58,985027-06:00 iwlwifi :00:14.3: 0x | trm_hw_status1 2023-12-06T16:03:58,985029-06:00 iwlwifi :00:14.3: 0x004DB338 | branchlink2 2023-12-06T16:03:58,985032-06:00 iwlwifi :00:14.3: 0x004D119A | interruptlink1 2023-12-06T16:03:58,985034-06:00 iwlwifi :00:14.3: 0x004D119A | interruptlink2 2023-12-06T16:03:58,985036-06:00 iwlwifi :00:14.3: 0x000157E2 | data1 2023-12-06T16:03:58,985038-06:00 iwlwifi :00:14.3: 0x0010 | data2 2023-12-06T16:03:58,985040-06:00 iwlwifi :00:14.3: 0x | data3 2023-12-06T16:03:58,985042-06:00 iwlwifi :00:14.3: 0xCDC0BA9E | beacon time 2023-12-06T16:03:58,985044-06:00 iwlwifi :00:14.3: 0x7C09EDE4 | tsf low 2023-12-06T16:03:58,985046-06:00 iwlwifi :00:14.3: 0x | tsf hi 2023-12-06T16:03:58,985048-06:00 iwlwifi :00:14.3: 0x | time gp1 2023-12-06T16:03:58,985050-06:00 iwlwifi :00:14.3: 0x7C0B338A | time gp2 2023-12-06T16:03:58,985052-06:00 iwlwifi :00:14.3: 0x0001 | uCode revision type 2023-12-06T16:03:58,985054-06:00 iwlwifi :00:14.3: 0x0053 | uCode version major 2023-12-06T16:03:58,985056-06:00 iwlwifi :00:14.3: 0xE8F84E98 | uCode version minor 2023-12-06T16:03:58,985058-06:00 iwlwifi :00:14.3: 0x0370 | hw version 2023-12-06T16:03:58,985060-06:00 iwlwifi :00:14.3: 0x00480002 | board version 2023-12-06T16:03:58,985062-06:00 iwlwifi :00:14.3: 0x8096FD26 | hcmd 2023-12-06T16:03:58,985064-06:00 iwlwifi :00:14.3: 0x0002 | isr0 2023-12-06T16:03:58,985066-06:00 iwlwifi :00:14.3: 0x | isr1 2023-12-06T16:03:58,985068-06:00 iwlwifi :00:14.3: 0x48F04802 | isr2 2023-12-06T16:03:58,985069-06:00 iwlwifi :00:14.3: 0x00C3000C | isr3 2023-12-06T16:03:58,985071-06:00 iwlwifi :00:14.3: 0x | isr4 2023-12-06T16:03:58,985073-06:00 iwlwifi :00:14.3: 0x00B40103 | last cmd Id 2023-12-06T16:03:58,985075-06:00 iwlwifi :00:14.3: 0x000157E2 | wait_event 2023-12-06T16:03:58,985077-06:00 iwlwifi :00:14.3: 0x | l2p_control 2023-12-06T16:03:58,985079-06:00 iwlwifi :00:14.3: 0x | l2p_duration 2023-12-06T16:03:58,985081-06:00 iwlwifi :00:14.3: 0x | l2p_mhvalid 2023-12-06T16:03:58,985083-06:00 iwlwifi :00:14.3: 0x | l2p_addr_match 2023-12-06T16:03:58,985085-06:00 iwlwifi :00:14.3: 0x0018 | lmpm_pmg_sel 2023-12-06T16:03:58,985087-06:00 iwlwifi :00:14.3: 0x | timestamp 2023-12-06T16:03:58,985089-06:00 iwlwifi :00:14.3: 0xB82C | flow_handler 2023-12-06T16:03:58,985169-06:00 iwlwifi :00:14.3: Start IWL Error Log Dump: 2023-12-06T16:03:58,985170-06:00 iwlwifi :00:14.3: Transport status: 0x004A, valid: 7 2023-12-06T16:03:58,985173-06:00 iwlwifi :00:14.3: 0x2010190E | ADVANCED_SYSASSERT 2023-12-06T16:03:58,985176-06:00 iwlwifi :00:14.3: 0x | umac branchlink1 2023-12-06T16:03:58,985178-06:00 iwlwifi :00:14.3: 0x80471ABC | umac branchlink2 2023-12-06T16:03:58,985179-06:00 iwlwifi :00:14.3: 0xC008185C | umac interruptlink1 2023-12-06T16:03:58,985181-06:00 iwlwifi :00:14.3: 0x | umac interruptlink2 2023-12-06T16:03:58,985183-06:00 iwlwifi :00:14.3: 0x0102171C | umac data1 2023-12-06T16:03:58,985185-06:00 iwlwifi :00:14.3: 0xDEADBEEF | umac data2 2023-12-06T16:03:58,985187-06:00 iwlwifi :00:14.3: 0xDEADBEEF | umac data3 2023-12-06T16:03:58,985189-06:00 iwlwifi :00:14.3: 0x0053 | umac major 2023-12-06T16:03:58,985191-06:00 iwlwifi :00:14.3: 0xE8F84E98 | umac minor 2023-12-06T16:03:58,985193-06:00 iwlwifi :00:14.3: 0x7C0B3384 | frame pointer 2023-12-06T16:03:58,985195-06:00 iwlwifi :00:14.3: 0xC0886BE0 | stack pointer 2023-12-06T16:03:58,985197-06:00 iwlwifi :00:14.3: 0x00ED019C | last host cmd 2023-12-06T16:03:58,985199-06:00 iwlwifi :00:14.3: 0x |
[Desktop-packages] [Bug 2025526] Re: Printer is not available in chromium snap
@wallento and @jose+ubu1, could you please run the command ps aux | grep cups-proxyd and post the output here and also could you attach the files /var/snap/cups/current/var/log/cups-proxyd_log /var/snap/cups/current/var/log/error_log /var/log/cups/error_log Attach the files one by one, in separate comments, and do not compress them, this way I will be able to easily read right out of the browser. -- 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/2025526 Title: Printer is not available in chromium snap Status in chromium-browser package in Ubuntu: Confirmed Status in cups package in Ubuntu: Confirmed Bug description: My printer is not available in chromium. I had the same problem in firefox but fixed it with the following command: sudo snap connect firefox:cups-control However this did not work with the chromium snap. I got the following error: snap "chromium" has no plug named "cups-control" My printer is a network printer and is automatically detected by my Kubuntu install. It works out of the box with all native apps and flatpaks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025526/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows
I am using 545.23.08 and this problem is still affecting me. It's surreal to buy a graphics card for over a thousand dollars and have the drivers be unable to move a window without lag -- 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/1799679 Title: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows Status in Mutter: Fix Released Status in metacity package in Ubuntu: Invalid Status in mutter package in Ubuntu: Opinion Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-410 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-470 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-510 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-515 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Bug description: Nvidia driver causes Xorg to use 100% CPU and shows high lag and stutter... but only when dragging glxgears/glxheads, or any window over them. Other apps do not exhibit the problem. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Wed Oct 24 19:11:15 2018 InstallationDate: Installed on 2018-05-26 (151 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1799679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written
** Description changed: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: - 1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04 + 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable - 4. Open any website containing images in Firefox / Chromium + 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Triaged Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are
Re: [Desktop-packages] [Bug 2023322] Re: GTK internal browser does not render with Nvidia drivers
I just recently upgraded to Ubuntu 23.10 and the issues are gone. I was able to create my google account just fine under 23.10 On Tue, Dec 5, 2023 at 7:50 PM Jeremy Bícha <2023...@bugs.launchpad.net> wrote: > That bug was filed before we fixed Jammy on 2023-11-20 > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2027737). > https://bugs.launchpad.net/bugs/2023322 > > Title: > GTK internal browser does not render with Nvidia drivers > > Status in Webkit: > Confirmed > 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
[Desktop-packages] [Bug 2045043] Re: Update fonts-noto-color-emoji for Unicode 15.1
This bug was fixed in the package fonts-noto-color-emoji - 2.042-1 --- fonts-noto-color-emoji (2.042-1) unstable; urgency=medium * New upstream release - Update flag for Martinique -- Jeremy Bícha Thu, 30 Nov 2023 11:34:59 -0500 ** Changed in: fonts-noto-color-emoji (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/2045043 Title: Update fonts-noto-color-emoji for Unicode 15.1 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Jammy: In Progress Status in fonts-noto-color-emoji source package in Mantic: In Progress Bug description: [Impact] Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the Show new link to see the new emoji. Click the changed link to see other changes that were made in this release. https://emojipedia.org/google/15.1/ Or see https://blog.emojipedia.org/googles-emoji-15-1-support-in-noto- color-emoji/ More background at https://jenniferdaniel.substack.com/p/breaking-the- cycle [Test Plan] The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont [Where problems could occur] Sometimes there is an issue with the display of a particular font after the font has been updated. See LP: #2034986 for instance. Perhaps this is a bug with font caching. In this case, it is not believed that the color emoji font is used by GNOME Shell itself so a simple restart of any apps that use emoji should be enough to fix that issue. This could technically be a User Interface Freeze change, but the new and changed emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. [Other] I do not intend to prepare this update for Ubuntu 23.04. People are encouraged to upgrade to 23.10 for UI improvements and 23.04 will reach end of life around January. This update does not require nototools to be updated. This update is a prerequisite for a GNOME Characters update for Ubuntu 23.10. See LP: #2045056 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/2045043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043538] Re: gnome-shell takes too much ram
Disabling the extension that monitors the ram makes indeed the memory leak disappear ! Thank you for your help. -- 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/2043538 Title: gnome-shell takes too much ram Status in gnome-shell package in Ubuntu: Incomplete Bug description: I had no memory problems with Ubuntu 20.04. After upgrading to Ubuntu 22.04, my 16GB laptop suffered from lack of memory. I upgraded to 48GB (!), and the memory still continues to fill. After a few days, with no program started, 12GB is taken. Gnome-shell alone is taking 17.4% of my 48GB. I guess it is suffering from a memory leak. Description:Ubuntu 22.04.3 LTS gnome-shell: Installé : 42.9-0ubuntu2 Candidat : 42.9-0ubuntu2 Table de version : *** 42.9-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 15 07:04:21 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-31 (75 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu5 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/2043538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759591] Re: [printer] segfault when printing a test page
The issue seems to have been resolved in newer versions ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1759591 Title: [printer] segfault when printing a test page Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Bug description: was setting the printer ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu4 Uname: Linux 4.16.0-041600rc7-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 AssertionMessage: corrupted size vs. prev_size CurrentDesktop: GNOME Date: Wed Mar 28 16:23:37 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-02-06 (49 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcCmdline: gnome-control-center printers Signal: 6 SourcePackage: gnome-control-center StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fa0d6dcdb9a "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7fa0d6dcbc9d "corrupted size vs. prev_size") at malloc.c:5350 _int_realloc (av=av@entry=0x7fa0d7002c40 , oldp=oldp@entry=0x55f7d56c5400, oldsize=oldsize@entry=912, nb=nb@entry=928) at malloc.c:4564 __GI___libc_realloc (oldmem=0x55f7d56c5410, bytes=912) at malloc.c:3230 g_realloc () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center assert failure: corrupted size vs. prev_size UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1759591/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045043] Re: Update fonts-noto-color-emoji for Unicode 15.1
** Description changed: [Impact] Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the Show new link to see the new emoji. Click the changed link to see other changes that were made in this release. https://emojipedia.org/google/15.1/ Or see https://blog.emojipedia.org/googles-emoji-15-1-support-in-noto- color-emoji/ + + More background at https://jenniferdaniel.substack.com/p/breaking-the- + cycle [Test Plan] The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont [Where problems could occur] Sometimes there is an issue with the display of a particular font after the font has been updated. See LP: #2034986 for instance. Perhaps this is a bug with font caching. In this case, it is not believed that the color emoji font is used by GNOME Shell itself so a simple restart of any apps that use emoji should be enough to fix that issue. This could technically be a User Interface Freeze change, but the new and changed emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. [Other] I do not intend to prepare this update for Ubuntu 23.04. People are encouraged to upgrade to 23.10 for UI improvements and 23.04 will reach end of life around January. This update does not require nototools to be updated. This update is a prerequisite for a GNOME Characters update for Ubuntu 23.10. See LP: #2045056 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/2045043 Title: Update fonts-noto-color-emoji for Unicode 15.1 Status in fonts-noto-color-emoji package in Ubuntu: Fix Committed Status in fonts-noto-color-emoji source package in Jammy: In Progress Status in fonts-noto-color-emoji source package in Mantic: In Progress Bug description: [Impact] Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the Show new link to see the new emoji. Click the changed link to see other changes that were made in this release. https://emojipedia.org/google/15.1/ Or see https://blog.emojipedia.org/googles-emoji-15-1-support-in-noto- color-emoji/ More background at https://jenniferdaniel.substack.com/p/breaking-the- cycle [Test Plan] The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont [Where problems could occur] Sometimes there is an issue with the display of a particular font after the font has been updated. See LP: #2034986 for instance. Perhaps this is a bug with font caching. In this case, it is not believed that the color emoji font is used by GNOME Shell itself so a simple restart of any apps that use emoji should be enough to fix that issue. This could technically be a User Interface Freeze change, but the new and changed emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. [Other] I do not intend to prepare this update for Ubuntu 23.04. People are encouraged to upgrade to 23.10 for UI improvements and 23.04 will reach end of life around January. This update does not require nototools to be updated. This update is a prerequisite for a GNOME Characters update for Ubuntu 23.10. See LP: #2045056 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/2045043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2024680] Re: Dell XPS 9730 no sound, I have tried the 22.04 lts same issue
Had encountered the same issue on 22.04. Applying this patch https://github.com/torvalds/linux/commit/43e354dada62c0425db900f327a6e11babefcf5c seems to work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2024680 Title: Dell XPS 9730 no sound, I have tried the 22.04 lts same issue Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've tried various fixes without success, I did manage to get the NVIDA HDMI in the sound options but I've never had the inbuilt Intel Media Hardware working for sound. 22.04 LTS had the same issue and I've upgraded to the new version 23.04 which looks good. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pulseaudio 1:16.1+dfsg1-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 2245 F wireplumber /dev/snd/seq:daniel 2241 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 22 17:30:27 2023 InstallationDate: Installed on 2023-06-16 (5 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2023 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 067X4F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd03/23/2023:br1.2:efr1.1:svnDellInc.:pnXPS179730:pvr:rvnDellInc.:rn067X4F:rvrA00:cvnDellInc.:ct10:cvr:sku0BDB: dmi.product.family: XPS dmi.product.name: XPS 17 9730 dmi.product.sku: 0BDB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2024680/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2031252] Re: Playing video with audio freezes
This is still happening for me under Ubuntu 23.10. -- 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/2031252 Title: Playing video with audio freezes Status in alsa-driver package in Ubuntu: New Bug description: I'm not sure when this started, but any video I play with audio is not working properly - it severely lags and/or freezes. This happens in Youtube on both Chrome and Firefox, and in the regular GNOME media player. Audio by itself works fine, and video with audio muted works fine. I tried restarting and downgrading the kernel, to no avail. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ari2679 F pipewire ari2700 F wireplumber /dev/snd/seq:ari2679 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 13 17:22:56 2023 InstallationDate: Installed on 2022-06-07 (432 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to lunar on 2023-07-20 (23 days ago) dmi.bios.date: 06/12/2023 dmi.bios.release: 1.61 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET85W (1.61 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrN32ET85W(1.61):bd06/12/2023:br1.61:efr1.34:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2031252/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045772] [NEW] Gnome session freezes a few seconds after starting Meet on Chrome under Wayland
Public bug reported: Since updating to Ubuntu 23.10, every time I start a Google Meet meeting, with the webcam on, in Chrome under Wayland after a few second of working fine the computer freezes and the screen starts flashing every couple of seconds. I can't do anything else but force restart the computer. This problem only happens in Chrome (not Firefox) under Wayland (it works fine on X11). I understand this may be a bug of Chrome. But the desktop shouldn't have an unrecoverable freeze even if an application crashes. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Dec 6 12:03:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-02 (672 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-29 (68 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic third-party-packages -- 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/2045772 Title: Gnome session freezes a few seconds after starting Meet on Chrome under Wayland Status in gnome-shell package in Ubuntu: New Bug description: Since updating to Ubuntu 23.10, every time I start a Google Meet meeting, with the webcam on, in Chrome under Wayland after a few second of working fine the computer freezes and the screen starts flashing every couple of seconds. I can't do anything else but force restart the computer. This problem only happens in Chrome (not Firefox) under Wayland (it works fine on X11). I understand this may be a bug of Chrome. But the desktop shouldn't have an unrecoverable freeze even if an application crashes. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Dec 6 12:03:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-02 (672 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-29 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969602] Re: gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing
This was fixed in Ubuntu 23.04, but then broke again with 23.10. The workaround that worked for me in 22.04 was to install https://extensions.gnome.org/extension/4673/alt-tab-move-mouse/, but that's not available for GNOME 45. Supposedly this update to mutter fixes the issue but I haven't tested it: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3258 -- 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/1969602 Title: gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have set gnome to "focus on hover", i.e. focus follows mouse. If I alt-tab to bring a window to the front but the mouse is over another window, then the hovered-over window will reclaim focus and the window I raised will typically get covered up again. In previous gnome versions, if I explicitly focussed a window via keyboard shortcuts, it remained focussed and I think this is the preferred behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:35:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-17 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 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/1969602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003042] Re: gnome-shell crashed with SIGSEGV in meta_kms_connector_read_state(drm_connector=NULL) from meta_kms_connector_update_state()
** Changed in: mutter (Fedora) Status: Unknown => Won't Fix -- 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/2003042 Title: gnome-shell crashed with SIGSEGV in meta_kms_connector_read_state(drm_connector=NULL) from meta_kms_connector_update_state() Status in mutter package in Ubuntu: Fix Released Status in mutter package in Fedora: Won't Fix Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 43.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/8158e20e6ac0a16fd196b1b06a27678cf87f2029 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003042]
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed. -- 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/2003042 Title: gnome-shell crashed with SIGSEGV in meta_kms_connector_read_state(drm_connector=NULL) from meta_kms_connector_update_state() Status in mutter package in Ubuntu: Fix Released Status in mutter package in Fedora: Won't Fix Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 43.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/8158e20e6ac0a16fd196b1b06a27678cf87f2029 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045753] Re: Ubuntu stuck on the boot screen
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709
--
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/2045753
Title:
Ubuntu stuck on the boot screen
Status in xorg package in Ubuntu:
New
Bug description:
I'm using nomodeset option as a workaround, but I'd prefer a permanent
solution.
I have no idea what I'm doing, so if I'm not specific enough, just ask.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
Uname: Linux 6.5.0-060500-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 6 11:42:55 2023
DistUpgraded: 2023-10-18 10:12:58,820 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
bbswitch/0.8, 6.5.0-060500-generic, x86_64: installed
bbswitch/0.8, 6.5.0-14-generic, x86_64: installed
nvidia/545.29.06, 6.5.0-060500-generic, x86_64: installed
nvidia/545.29.06, 6.5.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02)
(prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620]
[103c:8537]
InstallationDate: Installed on 2020-05-20 (1295 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=pl_PL.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-060500-generic
root=UUID=d81f0b8d-3e0f-4039-a46f-5c1c780cac2c ro quiet splash vt.handoff=7
nomodeset
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
UpgradeStatus: Upgraded to mantic on 2023-10-18 (49 days ago)
dmi.bios.date: 04/27/2020
dmi.bios.release: 11.1
dmi.bios.vendor: HP
dmi.bios.version: R71 Ver. 01.11.01
dmi.board.name: 8537
dmi.board.vendor: HP
dmi.board.version: KBC Version 51.2A.00
dmi.chassis.asset.tag: 5CD0097RK4
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 81.42
dmi.modalias:
dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:br11.1:efr81.42:svnHP:pnHPProBook440G6:pvr:rvnHP:rn8537:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr:sku5PQ09EA#AKD:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 440 G6
dmi.product.sku: 5PQ09EA#AKD
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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/xorg/+bug/2045753/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045754] [NEW] Graphics card driver crash
Public bug reported:
I was just browsing the web when the bottom half of the display became black,
the cursor froze, and everything started flickering.
I think eventually KDE crashed and some terminal messages were shown.
I Ctrl+alt+f3 to a terminal and shut down from there.
The terminal was glitchy with random artifacts but visible.
After reboot everything is working again for now.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Dec 6 12:03:24 2023
DistUpgraded: 2023-11-06 09:55:34,023 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: This is the first time
GraphicsCard:
Intel Corporation DG2 [Arc A770] [8086:56a0] (rev 08) (prog-if 00 [VGA
controller])
Subsystem: Intel Corporation DG2 [Arc A770] [8086:1020]
InstallationDate: Installed on 2022-10-30 (402 days ago)
InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=bcf965e4-1a60-42fe-8033-214524d1908b ro quiet
cryptdevice=UUID=66cc3c7b-e0bd-4535-b634-d56226dd88f1:luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1
root=/dev/mapper/luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2023-11-06 (30 days ago)
dmi.bios.date: 05/18/2023
dmi.bios.release: 16.18
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1618
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING X670E-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1618:bd05/18/2023:br16.18:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUS:rvrRev1.xx: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.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug freeze kubuntu mantic ubuntu wayland-session
** Attachment added: "dmesg log of the crash"
https://bugs.launchpad.net/bugs/2045754/+attachment/5726688/+files/dmesg-gpu-txt
--
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/2045754
Title:
Graphics card driver crash
Status in xorg package in Ubuntu:
New
Bug description:
I was just browsing the web when the bottom half of the display became black,
the cursor froze, and everything started flickering.
I think eventually KDE crashed and some terminal messages were shown.
I Ctrl+alt+f3 to a terminal and shut down from there.
The terminal was glitchy with random artifacts but visible.
After reboot everything is working again for now.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Dec 6 12:03:24 2023
DistUpgraded: 2023-11-06 09:55:34,023 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: This is the first time
GraphicsCard:
Intel Corporation DG2 [Arc A770] [8086:56a0] (rev 08) (prog-if 00 [VGA
controller])
Subsystem: Intel Corporation DG2 [Arc A770] [8086:1020]
InstallationDate: Installed on 2022-10-30 (402 days ago)
InstallationMedia:
[Desktop-packages] [Bug 2045753] [NEW] Ubuntu stuck on the boot screen
Public bug reported:
I'm using nomodeset option as a workaround, but I'd prefer a permanent
solution.
I have no idea what I'm doing, so if I'm not specific enough, just ask.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
Uname: Linux 6.5.0-060500-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 6 11:42:55 2023
DistUpgraded: 2023-10-18 10:12:58,820 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
bbswitch/0.8, 6.5.0-060500-generic, x86_64: installed
bbswitch/0.8, 6.5.0-14-generic, x86_64: installed
nvidia/545.29.06, 6.5.0-060500-generic, x86_64: installed
nvidia/545.29.06, 6.5.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02)
(prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620]
[103c:8537]
InstallationDate: Installed on 2020-05-20 (1295 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=pl_PL.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-060500-generic
root=UUID=d81f0b8d-3e0f-4039-a46f-5c1c780cac2c ro quiet splash vt.handoff=7
nomodeset
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
UpgradeStatus: Upgraded to mantic on 2023-10-18 (49 days ago)
dmi.bios.date: 04/27/2020
dmi.bios.release: 11.1
dmi.bios.vendor: HP
dmi.bios.version: R71 Ver. 01.11.01
dmi.board.name: 8537
dmi.board.vendor: HP
dmi.board.version: KBC Version 51.2A.00
dmi.chassis.asset.tag: 5CD0097RK4
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 81.42
dmi.modalias:
dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:br11.1:efr81.42:svnHP:pnHPProBook440G6:pvr:rvnHP:rn8537:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr:sku5PQ09EA#AKD:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 440 G6
dmi.product.sku: 5PQ09EA#AKD
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic 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/2045753
Title:
Ubuntu stuck on the boot screen
Status in xorg package in Ubuntu:
New
Bug description:
I'm using nomodeset option as a workaround, but I'd prefer a permanent
solution.
I have no idea what I'm doing, so if I'm not specific enough, just ask.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
Uname: Linux 6.5.0-060500-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 6 11:42:55 2023
DistUpgraded: 2023-10-18 10:12:58,820 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
bbswitch/0.8, 6.5.0-060500-generic, x86_64: installed
bbswitch/0.8, 6.5.0-14-generic, x86_64: installed
nvidia/545.29.06, 6.5.0-060500-generic, x86_64: installed
nvidia/545.29.06, 6.5.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02)
(prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620]
[103c:8537]
InstallationDate: Installed on 2020-05-20 (1295 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=pl_PL.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-060500-generic
root=UUID=d81f0b8d-3e0f-4039-a46f-5c1c780cac2c ro quiet splash vt.handoff=7
nomodeset
RebootRequiredPkgs: Error: path
[Desktop-packages] [Bug 1878617] Re: Apple pages file type should be added to MIME types
Fantastic! I can confirm that this is fixed on Ubuntu 23.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1878617 Title: Apple pages file type should be added to MIME types Status in shared-mime-info: Fix Released Status in mime-support package in Ubuntu: Invalid Status in shared-mime-info package in Ubuntu: Fix Released Bug description: LibreOffice can open .pages files (from Apple pages). However, the mime type for these files is incorrectly just application/zip: $ file --mime-type example.pages example.pages: application/zip Instead, it should be application/vnd.apple.pages . This would allow the user to associate LibreOffice Writer with these types of files, and use it to open this file. (LibreOffice Writer can open .pages files) Apple Keynote files should have this MIME type: application/vnd.apple.keynote Apple Numbers files should have this MIME type: application/vnd.apple.numbers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mime-support 3.64ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 14:46:40 2020 InstallationDate: Installed on 2018-11-11 (550 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: mime-support UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1878617/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045744] Re: Add profile to open Textedit links in files generated by Lilypond
I'm not sure if the relevant change in the config file is included or
not, so I'll add it here as well:
# 'Show Containing Folder' (LP: #1022962)
/usr/bin/nautilus Cx -> sanitized_helper, # Gnome
/usr/bin/pcmanfm Cx -> sanitized_helper, # LXDE
/usr/bin/krusader Cx -> sanitized_helper, # KDE
/usr/bin/thunar Cx -> sanitized_helper, # XFCE
+ # For Textedit links
+ /usr/bin/lilypond-invoke-editor Cx -> sanitized_helper,
# Print Dialog
/usr/lib/@{multiarch}/libproxy/*/pxgsettings Cx -> sanitized_helper,
# For Xubuntu to launch the browser
#include
--
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/2045744
Title:
Add profile to open Textedit links in files generated by Lilypond
Status in evince package in Ubuntu:
New
Bug description:
I modified the /etc/apparmor.d/usr.bin.evince file to be able to click
on Textedit links (these are generated by the Lilypond program) so
that it opens up an editor at the correct place in the file.
Since I need to port this change every time that the profile is
changed up-stream, and more people need to change their config in
order to be able to easily edit their source files, I thought it would
help to add this to the standard config for AppArmor for Evince.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: evince 42.3-0ubuntu3.1
ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
Uname: Linux 5.15.0-89-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed Dec 6 10:19:36 2023
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-06-03 (2376 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: evince
UpgradeStatus: Upgraded to jammy on 2022-08-31 (461 days ago)
modified.conffile..etc.apparmor.d.usr.bin.evince: [modified]
mtime.conffile..etc.apparmor.d.usr.bin.evince: 2023-12-06T09:40:27.053916
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2045744/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045744] [NEW] Add profile to open Textedit links in files generated by Lilypond
Public bug reported: I modified the /etc/apparmor.d/usr.bin.evince file to be able to click on Textedit links (these are generated by the Lilypond program) so that it opens up an editor at the correct place in the file. Since I need to port this change every time that the profile is changed up-stream, and more people need to change their config in order to be able to easily edit their source files, I thought it would help to add this to the standard config for AppArmor for Evince. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126 Uname: Linux 5.15.0-89-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Dec 6 10:19:36 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-03 (2376 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-08-31 (461 days ago) modified.conffile..etc.apparmor.d.usr.bin.evince: [modified] mtime.conffile..etc.apparmor.d.usr.bin.evince: 2023-12-06T09:40:27.053916 ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2045744 Title: Add profile to open Textedit links in files generated by Lilypond Status in evince package in Ubuntu: New Bug description: I modified the /etc/apparmor.d/usr.bin.evince file to be able to click on Textedit links (these are generated by the Lilypond program) so that it opens up an editor at the correct place in the file. Since I need to port this change every time that the profile is changed up-stream, and more people need to change their config in order to be able to easily edit their source files, I thought it would help to add this to the standard config for AppArmor for Evince. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126 Uname: Linux 5.15.0-89-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Dec 6 10:19:36 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-03 (2376 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-08-31 (461 days ago) modified.conffile..etc.apparmor.d.usr.bin.evince: [modified] mtime.conffile..etc.apparmor.d.usr.bin.evince: 2023-12-06T09:40:27.053916 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2045744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045743] [NEW] Ubuntu Pro attached machine displays ESM support until 31/12/99
Public bug reported: The Software and Update app incorrectly shows ESM support continuing until 31/12/99 when the machine is Pro attached. The date for basic support displays correctly when Pro is not enabled. Worth noting that this page does not refresh when a Pro token is detached and needs a relaunch to display the correct support status. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2023-12-06 08-48-52.png" https://bugs.launchpad.net/bugs/2045743/+attachment/5726651/+files/Screenshot%20from%202023-12-06%2008-48-52.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2045743 Title: Ubuntu Pro attached machine displays ESM support until 31/12/99 Status in software-properties package in Ubuntu: New Bug description: The Software and Update app incorrectly shows ESM support continuing until 31/12/99 when the machine is Pro attached. The date for basic support displays correctly when Pro is not enabled. Worth noting that this page does not refresh when a Pro token is detached and needs a relaunch to display the correct support status. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2045743/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2045740] [NEW] gnome-terminal shortcut key meddled by more general one
Public bug reported: In ubuntu 22.04.03 with gnome terminal version 3.44.0 for GNOME 42 If I define a general shortcut crtl+T in place of ctrl+alt+T for new terminal. the shortcut key ctrl+shift+T in gnome-terminal do not work (no response) Choosing another shortcut for the gnome-terminal will restore the function (for example ctrl+alt+T will work and open a new tab). ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2045740 Title: gnome-terminal shortcut key meddled by more general one Status in gnome-terminal package in Ubuntu: New Bug description: In ubuntu 22.04.03 with gnome terminal version 3.44.0 for GNOME 42 If I define a general shortcut crtl+T in place of ctrl+alt+T for new terminal. the shortcut key ctrl+shift+T in gnome-terminal do not work (no response) Choosing another shortcut for the gnome-terminal will restore the function (for example ctrl+alt+T will work and open a new tab). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2045740/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
