[Bug 1948612] Re: gnome-shell crashed with SIGSEGV in std::__uniq_ptr_impl::_M_ptr from std::unique_ptr::get from std::unique_ptr::operator bool from GjsMaybeOwned::get
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1948612 Title: gnome-shell crashed with SIGSEGV in std::__uniq_ptr_impl::_M_ptr from std::unique_ptr::get from std::unique_ptr::operator bool from GjsMaybeOwned::get To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948612/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963770] Re: gnome-shell crashed with SIGSEGV
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, processing it in order to get sufficient information for the developers failed (it does not generate an useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report. Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => 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/1963770 Title: gnome-shell crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963770/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1933890] Re: No wacom tablet or stylus discovered, Fujitsu T935
** Package changed: gnome-control-center (Ubuntu) => libwacom (Ubuntu) ** Changed in: libwacom (Ubuntu) Assignee: (unassigned) => Rob Frohne (frohro) ** Changed in: libwacom (Ubuntu) Status: New => In Progress ** Changed in: libwacom (Ubuntu) Importance: Undecided => Medium ** No longer affects: mutter (Ubuntu) -- 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/1933890 Title: No wacom tablet or stylus discovered, Fujitsu T935 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1933890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766775] Re: "Automatic suspend" notifications do not disappear
** Tags added: focal -- 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/1766775 Title: "Automatic suspend" notifications do not disappear To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1766775/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963906] Re: Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it
The gnome-control-center 1:41.4-1ubuntu3.1 indeed fix the issue. -- 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/1963906 Title: Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1963906/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962761] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1962761/+attachment/5566718/+files/StacktraceSource.txt -- 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/1962761 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1962761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962761] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1962761/+attachment/5566719/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1962761/+attachment/5565047/+files/CoreDump.gz -- 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/1962761 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1962761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962761] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1962761/+attachment/5566717/+files/Stacktrace.txt -- 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/1962761 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1962761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962761] nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()
StacktraceTop: gtk_widget_get_ancestor (widget=0x55d68dfbd340, widget_type=94379979195536) at ../../../../gtk/gtkwidget.c:11653 button_data_file_changed (file=0x55d68d4c4c20, button_data=0x55d68d7d05a0) at ../src/nautilus-pathbar.c:952 g_closure_invoke (closure=0x55d68d1dbc90, return_value=0x0, n_param_values=1, param_values=0x7ffc0e3c04c0, invocation_hint=0x7ffc0e3c0440) at ../../../gobject/gclosure.c:830 signal_emit_unlocked_R (node=node@entry=0x55d68d36b400, detail=detail@entry=0, instance=instance@entry=0x55d68d4c4c20, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffc0e3c04c0) at ../../../gobject/gsignal.c:3744 g_signal_emit_valist (instance=, signal_id=, detail=, var_args=var_args@entry=0x7ffc0e3c0670) at ../../../gobject/gsignal.c:3497 -- 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/1962761 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1962761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841826] Re: Going to sleep instead of logging in while lid closed & external display
The problem is that laptop go to suspend during boot because lid is closed. The behavior is actually highly depends on the hardware you use. It works for me with Lenovo Thinkpad P52 + Lenovo Thinkpad Thunderbolt 3 Gen2 dock station. Here is my full logind.conf: #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate HandleLidSwitch=lock HandleLidSwitchExternalPower=lock HandleLidSwitchDocked=ignore #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s #IdleAction=ignore #IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 Here is the ways i found to deal with that: 1) Play with logind.conf params (https://www.freedesktop.org/software/systemd/man/logind.conf.html - manual for configuration) 2) Use gnome-tweaks to disable suspend on lid closed (it actually creates ~/.config/autostart/ignore-lid-switch-tweak.desktop to achieve this) - does nothing for me 3) There is an option (which i use in combination with logind.conf) in Lenovo BIOS to use external docked monitor as main screen during boot - check if there is similar option in your BIOS. Please, let us know if you will find a solution for your hardware -- 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/1841826 Title: Going to sleep instead of logging in while lid closed & external display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1841826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841826] Re: Going to sleep instead of logging in while lid closed & external display
Shadrin, I tried that... removed the # from the start of that line so it was set to ignore. It had no effect. I notice that there is another parameter LidSwitchIgnoreInhibited. That is set to yes. What is the function of that parameter, do you know? Thanks... AND I CONCUR: Please correct this 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/1841826 Title: Going to sleep instead of logging in while lid closed & external display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1841826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
This bug was fixed in the package ubuntu-drivers-common - 1:0.9.5.1 --- ubuntu-drivers-common (1:0.9.5.1) jammy; urgency=medium * Change maximum open file descriptors limit for the process in the test suite. This should fix the FTBFS. -- Alberto Milone Mon, 07 Mar 2022 17:16:26 +0100 ** Changed in: ubuntu-drivers-common (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1958488 Title: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852183] Re: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93 and 176)
** Changed in: df-libreoffice Status: Confirmed => Won't Fix -- 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/1852183 Title: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93 and 176) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852183]
@albertoma/Moshpirit: Please create a new bug as this one here is specifically about the Mutter situation. -- 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/1852183 Title: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93 and 176) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962566] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1962566/+attachment/5566644/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1962566/+attachment/5564431/+files/CoreDump.gz ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium -- 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/1962566 Title: gnome-shell crash after resume from suspend in gdm/util.js:154 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1962566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962566] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1962566/+attachment/5566642/+files/Stacktrace.txt -- 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/1962566 Title: gnome-shell crash after resume from suspend in gdm/util.js:154 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1962566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962566] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1962566/+attachment/5566643/+files/StacktraceSource.txt -- 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/1962566 Title: gnome-shell crash after resume from suspend in gdm/util.js:154 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1962566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962566] gnome-shell crash after resume from suspend in gdm/util.js:154
StacktraceTop: g_source_get_context (source=source@entry=0xa0c0) at ../../../glib/gmain.c:1481 g_task_return (type=, task=0x55ba93253a70) at ../../../gio/gtask.c:1278 g_task_return (task=0x55ba93253a70, type=) at ../../../gio/gtask.c:1249 g_task_return_error (task=, error=) at ../../../gio/gtask.c:1889 fp_device_task_return_in_idle_cb (user_data=0x55ba9326a220) at /usr/include/glib-2.0/glib/gmem.h:213 -- 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/1962566 Title: gnome-shell crash after resume from suspend in gdm/util.js:154 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1962566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963906] Re: Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it
This bug was fixed in the package gnome-control-center - 1:41.4-1ubuntu3.1 --- gnome-control-center (1:41.4-1ubuntu3.1) jammy; urgency=medium * debian/patches/git_owe_settings.patch: Fix OWE settings (lp: #1963906) -- Sebastien Bacher Mon, 07 Mar 2022 17:05:27 +0100 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- 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/1963906 Title: Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1963906/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs
Don't know if this is possible, but would there be a way to have gdb stop at the point where the segfault occurs in the updated library when using the previous release to see what differs? I want to help you track this down, but I am unsure what else I can do at this point. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962807 Title: segfault in libgtk-x11-2.0.so.0 with several programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963906] Re: Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Committed -- 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/1963906 Title: Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1963906/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963241] Re: [FFe] evince 42
Hey Jeremy! Thanks for filling in this FFe. Did you do a test build of the new evince for non-amd64 architectures as well (like in some PPA, for instance)? Also, I assume that the two reverted commits for the new libarchive support have been rather non-invasive, right? If the answer is 'yes' for both, I think we can go ahead with this FFe. Seeing that the NEWS file advertises the libarchive >= 3.6.0 dependency, I was wondering: do you want/need to have this in jammy? Are we missing out (or risking regressing) some features by sticking with the old version? I don't think Foundations had plans on pulling in the new upstream version past FF, but we could discuss that if there is *actual* need for it (since it's out since last month). Though Debian's still on 3.5.2, and so far this was a merge/sync. ** Changed in: evince (Ubuntu) Status: New => Incomplete -- 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/1963241 Title: [FFe] evince 42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1963241/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963902] Re: xdg-user-dirs-gtk-update not working properly
Thank you for your bug report. What xdg-user-dirs-gtk-update is doing is that if the session locale is changed to another language it will suggest renaming the directories to words that make sense in the new language ** Package changed: evince (Ubuntu) => xdg-user-dirs-gtk (Ubuntu) ** Changed in: xdg-user-dirs-gtk (Ubuntu) Importance: Undecided => Low ** Changed in: xdg-user-dirs-gtk (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xdg-user-dirs-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1963902 Title: xdg-user-dirs-gtk-update not working properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs-gtk/+bug/1963902/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963906] Re: Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it
MP in upstream fixing the issue https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1232 https://gitlab.gnome.org/GNOME/network-manager-applet/-/merge_requests/108 -- 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/1963906 Title: Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1963906/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963906] [NEW] Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it
Public bug reported: Refer to https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/1521 Reproduce step: 1. Boot into Ubuntu Jammy 2. Connect to Wi-Fi 6GHz OWE network 3. Try to configure the network to static IP 4. Reboot, then the network is not able to active anymore ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu3 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: Mon Mar 7 20:34:53 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X192 InstallationDate: Installed on 2022-03-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-03-07 (0 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy oem-priority third-party-packages ** Description changed: - Refer to gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1521 + Refer to https://gitlab.gnome.org/GNOME/gnome-control- + center/-/issues/1521 Reproduce step: 1. Boot into Ubuntu Jammy 2. Connect to Wi-Fi 6GHz OWE network 3. Try to configure the network to static IP 4. Reboot, then the network is not able to active anymore ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu3 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: Mon Mar 7 20:34:53 2022 DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X192 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-focal-amd64-20200502-85+fossa-psyduck+X192 InstallationDate: Installed on 2022-03-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-03-07 (0 days ago) ** Tags added: oem-priority -- 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/1963906 Title: Can't active Wi-Fi 6GHz OWE network anymore once reconfigure it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1963906/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963905] Re: /usr/bin/nautilus:11:gtk_widget_get_ancestor:button_data_file_changed:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist
*** This bug is a duplicate of bug 1962761 *** https://bugs.launchpad.net/bugs/1962761 ** This bug has been marked a duplicate of bug 1962761 nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() -- 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/1963905 Title: /usr/bin/nautilus:11:gtk_widget_get_ancestor:button_data_file_changed:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1963905/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962761] Re: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()
https://errors.ubuntu.com/problem/129adc3ee2e72c20335397eb652e701228616925 ** Changed in: nautilus (Ubuntu) Importance: Undecided => High ** Information type changed from Private to Public -- 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/1962761 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1962761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963905] [NEW] /usr/bin/nautilus:11:gtk_widget_get_ancestor:button_data_file_changed:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist
*** This bug is a duplicate of bug 1962761 *** https://bugs.launchpad.net/bugs/1962761 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:42~beta-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/129adc3ee2e72c20335397eb652e701228616925 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: jammy vivid xenial yakkety -- 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/1963905 Title: /usr/bin/nautilus:11:gtk_widget_get_ancestor:button_data_file_changed:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1963905/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963902] [NEW] xdg-user-dirs-gtk-update not working properly
Public bug reported: Hello. It seems to me that the xdg-user-dirs-gtk-update command does nothing at all. I want to change the location of the download directory. So I move the directory with this command: "mv -v /media/Common/a/Downloads /media/Common/a/BisDownloads" Then I update my reference file with this command: "xdg-user-dirs-update --set DOWNLOAD /media/Commun/a/DownloadsBis" Then I think to inform the software that the directory has changed by doing this command: "xdg-user-dirs-gtk-update" But when initiating a download, it cannot be done with the error message "...unable to save because an unknown error has occurred" Also, the "files" application continues to reference the old directory as if no update had been made. I have to log out and log back in to get everything working properly again. On the other hand, would it be possible to modify the contents of the file "user-dirs.dirs" to clearly say if the modification carried out by the command "xdg-user-dirs-update --set DOWNLOAD /media/Commun/a/TéléchargementsBis" is immediately carried out wherever necessary or if it is necessary to make another additional command or if it is necessary to wait for the next session launch because the message is not very understandable by saying only that the modifications are not lost. UBUNTU version 20.04 Thank you. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 41.3-3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 13:09:20 2022 InstallationDate: Installed on 2022-02-16 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220216) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (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 evince in Ubuntu. https://bugs.launchpad.net/bugs/1963902 Title: xdg-user-dirs-gtk-update not working properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1963902/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963896] Re: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()
*** This bug is a duplicate of bug 1962761 *** https://bugs.launchpad.net/bugs/1962761 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1962761, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1963896/+attachment/5566468/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1963896/+attachment/5566470/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1963896/+attachment/5566474/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1963896/+attachment/5566475/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1963896/+attachment/5566476/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1963896/+attachment/5566477/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1963896/+attachment/5566478/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1962761 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1963896 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1963896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine
** Tags added: rls-jj-incoming -- 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/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963754] Re: No brightness slider in settings
** Package changed: ubuntu => gnome-shell (Ubuntu) -- 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/1963754 Title: No brightness slider in settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963754/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963754] [NEW] No brightness slider in settings
You have been subscribed to a public bug: This page mentions a brightness slider : https://help.ubuntu.com/22.04/ubuntu-help/display-brightness.html.en When I click on the system settings I see a (sound) volume slider but no brightness slider. screenshot : https://i.imgur.com/N6EWUra.png lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 apt update/upgrade done today 2022-03-05 Gnome version 42.beta Windowing system X11 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- No brightness slider in settings https://bugs.launchpad.net/bugs/1963754 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
** Tags removed: gdm3 ** Tags added: nvidia -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1958488 Title: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1956143] Re: gnome-control-center requires libcheese8 and libcheese-gtk25
the -faces package contains only icons, libcheese is used by the user panel to allow taking a picture for the profile, it's a shared library and isn't optional, without it the users panel wouldn't start -- 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/1956143 Title: gnome-control-center requires libcheese8 and libcheese-gtk25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956143/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
** Summary changed: - [nvidia][xorg] display hangs on boot LOGO + [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe ** Tags added: gdm3 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1958488 Title: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962523] Re: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed
** Tags added: gdm3 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine
** Tags added: gdm3 -- 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/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
