*** This bug is a duplicate of bug 2063005 ***
https://bugs.launchpad.net/bugs/2063005
The Xorg log mentions "(**)" meaning some things like the touchscreen
(/dev/input/event5) are configured by a config file. Was that created by
hand or generated? Look in /usr/share/X11/xorg.conf.d
** Tags a
*** This bug is a duplicate of bug 2063005 ***
https://bugs.launchpad.net/bugs/2063005
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 2063005, so it is being marked as such. Please look
Has the test plan (https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs)
been executed? It's great that GNOME Shell seems stable, but there are
other consumers of gjs that need testing.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs
** Description changed:
[ Impact ]
gnome-shell crashes with SIGSEGV in st_theme_node_lookup_shadow() when
the screen is locked from the overview, if you had any extension loaded
- that changes stylesheets (like ubuntu-dock or dash-to-dock).
+ that changes stylesheets (like ubuntu-dock or
** Description changed:
[ Impact ]
gnome-shell crashes with SIGSEGV in st_theme_node_lookup_shadow() when
the screen is locked from the overview, if you had any extension loaded
that changes stylesheets (like ubuntu-dock or dash-to-dock). In theory
it could happen whenever such an ext
*** This bug is a duplicate of bug 2037055 ***
https://bugs.launchpad.net/bugs/2037055
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
46.0-0ubuntu6~24.04.1, the problem
*** This bug is a duplicate of bug 2037055 ***
https://bugs.launchpad.net/bugs/2037055
** This bug has been marked a duplicate of bug 2037055
gnome-shell crashed with SIGABRT:
ERROR:../src/shell-app.c:1644:shell_app_dispose: assertion failed: (app->state
== SHELL_APP_STATE_STOPPED)
--
Y
Oh this is going to be stuck behind 46.0-0ubuntu6~24.04.1 which has
stopped phasing due to bug 2075309 :(
--
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/2069559
Title:
gnome-sh
*** This bug is a duplicate of bug 2037055 ***
https://bugs.launchpad.net/bugs/2037055
Despite what
https://errors.ubuntu.com/problem/352b5b0892c4a5f7cd9b445d91d146119a2837e9
says, this is not new. It was already a known issue in
https://errors.ubuntu.com/problem/1abaaf46c8b70b1fc87278bec9e4d2
** Description changed:
+ https://errors.ubuntu.com/problem/1abaaf46c8b70b1fc87278bec9e4d2cefc15daaf
+ https://errors.ubuntu.com/problem/352b5b0892c4a5f7cd9b445d91d146119a2837e9
+
Running MATLAB 2023b with Matlab Connector installed suddenly crashed
gnome-shell and returned to gdm. Has been r
Public bug reported:
I'm using Alt+Shift keys to change layout, not default Super+Space
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nautilus 1:46.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset
Public bug reported:
As title says: sometimes when I disconnect my laptop from DisplayPort-
over-USBC monitor desktop goes to black screen (sometimes with cursor
available, but only the cursor!), and over the time I've found out that
opening a tty session and executing a `killall gnome-shell` brin
I do have a user process running on Ubuntu 24.04 LTS and 24.10
/usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f
Perhaps try if you can reproduce this issue on a clean Ubuntu install or
on a clean system upgraded from previous Ubuntu releases.
On my Android phone, I do see a popup "Allow access to
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: webkit2gtk (Ubuntu Artful)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscri
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: evolution (Ubuntu Artful)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscr
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: evolution-data-server (Ubuntu Artful)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whi
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: snapd-glib (Ubuntu Artful)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is sub
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: snapd-glib (Ubuntu Artful)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is sub
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: gnome-software (Ubuntu Artful)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is s
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: gtk+3.0 (Ubuntu Artful)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscrib
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: gnome-software (Ubuntu Artful)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subsc
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: ibus-libpinyin (Ubuntu Artful)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribe
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: gnome-software (Ubuntu Artful)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: epiphany-browser (Ubuntu Artful)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is sub
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: gdm3 (Ubuntu Artful)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: gtk+3.0 (Ubuntu Artful)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed t
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: mutter (Ubuntu Artful)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: gnome-software (Ubuntu Artful)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is sub
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: snapd-glib (Ubuntu Artful)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscri
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: evolution (Ubuntu Artful)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscr
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: gnome-software (Ubuntu Artful)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subsc
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: gnome-control-center (Ubuntu Artful)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: mutter (Ubuntu Artful)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: gnome-software (Ubuntu Artful)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is sub
Public bug reported:
crash on startup of nautilus
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nautilus 1:46.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
Uname: Linux 6.8.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3
I'll try to reproduce with a clean profile when I have a moment.
In the meantime, could you tell me what systemd user unit the process is
part of on your system? I don't see anything in the gvfs-fuse package
itself that would start it as part of a user session.
--
You received this bug notificat
The trigger may be when a) the screen is locked, and b) the screen
blacks out. Logging back in after this leads to the flickering black
rectangle at the top of the secondary monitor. This occurs without any
use of SDL.
Switching the monitor off and on does not fix the problem. Disconnecting
and re
$ systemctl status --user gvfs-daemon.service
● gvfs-daemon.service - Virtual filesystem service
Loaded: loaded (/usr/lib/systemd/user/gvfs-daemon.service; static)
Active: active (running)
Main PID: 3721 (gvfsd)
CGroup:
/user.slice/user-1000.slice/user@1000.service/session.slice
GNOME restarting when you unplug the monitor is a bug. Likely bug
2050865.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Thanks for the bug report.
I don't think the above log messages are relevant to the main problem
here. Please start by removing all local extensions:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again. If the problem continues to happen then next time
it does, after bring
40 matches
Mail list logo
