[Bug 2059818] Re: Regression: Jammy to Noble, set_label no longer functions
I installed the 58-1 version of gnome-shell-extension-appindicator from noble-proposed and rebooted and can confirm that I now see the label on an appindicator (indicator-sensors in this case) as expected. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2059818 Title: Regression: Jammy to Noble, set_label no longer functions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060575] [NEW] gnome-keyring fails to automatically unlock login keyring after recent updates in noble
Public bug reported: After installing recent updates in 24.04, upon logging in the gnome- shell based UI pops up saying that the login keyring was not unlocked and asking for the users password to be input to unlock it. Similarly a second, non-gnome-shell based UI is also present asking the same thing. Will try and get a screenshot to attach. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libpam-gnome-keyring 46.1-2build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 9 06:16:46 2024 InstallationDate: Installed on 2021-08-03 (980 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-keyring UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1929209] Re: [i915] external monitor goes black for several seconds at a time, randomly
Same issue with external monitor in Ubuntu 20.04 LTS, Fedora 39 (KDE plasma) and I observed it with many other distributions (e.g. Lubuntu 23.10). With exactly same setup, Windows 10 Pro on my lenovo T470s with external monitor does not give any issues, so, not a HW problem. Tried xset -dpms, sxet s off did not really solved the problem.. better say this WA did not help at all. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1929209 Title: [i915] external monitor goes black for several seconds at a time, randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039577] Re: gnome-control-center incorrectly claims remote login is off
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2039577 Title: gnome-control-center incorrectly claims remote login is off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2039577/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1879137] Re: The snap-store is using hundreds of MiBs of RAM.
Polite ping... JFYI: 4.5GB RAM usage by snap-store for 11 days uptime on Mantic: > date Tue Dec 5 05:43:26 PM CET 2023 > uptime 17:43:29 up 11 days, 7:22, 2 users, load average: 2.63, 2.76, 2.70 > lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 23.10 Release:23.10 Codename: mantic > ps auxww | grep "snap-store\|MEM" USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND me 2329407 0.0 7.0 5602200 4607896 ? Sl Dec04 1:06 /snap/snap-store/959/usr/bin/snap-store --local-filename /home/me/... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1879137 Title: The snap-store is using hundreds of MiBs of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1879137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2044588] Re: Gnome crash after suspend mode , all openapps auto closed
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2044588 Title: Gnome crash after suspend mode , all openapps auto closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2044588/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1879137] Re: The snap-store is using hundreds of MiBs of RAM.
@waveform (Dave Jones) The issue is still reproducible for me on 23.10 (see the new attached picture). Snap-store used 2GB RAM my laptop with 1 day uptime only (and the RAM usage is growing over the time, please check my screenshot in https://bugs.launchpad.net/snap-store-desktop/+bug/1879137/comments/36 26GB RAM used by snap-store there !!!) Happy to help with tracing it, feel free to ping me in MM! ** Attachment added: "snap-store.png" https://bugs.launchpad.net/snap-store-desktop/+bug/1879137/+attachment/5721584/+files/snap-store.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1879137 Title: The snap-store is using hundreds of MiBs of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1879137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
had the same issue on my thinkpad t16 (amd) on 23.10. I did some updates and it fixed the issue -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2041478] Re: /usr/bin/gnome-calendar:6:g_assertion_message:g_assertion_message_expr:recalculate_layout_blocks:gcal_month_view_row_add_event:gcal_month_view_add_event
Ah I see this is already in 45.1-1 in noble ** Also affects: gnome-calendar (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gnome-calendar (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: gnome-calendar (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/2041478 Title: /usr/bin/gnome- calendar:6:g_assertion_message:g_assertion_message_expr:recalculate_layout_blocks:gcal_month_view_row_add_event:gcal_month_view_add_event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/2041478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2041478] Re: /usr/bin/gnome-calendar:6:g_assertion_message:g_assertion_message_expr:recalculate_layout_blocks:gcal_month_view_row_add_event:gcal_month_view_add_event
I can reliably reproduce this by just launching gnome-calendar on mantic. This looks to be the same issue as the upstream https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1106 which has an associated fix in https://gitlab.gnome.org/GNOME/gnome- calendar/-/merge_requests/366 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-calendar/-/issues #1106 https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1106 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/2041478 Title: /usr/bin/gnome- calendar:6:g_assertion_message:g_assertion_message_expr:recalculate_layout_blocks:gcal_month_view_row_add_event:gcal_month_view_add_event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/2041478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2041267] [NEW] Laptop not recovering after Lid Close
Public bug reported: Closed laptop lid (10:32) and after about an hour opened it back up (11:30). System was responsive and I could hear notifications, but the screen was completely dark and the laptop keys were not lit up. I was holding down my power button on the keyboard but the system was not turning off. I eventually managed to reboot by blindly typing on an external USB keyboard. System Info: alex@ubuntu:~$ inxi -F System: Host: ubuntu Kernel: 6.5.0-10-generic arch: x86_64 bits: 64 Desktop: GNOME v: 45.0 Distro: Ubuntu 23.10 (Mantic Minotaur) Machine: Type: Laptop System: Razer product: Blade 15 (2022) - RZ09-0421 v: 8.04 serial: Mobo: Razer model: CH580 v: 4 serial: UEFI: Razer v: 2.02 date: 01/10/2023 Battery: ID-1: BAT0 charge: 71.5 Wh (96.9%) condition: 73.8/80.2 Wh (92.0%) CPU: Info: 14-core (6-mt/8-st) model: 12th Gen Intel Core i7-12800H bits: 64 type: MST AMCP cache: L2: 11.5 MiB Speed (MHz): avg: 445 min/max: 400/4700:4800:3700 cores: 1: 584 2: 400 3: 458 4: 400 5: 582 6: 458 7: 767 8: 400 9: 470 10: 400 11: 400 12: 400 13: 400 14: 400 15: 400 16: 400 17: 400 18: 400 19: 400 20: 400 Graphics: Device-1: Intel Alder Lake-P Integrated Graphics driver: i915 v: kernel Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] driver: nvidia v: 535.113.01 Device-3: IMC Networks Integrated RGB Camera driver: uvcvideo type: USB Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 23.2.0 driver: X: loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa dri: iris gpu: i915 resolution: 2560x1440~240Hz API: OpenGL v: 4.6 Mesa 23.2.1-1ubuntu3 renderer: Mesa Intel Graphics (ADL GT2) Audio: Device-1: Intel Alder Lake PCH-P High Definition Audio driver: sof-audio-pci-intel-tgl Device-2: NVIDIA GA106 High Definition Audio driver: snd_hda_intel API: ALSA v: k6.5.0-10-generic status: kernel-api Server-1: PipeWire v: 0.3.79 status: active Network: Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi IF: wlo1 state: up mac: 4c:44:5b:81:97:dc Bluetooth: Device-1: Intel driver: btusb type: USB Report: hciconfig ID: hci0 state: up address: 4C:44:5B:81:97:E0 bt-v: 5.3 Drives: Local Storage: total: 953.87 GiB used: 289.01 GiB (30.3%) ID-1: /dev/nvme0n1 model: NVMe CA6-8D1024 size: 953.87 GiB Partition: ID-1: / size: 20 GiB used: 7.27 GiB (36.4%) fs: btrfs dev: /dev/nvme0n1p7 ID-2: /boot size: 974.7 MiB used: 166 MiB (17.0%) fs: ext4 dev: /dev/nvme0n1p20 ID-3: /boot/efi size: 96 MiB used: 73 MiB (76.1%) fs: vfat dev: /dev/nvme0n1p2 ID-4: /home size: 600 GiB used: 273.08 GiB (45.5%) fs: btrfs dev: /dev/nvme0n1p8 ID-5: /var size: 20 GiB used: 8.49 GiB (42.4%) fs: btrfs dev: /dev/nvme0n1p5 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 33.0 C mobo: N/A Fan Speeds (rpm): N/A Info: Processes: 471 Uptime: 13m Memory: total: 16 GiB note: est. available: 15.3 GiB used: 3.11 GiB (20.4%) Shell: Bash inxi: 3.3.29 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gdm3 45~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 11:46:32 2023 InstallationDate: Installed on 2023-05-30 (149 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: Upgraded to mantic on 2023-10-26 (0 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic ** Attachment added: "Journalctl logs from this boot." https://bugs.launchpad.net/bugs/2041267/+attachment/5713552/+files/logs.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2041267 Title: Laptop not recovering after Lid Close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2041267/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039607] Re: ClamTK not working properly
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** Package changed: gnome-terminal (Ubuntu) => clamtk (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2039607 Title: ClamTK not working properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamtk/+bug/2039607/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028312] Re: does not support spec 1.5
@seb128 @racb Looks like release 0.27 was pushed last week: https://gitlab.freedesktop.org/xdg/desktop-file-utils/-/commit/2470d73f93d02b354ecbee7c2f02a83efaae84d8 Can we have the Ubuntu package updated as well? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/2028312 Title: does not support spec 1.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/2028312/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1879137] Re: The snap-store is using hundreds of MiBs of RAM.
On my Ubuntu 23.04 the snap-store uses ~26GB!!! of RAM in 7 days of uptime. o_0 > ps -p 6720 -o %cpu,%mem,cmd %CPU %MEM CMD 0.0 39.6 /snap/snap-store/959/usr/bin/snap-store --gapplication-service > top -n 1 -p 6720 top - 00:54:56 up 7 days, 20:34, 2 users, load average: 1.83, 2.31, 2.60 Tasks: 1 total, 0 running, 1 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 64004.4 total, 19553.1 free, 42037.0 used, 6194.6 buff/cache MiB Swap: 1952.0 total, 0.0 free, 1952.0 used. 21967.4 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 6720 taurus20 0 27.1g 24.8g 5604 S 0.0 39.6 4:39.30 snap-store Happy to help tracing it! How? P.S. It could be the separate issue... ** Attachment added: "Screenshot from 2023-09-29 00-57-05.png" https://bugs.launchpad.net/snap-store-desktop/+bug/1879137/+attachment/5705240/+files/Screenshot%20from%202023-09-29%2000-57-05.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1879137 Title: The snap-store is using hundreds of MiBs of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1879137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2033566] Re: Cursor drawn incorrectly on portrait mode
Took a video recording with my phone. Oop, just saw your comment. Thank you! ** Attachment added: "mouse_issue.mp4" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2033566/+attachment/5696608/+files/mouse_issue.mp4 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2033566 Title: Cursor drawn incorrectly on portrait mode To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2033566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2033566] Re: Cursor drawn incorrectly on portrait mode
** Description changed: On 23.10 Ubuntu Mantic Minotaur (development branch). Noticed this when upgrading to gnome-shell 45~beta.1-0ubuntu2 While the cursor itself behaves normally on portrait mode (I can fully drag around windows and click on things normally), how it's drawn is not. It seems like the cursor is being drawn as if the monitor is in landscape mode? When moving my invisible up and down cursor near the top of my Portrait Right monitor, the drawn cursor on the top moving left and right. Moving the cursor to the top of my monitor causes the drawn one to hit the right side, and moving my cursor downwards causes the drawn one to go off-screen to the left. In Portrait Right at least, my monitor is physically vertical but the "monitor" that the mouse was drawn on is rotated 90 degrees clockwise with the top right corner aligned. Notably, the mouse is the correct orientation. - Also notably, the built in screen recorder, when it didn't crash, seems to see the cursor drawn correctly? - + Both the built in screen recorder (when it isn't crashing) and OBS with a Screen Capture (PipeWire) source both capture the cursor drawn correctly. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 30 20:17:47 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-30 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2033566 Title: Cursor drawn incorrectly on portrait mode To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2033566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2033566] Re: Cursor drawn incorrectly on portrait mode
** Description changed: On 23.10 Ubuntu Mantic Minotaur (development branch). Noticed this when upgrading to gnome-shell 45~beta.1-0ubuntu2 - While the cursor itself behaves normally on portrait mode (I can fully drag around windows and click on things normally), how it's drawn is not. It seems like the cursor is being drawn as if the monitor is in landscape mode? When moving my invisible up and down cursor near the top of my Portrait Right monitor, the drawn cursor on the top moving left and right. Moving the cursor to the top of my monitor causes the drawn one to hit the right side, and moving my cursor downwards causes the drawn one to go off-screen to the left. - Notably, the mouse is the correct orientation. + While the cursor itself behaves normally on portrait mode (I can fully + drag around windows and click on things normally), how it's drawn is + not. It seems like the cursor is being drawn as if the monitor is in + landscape mode? When moving my invisible up and down cursor near the top + of my Portrait Right monitor, the drawn cursor on the top moving left + and right. Moving the cursor to the top of my monitor causes the drawn + one to hit the right side, and moving my cursor downwards causes the + drawn one to go off-screen to the left. In Portrait Right at least, my monitor is physically vertical but the "monitor" that the mouse was drawn on is rotated 90 degrees clockwise with the top right corner aligned. + + Notably, the mouse is the correct orientation. + Also notably, the built in screen recorder, when it didn't crash, seems to see the cursor drawn correctly? + ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 30 20:17:47 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-30 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2033566 Title: Cursor drawn incorrectly on portrait mode To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2033566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2033566] [NEW] Cursor drawn incorrectly on portrait mode
Public bug reported: On 23.10 Ubuntu Mantic Minotaur (development branch). Noticed this when upgrading to gnome-shell 45~beta.1-0ubuntu2 While the cursor itself behaves normally on portrait mode (I can fully drag around windows and click on things normally), how it's drawn is not. It seems like the cursor is being drawn as if the monitor is in landscape mode? When moving my invisible up and down cursor near the top of my Portrait Right monitor, the drawn cursor on the top moving left and right. Moving the cursor to the top of my monitor causes the drawn one to hit the right side, and moving my cursor downwards causes the drawn one to go off-screen to the left. Notably, the mouse is the correct orientation. In Portrait Right at least, my monitor is physically vertical but the "monitor" that the mouse was drawn on is rotated 90 degrees clockwise with the top right corner aligned. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 30 20:17:47 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-30 (1 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2033566 Title: Cursor drawn incorrectly on portrait mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2033566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2031406] Re: [MIR] libei
I reviewed libei 1.0.0-0ubuntu2 as checked into mantic. This shouldn't be considered a full audit but rather a quick gauge of maintainability. libei is a library to emulate input, particularly for the Wayland graphics stack. It provides 3 components - libei - the library to emulate inputs on the client side - libeis - a library to process these inputs on the server side - oeffis - a library for communicating with the XDG RemoteDesktop Portal - CVE History - None - Build-Depends - No interesting / security relevant dependencies - No pre/post inst/rm scripts - No init scripts - No systemd units - No dbus system/session services - No setuid binaries - No binaries in PATH - No sudo fragments - No polkit files - No udev rules - unit tests / autopkgtests - No autopkgtests but since this package is just a library with minimal external depencies, I don't think this should be a blocker. - unit tests look quite comprehensive: 1/9 libei / unit-tests-utils OK 0.02s 2/9 libei / unit-tests-ei OK 0.02s 3/9 libei / unit-tests-eisOK 0.02s 4/9 libei / unit-tests-oeffis OK 0.01s 5/9 libei / eierpeckenOK 0.08s 6/9 libei:python / python-black OK 0.49s 7/9 libei:python / scanner-pytest OK 0.52s 8/9 libei:python / oeffis-pytest OK 2.58s 9/9 libei:python / protocol-test OK 6.61s Ok: 9 Expected Fail: 0 Fail: 0 Unexpected Pass:0 Skipped:0 Timeout:0 - No cron jobs - Build logs contain a couple warnings - the second of which should ideally be fixed: ../tools/ei-demo-client.c:102:9: warning: ignoring return value of read declared with attribute warn_unused_result [-Wunused-result] ../src/util-sources.c:311:9: warning: ignoring return value of read declared with attribute warn_unused_result [-Wunused-result] - No processes spawned - Memory management - Given this is written in C there is suprisingly little dynamic memory management - when malloc() etc are used, the code has a tendency to use assert() to die immediately if memory fails to be allocated. Whilst not very graceful, this is pretty standard in higher order libraries like glib etc so is not really concerning to see it here. In general the code appears quite defensive too. - File IO - Only really used for creating a lock file and reading its own cmdline - again this is quite safe. - Logging - Appears quite careful, no apparent uses of directives that might be vulnerable to string-format attacks etc - Environment variable usage - Only uses XDG_RUNTIME_DIR and its own LIBEI_SOCKET environment variables - No apparent use of privileged functions - Uses rand() to assign a non-overlapping token for requests to xdg-desktop-portal - this is fine, they are not expected to be cryptographically secure etc, they just need to be unique within a session - No use of temp files - Uses AF_UNIX sockets for local communication - No use of WebKit - No use of PolicyKit - No significant cppcheck results - One significant Coverity result - I reported this upstream https://gitlab.freedesktop.org/libinput/libei/-/issues/43 who fixed it within 24 hours - along with a related issue they noticed - No significant shellcheck results - No significant bandit results - all issues identified are in the test suite and most can be ignored (ie. use of assert etc.) - No significant govulncheck results - No significant Semgrep results In general libei looks to be quite a well-written and maintained code- base. The upstream is responsive to issues and easy to work with as well. Security team ACK for promoting libei to main. ** Bug watch added: gitlab.freedesktop.org/libinput/libei/-/issues #43 https://gitlab.freedesktop.org/libinput/libei/-/issues/43 ** Changed in: libei (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2031406 Title: [MIR] libei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libei/+bug/2031406/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028312] Re: does not support spec 1.5
Yes, however their repository is not very active. It's going to be a waiting game. I think I will just use a rolling release distribution instead. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/2028312 Title: does not support spec 1.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/2028312/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028312] Re: does not support spec 1.5
error when trying trying to validate a desktop file running spec 1.5: $ desktop-file-validate Applications/squashfs-root/org.keepassxc.KeePassXC.desktop Applications/squashfs-root/org.keepassxc.KeePassXC.desktop: error: value "1.5" for key "Version" in group "Desktop Entry" is not a known version Applications/squashfs-root/org.keepassxc.KeePassXC.desktop: hint: value item "Security" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Settings, or System Applications/squashfs-root/org.keepassxc.KeePassXC.desktop: error: file contains key "SingleMainWindow" in group "Desktop Entry", but keys extending the format should start with "X-" -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/2028312 Title: does not support spec 1.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/2028312/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028312] [NEW] does not support spec 1.5
Public bug reported: This package's code is a bit behind from the upstream code. In 2022, code was committed to support 1.5: https://gitlab.freedesktop.org/xdg/desktop-file-utils/-/commit/56d220dd679c7c3a8f995a41a27a7d6f3df49dea When trying to validate .desktop files in Ubuntu that are running 1.5, I am getting errors. I am running Ubuntu 23.04 desktop-file-utils 0.26-1ubuntu5 ** Affects: desktop-file-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/2028312 Title: does not support spec 1.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/2028312/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008355] Re: Unable to set fractional scaling on three monitor setup
I have the same problem (two 1080p displays and one 3k display). Would that workaround work with wayland? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2008355 Title: Unable to set fractional scaling on three monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2008355/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
On an Ubuntu 22.04 (newly updated from 18.04) box I got Firefox and
Chromium browser back to using the good, system SaveAs dialog box
instead of the horrid (((search box focus grabber and almost impossible
to change file name from the default))) dialog box by doing this:
sudo snap install snapd
This version of snapd, 2.38.3, apparently overrides the apt-installed
snapd version 2.38.
That the snap version of snapd wasn't installed ("snap list" did not
list it) was the glaring difference between the bad box and a laptop
that did not have the problem.
I should note: widget.use-xdg-desktop-portal.file-picker needs to be put
back to the default, 2, from 0.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1949340
Title:
[upstream] Saving downloads or pages is difficult because of unfocused
file chooser dialog
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961508] Re: Dock displaying over window after resuming from blank screen
Hi, affected. Notebook. Ubuntu 22.04.2 LTS, Wayland. Gnome Version 42.5 Affected apps: Firefox, gnome-terminal. Hardware: HP EliteBook 850 G8 Notebook PC 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz × 8 Mesa Intel® Xe Graphics (TGL GT2) It happened once with this flow but I couldn't reproduce it immediately after: 1. Locking the screen by closing my notebook. 2. Opening my notebook and unlocking the login screen 3. Switching from a window like Firefox with Alt+Tab to the terminal 4. At that point, the dock overlapped the terminal and when alt-tabbing again, it also overlapped Firefox. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000644] Re: switching workspaces with shortcut sometimes freezes screen
Same as Gauthier for me, I have the bug. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2000644 Title: switching workspaces with shortcut sometimes freezes screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2000644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000332] [NEW] package xrdp 0.9.17-2ubuntu2 failed to install/upgrade: installed xrdp package post-installation script subprocess returned error exit status 1
Public bug reported: no ProblemType: Package DistroRelease: Ubuntu 22.04 Package: xrdp 0.9.17-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-1029.36-azure 5.15.64 Uname: Linux 5.15.0-1029-azure x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: xrdp:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Dec 22 14:39:10 2022 ErrorMessage: installed xrdp package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: xrdp Title: package xrdp 0.9.17-2ubuntu2 failed to install/upgrade: installed xrdp package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xrdp.sesman.ini: 2022-12-22T01:41:47.290830 mtime.conffile..etc.xrdp.xrdp.ini: 2022-12-22T01:43:30.420150 ** Affects: xrdp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xrdp in Ubuntu. https://bugs.launchpad.net/bugs/2000332 Title: package xrdp 0.9.17-2ubuntu2 failed to install/upgrade: installed xrdp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/2000332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994941] Re: I locked computer after night I am trying to turn on by open lid and am see dark srceen. keyboard does not respond, can connect only by ssh from other pc.
sudo gdm3 restart from ssh is solve the problem, but I lose open applications -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994941 Title: I locked computer after night I am trying to turn on by open lid and am see dark srceen. keyboard does not respond, can connect only by ssh from other pc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994941/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1994941] [NEW] I locked computer after night I am trying to turn on by open lid and am see dark srceen. keyboard does not respond, can connect only by ssh from other pc.
Public bug reported: I locked computer. After night I am trying to turn on by open lid and I am see dark srceen. keyboard does not respond, can connect only by ssh from other pc. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Oct 27 14:33:47 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-10 (17 days ago) InstallationMedia: Ubuntu 20.04.4 2022.08.10 LTS "Custom Focal Fossa" (20220810) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-10-10 (16 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994941 Title: I locked computer after night I am trying to turn on by open lid and am see dark srceen. keyboard does not respond, can connect only by ssh from other pc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994941/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1992234] [NEW] Nautilus switching folders delay
Public bug reported: Small delay when switching folders using nautilus 1:42.2-0ubuntu1. Mouse crosshair has a clock-timer showing up. The delay is not very big, I would estimate 0.2-0.3s on a fresh ubuntu upgrade install. This delay however is not noticed using pcmanfm filemanager, or when I installed flasharch (flash player) and used some nautilus-mod to browse files within the app. I have confirmed the bug to affect others in IRC libera chat #ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 1:42.2-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 13:03:57 2022 GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'never'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1138, 1110)' InstallationDate: Installed on 2021-04-18 (537 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210322) SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-08-22 (46 days ago) 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 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy ** Description changed: Small delay when switching folders using nautilus 1:42.2-0ubuntu1. Mouse crosshair has a clock-timer showing up. The delay is not very big, I - would estimate 0.2-0.3s on a fresh ubuntu install. + would estimate 0.2-0.3s on a fresh ubuntu upgrade install. This delay however is not noticed using pcmanfm filemanager, or when I installed flasharch (flash player) and used some nautilus-mod to browse files within the app. I have confirmed the bug to affect others in IRC libera chat #ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 1:42.2-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 13:03:57 2022 GsettingsChanges: - b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" - b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" - b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'never'" - b'org.gnome.nautilus.window-state' b'initial-size' b'(1138, 1110)' + b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" + b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" + b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'never'" + b'org.gnome.nautilus.window-state' b'initial-size' b'(1138, 1110)' InstallationDate: Installed on 2021-04-18 (537 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210322) SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-08-22 (46 days ago) 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 + evince42.3-0ubuntu2 + file-roller 3.42.0-1 + nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 + nautilus-share0.7.3-2ubuntu6 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1992234 Title: Nautilus switching folders delay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1992234/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1991780] [NEW] Changes in display configuration couses crash in gnome-shell and logout
Public bug reported: If i try to configure multiple monitor setup, it is often causes logout, that i even can't press "keep changes" button. Also it happens that Ubuntu user suddenly logs-out when i unplug one of the monitors. Ubuntu 22.04.1 LTS 64 bit GNOME Version 42.4 Windowing System Wayland I fond there is a gnome-shell crash report in /var/crash, and if i try to see the back-trace i get following [Current thread is 1 (Thread 0x7f76ff4ee5c0 (LWP 104545))] (gdb) bt #0 0x5502 in ?? () #1 0x7f7704af075f in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #2 0x7f7705804dfd in g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #3 0x7f7704afa240 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #4 0x7f77056e1698 in g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f7704b065bc in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #6 0x7f7704b2095e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #7 0x7f7704b0662d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #8 0x7f77056fdc24 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f77057526f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f77056fd293 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f7704a6d849 in meta_context_run_main_loop () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #12 0x5574c350cf12 in ?? () #13 0x7f770479ed90 in __libc_start_call_main (main=main@entry=0x5574c350ca70, argc=argc@entry=1, argv=argv@entry=0x7ffe866c19f8) at ../sysdeps/nptl/libc_start_call_main.h:58 #14 0x7f770479ee40 in __libc_start_main_impl (main=0x5574c350ca70, argc=1, argv=0x7ffe866c19f8, init=, fini=, rtld_fini=, stack_end=0x7ffe866c19e8) at ../csu/libc-start.c:392 #15 0x5574c350d1b5 in ?? () ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1991780 Title: Changes in display configuration couses crash in gnome-shell and logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1991780/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1982422] Re: Multiple vulnerabilities in Bionic, Focal and Jammy
> All the CVEs fixed by the attached debdiffs have priority low or negligible. > Therefore, these updates should not be sponsored until a higher priority issue > is found in GIMP. I don't think it is right to try and say these should not be sponsored until a higher priority issue is found - it is just that other higher priority updates for other packages will usually take precedence. Please try not to talk with authority about things which you do not have authority over. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1982422 Title: Multiple vulnerabilities in Bionic, Focal and Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1982422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently
>> I don't think it's appropriate to display that in the settings app. > I suppose that not knowing is more secure? Yes if you consider the risk of users DoS'ing themselves by having to potentially hack around in the CLI / BIOS settings to try and find the right incantations to get a green check mark to appear. The status quo is a lack of awareness - so we need to trade of the risks of showing something which is unactionable and potentially alarming vs. keeping things as they are. Once there is support to rectify these issues from the GUI then I am not at all opposed to showing this information and would welcome it. However even then, we will want to ensure this is a robust process since we don't want to say make it easy to enable Secure Boot and then prevent machines from booting since the user doesn't actually run a signed kernel, or say end up having hardware devices silently disabled on a subsequent reboot since they were previously using unsigned modules etc. There is a lot of complexity and corner cases here so it is prudent to be conservative in our approach IMO. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1987162 Title: 43: New Device Security feature is confusing and unhelpful currently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently
Indeed - I don't think it is useful to have such information displayed prominently when there is nothing that user's can do to affect this (in general) and so this will only cause alarm. Like Marc said, it is then not useful to display this without offering actionable tasks that a user an perform to increase their security, since then as jbicha suggested, some users will likely try and manually workaround these findings to 'increase' their security and potentially break their systems. Whilst it is commendable that GNOME is trying to perhaps raise security awareness for users, doing this in a way where users don't really have any control over the results is likely to cause more harm than good. So I agree, this should not be part of the standard gnome-control-center at this stage for Ubuntu. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1987162 Title: 43: New Device Security feature is confusing and unhelpful currently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
Same issue with Alt+Shift on Ubuntu 22.04 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 283115] Re: Gimp: toolbox windows can't be minimized
** Changed in: gimp (Ubuntu) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/283115 Title: Gimp: toolbox windows can't be minimized To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/283115/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
** Changed in: apparmor (Ubuntu Jammy) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1969896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
I have verified this as follows: # enable proposed so we can install apparmor from there # https://wiki.ubuntu.com/Testing/EnableProposed cat
[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
** Description changed: - Just switched from Ubuntu 20.04 to 22.04 and realized that Document - Viewer no longer open on the last viewed page and doesn't remember the - side pane preference even after using the "Save Current Settings as - Default" option. Kindly advise + [Impact] - ProblemType: Bug - DistroRelease: Ubuntu 22.04 - Package: evince 42.1-3 - ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 - Uname: Linux 5.15.0-25-generic x86_64 - NonfreeKernelModules: nvidia_modeset nvidia - ApportVersion: 2.20.11-0ubuntu82 - Architecture: amd64 - CasperMD5CheckResult: unknown - CurrentDesktop: ubuntu:GNOME - Date: Fri Apr 22 15:58:50 2022 - InstallationDate: Installed on 2022-03-19 (34 days ago) - InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) - ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash - SourcePackage: evince - UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) + * Evince does not behave as expected and launches with a very small + window resulting in a poor user experience + + * Fixing this requires only a minor change to the exo-open abstraction + and results in correctly functioning evince + + * By removing the dbus deny rule in the exo-open abstraction, evince is + able to correctly communicate with gvfs and start up as normal + + [Test Plan] + + * Start dbus-monitor to watch for AppArmor denials + + $ dbus-monitor --session | grep AppArmor + + * Launch evince and there should be no AppArmor message shown above + from dbus-monitor + + [Where problems could occur] + + * By removing this deny rule from the exo-open abstraction, AppArmor + will be more permissive for anything which uses the exo-open abstraction + and potentially allow it access to gvfs where it did not before. + + * This should not result in any regressions as we are granting extra + functionality which wasn't allowed before, however perhaps in the case + of an application which expects *not* to be able to use gvfs as this was + previously explicitly denied, it may now be able to (if it has a less + specific allow rule) and hence it may function differently than before. + + [Other Info] + + * Whilst on the surface by removing this deny rule it may appear that this grants additional permissions to anything which uses the exo-open abstraction, this is not necessarily true as AppArmor denies all accesses by default unless explicitly allowed by a profile. And so in general this will not grant permission to use a DBus interface that an application did not have before. However, due to the way that deny rules take precedence over allow rules in AppArmor, if an application had been allowed generic dbus access to the user's session bus, the previous deny rule in the exo-open abstraction would then have denied them access to just gvfs via dbus. With this new proposed change, this is not explicitly denied and so is now allowed as expected. But for applcations which may have used the exo-open abstraction and which did *not* have DBus access before, this change will not result in them obtaining DBus access either. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1969896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
@georgia so the usual process (as per https://wiki.ubuntu.com/StableReleaseUpdates) from here would be to first get the changes into apparmor/evince in the current devel release (kinetic) and once it is verified that they are working fine there, then we backport them to jammy etc. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
** Also affects: evince (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: evince (Ubuntu Kinetic) Importance: High Status: In Progress ** Also affects: apparmor (Ubuntu Kinetic) Importance: High Status: Confirmed ** Changed in: apparmor (Ubuntu Kinetic) Status: Confirmed => In Progress ** Changed in: apparmor (Ubuntu Jammy) Status: New => In Progress ** Changed in: apparmor (Ubuntu Kinetic) Assignee: (unassigned) => Alex Murray (alexmurray) ** Changed in: apparmor (Ubuntu Jammy) Assignee: (unassigned) => Alex Murray (alexmurray) ** Changed in: apparmor (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1969896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
FYI I have sent a MR to the upstream AppArmor project to remove this dbus deny rule from the exo-open abstraction: https://gitlab.com/apparmor/apparmor/-/merge_requests/884 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1969896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1917175] Re: gdm login screen says "Something went wrong please try again" three times and sends me back to the login screen when I'm not typing anything
*** This bug is a duplicate of bug 1917178 *** https://bugs.launchpad.net/bugs/1917178 I had a very similar problem: whenever I clicked on a user at a login screen I had to type my password really quick in order for it not to be reset. Then sometimes login process stuck and I had to go into a text-based login prompt (ctrl+alt+f2) and then back to UI (ctrl+alt+f1) and this worked. Staying on the UI prompt didn't work. After reading this thread I removed: sudo apt purge --auto-remove fprintd libfprint-2-2 and I saw that option for fingerprint login disappeared from the user's settings menu. I restarted my notebook and login screen worked without any issues. I'm having HP EliteBook G8 and official Ubuntu notes at https://ubuntu.com/certified/202103-28761 say: "Fingerprint reader and WWAN hardware are not supported on this device" However, I experimented with it trying to check it after fresh installation. I hope these workarounds can help people struggling with the login as I did. Also, if somebody wants any reports from me, I can try to install fprint libraries and reproduce it. Just let me know. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1917175 Title: gdm login screen says "Something went wrong please try again" three times and sends me back to the login screen when I'm not typing anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1917175/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964091] Re: long touch/press a directory won't trigger the context menu like file on empty space. on touch monitor
** Changed in: oem-priority Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1964091 Title: long touch/press a directory won't trigger the context menu like file on empty space. on touch monitor To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1964091/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968402] Re: Ubuntu 20.04.3 boots to black screen, no TTY available
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968402 Title: Ubuntu 20.04.3 boots to black screen, no TTY available To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1968402/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964442] Re: [jammy][regression] gnome-shell PolicyKit password prompt sends keys to the terminal
Upstream bug filed https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5242 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5242 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5242 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1964442 Title: [jammy][regression] gnome-shell PolicyKit password prompt sends keys to the terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964442/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964442] Re: [jammy][regression] gnome-shell PolicyKit password prompt sends keys to the terminal
I personally don't think this should be low priority - this affects any application which ends up causing the gnome shell prompt dialog to appear - so in my case when reading my email and opening a GPG encrypted email I get prompted for my GPG passphrase - whilst this is happening my email client is repeatedly getting sent to it, causing it to advance forward to the next email and mark the current one as read - so this has a real usability impact IMO. This is not just relevant to terminal applications etc. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1964442 Title: [jammy][regression] gnome-shell PolicyKit password prompt sends keys to the terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964442/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965837] [NEW] Erroneous / extra input generated in requesting application when prompting to unlock keys
Public bug reported: Recently I have noticed that when I am being prompted for the passphrase for to unlock a GPG/SSH key via the gnome-shell prompter, whilst the prompt is visible the requesting window seems to get spammed by input - this can be reproduced via running the following (but replace the gpg recipient with the one of your own user's private key): $ echo RELOADAGENT | gpg-connect-agent; echo foo | gpg --encrypt --recipient alex.mur...@canonical.com | gpg --decrypt See attached for a short video demonstrating the issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 22 11:43:36 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-03 (230 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-01-14 (66 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Screencast from 22-03-22 11:45:41.webm" https://bugs.launchpad.net/bugs/1965837/+attachment/5571537/+files/Screencast%20from%2022-03-22%2011%3A45%3A41.webm -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965837 Title: Erroneous / extra input generated in requesting application when prompting to unlock keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965837/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965837] Re: Erroneous / extra input generated in requesting application when prompting to unlock keys
If it is not clear from the video - watch the terminal window in the background when the prompt for the passphrase appears - it keeps scrolling as though getting input by newlines all the time - and this then persists even after the prompt is dismissed until I manually provide some input myself. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965837 Title: Erroneous / extra input generated in requesting application when prompting to unlock keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965837/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach
** Tags added: nvidia ** Changed in: oem-priority Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962276] Re: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed
See this related debian bug https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1006368 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1962276/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962276] Re: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed
This appears to be caused (for me at least) by upower 0.99.16-1 - after upgrading today to 0.99.16-2 things are working again as expected. ** Also affects: upower (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1006368 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006368 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1962276 Title: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1962276/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962351] [NEW] login screen shown on inactive monitor
Public bug reported: My laptop is docked with the lid closed and connected to 2 external monitors. After upgrading a bunch of packages from jammy in the last 24 hours I notice that when logging in, both of my external monitors just show the purple background whilst the login dialog was actually displayed on the closed lid of my laptop. Wasn't sure if this should be filed against some other package as it doesn't look like gnome-shell or gdm3 have changed lately (I only see gnome-shell-extension-appindicator and gnome-shell-extension-ubuntu-dock in my apt history that could be related...) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 41.3-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 09:52:39 2022 InstallationDate: Installed on 2021-08-03 (206 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-01-14 (42 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1962351 Title: login screen shown on inactive monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1962351/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1961910] Re: Ubuntu 22 crash when updating, broken network manager and cannot report bug
See https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962127 for an ubuntu-bug of the gnome-shell crash file when this occurred for me yesterday. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1728342] Re: Some applications disable "Night Light" and it is not reenabled upon exiting application
It happens on Ubuntu 20.04 as well -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1728342 Title: Some applications disable "Night Light" and it is not reenabled upon exiting application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728342/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1946578] Re: Placeholder for CVE-2021-41133
** Also affects: flatpak (Ubuntu Impish) Importance: Undecided Assignee: Andrew Hayzen (ahayzen) Status: New ** Also affects: flatpak (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: flatpak (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: flatpak (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1946578 Title: Placeholder for CVE-2021-41133 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1946578/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Is there any option to do this via portals - ie can evince use https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus- org.freedesktop.portal.OpenURI to open the URI? Would then this allow to avoid going via xdg-open? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1942542] Re: gedit causes loss of extended attributes (xattrs)
https://gitlab.gnome.org/GNOME/gedit/-/issues/464 ** Bug watch added: gitlab.gnome.org/GNOME/gedit/-/issues #464 https://gitlab.gnome.org/GNOME/gedit/-/issues/464 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1942542 Title: gedit causes loss of extended attributes (xattrs) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1942542/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1942653] [NEW] RandR fractional scaling patch interferes with manual RandR output scaling
Public bug reported: $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 $ apt-cache policy mutter mutter: Installed: 3.36.9-0ubuntu0.20.04.1 Candidate: 3.36.9-0ubuntu0.20.04.1 Version table: *** 3.36.9-0ubuntu0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-3ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages --- As an example with one output, scaling it with e.g. 'xrandr --output --mode 3840x2160 --scale-from 1920x1080', would usually result in a screen size of 1920x1080, as xrandr sets the screen size to the bounding box of the configured crtcs. Ubuntu carries an out-of-tree patch for Mutter: x11-Add-support-for-fractional-scaling-using-Randr.patch, attached. It adds a new function, meta_monitor_manager_xrandr_update_screen_size_derived(), that in response to RandR configuration changes will attempt to set its own screen size. When calculating the new screen size, it applies a scaling factor to each crtc that effectively reverses the requested one. As a result, in the above example the resulting screen size is 3840x2160, despite the fact that there is only a 1920x1080 viewport into it. With the modesetting driver, this isn't a huge issue. The resulting screen size is larger than you can actually interact with, wasting memory, but it doesn't cause any visible functional issues. The NVIDIA driver automatically configures panning when the requested outputs' viewports are smaller than the screen size. This increases crtc size, which impacts Mutter's screen size calculation. When Mutter sets the larger-than-outputs screen size, it triggers the NVIDIA driver to automatically configure panning. Mutter reacts to the RandR configuration change by again recalculating the screen size, this time growing it even larger due to the larger crtcs. In response, the NVIDIA driver sets up the new, larger panning configuration, causing the crtcs to be even larger, and causing Mutter to once again recalculate the screen size. This goes on until all memory is consumed and gnome-shell is killed by the OOM killer, or the screen reaches maximum size. In the meantime, the screen is black with only a cursor while gnome-shell spins. It appears that meta_monitor_manager_xrandr_update_screen_size_derived() is intended for GNOME fractional scaling, adjusting the screen size to accommodate. In this case we are manually configuring output scaling with RandR, but this code still runs, causing unintended consequences. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Patch added: "x11-Add-support-for-fractional-scaling-using-Randr.patch" https://bugs.launchpad.net/bugs/1942653/+attachment/5522890/+files/x11-Add-support-for-fractional-scaling-using-Randr.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1942653 Title: RandR fractional scaling patch interferes with manual RandR output scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1942653/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1940758] [NEW] gedit file edit causes loss of birth time
Public bug reported: gedit 3.38.1-1 Ubuntu 21.04 Editing a previously created file with gedit and saving it causes loss of the original file birth time and updates it to the time of the file save. File birth time should not be changed. Compare this with nano, which does not change the file birth time. File birth time can be shown with the stat command. ** Affects: gedit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1940758 Title: gedit file edit causes loss of birth time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1940758/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892456] security audit
I reviewed malcontent 0.10.0-2 as checked into impish. This shouldn't be considered a full audit but rather a quick gauge of maintainability. malcontent provides a library and application to manage "parental" restrictions for users. It allows to define restrictions on what applications should be presented to the user to be able to be launched, as well as what kinds of applications (as defined by their OARS rating) are allowed to be installed by the user via gnome-software or similar. Currently this is limited to flatpak application IDs so if this was intended to support snaps Ubuntu would have to patch malcontent (as well as potentially gnome-shell and gnome-software/snap-store etc) to support snaps. It does not perform any enforcement itself, instead it provides a means for configuring the policy via a GUI and an library which would then be used by gnome-shell / gnome-software etc and these applications would then do the actual enforcement by filtering their results accordingly. malcontent also includes a PAM plugin to check session time limits and only allow a user to log in if they have not exceeded their allocated time. By design, malcontent states that it is not a security boundary as it's restrictions can potentially be circumvented by simply using applications to launch/install software that do not integrate with the malcontent system. As such, installing or launching applications via the command-line directly would appear to circumvent the malcontent restrictions. As such I do not feel malcontent requires a full security audit as part of the MIR process, however the following is provided as a high-level summary nonetheless. - No CVE History - Interesting Build-Depends: - policykit-1 - pre/post inst/rm scripts - libpam-malcontent: - postinst script registers the pam plugin - prerm script removes the pam plugin - malcontent - postinst script restarts the accounts-daemon service - postrm scripts restarts the accounts-daemon service - No init scripts - No systemd units - No dbus services - No setuid binaries - binaries in PATH: - malcontent: - -rwxr-xr-x root/root 23077 2020-12-10 03:23 ./usr/bin/malcontent-client - malcontent-gui: - -rwxr-xr-x root/root 63792 2021-02-10 00:41 ./usr/bin/malcontent-control - No sudo fragments - polkit files - malcontent: -rw-r--r-- root/root 39834 2021-02-10 00:41 ./usr/share/polkit-1/actions/com.endlessm.ParentalControls.policy -rw-r--r-- root/root 1517 2021-02-10 00:41 ./usr/share/polkit-1/rules.d/com.endlessm.ParentalControls.rules -rw-r--r-- root/root 393 2021-02-10 00:41 ./var/lib/polkit-1/localauthority/10-vendor.d/com.endlessm.ParentalControls.pkla - configures policykit to ensure only admins can modify policies but allows users to introspect their own restrictions. - No udev rules - No autopkgtests - Unit tests run during the build - No cron jobs - Build logs are relatively clean - Processes spawned - GUI supports spawning gnome-control-center to show the user accounts page - this looks safe from command-injection etc. - Memory management - Is written in C but uses glib/gobject APIs and appears quite defensive. - No obvious File IO - Logging is via glib macros and appears careful to avoid overflows / string format vulns etc. - No environment variable usage - No use of privileged functions - No use of cryptography / random number sources etc - No use of temp files - No use of networking - No use of WebKit - Uses PolicyKit to authorise changes to the various restrictions that can be performed via libmalcontent but this is done solely via installing policykit policies for the various actions - No significant cppcheck results - No significant Coverity results Security team ACK for promoting malcontent to main. ** Tags added: security-review-done ** Changed in: malcontent (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to malcontent in Ubuntu. https://bugs.launchpad.net/bugs/1892456 Title: [MIR] malcontent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/malcontent/+bug/1892456/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1456668] Re: evince cannot display one of my postscript files
The problem seems to be caused by evince that uses DSC processing on a non-DSC-conforming file. Removal of all DSC comments makes evince display the last page of the file only. This indicates that evince cannot handle non-conforming files at all. Perhaps evince can convert all PostScript files to PDF and avoid the reliance on DSC parsing. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1456668 Title: evince cannot display one of my postscript files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1456668/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865838] Re: no error displayed on failed fingerprint authentication
** Changed in: oem-priority Assignee: Alex Tu (alextu) => Andy Chi (andch) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1865838 Title: no error displayed on failed fingerprint authentication To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp
** Also affects: flatpak (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: flatpak (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: flatpak (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1918482 Title: Update for GHSA-xgh4-387p-hqpp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell
I think should be included by default the possibility to use a desktop with files and icons. A desktop for just a wallpaper is nonsense. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898462 Title: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1898462/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1911473] Re: Update for ghsa-4ppf-fxf6-vxg2
** Also affects: flatpak (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: flatpak (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: flatpak (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: flatpak (Ubuntu Hirsute) Importance: Undecided Assignee: Andrew Hayzen (ahayzen) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1911473 Title: Update for ghsa-4ppf-fxf6-vxg2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1911473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
@Chistiano Nunes right, I updated and installed it, but but everything like before. So I installed the "temporarily as a workaround" from above again. sudo apt install libmutter-6-0=3.36.1-3ubuntu3 gir1.2-mutter-6=3.36.1-3ubuntu3 sudo apt-mark hold libmutter-6-0 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
@Kai Kasurinen >probably fixed on shared-mime-info 2.0: >https://gitlab.freedesktop.org/xdg/shared-mime-info/-/commit/18bb7cfc6c43d710ecf60339b5dd9bd19c297cdf Yeah, well. It's if they only used the same database. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: misidentifies .html file as Perl script when it contains JavaScript "use strict" To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
If you wrap string in the proper tags you will get the same result, but
with different offset (28 chars):
tee "index.html" <
`printf "x"%.0s {1..228}`
use strict
eol # -> text/html
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu.
https://bugs.launchpad.net/bugs/1890716
Title:
misidentifies .html file as Perl script when it contains JavaScript
"use strict"
To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
#ＩＮＴＲＯ After digging up for a while I've found where the issue comes from for both `.html` and `.py` (bug #1857824) files. #ＳＨＯＲＴ The culprit responsible for misidentification resides in `.xml` database which specifies how to match mime-type against input data. It can be found here [2]. #ＬＯＮＧ The `kmimetypefinder.cpp` pulls up [0] `QMimeDatabase db` apis by `db.mimeTypeForFile(...)` which in turns bootstrup `QMimeDatabasePrivate ...` XML database from .xml file.[1] If we look carefully at the content of the `"text/x-perl"` entry we would see the following: ``` ... ... ``` Did you notice the offset attribute `"0:256"`? Now if we run the following two cases we will see that files whose content contains keywords `use strict` in the range of 1..256 will be identified as `text/x-perl` script and as `text/html` if the `use trict` is located outside of such range otherwise, checkout: tee "index.html"
[Bug 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
With the same setup I have the `mimetype` to output `text/html` for `index.html`. It seems it workds correctly. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: misidentifies .html file as Perl script when it contains JavaScript "use strict" To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
** Also affects: kde-cli-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: misidentifies .html file as Perl script when it contains JavaScript "use strict" To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890716] Re: kmimetypefinder5 *.html reports wrong type
I've reported a new bug providing a complete and correct description: https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1896682 This one can be safely closed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: kmimetypefinder5 *.html reports wrong type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890716] Re: kmimetypefinder5 *.html reports wrong type
New bug reopened with complete and correct explanation: https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1896682 ** Changed in: shared-mime-info (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: kmimetypefinder5 *.html reports wrong type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890716] Re: xdg-mime query filetype index.html reports wrong type
After running that commands I got the following output: $ ... Running kmimetypefinder5 "/home/alex/Desktop/index.html" application/x-perl It seems like that kmimetypefinder5 is major culprit here. I've found another unrelated bugreport here which was reported about a year ago: https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1857824 In that case the program reports wrong type for *.py files with correct content. Weird! I think it's wortht to rename this bugreport. ** Summary changed: - xdg-mime query filetype index.html reports wrong type + kmimetypefinder5 *.html reports wrong type -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: kmimetypefinder5 *.html reports wrong type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890716] Re: xdg-mime query filetype index.html reports wrong type
I just have tried a fresh new user. The output is identical. See attached screenshot. ** Attachment added: "xdg-mime query wrong result" https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+attachment/5413048/+files/Screenshot_20200921_232318.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: xdg-mime query filetype index.html reports wrong type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Changed in: oem-priority Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Also affects: hwe-next Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
reply to #39, yes it's a trade off that we don't either want user get darkscreen when then randomly plug display port for case like #38 or user get lower bpc on their working display port. So far, there seems no solid way to make sure both requirement. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
according to #40 and conversation on mattermost with Kai-Heng. HWE is planning to add quirk for the faulty dongles so that the dark screen during boot time[1] can be fixed. [1] https://gitlab.freedesktop.org/drm/intel/-/issues/1890 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
I afraid we can not just trust (EDID_version >= 1.4 && EDID_supports_10bit). Because this issue caused by any problematic component in the middle of pipeline. To ensure the compatibility, better to just defautly set bpc=8. Think of one scenario, a speaker get his Ubuntu machine onto stage, plug the HDMI or DP projector which works well on latest speaker who is using Windows machine. Then, he get dark screen or audio function lost I guess the Ubuntu user might not aware it's caused by bpc. The default behavior should offer better user experience. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1066 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1066 ** Also affects: xorg-server via https://gitlab.freedesktop.org/xorg/xserver/-/issues/1066 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1108 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1108 ** Also affects: xorg-server via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1108 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1890772/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
Thanks for understanding. There's an upstream bug discussing this similar issue, we can follow their effort there. https://gitlab.freedesktop.org/drm/intel/-/issues/1890 ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #1890 https://gitlab.freedesktop.org/drm/intel/-/issues/1890 ** Description changed: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` - Would like to open this bug to open discussion for enhancing user experience. + Would like to open this bug to open discussion for enhancing user + experience. + + existed upstream bug: + - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 ** Changed in: oem-priority Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1890772/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
I think different from #32. To adding a GUI configure bpc is a long-term plan. Before that,the default behavior should be designed to get the best user experience. As we all know, there're lot of hardware components on the pipline of display path(e.g. socket, converter, dongle, cable, monitor) With any lower quality component on the pipeline, dark screen or function lost is not acceptable. It should be better to provide lower default bpc than dark user's screen. Afterall, user can adjust the bpc by command in short-term or by UI in long-term plan. But if we just dark user's screen, user mostly thinks the hardware is broken or Ubuntu provides poor compatibility(if they compare the same component to Windows). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1890772/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890716] Re: xdg-mime query filetype index.html reports wrong type
Hi Sebastien. Thaks your for your reply. I suggest you to do the following to see that even if file is starting with proper tags it is recognized as `application/x-perl`: $ tee "index.html" < use strict eol $ xdg-mime query filetype index.html # -> application/x-perl - wrong type Why did you tagged report as invalid? I just got a file with minified JS code which has `use strict` burrowed deep somewhere inside correct html file but it's still recognized as perl script. I can't use some tools to open the file in browser by using xdg-open and forced to use browser-specific launcher. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: xdg-mime query filetype index.html reports wrong type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890716] Re: xdg-mime query filetype index.html reports wrong type
why did you tag the report* Bump. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: xdg-mime query filetype index.html reports wrong type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Tags added: originate-from-1887915 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1890772/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Tags added: oem-priority originate-from-1886778 somerville -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1890772/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Did some more testing, it does actually look like one of my monitors is running at 30hz instead of 60hz, although the settings are reporting that it is running at 60hz. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
I had a 2080ti that died so I was running a 1070 until the RMA came, and the updated PPA worked perfectly with no issues. Swapped in the new 2080ti yesterday and have had a pretty significant performance hit since then, choppy movement and animations, feels like the whole desktop is running at 30fps or less. Same driver and other hardware. Nvidia driver 440.100 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882885] Re: FP Auth enroll for Multi user Scenario
I just follow your instructions on XPS 9300 with goodix fingerprint driver. `apt-get update; apt-get dist-upgrade -y; apt-get install -y libfprint-2-tod1-goodix` (there's an online update is on-going, after that, libfprint-2-tod1-goodix will be installed automatically) But I can not reproduce the issue you encountered. I will guess you are encountering the known issue there: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1865838It will stop FP authentication after several incorrect fingerprints without error display. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1882885 Title: FP Auth enroll for Multi user Scenario To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1882885/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882885] Re: FP Auth enroll for Multi user Scenario
also attached the logs from oem-getlogs from apport package. ** Attachment added: "oemlogs-u-XPS-13-9300-20200713183746+0800.apport.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1882885/+attachment/5392305/+files/oemlogs-u-XPS-13-9300-20200713183746+0800.apport.gz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1882885 Title: FP Auth enroll for Multi user Scenario To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1882885/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882885] Re: FP Auth enroll for Multi user Scenario
also attached the logs from oem-getlogs from apport package. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1882885 Title: FP Auth enroll for Multi user Scenario To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1882885/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885673] [NEW] won't auto-select input when headset is plugged and selected in pop-up window
Public bug reported: Step to reproduce: 1. plug-in headset 2. select headset in pop-up window. 3. check g-c-c Expected result: correct input is selected so that mic on the headset just works Actual result: The correct input is not selected. a patch is there waiting for upstream review : https://gitlab.gnome.org/GNOME/libgnome-volume- control/-/merge_requests/10 ** Affects: oem-priority Importance: High Status: New ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1875597 originate-from-1882905 somerville ** Summary changed: - mixer-control: adding ucm port names for audio device selection + won't auto-select input when headset is plugged and selected in pop-up window Edit ** Summary changed: - won't auto-select input when headset is plugged and selected in pop-up window Edit + won't auto-select input when headset is plugged and selected in pop-up window ** Description changed: - Recently Intel added a new audio driver in the Linux kernel, it is - called sof driver. This driver is needed on the laptops which - connect the digital mic to the PCH instead of the codec. To make the - sof driver work with pulseaudio, the ucm is mandatory. Intel - wrote the ucm for the machines with multi-function audio jack, with - this ucm, the port names are different from the ones without ucm, this - is the port names with the ucm: - [In] Dmic: Digital Microphone (priority: 100, latency offset: 0 usec) - Part of profile(s): Hdmi3, Hdmi2, Hdmi1, HiFi - [In] Headphone Microphone: Headphone Microphone (priority: 100, latency offset: 0 usec, available) - Part of profile(s): Hdmi3, Hdmi2, Hdmi1, HiFi - [In] Headset Microphone: Headset Microphone (priority: 100, latency offset: 0 usec, available) - Part of profile(s): Hdmi3, Hdmi2, Hdmi1, HiFi - [Out] Headphone: Headphone (priority: 200, latency offset: 0 usec, available) - Part of profile(s): HiFi - [Out] Speaker: Speaker (priority: 100, latency offset: 0 usec) - Part of profile(s): HiFi - To make the audio device selection work, let's add those new port - names. - And with the ucm, the Dmic (internal mic) is on one source since the - dmic connects to PCH, the headphone-mic and headset mic are on another - source since they connect to the codec. This needs us to add calling - set_default_source() in the source_info_cb(), it is safe even for old - machines on which internal mic, headphone-mic and headset-mic are on - the same source. + Step to reproduce: + + 1. plug-in headset + 2. select headset in pop-up window. + 3. check g-c-c + + Expected result: + correct input is selected so that mic on the headset just works + + Actual result: + The correct input is not selected. + + a patch is there waiting for upstream review : + https://gitlab.gnome.org/GNOME/libgnome-volume- + control/-/merge_requests/10 ** Tags added: oem-priority originate-from-1882905 somerville ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Importance: Critical => High ** Tags added: originate-from-1875597 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1885673 Title: won't auto-select input when headset is plugged and selected in pop-up window To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1885673/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
The scaling issue was fixed for me, now I can independently scale monitors, but if I try to change a monitor to portrait mode it fails and I get the issue with incorrect zoom and overlapping view ports. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
for me the two workaround doesn't work -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865845] Re: No UI indication for more than 10 fingerprint enrolling progress
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1865845 Title: No UI indication for more than 10 fingerprint enrolling progress To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1865845/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865838] Re: no error displayed on failed fingerprint authentification
** Tags added: oem-priority originate-from-1880064 somerville -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1865838 Title: no error displayed on failed fingerprint authentification To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865838] Re: no error displayed on failed fingerprint authentification
** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1865838 Title: no error displayed on failed fingerprint authentification To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
