** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1018
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018
Importance: Unknown
Status: Unknown
--
You received this bug notifica
The verification of the Stable Release Update for glib2.0 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package glib2.0 - 2.56.4-0ubuntu0.18.04.2
---
glib2.0 (2.56.4-0ubuntu0.18.04.2) bionic; urgency=medium
* Backport upstream patches to fix GVariant alignment tests
d/p/gvariant-test-Also-force-alignment-for-tuple-test-data.patch,
d/p/tests-Allocate-g
The verification of the Stable Release Update for glib2.0 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package glib2.0 - 2.56.4-0ubuntu0.18.04.2
---
glib2.0 (2.56.4-0ubuntu0.18.04.2) bionic; urgency=medium
* Backport upstream patches to fix GVariant alignment tests
d/p/gvariant-test-Also-force-alignment-for-tuple-test-data.patch,
d/p/tests-Allocate-g
** Description changed:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018
https://gitlab.gnome.org/GNOME/gnome-shell/issues/804
+
+ [ Impact ]
+
+ - GNOME Shell crashes in st_widget_get_theme_node
+
+
+ [ Test Case ]
+
+ - No clear test case for this, monitoring errors.ubuntu.com i
Public bug reported:
It has long been known that #1164016 has regressed, but for some reason
nobody yet has changed back the status of the bug from "fix released",
so (since I can't do that) I'm opening a new one.
Feel free to mark this as duplicate if (and only if) #1164016 is
reopened.
All the
> The Gnome team is extremely resistant to bring back the old intuitive
> functionality.
> I tried to explain the problems at
> https://gitlab.gnome.org/GNOME/nautilus/issues/244
> , as did many others.
Trying to reason with the Gnome team is a complete waste of time.
That's why Ubuntu should
** 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/1796606
Title:
gnome-shell crashed with SIGSEGV in st_widget_get_theme_n
This crash seems to be fixed in this commit, included in gnome-session 3.30.0:
https://github.com/GNOME/gnome-session/commit/3aafcf0f0129e28b5c52f32284f1164a93867ea3
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubun
apport is enabled.
>From /var/log/apport.log.1:
ERROR: apport (pid 3078) Wed Apr 24 08:55:18 2019: called for pid 2699, signal
5, core limit 0, dump mode 1
ERROR: apport (pid 3078) Wed Apr 24 08:55:18 2019: executable:
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR: apport (pi
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503
** Also affects: gnome-control-center via
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Deskto
Public bug reported:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503
---
[Impact]
When I try to set the pen on my touch screen. gnome-control-center crashes.
[Fix]
That you can configure the pencil to later occupy it with my touch screen.
[Test Case]
1. Open gnome-control-center
** Changed in: mutter
Status: New => Fix Released
--
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/1813716
Title:
gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisp
Uninstalled xorgxrdp, no change:
/var/log/apport.log:
ERROR: apport (pid 3174) Tue Apr 30 16:47:43 2019: called for pid 2790, signal
5, core limit 0, dump mode 1
ERROR: apport (pid 3174) Tue Apr 30 16:47:43 2019: executable:
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR: appor
** Attachment added: "_usr_bin_nautilus.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1827158/+attachment/5260436/+files/_usr_bin_nautilus.1000.crash
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in
Public bug reported:
widon@widon-X555YI:/var/log$ dpkg -l | grep nautilus
ii nautilus 1:3.26.4-0~ubuntu18.04.4
amd64file manager and graphical shell for GNOME
I don't how to reproduce it, it happens when I copy some picture from
** Tags added: disco
--
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/1796606
Title:
gnome-shell crashed with SIGSEGV in st_widget_get_theme_node →
ffi_call_unix64 → ffi_call →
Yeah, we seem to only be getting crash reports from 3.28 (bionic) now...
https://errors.ubuntu.com/problem/32ef08d11dc442f40fddf95eb9a987d2dd02425a
** Also affects: gnome-session (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: gnome-session (Ubuntu Eoan)
Importance
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
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/1827154
Title:
gnome-control-center crashe
I added the newest journalctl to the post above, and here's the entire
thing.
** Description changed:
After installing an update for Ubuntu 18.04 LTS, GNOME's App Launcher
screen faces graphical issues when scrolling. To reproduce this, simply
open the Application menu and scroll in the pag
I would say remove Yaru here. The theme can't directly control whether
the dialog is too small and needs wrapping. Although it can control the
dialog size indirectly with some tweaks, but doing that would be a hack.
I think this is a pure Gnome Shell bug.
--
You received this bug notification be
I can't see any history of a fix. But it's only reported in 3.28 here
and 3.30 upstream...?
--
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/1809788
Title:
Shell dialog messages
Tracking upstream in https://gitlab.gnome.org/GNOME/gnome-
shell/issues/922
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #922
https://gitlab.gnome.org/GNOME/gnome-shell/issues/922
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/issues/922
Impo
** Changed in: gnome-control-center
Status: Unknown => New
--
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/1827154
Title:
gnome-control-center crashed with SIGSE
** Changed in: gvfs
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1824738
Title:
gvfsd-admin crashed with signal 5
To manage notifications about t
** 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/1809788
Title:
Shell dialog messages are truncated and ellipsized...
To
Please try:
(1) Updating your system, since the fix mentioned in comment #1 should
now be included in 18.04 updates. Maybe this bug has been fixed.
(2) If you do restart gnome-shell and find that improves performance,
then wait another 30 seconds or more and retest. Does it get slower
again after
that does never work for me
`sudo /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 93
fish: “sudo /usr/lib/gnome-settings-da…” terminated by signal SIGSEGV (Address
boundary error)
`
gsd-backlight-h[19085]: segfault at 0 ip 7f7235fe25ee sp 7fff88c62278
error 4 in libc-
It appears this message keeps happening with the gnome-shell crash:
"Impossible to lock surface front buffer: Function not implemented"
that's from mutter's "native" (Wayland) backend:
next_bo = gbm_surface_lock_front_buffer (gbm_surface);
if (!next_bo)
{
g_error ("Impossible to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/182
** Package changed: gnome-shell (Ubuntu) => mesa (Ubuntu)
--
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/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surface f
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1826
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1826025
Title:
gnome-shell trap int3 no
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
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/1826025
Tracking upstream (I think) in
https://gitlab.gnome.org/GNOME/mutter/issues/57
** Package changed: gdm3 (Ubuntu) => linux (Ubuntu)
** Summary changed:
- gnome-shell trap int3 no desktop (MGA G200eW fails when calling
gbm_surface_lock_front_buffer)
+ gnome-shell trap int3 no desktop (Matrox MGA
** Package changed: glib2.0 (Ubuntu) => mutter (Ubuntu)
--
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/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surface f
** No longer affects: linux (Ubuntu)
** Summary changed:
- gnome-shell trap int3 no desktop (Matrox MGA G200eW fails when calling
gbm_surface_lock_front_buffer)
+ gnome-shell trap int3 no desktop ("Impossible to lock surface front buffer:
Function not implemented" on Matrox graphics card)
** C
*** This bug is a duplicate of bug 1809407 ***
https://bugs.launchpad.net/bugs/1809407
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 1809407, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1826201 ***
https://bugs.launchpad.net/bugs/1826201
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 1826201, so it is being marked as such. Please look
Also, to avoid Wayland fully, please edit /etc/gdm3/custom.conf and
uncomment:
#WaylandEnable=false
then reboot.
--
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/1826025
Title:
gn
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
--
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/1827059
Title:
Gnome-shell won't lock screen anymore
To
Public bug reported:
Attempting to install lyx from command-line with sudo apt install.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: desktop-file-utils 0.22-1ubuntu5.2
ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177
Uname: Linux 4.4.0-146-generic x86_64
ApportVersion: 2.20
** Tags removed: need-duplicate-check
--
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/1827169
Title:
package desktop-file-utils 0.22-1ubuntu5.2 failed to install/upgrade:
** Changed in: mutter
Status: Unknown => 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/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surface front
The problem seems not to be Ubuntu specific.
https://bugzilla.redhat.com/show_bug.cgi?id=1696788
(I get those "Recursion depth exceeded calculating {bg,fg} color"
messages too on eoan and disco.
** Bug watch added: Red Hat Bugzilla #1696788
https://bugzilla.redhat.com/show_bug.cgi?id=1696788
I didn't know how to log into "Ubuntu" instead of "Ubuntu on Wayland"
since I only got a blinking cursor and no logon prompt. I edited
/etc/gdm3/custom.conf and rebooted.
Successfully got a GUI logon prompt and was able to log in to the
desktop.
--
You received this bug notification because you
Great!
By the way, one possible reason why you were unable to follow comment #2
is that gdm is designed to catch mutter/gnome-shell crashes in the
Wayland backend (which it tries first). If such a crash occurs then it
is meant to automatically fall back to Xorg.
Regardless of whether the automati
** Merge proposal linked:
https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/36
--
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/1813716
Title:
gnome-s
** Changed in: gnome-shell (Ubuntu Disco)
Status: New => In Progress
** Changed in: mutter (Ubuntu Disco)
Status: New => In Progress
** Description changed:
+ [ Impact ]
+
+ GNOME Shell crashes on restart or when ending the session
+
+ [ Test Case ]
+
+ Under X11, try to reload
Launchpad has imported 2 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1696788.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://hel
Also gst-play-1.0 seems to work fine, and that does use gstreamer-vaapi.
So maybe the bug here is more Totem-specific in package
'gstreamer1.0-clutter-3.0'?
** Also affects: clutter-gst-3.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: clutter-gst-3.0 (Ubuntu)
Status
** Changed in: gnome-shell (Ubuntu)
Status: Triaged => In Progress
--
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/1826797
Title:
[regression] gnome-shell crashes if boot
** Also affects: gnome-shell (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu Disco)
Status: New => In Progress
** Changed in: gnome-shell (Ubuntu Disco)
Importance: Undecided => High
** Changed in: gnome-shell (Ubuntu Disco)
Assignee:
** Merge proposal linked:
https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/38
--
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/1826797
T
** Description changed:
+ [ Description ]
+
Ubuntu 19.04
DisplayLink properietary driver installed.
Log in to GNOME desktop in Wayland mode. Hotplug a DisplayLink USB dock
with one monitor connected.
What happens: The desktop session shuts down and throws me back into the
log
** Description changed:
+ [ Impact ]
+
On a fresh install of Ubuntu 19.04 applications that are started from the
dash inside a Wayland session often do not receive focus.
The behavior is inconsistent. Some applications (like the terminal) always
properly get the focus. Some like GEdit en Ch
** Description changed:
+ [ Impact ]
+
From time to time, my chrome icon disappears in gnome shell 3.32,
leaving only the "open window indicator" below it. It's the first of my
icons, and this is running a vanilla gnome session.
- ProblemType: Bug
- DistroRelease: Ubuntu 19.04
+ [ QA ]
+
** Description changed:
+ [ Impact ]
+
+
+ Touching and dragging an icon on the dock blocks input to other apps Edit
+
+ [ Test case ]
+
+ - make sure the Ubuntu dock is visible
+ - Using a finger drag, for example, a LibreOffice icon up and down the dock
and then drop
+ it on Nautilus.
These also have the bug:
gst-play-1.0 --videosink clutterautovideosink
gst-play-1.0 --videosink glimagesink
but these do not:
gst-play-1.0 --videosink ximagesink
gst-play-1.0 --videosink xvimagesink
That confirms the problem is not specific to totem or
gstreamer1.0-clutter-3.0.
** No
It seems that in a second log in, Guake does not start. Only in the
first login after adding it. And it does not seem like opening the
Startup Applications is the cause of its removal.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gn
- Logged in.
- Guake did start.
- Opened Startup Applications.
- Item is not there.
```
➜ ~ git:(master) ✗ ls -l ~/.config/ | grep autostart
drwxr-xr-x 2 shahar shahar 4096 May 1 13:25 autostart
➜ ~ git:(master) ✗ ls -l ~/.config/autostart
total 16
-rw-rw-r-- 1 shahar shahar 204 May 9
I did not have the problem in cosmic. Since I upgraded from bionic to
cosmic and then immediately to disco, I did not notice whether this bug
was introduced in cosmic or disco.
Example item would be:
Name: Guake
Command: guake
Will now re-test:
- Opening Startup Applications.
- Item is not ther
- Logged out again.
- Logged in again.
- Guake did not start.
- Opened Startup Applications.
- Added Guake.
- Logged out and back in.
- Guake did start.
So, it seems that it lasts one login and then disappears? Or is it the
opening of the Startup Applications that makes it disappear? I'll check.
101 - 164 of 164 matches
Mail list logo
