Is your experience matching the one described on the gitlab ticket?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1964091
Title:
long touch/press a directory won't trigger the
I was testing in Wayland. Just test under X11, slightly better, but
still not useable.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1964091
Title:
long touch/press a directory
** Summary changed:
- long touch/press a director won't trigger the context menu like file on empty
space. on touch monitor
+ long touch/press a directory won't trigger the context menu like file on
empty space. on touch monitor
--
You received this bug notification because you are a member
Also fixed in
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/842
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1283
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1283
** Changed in: xorg-server
Remote watch:
Sounds like the fix is in mutter 42.beta
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2235
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Status: New => Fix Committed
** Tags added: fixed-in-mutter-42.beta
Tracking upstream in
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1306 or probably
more accurately:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1283
** No longer affects: gnome-shell (Ubuntu)
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1306
It looks like we're probably looking for a crash from 'Xwayland'.
** Tags added: wayland-session
** Also affects: xwayland (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xwayland (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
[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.
** Tags added: jammy regression
--
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/1964136
Title:
Settings item not shown in System menu
To manage notifications about this bug go
I'm not sure we should assign this to ubuntu-22.04-beta when it's only
ever been observed on 21.10.
--
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/1962346
Title:
Ubuntu
The OEM team seem to have this under control and I'm not planning on
doing any gdm3 work at all. But as a team we might want to keep an eye
on https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/171 and revisit
our defaults in the coming weeks.
** Changed in: gdm3 (Ubuntu)
Assignee: Daniel
That all said, I haven't seen any reason why we should do anything other
than go with upstream's gdm patches. If Wayland needs to be avoided in
some Nvidia setups then we should do so to get at least the login
screen.
I'm confused though, because some people have made comments suggesting
it
In a hybrid (usually muxless) laptop the BIOS will flag the Intel GPU is
the boot GPU, which means gnome-shell/mutter will flag that one as
"primary" and will do ALL shell rendering on it.
In a hybrid desktop/workstation the BIOS will *usually* disable the
integrated GPU leaving only the discrete
Hi Seb,
FWIK, the fix from gdm is not mandatory.
The display-manager (inside u-d-c) will handle it.
but if any flavor which doesn't use u-d-c then gdm upstream also provide this
commit
https://gitlab.gnome.org/GNOME/gdm/-/commit/ecbd9694458194e24f356ba9d37fc4f3a515c3dd#note_1402863
to fix this
Although duplicate bug 1964254 is gnome-shell 41.
** Summary changed:
- gnome-shell crashed with SIGSEGV at ?+a7c
+ gnome-shell crashed with SIGSEGV at ?+a7c called from [heap address]
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Looks the same as these, which are also new in gnome-shell 42:
https://errors.ubuntu.com/problem/72ac8d41c03462cc0271527dec039025218b46d4
https://errors.ubuntu.com/problem/644a6cc9e462a67db78caff5570888f0fc956d0b
https://errors.ubuntu.com/problem/f87fbdb8562f83f5a04d1b4910b46dc111548b00
Frame #1
*** This bug is a duplicate of bug 1964120 ***
https://bugs.launchpad.net/bugs/1964120
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 1964120, so it is being marked as such. Please
** Tags added: 2-in-1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1964091
Title:
long touch/press a director won't trigger the context menu like file
on empty space. on
** Changed in: gnome-shell (Ubuntu)
Milestone: None => ubuntu-22.04-beta
--
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/1962346
Title:
Ubuntu reboots instead of powering
Public bug reported:
System :
Ubuntu 21.10
Kernel 5.13.0-35
Session : Wayland
Each time I try to rip a CD with "abcde" gnome-shell crashes
What I understand from the logs :
Before the CD is ripped, abcde downloads a picture (from internet) as a cover
of the CD.
When tracker-extract discovers
Adding back gnome-shell as affected package for now. Leaving it to
others to decide which route to take. ;)
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => High
** Changed in: gnome-shell (Ubuntu)
Here are the results:
dhdurgee@z560:~/Downloads$ sudo apt remove libgail-common
[sudo] password for dhdurgee:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
$ sudo apt remove libgail-common
it's more of a workaround to try, but check what it would potential
remove also if anything
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1962807
How should I remove libgail-common? Could doing so cause other
problems?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1962807
Title:
segfault in libgtk-x11-2.0.so.0 with
I'm out of idea at this point, you could try to remove libgail-common
and see if that makes a difference but otherwise unsure why it's hitting
a segfault in the menu code...
** Changed in: gtk+2.0 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a
As I had not heard anything from you for a while I went ahead and
followed your directions
to return to the prior version as follows:
dhdurgee@z560:~/Downloads/debs$ sudo dpkg -i *.deb
[sudo] password for dhdurgee:
dpkg: warning: downgrading gir1.2-gtk-3.0:amd64 from 3.24.20-0ubuntu1.1
Stacktrace:
#0 0x7fc4fe18aa7c in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7ffd499cdaa0
StacktraceSource: #0 0x7fc4fe18aa7c in ?? ()
StacktraceTop: ?? ()
** Tags removed: need-amd64-retrace
--
You received this bug notification
Public bug reported:
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop:
@Jeremy, I'm unsure to understand your point, what do you suggest doing
exactly? The shell revert seems the safest way there, unless you want to
provide compat with different names but what is the win for the LTS
users exactly?
--
You received this bug notification because you are a member of
** Changed in: systemd (Ubuntu Jammy)
Status: New => In Progress
** Changed in: systemd (Ubuntu Jammy)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Here's a better list of affected packages:
https://codesearch.debian.net/search?q=gnome-control-center.desktop=1
The network-manager plugins are for AppStream metadata and it's pretty
easy to support both names there.
budgie-control-center can be ignored since it's just a fork of gnome-
-1 on doing the rename before the LTS, we are past feature freeze, a
check on the old name shows quite some reverse depends call to the name
to trigger the settings
https://codesearch.debian.net/search?q=org.gnome.ControlCenter
We could start patching the rdepends but that's not useful work, we
I did a review on the upstream MP that Daniel shared.
It looks to me that the upstream intend to disable Wayland in many of scenarios.
It contains a case:
(proprietary nvidia) + (hybrid graphics) + (laptop)
It make me feel curious that why only impact "hybrid laptop" but "hybrid
is there anything needed from gdm there?
--
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/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to race of gdm and
nvidia
gnome-control-center 42 changed its .desktop name. We either need to
backport that change to Jammy or revert gnome-shell 42's change. I
proposed the backport:
https://salsa.debian.org/gnome-team/gnome-control-
center/-/merge_requests/24
** Package changed: gnome-shell (Ubuntu) =>
** Changed in: gdm3 (Ubuntu)
Status: New => Incomplete
** Changed in: gdm3 (Ubuntu Focal)
Status: New => Incomplete
** Changed in: gdm3 (Ubuntu Impish)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Was fixed in
https://launchpad.net/ubuntu/+source/gnome-session/41.3-1ubuntu1
- Ensure that systemd is preferred on startup (LP: #1959596)
** Package changed: gnome-shell (Ubuntu Jammy) => gnome-session (Ubuntu
Jammy)
** Changed in: gnome-session (Ubuntu Jammy)
Status: Confirmed =>
Daniel, could you check what we need here?
** Changed in: gdm3 (Ubuntu)
Importance: Undecided => High
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: evince (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
Public bug reported:
Version (in jammy-proposed): 42~beta-1ubuntu1
Please see screenshot.
** Affects: gnome-shell (Ubuntu)
Importance: High
Status: New
** Attachment added: "system-menu.png"
https://bugs.launchpad.net/bugs/1964136/+attachment/5567026/+files/system-menu.png
Successful build logs for all PPA arches:
https://launchpad.net/~jbicha/+archive/ubuntu/arch/+sourcepub/13299512/+listing-archive-extra
The two reverted commits were easy enough to apply and feel like they
shouldn't interfere with pushing normal 42.* point releases to 22.04 LTS
later.
I believe
--
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/1947130
Title:
gnome-shell crashed with SIGSEGV in js::gc::Cell::storeBuffer from
JSObject::writeBarrierPost from
** Description changed:
Long press/touch a directory won't trigger the context menu for it.
OS: 22.04, up to date @ Mar 8, 2022.
nautilus: 1:42~beta-1ubuntu1
+ mode: wayland
With a touch monitor, it will be useful if we can do more operation with
it.
If I long press a file
Thank you for your bug report, is that under wayland or x11?
https://gitlab.gnome.org/GNOME/nautilus/-/issues/626 upstream seems
similar and suggests things should work slightly better under x11 if you
want to confirm
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #626
The latest jammy live images are still crashing even though they use
libmozjs-91-0 so I'll need to debug that to see if it's the same stack
trace.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
Long press/touch a directory won't trigger the context menu for it.
OS: 22.04, up to date @ Mar 8, 2022.
nautilus: 1:42~beta-1ubuntu1
With a touch monitor, it will be useful if we can do more operation with
it.
If I long press a file (for about 1 second), a context menu
The only difference is which GPU mutter/gnome-shell is trying to use as
"primary". According to the log in comment #2 it sounds like Nvidia is
indeed the primary here:
三 04 23:54:57 ubuntu-ThinkStation-P350-Tower gnome-shell[1127]: Added
device '/dev/dri/card1' (nvidia-drm) using non-atomic
*** This bug is a duplicate of bug 1868293 ***
https://bugs.launchpad.net/bugs/1868293
https://errors.ubuntu.com/problem/bc718fcc290d04f4e23c6246836d992f140e7058
is currently showing a stack trace that matches bug 1868293. Although if
it changes again (due to limitations/bugs in
Oops, yes, sorry.
** Tags added: fixed-in-42 fixed-upstream
--
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/1962523
Title:
[Wayland][Nvidia] gdm default use Xorg in 22.04 if
*** This bug is a duplicate of bug 1959888 ***
https://bugs.launchpad.net/bugs/1959888
Hi Daniel,
This issue is talking about I+N desktop.
It may not same as a hybrid laptop.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3
Hi Daniel,
The patch from comment#1 is from upstream.
https://gitlab.gnome.org/GNOME/gdm/-/commit/dda2fbb175ca00fc4f6c4e3c149464a570e1dca4
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
*** This bug is a duplicate of bug 1959888 ***
https://bugs.launchpad.net/bugs/1959888
** Tags added: hybrid multigpu wayland wayland-session
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Exactly, I wonder as well.
It worked fine in 20.04 and then after the upgrade it stopped working. The
truth is that during the upgrade process something went wrong and I had to
reboot. Then I continued the upgrade process again but who knows how things
work in such scenario. On the VM guest it
If you are using a desktop then this is not a bug. The brightness slider
is for laptop screens only.
If you are using a laptop then it most likely is a kernel bug.
** Tags added: jammy
** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you
This may mean gnome-shell has crashed.
Please:
1. Follow these instructions to check for crashes:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
2. Try to reduce the list of extensions as much as possible until you
find which extension is causing the
Curious. You should have received those packages already since they're
required by gnome-remote-desktop, which is recommended by ubuntu-desktop
and gnome-shell. Maybe this was an Ubuntu "minimal" installation, or
maybe it's a problem with upgrades?
** Changed in: gnome-shell (Ubuntu)
*** This bug is a duplicate of bug 1959888 ***
https://bugs.launchpad.net/bugs/1959888
While bug 1959888 is still open we should track it there.
** This bug has been marked a duplicate of bug 1959888
Wayland sessions can't use external monitors that are connected to an Nvidia
GPU with
Bug 1959888 is still open, awaiting either feedback from the user or for
me to confirm it.
As for this bug, please propose the patch to upstream first:
https://gitlab.gnome.org/GNOME/gdm/-/merge_requests
We don't want to conflict with their existing plans:
59 matches
Mail list logo
