Hi,
This crash is still present in the latest gnome-shell version
3.28.4-0ubuntu18.04.1
--
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/1813173
Title:
gnome-shell crashed with
The attached file JournalErrors.txt suggests the GPaste extension might
be the most suspicious extension:
яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: == Stack trace for
context 0x55db415214d0 ==
яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #0 0x7fff6837e650 I
resource:
Yes, that does seem to be the problem, most likely. The only calls to
'get_child_meta' in gnome-shell are in environment.js, which seems to be
called from the GPaste extension per the above comment.
I recommend uninstalling the GPaste extension.
--
You received this bug notification because you
It appears this crash is not very common, suggesting it might be related
to some extension(s).
You seem to have installed:
'weatherinthecl...@jasonlg1979.github.io'
'gpa...@gnome-shell-extensions.gnome.org'
'sound-output-device-choo...@kgshank.net'
so please try uninstalling those completely, an
** Tags added: nvidia-drm.modeset
--
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/1716857
Title:
gdm3, hybrid nvidia with modeset=1, no external monitors detected
To manage notifica
Public bug reported:
## Issue
In certain case, system wake-up from suspend will suspend again automatically.
The issue comes from a target machine turning auto-suspend on and
suspends after the idle time-out. Manually suspend, e.g., click suspend
icon or execute "systemctl suspend" won't reproduc
In a more pure development environment, I can confirm this bug without
needing hybrid GPUs, or gdm3.
Just the Nvidia driver and Xorg results in no outputs/monitors detected:
$ xrandr
Screen 0: minimum 8 x 8, current 640 x 480, maximum 16384 x 16384
To work around the problem I need to run Xorg a
For a full list of reasons to not use nvidia-drm.modeset=1 right now, please
see:
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-drm.modeset
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.laun
Sounds like the root cause here is the same as bug 1716857.
** Changed in: gdm3 (Ubuntu)
Status: Confirmed => Invalid
--
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/1769857
Titl
*** This bug is a duplicate of bug 1716857 ***
https://bugs.launchpad.net/bugs/1716857
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1716857, so it is being marked as such. Please look
Also, it sounds like the root cause here is the same as bug 1769857.
--
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/1716857
Title:
nvidia-drm.modeset=1 results in no monitors detect
Hi Daniel, thanks for not forgetting about this, unlike everyone else :)
Have you communicated this observation to Nvidia 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/1716857
Not yet. I am just untangling more Nvidia bugs today.
Also, I forgot to mention that you CAN run Xorg+Nvidia and see your
monitors as non-root. But only after you have started and stopped Xorg
as root beforehand. Something gets remembered, maybe in $HOME somewhere?
--
You received this bug notif
I will post your findings to the nvidia developers forum.
--
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/1716857
Title:
nvidia-drm.modeset=1 results in no monitors detected by Xorg
** No longer affects: gdm3 (Debian)
** Tags added: eoan
--
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/1716857
Title:
nvidia-drm.modeset=1 results in no monitors detected by Xorg
Comment #116 appears to be linking to the wrong bug. That link is for
nvidia-drm.modeset=1 and this bug is specifically about when you don't
have that set, like the default.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell i
-black
+blank
Because on Ubuntu 19.10 it's purple. Still the same bug though.
** Summary changed:
- Ubuntu boots to black screen when using Nvidia drivers (on a desktop with an
Intel GPU)
+ Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an
Intel GPU)
** Tags removed
Two years later...
I am reviewing this bug again today. I can confirm it's still in Ubuntu
19.10. And I can confirm that comment #19 was right. See comment #19.
** Summary changed:
- Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an
Intel GPU)
+ Ubuntu boots to blank
Also, just a reminder: If anyone is using a multi-GPU desktop machine
then please see bug 1705369 instead.
** Summary changed:
- Ubuntu login screen never appears when using the Nvidia driver (and setting
WaylandEnable=false fixes it)
+ Ubuntu login screen sometimes doesn't appear on a single GP
** Changed in: gnome-shell
Status: Unknown => 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/1705369
Title:
Ubuntu boots to blank screen when using Nvidia (on a desk
I posted here:
https://devtalk.nvidia.com/default/topic/1055528/linux/nvidia-driver-in-
modeset-1-requires-root-permissions-daniel-van-vugt-canonical-concludes-
it-is-an-nvidia-bug/?offset=3#5351122
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is s
User generix reports that when gdm3 is compiled without wayland support,
this bug is not seen.
--
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/1716857
Title:
nvidia-drm.modeset=1 res
** Changed in: oem-priority
Status: Triaged => Fix Released
--
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/1772811
Title:
[SRU] different behaviors for switch display mo
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Confirmed
--
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/1831356
Title:
Settings crashes when
Issue may get closed.
Solved with upgrading to Ubuntu 19.04.
Nevertheless thanks for your help.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1782535
Title:
cifs - poor upload s
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-menus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-menus in Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
I've reported this upstream (https://gitlab.gnome.org/GNOME/gnome-
shell/issues/1370), but given that this is an important part of the
Ubuntu desktop and that you're providing some patches for improving the
X11 experience with hidpi monitors, I'm notifying about the issue here
I've changed `baseIconSizes` from the looking glass and I get bigger
icons. This doesn't seem to be hard to fix really. Maybe the size
restriction should be checked *before* scaling up 2x. Maybe bigger icons
should be allowed.
--
You received this bug notification because you are a member of Ubun
Public bug reported:
I've tried this in two different hidpi monitors with different scaling
configurations:
1) A 1920x1080 screen with scale factor 1x and font scale factor 1.25.
2) A 3000x2000 screen with scale factor 2x.
In the first one, icons are too small, I have to change:
this._iconB
I've reported this in github also: https://github.com/ubuntu/gnome-
shell-extension-appindicator/issues/181. I'm not sure which is the
better place since upstream = distro here.
** Bug watch added: github.com/ubuntu/gnome-shell-extension-appindicator/issues
#181
https://github.com/ubuntu/gnome
See my report https://bugs.launchpad.net/ubuntu/+source/gnome-shell-
extension-appindicator/+bug/1832793
Indeed PANEL_ICON_SIZE is the wrong way to compute the icon size.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-ex
Nvidia 430.26 behaves a bit differently. It just fails to start as non-
root and gives reasons:
[ 897.467] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not
permitted)
...
[ 897.470] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please
see the
[ 897.470] (EE) NVIDI
** Tags added: hidpi
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1370
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1370
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1370
Importance: Unknown
Status: Unknown
--
You rece
** Tags added: hidpi
--
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/1831161
Title:
App-switcher icons too small with hidpi monitor and 1.25 scaling
To manage notifications abo
** Changed in: gnome-shell
Status: Unknown => 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/1832792
Title:
App-switcher icons too small with hidpi (3000x2000) monit
[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:/
[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:/
[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:/
How to reproduce this ?
Previously crash was in `nautilus_window_slot_get_location` which is now
fixed upstream.
With 3.32.1-1ubuntu1, I can't reproduce with G_MESSAGES_DEBUG=all
/usr/bin/nautilus. Can you copy/paste error as I don't have access?
But we don't really to update windows locations w
39 matches
Mail list logo
