[Bug 1983483] Re: totem crashing inside nouveau DRI when replaying video (actually nouveau bug?)
*** This bug is a duplicate of bug 1497593 *** https://bugs.launchpad.net/bugs/1497593 That's a very old problem with nouveau... I would recommend opening the Additional Drivers app and installing a proprietary Nvidia driver instead. -- 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 1983508] Re: Moving windows between monitors with different scaling causes isues
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 1983508 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. ** Tags added: focal ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/1983508 Title: Moving windows between monitors with different scaling causes isues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1983508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983456] Re: Context menu options are shown under dock panel and can not be chosen on Ubuntu 22.04
The shell defines a "work area" that is the available desktop space where windows can be automatically placed. So that's the screen minus permanent panels/docks. If your dock is set to auto-hide then it will indeed cover part of the work area where windows (including menus) are allowed to appear. Solving this for app windows is not possible without disabling auto- hide. But it might be possible to solve for this menu case by changing the stacking order. I don't really know how that would be done in a Wayland session but it does mean the bug can be reassigned back to the dock and shell... ** Package changed: nautilus (Ubuntu) => gnome-shell-extension-ubuntu-dock (Ubuntu) ** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => New ** Tags added: wayland wayland-session -- 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/1983456 Title: Context menu options are shown under dock panel and can not be chosen on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1983456/+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?)
*** This bug is a duplicate of bug 1497593 *** https://bugs.launchpad.net/bugs/1497593 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1497593, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1497593 [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. -- 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 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()
Thanks. That suggests even this problem might be triggered by the presence of nouveau. -- 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 1983481] Re: Can't report totem crash with ubuntu-bug
** Package changed: totem (Ubuntu) => apport (Ubuntu) -- 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/apport/+bug/1983481/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983523] Re: Evolution / Evolution EWS using Oauth2 Segfault when adding account
I have further found that this appears to be related Wayland in some manner, likely something with nvidia too? I can't tell. ** Attachment added: "Coredump" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1983523/+attachment/5606825/+files/_usr_bin_evolution.1000.crash -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1983523 Title: Evolution / Evolution EWS using Oauth2 Segfault when adding account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1983523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983523] [NEW] Evolution / Evolution EWS using Oauth2 Segfault when adding account
Public bug reported: Ubuntu 22.04.1 LTS. When attempting to add an account to Evolution, I am met with a segmentation fault when the authentication portion begins. To test this scenario/recreate it, all you need to do is the following. You do not require any office365 account or anything to cause this segfault. 1) Load Evolution 2) Create a new account 3) Use whate...@whatever.com 4) Set it to skip detection 5) Set it to an Exchange Web Services 6) Change Authentication to oauth2. 7) Click fetch. evolution-common/jammy-updates,jammy-updates,now 3.44.1-0ubuntu1 all [installed,automatic] evolution-data-server-common/jammy-updates,jammy-updates,now 3.44.2-0ubuntu1 all [installed,automatic] evolution-data-server-dev/jammy-updates 3.44.2-0ubuntu1 amd64 evolution-data-server-dev/jammy-updates 3.44.2-0ubuntu1 i386 evolution-data-server-doc/jammy-updates,jammy-updates 3.44.2-0ubuntu1 all evolution-data-server-tests/jammy-updates 3.44.2-0ubuntu1 amd64 evolution-data-server/jammy-updates,now 3.44.2-0ubuntu1 amd64 [installed,automatic] evolution-dev/jammy-updates 3.44.1-0ubuntu1 amd64 evolution-ews/jammy,now 3.44.0-1 amd64 [installed] evolution-plugin-bogofilter/jammy-updates,now 3.44.1-0ubuntu1 amd64 [installed,automatic] evolution-plugin-pstimport/jammy-updates,now 3.44.1-0ubuntu1 amd64 [installed,automatic] evolution-plugin-spamassassin/jammy-updates 3.44.1-0ubuntu1 amd64 evolution-plugins-experimental/jammy-updates 3.44.1-0ubuntu1 amd64 evolution-plugins/jammy-updates,now 3.44.1-0ubuntu1 amd64 [installed,automatic] evolution-rss/jammy 0.3.96-4build2 amd64 evolution/jammy-updates,now 3.44.1-0ubuntu1 amd64 [installed] libevolution/jammy-updates,now 3.44.1-0ubuntu1 amd64 [installed,automatic] libreoffice-evolution/jammy-updates 1:7.3.5-0ubuntu0.22.04.1 amd64 libsmltk0/jammy 3.4.0.47.5+syncevolution-1.5.3-1.1 amd64 libsyncevolution0/jammy 2.0.0-3 amd64 libsynthesis-dev/jammy 3.4.0.47.5+syncevolution-1.5.3-1.1 amd64 libsynthesis0v5/jammy 3.4.0.47.5+syncevolution-1.5.3-1.1 amd64 r-revolution-revobase/jammy 3.0.0-1ubuntu3 amd64 revolution-mkl/jammy 3.0.0-1ubuntu1 amd64 revolution-r/jammy,jammy 3.0.0-1ubuntu1 all syncevolution-common/jammy,jammy 2.0.0-3 all syncevolution-dbus/jammy 2.0.0-3 amd64 syncevolution-http/jammy,jammy 2.0.0-3 all syncevolution-libs-gnome/jammy 2.0.0-3 amd64 syncevolution-libs/jammy 2.0.0-3 amd64 syncevolution/jammy 2.0.0-3 amd64 ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1983523 Title: Evolution / Evolution EWS using Oauth2 Segfault when adding account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1983523/+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
*** This bug is a duplicate of bug 1973570 *** https://bugs.launchpad.net/bugs/1973570 There are currently some infrastructure issues with the crash retracers which are causing a backlog in the retracing system for the crashes. Given that Daniel could see the crash it was in fact successfully reported. -- 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 1983456] Re: Context menu options are shown under dock panel and can not be chosen on Ubuntu 22.04
** Description changed: 1. Ubuntu 22.04.1 LTS 2. Installed packeges: ... gnome-shell-common/jammy-updates,jammy-updates,now 42.2-0ubuntu0.2 all [installed,automatic] gnome-shell-extension-appindicator/jammy,jammy,now 42-2~fakesync1 all [installed,automatic] gnome-shell-extension-desktop-icons-ng/jammy-updates,jammy-updates,now 43-2ubuntu1 all [installed,automatic] gnome-shell-extension-ubuntu-dock/jammy-updates,jammy-updates,now 72~ubuntu5.22.04.1 all [installed,automatic] gnome-shell/jammy-updates,now 42.2-0ubuntu0.2 amd64 [installed,automatic] 3. Expected to choose "Property" option in right-click context menu of a folder in file manager. 4. In some position of file manager's window near middle to bottom of the screen, the context menu was shown under dock panel without possibility to choose options, the dock hides menu. - - *On Ubuntu 20.04 the menu is shown upon the dock panel, so all options - can be chosen. -- 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/1983456 Title: Context menu options are shown under dock panel and can not be chosen on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1983456/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983508] [NEW] Moving windows between monitors with different scaling causes isues
Public bug reported: When two displays are connected and one has a 200% scaling, moving apps between them results in several issues: Apps that can actively scale (such as native Nautilus, Settings...): When dragging the window around, it automatically adjusts scaling based on on which of the monitors is the majority of the app (this is probably correct behaviour), BUT when using keyboard shortcuts [Ctrl] + [Super] + ←/↑/↓/→, fullscreen windows jump around and scale correctly, but half-full screen apps (arranged by [Super] + ←/→) cannot go from the larger monitor to the smaller, they get stuck in the scaled-up version and don't fit on the smaller display. Small non-maximized windows don't have this issue, possibly because when they first move in their scaled-up state, they do fit on the smaller monitor still, and only then are they scaled down. Apps that don't support changes in scaling and only apply the new scaling on a relaunch (such as Chrome) don't have these issues, but they obviously have that other problem. Description:Ubuntu 20.04.4 LTS Release:20.04 mutter 3.36.9 What I expect: Windows covering half a full screen, when moved to a different display with different scaling (using a keyboard), stay covering half a full screen. What happens instead: When moved to a display with higher scaling, this happens correctly, but when moved to a monitor with lower scaling, they get "stuck" on both monitors in their inflated state. ** Affects: mutter (Ubuntu) Importance: Undecided Status: 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/1983508 Title: Moving windows between monitors with different scaling causes isues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1983508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983505] [NEW] close sudenly Gimp
Public bug reported: ``` Programa de retoc d'imatges de GNU version 2.10.18 git-describe: GIMP_2_10_16-38-gde7f04567d 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/9/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 9.3.0-8ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --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 --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) # Libraries # using babl version 0.1.74 (compiled against version 0.1.74) using GEGL version 0.4.22 (compiled against version 0.4.22) using GLib version 2.64.6 (compiled against version 2.64.1) using GdkPixbuf version 2.40.0 (compiled against version 2.40.0) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.44.7 (compiled against version 1.44.7) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > El GIMP-CRÍTIC: gimp_text_tool_apply: assertion 'text_tool->text != NULL' > failed Stack trace: ``` # Stack traces obtained from PID 11612 - Thread 11612 # [New LWP 11614] [New LWP 11615] [New LWP 11616] [New LWP 11617] [New LWP 11618] [New LWP 11619] [New LWP 11620] [New LWP 11621] [New LWP 11622] [New LWP 11623] [New LWP 11624] [New LWP 11625] [New LWP 11626] [New LWP 11627] [New LWP 11628] [New LWP 11629] [New LWP 11630] [New LWP 11634] [New LWP 11669] [New LWP 30805] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __libc_read (nbytes=256, buf=0x7ffe5d06f0f0, fd=17) at ../sysdeps/unix/sysv/linux/read.c:26 Id Target Id Frame * 1Thread 0x7f0fa140 (LWP 11612) "gimp-2.10" __libc_read (nbytes=256, buf=0x7ffe5d06f0f0, fd=17) at ../sysdeps/unix/sysv/linux/read.c:26 2Thread 0x7f0fa059b700 (LWP 11614) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread 0x7f0f9fd9a700 (LWP 11615) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 4Thread 0x7f0f9f599700 (LWP 11616) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 5Thread 0x7f0f9ed98700 (LWP 11617) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 6Thread 0x7f0f9e597700 (LWP 11618) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 7Thread 0x7f0f9dd96700 (LWP 11619) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 8Thread 0x7f0f9d595700 (LWP 11620) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 9Thread 0x7f0f9cd94700 (LWP 11621) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 10 Thread 0x7f0f97fff700 (LWP 11622) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 11 Thread 0x7f0f977fe700 (LWP 11623) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 12 Thread 0x7f0f96ffd700 (LWP 11624) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 13 Thread 0x7f0f967fc700 (LWP 11625) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 14 Thread 0x7f0f95ffb700 (LWP 11626) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 15 Thread 0x7f0f957fa700 (LWP 11627) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 16 Thread 0x7f0f94ff9700 (LWP 11628) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 17 Thread 0x7f0f8f8a8700 (LWP 11629) "gmain" 0x7f0fa216c99f in __GI___poll (fds=0x557f146fd7d0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 18 Thread 0x7f0f8f0a7700 (LWP 11630) "gdbus" 0x7f0fa216c99f in __GI___poll (fds=0x557f14715e10, nfds=2, timeout=-1) at
[Bug 1983483] XorgLog.txt
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
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
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
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?)
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
Your point regarding reporting crashes to Launchpad using ubuntu-bug for stable releases is tracked in this bug report: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1972115 -- 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 1968333] Re: FTBFS
I'm doing an upload now to ignore the build test failures since I need to rebuild indicator-keyboard to complete the gnome-desktop 43 library transition. Build tests are a very useful QA element so please try to get these tests working again this release cycle. ** Also affects: indicator-keyboard (Ubuntu Kinetic) Importance: High Status: New -- 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/1968333 Title: FTBFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1968333/+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
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 1983481] Re: Can't report totem crash with ubuntu-bug
When the development release of Ubuntu is being used crash reports are sent to Launchpad, while for stable releases of Ubuntu crash reports are sent to the Ubuntu Error Tracker (errors.ubuntu.com). In your /var/crash folder there should be a /var/crash/_usr_bin_totem.1000.uploaded file which will contain the unique identifier for the crash. -- 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()
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?)
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
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 1983456] Re: Context menu options are shown under dock panel and can not be chosen on Ubuntu 22.04
Thank you for quick response. * My dock set to auto-hide. * I am using Wayland. -- 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/1983456 Title: Context menu options are shown under dock panel and can not be chosen on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1983456/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964601] Re: incorrect cpu/graphics/disks information on raspi
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/1964601 ** Tags added: iso-testing -- 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/1964601 Title: incorrect cpu/graphics/disks information on raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964601/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983456] Re: Context menu options are shown under dock panel and can not be chosen on Ubuntu 22.04
* Is your dock set to auto-hide? * Are you using Wayland or Xorg? ** Tags added: jammy ** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => nautilus (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1983456 Title: Context menu options are shown under dock panel and can not be chosen on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1983456/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983456] [NEW] Context menu options are shown under dock panel and can not be chosen on Ubuntu 22.04
Public bug reported: 1. Ubuntu 22.04.1 LTS 2. Installed packeges: ... gnome-shell-common/jammy-updates,jammy-updates,now 42.2-0ubuntu0.2 all [installed,automatic] gnome-shell-extension-appindicator/jammy,jammy,now 42-2~fakesync1 all [installed,automatic] gnome-shell-extension-desktop-icons-ng/jammy-updates,jammy-updates,now 43-2ubuntu1 all [installed,automatic] gnome-shell-extension-ubuntu-dock/jammy-updates,jammy-updates,now 72~ubuntu5.22.04.1 all [installed,automatic] gnome-shell/jammy-updates,now 42.2-0ubuntu0.2 amd64 [installed,automatic] 3. Expected to choose "Property" option in right-click context menu of a folder in file manager. 4. In some position of file manager's window near middle to bottom of the screen, the context menu was shown under dock panel without possibility to choose options, the dock hides menu. *On Ubuntu 20.04 the menu is shown upon the dock panel, so all options can be chosen. ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2022-08-03 11-35-43.png" https://bugs.launchpad.net/bugs/1983456/+attachment/5606646/+files/Screenshot%20from%202022-08-03%2011-35-43.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1983456 Title: Context menu options are shown under dock panel and can not be chosen on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1983456/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 199820] Re: Win-L as shortcut to lock the screen does not work
I seem to have a similar (same?) issue: my lock screen hotkey (++L) does not lock the screen. Clicking in upper right corner of the screen and then clicking "Lock" works. Started happening immediately after an upgrade from 18.04 to 20.04. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/199820 Title: Win-L as shortcut to lock the screen does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/199820/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983449] Re: Screen does not get turned of after 1 minute of inactivity even though it is configured to do so in Settings->Power->Power Saving->Blank Screen
What result do you get from this command? gsettings get org.gnome.desktop.lockdown disable-lock-screen ** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1983449 Title: Screen does not get turned of after 1 minute of inactivity even though it is configured to do so in Settings->Power->Power Saving->Blank Screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1983449/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983453] [NEW] A locked screen does not blank after brief inactivity
Public bug reported: Started happening immediately after an upgrade from 18.04 to 20.04. Previously, when locking the screen, in short absence of activity (1 minute?), the screen would go blank. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-122.138-generic 5.4.192 Uname: Linux 5.4.0-122-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 3 10:11:52 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-02-18 (1991 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2022-08-02 (0 days ago) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Package changed: gnome-control-center (Ubuntu) => ubuntu -- 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/1983453 Title: A locked screen does not blank after brief inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1983453/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983450] [NEW] Automatic Suspend set to "Off", but the machine still suspends if I lock the screen
Public bug reported: Started happening immediately after an upgrade from 18.04 to 20.04. Probably completely unrelated to gnome control center, but the setting is there. I don't know what's responsible on acting on this setting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-122.138-generic 5.4.192 Uname: Linux 5.4.0-122-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 3 10:05:50 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-02-18 (1991 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2022-08-02 (0 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1983450 Title: Automatic Suspend set to "Off", but the machine still suspends if I lock the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983450/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1983449] [NEW] Screen does not get turned of after 1 minute of inactivity even though it is configured to do so in Settings->Power->Power Saving->Blank Screen
Public bug reported: Started happening immediately after an upgrade from 18.04 to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.4 ProcVersionSignature: Ubuntu 5.4.0-122.138-generic 5.4.192 Uname: Linux 5.4.0-122-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 3 09:48:40 2022 InstallationDate: Installed on 2017-02-18 (1991 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2022-08-02 (0 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1983449 Title: Screen does not get turned of after 1 minute of inactivity even though it is configured to do so in Settings->Power->Power Saving->Blank Screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1983449/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
