[Bug 2027844] Re: opening sound settings from GNOME top menu yields blank control center

[Jonathan Kamens]

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 sound settings from GNOME top menu yields blank control center

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2027844/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2034942] Re: Hanging every time I attempt to add a Google account in GNOME control center

[Jonathan Kamens]

Tried building gnome-control-center from source and running gnome-
control-center-goa-helper under valgrind, no memory errors detected.

-- 
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/2034942

Title:
  Hanging every time I attempt to add a Google account in GNOME control
  center

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2034942/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2034942] [NEW] Hanging every time I attempt to add a Google account in GNOME control center

[Jonathan Kamens]

Public bug reported:

I've tried about 15 times in a row now to add a Google account in GNOME
control center, and every time it has hung at some point in the process
before letting me enter my password.

Sometimes it hangs before it even asks for my Google username.
Sometimes it hangs right after it accepts my username, before displaying the 
password prompt.
Sometimes it displays the password prompt but hangs before I am able to enter 
my password.

Sometimes when it hangs I see the message "GLib: unsetenv() is not
thread-safe and should not be used after threads are created" in
journalctl --user --follow output. I wonder if there is a memory
corruption issue attributable to that. :shrug:

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-control-center 1:45~rc-1ubuntu2
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep  8 12:11:52 2023
InstallationDate: Installed on 2019-01-02 (1710 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to mantic on 2023-05-20 (111 days ago)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug mantic third-party-packages

-- 
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/2034942

Title:
  Hanging every time I attempt to add a Google account in GNOME control
  center

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2034942/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2034724] Re: minimize, maximize, close buttons in title bar become invisible

[Jonathan Kamens]

*** This bug is a duplicate of bug 2002624 ***
https://bugs.launchpad.net/bugs/2002624

I am not able to reproduce this merely by locking and unlocking my
screen so I don't think this is the same as #2002624.

-- 
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/2034724

Title:
  minimize, maximize, close buttons in title bar become invisible

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034724/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2034724] Re: minimize, maximize, close buttons in title bar become invisible

[Jonathan Kamens]

I believe so. For example I believe I've noticed it in the Settings app.
I will keep an eye out and confirm here when I see it in another app.

-- 
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/2034724

Title:
  minimize, maximize, close buttons in title bar become invisible

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034724/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2034724] Re: minimize, maximize, close buttons in title bar become invisible

[Jonathan Kamens]

** Attachment added: "2023-09-07_11-35.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034724/+attachment/5698315/+files/2023-09-07_11-35.png

-- 
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/2034724

Title:
  minimize, maximize, close buttons in title bar become invisible

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034724/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2034724] [NEW] minimize, maximize, close buttons in title bar become invisible

[Jonathan Kamens]

Public bug reported:

Recently when I go to minimize, maximize, or close a window (I have the
minimize and maximize buttons enabled in Tweaks) I discover that the
buttons are invisible. I know they're there, just invisible, because I
can click where they should be visible and the expected thing happens.
If I quit and restart the application in question the buttons become
visible again. This only affects some windows (usually just one) at any
given time, not all of my windows. See attached screenshots for an
example of what I'm talking about.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45~beta.1-0ubuntu2
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep  7 11:37:40 2023
DisplayManager: gdm3
InstallationDate: Installed on 2019-01-02 (1709 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-05-20 (110 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug mantic third-party-packages

** Attachment added: "2023-09-07_11-34.png"
   
https://bugs.launchpad.net/bugs/2034724/+attachment/5698308/+files/2023-09-07_11-34.png

-- 
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/2034724

Title:
  minimize, maximize, close buttons in title bar become invisible

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034724/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2033902] Re: GNOME screen sharing completely borked with recent Mantic updates

[Jonathan Kamens]

This was a PEBKAC issue. I was opening the Unity sharing control panel
instead of the GNOME sharing control panel.

I have no idea why the Unity sharing control panel is still on my computer. I 
thought unity was gone. ;-)
Is it safe to remove it?


** Changed in: gnome-control-center (Ubuntu)
   Status: New => 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/2033902

Title:
  GNOME screen sharing completely borked with recent Mantic updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2033902/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2033901] Re: gnome-shell regularly showing the "Oops! Something went wrong/ logout" screen after Alt-F2 r RET

[Jonathan Kamens]

1) Is crash reporting fixed? Ref:
https://bugs.launchpad.net/launchpad/+bug/2033653

2) Do you still need the crash report given your comment above?

-- 
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/2033901

Title:
  gnome-shell regularly showing the "Oops! Something went wrong/ logout"
  screen after Alt-F2 r RET

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2033901/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2033902] [NEW] GNOME screen sharing completely borked with recent Mantic updates

[Jonathan Kamens]

Public bug reported:

The most recent Mantic turned off Screen Sharing, which was previously
turned on.

When I go to turn it on in the sharing control panel, i see that sharing
is completely disabled, i.e., the rocker switch at the top of the window
is off, presumably because the only kind of sharing I had enabled was
screen sharing, i.e., I didn't have media sharing enabled, so presumably
once screen sharing was turned off sharing in general turned off.

So I turn that top rocker switch back on, and now I need to configure
screen sharing, which still says it's off, so I click on that.

The window that comes up says VNC, which is *VERY* strange since we
quite a while ago switched from VNC to RDP, right? Why has it reverted
to VNC?

But in any case I can't do anything at this point. The rocker switch in
the upper left corner of the screen sharing pop-up won't let me turn it
on. The rocker switch next to my network connection won't let me turn it
on. And there's no way to close the pop-up! I have to kill the settings
app to make it go away at this point.

This is bad.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45~beta.1-0ubuntu2
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep  1 09:59:39 2023
DisplayManager: gdm3
InstallationDate: Installed on 2019-01-02 (1703 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-05-20 (104 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug mantic regression-release third-party-packages

-- 
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/2033902

Title:
  GNOME screen sharing completely borked with recent Mantic updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2033902/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2033901] [NEW] gnome-shell regularly showing the "Oops! Something went wrong/ logout" screen after Alt-F2 r RET

[Jonathan Kamens]

Public bug reported:

With the most recent Mantic updates gnome-shell is regularly, but not
every time, crashing and showing me the "Oops!" screen and forcing a
logout when I type Alt-F2 r RET (using X11, obviously, since AFAIK that
still isn't supported in Wayland).

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45~beta.1-0ubuntu2
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep  1 09:57:07 2023
DisplayManager: gdm3
InstallationDate: Installed on 2019-01-02 (1703 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-05-20 (104 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug mantic regression-release third-party-packages

** Tags added: regression-release

-- 
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/2033901

Title:
  gnome-shell regularly showing the "Oops! Something went wrong/ logout"
  screen after Alt-F2 r RET

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2033901/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2031907] Re: gimp is segfaulting on startup

[Jonathan Kamens]

Well, _this_ is fascinating.

I downloaded and built gimp from source:

sudo apt install dpkg-dev devscripts
cd /tmp
sudo apt source gimp
sudo apt build-dep gimp
cd gimp-2.10.34
sudo debuild

Then I modified app/gimp-2.10 to use "exec gdb" instead of "exec" to run
gimp.

Then I made sure gdb would be able to find the source code:

sudo ln -s /tmp/gimp-2.10.34 /usr/src/gimp-2.10.34-1

Then I ran app/gimp-2.10 and reproduced the crash.

The money shot:

(gdb) up
#3  0x5599df5a in gimp_object_name_normalize (object=0x5800b2b0)
at core/gimpobject.c:399
399   gchar *key = g_utf8_collate_key (object->p->name, -1);
(gdb) print object->p->name
$4 = (gchar *) 0x58082ad0 "Logitech a\267\342\004"

Well, that certainly looks like a string missing a null terminator, eh?

And then I made the crash go away... by unplugging my Logitech mouse's
USB dongle and plugging it back in.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/2031907

Title:
  gimp is segfaulting on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2031907/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2031907] Re: gimp is segfaulting on startup

[Jonathan Kamens]

I ran gimp under gdb and got the more useful stack trace below, though
there still isn't enough info to figure out what's going on.

#0  __wcslen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:76
#1  0x76ad0d8e in __GI___wcsxfrm_l
(dest=0x0, src=0x0, n=0, l=) at ../string/strxfrm_l.c:676
#2  0x76ede8be in g_utf8_collate_key ()
at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x55994fab in gimp_object_name_normalize (object=0x57d8ae10)
at core/gimpobject.c:399
#4  0x557a19a0 in gimp_object_name_collate
(object2=0x57d8ae10, object1=0x57daeea0) at core/gimpobject.c:387
#5  gimp_device_info_compare (a=0x57daeea0, b=0x57d8ae10)
at widgets/gimpdeviceinfo.c:942
#6  0x76ebc375 in g_queue_insert_sorted ()
at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x55994f09 in gimp_list_add
(container=0x57e0c610, object=0x57d8ae10) at core/gimplist.c:261
#8  0x76fa5130 in g_closure_invoke ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x76fd25f0 in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x76fc39b1 in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x76fc3bd6 in g_signal_emit_valist ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x76fc3c93 in g_signal_emit ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x5591ec43 in gimp_container_add
(container=0x57e0c610, object=0x57d8ae10)
at core/gimpcontainer.c:632
#14 0x557a8a6c in gimp_device_manager_device_added
(manager=0x57e0c610, device=0x55f835d0, gdk_display=0x55f89be0)
at widgets/gimpdevicemanager.c:423
#15 gimp_device_manager_display_opened
(disp_manager=, manager=0x57e0c610, 
gdk_display=0x55f89be0) at widgets/gimpdevicemanager.c:360
#16 gimp_device_manager_display_opened
(disp_manager=, gdk_display=0x55f89be0, 
manager=0x57e0c610) at widgets/gimpdevicemanager.c:334
#17 0x557a8b36 in gimp_device_manager_constructed
(object=0x57e0c610) at widgets/gimpdevicemanager.c:168
#18 0x76fb52c3 in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#19 0x76fb7273 in g_object_new_valist ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#20 0x76fb75cd in g_object_new ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#21 0x557a77d5 in gimp_device_manager_new
(gimp=gimp@entry=0x56031b40) at widgets/gimpdevicemanager.c:271
#22 0x557a7888 in gimp_devices_init (gimp=0x56031b40)
at widgets/gimpdevices.c:66
#23 0x556432a2 in gui_restore_callback
(gimp=0x56031b40, status_callback=0x5563c770 ) at gui/gui.c:561
#24 0x76fa5130 in g_closure_invoke ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#25 0x76fd24ac in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#26 0x76fc39b1 in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#27 0x76fc3bd6 in g_signal_emit_valist ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#28 0x76fc3c93 in g_signal_emit ()
at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#29 0x558f5691 in gimp_restore
(gimp=0x56031b40, status_callback=0x5563c770 , error=) at core/gimp.c:844
#30 0x5564533b in app_run

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/2031907

Title:
  gimp is segfaulting on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2031907/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2031907] Re: gimp is segfaulting on startup

[Jonathan Kamens]

I tried removing ~/.config/GIMP to see if starting from scratch would
fix the crash. No luck.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/2031907

Title:
  gimp is segfaulting on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2031907/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2031907] Re: gimp is segfaulting on startup

[Jonathan Kamens]

Still happening.


** Tags added: regression-release

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/2031907

Title:
  gimp is segfaulting on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2031907/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2031907] [NEW] gimp is segfaulting on startup

[Jonathan Kamens]

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 2.10.34
git-describe: GIMP_2_10_34
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
12.2.0-16ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-12 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin 
--enable-default-pie --with-system-zlib --enable-libphobos-checking=release 
--with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch 
--disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-12-TwSidC/gcc-12-12.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-12-TwSidC/gcc-12-12.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.2.0 (Ubuntu 12.2.0-16ubuntu1) 

# Libraries #
using babl version 0.1.106 (compiled against version 0.1.98)
using GEGL version 0.4.44 (compiled against version 0.4.42)
using GLib version 2.77.1 (compiled against version 2.75.3)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.50.14 (compiled against version 1.50.12)
using Fontconfig version 2.14.1 (compiled against version 2.14.1)
using Cairo version 1.17.8 (compiled against version 1.16.0)

```
> fatal error: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 26439 - Thread 26439 #


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from 
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 26440]
[New LWP 26441]
[New LWP 26442]
[New LWP 26443]
[New LWP 26444]
[New LWP 26445]
[New LWP 26446]
[New LWP 26447]
[New LWP 26448]
[New LWP 26449]
[New LWP 26453]
[New LWP 26454]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__GI___libc_read (nbytes=256, buf=0x7ffd237b6c40, fd=13) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target IdFrame 
* 1Thread 0x7f88fe2bf2c0 (LWP 26439) "gimp" __GI___libc_read 
(nbytes=256, buf=0x7ffd237b6c40, fd=13) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7f88fdcbd6c0 (LWP 26440) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7f88fd4bc6c0 (LWP 26441) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7f88fccbb6c0 (LWP 26442) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7f88e6c0 (LWP 26443) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7f88ef7fe6c0 (LWP 26444) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7f88eeffd6c0 (LWP 26445) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7f88ee7fc6c0 (LWP 26446) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7f88edf936c0 (LWP 26447) "pool-spawner" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7f88ed7926c0 (LWP 26448) "gmain"0x7f88fed0fd7f in 
__GI___poll (fds=0x558fcebcf1f0, nfds=1, timeout=7064) at 
../sysdeps/unix/sysv/linux/poll.c:29
  11   Thread 0x7f88ecf916c0 (LWP 26449) "gdbus"0x7f88fed0fd7f in 
__GI___poll (fds=0x7f88cc000b90, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  12   Thread 0x7f88c2dff6c0 (LWP 26453) "async"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  13   Thread 0x7f88c25fe6c0 (LWP 

[Bug 2027844] [NEW] opening sound settings from GNOME top menu yields blank control center

[Jonathan Kamens]

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 on 
Sound, it shows up properly.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-control-center 1:44.3-1ubuntu2
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
ApportVersion: 2.26.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul 15 00:32:27 2023
InstallationDate: Installed on 2022-09-17 (300 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to mantic on 2023-05-20 (55 days ago)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug mantic wayland-session

-- 
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 sound settings from GNOME top menu yields blank control center

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2027844/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2023588] Re: PDF fonts messed up in evince, mupdf, are fine in chrome

[Jonathan Kamens]

** 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.
https://bugs.launchpad.net/bugs/2023588

Title:
  PDF fonts messed up in evince, mupdf, are fine in chrome

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2023588/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2023588] [NEW] PDF fonts messed up in evince, mupdf, are fine in chrome

[Jonathan Kamens]

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 tried loading the PDF gimp, it's rendered wrong there like in
evince. Same with xournalpp.

Mupdf is close to correct but I think I think Chrome is doing a better
job.

Made sure all packages were up-to-date and rebooted, didn't help.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: evince 44.1-1
ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6
Uname: Linux 6.2.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 12 15:04:13 2023
InstallationDate: Installed on 2019-01-02 (1622 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: evince
UpgradeStatus: Upgraded to mantic on 2023-05-20 (23 days ago)

** Affects: evince (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug mantic

** Attachment added: "samples.png"
   
https://bugs.launchpad.net/bugs/2023588/+attachment/5679357/+files/samples.png

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/2023588

Title:
  PDF fonts messed up in evince, mupdf, are fine in chrome

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2023588/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2011251] Re: When focus-mode=mouse is set, gnome-shell gets into state where clicking on window title bars doesn't raise them

[Jonathan Kamens]

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 not occur even if I change focus to mouse. So the deciding
factor seems to be the focus setting that's active at the time the user
logs in.


** Changed in: mutter (Ubuntu)
   Status: Incomplete => New

** 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/2011251

Title:
  When focus-mode=mouse is set, gnome-shell gets into state where
  clicking on window title bars doesn't raise them

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2011251/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)

[Jonathan Kamens]

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 does not transfer focus to target window
  (server side decorations in Xorg sessions)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)

[Jonathan Kamens]

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

Title:
  Single click on title bar does not transfer focus to target window
  (server side decorations in Xorg sessions)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)

[Jonathan Kamens]

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 target window
  (server side decorations in Xorg sessions)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2011251] Re: gnome-shell gets into state where clicking on window title bars doesn't raise them

[Jonathan Kamens]

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 mantic, clicking on the title bar still doesn't
raise the window, whereas clicking on the title bar of a terminal window
DOES raise it. I.e., the problem I initially reported above still
exists.

** Changed in: mutter (Ubuntu)
   Status: Fix Released => 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/2011251

Title:
  gnome-shell gets into state where clicking on window title bars
  doesn't raise them

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2011251/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2011244] Re: emacs launching in GNOME is all messed up

[Jonathan Kamens]

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.
https://bugs.launchpad.net/bugs/2011244

Title:
  emacs launching in GNOME is all messed up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/2011244/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2011244] Re: emacs launching in GNOME is all messed up

[Jonathan Kamens]

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?


** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: 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/2011244

Title:
  emacs launching in GNOME is all messed up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/2011244/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1772212] Re: [nvidia] Night light doesn't cover all monitors fully

[Jonathan Kamens]

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 monitor works fine on the login screen and under Xorg
but does not work under Wayland: when I log into Wayland the computer
thinks that the DisplayLink monitor is active (i.e., the display
settings applet claims that my display is extended to it and I can move
my mouse off the edge of one screen and supposedly onto the other), but
it's blank and the monitor claims it's not getting a signal.

When I log into Wayland Nightlight is disabled and the settings applet
for it says that it's unavailable. (And of course none of them are the
same as the bug to which I'm adding this comment.)

When I log into Xorg Nightlight is supposedly enabled but does not
appear to do anything to the color of the display on either the direct
monitor or the DisplayLink monitor, i.e., it doesn't appear to work.

I'm guessing these are all separate bugs but I'm so overwhelmed by the
number and variety of them that I'm not sure how best to report them.

-- 
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/1772212

Title:
  [nvidia] Night light doesn't cover all monitors fully

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1772212/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2011317] Re: gnome-shell spontaneously logging me out when screen locked, laptop lid closed

[Jonathan Kamens]

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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2011317

Title:
  gnome-shell spontaneously logging me out when screen locked, laptop
  lid closed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011317/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2011317] Re: gnome-shell spontaneously logging me out when screen locked, laptop lid closed

[Jonathan Kamens]

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
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 closed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011317/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2011317] Re: gnome-shell spontaneously logging me out when screen locked, laptop lid closed

[Jonathan Kamens]

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 closed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011317/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2011257] Re: Latest gnome-shell hanging regularly

[Jonathan Kamens]

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 notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2011257

Title:
  Latest gnome-shell hanging regularly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011257/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2011321] [NEW] random windows launching with wrong title bar settings

[Jonathan Kamens]

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 I have them configured via the Tweaks
apps to be on the left.

Logging out and logging back in seems to clear up the issue temporarily.

Again, this isn't happening with all windows even within the same
session. Truly bizarre.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44~beta-1ubuntu1
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 11 21:10:00 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-09-17 (175 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
RelatedPackageVersions: mutter-common 44~beta-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to lunar on 2022-11-17 (114 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug 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/2011321

Title:
  random windows launching with wrong title bar settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011321/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2011317] Re: gnome-shell spontaneously logging me out when screen locked, laptop lid closed

[Jonathan Kamens]

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 problem has been happening has had some bizarre screen
flickering recently, so maybe there's a graphics hardware issue that is
causing the Wayland server to crash or something?

-- 
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 closed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011317/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2011317] [NEW] gnome-shell spontaneously logging me out when screen locked, laptop lid closed

[Jonathan Kamens]

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 why/how?

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44~beta-1ubuntu1
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 11 16:57:51 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-09-17 (175 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
RelatedPackageVersions: mutter-common 44~beta-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to lunar on 2022-11-17 (114 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug 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/2011317

Title:
  gnome-shell spontaneously logging me out when screen locked, laptop
  lid closed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011317/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2011257] [NEW] Latest gnome-shell hanging regularly

[Jonathan Kamens]

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 account in the same profile, and I
clicked the yes button to do that, and then my screen simply hang and
refused to do anything for about 30-45 seconds, after which it unhung.
The mouse pointer moved during the hang but nothing else.

The second time I attempted to open an external drive that was mounted
by clicking on its icon in the dock, and the open animation appeared but
the folder didn't open. I clicked again and the open animation appeared
again but again the folder did not open. At this point everything hung--
once again, mouse cursor moved but nothing else would happen no matter
what I typed or clicked. Waiting this one out didn't work; I had to SSH
into the machine from another bo and kill -9 the gnome-shell process to
escape.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44~beta-1ubuntu1
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 10 16:20:01 2023
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-16 (1302 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 44~beta-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to lunar on 2022-11-24 (106 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug lunar wayland-session

-- 
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/2011257

Title:
  Latest gnome-shell hanging regularly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011257/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2011251] [NEW] gnome-shell gets into state where clicking on window title bars doesn't raise them

[Jonathan Kamens]

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
rebooted. I think this may have occurred after some other aberrant
behavior, specifically the shell hanging for about 30 seconds (I will
file a separate bug about that), so it's possible that things were in
some sort of broken state because of that and this bug isn't actually
specifically about the title bar, but I thought I should file a bug
report about it just in case it's something other people start seeing so
we can see how frequently it's happening.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44~beta-1ubuntu1
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 10 16:16:22 2023
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-16 (1302 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 44~beta-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to lunar on 2022-11-24 (106 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug lunar wayland-session

-- 
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/2011251

Title:
  gnome-shell gets into state where clicking on window title bars
  doesn't raise them

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011251/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1990861] Re: can no longer click on speaker icon in system tray menu to mute/unmute

[Jonathan Kamens]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990861/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2007411] [NEW] gnome-control-center-goa-helper hangs after toggling a rocker switch

[Jonathan Kamens]

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 and can't be 
closed.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-control-center 1:44~alpha-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.24.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 15 11:15:03 2023
InstallationDate: Installed on 2019-01-02 (1505 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to lunar on 2022-11-24 (82 days ago)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug lunar

-- 
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/2007411

Title:
  gnome-control-center-goa-helper hangs after toggling a rocker switch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2007411/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1992263] [NEW] shell says I'm in airplane mode when I'm not

[Jonathan Kamens]

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 turn
"airplane mode" back on it turns itself back on when I restart the
shell.

I'm not in "airplane mode" just because no wireless controllers are
currently in use. I'm in "airplane mode" when I tell the shell I want to
be in "airplane mode". Yes, absolutely, if I turn airplane mode on and
then subsequently turn wifi or bluetooth back on manually, airplane mode
should automatically shut off. But the opposite — automatically turning
*on* airplane mode whenever no wireless controllers are active — simply
should not be the case.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
Uname: Linux 5.19.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct  8 20:50:00 2022
DisplayManager: gdm3
InstallationDate: Installed on 2019-01-02 (1375 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
RelatedPackageVersions: mutter-common 43.0-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2022-09-24 (14 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug kinetic third-party-packages

-- 
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/1992263

Title:
  shell says I'm in airplane mode when I'm not

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1992263/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1991598] [NEW] laptop not reliably going to sleep when lid closed on battery power

[Jonathan Kamens]

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 for hours and never went to sleep.

When I opened the lid I found it locked as it should have been, so
that's apparently not the issue. The issue is that it just never went to
sleep even though it was idle for hours.

This is a regression from Jammy.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct  3 21:24:57 2022
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-16 (1144 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 43.0-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2022-09-24 (9 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug kinetic third-party-packages

-- 
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/1991598

Title:
  laptop not reliably going to sleep when lid closed on battery power

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1991598/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1990861] [NEW] can no longer click on speaker icon in system tray menu to mute/unmute

[Jonathan Kamens]

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: Ubuntu 22.10
Package: gnome-shell 43.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 26 11:39:09 2022
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-16 (1136 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 43.0-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2022-09-24 (1 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug kinetic third-party-packages

-- 
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990861/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1990742] [NEW] screen not consistently locking when lid is closed

[Jonathan Kamens]

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 lock-enabled true

This worked fine in Jammy: whenever my screen was unlocked and I closed
my laptop lid, it locked immediately, i.e., if I immediately reopened my
lid, the screen was locked.

After having just upgraded to Kinetic, however, sometimes when I close
the lid it locks as described above, and sometimes it just... doesn't,
i.e., when I open the lid again the screen is unlocked and I can just
keep working.

I have been unable to determine what the factors are which control
whether the screen locks when I close the lid.

There is a moderate security implication here, as it's problematic for
someone's screen not to lock when they think that it did.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 24 17:57:37 2022
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-16 (1135 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 43.0-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug kinetic third-party-packages

-- 
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/1990742

Title:
  screen not consistently locking when lid is closed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990742/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1983483] Re: totem crashing inside nouveau DRI when replaying video (actually nouveau bug?)

[Jonathan Kamens]

*** 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 be
working at least for the time being, so I'll stick with that for a while
and we'll see what happens. :shrug:

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1983483

Title:
  totem crashing inside nouveau DRI when replaying video (actually
  nouveau bug?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1983483/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1983483] XorgLog.txt

[Jonathan Kamens]

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.
https://bugs.launchpad.net/bugs/1983483

Title:
  totem crashing inside nouveau DRI when replaying video (actually
  nouveau bug?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1983483/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1983483] ProcEnviron.txt

[Jonathan Kamens]

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.
https://bugs.launchpad.net/bugs/1983483

Title:
  totem crashing inside nouveau DRI when replaying video (actually
  nouveau bug?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1983483/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1983483] ProcCpuinfoMinimal.txt

[Jonathan Kamens]

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.
https://bugs.launchpad.net/bugs/1983483

Title:
  totem crashing inside nouveau DRI when replaying video (actually
  nouveau bug?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1983483/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1983483] GstreamerVersions.txt

[Jonathan Kamens]

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.
https://bugs.launchpad.net/bugs/1983483

Title:
  totem crashing inside nouveau DRI when replaying video (actually
  nouveau bug?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1983483/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1983483] Re: totem crashing inside nouveau DRI when replaying video (actually nouveau bug?)

[Jonathan Kamens]

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
  bug rather than a totem bug. I can't report it with ubuntu-bug because
  of bug 1983481. I did manage to capture a stack trace with gdb, which
  I've attached.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: totem 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug  3 10:43:36 2022
  InstallationDate: Installed on 2019-01-02 (1308 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  LogAlsaMixer:
   Simple mixer control 'Line',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined
 Capture channels: Mono
 Limits: Capture 0 - 15
 Mono: Capture 15 [100%] [15.00dB] [on]
  SourcePackage: totem
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (163 days ago)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.1
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2019-01-02 (1309 days ago)
+ InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
+ LogAlsaMixer:
+  Simple mixer control 'Line',0
+Capabilities: cvolume cvolume-joined cswitch cswitch-joined
+Capture channels: Mono
+Limits: Capture 0 - 15
+Mono: Capture 15 [100%] [15.00dB] [on]
+ Package: totem 42.0-1ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
+ Tags:  jammy
+ Uname: Linux 5.15.0-43-generic x86_64
+ UpgradeStatus: Upgraded to jammy on 2022-02-20 (163 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers 
wireshark
+ _MarkForUpload: True
+ modified.conffile..etc.apport.crashdb.conf: [modified]
+ mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1983483/+attachment/5606790/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1983483

Title:
  totem crashing inside nouveau DRI when replaying video (actually
  nouveau bug?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1983483/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1983481] Re: Can't report totem crash with ubuntu-bug

[Jonathan Kamens]

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 crashes are not reported automatically, but I
believe when a crash is reported manually with ubuntu-bug as I'm doing
it should go into Launchpad, which as I indicated above is not
happening.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1983481

Title:
  Can't report totem crash with ubuntu-bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1983481/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1973570] Re: totem crashed with SIGSEGV in ___pthread_mutex_destroy() from g_rec_mutex_impl_free() from g_rec_mutex_clear() from gst_video_decoder_finalize() from g_object_unref()

[Jonathan Kamens]

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 notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1973570

Title:
  totem crashed with SIGSEGV in ___pthread_mutex_destroy() from
  g_rec_mutex_impl_free() from g_rec_mutex_clear() from
  gst_video_decoder_finalize() from g_object_unref()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1973570/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1983483] [NEW] totem crashing inside nouveau DRI when replaying video (actually nouveau bug?)

[Jonathan Kamens]

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 because
of bug 1983481. I did manage to capture a stack trace with gdb, which
I've attached.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug  3 10:43:36 2022
InstallationDate: Installed on 2019-01-02 (1308 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
LogAlsaMixer:
 Simple mixer control 'Line',0
   Capabilities: cvolume cvolume-joined cswitch cswitch-joined
   Capture channels: Mono
   Limits: Capture 0 - 15
   Mono: Capture 15 [100%] [15.00dB] [on]
SourcePackage: totem
UpgradeStatus: Upgraded to jammy on 2022-02-20 (163 days ago)

** Affects: totem (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

** Attachment added: "script-totem.out"
   
https://bugs.launchpad.net/bugs/1983483/+attachment/5606748/+files/script-totem.out

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1983483

Title:
  totem crashing inside nouveau DRI when replaying video (actually
  nouveau bug?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1983483/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1983481] [NEW] Can't report totem crash with ubuntu-bug

[Jonathan Kamens]

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
jik@jik5:~$ 

2) Sometimes I get a stack trace before it exits:

jik@jik5:~$ ubuntu-bug /var/crash/_usr_bin_totem.1000.crash
ERROR: hook /usr/share/apport/package-hooks/source_totem.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook
symb['add_info'](report, ui)
  File "/usr/share/apport/package-hooks/source_totem.py", line 9, in add_info
response = ui.choice("How would you describe the issue?", ["The totem 
interface is not working correctly", "No sound is being played", "Some audio 
files or videos are not being played correctly"], False)
AttributeError: 'NoneType' object has no attribute 'choice'
jik@jik5:~$ 

Either way, my browser doesn't open to launchpad as it should after
ubuntu-bug posts a report.

This makes it difficult, to say the least, to report a totem crash
properly.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem-common 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug  3 10:35:28 2022
InstallationDate: Installed on 2019-01-02 (1308 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
LogAlsaMixer:
 Simple mixer control 'Line',0
   Capabilities: cvolume cvolume-joined cswitch cswitch-joined
   Capture channels: Mono
   Limits: Capture 0 - 15
   Mono: Capture 15 [100%] [15.00dB] [on]
PackageArchitecture: all
SourcePackage: totem
UpgradeStatus: Upgraded to jammy on 2022-02-20 (163 days ago)

** Affects: totem (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1983481

Title:
  Can't report totem crash with ubuntu-bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1983481/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1983294] Re: totem is coredumping, ubuntu-bug on the crash file is failing

[Jonathan Kamens]

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 
../../../glib/gthread-posix.c:299
#2  g_rec_mutex_clear (rec_mutex=rec_mutex@entry=0x7fff980b33a8) at 
../../../glib/gthread-posix.c:376
#3  0x76d45f7c in gst_video_decoder_finalize (object=0x7fff980b3290 
[GstVaapiDecode]) at ../gst-libs/gst/video/gstvideodecoder.c:943
#4  0x77ee0dfd in g_object_unref (_object=) at 
../../../gobject/gobject.c:3678
#5  g_object_unref (_object=0x7fff980b3290) at ../../../gobject/gobject.c:3553
#6  0x76e5ccd3 in gst_object_unref (object=) at 
../gst/gstobject.c:267
#7  0x76e664c0 in gst_bin_remove_func (bin=0x56591830 
[GstVaapiDecodeBin], element=) at ../gst/gstbin.c:1815
#8  0x76e6170b in gst_bin_remove (bin=bin@entry=0x56591830 
[GstVaapiDecodeBin], element=0x7fff980b3290 [GstVaapiDecode]) at 
../gst/gstbin.c:1867
#9  0x76e61e2b in gst_bin_dispose (object=0x56591830 
[GstVaapiDecodeBin]) at ../gst/gstbin.c:527
...

Having said that, we still have the problem that neither ubuntu-bug nor
apport-cli are able to successfully report this crash. Should we convert
this bug into that issue and leave the other ticket for the crash issue?

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1983294

Title:
  totem is coredumping, ubuntu-bug on the crash file is failing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1983294/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1983294] Re: totem is coredumping, ubuntu-bug on the crash file is failing

[Jonathan Kamens]

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 then
it exits without doing anything:

jik@jik5:~$ apport-cli /var/crash/_usr_bin_totem.1000.crash

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (27.5 MB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): s
jik@jik5:~$

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1983294

Title:
  totem is coredumping, ubuntu-bug on the crash file is failing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1983294/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1983294] [NEW] totem is coredumping, ubuntu-bug on the crash file is failing

[Jonathan Kamens]

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:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook
symb['add_info'](report, ui)
  File "/usr/share/apport/package-hooks/source_totem.py", line 9, in add_info
response = ui.choice("How would you describe the issue?", ["The totem 
interface is not working correctly", "No sound is being played", "Some audio 
files or videos are not being played correctly"], False)
AttributeError: 'NoneType' object has no attribute 'choice'

So that's two different issues -- the crash and the fact that I can't
report it using ubuntu-bug.

I'm hoping you can pull the crash from the ID above and maybe do
something useful with it. :shrug:

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug  1 21:12:09 2022
InstallationDate: Installed on 2019-01-02 (1307 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
LogAlsaMixer:
 Simple mixer control 'Mic',0
   Capabilities: cvolume cvolume-joined cswitch cswitch-joined
   Capture channels: Mono
   Limits: Capture 0 - 15
   Mono: Capture 15 [100%] [50.00dB] [on]
SourcePackage: totem
UpgradeStatus: Upgraded to jammy on 2022-02-20 (162 days ago)

** Affects: totem (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1983294

Title:
  totem is coredumping, ubuntu-bug on the crash file is failing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1983294/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1975597] [NEW] Python files are still packaged for Python 3.8

[Jonathan Kamens]

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 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue May 24 10:08:37 2022
InstallationDate: Installed on 2019-08-16 (1011 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: indicator-keyboard
UpgradeStatus: Upgraded to jammy on 2021-11-09 (196 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

** Affects: indicator-keyboard (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to indicator-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1975597

Title:
  Python files are still packaged for Python 3.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1975597/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1969280] [NEW] gnome-terminal not obeying light vs. dark theme

[Jonathan Kamens]

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 to a
white background except gnome-terminal.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-terminal 3.44.0-1ubuntu1 [modified: 
usr/share/applications/org.gnome.Terminal.desktop]
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 16 14:44:00 2022
InstallationDate: Installed on 2019-08-16 (973 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to jammy on 2021-11-09 (158 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1969280

Title:
  gnome-terminal not obeying light vs. dark theme

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1969280/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967637] Re: gnome-extensions-app crashing on startup, not producing reportable crash for some reason

[Jonathan Kamens]

I just installed another round of new Jammy updates on the laptop where
gnome-extensions-app was crashing, and it's not crashing anymore. I
don't know if it's the installing of the updates that fixed this or if
it's an intermittent issue and just not happening at the moment. Hard to
tell since no crash report was generated. :shrug:

-- 
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/1967637

Title:
  gnome-extensions-app crashing on startup, not producing reportable
  crash for some reason

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967637/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967637] Re: gnome-extensions-app crashing on startup, not producing reportable crash for some reason

[Jonathan Kamens]

I have two machines with Jammy on them and this is happening reliably on
one but not the other.

On the one where it's happening, it happens even immediately after I've
updated all out-of-date packages and rebooted the machine.

I don't know why it's not generating a crash report. :-(

-- 
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/1967637

Title:
  gnome-extensions-app crashing on startup, not producing reportable
  crash for some reason

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967637/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1967637] [NEW] gnome-extensions-app crashing on startup, not producing reportable crash for some reason

[Jonathan Kamens]

Public bug reported:

$ /usr/bin/gnome-extensions-app
Segmentation fault (core dumped)

There's nothing in /var/crash.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell-extension-prefs 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  2 17:01:32 2022
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-16 (960 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 42.0-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2021-11-09 (144 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

-- 
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/1967637

Title:
  gnome-extensions-app crashing on startup, not producing reportable
  crash for some reason

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967637/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966614] Re: I am getting calendar notification pop-ups even though I've turned them off

[Jonathan Kamens]

Yes they are Reminders from the Calendar app. For a Google account.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1966614

Title:
  I am getting calendar notification pop-ups even though I've turned
  them off

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1966614/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966614] [NEW] I am getting calendar notification pop-ups even though I've turned them off

[Jonathan Kamens]

Public bug reported:

I keep getting calendar notification pop-ups -- at the top middle of my
screen -- even though in the calendar settings in Notifications I have
"Notification Popups" turned off.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-calendar 41.2-3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 27 20:20:15 2022
InstallationDate: Installed on 2019-08-16 (954 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: gnome-calendar
UpgradeStatus: Upgraded to jammy on 2021-11-09 (138 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

** Affects: gnome-calendar (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1966614

Title:
  I am getting calendar notification pop-ups even though I've turned
  them off

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1966614/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1963755] [NEW] extensions get turned off spontaneously when I log out and log back in

[Jonathan Kamens]

Public bug reported:

1. Have some GNOME shell extensions installed (I have Allow Locked Remote 
Desktop, Mpris Indicator Button, Removable Drive Menu, User Themes, plus 
built-ins Desktop Icons NG, Ubuntu AppIndicators, Ubuntu Dock).
2. Open the Extensions app.
3. Confirm that the switch at the top controlling all extensions is on.
4. Log out.
5. Log back in.
6. Observe that your extensions are not running.
7. Open the Extensions app.
8. Observe that the switch at the top is now off, even though you never turned 
it off.

This is reproducible for me.

ProblemType: Bug
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: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar  5 13:02:55 2022
DisplayManager: gdm3
InstallationDate: Installed on 2019-01-02 (1158 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
RelatedPackageVersions: mutter-common 41.3-3ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-02-20 (12 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy third-party-packages

-- 
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/1963755

Title:
  extensions get turned off spontaneously when I log out and log back in

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963755/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1952556] Re: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong."

[Jonathan Kamens]

No longer reproducible for me.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1952556

Title:
  Jammy, attempt to log into Xorg session, "Oh no! Something has gone
  wrong."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1952556/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1953209] [NEW] ICS imported into GNOME calendar (Google Calendar) with UTC start and end times breaks if you edit it

[Jonathan Kamens]

Public bug reported:

1. Your local computer should be in a time zone other than UTC.
2. Save the attached sample.ics to your Desktop.
3. Double-click on it to import it into GNOME Calendar.
4. Save the imported event. Observe that it is saved at the correct time in 
your calendar.
5. In GNOME calendar, click on the event and click edit.
6. Expand the start and end time sections and observe that the times next to 
"Starts" and "Ends" are the UTC times for the event, while the times in the 
time pickers are the correct time in the local time zone.
7. Click the "Done" button without actually changing anything and observe that 
the event moves to the incorrect time, interpreting the original UTC times of 
the event as local times.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-calendar 41.1-1
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu74
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  3 21:28:09 2021
InstallationDate: Installed on 2019-08-16 (840 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: gnome-calendar
UpgradeStatus: Upgraded to jammy on 2021-11-09 (24 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

** Affects: gnome-calendar
 Importance: Unknown
 Status: Unknown

** Affects: gnome-calendar (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

** Attachment added: "sample ICS file to demonstrate bug"
   https://bugs.launchpad.net/bugs/1953209/+attachment/5545308/+files/sample.ics

** Bug watch added: gitlab.gnome.org/GNOME/gnome-calendar/-/issues #755
   https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/755

** Also affects: gnome-calendar via
   https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/755
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1953209

Title:
  ICS imported into GNOME calendar (Google Calendar) with UTC start and
  end times breaks if you edit it

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-calendar/+bug/1953209/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1952557] Re: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly

[Jonathan Kamens]

1) ~/.local/share/gnome-shell/extensions is empty

2) I reproduced this issue with Chromium and there is no Chromium crash
in /var/crash, nor is there an error report for Chromium tied to my
whoopsie ID.

Since the chromium snap is provided by Canonical and this issue is
reproducible with Chromium does that mean it's no longer an "Invalid"
issue?

-- 
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/1952557

Title:
  Jammy after logging out of wayland session and back in Chrome says it
  wasn't shut down correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952557/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1952556] Re: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong."

[Jonathan Kamens]

(Though why _Wayland_ is crashing when I'm trying to log into an _Xorg_
session and the options menu on the login screen says that I have Xorg
selected remains a mystery.)

-- 
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/1952556

Title:
  Jammy, attempt to log into Xorg session, "Oh no! Something has gone
  wrong."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952556/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1952556] Re: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong."

[Jonathan Kamens]

Problem still occurs with mprisindicatorbutton, batime, and
allowlockedremotedesktop completely uninstalled. Can't uninstall multi-
volume because neither Extensions app nor extensions.gnome.org say it's
installed.

Probably relevant crash:
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1952619

-- 
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/1952556

Title:
  Jammy, attempt to log into Xorg session, "Oh no! Something has gone
  wrong."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952556/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1952557] Re: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly

[Jonathan Kamens]

** Attachment added: "screenshot showing no multi-volume@tigersoldier"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952557/+attachment/5544070/+files/extensions%20app.png

-- 
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/1952557

Title:
  Jammy after logging out of wayland session and back in Chrome says it
  wasn't shut down correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952557/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1952557] Re: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly

[Jonathan Kamens]

I removed 'mprisindicatorbut...@jasonlg1979.github.io',
'bat...@martin.zurowietz.de', and 'allowlockedremotedesk...@kamens.us',
but GNOME doesn't seem to think I have  'multi-volume@tigersoldier'
installed, so I'm not sure where you got that from or what to do with
it. See attached screenshot of Extensions app. I also looked on
extensions.gnome.org and it also doesn't list it as an installed
extension.

With the other three extensions removed completely the problem still
occurs even after two logout / login cycles after removing the
extensions to ensure they're completely purged.

Regarding the crash instructions you sent, there is in fact a Chrome
crash in /var/crash that looks relevant but of course I can't report it
with ubuntu-bug because Chrome is not an Ubuntu package. There are no
crashes on errors.ubuntu.com for my Whoopsie ID, and I've already got
the workaround from bug 994921.

-- 
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/1952557

Title:
  Jammy after logging out of wayland session and back in Chrome says it
  wasn't shut down correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952557/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1952557] [NEW] Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly

[Jonathan Kamens]

Public bug reported:

In Jammy when I have Chrome running and I log out of a Wayland session
and then log back in and restart Chrome it says it wasn't shut down
correctly.

I'm pretty sure in earlier releases Chrome was given the opportunity to
shut down cleanly when I logged out, but :shrug: I could be remembering
this incorrectly.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 40.5-1ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 28 11:17:25 2021
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-16 (834 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 40.5-1ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2021-11-09 (19 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

-- 
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/1952557

Title:
  Jammy after logging out of wayland session and back in Chrome says it
  wasn't shut down correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952557/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1952556] [NEW] Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong."

[Jonathan Kamens]

Public bug reported:

On Jammy, I log out of a Wayland session, click my name on the login
screen, go down to the options menu and select Ubuntu on Xorg, enter my
password, get "Oh no! Something has gone wrong. A probleme has occurred
and the system can't recover. Please log out and try again. [Log Out]" I
click the log out button and log in again, and I'm logged into a Wayland
session. Why was I logged into a Wayland session when I selected Xorg
the last time I tried to log in?

This issue is intermittent I had been able to log into an Xorg session
just a few minutes prior.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 40.5-1ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 28 11:10:10 2021
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-16 (834 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 40.5-1ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2021-11-09 (19 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

-- 
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/1952556

Title:
  Jammy, attempt to log into Xorg session, "Oh no! Something has gone
  wrong."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952556/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1952556] Re: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong."

[Jonathan Kamens]

I logged out immediately after logging in again as described above, then
went to log in again and checked the options menu, and it correctly had
"Ubuntu on Xorg" selected as my session type, but when I finished
logging in I was in a Wayland session, not an Xorg session. So for some
reason my selection of Xorg as my desired session is being ignored?

-- 
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/1952556

Title:
  Jammy, attempt to log into Xorg session, "Oh no! Something has gone
  wrong."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952556/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1813441] Re: Can no longer drag and drop files between desktop and applications

[Jonathan Kamens]

Can you please read what other people have said before commenting.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
https://bugs.launchpad.net/bugs/1813441

Title:
  Can no longer drag and drop files between desktop and applications

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1920061] Re: when I go to restart it claims there is someone logged in remotely when no one is

[Jonathan Kamens]

lol PEBKAC issue. I had an sshfs session running on another computer and
whenever I rebooted it was reconnecting. Sorry to trouble you. That's
for telling me how to figure it out.


** Changed in: gnome-shell (Ubuntu)
   Status: New => 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/1920061

Title:
  when I go to restart it claims there is someone logged in remotely
  when no one is

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1920061/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1920061] Re: when I go to restart it claims there is someone logged in remotely when no one is

[Jonathan Kamens]

It says "No inhibitors", and yet there is still no one else logged in
remotely and it is still claiming that there is when I try to restart.


** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => 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/1920061

Title:
  when I go to restart it claims there is someone logged in remotely
  when no one is

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1920061/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1920061] [NEW] when I go to restart it claims there is someone logged in remotely when no one is

[Jonathan Kamens]

Public bug reported:

With all current Hirsute updates as of today, when I reboot my machine
and then immediately after logging in select Power Off/Log Out and then
Restart... the warning that pops up claims that I am logged in remotely
(see attached screenshot) when I am not. As I said, I just rebooted and
no one else is logged in. `who` also doesn't think anyone else is logged
in:

jik@jik5:~$ who
jik  :0   2021-03-18 15:24 (:0)
jik@jik5:~$ ubuntu-bug gnome-shell

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.3-3ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
Uname: Linux 5.11.0-11-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu60
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 18 15:28:47 2021
DisplayManager: gdm3
InstallationDate: Installed on 2019-01-02 (806 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to hirsute on 2021-02-21 (25 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute regression-release

** Attachment added: "screen shot of restart pop-up claiming I am logged in 
remotely"
   
https://bugs.launchpad.net/bugs/1920061/+attachment/5477970/+files/2021-03-18_15-28.png

-- 
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/1920061

Title:
  when I go to restart it claims there is someone logged in remotely
  when no one is

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1920061/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1813441] Re: Can no longer drag and drop files between desktop and applications

[Jonathan Kamens]

I want to thank you from the bottom of my heart for taking time out of
what I'm sure is a very busy schedule to educate poor little me, who is
so ignorant that I've only been working on open source and commercial
software for over 30 years and using Linux since the early days of
Slackware and at one point had submitted more Linux bug reports to Red
Hat than literally any other account in bugzilla, about what a "show-
stopper" bug is. Truly, I am enlightened.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
https://bugs.launchpad.net/bugs/1813441

Title:
  Can no longer drag and drop files between desktop and applications

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1813441] Re: Can no longer drag and drop files between desktop and applications

[Jonathan Kamens]

Claiming that Ubuntu could simply have stuck with the previous version
of GNOME when shipping the LTS release is failing to see the forest for
the trees. Many factors go into the decision of what version of a
critical package like GNOME to put in a release. Ubuntu looked at all of
those factors and made the decision they did. Unless you were involved
in that discussion or have done an analysis similar to theirs, you are
in no position to second-guess their decision; you simply are not
considering even a small fraction of the information they considered
when making it.

Desktop Icons NG was around when 20.04 shipped, though it probably
wasn't complete, tested, or stable enough to ship with an LTS release.
There have been significant changes since 20.04 shipped.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
https://bugs.launchpad.net/bugs/1813441

Title:
  Can no longer drag and drop files between desktop and applications

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1813441] Re: Can no longer drag and drop files between desktop and applications

[Jonathan Kamens]

Three notes:

1. Ubuntu has addressed this in 21.04 by shipping gnome-shell-extension-
desktop-icons-ng by default.

2. Note that you can fix this yourself in any earlier version of Ubuntu
by installing that extension directly from extensions.gnome.org (
https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/ ) and
disabling the older version shipped with Ubuntu.

3. This is GNOME's fault, not Ubuntu's fault, so bitching at Ubuntu
about it is not helpful or useful. It's not practical for Ubuntu to keep
using obsolete versions of GNOME when the GNOME developers introduce
regressions like this, and it's not feasible for Ubuntu to fix all of
the regressions that the GNOME developers introduce.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
https://bugs.launchpad.net/bugs/1813441

Title:
  Can no longer drag and drop files between desktop and applications

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1917175] Re: gdm login screen says "Something went wrong please try again" three times and sends me back to the login screen when I'm not typing anything

[Jonathan Kamens]

I don't understand why you are asking me for a crash report. You don't
need a crash report to know what is going on here. I described to you
exactly what is going on and exactly how to reproduce the issue: gdm
fails in the way I described if libpam-fprintd isn't installed, and the
web of dependencies of packages in Hirsute allowed an upgrade to
uninstall fprintd-clients but did not require libpam-fprintd to be
installed in its place.

It appears that perhaps a dependency to libpam-fprintd was added to the
gdm3 package after I filed this issue, because I see that it has such a
dependency now, and I don't see how I could have done the update before
with that dependency in place without libpam-fprintd being installed
during the update.

-- 
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/1917175

Title:
  gdm login screen says "Something went wrong please try again" three
  times and sends me back to the login screen when I'm not typing
  anything

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1917175/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1917175] Re: gdm login screen says "Something went wrong please try again" three times and sends me back to the login screen when I'm not typing anything

[Jonathan Kamens]

I figured out the problem. When I upgraded packages today, it
uninstalled fprintd-clients but did not install libpam-fprintd.
/etc/pam.d/gdm-fingerprint says that gdm is supposed to open
pam_fprintd.so, but it couldn't because it wasn't available any longer.

I have no understanding of the intricacies of all the package
dependencies that caused this broken situation to be allowed to occur. I
will, however, mention that previous to today's package upgrade, I had
open-fprintd installed, _not_ fprintd, because the fprintd that ships
with Ubuntu is incompatible with my fingerprint reader (Lenovo Thinkpad
X1 Carbon 6th gen). I don't know whether this is relevant to the problem
that occurred here.

To fix this, I had to uninstall open-fprintd (which means I can no
longer use my fingerprint reader) and install libpam-fprintd, which
pulled in the fprintd package along with it even though that's useless
to me since that fprintd doesn't work with my reader.

I am now unable to use open-fprintd because it conflicts with the
fprintd package but I can't uninstall fprintd because that will cause
libpam-fprintd to be uninstalled as well. But I'm going to open a
separate ticket about that, since that's a different issue from the fact
that today's upgrade made my system unusable as described above.

-- 
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/1917175

Title:
  gdm login screen says "Something went wrong please try again" three
  times and sends me back to the login screen when I'm not typing
  anything

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1917175/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1917175] [NEW] gdm login screen says "Something went wrong please try again" three times and sends me back to the login screen when I'm not typing anything

[Jonathan Kamens]

Public bug reported:

After today's update to all of the current Hirsute packages, I can't
login in. When I click on my username on the gdm3 login screen, it
immediately displays with shaking the error "Sorry, that didn't work.
Please try again." It does this three times, and then sends me back to
the main login screen. It does this EVEN THOUGH I'M NOT TYPING ANYTHING.
Please see the attached video.

I tried downgrading a bunch of packages but wasn't able to find a
downgrade that made the problem go away.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gdm3 3.38.1-2ubuntu1.1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sat Feb 27 16:20:47 2021
InstallationDate: Installed on 2019-08-16 (561 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: gdm3
UpgradeStatus: Upgraded to hirsute on 2021-02-20 (6 days ago)

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute regression-release

** Attachment added: "video of my being unable to log in"
   
https://bugs.launchpad.net/bugs/1917175/+attachment/5469795/+files/login_failure.mp4

-- 
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/1917175

Title:
  gdm login screen says "Something went wrong please try again" three
  times and sends me back to the login screen when I'm not typing
  anything

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1917175/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1696885] Re: Implement remote desktop support for GNOME on Wayland

[Jonathan Kamens]

GNOME now supports remote desktop sharing in Wayland, but it isn't
enabled in Ubuntu. Apparently one of the prerequisites for being able to
enable it in Ubuntu was recompiling mutter with support for it, and that
has now been done in Hirsute. What else needs to be done in Hirsute to
make this work?

-- 
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/1696885

Title:
  Implement remote desktop support for GNOME on Wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696885/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1730612] Re: Enable Remote desktop feature during build

[Jonathan Kamens]

Even with that version of mutter installed I still don't see screen
sharing as an option under sharing in the settings app when logged in
under Wayland. Are there other packages that need to be updated before
screen sharing will be available in Wayland sessions, and are there open
bug tickets for those?

-- 
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/1730612

Title:
  Enable Remote desktop feature during build

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1730612/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1902766] Re: Automatic suspend when idle not working in 20.10

[Jonathan Kamens]

Darn it, I tested this like three times before reporting it, but I can
no longer reproduce the issue. Sorry to bother you.


** 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/1902766

Title:
  Automatic suspend when idle not working in 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902766/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1902766] [NEW] Automatic suspend when idle not working in 20.10

[Jonathan Kamens]

Public bug reported:

I have my laptop configured to suspend automatically after 20 minutes of
idle time when on battery power. See screenshot attached showing these
settings.

This worked fine in 20.04. It is not working in 20.10: the laptop is not
suspending even after far more than 20 minutes of idle time.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  3 13:18:59 2020
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-16 (444 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to groovy on 2020-10-26 (8 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2020-04-19T16:14:35.801558

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy

** Attachment added: "screenshot of automatic suspend configuration"
   
https://bugs.launchpad.net/bugs/1902766/+attachment/5430756/+files/2020-11-03_13-20.png

-- 
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/1902766

Title:
  Automatic suspend when idle not working in 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902766/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1901631] [NEW] flameshot, yubico authenticator app indicator icons missing on login

[Jonathan Kamens]

Public bug reported:

This problem seems to come and go. It was gone in Ubuntu 20.04 and it's
back in Ubuntu 20.10.

I have both Flameshot and Yubico Authenticator configured to launch on
login. They are supposed to put app indicator icons in the top bar. The
icons are not there even though both apps are running.

To get the icons I have to kill the apps and run them again.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell-extension-appindicator 34-1
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 26 19:32:07 2020
InstallationDate: Installed on 2019-01-02 (663 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-appindicator
UpgradeStatus: Upgraded to groovy on 2020-10-25 (1 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2020-04-17T14:48:03.262066

** Affects: gnome-shell-extension-appindicator (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy regression-release regression-update

** Tags added: regression-release regression-update

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
https://bugs.launchpad.net/bugs/1901631

Title:
  flameshot, yubico authenticator app indicator icons missing on login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1901631/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1844808] Re: Can't delete file from desktop by clicking it and hitting delete key

[Jonathan Kamens]

I can't test because I've followed the instructions in
https://gitlab.gnome.org/GNOME/nautilus/issues/158#alternative-solution
to switch to Nemo to address both this issue and
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-
icons/+bug/1813441, which still hasn't been fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
https://bugs.launchpad.net/bugs/1844808

Title:
  Can't delete file from desktop by clicking it and hitting delete key

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1844808/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."

[Jonathan Kamens]

I understand that, but in this particular case we're talking about a
transition from a deb to a snap, not a snap update. Apparently there's
special logic in update-manager to handle this, and perhaps in do-
release-upgrade as well, but I don't think either apt nor snap auto-
updates will handle this.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1861631

Title:
  "The AppStream system cache was updated, but some components were
  ignored. Refer to the verbose log for more information."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1861631/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."

[Jonathan Kamens]

I think Naël is correct that this problem goes away when gnome-software
is replaced by snap-store. Or, at least, it appears to have gone away
for me when I did that.

I'm a bit concerned about that, though, because the reason why I didn't
get that update is because I pretty much exclusively use apt to do my
updates, and apparently that's no longer sufficient to get all the
updates needed on an Ubuntu system. I don't want to have to run the
graphical update-manager to do updates. I know this is mostly off-topic
here, but I don't suppose anyone knows whether there is a way to do the
equivalent of what update-manager does, but from the command line?

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1861631

Title:
  "The AppStream system cache was updated, but some components were
  ignored. Refer to the verbose log for more information."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1861631/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."

[Jonathan Kamens]

>With the replacement of gnome-software by snap-store in 20.04, this bug
is no longer apparent. Only users who manually (re-)install gnome-
software will see it.

I am not sure what you mean. There is no "snap-store" deb on my 20.04
system, nor does "apt search snap-store" yield any results.

Furthermore, this bug was initially reported about the output of
apticron showing up in cron job emails; as far as I know, apticron is
independent of gnome-software.

Please clarify your meaning.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1861631

Title:
  "The AppStream system cache was updated, but some components were
  ignored. Refer to the verbose log for more information."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1861631/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1801757] Re: all app indicators disappear

[Jonathan Kamens]

If I restart gnome shell, most of the app indicators remain, but the
Google Chrome and Hangouts appindicators disappear.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
https://bugs.launchpad.net/bugs/1801757

Title:
  all app indicators disappear

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1801757/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1726402] Re: No Google Chrome icons in top bar

[Jonathan Kamens]

I still see it in current Focal.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
https://bugs.launchpad.net/bugs/1726402

Title:
  No Google Chrome icons in top bar

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1726402/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1726402] Re: No Google Chrome icons in top bar

[Jonathan Kamens]

Well, more accurately, I _sometimes_ see it in Focal. The icons in the
top bar come and go seemingly at random i.e. I can't currently identify
what makes them disappear.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
https://bugs.launchpad.net/bugs/1726402

Title:
  No Google Chrome icons in top bar

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1726402/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1866460] [NEW] UEFI Device Firmware update failing

[Jonathan Kamens]

Public bug reported:

The Updates tab on Software Center is currently telling me that I have a
Lenofo ThinkPad X1 Carbon 7th / X1 Yoga 4th Embedded Controller Firmware
Version 1.5 updae to install. It claims it will upgrade my UEFI Device
Firmware from 0.1.14 to 0.1.15. I click the Update button. The update
goes away briefly and a pop-up appears telling me I need to reboot. Then
the update reappears. I reboot, and nothing happens during the reboot,
i.e., I don't see an update being installed during the reboot, and when
I open Software Center again after the reboot the update is still listed
there.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-software 3.35.91-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22
Uname: Linux 5.4.0-17-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar  7 09:01:19 2020
InstallationDate: Installed on 2019-09-12 (176 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-snap3.35.91-0ubuntu1
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1866460

Title:
  UEFI Device Firmware update failing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1866460/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1866222] Re: GNOME Shell crashed with signal 11

[Jonathan Kamens]

I already have the workaround in bug 994921 and have for a long time. My
system has generated and reported crashes as recently as February 28.

There's no crash for this in /var/crash.

There's no crash for this on errors.ubuntu.com.

For some reason, when this crash occurs it's not generating a crash that
can be reported to Ubuntu. It's still a bug that needs to be fixed,
though, obviously, so I am changing the status of this bug from
Incomplete back to New.


** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => 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/1866222

Title:
  GNOME Shell crashed with signal 11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1866222] [NEW] GNOME Shell crashed with signal 11

[Jonathan Kamens]

Public bug reported:

gnome-shell has crashed twice on me today.

Unfortunately there's nothing in /var/crash.

There's nothing in the journalctl log prior to the crash that explains
it.

I've attached a log of everything between when the crash happened and
when I logged back in (though I suspect most of it is not relevant).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.35.91-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22
Uname: Linux 5.4.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar  5 13:04:21 2020
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-16 (201 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-31 (34 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages wayland-session

** Attachment added: "journalctl.log"
   
https://bugs.launchpad.net/bugs/1866222/+attachment/5333922/+files/journalctl.log

-- 
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/1866222

Title:
  GNOME Shell crashed with signal 11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland

[Jonathan Kamens]

It was a private email exchange between me and the DisplayLink folks.
Basically, I emailed them and told them them their package wasn't
working on 20.04 and asked them to fix it and they emailed back and said
they're working on it.

-- 
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/1853357

Title:
  display (whole computer?) hangs when I attempt to use DisplayLink with
  Wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1853357/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland

[Jonathan Kamens]

You say that the library and kernel module in Ubuntu are older than the
ones from DisplayLink.com. Can you explain why the current versions of
the module and library aren't being shipped in Focal?

I'm afraid I can't test any further in 19.10 since I've already upgraded
both of my laptops to 20.04. :-(

And I can't test the kernel module and library from the DisplayLink.com
release in 20.04 because (as noted above) they don't build successfully.

I've been in contact with the DisplayLink.com folks and they say that
they are working on an updated release for 20.04. So perhaps at this
point all that I can do is wait for that to come out and then retest
eveything and we can figure out what to do from there if there are still
issues.

-- 
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/1853357

Title:
  display (whole computer?) hangs when I attempt to use DisplayLink with
  Wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1853357/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs