Works for me.
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Invalid
--
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/2027844
Title:
opening
Public bug reported:
Unfortunately it appears that gimp catches segfaults and I can't figure
out how to disable that so I can't report this crash with appport.
Here's the bug information in the pop-up that gimp displays when it
catches the segfault:
```
GNU Image Manipulation Program version
Public bug reported:
The Python files in the indicator-keyboard package are being installed
in /usr/lib/python3.8 instead of /usr/lib/python3.10.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: indicator-keyboard 0.0.0+19.10.20190716-0ubuntu3
ProcVersionSignature: Ubuntu
Public bug reported:
In a brand new account created just to test this issue, gnome-terminal
has a dark background and light fonts even when the GNOME them is set to
light. I am not sure if this is a new issue in Jammy, but it sure is
frustrating that when I switch to light mode every app switches
Public bug reported:
Totem is crashing on launch.
I see in /var/crash that the crash was reported, with crash id
affaa5ef-11fd-11ed-a50a-fa163e55efd0, but when I try to run ubuntu-bug
on the crash file it reports this:
ERROR: hook /usr/share/apport/package-hooks/source_totem.py crashed:
Presumably it doesn't have a stack trace because it didn't upload
successfully. I don't know how to fix that.
It's crashing reliably for me but it isn't producing a new crash each
time in /var/crash, just the first one is there.
apport-cli isn't working either. I tell it to send the report and
OK, I installed debug symbols and ran totem inside gdb, and this looks
like the most common crash listed there, i.e., bug 1973570:
(gdb) where
#0 ___pthread_mutex_destroy (mutex=mutex@entry=0x0) at
./nptl/pthread_mutex_destroy.c:31
#1 0x77e282a0 in g_rec_mutex_impl_free (mutex=0x0) at
Public bug reported:
In Jammy, if I opened the system menu (click on system tray in top right
corner of screen) and clicked the little speaker icon it would mute my
audio, and then if I clicked again it would unmute.
That icon is no longer clickable in Kinetic.
ProblemType: Bug
DistroRelease:
Public bug reported:
I have GNOME configured to lock the screen when the screen is blanked,
and to blank the screen when the lid is closed:
org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank'
org.gnome.desktop.screensaver lock-delay uint32 0
org.gnome.desktop.screensaver
Public bug reported:
I have the shell configured to lock the screen when I close the lid and
go to sleep after 20 idle minutes on battery power.
Immediately before I opened my laptop and unlocked it to submit this
bug, the laptop was unplugged from battery power and sitting with the
lid closed
Public bug reported:
My desktop has wired ethernet and I keep Bluetooth disabled when I'm not
using it for security reasons. Because of this the shell decides I'm in
"Airplane mode" and highlights the button in the system tray menu and
sticks the airplane mode icon in the system tray. Even if I
Public bug reported:
When totem crashes and I try to report the crash with ubuntu-bug, one of
two things happens:
1) Sometimes after the dialog pops up and I click the "Send" button,
ubuntu-bug immediately exits without doing anything:
jik@jik5:~$ ubuntu-bug /var/crash/_usr_bin_totem.1000.crash
Public bug reported:
When I try to play a video with totem it either crashes or hangs my
display (mouse cursor still moves but nothing else works and I have to
reboot). The crash is inside nouveau drivers, so this may be a nouveau
bug rather than a totem bug. I can't report it with ubuntu-bug
Removing gstreamer1.0-vaapi does make this particular crash go away, but
then I get another one. See bug 1983483.
See also bug 1983481 about the fact that I was unable to report either
the crash in this bug or the crash in bug 1983483 with ubuntu-bug or
apport-cli.
--
You received this bug
1) Your comment does not address the stack trace I am getting, shown
above, from the apport script in totem-common.
2) The crash is not being uploaded successfully to the crash tracker
either; see
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1983294/comments/2
.
3) I understand that
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1983483/+attachment/5606794/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1983483/+attachment/5606793/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1983483/+attachment/5606792/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
When I try to play a video with totem it either crashes or hangs my
display (mouse cursor still moves but nothing else works and I have to
reboot). The crash is inside nouveau drivers, so this may be a nouveau
apport information
** Attachment added: "GstreamerVersions.txt"
https://bugs.launchpad.net/bugs/1983483/+attachment/5606791/+files/GstreamerVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
*** This bug is a duplicate of bug 1497593 ***
https://bugs.launchpad.net/bugs/1497593
Welp, I had disabled the proprietary nvidia driver because I use a
DisplayLink hub and DisplayLink was really unhappy about nvidia, but I
just tried it again with the current nvidia driver and it appears to
So far this is only happening on one of the three machines on which I
run current Lunar, and all three of the machines have different hardware
profiles, so I'm wondering if perhaps this isn't actually a gnome-shell
issue but rather a hardware issue. I've noticed that the machine on
which this
Public bug reported:
With recent gnome-shell in Lunar, some of my windows, seemingly at
random, are launching with weird title bars that don't reflect the title
bar settings I have configured.
E.g., the font in the title bar is not the same as for other windows,
and the buttons on the right when
Public bug reported:
In the short time since I've installed the recent GNOME updates in
Lunar, I've been logged out spontaneously at least three times while my
laptop lid was closed and screen locked and I wasn't doing anything with
my computer. Perhaps the attached logs will help you figure out
Well, that one was just closed, so removing the duplicate link because
otherwise this one won't get any attention?
** This bug is no longer a duplicate of private bug 2011426
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
This is happening for me on machines with a single display (laptop, no
external monitor connected), so if that other bug is accurate that it's
just about multi-monitor displays, then that's not the problem here.
I'll try without extensions and see what happens.
--
You received this bug
This appears to be fixed in current Lunar.
--
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/1990861
Title:
can no longer click on speaker icon in system tray menu to mute/unmute
Public bug reported:
In the short time I've had the newest GNOME updates for Lunar, my gnome-
shell has hung twice.
The first time I had just logged into a Google account in Chrome, and it
popped up the window asking me if I wanted to switch to a new Chrome
profile rather than logging into that
Public bug reported:
After the most recent Lunar updates (i.e., with the newest GNOME) my
gnome-shell got into a state where clicking on the title bar of a window
wouldn't raise the window (or do anything else), while clicking inside
the window raised it as expected. The problem went away after I
Nope I'm on the current 6.1 kernel.
--
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/2011317
Title:
gnome-shell spontaneously logging me out when screen locked, laptop
lid
Not 100% certain but I think this is one of the times I was
spontaneously logged out:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011426
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
I dug into this a little and encountered a whole slew of issues, such
that I'm really unsure how to file them or under what packages.
I'm using nvidia-driver-525 with one monitor plugged directly into the
back of my computer and a second monitor plugged into a DisplayLink hub.
The DisplayLink
I marked this as affecting gnome-shell as well as Emacs because the
problem of Emacs launching with a tiny window instead of the properly
sized window is occurring even when I downgrade to the older Emacs debs,
so that's apparently a problem with the new gnome-shell, not with the
new Emacs?
**
Note: the "Sometimes Emacs launches as a tiny window" issue happens
*even when Emacs is explicitly launched with -g 80x35 on the command
line*.
--
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:
1. Open Settings.
2. Go to Online Accounts.
3. Add a Google account, or if you already have one, click on it, to open the
Google Account window.
4. Toggle one of the rocker switches from on to off or vice versa.
5. Observe that at this point the window becomes unresponsive
** Attachment added: "same page which demonstrates this issue"
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2023588/+attachment/5679706/+files/sample.pdf
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
Public bug reported:
Just downloaded my credit card statement PDF and opened it with evince.
Fonts are all messed up. Tried mupdf; also messed up. Opened it in
Chrome, everything is fine. See attached screenshots of how a particular
paragraph in the PDF looks in Chrome, evince, and mupdf.
Also
Public bug reported:
1. Click the sound icon in the upper right corner of the screen.
2. Click the arrow next to the sound slider.
3. Select "Sound Settings".
4. Observe how the control panel window that opens up is empty.
5. If you then click on a different control center section and then click
OK, yes, it turns out that mouse focus vs. click focus is indeed the
differentiator for me, but it's a bit more complicated than that. If I
have focus set to mouse when I log in, then this bug manifests even if I
change focus to click. If I have focus set to click when I log in, then
this bug does
This issue is NOT fixed in 44.1-1ubuntu1. I don't know whether that's
because the fix from upstream didn't get included in that package
somehow, or whether the upstream bug is not actually the root cause of
the issue reported here. If I launch an emacs window with the new
version of mutter in
What do I do about the fact that I am unable to edit the status of the
bug to indicate that it is not fixed? File a new bug?
--
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/2013216
This bug is not fixed. Still happening for me in Xorg on Mantic.
--
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/2013216
Title:
Single click on title bar does not transfer focus to
Logged out, rebooted, made sure all packages are up-to-date, none of it
made a difference.
--
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/2013216
Title:
Single click on title bar
201 - 243 of 243 matches
Mail list logo
