[Desktop-packages] [Bug 1989128] Re: Reintroduce Ctrl+Shift+PrtScn key combination
ok, by the way ubuntu deviates from gnome in this. ** Attachment added: "gnome printscreen shortcuts" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989128/+attachment/5619703/+files/gnome-ps.png -- 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/1989128 Title: Reintroduce Ctrl+Shift+PrtScn key combination Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: Since 22.04 Ctrl-Shift-Printscreen (copy selection of screen to clipboard) isn't working anymore To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1989128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990456] Re: xorg reports bogus 1600x1024 resolution
Hello Yao, or anyone else affected, Accepted xorg-server into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:21.1.3-2ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: xorg-server (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1990456 Title: xorg reports bogus 1600x1024 resolution Status in OEM Priority Project: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Bug description: xorg reports 1600x1024 bogus resolution [ Impact ] * User of NVIDIA GPU is able to switch to 1600x1024 resolution but cannot display anything under the resolution [ Fix ] Drop 001_fedora_extramodes.patch which was dropped from Fedora since xserver 1.5.0. [ Test Plan ] 1. Find a test unit with NVIDIA GPU, or anything but use Xorg mode to enter the desktop 2. Type `xrandr` in terminal Expected: The resolution 1600x1024 should not appear if the display does not support it. Actual: The resolution 1600x1024 appears. [ Where problems could occur ] * Lack of extra modes that the display might actually support. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 399765] Re: [Upstream] Ctrl Q doesn't quit when a combo box is focused
** Changed in: df-libreoffice Importance: Low => Wishlist -- 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/399765 Title: [Upstream] Ctrl Q doesn't quit when a combo box is focused Status in LibreOffice: Confirmed Status in OpenOffice: Invalid Status in libreoffice package in Ubuntu: Confirmed Bug description: OpenOffice.org 3.0.1, Ubuntu 9.04 LibreOffice 3.4.3, Ubuntu 11.10 beta 1. Focus any combo box, e.g. the style combo box in Writer, or the font or size combo boxes in Writer or Calc. 2. Type Ctrl Q to quit the program. What should happen: The application quits. What actually happens: Nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/399765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970800] Re: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch
Yes it's still not solved if you want... nevertheless, I no longer notice this bug under Ubuntu 22.10 whereas I noticed it before! And this as well with real and virtual installations. So sorry for those who still have this bug but I repeat what I said before, I don't have it anymore, that's all. I'm not a specialized technician, I see, that's all. -- 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/1970800 Title: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: If you click a calendar date in the bottom row of the top panel calendar, the backdrop shrinks and the dates overflow out of the backdrop boundaries. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 28 16:25:17 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] CometLake-U GT2 [UHD Graphics] [1462:129c] Subsystem: Micro-Star International Co., Ltd. [MSI] TU117M [GeForce GTX 1650 Mobile / Max-Q] [1462:129c] InstallationDate: Installed on 2022-04-22 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2019 dmi.bios.release: 1.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16S3IMS.108 dmi.board.asset.tag: Default string dmi.board.name: MS-16S3 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16S3.1: dmi.product.family: Prestige dmi.product.name: Prestige 15 A10SC dmi.product.sku: 16S3.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/gnome-shell/+bug/1970800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991001] Re: Can't move (or see) the mouse cursor during desktop zoom
> I used gsettings to set caret-tracking and focus-tracking to 'none' Did you perhaps also change mouse-tracking to 'none' by accident? It should be 'push': gsettings set org.gnome.desktop.a11y.magnifier mouse-tracking 'push' ** Summary changed: - Gnome Zoom/Magnifier doesn't work after log-in + Can't move (or see) the mouse cursor during desktop zoom ** 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/1991001 Title: Can't move (or see) the mouse cursor during desktop zoom Status in gnome-shell package in Ubuntu: Incomplete Bug description: What I expect to happen: After booting up Ubuntu I'd like to be able to just enable desktop zoom using Alt+Super+8. What actually happens: When I enable desktop zoom after logging in to Ubuntu, it doesn't work. Magnifier zooms in to the top-left portion of my desktop. The mouse pointer disappears and I can no longer move my view around. I can still disable zoom, so apparently it didn't crash. After I go to Settings->Accessibility>Zoom, change some settings and enable zoom it works. When I change the settings back to my preferences it still works. After this the magnifier seems to work without further problems. I'm experiencing this problem with both xorg and Wayland. Some general information: - My Magnifier settings: - Magnification: 2.00 - Magnifier position: - Screen part: full screen - Magnifier cursor pushes contents around - I used gsettings to set caret-tracking and focus-tracking to 'none' - Graphics card: NVidia GeForce GTX 970 - Graphics driver: Proprietary nvidia-driver-5.15 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.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: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 27 18:44:56 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 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/1991001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990998] Re: gnome-shell crashes on connection from gnome-remote-desktop in EXTEND mode
*** This bug is a duplicate of bug 1970917 ***
https://bugs.launchpad.net/bugs/1970917
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1970917, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.
** No longer affects: gnome-shell (Ubuntu)
** This bug has been marked a duplicate of bug 1970917
gnome-shell crashes with SIGABRT due to assertion failure "!window->monitor
|| g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager),
window->monitor)" in meta_window_update_for_monitors_changed()
--
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/1990998
Title:
gnome-shell crashes on connection from gnome-remote-desktop in EXTEND
mode
Status in mutter package in Ubuntu:
New
Bug description:
Hey all,
I've encountered a bug in libmutter that crashes GNOME Shell when connecting
via gnome-remote-desktop in EXTEND mode.
gnome-shell[1500]: **
gnome-shell[1500]:
libmutter:ERROR:../src/core/window.c:3730:meta_window_update_for_monitors_changed:
assertion failed: (!window->monitor || g_list_find
(meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor))
gnome-shell[1500]: Bail out!
libmutter:ERROR:../src/core/window.c:3730:meta_window_update_for_monitors_changed:
assertion failed: (!window->monitor || g_list_find
(meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor))
gnome-shell[1500]: GNOME Shell crashed with signal 6
This statistically crashes the GNOME session on connection from RDP.
This bug is addressed in
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2554
Steps to Reproduce:
1. Setup Ubuntu machine on low resolution (1280x960)
2. Setup gnome-remote-desktop to accept connections in 'extend' mode.
3. Connect from xfreerdp with /dynamic-resolution and /w:, /h: set to a
resolution much larger than your current monitor (For example 3840x2160 on a
1080p screen)
4. Open multiple windows, shift them around, maximize some.
5. Disconnect
6. Reconnect.
7. Session should crash, resulting in potential used data loss.
NOTE: I couldn't reliably reproduce the bug. Sometimes restarting and trying
again triggered it.
Setup:
lsb_release -a:
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy
apt-cache policy mutter:
mutter:
Installed: 42.2-0ubuntu1
Candidate: 42.2-0ubuntu1
Version table:
*** 42.2-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64
Packages
100 /var/lib/dpkg/status
42.0-3ubuntu2 500
500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
apt-cache policy gnome-shell:
gnome-shell:
Installed: 42.4-0ubuntu0.22.04.1
Candidate: 42.4-0ubuntu0.22.04.1
Version table:
*** 42.4-0ubuntu0.22.04.1 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
42.0-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
```
(gdb) bt full
#0 __pthread_kill_implementation (no_tid=0, signo=6,
threadid=139943778018752) at ./nptl/pthread_kill.c:44
tid =
ret = 0
pd = 0x7f47332d65c0
old_mask = {__val = {2048, 139943866772608, 2064, 129,
95, 139943865243713, 139943866772704, 0, 7, 139943865090602, 344544753768,
2048, 94006337625088, 5680105379855955242, 143, 2096}}
ret =
#1 __pthread_kill_internal (signo=6, threadid=139943778018752) at
./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=139943778018752, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
#3 0x7f47385a3476 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
ret =
#4 0x7f47385897f3 in __GI_abort () at ./stdlib/abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0xed,
sa_sigaction = 0xed}, sa_mask = {__val = {237, 94006402588640,
139943881008423, 94006314421680, 140725925571312, 32, 94006337054400,
0, 6907377910888285440, 1, 18446744073709551488, 61, 214,
140725925571408, 139943868561280, 139943868561280}}, sa_flags =
945841363, sa_restorer = 0x557f8e53a6c0}
sigs = {__val = {32, 139943866772608, 1322117968, 0,
139943868561280, 6907377910888285440, 94006310750208, 18446744073709551488, 61,
140725925571304, 237, 1, 94006337054400, 139943865246931, 94006337054400,
[Desktop-packages] [Bug 1988836] Re: Enable the open NVIDIA kernel modules
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-515 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-515/515.65.01-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-515 (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Focal: In Progress Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Jammy: In Progress Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988786] Re: system does not boot after full-upgrade on kinetic
** Tags added: kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1988786 Title: system does not boot after full-upgrade on kinetic Status in gdm3 package in Ubuntu: New Status in gnome-session package in Ubuntu: New Bug description: Hi, After a full upgrade on a kinetic system, the system no longer boots normally. When I power the computer on, I get a prompt to decrypt my disk. I insert the password, and am redirected to a screen saying a fschk is running. It spend hours in that screen with apparently no activity. Pressing ctrl+C does not help at that point. Booting through recovery mode and then requesting to proceed to boot works fine. A regular fschk also suceeds. Here is what I could extract from my journal: Sep 05 16:10:57 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Sep 05 16:10:57 castor gnome-session-binary[2000]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Sep 05 16:10:57 castor gnome-session-binary[2000]: Unrecoverable failure in required component org.gnome.Shell.desktop Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Activating service name='ca.desrt.dconf' requested by ':1.2' (uid=127 pid=2000 comm="/usr/libexec/gnome-session-binary --autostart /usr" label="unconfined") Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Successfully activated service 'ca.desrt.dconf' Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.54' (uid=127 pid=3239 comm="/usr/libexec/gsd-rfkill" label="unconfined") Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Activating service name='org.freedesktop.systemd1' requested by ':1.7' (uid=127 pid=3227 comm="/usr/libexec/gsd-sharing" label="unconfined") Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Sep 05 16:10:57 castor systemd[1]: Starting Hostname Service... Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Successfully activated service 'org.freedesktop.hostname1' Sep 05 16:10:57 castor systemd[1]: Started Hostname Service. Sep 05 16:10:57 castor kernel: rfkill: input handler disabled Sep 05 16:11:27 castor systemd[1]: systemd-hostnamed.service: Deactivated successfully. Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Wacom.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Power.desktop Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in required component org.gnome.SettingsDaemon.MediaKeys.desktop Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Keyboard.desktop Sep 05 16:12:27 castor
[Desktop-packages] [Bug 1989128] Re: Reintroduce Ctrl+Shift+PrtScn key combination
I think it's still a valid enhancement since shortcuts are meant to provide shortcuts. We can keep it open while the upstream bug is open: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5447 -- 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/1989128 Title: Reintroduce Ctrl+Shift+PrtScn key combination Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: Since 22.04 Ctrl-Shift-Printscreen (copy selection of screen to clipboard) isn't working anymore To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1989128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970800] Re: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch
No it's not solved. It's still happening in 43.0-1ubuntu1 -- 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/1970800 Title: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: If you click a calendar date in the bottom row of the top panel calendar, the backdrop shrinks and the dates overflow out of the backdrop boundaries. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 28 16:25:17 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] CometLake-U GT2 [UHD Graphics] [1462:129c] Subsystem: Micro-Star International Co., Ltd. [MSI] TU117M [GeForce GTX 1650 Mobile / Max-Q] [1462:129c] InstallationDate: Installed on 2022-04-22 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2019 dmi.bios.release: 1.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16S3IMS.108 dmi.board.asset.tag: Default string dmi.board.name: MS-16S3 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16S3.1: dmi.product.family: Prestige dmi.product.name: Prestige 15 A10SC dmi.product.sku: 16S3.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/gnome-shell/+bug/1970800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990891] Re: after today's Kinetic updates, WiFi no longer working, so laptop basically useless
It looks like in today's Kinetic update iwd was removed, perhaps because of this bug? If so then the removal caused another problem: /etc/NetworkManager/conf.d/iwd.conf still existed after the iwd package was removed (I don't understand why, honestly), so even after I unmasked and re-enabled wpa_supplicant, NetworkManager still thought it was supposed to be using iwd instead. I had to delete iwd.conf by hand and restart NetworkManager to regain wifi connectivity. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1990891 Title: after today's Kinetic updates, WiFi no longer working, so laptop basically useless Status in network-manager package in Ubuntu: Confirmed Bug description: ThinkPad X1 Carbon 6th Gen WiFi was working fine. Installed today's batch of Kinetic updates. Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad USB dongle and plug into my router to be able to submit this bug report). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: network-manager 1.40.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 17:09:25 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-08-16 (1137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 100 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.40.0 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1990891/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991029] [NEW] network-manager-config-connectivity-ubuntu trying to restart "network-manager" service instead of "NetworkManager"?
Public bug reported: Setting up network-manager-config-connectivity-ubuntu (1.40.0-1ubuntu2) ... Failed to restart network-manager.service: Unit network-manager.service not found. invoke-rc.d: initscript network-manager, action "force-reload" failed. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: network-manager-config-connectivity-ubuntu 1.40.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 27 20:53:37 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-08-16 (1138 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.4.1 dev wlan0 proto dhcp src 192.168.4.21 metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/24 dev wlan0 proto kernel scope link src 192.168.4.21 metric 600 PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: network-manager UpgradeStatus: Upgraded to kinetic on 2022-09-24 (3 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.40.0 connected started full enabled enabled enabled missing enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1991029 Title: network-manager-config-connectivity-ubuntu trying to restart "network- manager" service instead of "NetworkManager"? Status in network-manager package in Ubuntu: New Bug description: Setting up network-manager-config-connectivity-ubuntu (1.40.0-1ubuntu2) ... Failed to restart network-manager.service: Unit network-manager.service not found. invoke-rc.d: initscript network-manager, action "force-reload" failed. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: network-manager-config-connectivity-ubuntu 1.40.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 27 20:53:37 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-08-16 (1138 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.4.1 dev wlan0 proto dhcp src 192.168.4.21 metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/24 dev wlan0 proto kernel scope link src 192.168.4.21 metric 600 PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: network-manager UpgradeStatus: Upgraded to kinetic on 2022-09-24 (3 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.40.0 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1991029/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist
Targeting this correctly. No clue why this was isn't being prioritized.
** Also affects: software-properties (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: software-properties (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: software-properties (Ubuntu Kinetic)
Importance: Undecided
Status: Triaged
** Changed in: software-properties (Ubuntu Jammy)
Status: New => Triaged
** Changed in: software-properties (Ubuntu Focal)
Status: New => Triaged
** Tags removed: bionic hirsute impish rls-hh-notfixing
** Tags added: jammy ubuntustudio
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/1795278
Title:
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
Status in software-properties package in Ubuntu:
Triaged
Status in software-properties source package in Focal:
Triaged
Status in software-properties source package in Jammy:
Triaged
Status in software-properties source package in Kinetic:
Triaged
Bug description:
Release: Kubuntu 18.04
Version: 0.96.24.32.1
When clicking the "Import Key" button in the "Authentication" section
of the panel it throws this error:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
line 667, in add_key_clicked
url = KUrl.fromPath(home)
NameError: name 'KUrl' is not defined
While this doesn't crash the program it causes nothing to happen when
clicking the button. Running the program in a terminal reveals the
error being printed to stderr.
After debugging it appears KUrl doesn't exist anywhere and I'm not
sure if's a python module that has changed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990841] Re: Local network share option disappeared
nautilus-share was updated in Debian and is in the NEW queue for Kinetic. It's going to be in universe so no longer installed by default. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/1990841 Title: Local network share option disappeared Status in nautilus-share package in Ubuntu: Confirmed Bug description: On Ubuntu 22.10 nautilus: 1:43.0-1ubuntu1 right click on a folder: the option 'Local network share' no longer appears ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 13:57:35 2022 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1545, 823)' InstallationDate: Installed on 2022-09-08 (18 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.1-2ubuntu1 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1990841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990677] Re: Update fonts-noto-color-emoji for Unicode 15
** Changed in: fonts-noto-color-emoji (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1990677 Title: Update fonts-noto-color-emoji for Unicode 15 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Jammy: In Progress Bug description: [Impact] Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the Show new link to see the new emoji. Click the changed link to see other changes that were made in this release. https://emojipedia.org/google/15.0/ [Test Plan] The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont [Where problems could occur] Sometimes there is an issue with the display of a particular font after the font has been updated. See Debian #788791 for instance. Perhaps this is a bug with font caching. To avoid this bug, it's recommended to restart your computer after applying the update. We are adding a postinst to tell Ubuntu's update-notifier to prompt the user to restart. This could technically be a User Interface Freeze change, but the new and changed emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. [Other] This bug is fixed in the current development release. Fix is released: https://bugs.launchpad.net/ubuntu/+source/fonts-noto- color-emoji/+bug/1989626 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1990677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983794] Re: Evolution not deleting autosave files
Is there some setting in Evolution for "Autosave"? And would disabling
it or setting to a longer interval negate some of this while we wait for
a fix?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Triaged
Bug description:
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991022] [NEW] Feature freeze exception: Socket activation
Public bug reported: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Rationale] It's relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it > inside of the sandbox, so that each application has its own "private" > instance of Speech Dispatcher running. This works more or less, but it has > the downside that speech dispatcher cannot coordinate simultaneous messages > from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the > same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps > access to the Speech Dispatcher instance of the host. And then, > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The change was already proposed upstream[2], but it is on hold because the build with undefined sanitizer CI failed two times out of four. In the words of the maintainer, > That's not systematic, but that's often enough that it'll be a pain in the CI, and is a sign of some subtle bug creeping in there. I then opened my own fork with debugging enabled[3] to track down the problem, but the CI succeeded all the six times I executed it[4], so at this point I'd assume it was a transient issue more than a subtle bug. I have built and installed the package in Kinetic and verified that spd- say still causes the dispatcher spawn and emits sound. Upstream test can also confirm this. [1]: https://github.com/brailcom/speechd/issues/335 [2]: https://github.com/brailcom/speechd/pull/763 [3]: https://github.com/brailcom/speechd/commit/a63a5f7fe187edd5bf60c12a9c8e078cd2234e73 [4]: https://github.com/nteodosio/speechd/actions/runs/3129483607 ** Affects: speech-dispatcher (Ubuntu) Importance: Undecided Status: New ** Tags: kinetic wip ** Attachment added: "speechd-sbuild-log" https://bugs.launchpad.net/bugs/1991022/+attachment/5619593/+files/speechd-sbuild-log ** Tags added: wip ** Tags added: kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: Feature freeze exception: Socket activation Status in speech-dispatcher package in Ubuntu: New Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Rationale] It's relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. And then, > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The change was already proposed upstream[2], but it is on hold because the build with undefined sanitizer CI failed two times out of four. In the words of the maintainer, > That's not systematic, but that's often enough that it'll be a pain in the CI, and is a sign of some subtle bug creeping in there. I then opened my own fork with debugging enabled[3] to track down the problem, but the CI succeeded all the six times I executed it[4], so at this point I'd assume it was a transient issue more than a subtle bug. I have built and installed the package in Kinetic and verified that spd-say still causes the dispatcher spawn and emits sound. Upstream test can also confirm this. [1]: https://github.com/brailcom/speechd/issues/335 [2]: https://github.com/brailcom/speechd/pull/763 [3]:
[Desktop-packages] [Bug 1781810] Re: Plank dock is not showing an indicator when a certain application is open anymore and when an application that is open is clicked on the dock, a new instance of it
I stopped seeing this problem a while ago - when I was on Mint 20.3 Cinnamon. I am now on Mint 21 Cinnamon and I have not seen it there either. This the present page shows that other DEs / distros are affected; and perhaps I've just been lucky in not encountering the problem recently. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1781810 Title: Plank dock is not showing an indicator when a certain application is open anymore and when an application that is open is clicked on the dock, a new instance of it is opened Status in BAMF: Expired Status in Plank: Expired Status in bamf package in Ubuntu: Expired Status in plank package in Ubuntu: Expired Bug description: Plank version: 0.11.4 Distribution: Ubuntu MATE 18.04 DE: MATE Desktop Window manager: Marco Video card: Intel HD Graphics 4000 Plank comes installed with the system by default When i used Ubuntu MATE 16.04 it didn't happen. I had an indicator that the application i was clicking on was open and when i clicked it, it would be restored if it was minimized and it will be minimized if it was maximized or just being shown on the screen but on this version, even if the application is minimized or maximized, when i click on its icon, first of all, i can't see that "application open" indicator below its icon anymore(Only below the Plank icon) and second of all, Plank will open a new instance of that same application. I recorded a video showing you what i am talking about. And also, sometimes when i click on the icons on the dock, i won't have that visual feedback, that "little jump" of the icon i click. That's very important as well otherwise, i think nothing happened. That's all. I really like Plank and it is a great application. Thanks for it. Best wishes To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1781810/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985089] Re: Resizing two edge tiled windows is laggy
There's already a merge request for this issue https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2579 Could we expect updated Mutter package with this patch? --- For now I've backported https://launchpad.net/ubuntu/+source/mutter/42.4-2ubuntu1 and applied patch on top of it. Temporal PPA - https://launchpad.net/~xalt7x/+archive/ubuntu/mutter-42.4-for-jammy. -- 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/1985089 Title: Resizing two edge tiled windows is laggy Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: Just to report an issue that other people have reported to GNOME and in Reddit, that seems to also affect Ubuntu 22.04. If you snap 2 windows side-by-side in Wayland and then try to resize them, it's very slow and uses a lot of memory. Check here for more details: - https://gitlab.gnome.org/GNOME/mutter/-/issues/2246 - https://old.reddit.com/r/gnome/comments/whjgel/resizing_two_tiled_windows_leaks_memory_and_is/ To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1985089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985089] Re: Resizing two edge tiled windows is laggy
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1985089 Title: Resizing two edge tiled windows is laggy Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: Just to report an issue that other people have reported to GNOME and in Reddit, that seems to also affect Ubuntu 22.04. If you snap 2 windows side-by-side in Wayland and then try to resize them, it's very slow and uses a lot of memory. Check here for more details: - https://gitlab.gnome.org/GNOME/mutter/-/issues/2246 - https://old.reddit.com/r/gnome/comments/whjgel/resizing_two_tiled_windows_leaks_memory_and_is/ To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1985089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1781810] Re: Plank dock is not showing an indicator when a certain application is open anymore and when an application that is open is clicked on the dock, a new instance of it
It's still persist on Ubuntu 22.04 Mate Desktop. It's annoying. I have to kill and launch plank from terminal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1781810 Title: Plank dock is not showing an indicator when a certain application is open anymore and when an application that is open is clicked on the dock, a new instance of it is opened Status in BAMF: Expired Status in Plank: Expired Status in bamf package in Ubuntu: Expired Status in plank package in Ubuntu: Expired Bug description: Plank version: 0.11.4 Distribution: Ubuntu MATE 18.04 DE: MATE Desktop Window manager: Marco Video card: Intel HD Graphics 4000 Plank comes installed with the system by default When i used Ubuntu MATE 16.04 it didn't happen. I had an indicator that the application i was clicking on was open and when i clicked it, it would be restored if it was minimized and it will be minimized if it was maximized or just being shown on the screen but on this version, even if the application is minimized or maximized, when i click on its icon, first of all, i can't see that "application open" indicator below its icon anymore(Only below the Plank icon) and second of all, Plank will open a new instance of that same application. I recorded a video showing you what i am talking about. And also, sometimes when i click on the icons on the dock, i won't have that visual feedback, that "little jump" of the icon i click. That's very important as well otherwise, i think nothing happened. That's all. I really like Plank and it is a great application. Thanks for it. Best wishes To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1781810/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969315] Re: text in torrent info tabs change after opening it to gibberish
Here is my wasteful "Me Too" post. I hope a fix is coming soon. I'm not capable, but would help if I could. constant crashing on 22.04 with gtk variant from mainline -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1969315 Title: text in torrent info tabs change after opening it to gibberish Status in transmission package in Ubuntu: Confirmed Bug description: on transmission-gtk after opening the torrent's properties panel, the text at first it's showing ok, buy on mouse hover it changes to random text worked fine on 21.10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: transmission-gtk 3.00-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 17 19:28:03 2022 SourcePackage: transmission UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988786] Re: system does not boot after full-upgrade on kinetic
** Attachment added: "gnome-boot-debug.logs" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1988786/+attachment/5619578/+files/gnome-boot-debug.logs ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1988786 Title: system does not boot after full-upgrade on kinetic Status in gdm3 package in Ubuntu: New Status in gnome-session package in Ubuntu: New Bug description: Hi, After a full upgrade on a kinetic system, the system no longer boots normally. When I power the computer on, I get a prompt to decrypt my disk. I insert the password, and am redirected to a screen saying a fschk is running. It spend hours in that screen with apparently no activity. Pressing ctrl+C does not help at that point. Booting through recovery mode and then requesting to proceed to boot works fine. A regular fschk also suceeds. Here is what I could extract from my journal: Sep 05 16:10:57 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Sep 05 16:10:57 castor gnome-session-binary[2000]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Sep 05 16:10:57 castor gnome-session-binary[2000]: Unrecoverable failure in required component org.gnome.Shell.desktop Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Activating service name='ca.desrt.dconf' requested by ':1.2' (uid=127 pid=2000 comm="/usr/libexec/gnome-session-binary --autostart /usr" label="unconfined") Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Successfully activated service 'ca.desrt.dconf' Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.54' (uid=127 pid=3239 comm="/usr/libexec/gsd-rfkill" label="unconfined") Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Activating service name='org.freedesktop.systemd1' requested by ':1.7' (uid=127 pid=3227 comm="/usr/libexec/gsd-sharing" label="unconfined") Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Sep 05 16:10:57 castor systemd[1]: Starting Hostname Service... Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Successfully activated service 'org.freedesktop.hostname1' Sep 05 16:10:57 castor systemd[1]: Started Hostname Service. Sep 05 16:10:57 castor kernel: rfkill: input handler disabled Sep 05 16:11:27 castor systemd[1]: systemd-hostnamed.service: Deactivated successfully. Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Wacom.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Power.desktop Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in required component org.gnome.SettingsDaemon.MediaKeys.desktop Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application
[Desktop-packages] [Bug 1988786] Re: system does not boot after full-upgrade on kinetic
I am attaching the boot logs with gdm and gnome-session debug modes on. I hope this helps. I am also targeting the bug to gdm3, since replacing it with lightdm does fix the issue for me. Finally, I tried reproducing the issue by performing a clean jammy installation and upgrading to kinetic. I could not reproduce the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1988786 Title: system does not boot after full-upgrade on kinetic Status in gdm3 package in Ubuntu: New Status in gnome-session package in Ubuntu: New Bug description: Hi, After a full upgrade on a kinetic system, the system no longer boots normally. When I power the computer on, I get a prompt to decrypt my disk. I insert the password, and am redirected to a screen saying a fschk is running. It spend hours in that screen with apparently no activity. Pressing ctrl+C does not help at that point. Booting through recovery mode and then requesting to proceed to boot works fine. A regular fschk also suceeds. Here is what I could extract from my journal: Sep 05 16:10:57 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Sep 05 16:10:57 castor gnome-session-binary[2000]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Sep 05 16:10:57 castor gnome-session-binary[2000]: Unrecoverable failure in required component org.gnome.Shell.desktop Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Activating service name='ca.desrt.dconf' requested by ':1.2' (uid=127 pid=2000 comm="/usr/libexec/gnome-session-binary --autostart /usr" label="unconfined") Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Successfully activated service 'ca.desrt.dconf' Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.54' (uid=127 pid=3239 comm="/usr/libexec/gsd-rfkill" label="unconfined") Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Activating service name='org.freedesktop.systemd1' requested by ':1.7' (uid=127 pid=3227 comm="/usr/libexec/gsd-sharing" label="unconfined") Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: dbus-daemon[1986]: [session uid=127 pid=1986] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Sep 05 16:10:57 castor systemd[1]: Starting Hostname Service... Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Successfully activated service 'org.freedesktop.hostname1' Sep 05 16:10:57 castor systemd[1]: Started Hostname Service. Sep 05 16:10:57 castor kernel: rfkill: input handler disabled Sep 05 16:11:27 castor systemd[1]: systemd-hostnamed.service: Deactivated successfully. Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.Wacom.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Power.desktop Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to register before timeout Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in required component org.gnome.SettingsDaemon.MediaKeys.desktop Sep 05 16:12:27
[Desktop-packages] [Bug 1989359] Re: [UIFe] Kinetic wallpapers updates
** Changed in: ubuntucinnamon-wallpapers (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1989359 Title: [UIFe] Kinetic wallpapers updates Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in ubuntu-unity-backgrounds package in Ubuntu: Fix Released Status in ubuntu-wallpapers package in Ubuntu: In Progress Status in ubuntucinnamon-wallpapers package in Ubuntu: Fix Released Status in ubuntustudio-default-settings package in Ubuntu: Fix Released Status in ubuntustudio-look package in Ubuntu: Fix Released Bug description: The Canonical design team isn't going to have the new default wallpapers ready by UIF but target end of September so we are requesting an exception to upload those once they are available. The community wallpapers are also going to be available after UIF since the competition was not organized early enough https://discourse.ubuntu.com/t/kinetic-kudu-22-10-wallpaper-competition The results will be published on Sep 23th so we ask for permission to refresh our package with the new content by the next monday (26th) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1989359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990673]
FWIW: I'm not a PS Style expert.. I'm not even sure if the below could be implemented at all (compatibility reasons). Only thinking out loud.. A) I surely grasp inconvenience mentioned in comment 30 comment 36. Where the order of actions has influence on the formatting. Terrible, IMHO B) Default Paragraph Style is actually "Master/Parent Paragraph Style" (like comment 5 points out). It's not a ordinary style, in principle it affects all other Paragraph Styles except if those other paragraphs explicitly define otherwise. Currently the 'Master/Parent Paragraph Style is set to be default too., C) There is the (taste) question: do you like the 'Text Body' formatting to be default.. comment 38 A way out would be to change Next Paragraph Style from headings and such to Default Paragraph Style instead of Text Body. However you likely into the issue at comment 22.. so no go If the current called Default Paragraph Style would be renamed Master Style or Parent Style. And a new Style introduced: a 'dummy' style: which would be an empty style.. so exact copy of Master Style or Parent Style (the current Default Paragraph Style), called yet Default Paragraph Style. And this style would be made default, instead of the Master Style: problem 22 would be gone. If you change Next Style to the 'future' Default Paragraph Style (instead of Text Body), the formatting difference would be gone as mentioned under A If you prefer different look you can modify the Default Paragraph Style (new), without affect all other styles. Sadly it's impossible to say: replace Default Paragraph Style (new) by say Text Body Style. Which would make it easy an existing PS style to something else of desire. Why would I manually configure the default Paragraph Style to match the specifications of Text Body. -- 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/1990673 Title: Default paragraph style should be "Text body" Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: New Bug description: Summary: when creating a new Writer document, the first paragraph has the style "Default Paragraph Style", which leads to surprising behaviour. This bug has been reported in upstream [1], but at least some devs seem to believe that this is a packaging issue [2] so it might make sense to be fixed in downstream. Ideally fixed in upstream as well. [1] https://bugs.documentfoundation.org/show_bug.cgi?id=47295 [2] even though this issue is seemingly present on all platforms To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1990673/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991015] [NEW] Reminna has unusable framerate when clipboard sync turned on
Public bug reported: On an intermittent basis, Remmina will, if clipboard sync is on, drop to an unusably low framerate after login to the remote machine. I have not managed to fully determine the conditions under which this occurs: it appears to happen or not happen consistently across a login session on the local machine (conditional upon clipboard sync being on), or possibly across a boot of the local machine. I have noticed it start occurring or stop occurring on reboots. When it occurs, it occurs for both remote machines I have set up (A Raspberry Pi 2 running Ubuntu Mate 18.04 and an x86 server running Debian Bullseye with LxQT). When it does not occur, it does not occur for either machine (this seems to include the case where clipboard sync has been turned off for one remote machine and not the other and the connections are open simultaneously, in which case the issue appears on neither!). The local machine is running Kubuntu 20.04, though some Mate components are also running on top of KDE. The connection is made via RDP, to xrdp v 0.6.x on the Raspberry Pi and xrdp 0.9.12 on the x86 server. All devices are in the same room, with gigabit ethernet connections. I have verified that I am getting gigabit bandwidth with iperf3, and ping latencies are sub-millisecond. Remmina is version 1.4.2+dfsg-1ubuntu1 ** Affects: remmina (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1991015 Title: Reminna has unusable framerate when clipboard sync turned on Status in remmina package in Ubuntu: New Bug description: On an intermittent basis, Remmina will, if clipboard sync is on, drop to an unusably low framerate after login to the remote machine. I have not managed to fully determine the conditions under which this occurs: it appears to happen or not happen consistently across a login session on the local machine (conditional upon clipboard sync being on), or possibly across a boot of the local machine. I have noticed it start occurring or stop occurring on reboots. When it occurs, it occurs for both remote machines I have set up (A Raspberry Pi 2 running Ubuntu Mate 18.04 and an x86 server running Debian Bullseye with LxQT). When it does not occur, it does not occur for either machine (this seems to include the case where clipboard sync has been turned off for one remote machine and not the other and the connections are open simultaneously, in which case the issue appears on neither!). The local machine is running Kubuntu 20.04, though some Mate components are also running on top of KDE. The connection is made via RDP, to xrdp v 0.6.x on the Raspberry Pi and xrdp 0.9.12 on the x86 server. All devices are in the same room, with gigabit ethernet connections. I have verified that I am getting gigabit bandwidth with iperf3, and ping latencies are sub-millisecond. Remmina is version 1.4.2+dfsg-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1991015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991001] Re: Gnome Zoom/Magnifier doesn't work after log-in
** Description changed: What I expect to happen: After booting up Ubuntu I'd like to be able to just enable desktop zoom using Alt+Super+8. What actually happens: - When I enable desktop zoom after logging in to Ubuntu, it doesn't work. Magnifier zooms in to the top-left portion of my desktop. The mouse pointer disappears and I can no longer move my view around. I can still disable zoom, so apparently it didn't crash. After I go to Settings->Accessibility and I change some zoom settings and change them back, zoom works fine. + When I enable desktop zoom after logging in to Ubuntu, it doesn't work. Magnifier zooms in to the top-left portion of my desktop. The mouse pointer disappears and I can no longer move my view around. I can still disable zoom, so apparently it didn't crash. After I go to Settings->Accessibility>Zoom, change some settings and enable zoom it works. When I change the settings back to my preferences it still works. After this the magnifier seems to work without further problems. + I'm experiencing this problem with both xorg and Wayland. Some general information: - My Magnifier settings: - Magnification: 2.00 - Magnifier position: - Screen part: full screen - Magnifier cursor pushes contents around - I used gsettings to set caret-tracking and focus-tracking to 'none' - Graphics card: NVidia GeForce GTX 970 - Graphics driver: Proprietary nvidia-driver-5.15 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.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: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 27 18:44:56 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1991001 Title: Gnome Zoom/Magnifier doesn't work after log-in Status in gnome-shell package in Ubuntu: New Bug description: What I expect to happen: After booting up Ubuntu I'd like to be able to just enable desktop zoom using Alt+Super+8. What actually happens: When I enable desktop zoom after logging in to Ubuntu, it doesn't work. Magnifier zooms in to the top-left portion of my desktop. The mouse pointer disappears and I can no longer move my view around. I can still disable zoom, so apparently it didn't crash. After I go to Settings->Accessibility>Zoom, change some settings and enable zoom it works. When I change the settings back to my preferences it still works. After this the magnifier seems to work without further problems. I'm experiencing this problem with both xorg and Wayland. Some general information: - My Magnifier settings: - Magnification: 2.00 - Magnifier position: - Screen part: full screen - Magnifier cursor pushes contents around - I used gsettings to set caret-tracking and focus-tracking to 'none' - Graphics card: NVidia GeForce GTX 970 - Graphics driver: Proprietary nvidia-driver-5.15 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.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: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 27 18:44:56 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 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/1991001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991008] Re: goa-daemon crashed with SIGABRT in g_assertion_message_expr()
*** This bug is a duplicate of bug 1990123 *** https://bugs.launchpad.net/bugs/1990123 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1990123, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1991008/+attachment/5619542/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1991008/+attachment/5619544/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1991008/+attachment/5619547/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1991008/+attachment/5619548/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1991008/+attachment/5619549/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1991008/+attachment/5619550/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1991008/+attachment/5619551/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1990123 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1991008 Title: goa-daemon crashed with SIGABRT in g_assertion_message_expr() Status in gnome-online-accounts package in Ubuntu: New Bug description: crashed after login to desktop ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.46.0-1 ProcVersionSignature: Ubuntu 5.19.0-17.17-generic 5.19.7 Uname: Linux 5.19.0-17-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Wed Sep 28 01:34:46 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2020-06-25 (823 days ago) InstallationMedia: JournalErrors: Error: command ['journalctl', '--priority=warning', '--since=@1664300076', '--until=@1664300096'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/libexec/goa-daemon Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () from /lib/x86_64-linux-gnu/librest-1.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (155 days ago) UserGroups: nordvpn sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1991008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991006] [NEW] gnome-screensaver locked pointer as a crosshair
Public bug reported: (i've seen it do this before but it only happens very rarely) what should happen: 1) run gnome-screenshot 2) it presents a little window of which kind of screenshot you want to take 3) select 'select area to grab' 4) the pointer is replaced by a crosshair and you can't click on anything except with that crosshair to select an area 5) after you are done selecting an area, the screenshot is taken and the cursor is returned to normal along with its functionality what happened instead: 5) the pointer got stuck in this crosshair (only on particular areas of the screen though, the dock(?) and a couple other windows like audacious. ironically ubuntu-bug got the pointer back into a pointer again but it still seems stuck and unable to click on icons such as the screenshot shortcut icon, changing the active window (unless you click in a text field), dragging windows around (alt-tab still works) DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" gnome-screenshot: Installed: 3.36.0-1ubuntu1 Candidate: 3.36.0-1ubuntu1 Version table: *** 3.36.0-1ubuntu1 500 500 http://muug.ca/mirror/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30 Uname: Linux 5.4.0-26-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 27 11:27:50 2022 InstallationDate: Installed on 2017-04-18 (1987 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to focal on 2020-04-25 (885 days ago) mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404 ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1991006 Title: gnome-screensaver locked pointer as a crosshair Status in gnome-screenshot package in Ubuntu: New Bug description: (i've seen it do this before but it only happens very rarely) what should happen: 1) run gnome-screenshot 2) it presents a little window of which kind of screenshot you want to take 3) select 'select area to grab' 4) the pointer is replaced by a crosshair and you can't click on anything except with that crosshair to select an area 5) after you are done selecting an area, the screenshot is taken and the cursor is returned to normal along with its functionality what happened instead: 5) the pointer got stuck in this crosshair (only on particular areas of the screen though, the dock(?) and a couple other windows like audacious. ironically ubuntu-bug got the pointer back into a pointer again but it still seems stuck and unable to click on icons such as the screenshot shortcut icon, changing the active window (unless you click in a text field), dragging windows around (alt-tab still works) DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" gnome-screenshot: Installed: 3.36.0-1ubuntu1 Candidate: 3.36.0-1ubuntu1 Version table: *** 3.36.0-1ubuntu1 500 500 http://muug.ca/mirror/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30 Uname: Linux 5.4.0-26-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 27 11:27:50 2022 InstallationDate: Installed on 2017-04-18 (1987 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to focal on 2020-04-25 (885 days ago) mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1991006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991008] [NEW] goa-daemon crashed with SIGABRT in g_assertion_message_expr()
*** This bug is a duplicate of bug 1990123 *** https://bugs.launchpad.net/bugs/1990123 Public bug reported: crashed after login to desktop ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.46.0-1 ProcVersionSignature: Ubuntu 5.19.0-17.17-generic 5.19.7 Uname: Linux 5.19.0-17-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Wed Sep 28 01:34:46 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2020-06-25 (823 days ago) InstallationMedia: JournalErrors: Error: command ['journalctl', '--priority=warning', '--since=@1664300076', '--until=@1664300096'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/libexec/goa-daemon Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () from /lib/x86_64-linux-gnu/librest-1.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (155 days ago) UserGroups: nordvpn sudo separator: ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash kinetic wayland-session ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1991008 Title: goa-daemon crashed with SIGABRT in g_assertion_message_expr() Status in gnome-online-accounts package in Ubuntu: New Bug description: crashed after login to desktop ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.46.0-1 ProcVersionSignature: Ubuntu 5.19.0-17.17-generic 5.19.7 Uname: Linux 5.19.0-17-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Wed Sep 28 01:34:46 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2020-06-25 (823 days ago) InstallationMedia: JournalErrors: Error: command ['journalctl', '--priority=warning', '--since=@1664300076', '--until=@1664300096'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/libexec/goa-daemon Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () from /lib/x86_64-linux-gnu/librest-1.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (155 days ago) UserGroups: nordvpn sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1991008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991004] Re: gjs-console crashed with SIGABRT in g_assertion_message_expr()
*** This bug is a duplicate of bug 1986455 *** https://bugs.launchpad.net/bugs/1986455 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1986455, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1991004/+attachment/5619509/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1991004/+attachment/5619511/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1991004/+attachment/5619515/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1991004/+attachment/5619516/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1991004/+attachment/5619517/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1991004/+attachment/5619518/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1991004/+attachment/5619519/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1986455 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1991004 Title: gjs-console crashed with SIGABRT in g_assertion_message_expr() Status in gjs package in Ubuntu: New Bug description: Used ArcMenu to find and open a LibreOffice Calc document. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gjs 1.74.0-1 ProcVersionSignature: Ubuntu 5.19.0-1003.3-lowlatency 5.19.0 Uname: Linux 5.19.0-1003-lowlatency x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 27 19:17:07 2022 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2022-08-13 (45 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220813) ProcCmdline: /usr/bin/gjs /usr/bin/gnome-characters --gapplication-service Signal: 6 SourcePackage: gjs StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 Title: gjs-console crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1991004/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990891] Re: after today's Kinetic updates, WiFi no longer working, so laptop basically useless
systemctl disable wpa_supplicant wasn't good enough. I had to mask it. Before I masked it, something started it on reboot even when it was disabled (I don't know what was starting it). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1990891 Title: after today's Kinetic updates, WiFi no longer working, so laptop basically useless Status in network-manager package in Ubuntu: Confirmed Bug description: ThinkPad X1 Carbon 6th Gen WiFi was working fine. Installed today's batch of Kinetic updates. Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad USB dongle and plug into my router to be able to submit this bug report). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: network-manager 1.40.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 17:09:25 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-08-16 (1137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 100 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.40.0 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1990891/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991001] [NEW] Gnome Zoom/Magnifier doesn't work after log-in
Public bug reported: What I expect to happen: After booting up Ubuntu I'd like to be able to just enable desktop zoom using Alt+Super+8. What actually happens: When I enable desktop zoom after logging in to Ubuntu, it doesn't work. Magnifier zooms in to the top-left portion of my desktop. The mouse pointer disappears and I can no longer move my view around. I can still disable zoom, so apparently it didn't crash. After I go to Settings->Accessibility and I change some zoom settings and change them back, zoom works fine. Some general information: - My Magnifier settings: - Magnification: 2.00 - Magnifier position: - Screen part: full screen - Magnifier cursor pushes contents around - I used gsettings to set caret-tracking and focus-tracking to 'none' - Graphics card: NVidia GeForce GTX 970 - Graphics driver: Proprietary nvidia-driver-5.15 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.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: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 27 18:44:56 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Description changed: What I expect to happen: After booting up Ubuntu I'd like to be able to just enable desktop zoom using Alt+Super+8. What actually happens: When I enable desktop zoom after logging in to Ubuntu, it doesn't work. Magnifier zooms in to the top-left portion of my desktop. The mouse pointer disappears and I can no longer move my view around. I can still disable zoom, so apparently it didn't crash. After I go to Settings->Accessibility and I change some zoom settings and change them back, zoom works fine. Some general information: - - Ubuntu version: Ubuntu 22.04.1 LTS - - gnome-shell version: 42.4-0ubuntu0.22.04.1 - My Magnifier settings: - - Magnification: 2.00 - - Magnifier position: - - Screen part: full screen - - Magnifier cursor pushes contents around - - I used gsettings to set caret-tracking and focus-tracking to 'none' + - Magnification: 2.00 + - Magnifier position: + - Screen part: full screen + - Magnifier cursor pushes contents around + - I used gsettings to set caret-tracking and focus-tracking to 'none' - Graphics card: NVidia GeForce GTX 970 - Graphics driver: Proprietary nvidia-driver-5.15 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.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: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 27 18:44:56 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1991001 Title: Gnome Zoom/Magnifier doesn't work after log-in Status in gnome-shell package in Ubuntu: New Bug description: What I expect to happen: After booting up Ubuntu I'd like to be able to just enable desktop zoom using Alt+Super+8. What actually happens: When I enable desktop zoom after logging in to Ubuntu, it doesn't work. Magnifier zooms in to the top-left portion of my desktop. The mouse pointer disappears and I can no longer move my view around. I can still disable zoom, so apparently it didn't crash. After I go to Settings->Accessibility and I change some zoom settings and change them back, zoom works fine. Some general information: - My Magnifier settings: - Magnification: 2.00 - Magnifier position: - Screen part: full screen - Magnifier cursor pushes contents around - I used gsettings to set caret-tracking and focus-tracking to 'none' - Graphics card: NVidia GeForce GTX 970 - Graphics driver: Proprietary nvidia-driver-5.15 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.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
[Desktop-packages] [Bug 1990998] Re: gnome-shell crashes on connection from gnome-remote-desktop in EXTEND mode
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1990998
Title:
gnome-shell crashes on connection from gnome-remote-desktop in EXTEND
mode
Status in gnome-shell package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
Hey all,
I've encountered a bug in libmutter that crashes GNOME Shell when connecting
via gnome-remote-desktop in EXTEND mode.
gnome-shell[1500]: **
gnome-shell[1500]:
libmutter:ERROR:../src/core/window.c:3730:meta_window_update_for_monitors_changed:
assertion failed: (!window->monitor || g_list_find
(meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor))
gnome-shell[1500]: Bail out!
libmutter:ERROR:../src/core/window.c:3730:meta_window_update_for_monitors_changed:
assertion failed: (!window->monitor || g_list_find
(meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor))
gnome-shell[1500]: GNOME Shell crashed with signal 6
This statistically crashes the GNOME session on connection from RDP.
This bug is addressed in
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2554
Steps to Reproduce:
1. Setup Ubuntu machine on low resolution (1280x960)
2. Setup gnome-remote-desktop to accept connections in 'extend' mode.
3. Connect from xfreerdp with /dynamic-resolution and /w:, /h: set to a
resolution much larger than your current monitor (For example 3840x2160 on a
1080p screen)
4. Open multiple windows, shift them around, maximize some.
5. Disconnect
6. Reconnect.
7. Session should crash, resulting in potential used data loss.
NOTE: I couldn't reliably reproduce the bug. Sometimes restarting and trying
again triggered it.
Setup:
lsb_release -a:
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy
apt-cache policy mutter:
mutter:
Installed: 42.2-0ubuntu1
Candidate: 42.2-0ubuntu1
Version table:
*** 42.2-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64
Packages
100 /var/lib/dpkg/status
42.0-3ubuntu2 500
500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
apt-cache policy gnome-shell:
gnome-shell:
Installed: 42.4-0ubuntu0.22.04.1
Candidate: 42.4-0ubuntu0.22.04.1
Version table:
*** 42.4-0ubuntu0.22.04.1 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
42.0-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
```
(gdb) bt full
#0 __pthread_kill_implementation (no_tid=0, signo=6,
threadid=139943778018752) at ./nptl/pthread_kill.c:44
tid =
ret = 0
pd = 0x7f47332d65c0
old_mask = {__val = {2048, 139943866772608, 2064, 129,
95, 139943865243713, 139943866772704, 0, 7, 139943865090602, 344544753768,
2048, 94006337625088, 5680105379855955242, 143, 2096}}
ret =
#1 __pthread_kill_internal (signo=6, threadid=139943778018752) at
./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=139943778018752, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
#3 0x7f47385a3476 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
ret =
#4 0x7f47385897f3 in __GI_abort () at ./stdlib/abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0xed,
sa_sigaction = 0xed}, sa_mask = {__val = {237, 94006402588640,
139943881008423, 94006314421680, 140725925571312, 32, 94006337054400,
0, 6907377910888285440, 1, 18446744073709551488, 61, 214,
140725925571408, 139943868561280, 139943868561280}}, sa_flags =
945841363, sa_restorer = 0x557f8e53a6c0}
sigs = {__val = {32, 139943866772608, 1322117968, 0,
139943868561280, 6907377910888285440, 94006310750208, 18446744073709551488, 61,
140725925571304, 237, 1, 94006337054400, 139943865246931, 94006337054400,
139943880987991}}
#5 0x7f47394b2b57 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6 0x7f473950c6ff in g_assertion_message_expr () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7 0x7f4738873856 in () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#8 0x7f4739505b10 in g_slist_foreach () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x7f473884b362 in () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#10 0x7f47395e2d2f in g_closure_invoke () at
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x7f47395feb76 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x7f4739600554 in g_signal_emit_valist () at
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x7f47396007a3 in g_signal_emit () at
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
[Desktop-packages] [Bug 1990444] Re: firefox snap took 20 minutes to update
** Changed in: snapd Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1990444 Title: firefox snap took 20 minutes to update Status in snapd: New Status in firefox package in Ubuntu: Invalid Bug description: I logged and firefox was unavailable, no indication of update, nothing. When I tried to launch firefox I was invited to install it BUT I klnow it's installed, so I tried to install it but it said to me I needed to 'snap refresh', I tried to snap refresh but it indicated that everything was up to date. I tried to uninstall/reinstall the firefox snap and at this moment, I got the indication that the update was in progress since 15 MINUTES ! Then I tried to remove the snap because I was sure it's bugged : in 20.04 firefox never took more than 2 mins to update and my machine BUT after 20 minutes firefox launched... wtf ? I'm an ubuntu user since circa 2005 and I believe firefox was already the default browser then, this is the worse user experience I've ever had. 1/ I never selected auto-update, let me update when I want : being blocked 15 MINUTES by the OS is not a good user experience, I know this is accepted by Windows users but I prefer to use Ubuntu 2/ If you want to update tell me you're updating not that the application is not installed : really not a good idea if you want your users to trust you I've waited 6 months after 22.04 release to migrate from 20.04 because I don't want to have this kind of bugs, I hope you do something really quick because this is not at the level of quality expected by your users. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1990444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990998] [NEW] gnome-shell crashes on connection from gnome-remote-desktop in EXTEND mode
Public bug reported:
Hey all,
I've encountered a bug in libmutter that crashes GNOME Shell when connecting
via gnome-remote-desktop in EXTEND mode.
gnome-shell[1500]: **
gnome-shell[1500]:
libmutter:ERROR:../src/core/window.c:3730:meta_window_update_for_monitors_changed:
assertion failed: (!window->monitor || g_list_find
(meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor))
gnome-shell[1500]: Bail out!
libmutter:ERROR:../src/core/window.c:3730:meta_window_update_for_monitors_changed:
assertion failed: (!window->monitor || g_list_find
(meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor))
gnome-shell[1500]: GNOME Shell crashed with signal 6
This statistically crashes the GNOME session on connection from RDP.
This bug is addressed in
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2554
Steps to Reproduce:
1. Setup Ubuntu machine on low resolution (1280x960)
2. Setup gnome-remote-desktop to accept connections in 'extend' mode.
3. Connect from xfreerdp with /dynamic-resolution and /w:, /h: set to a
resolution much larger than your current monitor (For example 3840x2160 on a
1080p screen)
4. Open multiple windows, shift them around, maximize some.
5. Disconnect
6. Reconnect.
7. Session should crash, resulting in potential used data loss.
NOTE: I couldn't reliably reproduce the bug. Sometimes restarting and trying
again triggered it.
Setup:
lsb_release -a:
Distributor ID: Ubuntu
Description:Ubuntu 22.04.1 LTS
Release:22.04
Codename: jammy
apt-cache policy mutter:
mutter:
Installed: 42.2-0ubuntu1
Candidate: 42.2-0ubuntu1
Version table:
*** 42.2-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64
Packages
100 /var/lib/dpkg/status
42.0-3ubuntu2 500
500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
apt-cache policy gnome-shell:
gnome-shell:
Installed: 42.4-0ubuntu0.22.04.1
Candidate: 42.4-0ubuntu0.22.04.1
Version table:
*** 42.4-0ubuntu0.22.04.1 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
42.0-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
```
(gdb) bt full
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139943778018752)
at ./nptl/pthread_kill.c:44
tid =
ret = 0
pd = 0x7f47332d65c0
old_mask = {__val = {2048, 139943866772608, 2064, 129, 95,
139943865243713, 139943866772704, 0, 7, 139943865090602, 344544753768, 2048,
94006337625088, 5680105379855955242, 143, 2096}}
ret =
#1 __pthread_kill_internal (signo=6, threadid=139943778018752) at
./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=139943778018752, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
#3 0x7f47385a3476 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
ret =
#4 0x7f47385897f3 in __GI_abort () at ./stdlib/abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0xed,
sa_sigaction = 0xed}, sa_mask = {__val = {237, 94006402588640,
139943881008423, 94006314421680, 140725925571312, 32, 94006337054400, 0,
6907377910888285440, 1, 18446744073709551488, 61, 214, 140725925571408,
139943868561280, 139943868561280}}, sa_flags = 945841363, sa_restorer =
0x557f8e53a6c0}
sigs = {__val = {32, 139943866772608, 1322117968, 0,
139943868561280, 6907377910888285440, 94006310750208, 18446744073709551488, 61,
140725925571304, 237, 1, 94006337054400, 139943865246931, 94006337054400,
139943880987991}}
#5 0x7f47394b2b57 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6 0x7f473950c6ff in g_assertion_message_expr () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7 0x7f4738873856 in () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#8 0x7f4739505b10 in g_slist_foreach () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x7f473884b362 in () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#10 0x7f47395e2d2f in g_closure_invoke () at
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x7f47395feb76 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x7f4739600554 in g_signal_emit_valist () at
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x7f47396007a3 in g_signal_emit () at
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x7f47388088d0 in () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#15 0x7f473880fead in meta_monitor_manager_rebuild () at
/lib/x86_64-linux-gnu/libmutter-10.so.0
#16 0x7f47388eb789 in () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#17 0x7f4738800bc0 in () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#18 0x7f47388060b7 in meta_monitor_manager_ensure_configured () at
/lib/x86_64-linux-gnu/libmutter-10.so.0
#19 0x7f47388a6f87 in () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#20 0x7f47388acdc7 in () at
[Desktop-packages] [Bug 1990444] Re: firefox snap took 20 minutes to update
Hi, the incident tooks place the 22 sept I guess it's the boot around 2h40, I tried to launch firefox seconds after booting. I can't retrieve the 'snap change ' because 'snap changes' only output this : ID Status SpawnReadySummary 18 Donetoday at 05:52 CEST today at 05:53 CEST Auto-refresh snap "snapd" I guess too much time have passed. You'll find the infos asked attached. ** Attachment added: "snap-debug-info.sh output" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1990444/+attachment/5619487/+files/debug_info.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1990444 Title: firefox snap took 20 minutes to update Status in snapd: Incomplete Status in firefox package in Ubuntu: Invalid Bug description: I logged and firefox was unavailable, no indication of update, nothing. When I tried to launch firefox I was invited to install it BUT I klnow it's installed, so I tried to install it but it said to me I needed to 'snap refresh', I tried to snap refresh but it indicated that everything was up to date. I tried to uninstall/reinstall the firefox snap and at this moment, I got the indication that the update was in progress since 15 MINUTES ! Then I tried to remove the snap because I was sure it's bugged : in 20.04 firefox never took more than 2 mins to update and my machine BUT after 20 minutes firefox launched... wtf ? I'm an ubuntu user since circa 2005 and I believe firefox was already the default browser then, this is the worse user experience I've ever had. 1/ I never selected auto-update, let me update when I want : being blocked 15 MINUTES by the OS is not a good user experience, I know this is accepted by Windows users but I prefer to use Ubuntu 2/ If you want to update tell me you're updating not that the application is not installed : really not a good idea if you want your users to trust you I've waited 6 months after 22.04 release to migrate from 20.04 because I don't want to have this kind of bugs, I hope you do something really quick because this is not at the level of quality expected by your users. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1990444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989359] Re: [UIFe] Kinetic wallpapers updates
I sponsored the upload of ubuntucinnamon-wallpapers, but the bug was not associated, so I'll just manually watch for the acceptance. ** Also affects: ubuntucinnamon-wallpapers (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntucinnamon-wallpapers (Ubuntu) Status: New => Fix Committed ** Changed in: ubuntucinnamon-wallpapers (Ubuntu) Importance: Undecided => High ** Changed in: ubuntucinnamon-wallpapers (Ubuntu) Milestone: None => ubuntu-22.10-beta ** Changed in: ubuntucinnamon-wallpapers (Ubuntu) Assignee: (unassigned) => Joshua Peisach (itzswirlz) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1989359 Title: [UIFe] Kinetic wallpapers updates Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in ubuntu-unity-backgrounds package in Ubuntu: Fix Released Status in ubuntu-wallpapers package in Ubuntu: In Progress Status in ubuntucinnamon-wallpapers package in Ubuntu: Fix Committed Status in ubuntustudio-default-settings package in Ubuntu: Fix Released Status in ubuntustudio-look package in Ubuntu: Fix Released Bug description: The Canonical design team isn't going to have the new default wallpapers ready by UIF but target end of September so we are requesting an exception to upload those once they are available. The community wallpapers are also going to be available after UIF since the competition was not organized early enough https://discourse.ubuntu.com/t/kinetic-kudu-22-10-wallpaper-competition The results will be published on Sep 23th so we ask for permission to refresh our package with the new content by the next monday (26th) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1989359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926256] Re: Pasted text in the terminal is always highlighted and selected
** Description changed: Steps to reproduce: 1. Have Ubuntu 21.04 installed 2. Launch terminal 3a. Execute some command, select this command to copy it, then paste command 3b. Paste some command from clipboard to terminal Expected result: * pasted command is not highlighted and is not selected Actual result: * pasted command is selected and highlighted + + [[Workaround]] + + * On 22.04, add 'set enable-bracketed-paste off' to /etc/inputrc + * Starting 22.10, add 'set enable-active-region off' to /etc/inputrc ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Apr 27 09:43:56 2021 InstallationDate: Installed on 2021-04-23 (3 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1926256 Title: Pasted text in the terminal is always highlighted and selected Status in bash package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in mate-terminal package in Ubuntu: Invalid Status in readline package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Have Ubuntu 21.04 installed 2. Launch terminal 3a. Execute some command, select this command to copy it, then paste command 3b. Paste some command from clipboard to terminal Expected result: * pasted command is not highlighted and is not selected Actual result: * pasted command is selected and highlighted [[Workaround]] * On 22.04, add 'set enable-bracketed-paste off' to /etc/inputrc * Starting 22.10, add 'set enable-active-region off' to /etc/inputrc ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Apr 27 09:43:56 2021 InstallationDate: Installed on 2021-04-23 (3 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1926256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990986] [NEW] With iwd, doesn't connect to WPA2 Enterprise network (e.g. eduroam)
Public bug reported: I believe my Kinetic system installed iwd with updates today, and now I am unable to my University's WPA2 Enterprise network eduroam. There is a no graphical error message, it just never connects. I tried forgetting the network and re-adding, and again there's no error, but no connection is established. Looking in the Logs app, I see messages like "Failed to add new connection: (5) 802.1x connections must have IWD provisioning files". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: iwd 1.30-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 27 09:32:38 2022 InstallationDate: Installed on 2022-08-25 (32 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220825) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: iwd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iwd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iwd in Ubuntu. https://bugs.launchpad.net/bugs/1990986 Title: With iwd, doesn't connect to WPA2 Enterprise network (e.g. eduroam) Status in iwd package in Ubuntu: New Bug description: I believe my Kinetic system installed iwd with updates today, and now I am unable to my University's WPA2 Enterprise network eduroam. There is a no graphical error message, it just never connects. I tried forgetting the network and re-adding, and again there's no error, but no connection is established. Looking in the Logs app, I see messages like "Failed to add new connection: (5) 802.1x connections must have IWD provisioning files". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: iwd 1.30-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 27 09:32:38 2022 InstallationDate: Installed on 2022-08-25 (32 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220825) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: iwd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/1990986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983794] Re: Evolution not deleting autosave files
Yeah, thanks I was aware of this and it was indeed my starting point.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Triaged
Bug description:
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983794] Test case from 1949200
I'm forwarding the program provided by
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/comments/26
as a useful minimal test case for the regression introduced by the
Libcanberra handle-display-closing patch.
** Attachment added: "test-gtk.c"
https://bugs.launchpad.net/bugs/1983794/+attachment/5619461/+files/test-gtk.c
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Triaged
Bug description:
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1979116] Re: no USB-key any more in the sidebar of the save-dialog
Thank you for reporting this bug to Ubuntu. Ubuntu 21.10 (impish) reached end-of-life on July 14, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. --- Sorry I missed comment/post #2, impish changed to jammy based on #2 ** Tags removed: impish ** Tags added: jammy -- 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/1979116 Title: no USB-key any more in the sidebar of the save-dialog Status in libreoffice package in Ubuntu: New Bug description: If I want to save a new document, then in the save-dialog there's no USB-key any more in the sidebar (so, on the left side), no matter if in the Options (in "LibreOffice" in "General") "Use LibreOffice dialogs" is checked or unchecked. But the USB-key still appears in the file-manager of the system. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.13.0-44.49-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Jun 18 12:05:53 2022 InstallationDate: Installed on 2022-02-06 (131 days ago) InstallationMedia: Lubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1979116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990886] Re: Security updates missing after 91.11.0
Yes, the update to thunderbird 102.2.2 is ready and awaiting validation and publication by the security team. ** Changed in: thunderbird (Ubuntu) Status: Confirmed => In Progress ** Changed in: thunderbird (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: thunderbird (Ubuntu) Importance: Undecided => High -- 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/1990886 Title: Security updates missing after 91.11.0 Status in thunderbird package in Ubuntu: In Progress Bug description: Upstream released Thunderbird 91.11.0 on June 28, 2022. It's now at 91.13.1 from September 19, 2022. The release notes say: "By popular demand, Thunderbird 91.13.1 contains important security updates that shipped in Thunderbird 102.2.1. Users are encouraged to update as soon as possible." Source: https://www.thunderbird.net/en-US/thunderbird/91.13.1/releasenotes/ Ubuntu 22.04 Jammy (but also the other supported LTS) still has Thunderbird 91.11.0 (1:91.11.0+build2-0ubuntu0.22.04.1) without the security fixes after 91.11.0. The package should be updated to 91.13.1. Given that it has been three months without security updates, there seems to be some general friction with following upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1990886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990904] Re: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
Relevant debug info from DpkgTerminalLog.txt: ==> Installing the firefox snap error: cannot perform the following tasks: - Run hook connect-plug-host-hunspell of snap "firefox" (run hook "connect-plug-host-hunspell": cannot perform operation: mount --bind /snap/core20/current/etc/nsswitch.conf /tmp/snap.rootfs_DkZnqA/etc/nsswitch.conf: Permission denied) I'm not sure what happened, but it looks like a problem with the core20 snap, not firefox. Can you try reinstalling, and let us know how it goes? sudo apt reinstall firefox ** Changed in: firefox (Ubuntu) Status: New => Incomplete ** Also affects: snapd Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1990904 Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in snapd: New Status in firefox package in Ubuntu: Incomplete Bug description: not sure ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 104.0+build3-0ubuntu0.20.04.1 Uname: Linux 4.9.312-125 aarch64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: odroid 3743 F pulseaudio alanm 5185 F pulseaudio BuildID: 20220818191623 CasperMD5CheckResult: unknown Channel: Unavailable Date: Mon Sep 26 19:41:24 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown IpRoute: default via 192.168.1.1 dev eth0 proto dhcp metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.43 metric 100 Lspci: NoProfiles: True PciNetwork: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-09-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1990904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970800] Re: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch
I noticed this problem some time ago but now the bug seems to have disappeared. The display of the calendar is done normally. -- 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/1970800 Title: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: If you click a calendar date in the bottom row of the top panel calendar, the backdrop shrinks and the dates overflow out of the backdrop boundaries. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 28 16:25:17 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] CometLake-U GT2 [UHD Graphics] [1462:129c] Subsystem: Micro-Star International Co., Ltd. [MSI] TU117M [GeForce GTX 1650 Mobile / Max-Q] [1462:129c] InstallationDate: Installed on 2022-04-22 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2019 dmi.bios.release: 1.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16S3IMS.108 dmi.board.asset.tag: Default string dmi.board.name: MS-16S3 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16S3.1: dmi.product.family: Prestige dmi.product.name: Prestige 15 A10SC dmi.product.sku: 16S3.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/gnome-shell/+bug/1970800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1979116] Re: no USB-key any more in the sidebar of the save-dialog
same problem in Lubuntu 22.04.1 -- 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/1979116 Title: no USB-key any more in the sidebar of the save-dialog Status in libreoffice package in Ubuntu: New Bug description: If I want to save a new document, then in the save-dialog there's no USB-key any more in the sidebar (so, on the left side), no matter if in the Options (in "LibreOffice" in "General") "Use LibreOffice dialogs" is checked or unchecked. But the USB-key still appears in the file-manager of the system. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.13.0-44.49-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Jun 18 12:05:53 2022 InstallationDate: Installed on 2022-02-06 (131 days ago) InstallationMedia: Lubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1979116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989128] Re: Reintroduce Ctrl+Shift+PrtScn key combination
just "print screen" works fine, see attached image. issue can be closed for me ** Attachment added: "screenshot shortcuts.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989128/+attachment/5619424/+files/screenshot%20shortcuts.png -- 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/1989128 Title: Reintroduce Ctrl+Shift+PrtScn key combination Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: Since 22.04 Ctrl-Shift-Printscreen (copy selection of screen to clipboard) isn't working anymore To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1989128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973358] Re: blinking app-indication area with Ubuntu 22.04
22.04 same -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1973358 Title: blinking app-indication area with Ubuntu 22.04 Status in gnome-shell-extension-appindicator package in Ubuntu: New Status in indicator-multiload package in Ubuntu: Confirmed Bug description: After updating 21.10 to 22.04 the app-indicator starts "blinking" as if the positions of the indicators constantly have to be redrawn. Hovering the mouse over the multiload indicator shows a menu that is constantly changing size and position. Closing the app removes the indicator and the indicator area stays calm again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1973358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990877] Re: Ubuntu 22.04 crash when I connect an external monitor with different refresh (Hz)
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: amdgpu multimonitor ** Package changed: wayland (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1990877 Title: Ubuntu 22.04 crash when I connect an external monitor with different refresh (Hz) Status in Ubuntu: Incomplete Bug description: When I connect from my laptop an external monitor with different refresh, instantly crash the session and get me back to the gdm. After connect the monitor from the restart the session, I can use it without any issues, but if I disconnect it and I connect it again, the session crash again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 19:57:38 2022 DistUpgraded: 2022-04-03 23:19:05,278 INFO cache.commit() DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.2.0: added ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1462:12ce] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Renoir [1462:12ce] InstallationDate: Installed on 2021-05-24 (489 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Micro-Star International Co., Ltd. Alpha 17 A4DEK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=d028c740-1e9e-4c72-a093-c9bef7123709 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to jammy on 2022-04-03 (175 days ago) dmi.bios.date: 10/26/2020 dmi.bios.release: 1.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17EKAMS.101 dmi.board.asset.tag: Default string dmi.board.name: MS-17EK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1: dmi.product.family: Al dmi.product.name: Alpha 17 A4DEK dmi.product.sku: 17EK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1990877/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990890] Re: Laptop display stays blank after resume
*** This bug is a duplicate of bug 1968040 *** https://bugs.launchpad.net/bugs/1968040 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1968040, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1968040 Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] -- 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/1990890 Title: Laptop display stays blank after resume Status in gnome-shell package in Ubuntu: New Bug description: Changing its display settings (e.g. refresh rate) gets it back. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 22:56:41 2022 DisplayManager: gdm3 InstallationDate: Installed on 2017-07-09 (1905 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-08-16 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990757] Re: Video 8K is lag
Thanks for the bug report. 1. Please ensure the correct driver is installed: sudo apt install intel-media-va-driver-non-free vainfo 2. Verify the driver is working by running 'vainfo'. 3. If the problem persists then tell us what app you are using to play video. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: hybrid i915 multigpu nvidia -- 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/1990757 Title: Video 8K is lag Status in Ubuntu: Incomplete Bug description: I'm turn on nvidia gpu and intel uhd graphic for running dual igpu and gpu. When watching video 8k on windows is very smoothy but vise versa on ubuntu. I don't know what make this difference from window and ubuntu ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.141.03 Thu Jun 30 18:45:31 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Sep 25 16:00:10 2022 DistUpgraded: 2022-09-14 19:12:50,793 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.141.03, 5.15.0-47-generic, x86_64: installed nvidia/470.141.03, 5.15.0-48-generic, x86_64: installed GraphicsCard: Intel Corporation Device [8086:4682] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] NVIDIA Corporation TU106 [GeForce RTX 2060 12GB] [10de:1f03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:886e] InstallationDate: Installed on 2022-09-06 (18 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=8fc46e98-c732-4255-b94b-20b8cd736a37 ro intel_iommu=on,igfx_off quiet splash amdgpu.exp_hw_support=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-09-14 (10 days ago) dmi.bios.date: 09/29/2021 dmi.bios.release: 4.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PRIME B660M-A D4 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.:bvr0405:bd09/29/2021:br4.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB660M-AD4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1990757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990767] Re: No Local Variables are initialized for Method [RUCC]
** Summary changed: - Drivers error + No Local Variables are initialized for Method [RUCC] ** Package changed: xorg (Ubuntu) => linux (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/1990767 Title: No Local Variables are initialized for Method [RUCC] Status in linux package in Ubuntu: Confirmed Bug description: I have a fresh install of Ubuntu 22.04 on my new laptop. Laptop: MSI Summit E16 flip Evo MFG: 2022/01 When my laptop boots up, I see the following errors on the display: [ 26.677123] kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.CR03._PLD], AE_NOT_FOUND (20210730/psargs-330) [ 26.677133] kernel: [ 26.677134] kernel: No Local Variables are initialized for Method [RUCC] [ 26.677135] kernel: [ 26.677136] kernel: Initialized Arguments for Method [RUCC]: (2 arguments defined for method invocation) [ 26.677137] kernel: Arg0: 57d68be0Integer 0003 [ 26.677142] kernel: Arg1: 6ae5efd8Integer 0002 [ 26.677145] kernel: [ 26.677147] kernel: ACPI Error: Aborting method \_SB.UBTC.RUCC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 26.677152] kernel: ACPI Error: Aborting method \_SB.PC00.TXHC.RHUB.SS03._PLD due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 26.677198] kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.CR04._PLD], AE_NOT_FOUND (20210730/psargs-330) [ 26.677203] kernel: [ 26.677204] kernel: No Local Variables are initialized for Method [RUCC] [ 26.677204] kernel: [ 26.677205] kernel: Initialized Arguments for Method [RUCC]: (2 arguments defined for method invocation) [ 26.677206] kernel: Arg0: 6ae5efd8Integer 0004 [ 26.677209] kernel: Arg1: c5813084Integer 0002 [ 26.677213] kernel: [ 26.677214] kernel: ACPI Error: Aborting method \_SB.UBTC.RUCC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 26.677219] kernel: ACPI Error: Aborting method \_SB.PC00.TXHC.RHUB.SS04._PLD due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [ 26.690809] kernel: sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:0:0-b678a [ 26.690813] kernel: sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:20:0 Kernel ABI 3:18:0 [ 26.690814] kernel: sof-audio-pci-intel-tgl :00:1f.3: warn: FW ABI is more recent than kernel [ 26.699117] kernel: sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:20:0 Kernel ABI 3:18:0 [ 26.699122] kernel: sof-audio-pci-intel-tgl :00:1f.3: warn: topology ABI is more recent than kernel [ 26.731884] kernel: hid-sensor-hub 001F:8087:0AC2.0007: hid_field_extract() called with n (192) > 32! (kworker/6:0) [ 26.734344] kernel: sof-audio-pci-intel-tgl :00:1f.3: ASoC: Parent card not yet available, widget card binding deferred [ 26.766928] kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC285: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [ 26.766933] kernel: snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 26.766934] kernel: snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 26.766936] kernel: snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 [ 26.766937] kernel: snd_hda_codec_realtek ehdaudio0D0:inputs: [ 26.766938] kernel: snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 [ 27.301459] kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.ETMD], AE_NOT_FOUND (20210730/psargs-330) [ 27.301469] kernel: [ 27.301470] kernel: No Local Variables are initialized for Method [_OSC] [ 27.301471] kernel: [ 27.301472] kernel: Initialized Arguments for Method [_OSC]: (4 arguments defined for method invocation) [ 27.301473] kernel: Arg0: 322401caBuffer(16) 5D A8 3B B2 B7 C8 42 35 [ 27.301482] kernel: Arg1: d63d1c67Integer 0001 [ 27.301485] kernel: Arg2: c7663632Integer 0002 [ 27.301489] kernel: Arg3: d2f230a3Buffer(8) 00 00 00 00 05 00 00 00 [ 27.301495] kernel: [ 27.301497] kernel: ACPI Error: Aborting method \_SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Sep 25 14:19:01 2022 DistUpgraded: Fresh install
[Desktop-packages] [Bug 1990861] Re: can no longer click on speaker icon in system tray menu to mute/unmute
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged -- 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/1990861 Title: can no longer click on speaker icon in system tray menu to mute/unmute Status in gnome-shell package in Ubuntu: Triaged Bug description: In Jammy, if I opened the system menu (click on system tray in top right corner of screen) and clicked the little speaker icon it would mute my audio, and then if I clicked again it would unmute. That icon is no longer clickable in Kinetic. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 11:39:09 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (1136 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 43.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-09-24 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989128] Re: Reintroduce Ctrl+Shift+PrtScn key combination
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1989128 Title: Reintroduce Ctrl+Shift+PrtScn key combination Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: Since 22.04 Ctrl-Shift-Printscreen (copy selection of screen to clipboard) isn't working anymore To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1989128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973570] Re: totem crashed with SIGSEGV in ___pthread_mutex_destroy() from g_rec_mutex_impl_free() from g_rec_mutex_clear() from gst_video_decoder_finalize() from g_object_unre
** Tags added: kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1973570 Title: totem crashed with SIGSEGV in ___pthread_mutex_destroy() from g_rec_mutex_impl_free() from g_rec_mutex_clear() from gst_video_decoder_finalize() from g_object_unref() Status in totem package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding totem. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/530e0bcdbf4a5adc3bdfa7a7759335f3b97388ce contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1973570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990563] Re: Some maximized windows appear on both monitors
** Changed in: mutter Status: Unknown => Fix Released -- 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/1990563 Title: Some maximized windows appear on both monitors Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: I have a dual monitor setup, with external monitor configured as primary. When I maximize certain windows on the secondary monitor, a copy of the same window appears on the primary monitor (see first attached video). It happens with some apps, not with all of them. For example, it happens with IntelliJ IDEA (Java app) and Spotify (presumably Electron app), not with Gnome Text Editor, Gnome Terminal, Chrome or Firefox, for instance. A very similar situation occurs when taking a screenshot with Flameshot, though in the opposite way: a copy of the primary monitor appears on the secondary (see second attached video). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: mutter 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Sep 22 14:37:37 2022 InstallationDate: Installed on 2018-12-14 (1378 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: mutter UpgradeStatus: Upgraded to kinetic on 2022-09-02 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1990563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990742] Re: screen not consistently locking when lid is closed
It looks like allowlockedremotedesk...@kamens.us may be to blame here. To be sure, please delete all local extensions: cd ~/.local/share/gnome-shell rm -rf extensions and then log in again. ** Information type changed from Public to Public Security ** Package changed: gnome-shell (Ubuntu) => ubuntu ** Changed in: 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/1990742 Title: screen not consistently locking when lid is closed Status in Ubuntu: Incomplete Bug description: I have GNOME configured to lock the screen when the screen is blanked, and to blank the screen when the lid is closed: org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank' org.gnome.desktop.screensaver lock-delay uint32 0 org.gnome.desktop.screensaver lock-enabled true This worked fine in Jammy: whenever my screen was unlocked and I closed my laptop lid, it locked immediately, i.e., if I immediately reopened my lid, the screen was locked. After having just upgraded to Kinetic, however, sometimes when I close the lid it locks as described above, and sometimes it just... doesn't, i.e., when I open the lid again the screen is unlocked and I can just keep working. I have been unable to determine what the factors are which control whether the screen locks when I close the lid. There is a moderate security implication here, as it's problematic for someone's screen not to lock when they think that it did. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 17:57:37 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (1135 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 43.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1990742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990444] Re: firefox snap took 20 minutes to update
Hi. Thank you for opening a bug report. I'm not sure that the store outage could prevent a snap from being used for 20 minutes since the snap remains available during the part of the update that fetches snaps and assertions from the store. The snap only becomes unavailable later when it's absolutely necessary. In order to help us understand what happened, could you run this script https://github.com/snapcore/snapd/blob/master/debug-tools/snap-debug- info.sh and share the output with us? Also if you could run `snap changes` to see the latest changes, identify the change corresponding to the slow firefox update and then run `snap change ` with that update's ID, that might give us an idea of what happened. Thank you for your help. ** Changed in: snapd Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1990444 Title: firefox snap took 20 minutes to update Status in snapd: Incomplete Status in firefox package in Ubuntu: Invalid Bug description: I logged and firefox was unavailable, no indication of update, nothing. When I tried to launch firefox I was invited to install it BUT I klnow it's installed, so I tried to install it but it said to me I needed to 'snap refresh', I tried to snap refresh but it indicated that everything was up to date. I tried to uninstall/reinstall the firefox snap and at this moment, I got the indication that the update was in progress since 15 MINUTES ! Then I tried to remove the snap because I was sure it's bugged : in 20.04 firefox never took more than 2 mins to update and my machine BUT after 20 minutes firefox launched... wtf ? I'm an ubuntu user since circa 2005 and I believe firefox was already the default browser then, this is the worse user experience I've ever had. 1/ I never selected auto-update, let me update when I want : being blocked 15 MINUTES by the OS is not a good user experience, I know this is accepted by Windows users but I prefer to use Ubuntu 2/ If you want to update tell me you're updating not that the application is not installed : really not a good idea if you want your users to trust you I've waited 6 months after 22.04 release to migrate from 20.04 because I don't want to have this kind of bugs, I hope you do something really quick because this is not at the level of quality expected by your users. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1990444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990736] Re: Xorg crash
Thanks for the bug report. This looks like it might be a kernel driver bug. Please open the Additional Drivers app and use it to install an official Nvidia driver, then reboot. If the crash persists after installing the official Nvidia driver then please follow: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Xorg crash + Crash -- 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/1990736 Title: Crash Status in Ubuntu: Incomplete Bug description: J'ai des crash répétitif depuis longtemps. Et parfois l'écran se fige je ne peux plus rien faire. J'ai déjà réinstallé 3 x. Impossible de trouver le problème. Merci beaucoup. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 22:02:01 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK107 [GeForce GTX 650] [3842:2650] InstallationDate: Installed on 2022-09-08 (16 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=fr_CH:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=30b5da29-5676-4f0b-bf23-d79eef14a3c5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1990736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950054] Re: files app loses orange dot in dock when usb drive is selected
Ubuntu 21.10 is no longer supported. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Won't Fix -- 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/1950054 Title: files app loses orange dot in dock when usb drive is selected Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Bug description: When I use a flash drive and select it in files app, the orange 'running' dot in dock for 'pinned' files app vanishes - it returns if you select Documents or Downloads a few times. Also, flash drives do not auto-mount, even though 'gsettings get org.gnome.desktop.media- handling automount' is set to true. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 17:38:10 2021 InstallationDate: Installed on 2021-05-01 (189 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to impish on 2021-11-02 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1950054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990719] Re: After switching the workspace, the taskbar icon of nautilus displays abnormally
Sounds related to bug 1960541. -- 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/1990719 Title: After switching the workspace, the taskbar icon of nautilus displays abnormally Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: After switches the workspace, the taskbar icon of nautilus displays abnormally. 1. The number of windows(the number of the orange dots) of nautilus is incorrect. 2. After left clicking on the icon, nothing happened. 3. After clicking middle mouse button on the icon, all the things will be OK. 4. After closing a window of nautilus, the icon in other workspaces is incorrect. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470.1 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 16:16:16 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" LiveMediaBuild: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1990719/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960541] Re: Apps in the dock lose the dot underneath them. I have many windows of VS Code open for example, and it doesn't show in the bottom dock anymore
Also sounds related to bug 1944065 -- 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/1960541 Title: Apps in the dock lose the dot underneath them. I have many windows of VS Code open for example, and it doesn't show in the bottom dock anymore Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Apps in the dock lose the dot underneath them. I have many windows of VS Code open for example, and it doesn't show in the bottom dock anymore ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 10 14:01:35 2022 InstallationDate: Installed on 2020-08-10 (549 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990563] Re: Some maximized windows appear on both monitors
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2387 https://gitlab.gnome.org/GNOME/mutter/-/issues/2387 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2387 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Status: New => Fix Committed ** Tags added: fixed-in-43.1 fixed-upstream ** Tags added: multimonitor -- 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/1990563 Title: Some maximized windows appear on both monitors Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Bug description: I have a dual monitor setup, with external monitor configured as primary. When I maximize certain windows on the secondary monitor, a copy of the same window appears on the primary monitor (see first attached video). It happens with some apps, not with all of them. For example, it happens with IntelliJ IDEA (Java app) and Spotify (presumably Electron app), not with Gnome Text Editor, Gnome Terminal, Chrome or Firefox, for instance. A very similar situation occurs when taking a screenshot with Flameshot, though in the opposite way: a copy of the primary monitor appears on the secondary (see second attached video). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: mutter 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Sep 22 14:37:37 2022 InstallationDate: Installed on 2018-12-14 (1378 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: mutter UpgradeStatus: Upgraded to kinetic on 2022-09-02 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1990563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1208084] Re: totem assert failure: totem: vm.c:1167: play_Cell: Asserção `0' falhou.
Safe to say Ubuntu 13.10 is no longer supported. ** Changed in: totem (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1208084 Title: totem assert failure: totem: vm.c:1167: play_Cell: Asserção `0' falhou. Status in totem package in Ubuntu: Won't Fix Bug description: crash when I tried to open an iso file ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: totem 3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.12-0ubuntu2 Architecture: amd64 AssertionMessage: totem: vm.c:1167: play_Cell: Asserção `0' falhou. Date: Sat Aug 3 21:49:01 2013 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2013-08-01 (2 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130801) MarkForUpload: True ProcCmdline: totem Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7f061c7bd89f , assertion=assertion@entry=0x7f05f02905bf "0", file=file@entry=0x7f05f0290560 "vm.c", line=line@entry=1167, function=function@entry=0x7f05f0290720 "play_Cell") at assert.c:92 __GI___assert_fail (assertion=0x7f05f02905bf "0", file=0x7f05f0290560 "vm.c", line=1167, function=0x7f05f0290720 "play_Cell") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libdvdnav.so.4 ?? () from /usr/lib/x86_64-linux-gnu/libdvdnav.so.4 ?? () from /usr/lib/x86_64-linux-gnu/libdvdnav.so.4 Title: totem assert failure: totem: vm.c:1167: play_Cell: Asserção `0' falhou. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio bluetooth cdrom clamav daemon dip firebird fuse libuuid lp lpadmin plugdev pulse sambashare ssh sudo tty users utempter utmp uucp vboxusers video voice www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1208084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990397] Re: Screen goes blank after a few seconds of inactivity
What output do you get from: gsettings list-recursively | grep delay ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: nvidia -- 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/1990397 Title: Screen goes blank after a few seconds of inactivity Status in Ubuntu: Incomplete Bug description: Despite "Never" being selected in the "Screen Blank" section of the "Power" pane of gnome settings. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-1ubuntu1) ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 21 10:16:49 2022 DistUpgraded: 2022-08-02 22:49:48,677 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: nvidia/515.65.01, 5.15.0-43-generic, x86_64: installed nvidia/515.65.01, 5.19.0-15-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [10de:249c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [17aa:22e4] InstallationDate: Installed on 2022-05-05 (138 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20Y5CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-08-03 (49 days ago) dmi.bios.date: 08/26/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N40ET37W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y5CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrN40ET37W(1.19):bd08/26/2022:br1.19:efr1.16:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i: dmi.product.family: ThinkPad X1 Extreme Gen 4i dmi.product.name: 20Y5CTO1WW dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i dmi.product.version: ThinkPad X1 Extreme Gen 4i dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.112-3ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.1.7-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.1.7-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1990397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989744] Re: KB/Mouse use causing short system freezes. Happens after resume
Sounds like the problem might be GNOME garbage collection, in which case I need to get back to https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2377 The problem might also be specific to the Nvidia driver. Are you able to try disabling the discrete GPU in the BIOS? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1989744 Title: KB/Mouse use causing short system freezes. Happens after resume Status in xorg-server package in Ubuntu: Incomplete Bug description: Summary: My laptop gets into a an odd state after resuming from sleep where, depending on user activity, the entire system freezes every 20 seconds for about 1/2 second. This does not happen after every resume. After upgrading to 22.04 was much less frequent than it was with 21.10. It seems that after some recent update it is happening more frequently again. Maybe one every 4 suspend/resume cycles. Normal operation can be restored by rebooting or sometimes suspending and waking. The triggering event is complex: * The pointer or pointer and keyboard must be actively used * Just typing with no mouse use will not cause it to happen. * Just moving the mouse pointer around but keeping it inside the same GUI element(a textarea for example) will not cause it * Typing for more than 20 seconds and then moving the mouse one pixel will cause it. * Moving the mouse around constantly for over 20 seconds will cause it to happen only if: a key on the keyboard was hit OR the pointer moved over a new GUI element(window border, button, even frames in a web page) * It is not application specific. The following is usually logged(not always though) when the freeze happens: ==> ~/.local/share/xorg/Xorg.1.log <== [1214998.964] (II) event5 - TPPS/2 Elan TrackPoint: SYN_DROPPED event - some input events have been lost. ==> /var/log/syslog <== Sep 15 08:23:51 krug /usr/libexec/gdm-x-session[3264]: (II) event5 - TPPS/2 Elan TrackPoint: SYN_DROPPED event - some input events have been lost. Sep 15 08:50:34 krug /usr/libexec/gdm-x-session[3264]: (II) event5 - TPPS/2 Elan TrackPoint: SYN_DROPPED event - some input events have been lost. Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer event4 trackpoint: scheduled expiry is in the past (-317ms), your system is too slow Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer event4 trackpoint: scheduled expiry is in the past (-301ms), your system is too slow Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer event4 trackpoint: scheduled expiry is in the past (-288ms), your system is too slow Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer event4 trackpoint: scheduled expiry is in the past (-278ms), your system is too slow Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) WARNING: log rate limit exceeded (5 msgs per 360ms). Discarding future messages. System Information: Lenovo Thinkpad P15 Model: 20YQ-003WUS OS: Ubuntu 22.04.1 LTS Kernel: 5.15.0-46-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-core 2:21.1.3-2ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 15 10:13:26 2022 DistUpgraded: 2022-06-30 16:37:37,968 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.34, 5.15.0-43-generic, x86_64: installed virtualbox/6.1.34, 5.15.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-H GT1 [UHD Graphics] [17aa:22d8] NVIDIA Corporation GA107GLM [RTX A2000 Mobile] [10de:25b8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA107GLM [RTX A2000 Mobile] [17aa:22d8] InstallationDate: Installed on 2022-03-03 (195 days ago) InstallationMedia: Ubuntu 20.04.4
[Desktop-packages] [Bug 1878247] Re: CTRL-Shift-PrntScreen screenshots sometimes don't work
Please advise if you experience any similar problems in Ubuntu 22.04 or later. ** No longer affects: mutter (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => 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/1878247 Title: CTRL-Shift-PrntScreen screenshots sometimes don't work Status in gnome-shell package in Ubuntu: Incomplete Bug description: Im not sure what exactly happens, but it seems like the print screen function does not work. I'll press ctrl-shift-prntscrn and it creates the pointer to select region, then nothing actually gets captured. If I just press print screen, then it takes a whole desktop screen shot and then after that it will let me screenshot an area. Ive had this happen a few times now. Anyway, I figured Id report it. I know its not really enough to go on, but I wanted to report that its happening. Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 12 12:22:59 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-28-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP104 [GeForce GTX 1070 Ti] [19da:2445] InstallationDate: Installed on 2020-04-24 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6b3bc0f9-1ec0-49ae-9a4f-972d83e14ce4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.00 dmi.board.name: Z390 Phantom Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.00:bd03/15/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878247/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989128] Re: ctrl shift printscreen not working
> Since 22.04 Ctrl-Shift-Printscreen (copy selection of screen to > clipboard) isn't working anymore It changed to just PrtScn in GNOME 42. So whether or not the old key combination should still work is a matter of opinion. Already reported upstream in https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5447 ** Tags added: jammy ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5447 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5447 ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Opinion ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5447 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: Opinion => Triaged ** Summary changed: - ctrl shift printscreen not working + Reintroduce Ctrl+Shift+PrtScn key combination -- 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/1989128 Title: Reintroduce Ctrl+Shift+PrtScn key combination Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Since 22.04 Ctrl-Shift-Printscreen (copy selection of screen to clipboard) isn't working anymore To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1989128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970800] Re: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch
No it's not solved. It's still happening in 43.0-1ubuntu1 ** Tags added: kinetic -- 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/1970800 Title: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: If you click a calendar date in the bottom row of the top panel calendar, the backdrop shrinks and the dates overflow out of the backdrop boundaries. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 28 16:25:17 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] CometLake-U GT2 [UHD Graphics] [1462:129c] Subsystem: Micro-Star International Co., Ltd. [MSI] TU117M [GeForce GTX 1650 Mobile / Max-Q] [1462:129c] InstallationDate: Installed on 2022-04-22 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2019 dmi.bios.release: 1.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16S3IMS.108 dmi.board.asset.tag: Default string dmi.board.name: MS-16S3 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16S3.1: dmi.product.family: Prestige dmi.product.name: Prestige 15 A10SC dmi.product.sku: 16S3.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/gnome-shell/+bug/1970800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Tags added: originate-from-1983068
--
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/1990089
Title:
Screen freeze when performing memory stress in Wayland mode
Status in Linux:
New
Status in Mutter:
Fix Released
Status in OEM Priority Project:
Incomplete
Status in linux package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Opinion
Bug description:
[Steps to reproduce]
(disable systemd-oomd or executing over ssh)
(below command allocates a lot of memory to stress kernel page fault)
1. stress-ng --stack 0 --timeout 300
2. check the screen
[Expected result]
Screen will update slowly when performing the stress-test.
but screen needs back to work after stress.
[Actual result]
Screen freeze after stress test.
[Additional information]
kernel version: vmlinuz-5.17.0-1017-oem
kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
Mesa version: 22.0.5-0ubuntu0.1
Mutter version: 42.2-0ubuntu1
Gnome-shell version: 42.2-0ubuntu0.2
* Issue happens in Wayland only
* gnome-shell keeps issuing ioctl()
```
(gdb) bt
#0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at
../sysdeps/unix/sysv/linux/ioctl.c:36
#1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80,
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
#2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=,
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
#3 iris_wait_syncobj (bufmgr=, syncobj=,
timeout_nsec=timeout_nsec@entry=9223372036854775807) at
../src/gallium/drivers/iris/iris_fence.c:215
#4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50,
wait=, query=0x55774159b800, ctx=) at
../src/gallium/drivers/iris/iris_query.c:635
#5 iris_get_query_result (ctx=, query=0x55774159b800,
wait=, result=0x7fffc5404e50) at
../src/gallium/drivers/iris/iris_query.c:601
#6 0x7fcaca405e89 in tc_get_query_result (_pipe=,
query=0x55774159b800, wait=, result=0x7fffc5404e50) at
../src/gallium/auxiliary/util/u_threaded_context.c:881
#7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0,
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at
../src/mesa/main/queryobj.c:266
#8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790,
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
#9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283
"glGetQueryObjecti64v", id=, pname=34918,
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
at ../src/mesa/main/queryobj.c:1174
#10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=,
pname=, params=) at
../src/mesa/main/queryobj.c:1257
#11 0x7fcadfa39b90 in ?? () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#20 0x7fcae0743c24 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fcae0743293 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fcadf8d0849 in meta_context_run_main_loop () from
/lib/x86_64-linux-gnu/libmutter-10.so.0
#24 0x55773f1a4f12 in ?? ()
#25 0x7fcadf429d90 in __libc_start_call_main
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1,
argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70,
argc=1, argv=0x7fffc54053e8, init=, fini=,
rtld_fini=, stack_end=0x7fffc54053d8)
at ../csu/libc-start.c:392
#27 0x55773f1a51b5 in ?? ()
```
Other discussion thread:
https://gitlab.freedesktop.org/drm/intel/-/issues/6851
https://gitlab.gnome.org/GNOME/mutter/-/issues/2431
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter (not installed)
Uname: Linux 5.18.0-rc2+ x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Sep 19 10:39:59 2022
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
[Desktop-packages] [Bug 1990891] Re: after today's Kinetic updates, WiFi no longer working, so laptop basically useless
I just felt disabling it until it was better fixed was better then removal, which causes a couple meta packages like ubuntu-desktop to also remove and could be forgotten causing issues in the future of not getting new packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1990891 Title: after today's Kinetic updates, WiFi no longer working, so laptop basically useless Status in network-manager package in Ubuntu: Confirmed Bug description: ThinkPad X1 Carbon 6th Gen WiFi was working fine. Installed today's batch of Kinetic updates. Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad USB dongle and plug into my router to be able to submit this bug report). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: network-manager 1.40.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 17:09:25 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-08-16 (1137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 100 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.40.0 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1990891/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990891] Re: after today's Kinetic updates, WiFi no longer working, so laptop basically useless
you can uninstall wpasupplicant instead of disabling it but if they conflict we need to resolve it differently than by adding iwd as we did -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1990891 Title: after today's Kinetic updates, WiFi no longer working, so laptop basically useless Status in network-manager package in Ubuntu: Confirmed Bug description: ThinkPad X1 Carbon 6th Gen WiFi was working fine. Installed today's batch of Kinetic updates. Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad USB dongle and plug into my router to be able to submit this bug report). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: network-manager 1.40.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 17:09:25 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-08-16 (1137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 100 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.40.0 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1990891/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990886] Re: Security updates missing after 91.11.0
Hi Olivier, Do you have any updates on line for thunderbird? We got a similar question last week on IRC. ** Information type changed from Private Security to Public Security ** 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/1990886 Title: Security updates missing after 91.11.0 Status in thunderbird package in Ubuntu: Confirmed Bug description: Upstream released Thunderbird 91.11.0 on June 28, 2022. It's now at 91.13.1 from September 19, 2022. The release notes say: "By popular demand, Thunderbird 91.13.1 contains important security updates that shipped in Thunderbird 102.2.1. Users are encouraged to update as soon as possible." Source: https://www.thunderbird.net/en-US/thunderbird/91.13.1/releasenotes/ Ubuntu 22.04 Jammy (but also the other supported LTS) still has Thunderbird 91.11.0 (1:91.11.0+build2-0ubuntu0.22.04.1) without the security fixes after 91.11.0. The package should be updated to 91.13.1. Given that it has been three months without security updates, there seems to be some general friction with following upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1990886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961910] Re: Ubuntu 22 crash when updating, broken network manager and cannot report bug
This bug is closed. Please open new bugs for any crashes you experience. -- 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/1961910 Title: Ubuntu 22 crash when updating, broken network manager and cannot report bug Status in gnome-shell package in Ubuntu: Invalid Bug description: A new day, a new struggle with Ubuntu 22.04. So, I decided to get my daily updates and in the middle of the process the system just crashed, leaving me at the login page. When I got back, the wifi was no longer there and the network configuration was reporting an error about the network manager having problems. I shut down and restarted, the wifi came back. Went to the var/crash folder to report the bug with $:/var/crash$ ubuntu-bug _usr_bin_gnome-shell.1000.crash and it started complaining about older packages that need to be upgraded. I run `apt upgrade`, one of the packages is `dbus`, I tried `apt install dbus` and another even uglier crash that left me with a black screen from which I could only come back with a forced shutdown and restart. Now, how do I get out of this mess and report the bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800740] Re: /usr/share/applications/evolution-calendar.desktop Exec program 'evolution -c calendar' has not ben found in th PATH
** Package changed: gnome-shell (Ubuntu) => evolution (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/1800740 Title: /usr/share/applications/evolution-calendar.desktop Exec program 'evolution -c calendar' has not ben found in th PATH Status in evolution package in Ubuntu: New Status in menulibre package in Ubuntu: Invalid Bug description: Invalid desktop file detected! Please see details Parsing Errors The following desktop file have failed parsing by the underlying library, and will therefore not show up in MenuLibre Please investigate these problems with the associated package maintainer /usr/share/applications/evolution-calendar.desktop Exec program 'evolution -c calendar' has not been found in the PATH ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: menulibre 2.2.0-1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 23:47:18 2018 InstallationDate: Installed on 2018-10-28 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: menulibre UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1800740/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906792] Re: Chromium tabs freeze with two windows on Wayland (Xwayland)
** Package changed: xorg-server (Ubuntu) => xwayland (Ubuntu) -- 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/1906792 Title: Chromium tabs freeze with two windows on Wayland (Xwayland) Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Original description: When using Chromium (snap) on Wayland (gnome-session), if I keep two windows open on different workspaces, sometimes the current tab becomes unusable as it freezes or is super-slow. This usually happens with specific pages open, like youtube, mattermost, google drive. Minimizing one of the two windows makes the other work fine. The issues does not happen if both windows are on the same workspace. I've seen this issue in 20.04 and 20.10, always on Wayland sessions. The same behavior doesn't happen on a plain X11 session. --- Updates: As for #1916458 this behaviour may happen also on the same workspace and with Google Chrome ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Dec 4 09:39:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-18 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1906792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990456] Re: xorg reports bogus 1600x1024 resolution
@Timo, Could you help to check when this SRU will be finished on Jammy? Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1990456 Title: xorg reports bogus 1600x1024 resolution Status in OEM Priority Project: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Confirmed Bug description: xorg reports 1600x1024 bogus resolution [ Impact ] * User of NVIDIA GPU is able to switch to 1600x1024 resolution but cannot display anything under the resolution [ Fix ] Drop 001_fedora_extramodes.patch which was dropped from Fedora since xserver 1.5.0. [ Test Plan ] 1. Find a test unit with NVIDIA GPU, or anything but use Xorg mode to enter the desktop 2. Type `xrandr` in terminal Expected: The resolution 1600x1024 should not appear if the display does not support it. Actual: The resolution 1600x1024 appears. [ Where problems could occur ] * Lack of extra modes that the display might actually support. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
