[Bug 1969121] Re: System fallback to gdm login screen when hot-plugging a external monitor in 1st time
Fixed 2 days ago in updated gdm package. -- 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/1969121 Title: System fallback to gdm login screen when hot-plugging a external monitor in 1st time To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1889686] Re: [focal] [nvidia] Patch causes small text in Pop!OS: x11-Add-support-for-fractional-scaling-using-Randr.patch
For what it's worth, the only difference between Ubuntu and Pop regarding Mutter is that we've removed the xrandr patching causing this issue. We tested the most recent version of the patch in proposed for Focal at this time, and the issue still occurs there. Given that it's an experimental feature, it's been more important for us to release 3.36.4 without the patch, than to stick to 3.36.3 until it's fixed. -- 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/1889686 Title: [focal] [nvidia] Patch causes small text in Pop!OS: x11-Add-support- for-fractional-scaling-using-Randr.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1889686/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1889686] Re: [focal] [nvidia] Patch causes small text: x11-Add-support-for-fractional-scaling-using-Randr.patch
The issue is super small text in all GDM and GNOME Shell elements when the display is being driven by NVIDIA graphics. The problem is caused by the patch in the title. If you switch to Intel graphics, the text is back to normal. If you switch to NVIDIA, the text shrinks down to what looks like 50% its original size. Some people experienced the opposite, with text appearing to be at 200% scale. -- 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/1889686 Title: [focal] [nvidia] Patch causes small text: x11-Add-support-for- fractional-scaling-using-Randr.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1889686/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1889686] Re: [focal] [nvidia] Patch causes small text: x11-Add-support-for-fractional-scaling-using-Randr.patch
We (System76) were able to replicate the issue on most of our NVIDIA laptops in NVIDIA mode, with the exception of the addw1. We've therefore repackaged mutter in Pop without the patch, so it's no longer a problem for us. You can find screenshots of the problem in this issue: https://github.com/pop-os/pop/issues/1170 ** Bug watch added: github.com/pop-os/pop/issues #1170 https://github.com/pop-os/pop/issues/1170 -- 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/1889686 Title: [focal] [nvidia] Patch causes small text: x11-Add-support-for- fractional-scaling-using-Randr.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1889686/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1889686] [NEW] [focal] [nvidia] Patch causes small text: x11-Add-support-for-fractional-scaling-using-Randr.patch
Public bug reported: With the package currently proposed for 20.04, NVIDIA systems are experiencing very small text in GDM and GNOME Shell. Removing x11-Add- support-for-fractional-scaling-using-Randr.patch fixes it. ** 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/1889686 Title: [focal] [nvidia] Patch causes small text: x11-Add-support-for- fractional-scaling-using-Randr.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1889686/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846541] Re: sigsegv in gtk_widget_get_scale_factor
Details from address sanitizer: Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: AddressSanitizer:DEADLYSIGNAL Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: = Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: ==11918==ERROR: AddressSanitizer: SEGV on unknown address 0x0006 (pc 0x7f58b1ab7c7d bp 0x0002 sp 0x7ffd3aad4da0 T0) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: ==11918==The signal is caused by a READ memory access. Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: ==11918==Hint: address points to the zero page. Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #0 0x7f58b1ab7c7c in g_slice_alloc (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x6fc7c) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #1 0x7f58b1abc687 in g_string_sized_new (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x74687) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #2 0x7f58b1a9baef (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x53aef) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #3 0x7f58b1a9e01a in g_markup_parse_context_parse (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5601a) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #4 0x7f58b22f1bdd (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x13abdd) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #5 0x7f58b22ebd50 in gtk_builder_add_from_resource (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x134d50) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #6 0x7f58b22ef2eb in gtk_builder_new_from_resource (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x1382eb) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #7 0x7f58b22d5c9f (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x11ec9f) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #8 0x7f58b1b87de2 in g_cclosure_marshal_VOID__OBJECTv (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x17de2) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #9 0x7f58b1b84935 (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x14935) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #10 0x7f58b1ba136b in g_signal_emit_valist (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x3136b) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #11 0x7f58b1ba19b2 in g_signal_emit (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x319b2) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #12 0x7f58b2565e57 in gtk_window_set_application (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x3aee57) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #13 0x7f58b1b8a710 (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x1a710) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #14 0x7f58b1b8c277 in g_object_new_valist (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x1c277) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #15 0x7f58b1b8c5cc in g_object_new (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x1c5cc) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #16 0x56047418a910 in gcal_application_activate ../src/gui/gcal-application.c:385 Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #17 0x7f58b1b84935 (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x14935) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #18 0x7f58b1ba136b in g_signal_emit_valist (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x3136b) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #19 0x7f58b1ba1fa8 in g_signal_emit_by_name (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x31fa8) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #20 0x7f58b1cb0bbc (/lib/x86_64-linux-gnu/libgio-2.0.so.0+0xe1bbc) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #21 0x7f58b1cda053 (/lib/x86_64-linux-gnu/libgio-2.0.so.0+0x10b053) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #22 0x7f58b1a9972d in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5172d) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #23 0x7f58b1a99adf (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x51adf) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #24 0x7f58b1a99b82 in g_main_context_iteration (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x51b82) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #25 0x7f58b1caea64 in g_application_run (/lib/x86_64-linux-gnu/libgio-2.0.so.0+0xdfa64) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #26 0x56047418881f in main ../src/main.c:40 Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #27 0x7f58b15aa1e2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x271e2) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: #28 0x56047418460d in _start (/usr/bin/gnome-calendar+0x5360d) Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: AddressSanitizer can not provide additional info. Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: SUMMARY: AddressSanitizer: SEGV (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x6fc7c) in g_slice_alloc Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: ==11918==ABORTING -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is
[Bug 1846541] Re: sigsegv in gtk_widget_get_scale_factor
AddressSanitizer:DEADLYSIGNAL = ==11918==ERROR: AddressSanitizer: SEGV on unknown address 0x0006 (pc 0x7f58b1ab7c7d bp 0x0002 sp 0x7ffd3aad4da0 T0) ==11918==The signal is caused by a READ memory access. ==11918==Hint: address points to the zero page. #0 0x7f58b1ab7c7c in g_slice_alloc (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x6fc7c) #1 0x7f58b1abc687 in g_string_sized_new (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x74687) #2 0x7f58b1a9baef (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x53aef) #3 0x7f58b1a9e01a in g_markup_parse_context_parse (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5601a) #4 0x7f58b22f1bdd (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x13abdd) #5 0x7f58b22ebd50 in gtk_builder_add_from_resource (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x134d50) #6 0x7f58b22ef2eb in gtk_builder_new_from_resource (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x1382eb) #7 0x7f58b22d5c9f (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x11ec9f) #8 0x7f58b1b87de2 in g_cclosure_marshal_VOID__OBJECTv (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x17de2) #9 0x7f58b1b84935 (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x14935) #10 0x7f58b1ba136b in g_signal_emit_valist (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x3136b) #11 0x7f58b1ba19b2 in g_signal_emit (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x319b2) #12 0x7f58b2565e57 in gtk_window_set_application (/lib/x86_64-linux-gnu/libgtk-3.so.0+0x3aee57) #13 0x7f58b1b8a710 (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x1a710) #14 0x7f58b1b8c277 in g_object_new_valist (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x1c277) #15 0x7f58b1b8c5cc in g_object_new (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x1c5cc) #16 0x56047418a910 in gcal_application_activate ../src/gui/gcal-application.c:385 #17 0x7f58b1b84935 (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x14935) #18 0x7f58b1ba136b in g_signal_emit_valist (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x3136b) #19 0x7f58b1ba1fa8 in g_signal_emit_by_name (/lib/x86_64-linux-gnu/libgobject-2.0.so.0+0x31fa8) #20 0x7f58b1cb0bbc (/lib/x86_64-linux-gnu/libgio-2.0.so.0+0xe1bbc) #21 0x7f58b1cda053 (/lib/x86_64-linux-gnu/libgio-2.0.so.0+0x10b053) #22 0x7f58b1a9972d in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5172d) #23 0x7f58b1a99adf (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x51adf) #24 0x7f58b1a99b82 in g_main_context_iteration (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x51b82) #25 0x7f58b1caea64 in g_application_run (/lib/x86_64-linux-gnu/libgio-2.0.so.0+0xdfa64) #26 0x56047418881f in main ../src/main.c:40 #27 0x7f58b15aa1e2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x271e2) #28 0x56047418460d in _start (/usr/bin/gnome-calendar+0x5360d) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x6fc7c) in g_slice_alloc ==11918==ABORTING -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1846541 Title: sigsegv in gtk_widget_get_scale_factor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1846541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846541] [NEW] sigsegv in gtk_widget_get_scale_factor
Public bug reported: Occasionally when launching the calendar from the overview, it segfaults at startup. This does not seem to happen when launched from the terminal. Logs from journald: Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Oct 03
[Bug 1818905] Re: Store screenshots to the org.gnome.gnome-screenshot auto-save-directory directory, if defined
Updating this to state that GNOME has yet to make a decision on how to approach this, but whatever decision they make will not consist of sharing an application-specific variable with GDM. They seem to be hinting that they will create a global variable that applications can use, but they've yet to make a decisions on where or how they want it implemented. Still waiting for feedback on the implementation specifics. ** Changed in: gnome-shell (Ubuntu) Status: In Progress => 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/1818905 Title: Store screenshots to the org.gnome.gnome-screenshot auto-save- directory directory, if defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1818905/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)
This still occurs in 19.04 with nvidia-driver-418. -- 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/1769857 Title: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818905] [NEW] Store screenshots to the org.gnome.gnome-screenshot auto-save-directory directory, if defined
Public bug reported: When the `PrintScrn` key is pressed in GNOME Shell, it takes a screenshot and writes it to `$HOME/Pictures`, or otherwise falling back to `$HOME` if that directory is not found. The `gnome-screenshot` tool does a similar action, but also checks for the existence of the `auto- save-directory` gsetting in `org.gnome.gnome-screenshot`. This will allow GNOME Shell to also use that key, and store screenshots in this location when found. ### Implementation Note I added a `CowPtr` type to make it possible for the `get_screenshot_directory()` function to return a `gchar*` which is either owned or borrowed, and to free a value when it is owned. `g_get_user_special_dir ()` and `g_get_home_dir ()` return `gchar*` values which are owned by GLib, and must not be freed, but `g_settings_get_string` is owned, and must be freed. Alternatively, I could `g_strdup()` the values to copy them onto the heap. ### Testing 1. Before applying the patch, take a screenshot with the PrintScrn key. 2. A screenshot should now be stored in `$HOME/Pictures`. 3. Create the new screenshot directory, and set the value for gnome-screenshot: ```sh mkdir $HOME/Screenshots gsettings set org.gnome.gnome-screenshot auto-save-directory $HOME/Screenshots ``` 4. Take the screenshot again, and notice that it stores in `$HOME/Pictures` instead of `$HOME/Screenshots` 5. Apply the patch, and restart `gnome-shell`, then take the screenshot again 6. The screenshot should be written in `$HOME/Screenshots` instead of `$HOME/Pictures`. 7. Delete the gsettings value, and try again, to see that it returns to storing screenshots in `$HOME/Pictures` ```sh gsettings reset org.gnome.gnome-screenshot auto-save-directory ``` ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Patch added: "screenshot_dir.patch" https://bugs.launchpad.net/bugs/1818905/+attachment/5244172/+files/screenshot_dir.patch -- 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/1818905 Title: Store screenshots to the org.gnome.gnome-screenshot auto-save- directory directory, if defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1818905/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774094] Re: [18.04] [3.26.3-0ubuntu4] .desktop extension is duplicated when renaming a .desktop file
@seb128 I guess that means we'll have to keep carrying the patch ourselves for bionic in our repos. Personally, I think you should reconsider it if the desktop is part of your "Long Term Support". -- 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/1774094 Title: [18.04] [3.26.3-0ubuntu4] .desktop extension is duplicated when renaming a .desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774094/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798877] [NEW] [cosmic] Mobile broadband & WiFi are displayed in Power even if they don't exist
Public bug reported: https://github.com/pop-os/pop/issues/370 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/1798877 Title: [cosmic] Mobile broadband & WiFi are displayed in Power even if they don't exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1798877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774094] Re: [18.04] [3.26.3-0ubuntu4] .desktop extension is duplicated when renaming a .desktop file
Submitted PR upstream to Nautilus' 3.26 branch: https://gitlab.gnome.org/GNOME/nautilus/merge_requests/241/diffs -- 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/1774094 Title: [18.04] [3.26.3-0ubuntu4] .desktop extension is duplicated when renaming a .desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774094/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774094] Re: [18.04] [3.26.3-0ubuntu4] .desktop extension is duplicated when renaming a .desktop file
GNOME merged the changes for their 3.26 branch, so it's now up to Ubuntu to make their move for 18.04 -- 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/1774094 Title: [18.04] [3.26.3-0ubuntu4] .desktop extension is duplicated when renaming a .desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774094/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774094] Re: [18.04] [3.26.3-0ubuntu4] .desktop extension is duplicated when renaming a .desktop file
** Summary changed: - [Patch Included] 3.26.3-0ubuntu4 .desktop extension is duplicated when renaming a .desktop file + [18.04] [3.26.3-0ubuntu4] .desktop extension is duplicated when renaming a .desktop file -- 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/1774094 Title: [18.04] [3.26.3-0ubuntu4] .desktop extension is duplicated when renaming a .desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774094/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774094] Re: [Patch Included] 3.26.3-0ubuntu4 .desktop extension is duplicated when renaming a .desktop file
** Patch removed: ".desktop rename patch for Nautilus" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774094/+attachment/5146234/+files/desktop-rename.patch ** Patch added: ".desktop rename patch for Nautilus" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774094/+attachment/5146415/+files/desktop-rename.patch ** Description changed: When attempting to rename a .desktop file in Ubuntu 18.04, .desktop is automatically appended. This causes the .desktop extension to get duplicated, where renaming `app.desktop` to `app2.desktop` will actually - rename it to `app2.desktop.desktop`. The included patch fixes the issue. + rename it to `app2.desktop.desktop`. + + The included patch fixes the issue to check if the new name already has + the `.desktop` suffix, and appends the extension only if it is missing. ** Description changed: When attempting to rename a .desktop file in Ubuntu 18.04, .desktop is automatically appended. This causes the .desktop extension to get duplicated, where renaming `app.desktop` to `app2.desktop` will actually rename it to `app2.desktop.desktop`. - The included patch fixes the issue to check if the new name already has - the `.desktop` suffix, and appends the extension only if it is missing. + The included patch will check if the new name already has the `.desktop` + suffix, and appends the extension only if it is missing. -- 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/1774094 Title: [Patch Included] 3.26.3-0ubuntu4 .desktop extension is duplicated when renaming a .desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774094/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774094] [NEW] [Patch Included] 3.26.3-0ubuntu4 .desktop extension is duplicated when renaming a .desktop file
Public bug reported: When attempting to rename a .desktop file in Ubuntu 18.04, .desktop is automatically appended. This causes the .desktop extension to get duplicated, where renaming `app.desktop` to `app2.desktop` will actually rename it to `app2.desktop.desktop`. The included patch fixes the issue. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Patch added: ".desktop rename patch for Nautilus" https://bugs.launchpad.net/bugs/1774094/+attachment/5146234/+files/desktop-rename.patch -- 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/1774094 Title: [Patch Included] 3.26.3-0ubuntu4 .desktop extension is duplicated when renaming a .desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774094/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
