[Bug 1270579] Re: On laptops, screen brightness and keyboard backlight isn't memorized between sessions
** Changed in: systemd Status: New => Confirmed -- 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/1270579 Title: On laptops, screen brightness and keyboard backlight isn't memorized between sessions To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1270579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1953080] Re: mouse click is delaying and sometimes don't work
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1953080 Title: mouse click is delaying and sometimes don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1953080/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959599] Re: gnome-shell freezes upon trying to login
Those log messages appear to be bug 1951786 / bug 1949352 which has a fix in proposed. I don't think that explains any freezes but you should probably try that first: https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/70~ubuntu3.21.10.1 If that doesn't fix the problem then next try disabling everything in the Extensions app. Then log in again. If that doesn't fix the problem then please run this command to collect more information: apport-collect 1959599 ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1959599 Title: gnome-shell freezes upon trying to login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959599/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959596] Re: Applications end up in session scope, rather than per .desktop scope
This might also explain why Chrome's log messages are prefixed as gnome- shell... Regardless, please report the issue to gnome-shell at: https://gitlab.gnome.org/GNOME/gnome-shell/issues -- 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/1959596 Title: Applications end up in session scope, rather than per .desktop scope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959596/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959599] Re: gnome-shell freezes upon trying to login
** Tags added: impish -- 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/1959599 Title: gnome-shell freezes upon trying to login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959599/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1930567] Re: Popup menus don't appear at all if opened close to inter-monitor boundaries in Wayland sessions
** Changed in: mutter (Ubuntu) Status: Triaged => Fix Committed ** Tags added: fixed-in-42.0 fixed-upstream -- 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/1930567 Title: Popup menus don't appear at all if opened close to inter-monitor boundaries in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1930567/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959507] Re: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f)
Looks like this crash has been fixed twice in the past: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2957 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4522 but all those fixes are in gnome-shell 41 already. So we need a new fix. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2957 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2957 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4522 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4522 -- 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/1959507 Title: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959507/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959507] Re: gnome-shell crashed with SIGABRT in __pthread_kill_implementation()
** This bug is no longer a duplicate of bug 1871262 gnome-shell freezes/crashes with meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ** Summary changed: - gnome-shell crashed with SIGABRT in __pthread_kill_implementation() + gnome-shell crashed with assertion failed: (guessed_scale >= 1.f) ** Summary changed: - gnome-shell crashed with assertion failed: (guessed_scale >= 1.f) + gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f) ** Information type changed from Private to Public ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => 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/1959507 Title: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959507/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)
Nvidia-470 has Wayland support if you add kernel parameter nvidia- drm.modeset=1 Also the Nvidia web site (driver downloads) clarifies the difference between the two current driver branches. Defaulting to 470 might still be a good idea for LTS... Production Branch (470): Production Branch drivers provide ISV certification and optimal stability and performance for Unix customers. This driver is most commonly deployed at enterprises, providing support for the sustained bug fix and security updates commonly required. New Feature Branch (495): New Feature Branch drivers provide early adopters and bleeding edge developers access to the latest driver features before they are integrated into the Production Branches -- 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/1959362 Title: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1959362/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959591] Re: Out-of-bounds read during processing of a password-protected PDF file
** Package changed: unzip (Ubuntu) => poppler (Ubuntu) ** Description changed: Out-of-bounds read during processing of a password-protected PDF file # Description During processsing of the attached pdf file via ``` pdftotext -upw USERPASS -opw OWNERPASS $PWD/testcase /tmp/out.txt ``` a out-of-bounds read happens. Since I was unable to reproduce this bug on the most recent upstream commit (b3f93644de4941bdbd532a7d8f82cd652dfbeadf), I report it here. - This bug allows an attacker to perform a denial of service and possibly opens up - other attack vectors. + This bug allows an attacker to perform a denial of service and possibly + opens up other attack vectors. To reproduce the crash, we provide the following script alongside the crashing input: - ./reproduce-ubuntu.sh: Reproduce crash via a Ubuntu 20.04 docker container If you need further details, we are happy to answer all questions. # apt show poppler-utils Package: poppler-utils Version: 0.86.1-0ubuntu1 Priority: optional Section: utils Source: poppler Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian freedesktop.org maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 754 kB Provides: pdftohtml, xpdf-utils Depends: libpoppler97 (= 0.86.1-0ubuntu1), libc6 (>= 2.14), libcairo2 (>= 1.12.0), libfreetype6 (>= 2.2.1), liblcms2-2 (>= 2.2+git20110628), libstdc++6 (>= 5.2) Conflicts: pdftohtml Breaks: xpdf-common, xpdf-utils (<< 1:0) Replaces: pdftohtml, xpdf-reader, xpdf-utils (<< 3.02-2~) Homepage: http://poppler.freedesktop.org/ Task: print-server, ubuntu-desktop-minimal, ubuntu-desktop, kubuntu-desktop, xubuntu-core, xubuntu-desktop, lubuntu-desktop, ubuntustudio-desktop-core, ubuntustudio-desktop, ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-budgie-desktop Download-Size: 174 kB APT-Manual-Installed: no APT-Sources: http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Description: PDF utilities (based on Poppler) - # valgrind Ubuntu ==1== Memcheck, a memory error detector ==1== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==1== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info ==1== Command: pdftotext -upw USERPASS -opw OWNERPASS /testcase /tmp/out.txt - ==1== + ==1== Syntax Error (409): Dictionary key must be a name object Syntax Error (796): Illegal character <29> in hex string Syntax Error (798): Illegal character <14> in hex string Syntax Error (799): Illegal character in hex string Syntax Error (800): Illegal character in hex string Syntax Error (801): Illegal character <8a> in hex string Syntax Error (860): Illegal character <58> in hex string Unimplemented Feature: Unsupported version/revision (1/0) of Standard security handler ==1== Invalid read of size 8 ==1==at 0x498F758: FilterStream::getDict() (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x4A0B4A9: Parser::makeStream(Object&&, unsigned char const*, CryptAlgorithm, int, int, int, int, bool) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x4A0BE3D: Parser::getObj(bool, unsigned char const*, CryptAlgorithm, int, int, int, int, bool) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x49EE0AE: Hints::readTables(BaseStream*, Linearization*, XRef*, SecurityHandler*) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x4A0C949: PDFDoc::checkLinearization() (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x4A0E4A9: PDFDoc::getPage(int) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x4A0E88C: PDFDoc::displayPage(OutputDev*, int, double, double, int, bool, bool, bool, bool (*)(void*), void*, bool (*)(Annot*, void*), void*, bool) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x4A0E9E1: PDFDoc::displayPages(OutputDev*, int, int, double, double, int, bool, bool, bool, bool (*)(void*), void*, bool (*)(Annot*, void*), void*) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x10C57F: main (pdftotext.cc:400) ==1== Address 0x60005ad8fc0 is not stack'd, malloc'd or (recently) free'd - ==1== - ==1== + ==1== + ==1== ==1== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==1== General Protection Fault ==1==at 0x498F758: FilterStream::getDict() (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x4A0B4A9: Parser::makeStream(Object&&, unsigned char const*, CryptAlgorithm, int, int, int, int, bool) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x4A0BE3D: Parser::getObj(bool, unsigned char const*, CryptAlgorithm, int, int, int, int, bool) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x49EE0AE: Hints::readTables(BaseStream*, Linearization*, XRef*, SecurityHandler*) (in
[Bug 1959591] [NEW] Out-of-bounds read during processing of a password-protected PDF file
*** This bug is a security vulnerability *** You have been subscribed to a public security bug: Out-of-bounds read during processing of a password-protected PDF file # Description During processsing of the attached pdf file via ``` pdftotext -upw USERPASS -opw OWNERPASS $PWD/testcase /tmp/out.txt ``` a out-of-bounds read happens. Since I was unable to reproduce this bug on the most recent upstream commit (b3f93644de4941bdbd532a7d8f82cd652dfbeadf), I report it here. This bug allows an attacker to perform a denial of service and possibly opens up other attack vectors. To reproduce the crash, we provide the following script alongside the crashing input: - ./reproduce-ubuntu.sh: Reproduce crash via a Ubuntu 20.04 docker container If you need further details, we are happy to answer all questions. # apt show poppler-utils Package: poppler-utils Version: 0.86.1-0ubuntu1 Priority: optional Section: utils Source: poppler Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian freedesktop.org maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 754 kB Provides: pdftohtml, xpdf-utils Depends: libpoppler97 (= 0.86.1-0ubuntu1), libc6 (>= 2.14), libcairo2 (>= 1.12.0), libfreetype6 (>= 2.2.1), liblcms2-2 (>= 2.2+git20110628), libstdc++6 (>= 5.2) Conflicts: pdftohtml Breaks: xpdf-common, xpdf-utils (<< 1:0) Replaces: pdftohtml, xpdf-reader, xpdf-utils (<< 3.02-2~) Homepage: http://poppler.freedesktop.org/ Task: print-server, ubuntu-desktop-minimal, ubuntu-desktop, kubuntu-desktop, xubuntu-core, xubuntu-desktop, lubuntu-desktop, ubuntustudio-desktop-core, ubuntustudio-desktop, ubuntukylin-desktop, ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-budgie-desktop Download-Size: 174 kB APT-Manual-Installed: no APT-Sources: http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Description: PDF utilities (based on Poppler) # valgrind Ubuntu ==1== Memcheck, a memory error detector ==1== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==1== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info ==1== Command: pdftotext -upw USERPASS -opw OWNERPASS /testcase /tmp/out.txt ==1== Syntax Error (409): Dictionary key must be a name object Syntax Error (796): Illegal character <29> in hex string Syntax Error (798): Illegal character <14> in hex string Syntax Error (799): Illegal character in hex string Syntax Error (800): Illegal character in hex string Syntax Error (801): Illegal character <8a> in hex string Syntax Error (860): Illegal character <58> in hex string Unimplemented Feature: Unsupported version/revision (1/0) of Standard security handler ==1== Invalid read of size 8 ==1==at 0x498F758: FilterStream::getDict() (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x4A0B4A9: Parser::makeStream(Object&&, unsigned char const*, CryptAlgorithm, int, int, int, int, bool) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x4A0BE3D: Parser::getObj(bool, unsigned char const*, CryptAlgorithm, int, int, int, int, bool) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x49EE0AE: Hints::readTables(BaseStream*, Linearization*, XRef*, SecurityHandler*) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x4A0C949: PDFDoc::checkLinearization() (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x4A0E4A9: PDFDoc::getPage(int) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x4A0E88C: PDFDoc::displayPage(OutputDev*, int, double, double, int, bool, bool, bool, bool (*)(void*), void*, bool (*)(Annot*, void*), void*, bool) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x4A0E9E1: PDFDoc::displayPages(OutputDev*, int, int, double, double, int, bool, bool, bool, bool (*)(void*), void*, bool (*)(Annot*, void*), void*) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x10C57F: main (pdftotext.cc:400) ==1== Address 0x60005ad8fc0 is not stack'd, malloc'd or (recently) free'd ==1== ==1== ==1== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==1== General Protection Fault ==1==at 0x498F758: FilterStream::getDict() (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x4A0B4A9: Parser::makeStream(Object&&, unsigned char const*, CryptAlgorithm, int, int, int, int, bool) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x4A0BE3D: Parser::getObj(bool, unsigned char const*, CryptAlgorithm, int, int, int, int, bool) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x49EE0AE: Hints::readTables(BaseStream*, Linearization*, XRef*, SecurityHandler*) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x4A0C949: PDFDoc::checkLinearization() (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x4A0E4A9: PDFDoc::getPage(int) (in /usr/lib/x86_64-linux-gnu/libpoppler.so.97.0.0) ==1==by 0x4A0E88C: PDFDoc::displayPage(OutputDev*, int,
[Bug 1959599] [NEW] gnome-shell freezes upon trying to login
Public bug reported: On Impish 21.10, gnome-shell freezes up when trying to login, specifically after I have typed in my password and hit enter. I have seen this both when logging in after the display shuts itself off after whatever the automatic timeout is, and also after manually locking the screen. This is the stack trace I see from gnome-shell at the time it freezes up: https://pastebin.ubuntu.com/p/9RcnnT32Nf/ The freeze was at 09:58:16 in the log. In this specific instance I just force rebooted the machine, in the other instance this happened to me, I let it sit and see if it would recover but it had not recovered after an hour or two. ** 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/1959599 Title: gnome-shell freezes upon trying to login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959599/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959596] [NEW] Applications end up in session scope, rather than per .desktop scope
Public bug reported: During systemd-oomd install in jammy (w/ GNOME session) today, I noticed that applications ended up in the wrong control group - in the session scope, rather than per .desktop one: Control group /: -.slice ├─user.slice │ └─user-1000.slice │ ├─user@1000.service │ │ ├─session.slice │ │ │ ├─xdg-document-portal.service │ │ │ │ ├─4514 /usr/libexec/xdg-document-portal │ │ │ │ └─4556 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount,subt… │ │ │ ├─xdg-desktop-portal.service │ │ │ │ └─6186 /usr/libexec/xdg-desktop-portal │ │ │ ├─pipewire-pulse.service │ │ │ │ └─4473 /usr/bin/pipewire-pulse │ │ │ ├─wireplumber.service │ │ │ │ └─4472 /usr/bin/wireplumber │ │ │ └─pipewire.service │ │ │ └─4461 /usr/bin/pipewire │ │ ├─background.slice │ │ │ └─tracker-miner-fs-3.service │ │ │ └─4940 /usr/libexec/tracker-miner-fs-3 │ │ ├─user.slice │ │ │ └─podman-pause-6313308764925138924.scope │ │ │ └─4602 /usr/bin/podman │ │ ├─app.slice │ │ │ ├─gvfs-goa-volume-monitor.service │ │ │ │ └─5417 /usr/libexec/gvfs-goa-volume-monitor │ │ │ ├─snap.syncthing.syncthing.908e68e0-47a9-47b6-80b0-a6a3afdd4f24.scope │ │ │ │ ├─4470 /snap/syncthing/501/syncthing │ │ │ │ └─5510 /snap/syncthing/501/syncthing │ │ │ ├─xdg-permission-store.service │ │ │ │ └─4527 /usr/libexec/xdg-permission-store │ │ │ ├─snap.spotify.spotify.b3c54917-38c3-473b-8774-b90e1d30a8c3.scope │ │ │ │ ├─198100 /snap/spotify/57/usr/share/spotify/spotify │ │ │ │ ├─198169 /snap/spotify/57/usr/share/spotify/spotify --type=zygote --n… │ │ │ │ ├─198170 /snap/spotify/57/usr/share/spotify/spotify --type=zygote --n… │ │ │ │ ├─198188 /snap/spotify/57/usr/share/spotify/spotify --type=gpu-proces… │ │ │ │ ├─198205 /snap/spotify/57/usr/share/spotify/spotify --type=utility --… │ │ │ │ ├─198208 /snap/spotify/57/usr/share/spotify/spotify --type=utility --… │ │ │ │ └─198235 /snap/spotify/57/usr/share/spotify/spotify --type=renderer -… │ │ │ ├─evolution-calendar-factory.service │ │ │ │ └─6018 /usr/libexec/evolution-calendar-factory │ │ │ ├─xdg-desktop-portal-gnome.service │ │ │ │ └─6193 /usr/libexec/xdg-desktop-portal-gnome │ │ │ ├─dconf.service │ │ │ │ └─5837 /usr/libexec/dconf-service │ │ │ ├─gvfs-daemon.service │ │ │ │ ├─ 4515 /usr/libexec/gvfsd │ │ │ │ ├─ 4531 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f │ │ │ │ ├─ 8485 /usr/libexec/gvfsd-http --spawner :1.4 /org/gtk/gvfs/exec_spa… │ │ │ │ ├─29658 /usr/libexec/gvfsd-trash --spawner :1.4 /org/gtk/gvfs/exec_sp… │ │ │ │ └─29990 /usr/libexec/gvfsd-burn --spawner :1.4 /org/gtk/gvfs/exec_spa… │ │ │ ├─evolution-source-registry.service │ │ │ │ └─5820 /usr/libexec/evolution-source-registry │ │ │ ├─gvfs-udisks2-volume-monitor.service │ │ │ │ └─5202 /usr/libexec/gvfs-udisks2-volume-monitor │ │ │ ├─app-org.gnome.Terminal.slice │ │ │ │ ├─gnome-terminal-server.service │ │ │ │ │ └─8577 /usr/libexec/gnome-terminal-server │ │ │ │ └─vte-spawn-e31cc856-c6d7-4247-935c-6d28706ab542.scope │ │ │ │ ├─ 8595 -bash │ │ │ │ ├─ 8617 tmux -u -2 -f /usr/share/byobu/profiles/tmuxrc new-session… │ │ │ │ ├─ 8648 tmux -u -2 -f /usr/share/byobu/profiles/tmuxrc new-session… │ │ │ │ ├─ 8655 /bin/bash │ │ │ │ ├─ 8749 journalctl -f │ │ │ │ ├─ 25429 /bin/bash │ │ │ │ ├─179012 /bin/bash │ │ │ │ ├─208170 systemd-cgls │ │ │ │ └─208171 xclip │ │ │ ├─gpg-agent.service │ │ │ │ ├─29718 /usr/bin/gpg-agent --supervised │ │ │ │ └─70766 scdaemon --multi-server │ │ │ ├─gvfs-gphoto2-volume-monitor.service │ │ │ │ └─5403 /usr/libexec/gvfs-gphoto2-volume-monitor │ │ │ ├─xdg-desktop-portal-gtk.service │ │ │ │ └─7143 /usr/libexec/xdg-desktop-portal-gtk │ │ │ ├─obex.service │ │ │ │ └─63426 /usr/lib/bluetooth/obexd │ │ │ ├─at-spi-dbus-bus.service │ │ │ │ ├─5443 /usr/libexec/at-spi-bus-launcher │ │ │ │ ├─5457 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2… │ │ │ │ └─5886 /usr/libexec/at-spi2-registryd --use-gnome-session │ │ │ ├─gvfs-metadata.service │ │ │ │ └─5931 /usr/libexec/gvfsd-metadata │ │ │ ├─dbus.service │ │ │ │ ├─ 4508 /usr/bin/dbus-daemon --session --address=systemd: --nofork --… │ │ │ │ ├─ 5431 /usr/libexec/goa-daemon │ │ │ │ ├─ 5513 /usr/libexec/goa-identity-service │ │ │ │ ├─ 5804 /usr/libexec/gnome-shell-calendar-server │ │ │ │ ├─ 5888 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Notificat… │ │ │ │ ├─ 6073 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.ScreenSaver │ │ │ │ ├─ 6426 /usr/libexec/ibus-portal │ │ │ │ └─29631 /usr/bin/gnome-calendar --gapplication-service │ │ │ ├─evolution-addressbook-factory.service │ │ │ │ └─7198 /usr/libexec/evolution-addressbook-factory │ │ │ ├─gvfs-mtp-volume-monitor.service │ │ │ │ └─5384 /usr/libexec/gvfs-mtp-volume-monitor │ │ │ └─gvfs-afc-volume-monitor.service │ │ │ └─5524 /usr/libexec/gvfs-afc-volume-monitor │ │ └─init.scope │ │ ├─4347 /lib/systemd/systemd --user │ │ └─4354
[Bug 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)
I've confirmed that nvidia-470 is getting installed in jammy, not nvidia-495. AFAIK this is a bug, I thought nvidia-495 was in jammy? Without it we don't get a wayland session with nvidia. ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Changed in: ubiquity (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) ** Tags added: rls-jj-incoming -- 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/1959362 Title: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1959362/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
