[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.
OK, next time (each time) the crash happens, please:
1. Wait 10 seconds.
2. Reboot.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach the resulting text file here.
5. Redo the steps in comment #2 at the top of the page.
--
You received this bug notification because you are a member of
Well, I have the choice in my BIOS between hybrid graphics and discrete
graphics, no option to disable the discrete graphics card entirely. And
before you ask: I will not run on the discrete graphics card alone,
because of the battery drain that comes with it
--
You received this bug
The only definite crash I can see here happened during GPU startup:
[ 3020.788168] lapis gnome-shell[13120]: Created gbm renderer for
'/dev/dri/card1'
[ 3021.413765] lapis gnome-shell[13120]: GNOME Shell crashed with signal 11
[ 3021.413765] lapis gnome-shell[13120]: == Stack trace for context
@vanvugt: I've tried disabling all extensions but that did not have any
correlation with crashes. It kept on crashing regardless, also before
they were installed at all.
It would be worrying that something quite high level can crash the
entire window manager. It's disturbing. The culprit is
Another common cause of crashes like this is the "nouveau" graphics
driver. It's not very reliable so we recommend opening the "Additional
Drivers" app and using it to install the NVIDIA driver instead.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
The most likely cause of this crash is locally installed extensions and
you seem to have a few. Please start by deleting them:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Still haven't got time to reproduce, but I do think as long as this
hardware combination doesn't work out of the box with wayland it should
be disabled automatically for this hardware after installation or
upgrade.
This script is already disabling Wayland for lots of hardware
configurations:
I'm sorry, but have spend lots of time working around this bug and need
to focus on this weird phenomenon called work first, but will try to
reproduce as soon as I have time
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell
The web page https://errors.ubuntu.com/user/... will initially show no
results but updates after a few seconds. If you still see no results
after 10 seconds then next please provide a log by:
1. Wait for the crash to occur again.
2. Wait 10 seconds.
3. Reboot.
4. Run:
journalctl -b-1 >
** Description changed:
I upgrade to Ubuntu 22.04 recently, and while upgrading and updating I
also got a new bios version (1.69) for my Lenovo Thinkpad P50 laptop.
Since then gnome-shell has been very unstable, crashing regularly on
- minor changes, like plugging in a monitor or going to
--
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/1989325
Title:
gnome-shell crashes on Lenovo Thinkpad P50 after upgrade to 22.04.1
To manage notifications about this bug go to:
12 matches
Mail list logo
