[Desktop-packages] [Bug 2005128] Re: mouse issues
Thanks for the bug report. I can see it happening in: [ 870.506] (II) modeset(0): Modeline "1366x768"x0.0 76.30 1366 1404 1426 1592 768 771 777 798 -hsync -vsync (47.9 kHz eP) [ 1932.032] (II) config/udev: removing device PixArt USB Optical Mouse [ 1932.033] (**) Option "fd" "29" [ 1932.033] (II) event5 - PixArt USB Optical Mouse: device removed [ 1932.036] (II) UnloadModule: "libinput" [ 1932.036] (II) systemd-logind: releasing fd for 13:69 [ 3180.712] (II) modeset(0): EDID vendor "AUO", prod id 11836 The problem is probably a hardware failure so you should try a different mouse. But if it is a software bug then it should be assigned to the kernel. ** Package changed: xorg (Ubuntu) => linux-hwe-5.4 (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/2005128 Title: mouse issues Status in linux-hwe-5.4 package in Ubuntu: New Bug description: external mouse disconnects after a while ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-137.154~18.04.1-generic 5.4.218 Uname: Linux 5.4.0-137-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 4 08:52:55 2023 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2019-07-28 (1287 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20L5000WUS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-137-generic root=UUID=9b94eb86-06c2-4d70-892a-122273bb72c0 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2022 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000WUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET71W(1.46):bd09/29/2022:svnLENOVO:pn20L5000WUS:pvrThinkPadT480:rvnLENOVO:rn20L5000WUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000WUS dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1~kisak~b version.libgl1-mesa-dri: libgl1-mesa-dri 22.3.4~kisak1~b version.libgl1-mesa-glx: libgl1-mesa-glx 22.3.4~kisak1~b version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/2005128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004063] Re: mouse pointer becomes laggy after some time and progressively gets worse
Yeah I noticed the extensions are still loaded so I opened the extension menu and switched off all extensions globally. I have thought about using my computer without Chrome but I don't have much to do on the machine without a browser. Perhaps I could use Firefox temporarily to see if the problem still persists. I will continue to try different experiments. -- 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/2004063 Title: mouse pointer becomes laggy after some time and progressively gets worse Status in gnome-shell package in Ubuntu: Incomplete Bug description: Over some period of time after logging in the mouse becomes laggy and eventually unusable. I generally have a lot of Chrome tabs open. The time period can be minutes to maybe an hour. I am not sure if Chrome is required to cause the problem yet but I have experimented with changed Chrome versions and enable/disable hardware acceleration in Chrome and that did not make a difference. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 27 23:12:58 2023 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-28 (1492 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-22 (219 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2004063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006042] Re: Laptop often freezes after waking up from suspend to ram
Thanks for the bug report. Next time the problem happens, please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. ** Summary changed: - Laptop often freezes after waking up from suspend to ram + [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: resume suspend-resume -- 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/2006042 Title: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram Status in Ubuntu: Incomplete Bug description: Hi, After waking up from suspend to RAM, my computer actually wakes up but can sometimes then hang on a black screen (no prompt, nothing displayed, screen is active). This issue happens quite frequently but seems rather random. I think certain circumstances lower the frequency (I'll elaborate in the report). First of all, I'm not exactly sure when it started but I would say first notable frequent occurrences were around summer 2021 (yes, I'm late, sorry for that). When this happens, Algr+SysRQ+[usb] is unresponsive. Or at least that's what I used to believe as it used to be true as I always tried from the laptop integrated keyboard. Until I connected an USB-C mechanical keyboard, from which I'm *sometimes* able to use the magic keys (not always, and with a lot of lag, but still). If magic keys are unresponsive, I need to hard reset/long press power. There is nothing unusual before that in syslog nor kern.log, at least not that I know of. Except the ^@^@^@ characters when I had to hard reset the computer. If I leave the laptop like that for a while, it eventually reboots by itself and stays on the FDE passphrase prompt (which is not nice as the screen can then stay on for a very long like that if I did not notice). I'm running KDE/Plasma desktop, and this issue has happened regardless of the display manager. I used to run Xorg but now I'm on wayland flavor (mostly to alleviate firefox rendering/compositing issues). This also seems unrelated to external screen being connected or not, as it happened in the past regardless of that parameter. Although, it *seems* frequency has lowered a bit since I changed the way I wake up my laptop. Higher frequency (almost every day): - no external screen or external screen connected to HDMI port - waking up from integrated keyboard power button short press Lower frequency (one to multiple times a week, but somewhat irregular, since ~ 2 months ago): - external screen connected to USB-C port - mechanical keyboard connected to USB-C port of screen - waking up from the mechanical keyboard It also seems to happen more frequently if I wake up the computer, do some very fast task and send it to sleep in under a few minutes. It's not guaranteed to happen, but seems to highly increase the probability. Also, this might be related so I'm adding that bit: I had to disable shutting the screen Off in energy saving settings, as enabling that option would trigger a similar behavior after a break long enough for that setting to trigger. I would come back on a laptop having self-rebooted and waiting for my input on the FDE passphrase prompt. During ACPI options testing, I noticed that setting might cause the sleep order to get cancelled. From that, I suspect in that case the laptop would go to sleep, then wake up immediately, which could have been triggering the bug as I described previously that rapid state changes would increase probability. Then as I described earlier, if I do nothing when this happens, the computer eventually reboots. This is only speculation as I'm usually not here to observe the behavior (this mostly happened during lunch breaks, which are long enough for all of these steps to happen). I disabled screen turn-off energy saving option a long while ago and have taken the habit of manually suspending to RAM when I intend on going away from the computer for more than a few minutes. As I described above, I've tried a few changes to check for behavior but that was a few months ago and I don't clearly remember all scenario. What I remember is that changing any of these did not resolve my issue and some even prevented my computer to even suspend to RAM properly (waking up immediately after). Among the options I tried is: - booting with a previous kernel, but then it's been happening for so long this would obviously not work (just for the sake of completion) - booting on latest mainstream kernel (tested linux-image-unsigned-6.0.9-060009-generic, this was the latest version when I tried a while ago) - booting with i915.enable_dpcd_backlight=3 (I thi
[Desktop-packages] [Bug 2006038] Re: can't restart when screen sleeps and power adapter plugged in
Thanks for the bug report. Next time the problem happens, please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. ** Summary changed: - can't restart when screen sleeps and power adapter plugged in + [Asus ZenBook UX325EA] can't restart when screen sleeps and power adapter plugged in ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: resume suspend-resume -- 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/2006038 Title: [Asus ZenBook UX325EA] can't restart when screen sleeps and power adapter plugged in Status in Ubuntu: Incomplete Bug description: on an Asus zenbook, 2022. When power is plugged in and screen goes to sleep, I can't get back, even with ctrl-alt-f1. I have to do a hard reboot. Here's my uname: Linux sleeky 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 4 17:21:51 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1452] InstallationDate: Installed on 2023-01-13 (22 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX325EA_UX325EA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=9d28c423-b126-49e5-9092-3ea7e2e68951 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX325EA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX325EA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.8 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX325EA.308:bd07/29/2021:br5.19:efr3.8:svnASUSTeKCOMPUTERINC.:pnZenBookUX325EA_UX325EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX325EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX325EA_UX325EA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2006038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004063] Re: mouse pointer becomes laggy after some time and progressively gets worse
It looks like the mouse is wireless. Please also test with a wired mouse so as to rule out radio interference. -- 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/2004063 Title: mouse pointer becomes laggy after some time and progressively gets worse Status in gnome-shell package in Ubuntu: Incomplete Bug description: Over some period of time after logging in the mouse becomes laggy and eventually unusable. I generally have a lot of Chrome tabs open. The time period can be minutes to maybe an hour. I am not sure if Chrome is required to cause the problem yet but I have experimented with changed Chrome versions and enable/disable hardware acceleration in Chrome and that did not make a difference. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 27 23:12:58 2023 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-28 (1492 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-22 (219 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2004063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004063] Re: mouse pointer becomes laggy after some time and progressively gets worse
It was just to confirm whether Chrome was using too much CPU and/or too much RAM at times. -- 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/2004063 Title: mouse pointer becomes laggy after some time and progressively gets worse Status in gnome-shell package in Ubuntu: Incomplete Bug description: Over some period of time after logging in the mouse becomes laggy and eventually unusable. I generally have a lot of Chrome tabs open. The time period can be minutes to maybe an hour. I am not sure if Chrome is required to cause the problem yet but I have experimented with changed Chrome versions and enable/disable hardware acceleration in Chrome and that did not make a difference. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 27 23:12:58 2023 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-28 (1492 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-22 (219 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2004063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006044] Re: Cursor becomes separated from window when unmaximizing via mouse drag
Tracking upstream in https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/4006 ** Summary changed: - Program opens in full screen and mouse pointer moves strangely when attempting to minimize the program on Ubuntu 22.10 system + Cursor becomes separated from window when unmaximizing via mouse drag ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Changed in: mutter (Ubuntu) Status: Incomplete => New ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4006 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4006 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4006 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** No longer affects: gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2006044 Title: Cursor becomes separated from window when unmaximizing via mouse drag Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: Processor: Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz Architecture: x86_64 Address sizes: 36 bits physical, 48 bits virtual CPU(s): 4 On-line CPU(s) list: 0-3 Vendor ID: GenuineIntel Model name: Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz CPU family: 6 Core(s) per socket: 4 Socket(s): 1 Virtualization: VT-x --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: sddm DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-01-24 (12 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Package: gnome-shell 43.1-0ubuntu1 PackageArchitecture: amd64 RelatedPackageVersions: mutter-common 43.0-1ubuntu4 Tags: kinetic Uname: Linux 6.1.9-060109-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2006044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787049] Re: gnome-shell crashed with SIGSEGV in meta_window_unmaximize() from update_move() from meta_window_handle_mouse_grab_op_event() from meta_display_handle_event()
** Tags added: jammy -- 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/1787049 Title: gnome-shell crashed with SIGSEGV in meta_window_unmaximize() from update_move() from meta_window_handle_mouse_grab_op_event() from meta_display_handle_event() Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/5fb0c783621f10ac741a0a841432fcc9a74ca69c --- I did not notice anything, but the system reported a crash. This is a macbookpro14,3 kernel 4.18. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 Uname: Linux 4.18.0-041800-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 14 12:38:19 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-09 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f598429b278 : mov 0x18(%rax),%esi PC (0x7f598429b278) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_window_unmaximize () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_window_handle_mouse_grab_op_event () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_window_unmaximize() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006055] Re: Gnome stuck after going to "activities"
Thanks for the bug report. The first thing to try is to uninstall/delete this extension: 'vertical-overv...@rensalthuis.github.com' and then log in again. If in doubt then just delete all local extensions: cd ~/.local/share/gnome-shell rm -rf extensions If the problem still occurs then next check for crashes by: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2006055 Title: Gnome stuck after going to "activities" Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome gets stuck keeping the CPU busy ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Feb 5 17:25:52 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-12-07 (60 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 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/2006055/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006070] Re: incredibly high memory usage
The attached information looks like memory mapped files. So that's virtual address space, not real memory. Please run: ps auxw > psall.txt and attach the resulting text file here. ** Project changed: xorg-server => gnome-software ** Package changed: xorg (Ubuntu) => gnome-software (Ubuntu) ** Changed in: gnome-software (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2006070 Title: incredibly high memory usage Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: Incomplete Bug description: Please describe the issue you’re experiencing: gnome-software is consuming 6+ GB of RAM on my machine. This is unacceptable and is affecting all other applications. Error message appearing in /var/log/syslog N/A -- other processes are fighting for memory, and OOM killer is more active. What Linux distribution are you using, and what kind of package (RPM, deb, flatpak, etc.) are you experiencing the problem with? Ubuntu 22.10 apt flatpak I don't know how to replicate this issue, however it does appear to be a problem retaining memory. See LSOF report below, software is gnome-software 43.0 ``` sudo lsof -p 750448 -n > ~/ramusage.txt cat ramusage.txt | perl -lane 'print "$F[6] $F[0] $F[1] $F[2] $F[3] $F[4] $F[5] $F[7] $F[8] $F[9] $F[10]"' | sort -rn > sorted-report.txt ``` Top 10 filehandles are holding onto something like 6GB of RAM?! What's going on here ? (open filehandles, sorted by bytes): ``` 1 157191688 gnome-sof 750448 beadon 11u netlink 0t0 ROUTE 2 103546882 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/icons/hicolor/icon-theme.cache 3 103022860 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/glib-2.0/schemas/gschemas.compiled 4 61210892 gnome-sof 750448 beadon DEL REG 259,2 /var/lib/flatpak/exports/share/icons/hicolor/icon-theme.cache 5 60828700 gnome-sof 750448 beadon DEL REG 259,2 /var/cache/fontconfig/2bd0278d-49c2-4c8c-9eea-32d695b22756-le64.cache-7 6 30430848 gnome-sof 750448 beadon mem REG 259,2 101455545 /usr/lib/x86_64-linux-gnu/libicudata.so.71.1 7 14516125 gnome-sof 750448 beadon mem REG 259,2 97416011 /home/beadon/.cache/gnome-software/flatpak-system-default/components.xmlb 8 11308392 gnome-sof 750448 beadon mem REG 259,2 101450031 /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0 9 8254320 gnome-sof 750448 beadon mem REG 259,2 101450280 /usr/lib/x86_64-linux-gnu/libgtk-4.so.1.800.1 10 7599984 gnome-sof 750448 beadon 475u REG 259,2 60821438 /var/tmp/#60821438 (deleted) 11 7582821 gnome-sof 750448 beadon 476u REG 259,2 60821485 /var/tmp/#60821485 (deleted) 12 6733824 gnome-sof 750448 beadon 478u REG 259,2 60821699 /var/tmp/#60821699 (deleted) 13 5966212 gnome-sof 750448 beadon mem REG 259,2 97419097 /home/beadon/.cache/gnome-software/appstream/components.xmlb 14 5712208 gnome-sof 750448 beadon mem REG 259,2 101450114 /usr/lib/locale/locale-archive 15 5681431 gnome-sof 750448 beadon 477u REG 259,2 60821584 /var/tmp/#60821584 (deleted) 16 5469177 gnome-sof 750448 beadon 482u REG 259,2 60817847 /var/tmp/#60817847 (deleted) 17 5406720 gnome-sof 750448 beadon 479u REG 259,2 60821593 /var/tmp/#60821593 (deleted) 18 5341166 gnome-sof 750448 beadon 493u REG 259,2 60821670 /var/tmp/#60821670 (deleted) 19 4616704 gnome-sof 750448 beadon 206u REG 259,2 60819152 /var/tmp/#60819152 (deleted) 20 4519958 gnome-sof 750448 beadon 497u REG 259,2 60821824 /var/tmp/#60821824 (deleted) ``` Details: [sorted-report.txt](/uploads/43c17fb8547366c33c3e49931a5a07b7/sorted-report.txt) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 5 20:06:15 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/525.78.01, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (27 days ago) InstallationMedia: U
[Desktop-packages] [Bug 1969130] Re: [Feature requrest] nvidia offloading doesn't work on Wayland
How would you use 'Launch using Discrete Graphics Card' if you are trying to run an app from nautilus? it doesn't show that option. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1969130 Title: [Feature requrest] nvidia offloading doesn't work on Wayland Status in OEM Priority Project: Incomplete Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-510 package in Ubuntu: Incomplete Status in xwayland package in Ubuntu: Incomplete Bug description: Based on nvidia README, it supports X server only. https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/primerenderoffload.html It's a wishlist level for nvidia graphic. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969130] Re: [Feature requrest] nvidia offloading doesn't work on Wayland
That would be a feature request for nautilus. More generally I think whatever launches it just needs to set environment: __NV_PRIME_RENDER_OFFLOAD=1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1969130 Title: [Feature requrest] nvidia offloading doesn't work on Wayland Status in OEM Priority Project: Incomplete Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-510 package in Ubuntu: Incomplete Status in xwayland package in Ubuntu: Incomplete Bug description: Based on nvidia README, it supports X server only. https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/primerenderoffload.html It's a wishlist level for nvidia graphic. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006110] [NEW] [SRU] Update to latest bugfix release for jammy
Public bug reported: Appstream 0.15.6 is available since December, 2022 and comes with lots of crash fixes [ Impact ] * Appstream is used by GNOME Software, KDE Discover, Flatpak, Snaps and probably lot of other components, since the release of Jammy, a few point releases have been made to appstream that fixes crashes and optimizations. [ Test Plan ] * Open GNOME Software and KDE Discover and see that it is still populatedwith data [ Where problems could occur ] * GNOME Software and KDE Discover could be affected by a sudden crashes but that is unlikely. [ Other Info ] * ** Affects: appstream (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [SRU] Update to latest bugfix release + [SRU] Update to latest bugfix release for jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/2006110 Title: [SRU] Update to latest bugfix release for jammy Status in appstream package in Ubuntu: New Bug description: Appstream 0.15.6 is available since December, 2022 and comes with lots of crash fixes [ Impact ] * Appstream is used by GNOME Software, KDE Discover, Flatpak, Snaps and probably lot of other components, since the release of Jammy, a few point releases have been made to appstream that fixes crashes and optimizations. [ Test Plan ] * Open GNOME Software and KDE Discover and see that it is still populatedwith data [ Where problems could occur ] * GNOME Software and KDE Discover could be affected by a sudden crashes but that is unlikely. [ Other Info ] * To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/2006110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999201] Re: right click on file/folder icon shows broken menu
** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1999201 Title: right click on file/folder icon shows broken menu Status in nautilus package in Ubuntu: Confirmed Bug description: Hi, Ubuntu 22.10 here Open Nautilus. Right click on any file or folder. Often shows a visually and functionally broken menu, where some items are hidden / overlapped by others. And those items can't be triggered. Screenshot attached. ( that screenshot may also serve to show a gnome-screenshot bug which is unable to correctly capture mouse cursor, see https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1989295 ) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-27 (43 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Package: nautilus 1:43.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Tags: wayland-session kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-27 (44 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Package: nautilus 1:43.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1999201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004063] Re: mouse pointer becomes laggy after some time and progressively gets worse
I use a thinkpad keyboard that has the little red pointer stick in the middle. It is USB and shows the same issue. When the mouse gets laggy the Alt-Tab switcher also will not come up or takes a while, depending on the circumstances. -- 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/2004063 Title: mouse pointer becomes laggy after some time and progressively gets worse Status in gnome-shell package in Ubuntu: Incomplete Bug description: Over some period of time after logging in the mouse becomes laggy and eventually unusable. I generally have a lot of Chrome tabs open. The time period can be minutes to maybe an hour. I am not sure if Chrome is required to cause the problem yet but I have experimented with changed Chrome versions and enable/disable hardware acceleration in Chrome and that did not make a difference. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 27 23:12:58 2023 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-28 (1492 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-22 (219 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2004063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004480] Re: Can't authenticate to Office 365 with oauth
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2004480 Title: Can't authenticate to Office 365 with oauth Status in Mozilla Thunderbird: Unknown Status in thunderbird package in Ubuntu: Confirmed Bug description: Upstream issue :https://bugzilla.mozilla.org/show_bug.cgi?id=1810760 Thunderbird blog post: https://blog.thunderbird.net/2023/01/important- message-for-microsoft-office-365-enterprise-users/ They say they released a "second build" of version 102.7.1. This is the version I have on Ubuntu 22.04 but I guess I have the "first build" installed? Could you backport the fix please? To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/2004480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987631] Re: Screencast only records one second
To clarify the gstreamer fix should be sufficient. The pipewire always- copy change I made allows for working around the bug but isn't required as long as you have the gstreamer fix. Fixes the bug in gstreamer: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/1c8244a19dbb4ebdf972a703b55d719f2b968056 Makes it possible to work around the gstreamer bug without updating gstreamer: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525c1ac946a915599c6bee813e88e8cee12 Note that gnome-shell applies the always-copy pipewire workaround based on gstreamer/pipewire version detection so this logic may need tweaking due to backports: https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/43.2/js/dbusServices/screencast/screencastService.js#L233-235 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: New Status in gstreamer1.0 source package in Jammy: New Status in pipewire source package in Jammy: Triaged Bug description: [Impact] When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed the Cheese preview stuck issue on jammy * d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch - Camera output freeze when using pipewiresrc (LP: #1985057) Here is a comment from https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 . === So that's a regression of one of the cherrypicked commits, details are in https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488 the issue is fixed in Kinetic through a combination of the shell fix and a new pipewire. In 22.04 the shell issue is fixed in the recent 42.5 update but we will need to cherrypick https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire to be working. === [Test Plan] 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression hardware list: a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD b. 0c45:6747 Microdia Integrated_Webcam_HD c. 0c45:6a14 Microdia Integrated_Webcam_HD d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera f. 0408:545a Quanta Computer, Inc. HP 5MP Camera g. 0408:5483 Quanta Computer, Inc. HP HD Camera h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4) i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a) j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD 2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2) 3. $ sudo reboot 4. Check if gst-launch-1.0 work a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest gst-launch-1.0 command b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin ! videoconvert ! glimagesink c. Check if the result ok 5. Check the screencast function by pressing 'prt sc' a. the screenshot of all screen/selected region should work good b. the screenrecord of all screen/selected region should work good 6. Check that video recording in gnome-shell works - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, verify that there is a new entry in ~/Video 7. Check that screen sharing is working - go to settings, screen sharing and enable the feature - try to connect using rdp/vnc from another client do those steps under wayland and unset X [Where problems could occur] The patches try to dequeue the shared buffer, instead of pool buffer to prevent the pool buffer being corrupted. it might cause some camera preview failed if shared buffer is corrupted. It is from upstream and there is no regression found, so the risk is low. [Other Info] Upstream commits for pipewire: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92 https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525c1ac946a915599c6bee813e88e8cee12 Upstream commits for gstre
[Desktop-packages] [Bug 2006113] [NEW] Incomplete variable fonts export to PDF
Public bug reported: Ubuntu version: 22.10 (Kinetic) LO version: 7.5.0_rc3-0ubuntu0.22.10.1~lo1 Document Foundation version: 7.5.0.3 (X86_64) When exporting to PDF a document containing variable fonts, some instances (different weight or width) do not appear. There are in the font list of the PDF document, but not correctly displayed (or printed). This incomplete behaviour is observed with the Ubuntu version of LO7.5, but not with the "official" one, the .deb downloaded from the Document Foundation site. The ODT file is attached, with both PDF output (_UB: Ubuntu, _DF: Document Foundation) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: variable-fonts ** Attachment added: "Polices_variables.tar.xz" https://bugs.launchpad.net/bugs/2006113/+attachment/5645043/+files/Polices_variables.tar.xz ** Tags added: fonts variable ** Tags removed: fonts variable ** Tags added: variable-fonts -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2006113 Title: Incomplete variable fonts export to PDF Status in libreoffice package in Ubuntu: New Bug description: Ubuntu version: 22.10 (Kinetic) LO version: 7.5.0_rc3-0ubuntu0.22.10.1~lo1 Document Foundation version: 7.5.0.3 (X86_64) When exporting to PDF a document containing variable fonts, some instances (different weight or width) do not appear. There are in the font list of the PDF document, but not correctly displayed (or printed). This incomplete behaviour is observed with the Ubuntu version of LO7.5, but not with the "official" one, the .deb downloaded from the Document Foundation site. The ODT file is attached, with both PDF output (_UB: Ubuntu, _DF: Document Foundation) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2006113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004063] Re: mouse pointer becomes laggy after some time and progressively gets worse
Next time the problem happens maybe look at all processes to see which are using the most CPU and RAM: ps auxw > psall.txt and then attach the resulting text file here. -- 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/2004063 Title: mouse pointer becomes laggy after some time and progressively gets worse Status in gnome-shell package in Ubuntu: Incomplete Bug description: Over some period of time after logging in the mouse becomes laggy and eventually unusable. I generally have a lot of Chrome tabs open. The time period can be minutes to maybe an hour. I am not sure if Chrome is required to cause the problem yet but I have experimented with changed Chrome versions and enable/disable hardware acceleration in Chrome and that did not make a difference. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 27 23:12:58 2023 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-28 (1492 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-22 (219 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2004063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kwin (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in kwin package in Debian: New Bug description: ... To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in kwin package in Debian: New Bug description: ... To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3
Apparently since we switched to mozjs102, the jammy image builds FTBFS because mozjs102 is in universe. I see it's in main for all the other series so after a few checks I'll promote it to main in jammy. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 Status in gjs package in Ubuntu: Fix Released Status in mozjs102 package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Committed Status in mozjs102 source package in Jammy: Fix Committed Status in mozjs102 source package in Kinetic: Fix Committed Bug description: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Updating mozjs in stable Ubuntu releases was recommended when Ubuntu first switched back to GNOME, but this is the first time it's been done. Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/ for Firefox ESR releases since Ubuntu's 91.10 and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE issued) mentioned at https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" mkdir ../tarballs; cd ../tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. Initial Testing Done I built the packages in my PPA. I installed the packages on Ubuntu 22.04 LTS and successfully completed the Test Case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004586] Re: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver.
DRI_DRIVER_DIR is supposed to be defined in build/config/linux/BUILD.gn, which relies on pkg-config.py output. The commits 5e90d57 and ac530f7 in amdgpu branch[1] were meant to inspect this more closely by turning debugging statements on. The log[2] says dridriverdir is found: line>dridriverdir=/usr/lib/x86_64-linux-gnu/dri Variable declaration, 'dridriverdir' has value '/usr/lib/x86_64-linux-gnu/dri' dridriverdir: /usr/lib/x86_64-linux-gnu/dri Then I made small changes (which include a runtime DRI_PATH log statement) that shouldn't affect that output and built again, but they affected it as that output mysteriously vanishes. [1] https://code.launchpad.net/~nteodosio/chromium-browser/+git/chromium-browser/+ref/amdgpu [2] https://launchpadlibrarian.net/649525665/buildlog_snap_ubuntu_focal_amd64_chromium-amdgpu_BUILDING.txt.gz [3] https://launchpadlibrarian.net/649584762/buildlog_snap_ubuntu_focal_amd64_chromium-amdgpu_BUILDING.txt.gz -- 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/2004586 Title: Chromium's minigbm uses incorrect path for loading radeonsi_dri driver. Status in chromium-browser package in Ubuntu: In Progress Bug description: [NOTE] This is for the HWACC build of chromium, from snap channel latest/candidate/hwacc $ snap info chromium | grep installed installed: 107.0.5304.68-hwacc(2301) 172MB - This hwacc branch uses minigbm over the Ubuntu-supplied libgbm from Mesa origin. (Unlike the Mesa variant, the minigbm bundled by chromium can do YUV buffers, like NV12.) Regular builds of the chromium snap will not use minigbm, and thus not exhibit this behaviour! Something goes wrong with the expansion of the macro DRI_DRIVER_DIR $ strings /snap/chromium/current/usr/lib/chromium-browser/chrome | grep radeonsi_ /usr/lib64/dri/radeonsi_dri.so DRI_DRIVER_DIR/radeonsi_dri.so dlopen(radeonsi_dri.so) failed with error: The DRI_DRIVER_DIR was not properly expanded to /usr/lib/x86_64-linux- gnu here. I've also built current HEAD of chromium source code manually, and did the same test on that, and that version is unaffected: $ strings out/Default/chrome | grep radeonsi_ dlopen(radeonsi_dri.so) failed with error: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so /usr/lib64/dri/radeonsi_dri.so A partner found this change to third_party/minigbm/src/amdgpu.c:27 to be working: //#define DRI_PATH STRINGIZE(DRI_DRIVER_DIR/radeonsi_dri.so) #define DRI_PATH "/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so" But it is better to understand why this expansion failed. And it is possibly fixed in later chromium releases, if not, we should look how our snap building differs from the official Linux building instructions for chromium. In any case, we should track this. OS: Ubuntu 22.10 Package: chromium Snap version: 107.0.5304.68-hwacc Channel: latest/candidate/hwacc Expectations: correctly loading driver from correct location. Actual: using incorrect location. I will follow up by testing this on a machine with an AMD GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2004586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999581] Re: Missing build dependencies: ruby (>= 1:3.1~)
Latest marisa upload seems to play well with ruby3.1. Will migrate when ruby-defaults has migrated. Closing. ** Tags removed: update-excuse ** Changed in: marisa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to marisa in Ubuntu. https://bugs.launchpad.net/bugs/1999581 Title: Missing build dependencies: ruby (>= 1:3.1~) Status in marisa package in Ubuntu: Invalid Bug description: marisa 0.2.6-12 in -proposed does not build due to a missing dependency. The explanation is that the ruby3.1 transition has not started yet in Ubuntu, see bug #1999550. No need to take separate measures for this reason; it will probably build as soon as the ruby3.1 transition has started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marisa/+bug/1999581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997907] Re: [snap] Message 0 rejected by interface blink.mojom.WidgetHost
Good to hear. Feel free to reopen if it comes back. ** Changed in: chromium-browser (Ubuntu) Status: New => Fix Released -- 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/1997907 Title: [snap] Message 0 rejected by interface blink.mojom.WidgetHost Status in chromium-browser package in Ubuntu: Fix Released Bug description: Chromium shuts down and when restarted, says it didn't shut down properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 24 16:34:50 2022 InstallationDate: Installed on 2022-03-19 (250 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: chromium 107.0.5304.110 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3
The image builds are pulling in -proposed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1993214 Title: [jammy] Update gjs to 1.74 using mozjs102 102.3 Status in gjs package in Ubuntu: Fix Released Status in mozjs102 package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Committed Status in mozjs102 source package in Jammy: Fix Committed Status in mozjs102 source package in Kinetic: Fix Committed Bug description: Impact -- GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 ESR series for security updates for the next year. This requires updating gjs from 1.72 to 1.74 from GNOME 43, as packaged in Ubuntu 22.10. This will be done as a Security Update. Updating mozjs in stable Ubuntu releases was recommended when Ubuntu first switched back to GNOME, but this is the first time it's been done. Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/ for Firefox ESR releases since Ubuntu's 91.10 and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE issued) mentioned at https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/ Uploaded Packages - We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being careful to publish it in main, not universe. And we'll update gjs. No other packages need to be updated for this change. mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are generally not possible), but nothing else in Ubuntu uses it. Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Security Sponsoring --- sudo apt install git-buildpackage gbp clone https://salsa.debian.org/gnome-team/gjs cd gjs git checkout ubuntu/jammy gbp buildpackage --git-builder="debuild -S -nc" mkdir ../tarballs; cd ../tarballs pull-lp-source mozjs102 kinetic cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. Initial Testing Done I built the packages in my PPA. I installed the packages on Ubuntu 22.04 LTS and successfully completed the Test Case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 33027] Re: [dapper] tooltip should disappear
Upstream issue was closed on 2015-02-16 as "RESOLVED WONTFIX" due to 14 years passing since issue was first reported to GNOME. Closing the Papercuts task as no-one is going work on this now. ** Changed in: hundredpapercuts Importance: Undecided => Wishlist ** Changed in: hundredpapercuts Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/33027 Title: [dapper] tooltip should disappear Status in GTK+: Won't Fix Status in One Hundred Papercuts: Won't Fix Status in gtk+2.0 package in Ubuntu: Triaged Bug description: Here gtk tooltips doesn't disappear after a while, as they used to (as far as I remember). This is a pretty annoying behavior, as I have to move the mouse to get rid of it. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/33027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 99015] Re: shuffle doesn't work in queue
Upstream issue was closed on 2008-11-16 as "RESOLVED NOTABUG" so this is seen as working as designed. I'm closing the Papercuts task as any change needs to happen upstream and not in Ubuntu. ** Changed in: hundredpapercuts Importance: Undecided => Wishlist ** Changed in: hundredpapercuts Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/99015 Title: shuffle doesn't work in queue Status in One Hundred Papercuts: Won't Fix Status in Rhythmbox: Invalid Status in rhythmbox package in Ubuntu: Confirmed Bug description: Binary package hint: rhythmbox Today my rhythmbox was upgraded to 0.9.8 by feisty beta. Now when I play my queue, it doesn't matter if "shuffle" is pressed or not - the songs are played in the order they stand there. Pressing shuffle also doesn't change the order. When I delete all songs from the queue and play the library on shuffle that works fine. Before the upgrade I didn't have the problem. EDIT: To be precise, it was upgraded to 0.9.8-0ubuntu3. I don't know which version it was before, probably also a 0.9.8. Steps to reproduce: Put some songs into your queue and play them with shuffle turned on. ProblemType: Bug Architecture: i386 Date: Fri Mar 30 15:49:35 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/rhythmbox Package: rhythmbox 0.9.8-0ubuntu3 PackageArchitecture: i386 ProcCmdline: rhythmbox ProcCwd: /home/tobi ProcEnviron: LANGUAGE=de_DE:de:en_GB:en PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox Uname: Linux tobi-laptop 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/99015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004480] Re: Can't authenticate to Office 365 with oauth
I've observed the issue described in this blog entry on Ubuntu 20.04 after the upgrade from thunderbird:amd64 1:102.4.2+build2-0ubuntu0.20.04.1 to 1:102.7.1+build2-0ubuntu0.20.04.1. The issue is resolved after downgrade back to 102.4.2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2004480 Title: Can't authenticate to Office 365 with oauth Status in Mozilla Thunderbird: Unknown Status in thunderbird package in Ubuntu: Confirmed Bug description: Upstream issue :https://bugzilla.mozilla.org/show_bug.cgi?id=1810760 Thunderbird blog post: https://blog.thunderbird.net/2023/01/important- message-for-microsoft-office-365-enterprise-users/ They say they released a "second build" of version 102.7.1. This is the version I have on Ubuntu 22.04 but I guess I have the "first build" installed? Could you backport the fix please? To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/2004480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 318517] Re: Word wrapping is not respecting indentation
Upstream issue was closed on 2018-05-26 as "RESOLVED WONTFIX". I'm closing the Papercuts task as any changes need to be made upstream and not in Ubuntu. ** Changed in: hundredpapercuts Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview3 in Ubuntu. https://bugs.launchpad.net/bugs/318517 Title: Word wrapping is not respecting indentation Status in gedit: Won't Fix Status in One Hundred Papercuts: Won't Fix Status in gtksourceview3 package in Ubuntu: Triaged Bug description: Binary package hint: gedit When wrapping a line it would be awesome to have gedit indent the wrapped line just like the original line. Imagine "_" being a space character, the current wrapping works like this hello hello hello hello hello hello hello hello It would be better if it worked like this: hello hello hello hello hello hello hello hello While editing this makes code-indentation readable even if the editing window is resized to be very narrow. It is also very helpful for unavoidable long lines, like regexps or URLs. It makes formatting less of a pain with generated code. etc etc etc KDE editor component and Eclipse both have this behaviour, it was also present in the famous EditPlus editor for Windows. I am sure i am not the first person requesting this feature, so i wonder if there is a philosophical stance against this wrapping style or if a plugin is available to handle it. ProblemType: Bug Architecture: i386 Date: Sun Jan 18 20:17:05 2009 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/gedit Package: gedit 2.22.3-0ubuntu1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gedit Uname: Linux 2.6.24-23-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/318517/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910421] Re: Evince crashes on an unreadable nonempty postscript file owned by root
Bug exists in Debian with evince 3.38.2. -- 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/1910421 Title: Evince crashes on an unreadable nonempty postscript file owned by root Status in evince package in Ubuntu: Invalid Bug description: Package: evince Version: 3.38.0-1 I run an up-to-date groovy 20.10. This is how to reproduce the segfault: root@host:/tmp# rm mwe.ps root@host:/tmp# echo "test" > mwe.ps root@host:/tmp# chmod g-rwx,o-rwx mwe.ps root@host:/tmp# exit logout user@host:/tmp$ evince mwe.ps Segmentation fault (core dumped) An expected outcome would be a meaningful error message instead of a crash. Thanks in advance for repairing this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1910421/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2002510] Re: bbswitch-dkms fails to build with jammy/linux-hwe-5.19
Confirmed that bbswitch-dkms (0.8-10ubuntu2.1) can be installed and built on a jammy system running the hwe-5.19 kernel: === Setting up bbswitch-dkms (0.8-10ubuntu2.1) ... Loading new bbswitch-0.8 DKMS files... Building for 5.19.0-32-generic Building initial module for 5.19.0-32-generic Done. bbswitch.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.19.0-32-generic/updates/dkms/ === I couldn't test loading the module due to lack of hardware. ADT tests were also successful with the GA 5.15 kernel: - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/b/bbswitch/20230127_140815_7abe1@/log.gz - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/b/bbswitch/20230127_140058_98ecd@/log.gz ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/2002510 Title: bbswitch-dkms fails to build with jammy/linux-hwe-5.19 Status in bbswitch package in Ubuntu: Fix Released Status in bbswitch source package in Jammy: Fix Committed Bug description: [Impact] bbswitch-dkms fails to build with jammy/linux-hwe-5.19. [Test case] $ sudo apt-get install bbswitch-dkms [Fix] To fix it we can take two approches: a) we import the Lunar version (0.8-14) into Jammy, and it's missing dependency (dh-dkms) or b) we apply the attached debdiff that is syncing the Jammy version up to Lunar, reverting on top the bits depending on dh-dkms. Whichever is the path of last resistance, i'm happy with it. [Regression potential] It's the same DKMS we are already using in Lunar, and it contains all the fixes upstream developed so far: Jammy and Lunar share the same base version (0.8). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/2002510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 923292] Re: shortcut for closing power statistics app not working
Closing Papercuts task as Ubuntu task was closed almost 10 years ago. ** Changed in: hundredpapercuts Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/923292 Title: shortcut for closing power statistics app not working Status in gnome-power: In Progress Status in One Hundred Papercuts: Fix Released Status in gnome-power-manager package in Ubuntu: Fix Released Bug description: Different app but the same type of problem as in #900753. Power statiscits app does not close after ctrl+q (and/or ctrl+w) is hit. Very common shortcut so it'd probably be handled also by Power Statistics app. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/923292/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1910421] Evince crashes on an unreadable nonempty postscript file owned by root
Paul, I tremendously apologize for writing you this way: it seems that my account at launchpad is gone. The bug still exists with the current Ubuntu: $ sudo aptitude show evince| grep Version Version: 43.0-1 $ sudo lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.10 Release: 22.10 Codename: kinetic $ env | grep XDG_SESSION_TYPE XDG_SESSION_TYPE=wayland Please reopen the bug report. Thanks in advance! Md 04.05.2022, 14:50, Bug 1910421 < mailto:1910...@bugs.launchpad.net 1910...@bugs.launchpad.net > Closing as no response to comment #1 re an issue in a release that is no longer supported (groovy). ** Changed in: evince (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1910421 https://bugs.launchpad.net/bugs/1910421 Title: Evince crashes on an unreadable nonempty postscript file owned by root Status in evince package in Ubuntu: Invalid Bug description: Package: evince Version: 3.38.0-1 I run an up-to-date groovy 20.10. This is how to reproduce the segfault: root@host:/tmp# rm mwe.ps root@host:/tmp# echo "test" > mwe.ps root@host:/tmp# chmod g-rwx,o-rwx mwe.ps root@host:/tmp# exit logout user@host:/tmp$ evince mwe.ps Segmentation fault (core dumped) An expected outcome would be a meaningful error message instead of a crash. Thanks in advance for repairing this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1910421/+subsc riptions https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1910421/+subscriptions -- 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/1910421 Title: Evince crashes on an unreadable nonempty postscript file owned by root Status in evince package in Ubuntu: Confirmed Bug description: Package: evince Version: 3.38.0-1 I run an up-to-date groovy 20.10. This is how to reproduce the segfault: root@host:/tmp# rm mwe.ps root@host:/tmp# echo "test" > mwe.ps root@host:/tmp# chmod g-rwx,o-rwx mwe.ps root@host:/tmp# exit logout user@host:/tmp$ evince mwe.ps Segmentation fault (core dumped) An expected outcome would be a meaningful error message instead of a crash. Thanks in advance for repairing this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1910421/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910421] Re: Evince crashes on an unreadable nonempty postscript file owned by root
Bug still exists in Ubuntu 22.10. Bug report re-opened as requested. ** Changed in: evince (Ubuntu) Status: Invalid => Confirmed ** Tags removed: groovy ** Tags added: kinetic -- 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/1910421 Title: Evince crashes on an unreadable nonempty postscript file owned by root Status in evince package in Ubuntu: Confirmed Bug description: Package: evince Version: 3.38.0-1 I run an up-to-date groovy 20.10. This is how to reproduce the segfault: root@host:/tmp# rm mwe.ps root@host:/tmp# echo "test" > mwe.ps root@host:/tmp# chmod g-rwx,o-rwx mwe.ps root@host:/tmp# exit logout user@host:/tmp$ evince mwe.ps Segmentation fault (core dumped) An expected outcome would be a meaningful error message instead of a crash. Thanks in advance for repairing this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1910421/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 388547] Re: Volume keys don't work inside a full-screen game
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #564 https://gitlab.freedesktop.org/xorg/xserver/-/issues/564 ** Changed in: xorg-server Importance: Medium => Unknown ** Changed in: xorg-server Remote watch: freedesktop.org Bugzilla #42244 => gitlab.freedesktop.org/xorg/xserver/-/issues #564 ** Changed in: hundredpapercuts Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/388547 Title: Volume keys don't work inside a full-screen game Status in One Hundred Papercuts: Confirmed Status in X.Org X server: Unknown Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: When I'm playing games in fullscreen mode, I cannot change the volume (laptop, HP tx2115nr with Jaunty) using my notebook keys. It's not possible to use my Play/Pause/Stop hotkeys (right side of my screen). I would like to change my volume without have to exit the game. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/388547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 48671] Re: Cannot rename by clicking on a file
Upstream issue was closed in 2021-06-18 as "RESOLVED OBSOLETE" after 14 years of no activity. I'm removing the Papercuts task as any change needs to happen upstream in GNOME and not in Ubuntu. ** No longer affects: hundredpapercuts -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/48671 Title: Cannot rename by clicking on a file Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: In Windows explorer, clicking a file and then clicking once more on the file name will enter "rename file" mode. Nautilus doesn't do this. Isn't it a useful feature to have? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/48671/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1910421] Evince crashes on an unreadable nonempty postscript file owned by root
Thanks for reopening #1910421 ! Md -- 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/1910421 Title: Evince crashes on an unreadable nonempty postscript file owned by root Status in evince package in Ubuntu: Confirmed Bug description: Package: evince Version: 3.38.0-1 I run an up-to-date groovy 20.10. This is how to reproduce the segfault: root@host:/tmp# rm mwe.ps root@host:/tmp# echo "test" > mwe.ps root@host:/tmp# chmod g-rwx,o-rwx mwe.ps root@host:/tmp# exit logout user@host:/tmp$ evince mwe.ps Segmentation fault (core dumped) An expected outcome would be a meaningful error message instead of a crash. Thanks in advance for repairing this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1910421/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1528928] Re: Specially crafted postscript file forces a segfault
On my machine, sudo systemd-analyze plot|a2ps > temp.ps produces request id is PDF-110 (0 file(s)) in my temp.ps. Do you mean sudo systemd-analyze plot|a2ps -o temp.ps or sudo systemd-analyze plot|a2ps - > temp.ps or something else? In the first two cases, please provide us with the permissions of the file generated, i.e., with the output of ls -la temp.ps to decide whether this bug is an instance of bug #1910421; cf. https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1910421 . (Personally, I doubt that these two bugs have the same cause, but you never know…) -- 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/1528928 Title: Specially crafted postscript file forces a segfault Status in evince package in Ubuntu: New Bug description: Running `evince temp.ps' causes a segmentation fault. The file was generated by doing `sudo systemd-analyze plot|a2ps > temp.ps'. Evince version: "GNOME Document Viewer 3.18.2" Running XFCE 4.12 on Arch Sorry I can't find any more detailed logs, don't really know what I'm looking for. I have attached the file temp.ps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1528928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
** Also affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => High ** Changed in: chromium-browser (Ubuntu) Status: New => In Progress ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) -- 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/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Triaged Bug description: I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1967632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1843392] Re: [snap] smart card reader no longer works
*** This bug is a duplicate of bug 1967632 *** https://bugs.launchpad.net/bugs/1967632 ** This bug has been marked a duplicate of bug 1967632 [snap] apparmor denied when trying to load pkcs11 module for smart card authentication -- 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/1843392 Title: [snap] smart card reader no longer works Status in Mozilla Firefox: Confirmed Status in chromium-browser package in Ubuntu: In Progress Status in firefox package in Ubuntu: Confirmed Bug description: chromium uses the Netscape Cryptographic Module to access smartcards for authentication purposes. This stopped working when switching to the snap version. Chromium would normally access the setup in ~/.pki/nssdb/pkcs11.txt That file would refer to a library used to access the smart card. I.e /usr/lib/x86_64-linux-gnu/pkcs11/opensc- pkcs11.so The problem can be bypassed by manually launching chromium via: /snap/chromium/current/usr/lib/chromium-browser/chrome To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1843392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 514973] Re: [Rhythmbox] Don't play Audiobooks in shuffle mode
Upstream issue was closed 2020/11/15 as no-one was able to provide an answer to "How would any application be able to "identify" audiobook files programmatically? I'm closing this bug report as "Invalid" as this is a GNOME issue for which they have provided an explanation as to why this issue will not be fixed. ** Changed in: hundredpapercuts Status: New => Invalid ** Changed in: rhythmbox (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/514973 Title: [Rhythmbox] Don't play Audiobooks in shuffle mode Status in One Hundred Papercuts: Invalid Status in Rhythmbox: Expired Status in rhythmbox package in Ubuntu: Invalid Bug description: This happens all the time, I'm away from the computer listening to music in shuffle mode, and a chapter of an audiobook starts playing. I have stop what I'm doing and change it. Why would anybody ever want to randomly listen to a random chapter of a book? To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/514973/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 692432] Re: reload in nautilus temporarily blanks file list
The upstream issue was closed on 2021-06-18 as "RESOLVED OBSOLETE" with no action being taken for over 10 years. Any fixes to this issue should be made upstream so not an issue for Ubuntu developers to fix. ** Changed in: hundredpapercuts Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/692432 Title: reload in nautilus temporarily blanks file list Status in One Hundred Papercuts: Won't Fix Status in Nautilus: New Status in nautilus package in Ubuntu: Triaged Bug description: Open a windows in Nautilus Hit F5 or View/Reload The current list of files goes blank then reloads completely This is annoying for me mainly in this scenario: I would like to use a file manager to monitor file sizes from multiple downloads. When I refresh, it should be easy to see if the file size has changed or not. However in nautilus, because the entire screen blanks out and then reappears, it's difficult to see if there has been a change in file size, *especially* if there are several files that changed in size. If you can't visualize how difficult it is to see if multiple files have changed, try setting up multiple file downloads, pointing nautilus at the download directory and hitting F5 to try and see if any of them have changed in file size - the "reload everything" makes it quite difficult. Compare this to doing an "ls -la" in a console window which is nearly instantaneous and you'll see what I mean. If the reload functionality could simply refresh each of the details for each file rather than reloading the whole screen from scratch then it would not "flash" and it would be a lot easier to track file size (or other attribute changes). To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/692432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 514973] Re: [Rhythmbox] Don't play Audiobooks in shuffle mode
The answer is ID3 tags though. On Mon, Feb 6, 2023, 16:26 Paul White <514...@bugs.launchpad.net> wrote: > Upstream issue was closed 2020/11/15 as no-one was able to > provide an answer to "How would any application be able to > "identify" audiobook files programmatically? > > I'm closing this bug report as "Invalid" as this is a GNOME > issue for which they have provided an explanation as to why > this issue will not be fixed. > > ** Changed in: hundredpapercuts >Status: New => Invalid > > ** Changed in: rhythmbox (Ubuntu) >Status: Triaged => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/514973 > > Title: > [Rhythmbox] Don't play Audiobooks in shuffle mode > > Status in One Hundred Papercuts: > Invalid > Status in Rhythmbox: > Expired > Status in rhythmbox package in Ubuntu: > Invalid > > Bug description: > This happens all the time, I'm away from the computer listening to music > in > shuffle mode, and a chapter of an audiobook starts playing. I have stop > what > I'm doing and change it. > > Why would anybody ever want to randomly listen to a random chapter of > a book? > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hundredpapercuts/+bug/514973/+subscriptions > > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/514973 Title: [Rhythmbox] Don't play Audiobooks in shuffle mode Status in One Hundred Papercuts: Invalid Status in Rhythmbox: Expired Status in rhythmbox package in Ubuntu: Invalid Bug description: This happens all the time, I'm away from the computer listening to music in shuffle mode, and a chapter of an audiobook starts playing. I have stop what I'm doing and change it. Why would anybody ever want to randomly listen to a random chapter of a book? To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/514973/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2004649] Re: Regression bug with mesa backport and ogre rendering
** Changed in: mesa (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2004649 Title: Regression bug with mesa backport and ogre rendering Status in mesa package in Ubuntu: Confirmed Bug description: We found a breaking change with https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1991761 when running an application that relies on ogre 1.9 for rendering inside a Docker container based on the ubuntu:jammy image. We could confirm that the upgrade causing this was as follows, because the issue goes away when downgrading versions: [UPGRADE] libegl-mesa0:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1 [UPGRADE] libgbm-dev:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1 [UPGRADE] libgbm1:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1 [UPGRADE] libgl1-mesa-dri:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1 [UPGRADE] libglapi-mesa:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1 [UPGRADE] libglx-mesa0:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1 For completeness, the full stack trace is: Stack trace (most recent call last) in thread 18237: #25 Object "[0x]", at 0x, in #24 Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f2ba75089ff, in #23 Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f2ba7476b42, in #22 Object "/lib/x86_64-linux-gnu/libstdc++.so.6", at 0x7f2ba3a4d2b2, in #21 Object "/usr/lib/x86_64-linux-gnu/ign-gazebo-6/plugins/libignition-gazebo-sensors-system.so", at 0x7f2b6456b2bf, in ignition::gazebo::v6::systems::SensorsPrivate::RenderThread() #20 Object "/usr/lib/x86_64-linux-gnu/ign-gazebo-6/plugins/libignition-gazebo-sensors-system.so", at 0x7f2b6456aba6, in ignition::gazebo::v6::systems::SensorsPrivate::RunOnce() #19 Object "/opt/underlay_ws/install/lib/libignition-sensors6.so.6", at 0x7f2b76db113e, in ignition::sensors::v6::Manager::RunOnce(std::chrono::duration > const&, bool) #18 Object "/opt/underlay_ws/install/lib/libignition-sensors6.so.6", at 0x7f2b76db95b5, in ignition::sensors::v6::Sensor::Update(std::chrono::duration > const&, bool) #17 Object "/opt/underlay_ws/install/lib/libignition-sensors6-rgbd_camera.so.6", at 0x7f2b6436a020, in ignition::sensors::v6::RgbdCameraSensor::Update(std::chrono::duration > const&) #16 Object "/opt/underlay_ws/install/lib/libignition-sensors6-rendering.so.6", at 0x7f2b64282a6d, in ignition::sensors::v6::RenderingSensor::Render() #15 Object "/usr/lib/x86_64-linux-gnu/ign-rendering-6/engine-plugins/libignition-rendering-ogre.so", at 0x7f2b5c6adc85, in ignition::rendering::v6::OgreDepthCamera::PostRender() #14 Object "/usr/lib/x86_64-linux-gnu/ign-rendering-6/engine-plugins/libignition-rendering-ogre.so", at 0x7f2b5c71d743, in ignition::rendering::v6::OgreRenderTexture::Buffer(float*) #13 Object "/lib/x86_64-linux-gnu/libOgreMain.so.1.9.0", at 0x7f2b5c32c90a, in Ogre::RenderTexture::copyContentsToMemory(Ogre::PixelBox const&, Ogre::RenderTarget::FrameBuffer) #12 Object "/usr/lib/x86_64-linux-gnu/OGRE-1.9.0/RenderSystem_GL.so", at 0x7f2aeac67a85, in Ogre::GLTextureBuffer::download(Ogre::PixelBox const&) #11 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b26225cdd, in #10 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b262246ae, in #9 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b262244b0, in #8 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b26082975, in #7 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b26224a86, in #6 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b260800a8, in #5 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b260a3f19, in #4 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b26c77f37, in #3 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b25fa88b6, in #2 Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f2ba740a7f2, in abort #1 Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f2ba7424475, in raise #0 Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f2ba7478a7c, in pthread_kill Aborted (Signal sent by tkill() 17739 0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2004649/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933186] Re: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from met
Thanks for the clarification, however just to make sure whenever I experience this behavior, both bugs are reported together every time. -- 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/1933186 Title: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from meta_window_force_placement() Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Fix Committed Status in mutter source package in Lunar: Fix Released Status in mutter package in Fedora: Unknown 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 3.38.4-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/7ae33f650c2de2c5580905f0c63e5b6c35fb46c6 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/mutter/+bug/1933186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006070] Re: incredibly high memory usage
Ok, one better, sorted results (lots of chrome tabs appear, fyi). ps auxw --sort -rss > psall.txt See attached file, since gnome-software has restarted, in 1 day it's up to 501+MB and written ~1.9GB to disk (why??). ** Attachment added: "psall.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2006070/+attachment/5645104/+files/psall.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2006070 Title: incredibly high memory usage Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: Incomplete Bug description: Please describe the issue you’re experiencing: gnome-software is consuming 6+ GB of RAM on my machine. This is unacceptable and is affecting all other applications. Error message appearing in /var/log/syslog N/A -- other processes are fighting for memory, and OOM killer is more active. What Linux distribution are you using, and what kind of package (RPM, deb, flatpak, etc.) are you experiencing the problem with? Ubuntu 22.10 apt flatpak I don't know how to replicate this issue, however it does appear to be a problem retaining memory. See LSOF report below, software is gnome-software 43.0 ``` sudo lsof -p 750448 -n > ~/ramusage.txt cat ramusage.txt | perl -lane 'print "$F[6] $F[0] $F[1] $F[2] $F[3] $F[4] $F[5] $F[7] $F[8] $F[9] $F[10]"' | sort -rn > sorted-report.txt ``` Top 10 filehandles are holding onto something like 6GB of RAM?! What's going on here ? (open filehandles, sorted by bytes): ``` 1 157191688 gnome-sof 750448 beadon 11u netlink 0t0 ROUTE 2 103546882 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/icons/hicolor/icon-theme.cache 3 103022860 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/glib-2.0/schemas/gschemas.compiled 4 61210892 gnome-sof 750448 beadon DEL REG 259,2 /var/lib/flatpak/exports/share/icons/hicolor/icon-theme.cache 5 60828700 gnome-sof 750448 beadon DEL REG 259,2 /var/cache/fontconfig/2bd0278d-49c2-4c8c-9eea-32d695b22756-le64.cache-7 6 30430848 gnome-sof 750448 beadon mem REG 259,2 101455545 /usr/lib/x86_64-linux-gnu/libicudata.so.71.1 7 14516125 gnome-sof 750448 beadon mem REG 259,2 97416011 /home/beadon/.cache/gnome-software/flatpak-system-default/components.xmlb 8 11308392 gnome-sof 750448 beadon mem REG 259,2 101450031 /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0 9 8254320 gnome-sof 750448 beadon mem REG 259,2 101450280 /usr/lib/x86_64-linux-gnu/libgtk-4.so.1.800.1 10 7599984 gnome-sof 750448 beadon 475u REG 259,2 60821438 /var/tmp/#60821438 (deleted) 11 7582821 gnome-sof 750448 beadon 476u REG 259,2 60821485 /var/tmp/#60821485 (deleted) 12 6733824 gnome-sof 750448 beadon 478u REG 259,2 60821699 /var/tmp/#60821699 (deleted) 13 5966212 gnome-sof 750448 beadon mem REG 259,2 97419097 /home/beadon/.cache/gnome-software/appstream/components.xmlb 14 5712208 gnome-sof 750448 beadon mem REG 259,2 101450114 /usr/lib/locale/locale-archive 15 5681431 gnome-sof 750448 beadon 477u REG 259,2 60821584 /var/tmp/#60821584 (deleted) 16 5469177 gnome-sof 750448 beadon 482u REG 259,2 60817847 /var/tmp/#60817847 (deleted) 17 5406720 gnome-sof 750448 beadon 479u REG 259,2 60821593 /var/tmp/#60821593 (deleted) 18 5341166 gnome-sof 750448 beadon 493u REG 259,2 60821670 /var/tmp/#60821670 (deleted) 19 4616704 gnome-sof 750448 beadon 206u REG 259,2 60819152 /var/tmp/#60819152 (deleted) 20 4519958 gnome-sof 750448 beadon 497u REG 259,2 60821824 /var/tmp/#60821824 (deleted) ``` Details: [sorted-report.txt](/uploads/43c17fb8547366c33c3e49931a5a07b7/sorted-report.txt) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 5 20:06:15 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/525.78.01, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (27 days ago) InstallationMedia:
[Desktop-packages] [Bug 2006370] [NEW] Terribly flicking and blicking HDMI-port display
Public bug reported: Hi, I have HP15 Gaming Pavilion bought 2-3 years ago. I had Windows 10 before (not it is the second OS due to this bug [I can't use Ubuntu with this bug]), and Win 10 has no problems. No solution [that I found over the internet] worked. I have to have at least two displays. My connection technology: PC HDMI output -> HDMI-VGA(+audio) transmitter -> LED 20' Display (external monitor) Win 10 have never had any problems with it (it has good drivers). When I add any input to the second screen - it blinks and flickers so terrible that I can see nothing - a white screen problem. If I do nothing - it will turn to some picture in some time, but if I make any action at the second monitor - flickering and the white screen problem appears again. I think these are drivers. I tested the equipment in Win 10 after I found this bug - and it works perfectly (so, the hardware is good). It is a typical notebook and this bug is crucial. I use two monitors to type codes and work on PC. I can't survive with just one monitor. Right now when I am typing you this message the second monitor became white again for quite a long time (I did nothing there). I hope you will be able to fix this bug :) Best wishes, Alex, Prague, Czech Republic, EU PS: When typing this message I found another bug compared to MS Windows. When making screenshots (Alt/Shift + Print Screen) - it makes perfect picture even when you actually have the second monitor white all the time (so the screenshot is not how it is). I made an actual photo (and deleted some parts of the background not related to the monitors/computer). You can see a white screen, but the screenshot shows a "perfect world" with a perfect picture which is not how it is on the screen. Windows, on the contrary, makes actual screenshots. And Win 10 test of this monitor never have this white screen or any other monitor problems. Moreover, when the monitors stops to be white for a second it depicts different picture (more terrible image; it is disproportional, with font heavily readable, but the screenshot functions shows an "ideal world" a user can never see :) I made this detailed description to help Ubuntu. I think the project is great in concept, but poor in realization. Such bugs make it impossible for users to use Ubuntu (who can work on just one monitor? Who do not wish to make screenshots with what he/she actually sees on the monitor [rather than modified images with the pictures users do not actually see]?). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 6 19:45:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117M [10de:1f99] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU117M [103c:87b1] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87b1] InstallationDate: Installed on 2023-02-04 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=30f188c5-d67f-4f68-ba6d-6995864ff95e ro quiet splash loglevel=3 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2021 dmi.bios.release: 15.25 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87B1 dmi.board.vendor: HP dmi.board.version: 31.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 31.23 dmi.modalias: dmi:bvnAMI:bvrF.25:bd08/18/2021:br15.25:efr31.23:svnHP:pnHPPavilionGamingLaptop15-ec1xxx:pvr:rvnHP:rn87B1:rvr31.23:cvnHP:ct10:cvrChassisVersion:sku1N3L2EA#ACB: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-ec1xxx dmi.product.sku: 1N3L2EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu)
[Desktop-packages] [Bug 2006370] Re: Terribly flicking and blicking HDMI-port display
PPS: I have Ubuntu 22.04 (the same version) on my Acer Aspire 3 A315-21G-63YM [very old notebook of about 5-6 years old]; I tried several times to connect this notebook to the same monitor with the same scheme - it works perfectly (I did not try screenshots, because the picture there is perfect). But I still am a rare user of Ubuntu, because I need powerful computers (like this HP Gaming Pavilion) for my operations, and I can't do them on just one monitor in quite OK computers, and I can't do this on two monitors with a relatively slow computer like Acer Aspire 3. It means, it is some driver issue [that Ubuntu has problems with the inbuilt drivers, but not 100% sure in this]. -- 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/2006370 Title: Terribly flicking and blicking HDMI-port display Status in xorg package in Ubuntu: New Bug description: Hi, I have HP15 Gaming Pavilion bought 2-3 years ago. I had Windows 10 before (not it is the second OS due to this bug [I can't use Ubuntu with this bug]), and Win 10 has no problems. No solution [that I found over the internet] worked. I have to have at least two displays. My connection technology: PC HDMI output -> HDMI-VGA(+audio) transmitter -> LED 20' Display (external monitor) Win 10 have never had any problems with it (it has good drivers). When I add any input to the second screen - it blinks and flickers so terrible that I can see nothing - a white screen problem. If I do nothing - it will turn to some picture in some time, but if I make any action at the second monitor - flickering and the white screen problem appears again. I think these are drivers. I tested the equipment in Win 10 after I found this bug - and it works perfectly (so, the hardware is good). It is a typical notebook and this bug is crucial. I use two monitors to type codes and work on PC. I can't survive with just one monitor. Right now when I am typing you this message the second monitor became white again for quite a long time (I did nothing there). I hope you will be able to fix this bug :) Best wishes, Alex, Prague, Czech Republic, EU PS: When typing this message I found another bug compared to MS Windows. When making screenshots (Alt/Shift + Print Screen) - it makes perfect picture even when you actually have the second monitor white all the time (so the screenshot is not how it is). I made an actual photo (and deleted some parts of the background not related to the monitors/computer). You can see a white screen, but the screenshot shows a "perfect world" with a perfect picture which is not how it is on the screen. Windows, on the contrary, makes actual screenshots. And Win 10 test of this monitor never have this white screen or any other monitor problems. Moreover, when the monitors stops to be white for a second it depicts different picture (more terrible image; it is disproportional, with font heavily readable, but the screenshot functions shows an "ideal world" a user can never see :) I made this detailed description to help Ubuntu. I think the project is great in concept, but poor in realization. Such bugs make it impossible for users to use Ubuntu (who can work on just one monitor? Who do not wish to make screenshots with what he/she actually sees on the monitor [rather than modified images with the pictures users do not actually see]?). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 6 19:45:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117M [10de:1f99] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU117M [103c:87b1] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87b1] InstallationDate: Installed on 2023-02-04 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=30f188c5-d67f-4f68-ba6d-6995864ff95e ro quiet splash loglevel=3 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2021 dmi.bios.release: 15.25 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.boar
[Desktop-packages] [Bug 2005124] Re: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubu
It struck me that this issue motivates a Breaks/Replaces in fontconfig- config to ensure smooth upgrades. I uploaded that change. ** Changed in: fontconfig (Ubuntu) Status: Invalid => Fix Committed ** Changed in: fontconfig (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2005124 Title: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 Status in fontconfig package in Ubuntu: Fix Committed Status in kubuntu-settings package in Ubuntu: Fix Released Status in fontconfig package in Debian: Unknown Bug description: I don't know ProblemType: Package DistroRelease: Ubuntu 23.04 Package: fontconfig-config 2.13.1-4.4ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Feb 4 05:59:53 2023 DuplicateSignature: package:fontconfig-config:2.13.1-4.4ubuntu1 Unpacking fontconfig-config (2.14.1-3ubuntu1) over (2.13.1-4.4ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-xn7IM4/015-fontconfig-config_2.14.1-3ubuntu1_amd64.deb (--unpack): trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 ErrorMessage: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 InstallationDate: Installed on 2023-01-31 (3 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230130) PackageArchitecture: all Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.19ubuntu3 apt 2.5.5 SourcePackage: fontconfig Title: package fontconfig-config 2.13.1-4.4ubuntu1 failed to install/upgrade: trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package kubuntu-settings-desktop 1:23.04.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen
Hi, affected here. Laptop + external monitor via docking station and DVI. Ubuntu 22.04.1, wayland. Affected apps: Firefox, gnome-terminal, evolution, Non-affected apps: rocket-chat-client (snap), Slack, MS-Teams (electron), nautilus Yours, Steffen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen Status in Dash to dock: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gnome-desktop package in Fedora: Confirmed Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-02-18 (328 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 43.0-1ubuntu4 Tags: wayland-session third-party-packages kinetic Uname: Linux 5.19.0-28-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899667] Re: LO can't send email, probably an apparmour problem
This is still broken in Kubuntu, as of 22.10. I use LO & Thunderbird. The preliminary steps happen, such as creating a PDF--if requested. But the email application (Thunderbird in my case) is never called. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1899667 Title: LO can't send email, probably an apparmour problem Status in kmail package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: LO can't send email: LibreOffice was unable to find a working email configuration. I'm pretty sure this is an apparmour profile problem since LO seems to want RW perms on something and AA seems not to want to give it. There lies the full extent on mu debugging expertise in this area. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.25 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Oct 13 17:01:43 2020 InstallationDate: Installed on 2017-03-26 (1297 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-10-08 (4 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmail/+bug/1899667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006110] Re: [SRU] Update to latest bugfix release for jammy
In any case, don't take 0.16.0 without this patch: https://github.com/ximion/appstream/commit/631303a8d16c2f608428a89bb94511bc28ae5417 - otherwise anything that's using GIR bindings will crash. I will be making an emergency 0.16.1 release soon, and all previous releases are perfectly fine and well tested too :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/2006110 Title: [SRU] Update to latest bugfix release for jammy Status in appstream package in Ubuntu: New Bug description: Appstream 0.15.6 is available since December, 2022 and comes with lots of crash fixes [ Impact ] * Appstream is used by GNOME Software, KDE Discover, Flatpak, Snaps and probably lot of other components, since the release of Jammy, a few point releases have been made to appstream that fixes crashes and optimizations. [ Test Plan ] * Open GNOME Software and KDE Discover and see that it is still populatedwith data [ Where problems could occur ] * GNOME Software and KDE Discover could be affected by a sudden crashes but that is unlikely. [ Other Info ] * To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/2006110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998917] Re: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04
The printer has firmware 20111021. The newest available firmware is 20140618 but can only be installed through Windows. This printer always reports low toner and I ignore it because it will continue printing with no loss of quality for hundreds of pages, usually several times what I already printed. It has also been telling me to replace the imaging drum for about 4 years. If you want me to try sending a mono Apple Raster you'll need to tell me how. How does any of this explain why 18.04 still prints at the correct size? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1998917 Title: Everything prints approximately 2% too small after upgrading to Ubuntu 22.04 Status in cups package in Ubuntu: New Bug description: To reproduce: 1. Open Inkscape. 2. Draw a rectangle 170mm x 230mm. 3. Print it. Expected result: The printed rectangle on paper should measure 170mm x 230mm. Actual result: The rectangle measures 168mm x 226mm, a difference of approximately 2%. I print a lot of labels. I make them in both LibreOffice (for mail merge) and Inkscape (when I want them all the same). I use standard downloaded templates in LibreOffice and in Inkscape I have made my own manually. I recently upgraded to 22.04 and now whenever I print any of my existing documents they no longer line up with the labels. They line up in the top left of the page but at the bottom right they are misaligned, shifted up and left. This happens because the entire page is now printed 2% smaller. Nothing else has changed about my setup: it is the same printer and the same documents printing differently. The printer is a network printer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-Gray..\' already exists W [06/Dec/2022:00:00:06 +] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_LaserJet_100_colorMFP_M175nw_61F41D-DeviceN..\' already exists CurrentDesktop: XFCE Date: Tue Dec 6 11:42:58 2022 InstallationDate: Installed on 2018-05-07 (1673 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_61F41D: implicitclass://HP_LaserJet_100_colorMFP_M175nw_61F41D/ MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=96ca3669-e2ac-4371-b36d-55bc9f3bd03a ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: no changes found SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-08-12 (115 days ago) dmi.bios.date: 03/15/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: Z170-A 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.:bvr3802:bd03/15/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A: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: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987631] Re: Screencast only records one second
** Changed in: gst-plugins-base1.0 (Ubuntu Jammy) Status: New => In Progress ** Changed in: gstreamer1.0 (Ubuntu Jammy) Status: New => In Progress ** Changed in: pipewire (Ubuntu Jammy) Status: Triaged => In Progress ** Changed in: gst-plugins-base1.0 (Ubuntu Jammy) Assignee: (unassigned) => Bin Li (binli) ** Changed in: gstreamer1.0 (Ubuntu Jammy) Assignee: (unassigned) => Bin Li (binli) ** Changed in: pipewire (Ubuntu Jammy) Assignee: (unassigned) => Bin Li (binli) ** Changed in: gst-plugins-base1.0 (Ubuntu) Status: New => Fix Released ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: In Progress Status in gstreamer1.0 source package in Jammy: In Progress Status in pipewire source package in Jammy: In Progress Bug description: [Impact] When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed the Cheese preview stuck issue on jammy * d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch - Camera output freeze when using pipewiresrc (LP: #1985057) Here is a comment from https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 . === So that's a regression of one of the cherrypicked commits, details are in https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488 the issue is fixed in Kinetic through a combination of the shell fix and a new pipewire. In 22.04 the shell issue is fixed in the recent 42.5 update but we will need to cherrypick https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire to be working. === [Test Plan] 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression hardware list: a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD b. 0c45:6747 Microdia Integrated_Webcam_HD c. 0c45:6a14 Microdia Integrated_Webcam_HD d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera f. 0408:545a Quanta Computer, Inc. HP 5MP Camera g. 0408:5483 Quanta Computer, Inc. HP HD Camera h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4) i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a) j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD 2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2) 3. $ sudo reboot 4. Check if gst-launch-1.0 work a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest gst-launch-1.0 command b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin ! videoconvert ! glimagesink c. Check if the result ok 5. Check the screencast function by pressing 'prt sc' a. the screenshot of all screen/selected region should work good b. the screenrecord of all screen/selected region should work good 6. Check that video recording in gnome-shell works - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, verify that there is a new entry in ~/Video 7. Check that screen sharing is working - go to settings, screen sharing and enable the feature - try to connect using rdp/vnc from another client do those steps under wayland and unset X [Where problems could occur] The patches try to dequeue the shared buffer, instead of pool buffer to prevent the pool buffer being corrupted. it might cause some camera preview failed if shared buffer is corrupted. It is from upstream and there is no regression found, so the risk is low. [Other Info] Upstream commits for pipewire: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92 https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525c1ac946a915599c6bee813e88e8cee12 Upstream commits for gstreamer: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/com
[Desktop-packages] [Bug 1887252] Re: config-error-dialog.sh should pass --no-markup
** Tags added: jammy lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1887252 Title: config-error-dialog.sh should pass --no-markup Status in gdm3 package in Ubuntu: Incomplete Status in lightdm package in Ubuntu: Incomplete Bug description: I modified my ~/.profile to call "logger". This resulted in in producing some output on stderr like ``` <13>Jul 11 13:02:46 /usr/sbin/lightdm-session[1408]: profile sourced ... ``` This showed an empty zenity prompt. Logs suggest zenity was failing because it was treating `<13>` as pango markup. ``` from markup due to error parsing markup: Error on line 3 char 6: “13” is not a valid ``` We should not assume the error message strings contain valid markup, since their source is unknown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006070] Re: incredibly high memory usage
There is no indication of a bug in the attachment of comment #6. The largest process is one of your Chrome tabs, and most of your memory is occupied by Chrome tabs. gnome-software has a resident set size of "only" 493616K. I agree that's a silly amount of memory, but it's not unusual these days and is not "6+ GB". If gnome-software is growing further over time then please provide more samples showing it getting bigger. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2006070 Title: incredibly high memory usage Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: Incomplete Bug description: Please describe the issue you’re experiencing: gnome-software is consuming 6+ GB of RAM on my machine. This is unacceptable and is affecting all other applications. Error message appearing in /var/log/syslog N/A -- other processes are fighting for memory, and OOM killer is more active. What Linux distribution are you using, and what kind of package (RPM, deb, flatpak, etc.) are you experiencing the problem with? Ubuntu 22.10 apt flatpak I don't know how to replicate this issue, however it does appear to be a problem retaining memory. See LSOF report below, software is gnome-software 43.0 ``` sudo lsof -p 750448 -n > ~/ramusage.txt cat ramusage.txt | perl -lane 'print "$F[6] $F[0] $F[1] $F[2] $F[3] $F[4] $F[5] $F[7] $F[8] $F[9] $F[10]"' | sort -rn > sorted-report.txt ``` Top 10 filehandles are holding onto something like 6GB of RAM?! What's going on here ? (open filehandles, sorted by bytes): ``` 1 157191688 gnome-sof 750448 beadon 11u netlink 0t0 ROUTE 2 103546882 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/icons/hicolor/icon-theme.cache 3 103022860 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/glib-2.0/schemas/gschemas.compiled 4 61210892 gnome-sof 750448 beadon DEL REG 259,2 /var/lib/flatpak/exports/share/icons/hicolor/icon-theme.cache 5 60828700 gnome-sof 750448 beadon DEL REG 259,2 /var/cache/fontconfig/2bd0278d-49c2-4c8c-9eea-32d695b22756-le64.cache-7 6 30430848 gnome-sof 750448 beadon mem REG 259,2 101455545 /usr/lib/x86_64-linux-gnu/libicudata.so.71.1 7 14516125 gnome-sof 750448 beadon mem REG 259,2 97416011 /home/beadon/.cache/gnome-software/flatpak-system-default/components.xmlb 8 11308392 gnome-sof 750448 beadon mem REG 259,2 101450031 /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0 9 8254320 gnome-sof 750448 beadon mem REG 259,2 101450280 /usr/lib/x86_64-linux-gnu/libgtk-4.so.1.800.1 10 7599984 gnome-sof 750448 beadon 475u REG 259,2 60821438 /var/tmp/#60821438 (deleted) 11 7582821 gnome-sof 750448 beadon 476u REG 259,2 60821485 /var/tmp/#60821485 (deleted) 12 6733824 gnome-sof 750448 beadon 478u REG 259,2 60821699 /var/tmp/#60821699 (deleted) 13 5966212 gnome-sof 750448 beadon mem REG 259,2 97419097 /home/beadon/.cache/gnome-software/appstream/components.xmlb 14 5712208 gnome-sof 750448 beadon mem REG 259,2 101450114 /usr/lib/locale/locale-archive 15 5681431 gnome-sof 750448 beadon 477u REG 259,2 60821584 /var/tmp/#60821584 (deleted) 16 5469177 gnome-sof 750448 beadon 482u REG 259,2 60817847 /var/tmp/#60817847 (deleted) 17 5406720 gnome-sof 750448 beadon 479u REG 259,2 60821593 /var/tmp/#60821593 (deleted) 18 5341166 gnome-sof 750448 beadon 493u REG 259,2 60821670 /var/tmp/#60821670 (deleted) 19 4616704 gnome-sof 750448 beadon 206u REG 259,2 60819152 /var/tmp/#60819152 (deleted) 20 4519958 gnome-sof 750448 beadon 497u REG 259,2 60821824 /var/tmp/#60821824 (deleted) ``` Details: [sorted-report.txt](/uploads/43c17fb8547366c33c3e49931a5a07b7/sorted-report.txt) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 5 20:06:15 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/525.78.01, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDa
[Desktop-packages] [Bug 2006070] Re: incredibly high memory usage
Yes, I killed the process as it approached 6GB after I filed this report. I will report back with the growth over the next few days. I suspect it occured when I switched between different wireless networks and physical locations, but I would need to run a series of tests to conslude this for certain. I also find Chrome's dramatic consumption of memory to be unnecessary, but this is another task to trace For the moment, I still am focused on gnome-software. For reference I am finding 2-older reports of a memory leak in gnome-software, but these too seemed to have died out as the reporter eventually stopped responding (they're a year old or more). These might be related. reference: https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1590 https://gitlab.gnome.org/GNOME/gnome-software/-/issues/941 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/-/issues #1590 https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1590 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/-/issues #941 https://gitlab.gnome.org/GNOME/gnome-software/-/issues/941 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2006070 Title: incredibly high memory usage Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: Incomplete Bug description: Please describe the issue you’re experiencing: gnome-software is consuming 6+ GB of RAM on my machine. This is unacceptable and is affecting all other applications. Error message appearing in /var/log/syslog N/A -- other processes are fighting for memory, and OOM killer is more active. What Linux distribution are you using, and what kind of package (RPM, deb, flatpak, etc.) are you experiencing the problem with? Ubuntu 22.10 apt flatpak I don't know how to replicate this issue, however it does appear to be a problem retaining memory. See LSOF report below, software is gnome-software 43.0 ``` sudo lsof -p 750448 -n > ~/ramusage.txt cat ramusage.txt | perl -lane 'print "$F[6] $F[0] $F[1] $F[2] $F[3] $F[4] $F[5] $F[7] $F[8] $F[9] $F[10]"' | sort -rn > sorted-report.txt ``` Top 10 filehandles are holding onto something like 6GB of RAM?! What's going on here ? (open filehandles, sorted by bytes): ``` 1 157191688 gnome-sof 750448 beadon 11u netlink 0t0 ROUTE 2 103546882 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/icons/hicolor/icon-theme.cache 3 103022860 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/glib-2.0/schemas/gschemas.compiled 4 61210892 gnome-sof 750448 beadon DEL REG 259,2 /var/lib/flatpak/exports/share/icons/hicolor/icon-theme.cache 5 60828700 gnome-sof 750448 beadon DEL REG 259,2 /var/cache/fontconfig/2bd0278d-49c2-4c8c-9eea-32d695b22756-le64.cache-7 6 30430848 gnome-sof 750448 beadon mem REG 259,2 101455545 /usr/lib/x86_64-linux-gnu/libicudata.so.71.1 7 14516125 gnome-sof 750448 beadon mem REG 259,2 97416011 /home/beadon/.cache/gnome-software/flatpak-system-default/components.xmlb 8 11308392 gnome-sof 750448 beadon mem REG 259,2 101450031 /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0 9 8254320 gnome-sof 750448 beadon mem REG 259,2 101450280 /usr/lib/x86_64-linux-gnu/libgtk-4.so.1.800.1 10 7599984 gnome-sof 750448 beadon 475u REG 259,2 60821438 /var/tmp/#60821438 (deleted) 11 7582821 gnome-sof 750448 beadon 476u REG 259,2 60821485 /var/tmp/#60821485 (deleted) 12 6733824 gnome-sof 750448 beadon 478u REG 259,2 60821699 /var/tmp/#60821699 (deleted) 13 5966212 gnome-sof 750448 beadon mem REG 259,2 97419097 /home/beadon/.cache/gnome-software/appstream/components.xmlb 14 5712208 gnome-sof 750448 beadon mem REG 259,2 101450114 /usr/lib/locale/locale-archive 15 5681431 gnome-sof 750448 beadon 477u REG 259,2 60821584 /var/tmp/#60821584 (deleted) 16 5469177 gnome-sof 750448 beadon 482u REG 259,2 60817847 /var/tmp/#60817847 (deleted) 17 5406720 gnome-sof 750448 beadon 479u REG 259,2 60821593 /var/tmp/#60821593 (deleted) 18 5341166 gnome-sof 750448 beadon 493u REG 259,2 60821670 /var/tmp/#60821670 (deleted) 19 4616704 gnome-sof 750448 beadon 206u REG 259,2 60819152 /var/tmp/#60819152 (deleted) 20 4519958 gnome-sof 750448 beadon 497u REG 259,2 60821824 /var/tmp/#60821824 (deleted) ``` Details: [sorted-report.txt](/uploads/43c17fb8547366c33c3e49931a5a07b7/sorted-report.txt) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 5 20:06:15 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contrac
Re: [Desktop-packages] [Bug 1887252] Re: config-error-dialog.sh should pass --no-markup
On Tue, Feb 7, 2023 at 10:45 AM Daniel van Vugt <1887...@bugs.launchpad.net> wrote: > > ** Tags added: jammy lunar > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2005135). > https://bugs.launchpad.net/bugs/1887252 > > Title: > config-error-dialog.sh should pass --no-markup > > Status in gdm3 package in Ubuntu: > Incomplete > Status in lightdm package in Ubuntu: > Incomplete > > Bug description: > I modified my ~/.profile to call "logger". This resulted in in > producing some output on stderr like > > ``` > <13>Jul 11 13:02:46 /usr/sbin/lightdm-session[1408]: profile sourced ... > ``` > > This showed an empty zenity prompt. > > Logs suggest zenity was failing because it was treating `<13>` as > pango markup. > > ``` >from markup due to error parsing markup: Error on line 3 char 6: “13” is > not a valid > ``` > > We should not assume the error message strings contain valid markup, > since their source is unknown. So, what should be the appropriate bug fix method in this scenario? > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+subscriptions Best, Zhao -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1887252 Title: config-error-dialog.sh should pass --no-markup Status in gdm3 package in Ubuntu: Incomplete Status in lightdm package in Ubuntu: Incomplete Bug description: I modified my ~/.profile to call "logger". This resulted in in producing some output on stderr like ``` <13>Jul 11 13:02:46 /usr/sbin/lightdm-session[1408]: profile sourced ... ``` This showed an empty zenity prompt. Logs suggest zenity was failing because it was treating `<13>` as pango markup. ``` from markup due to error parsing markup: Error on line 3 char 6: “13” is not a valid ``` We should not assume the error message strings contain valid markup, since their source is unknown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006070] Re: incredibly high memory usage
Please also only test the "apt" version of gnome-software for now because bugs from flatpaks can't be tracked here. The "ubuntu/+source" part of the URL means we're only talking about debs installed via apt. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2006070 Title: incredibly high memory usage Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: Incomplete Bug description: Please describe the issue you’re experiencing: gnome-software is consuming 6+ GB of RAM on my machine. This is unacceptable and is affecting all other applications. Error message appearing in /var/log/syslog N/A -- other processes are fighting for memory, and OOM killer is more active. What Linux distribution are you using, and what kind of package (RPM, deb, flatpak, etc.) are you experiencing the problem with? Ubuntu 22.10 apt flatpak I don't know how to replicate this issue, however it does appear to be a problem retaining memory. See LSOF report below, software is gnome-software 43.0 ``` sudo lsof -p 750448 -n > ~/ramusage.txt cat ramusage.txt | perl -lane 'print "$F[6] $F[0] $F[1] $F[2] $F[3] $F[4] $F[5] $F[7] $F[8] $F[9] $F[10]"' | sort -rn > sorted-report.txt ``` Top 10 filehandles are holding onto something like 6GB of RAM?! What's going on here ? (open filehandles, sorted by bytes): ``` 1 157191688 gnome-sof 750448 beadon 11u netlink 0t0 ROUTE 2 103546882 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/icons/hicolor/icon-theme.cache 3 103022860 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/glib-2.0/schemas/gschemas.compiled 4 61210892 gnome-sof 750448 beadon DEL REG 259,2 /var/lib/flatpak/exports/share/icons/hicolor/icon-theme.cache 5 60828700 gnome-sof 750448 beadon DEL REG 259,2 /var/cache/fontconfig/2bd0278d-49c2-4c8c-9eea-32d695b22756-le64.cache-7 6 30430848 gnome-sof 750448 beadon mem REG 259,2 101455545 /usr/lib/x86_64-linux-gnu/libicudata.so.71.1 7 14516125 gnome-sof 750448 beadon mem REG 259,2 97416011 /home/beadon/.cache/gnome-software/flatpak-system-default/components.xmlb 8 11308392 gnome-sof 750448 beadon mem REG 259,2 101450031 /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0 9 8254320 gnome-sof 750448 beadon mem REG 259,2 101450280 /usr/lib/x86_64-linux-gnu/libgtk-4.so.1.800.1 10 7599984 gnome-sof 750448 beadon 475u REG 259,2 60821438 /var/tmp/#60821438 (deleted) 11 7582821 gnome-sof 750448 beadon 476u REG 259,2 60821485 /var/tmp/#60821485 (deleted) 12 6733824 gnome-sof 750448 beadon 478u REG 259,2 60821699 /var/tmp/#60821699 (deleted) 13 5966212 gnome-sof 750448 beadon mem REG 259,2 97419097 /home/beadon/.cache/gnome-software/appstream/components.xmlb 14 5712208 gnome-sof 750448 beadon mem REG 259,2 101450114 /usr/lib/locale/locale-archive 15 5681431 gnome-sof 750448 beadon 477u REG 259,2 60821584 /var/tmp/#60821584 (deleted) 16 5469177 gnome-sof 750448 beadon 482u REG 259,2 60817847 /var/tmp/#60817847 (deleted) 17 5406720 gnome-sof 750448 beadon 479u REG 259,2 60821593 /var/tmp/#60821593 (deleted) 18 5341166 gnome-sof 750448 beadon 493u REG 259,2 60821670 /var/tmp/#60821670 (deleted) 19 4616704 gnome-sof 750448 beadon 206u REG 259,2 60819152 /var/tmp/#60819152 (deleted) 20 4519958 gnome-sof 750448 beadon 497u REG 259,2 60821824 /var/tmp/#60821824 (deleted) ``` Details: [sorted-report.txt](/uploads/43c17fb8547366c33c3e49931a5a07b7/sorted-report.txt) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 5 20:06:15 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/525.78.01, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom,
[Desktop-packages] [Bug 2006370] Re: Terribly flicking and blicking HDMI-port display
Thanks for the bug report. It looks like this is probably a bug in the nouveau graphics driver, and most likely the HDMI port is connected to your Nvidia GPU. The nouveau driver is also logging errors which may or may not be related to this bug. Please open the 'Additional Drivers' app and use it to install an official Nvidia driver instead. ** Tags added: amdgpu dualgpu hybrid nouveau ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Terribly flicking and blicking HDMI-port display + [nouveau] Terribly flicking and blicking HDMI-port display -- 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/2006370 Title: [nouveau] Terribly flicking and blicking HDMI-port display Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have HP15 Gaming Pavilion bought 2-3 years ago. I had Windows 10 before (not it is the second OS due to this bug [I can't use Ubuntu with this bug]), and Win 10 has no problems. No solution [that I found over the internet] worked. I have to have at least two displays. My connection technology: PC HDMI output -> HDMI-VGA(+audio) transmitter -> LED 20' Display (external monitor) Win 10 have never had any problems with it (it has good drivers). When I add any input to the second screen - it blinks and flickers so terrible that I can see nothing - a white screen problem. If I do nothing - it will turn to some picture in some time, but if I make any action at the second monitor - flickering and the white screen problem appears again. I think these are drivers. I tested the equipment in Win 10 after I found this bug - and it works perfectly (so, the hardware is good). It is a typical notebook and this bug is crucial. I use two monitors to type codes and work on PC. I can't survive with just one monitor. Right now when I am typing you this message the second monitor became white again for quite a long time (I did nothing there). I hope you will be able to fix this bug :) Best wishes, Alex, Prague, Czech Republic, EU PS: When typing this message I found another bug compared to MS Windows. When making screenshots (Alt/Shift + Print Screen) - it makes perfect picture even when you actually have the second monitor white all the time (so the screenshot is not how it is). I made an actual photo (and deleted some parts of the background not related to the monitors/computer). You can see a white screen, but the screenshot shows a "perfect world" with a perfect picture which is not how it is on the screen. Windows, on the contrary, makes actual screenshots. And Win 10 test of this monitor never have this white screen or any other monitor problems. Moreover, when the monitors stops to be white for a second it depicts different picture (more terrible image; it is disproportional, with font heavily readable, but the screenshot functions shows an "ideal world" a user can never see :) I made this detailed description to help Ubuntu. I think the project is great in concept, but poor in realization. Such bugs make it impossible for users to use Ubuntu (who can work on just one monitor? Who do not wish to make screenshots with what he/she actually sees on the monitor [rather than modified images with the pictures users do not actually see]?). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 6 19:45:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117M [10de:1f99] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU117M [103c:87b1] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:87b1] InstallationDate: Installed on 2023-02-04 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=30f188c5-d67f-4f68-ba6d-6995864ff95e ro quiet splash loglevel=3 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2021 dmi.bios.release: 15.25 dmi.bios.vendor: AMI dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87B1 dmi.board.vendor: HP dmi.board.version: 31.23 dmi.chassis.type: 10 dmi.chassi
