[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()

2022-08-02 Thread Daniel van Vugt
I can't see any upstream reports for this crash. If anyone is hitting it
then please tell us if uninstalling 'gstreamer1.0-vaapi' helps.

-- 
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 1983294] Re: totem is coredumping, ubuntu-bug on the crash file is failing

2022-08-02 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1973570 ***
https://bugs.launchpad.net/bugs/1973570

Thanks for the stack trace. We can track it in bug 1973570 now...

** This bug has been marked a duplicate of bug 1973570
   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()

-- 
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 1970495] Re: Window manager freezes when plugging in USB-C dock with external monitor ([drm] *ERROR* mstb 00000000f21f0a30 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed)

2022-08-02 Thread Tony762
Hi, same error occur to me. Dell XPS 17 9710. Ubuntu 22.04, Wayland.

```
[387809.776955] i915 :00:02.0: [drm] *ERROR* mstb 586103bb port 3: 
DPCD read on addr 0x4b0 for 1 bytes NAKed
[387809.782229] i915 :00:02.0: [drm] *ERROR* mstb 586103bb port 1: 
DPCD read on addr 0x4b0 for 1 bytes NAKed
[387809.794145] i915 :00:02.0: [drm] *ERROR* mstb 586103bb port 3: 
DPCD read on addr 0x4b0 for 1 bytes NAKed
[387809.799458] i915 :00:02.0: [drm] *ERROR* mstb 586103bb port 1: 
DPCD read on addr 0x4b0 for 1 bytes NAKed
[387809.810277] i915 :00:02.0: [drm] *ERROR* mstb 586103bb port 3: 
DPCD read on addr 0x4b0 for 1 bytes NAKed
```

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

Title:
  Window manager freezes when plugging in USB-C dock with external
  monitor ([drm] *ERROR* mstb f21f0a30 port 1: DPCD read on addr
  0x4b0 for 1 bytes NAKed)

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


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

[Bug 1981989] Re: fonttools breaks glyphslib autopkgtest: AssertionError: *.designspace file is different from expected

2022-08-02 Thread Bug Watch Updater
** Changed in: fonttools (Debian)
   Status: New => Fix Released

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

Title:
  fonttools breaks glyphslib autopkgtest: AssertionError: *.designspace
  file is different from expected

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


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

[Bug 1980836] Re: Regression in Ubuntu 22.04: Content of form field stored invisibly

2022-08-02 Thread Bug Watch Updater
** Changed in: poppler
   Status: New => Fix Released

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

Title:
  Regression in Ubuntu 22.04: Content of form field stored invisibly

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


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

[Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop

2022-08-02 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1924251

** Tags added: iso-testing

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions


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

[Bug 1923893] Re: After rescheduling an event, calendar alerts appear for the old time

2022-08-02 Thread Kai Groner
This continues to be an issue in 22.04.

** Tags removed: impish
** Tags added: jammy

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

Title:
  After rescheduling an event, calendar alerts appear for the old time

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1923893/+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()

2022-08-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: totem (Ubuntu)
   Status: New => Confirmed

-- 
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 1983294] Re: totem is coredumping, ubuntu-bug on the crash file is failing

2022-08-02 Thread 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

2022-08-02 Thread 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 1914930] Re: gjs loose gnome-shell parent and become zombie process

2022-08-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gjs (Ubuntu)
   Status: New => Confirmed

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

Title:
  gjs loose gnome-shell parent and become zombie process

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


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

[Bug 1983344] Re: GIMP failure

2022-08-02 Thread lotuspsychje
Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1983344

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  GIMP failure

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


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

[Bug 1983344] [NEW] GIMP failure

2022-08-02 Thread Gilpeigne
Public bug reported:




```
Éditeur d’image GIMP version 2.10.30
git-describe: GIMP_2_10_30
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/11/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 
11.2.0-16ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-11 
--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-bootstrap --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-11-O5cEXJ/gcc-11-11.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-11-O5cEXJ/gcc-11-11.2.0/debian/tmp-gcn/usr
 --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu 
--with-build-config=bootstrap-lto-lean --enable-link-serialization=2
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 11.2.0 (Ubuntu 11.2.0-16ubuntu1) 

# Libraries #
using babl version 0.1.92 (compiled against version 0.1.88)
using GEGL version 0.4.34 (compiled against version 0.4.34)
using GLib version 2.72.1 (compiled against version 2.71.1)
using GdkPixbuf version 2.42.8 (compiled against version 2.42.6)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.50.6 (compiled against version 1.50.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> GIMP-CRITIQUE: gimp_dock_columns_get_docks: assertion 'GIMP_IS_DOCK_COLUMNS 
> (dock_columns)' failed

Stack trace:
```

# Stack traces obtained from PID 13836 - Thread 13836 #

[New LWP 13839]
[New LWP 13840]
[New LWP 13841]
[New LWP 13842]
[New LWP 13843]
[New LWP 13844]
[New LWP 13872]
[New LWP 13880]
[New LWP 13901]
[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=0x7ffc9bb9d740, fd=22) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id   Frame 
* 1Thread 0x7fd6ee288300 (LWP 13836) "gimp-2.10"   __GI___libc_read 
(nbytes=256, buf=0x7ffc9bb9d740, fd=22) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7fd6ed658640 (LWP 13839) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7fd6ece57640 (LWP 13840) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7fd6ec656640 (LWP 13841) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7fd6eb9ff640 (LWP 13842) "gmain"   0x7fd6eef85d7f in 
__GI___poll (fds=0x55d9193f4890, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  6Thread 0x7fd6eb1fe640 (LWP 13843) "gdbus"   0x7fd6eef85d7f in 
__GI___poll (fds=0x55d919406570, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7fd6d3fff640 (LWP 13844) "async"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7fd6d2ffd640 (LWP 13872) "threaded-ml" 0x7fd6eef85d7f in 
__GI___poll (fds=0x7fd6c4013660, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  9Thread 0x7fd6d22a3640 (LWP 13880) "swap writer" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7fd69cc8a640 (LWP 13901) "paint"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 10 (Thread 0x7fd69cc8a640 (LWP 13901) "paint"):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1  0x7fd6ef03 in g_cond_wait () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x55d9177ab001 in ?? ()
No symbol table info available.
#3  0x7fd6ef202a41 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4  0x7fd6eef01b43 in start_thread (arg=) at 
./nptl/pthread_create.c:442
ret = 
pd = 
out = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140722921132640, 
-4692776140686076292, 140559730124352, 11, 140561108441168, 

[Bug 1868399] Re: Ghost copies of foreground dialogues when using GNOME Magnifier

2022-08-02 Thread Daniel van Vugt
It appears this was https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/3305 which was fixed in
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1899
(released in gnome-shell 41.0).


** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3305
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3305

** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Status: New => Fix Released

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  Ghost copies of foreground dialogues when using GNOME Magnifier

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


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

[Bug 1877686] Re: Mouse lags during desktop zoom

2022-08-02 Thread Daniel van Vugt
I expect this was fixed in GNOME 42, if not earlier. I remember this bug
but cannot reproduce it anymore.

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Mouse lags during desktop zoom

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


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