[Bug 2061850] Re: Can't authenticate in TTY after installing authd, but sudo works
The issue had been identified to be in GDM. ** Package changed: authd (Ubuntu) => gdm3 (Ubuntu) -- 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/2061850 Title: Can't authenticate in TTY after installing authd, but sudo works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2061850/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2061079] [NEW] Rendering issues on text with nvidia driver
Public bug reported: With nvidia driver, all GTK4 applications have label rendering issues. They are not refresh until passing the cursor over them, giving blank windows. The corner are white and not themed. Passing from one app scren to another one reproduces the issue. gnome-control-center or files, for instance, are blank by default. As suggested by seb128, exporting GSK_RENDERER=gl fixes the issue. Related upstream bugs and discussions are: - https://blog.gtk.org/2024/01/28/new-renderers-for-gtk/ - https://gitlab.gnome.org/GNOME/gtk/-/issues/6574 - https://gitlab.gnome.org/GNOME/gtk/-/issues/6411 - https://gitlab.gnome.org/GNOME/gtk/-/issues/6542 -- $ glxinfo name of display: :1 display: :1 screen: 0 direct rendering: Yes server glx vendor string: NVIDIA Corporation server glx version string: 1.4 server glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync client glx vendor string: NVIDIA Corporation client glx version string: 1.4 client glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_buffer, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 4096 MB Total available memory: 4096 MB Currently available dedicated video memory: 3041 MB OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GTX 1050/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 470.239.06 OpenGL core profile shading language version string: 4.60 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: GL_AMD_multi_draw_indirect, GL_AMD_seamless_cubemap_per_texture, GL_AMD_vertex_shader_layer, GL_AMD_vertex_shader_viewport_index, GL_ARB_ES2_compatibility, GL_ARB_ES3_1_compatibility, GL_ARB_ES3_2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_arrays_of_arrays, GL_ARB_base_instance, GL_ARB_bindless_texture, GL_ARB_blend_func_extended, GL_ARB_buffer_storage, GL_ARB_clear_buffer_object, GL_ARB_clear_texture, GL_ARB_clip_control, GL_ARB_color_buffer_float, GL_ARB_compressed_texture_pixel_storage, GL_ARB_compute_shader, GL_ARB_compute_variable_group_size, GL_ARB_conditional_render_inverted, GL_ARB_conservative_depth, GL_ARB_copy_buffer, GL_ARB_copy_image, GL_ARB_cull_distance, GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_depth_texture, GL_ARB_derivative_control, GL_ARB_direct_state_access, GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, GL_ARB_draw_indirect, GL_ARB_draw_instanced, GL_ARB_enhanced_layouts,
[Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share
** Package changed: gvfs (Ubuntu) => tracker-miners (Ubuntu) ** Changed in: tracker-miners (Ubuntu) Assignee: (unassigned) => Denison Barbosa (justdenis) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: Nautilus does not use a valid Kerberos ticket when accessing Samba share To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1779890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
** Changed in: gvfs (Ubuntu) Assignee: Didier Roche (didrocks) => Sebastien Bacher (seb128) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892456] Re: [MIR] malcontent
So, this seems a ack, but the libflatpak0 MIR should be dealt first. Let's put it as in progress. ** Changed in: malcontent (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to malcontent in Ubuntu. https://bugs.launchpad.net/bugs/1892456 Title: [MIR] malcontent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/malcontent/+bug/1892456/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1891682] Re: [MIR] sane-airscan
$ ./change-override -c main -S sane-airscan Override component to main sane-airscan 0.99.25-0ubuntu1 in hirsute: universe/misc -> main sane-airscan 0.99.25-0ubuntu1 in hirsute amd64: universe/graphics/optional/100% -> main sane-airscan 0.99.25-0ubuntu1 in hirsute arm64: universe/graphics/optional/100% -> main sane-airscan 0.99.25-0ubuntu1 in hirsute armhf: universe/graphics/optional/100% -> main sane-airscan 0.99.25-0ubuntu1 in hirsute ppc64el: universe/graphics/optional/100% -> main sane-airscan 0.99.25-0ubuntu1 in hirsute riscv64: universe/graphics/optional/100% -> main sane-airscan 0.99.25-0ubuntu1 in hirsute s390x: universe/graphics/optional/100% -> main Override [y|N]? y 7 publications overridden. ** Changed in: sane-airscan (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to sane-airscan in Ubuntu. https://bugs.launchpad.net/bugs/1891682 Title: [MIR] sane-airscan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-airscan/+bug/1891682/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1917926] Re: Window focus issues for Xorg sessions in 3.38.3-3ubuntu1
same here. As the testsuite doesn’t catch this, it clearly means each shell and mutter updates should be tested both on Xorg and Wayland. Nvidia user here, so Wayland isn’t an option -- 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/1917926 Title: Window focus issues for Xorg sessions in 3.38.3-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1915570] Re: Login screen password entry not working on systems with fingerprint support
** Package changed: gdm3 (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/1915570 Title: Login screen password entry not working on systems with fingerprint support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915570/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1915570] Re: Login screen password entry not working on systems with fingerprint support
gnome-shell (3.38.3-2ubuntu1) hirsute; urgency=medium * Merge with debian, containing new upstream release (LP: #1915089) * debian/patches: Correctly handle login cancellation and failures. Ensure the GDM workers are terminated before restarting a new auth request, allowing fingerprint authentication to be restarted. (LP: #1915066) * debian/patches: Show errors on fingerprint failures and limit retries. (LP: #1865838) * debian/control: BD on gstreamer and pipewire, depend on gstreamer1.0-pipewire. Enable building with pipewire now that is in main and add runtime dependency on gstreamer-pipewire to gnome-shell (LP: #1901391). -> I feel that the "Correctly handle login cancellation and failures" can be the cause… -- 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/1915570 Title: Login screen password entry not working on systems with fingerprint support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1915570/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1915570] Re: Login screen password entry not working
Seems to be fingerprinting linked. You can’t type any characters (regular or special): - you type a "a" - the password prompt shows up a first character being input - then, the password prompt is immediately reset to empty. -- 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/1915570 Title: Login screen password entry not working on systems with fingerprint support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1915570/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1915570] Re: Login screen password entry not working
I’m getting a lot of pam failures due to fingerprints in my logs: févr. 12 08:21:51 casanier gdm-password][6277]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:51 casanier gdm-fingerprint][6278]: gkr-pam: no password is available for user févr. 12 08:21:51 casanier gdm-password][6283]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:51 casanier gdm-fingerprint][6284]: gkr-pam: no password is available for user févr. 12 08:21:52 casanier gdm-password][6289]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:52 casanier gdm-fingerprint][6290]: gkr-pam: no password is available for user févr. 12 08:21:52 casanier gdm-password][6360]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:52 casanier gdm-fingerprint][6361]: gkr-pam: no password is available for user févr. 12 08:21:52 casanier gdm-password][6366]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:52 casanier gdm-fingerprint][6367]: gkr-pam: no password is available for user févr. 12 08:21:52 casanier gdm-password][6372]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:52 casanier gdm-fingerprint][6373]: gkr-pam: no password is available for user févr. 12 08:21:52 casanier gdm-password][6378]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:52 casanier gdm-fingerprint][6379]: gkr-pam: no password is available for user févr. 12 08:21:53 casanier gdm-password][6384]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:53 casanier gdm-fingerprint][6385]: gkr-pam: no password is available for user févr. 12 08:21:53 casanier gdm-password][6390]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:53 casanier gdm-fingerprint][6391]: gkr-pam: no password is available for user févr. 12 08:21:53 casanier gdm-password][6396]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:53 casanier gdm-fingerprint][6397]: gkr-pam: no password is available for user Before getting into that state, I got very few in my logs, and after reverting my system globally, I don’t have those when logging in. I think this is the cause of the password prompt emptying. -- 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/1915570 Title: Login screen password entry not working on systems with fingerprint support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1915570/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1915570] Re: Login screen password entry not working on systems with fingerprint support
** Attachment added: "Log of upgrade list between a working and faulty reboot" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1915570/+attachment/5463728/+files/apt-upgrade-list -- 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/1915570 Title: Login screen password entry not working on systems with fingerprint support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1915570/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1915570] Re: Login screen password entry not working
Automated login is disabled here and I’m affecting by this bug too. ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New ** Tags added: tracking-hh ** Tags removed: tracking-hh ** Tags added: rls-hh-bugs -- 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/1915570 Title: Login screen password entry not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1915570/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1891157] Re: [MIR] ipp-usb
$ ./change-override -c main -S golang-github-openprinting-goipp Override component to main golang-github-openprinting-goipp 1.0.0-1 in groovy: universe/misc -> main golang-github-openprinting-goipp-dev 1.0.0-1 in groovy amd64: universe/devel/optional/100% -> main golang-github-openprinting-goipp-dev 1.0.0-1 in groovy arm64: universe/devel/optional/100% -> main golang-github-openprinting-goipp-dev 1.0.0-1 in groovy armhf: universe/devel/optional/100% -> main golang-github-openprinting-goipp-dev 1.0.0-1 in groovy i386: universe/devel/optional/100% -> main golang-github-openprinting-goipp-dev 1.0.0-1 in groovy ppc64el: universe/devel/optional/100% -> main golang-github-openprinting-goipp-dev 1.0.0-1 in groovy riscv64: universe/devel/optional/100% -> main golang-github-openprinting-goipp-dev 1.0.0-1 in groovy s390x: universe/devel/optional/100% -> main Override [y|N]? y 8 publications overridden. ** Changed in: golang-github-openprinting-goipp (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to golang-github-openprinting-goipp in Ubuntu. https://bugs.launchpad.net/bugs/1891157 Title: [MIR] ipp-usb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-openprinting-goipp/+bug/1891157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892643] Re: [SRU] Update libgweather to 3.36.1
** Changed in: libgweather (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1892643 Title: [SRU] Update libgweather to 3.36.1 To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1892643/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892643] Re: [SRU] Update libgweather to 3.36.1
I reapplied your debian/changelog directly and pushed to focal (pending approval). Thanks a lot! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1892643 Title: [SRU] Update libgweather to 3.36.1 To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1892643/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892643] Re: [SRU] Update libgweather to 3.36.1
Hey Amr and thanks for making ubuntu better. Do you mind double checking your patch? Trying to apply it on 3.36.0-1, I get those chunks failing to apply (tried both your .diff and .diff.gz): patching file debian/changelog patching file libgweather/gweather-weather.c patching file libgweather/weather-metar.c patching file meson.build patching file NEWS patching file po/lv.po Hunk #1 FAILED at 6. Hunk #2 FAILED at 830. Hunk #3 FAILED at 849. Hunk #4 FAILED at 944. Hunk #5 FAILED at 1056. 5 out of 5 hunks FAILED -- saving rejects to file po/lv.po.rej patching file po/nb.po Hunk #1 succeeded at 1 with fuzz 2. Hunk #2 FAILED at 17. Hunk #3 FAILED at 246. Hunk #4 FAILED at 537. Hunk #5 FAILED at 843. Hunk #6 FAILED at 932. Hunk #7 FAILED at 1045. Hunk #8 succeeded at 1074 with fuzz 2. Hunk #9 succeeded at 1087 with fuzz 2. Hunk #10 succeeded at 1101 with fuzz 2. Hunk #11 succeeded at 1117 with fuzz 2. 6 out of 11 hunks FAILED -- saving rejects to file po/nb.po.rej patching file po/uk.po Hunk #1 FAILED at 1. Hunk #2 FAILED at 455. Hunk #3 FAILED at 544. Hunk #4 FAILED at 726. 4 out of 4 hunks FAILED -- saving rejects to file po/uk.po.rej patching file po-locations/nb.po Hunk #1 succeeded at 1 with fuzz 2. Hunk #4 FAILED at 1748. Hunk #5 succeeded at 1757 with fuzz 1. Hunk #6 FAILED at 2094. Hunk #10 succeeded at 5624 with fuzz 1. Hunk #12 FAILED at 6455. Hunk #15 FAILED at 6532. Hunk #16 FAILED at 6547. Hunk #18 FAILED at 7011. Hunk #20 succeeded at 7566 with fuzz 2. Hunk #24 FAILED at 7946. Hunk #27 succeeded at 8879 with fuzz 1. Hunk #28 FAILED at 9175. Hunk #32 FAILED at 9750. Hunk #33 FAILED at 10098. Hunk #34 FAILED at 10319. Hunk #35 FAILED at 10361. Hunk #36 FAILED at 10459. Hunk #37 succeeded at 10491 with fuzz 2. Hunk #38 FAILED at 10535. Hunk #39 FAILED at 10871. Hunk #40 FAILED at 10887. Hunk #41 FAILED at 10915. Hunk #43 FAILED at 11159. 18 out of 50 hunks FAILED -- saving rejects to file po-locations/nb.po.rej patching file po-locations/ro.po Hunk #1 FAILED at 9. Hunk #4 FAILED at 10310. Hunk #5 FAILED at 10352. Hunk #6 FAILED at 10450. Hunk #7 FAILED at 8. 5 out of 10 hunks FAILED -- saving rejects to file po-locations/ro.po.rej patching file po-locations/sk.po Hunk #1 succeeded at 10 with fuzz 1. Hunk #2 succeeded at 1767 with fuzz 2. Hunk #7 FAILED at 7278. Hunk #8 FAILED at 7628. Hunk #9 FAILED at 7673. Hunk #10 succeeded at 7713 with fuzz 2. Hunk #12 succeeded at 8882 with fuzz 2. Hunk #13 FAILED at 10322. Hunk #14 FAILED at 10364. Hunk #15 FAILED at 10462. Hunk #16 succeeded at 10500 with fuzz 2. 6 out of 18 hunks FAILED -- saving rejects to file po-locations/sk.po.rej patching file po-locations/uk.po Hunk #3 FAILED at 5066. Hunk #4 FAILED at 17519. 2 out of 4 hunks FAILED -- saving rejects to file po-locations/uk.po.rej -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1892643 Title: [SRU] Update libgweather to 3.36.1 To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1892643/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876050] Re: Should have a way to pin "Use dedicated card" for some applications
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2716 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2716 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2716 Importance: Unknown Status: Unknown -- 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/1876050 Title: Should have a way to pin "Use dedicated card" for some applications To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876050/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876049] Re: Nvidia performance mode enabled, the Shell still show useless "Use dedicated card option"
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2715 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2715 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2715 Importance: Unknown Status: Unknown -- 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/1876049 Title: Nvidia performance mode enabled, the Shell still show useless "Use dedicated card option" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876049/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876052] [NEW] Nvidia driver, default configuration, "Use dedicated card option" for app triggers software acceleration
Public bug reported: Fresh install of 20.04 LTS with nvidia binary driver from our archive. (dual Intel/Nvidia setup) No setting change has been done. The card supports "On demand". Tested with Firefox (about:support) and Chrome (config:cpu). Both are showing the same result: - default launch -> Intel drive, OK GL_VENDOR Intel GL_RENDERER Mesa Intel(R) UHD Graphics 630 (CFL GT2) GL_VERSION 4.6 (Core Profile) Mesa 20.0.4 - select use dedicated card -> Sofware acceleration! KO GL_VENDOR Google Inc. GL_RENDERER Google SwiftShader GL_VERSION OpenGL ES 3.0 SwiftShader 4.1.0.7 Selecting the option for performance though is worse than not selecting it with our default configuration. If you open nvidia-settings, you have only one tab available (which is showing Performance mode), which is misleading because this is not the mode you are in. Note that you not on On Demand mode either as selecting it + reboot restores a an expected behavior (multiple tabs in nvidia-settings). For completeness, here are the other settings: * On Demand (manually selected): OK Right click menu option shows Use dedicated card card option: OK - default launch -> Intel drive, OK - select use dedicated card -> Nvidia, OK * Power saving mode (manually selected): OK - default launch -> Intel drive, OK * Performance mode (manually selected, meaning choose another option to change the default and selecting it back): KO Right click menu option shows Use dedicated card card option! KO - default launch -> Nvidia, OK - select use dedicated card -> Nvidia, OK, but this option shouldn’t be present. Reported this one as bug #1876049 2 additional things: - It would be great the default to be either Performance mode (real one) or On Demand for supported card (nvidia-settings has the option only if this is supported AFAIK, so it would be good to default dynamically to this one. Filed as bug #1876051 - It would be great to have a way to pin an application with "Use dedicated card". bug #1876050 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 09:22:04 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-24 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal nvidia-dedicatedcard-option ** Also affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1876052 Title: Nvidia driver, default configuration, "Use dedicated card option" for app triggers software acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876052/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876050] [NEW] Should have a way to pin "Use dedicated card" for some applications
Public bug reported: I think the menu should rather be a checkbox which pins/unpins using a dedicated card option. That way, people can always launch, for instance, their browser with nvidia hardware acceleration for instance. Something to discuss upstream of course. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 09:42:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-24 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal nvidia-dedicatedcard-option -- 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/1876050 Title: Should have a way to pin "Use dedicated card" for some applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876050/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876049] [NEW] Nvidia performance mode enabled, the Shell still show useless "Use dedicated card option"
Public bug reported: Once you select manually performance mode in nvidia-settings, GNOME Shell shouldn’t display "Use dedicated card option". Launching directly any app, in this mode, starts your application using the nvidia card already. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 09:34:54 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-24 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal nvidia-dedicatedcard-option -- 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/1876049 Title: Nvidia performance mode enabled, the Shell still show useless "Use dedicated card option" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876049/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1874191] Re: Brightness setting too high
** Package changed: zsys (Ubuntu) => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1874191 Title: Brightness setting too high To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1874191/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869444] Re: Task Manager tab: File systems completely wrong
Retargetting to correct project with tag ** Package changed: zsys (Ubuntu) => gnome-disk-utility (Ubuntu) ** Tags added: zfs -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1869444 Title: Task Manager tab: File systems completely wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1869444/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853112] Re: Applications are closed when killing the Shell (like on a hang)
Rationale: this is a regression on X11 in eoan (maybe not worth fixing for it right now), but at least, should be fixed in focal IMHO ** Tags added: rls-ff-incoming -- 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/1853112 Title: Applications are closed when killing the Shell (like on a hang) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853112] [NEW] Applications are closed when killing the Shell (like on a hang)
Public bug reported: - Open some non dbus activated apps (so, not terminal for instance) in your dock - Kill the shell with SIGKILL - Applications are being killed with the Shell being killed, apart from the dbus activated ones. This wasn't the case before 19.10 on X11. (caused by dbus user session?) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 09:42:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-24 (543 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-01-08 (314 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Description changed: - Open some non dbus activated apps (so, not terminal for instance) in your dock - Kill the shell with SIGKILL - Applications are being killed with the Shell being killed, apart from the dbus activated ones. - This wasn't the case before 19.10. (caused by dbus user session?) + This wasn't the case before 19.10 on X11. (caused by dbus user session?) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 09:42:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-24 (543 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-01-08 (314 days ago) -- 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/1853112 Title: Applications are closed when killing the Shell (like on a hang) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849512] Re: Creating a new user on top of ZFS filesystem does not create a new dataset for his home directory
zsys is handling this (adduser will try to execute it and creates a dataset, and if it can't, it fallbacks to traditional directory creation. zsys isn't installed by default on 19.10 but should be on 20.04 LTS, so I encourage you to install and test it! Thanks :) I'll have to mark the bug as invalid. If you installed zsys and you still see this behavior, do not hesitate to ping us back! ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1849512 Title: Creating a new user on top of ZFS filesystem does not create a new dataset for his home directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1849512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843652] Re: The bootmenu for zfs based Ubuntu does partly not work
Only zsys systems will have rollback, we had to revert rollback in pure ZFS systems as per this package upload: https://launchpad.net/ubuntu/+source/grub2/2.04-1ubuntu7. Indeed, we need to release note that people shouldn't upgrade the bpool as grub isn't able to read newer zfs pool versions. -- 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/1843652 Title: The bootmenu for zfs based Ubuntu does partly not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1843652/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841929] Re: Volume up/down repeat keys don't work on Xorg
This is a regression for our vast majority of users using the normal ubuntu product and quite visible one, I wouldn't put it as low. ** Changed in: gnome-shell (Ubuntu) Importance: Low => High ** Changed in: mutter (Ubuntu) Importance: Low => High -- 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/1841929 Title: Volume up/down repeat keys don't work on Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1841929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841929] [NEW] Volume up/down repeat keys don't work on Xorg
Public bug reported: GNOME Shell & mutter on 3.33.91 When pressing volume up or down on Xorg and keeping it pressed, only the first key event is sent, so the volume only goes up or down once, and doesn't scale up/down as long as you keep the button pressed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 13:45:27 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-24 (461 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-01-08 (232 days ago) ** Affects: gnome-shell Importance: Unknown Status: Unknown ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan rls-ee-incoming ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1554 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1554 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1554 Importance: Unknown Status: Unknown ** Tags added: rls-ee-incoming -- 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/1841929 Title: Volume up/down repeat keys don't work on Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1841929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823301] Re: [nvidia] Shell hangs up at random times when using nvidia-drm.modeset=1
here is the output (reenabled drm to get it back): $ glxinfo | grep OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 1050/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 390.116 OpenGL core profile shading language version string: 4.60 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.6.0 NVIDIA 390.116 OpenGL shading language version string: 4.60 NVIDIA OpenGL context flags: (none) OpenGL profile mask: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 390.116 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: $ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 eDP-1-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 160mm x 90mm 1920x1080 60.00*+ 60.0050.0059.94 1920x1080i60.0060.0050.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 74.9859.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0060.0050.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.0050.00 720x480 60.0060.0059.9459.94 640x480 75.0072.8166.6760.0059.94 720x400 70.08 ** Changed in: mutter (Ubuntu) Status: Incomplete => 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/1823301 Title: [nvidia] Shell hangs up at random times when using nvidia- drm.modeset=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1823301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822478] Re: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.
https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/365502 doesn't fix it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1822478 Title: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823301] Re: [nvidia] Shell hangs up at random times when using nvidia-drm.modeset=1
-> I'm using 2 monitors (1 internal and 1 external). -> The nvidia GPU is enabled, monitor is plugged to it through HDMI. -> The CPU usage of GNOME Shell spikes. There is no writed at the same time (the led doesn't blink) and no other process seems to run for it. The memory usages seems stable though. See log attachement which is a snapshot of CPU and MEM usage every second (you can see at the end a freeze for multiple seconds corresponding to GNOME Shell CPU spike). CPU spike can go up to 200%. -> I've run a wayland session for a period of time and didn't notice any issues. So seems Xorg specific. Note that this is a regression as I'm running Xorg + drm modeset for a year or so without experiencing that previously. ** Changed in: mutter (Ubuntu) Status: Incomplete => 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/1823301 Title: [nvidia] Shell hangs up at random times when using nvidia- drm.modeset=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1823301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822478] Re: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.
FYI, this happens even without drm enabled and only on Xorg session. Alt+F2 -> r fixes it until next reboot. -- 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/1822478 Title: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823301] Re: [nvidia] Shell hangs up at random times when using nvidia-drm.modeset=1
** Attachment added: "cpu_mem.logs" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1823301/+attachment/5253048/+files/cpu_mem.logs -- 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/1823301 Title: [nvidia] Shell hangs up at random times when using nvidia- drm.modeset=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1823301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823301] Re: [nvidia] Shell hangs up at random times when using nvidia-drm.modeset=1
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Mobile) 01:00.0 VGA compatible controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] (rev a1) -- 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/1823301 Title: [nvidia] Shell hangs up at random times when using nvidia- drm.modeset=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1823301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823301] [NEW] [nvidia] Shell hangs up at random times when using nvidia-drm.modeset=1
Public bug reported: Mutter is hanging for multiple seconds (5 or so) at random times, especially when your user session starts and you open new applications from the launcher: - the screen freeze (apps & Shell) completely - you have a second cursor that you can move and refresh during that period It seems that disabling drm nvidia support prevent the issue from happening so far. More update if it's not the case anymore. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 10:21:09 2019 InstallationDate: Installed on 2018-05-24 (315 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: Upgraded to disco on 2019-01-08 (86 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco nvidia performance -- 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/1823301 Title: [nvidia] Shell hangs up at random times when using nvidia- drm.modeset=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1823301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822478] Re: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.
s/upon/until -- 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/1822478 Title: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822478] Re: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.
Note that I'm seeing this with modeset=1 (nvidia): - Shell UI has small text (and so, small panel and such…) - icons and application have normal size Going to g-c-c => displays scaling factor is at 100% (I never changed it before on that machine). Going to 200% -> Apply. The text is giant. Then, clicking "abandon configuration" on the modal dialog will reset the text size to an expected "normal" size (and g-c-c is showing a scaling factor of 100%). This works upon next reboot. -- 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/1822478 Title: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1815550] Re: RSS grows without limit, general slowness
confirming. I'm seeing the same regularly. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Tags added: rls-dd-incoming -- 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/1815550 Title: RSS grows without limit, general slowness To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1815550/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1819126] Re: gnome-shell crashed with SIGABRT [St:ERROR:../src/st/st-image-content.c:155:st_image_content_get_preferred_size: assertion failed (priv->width > -1): (-1 > -1)]
I confirmed that 3.32.0 + trunk commits fixes the crash. ** Changed in: gnome-shell (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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1819126 Title: gnome-shell crashed with SIGABRT [St:ERROR:../src/st/st-image- content.c:155:st_image_content_get_preferred_size: assertion failed (priv->width > -1): (-1 > -1)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819126/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818246] Re: update-notifier's notification is huge due to large icon
Ok, after some more testing with new GNOME Shell (3.32.0 + some commits backported), the situation has now improved when this case happens: - there is no more icons for applications not having any appinfo, like the update-notifier one. - applications with appinfo have an icon with a decent size (typically 48x48). I think if we really want an application to have the icon showing up, let's add then appinfo to it, otherwise, the current behaviour is fine. ** Changed in: gnome-shell (Ubuntu Disco) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1818246 Title: update-notifier's notification is huge due to large icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1818246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818246] Re: update-notifier's notification is huge due to large icon
Needs to be retested with G-S 3.32 which fixes the crash https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819126. Test case is: 1. sleep 1000 on one terminal 2. kill -SIGSEGV $(pidof sleep) -> wait for update-notifier to try showing up apport (application crash) or update-notifier (system crash) windows. This can take up to 180s. -- 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/1818246 Title: update-notifier's notification is huge due to large icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1818246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817073] [NEW] GNOME Shell crash when an asset is not found (due to too many logs spawn by appindicator extension)
Public bug reported: GNOME Shell freeze and crash if appindicator can't lookup an icon. A lot of messages are spawned in the logs: Feb 20 15:40:46 neutrino gnome-shell[2735]: message repeated 2 times: [ [AppIndicatorSupport-FATAL] unable to lookup icon for Cozy Drive1_4575] Feb 20 15:40:46 neutrino gnome-shell[2735]: [AppIndicatorSupport-FATAL] unable to lookup icon for Cozy Drive1_4578 Feb 20 15:41:32 neutrino gnome-shell[2735]: message repeated 3611 times: [ [AppIndicatorSupport-FATAL] unable to lookup icon for Cozy Drive1_4578] Feb 20 15:41:32 neutrino gnome-shell[2735]: ../../../../glib/gmem.c:135: failed to allocate 32 bytes Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: GNOME Shell crashed with signal 5 Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: == Stack trace for context 0x55b19a6e3210 == Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #0 7fff92c183f0 I /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:309 (7f6f5b632550 @ 680) Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #1 7fff92c184d0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6f63cb0b80 @ 71) Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #2 7fff92c18540 I /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:260 (7f6f5b6324c0 @ 115) Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #3 7fff92c18620 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6f63cb0b80 @ 71) Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #4 7fff92c186c0 I /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:425 (7f6f5b632820 @ 960) Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #5 7fff92c18790 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6f63cb0b80 @ 71) Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #6 7fff92c18800 I self-hosted:977 (7f6f63cf0280 @ 413) Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #7 7fff92c18870 I self-hosted:977 (7f6f63cf0280 @ 413) Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #8 7fff92c188f0 I resource:///org/gnome/gjs/modules/signals.js:128 (7f6f63cc18b0 @ 386) Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #9 7fff92c18940 I /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:162 (7f6f5b6320d0 @ 96) Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #10 7fff92c189d0 I self-hosted:261 (7f6f63cc1dc0 @ 223) Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #11 7fff92c189d0 I /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:156 (7f6f5b632040 @ 65) Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #12 7fff92c18ab0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6f63cb0b80 @ 71) Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #13 7fff92c18b30 I self-hosted:981 (7f6f63cf0280 @ 474) Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #14 7fff92c18bb0 I self-hosted:981 (7f6f63cf0280 @ 474) Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #15 7fff92c19ca0 b /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/util.js:42 (7f6f5b63b670 @ 145) https://gitlab.gnome.org/GNOME/gnome-shell/issues/984 ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Tags: rls-dd-incoming ** Tags added: rls-dd-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1817073 Title: GNOME Shell crash when an asset is not found (due to too many logs spawn by appindicator extension) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1817073/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798612] Re: OSD shows volume level = 100% even if volume > 100% on first press
This is merged and released ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1798612 Title: OSD shows volume level = 100% even if volume > 100% on first press To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1798612/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722886] Re: Include logs, monitors.xml and org.gnome.desktop.* settings in the apport-retrace data
** Changed in: gnome-shell (Ubuntu) Assignee: Didier Roche (didrocks) => (unassigned) -- 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/1722886 Title: Include logs, monitors.xml and org.gnome.desktop.* settings in the apport-retrace data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1789356] Re: The wrong background flashes up briefly during the login animation since Yaru was introduced
I think Daniel was clear by changing to verification-done that this can go in. We are talking about a less than a second flash, while blocking a bunch of fixes for GNOME Shell in cosmic. Note that this second flash already existed before the fix, and that the fix is correct, it will only be correctly applied once mutter is in. Daniel, can you please state clearly your intend? Sounds like the GNOME Shell SRU is now blocked for a month, resulting for instance in still no checkbox in GDM for accessibility, which is worse than the current issue we are nitpiking on here IMHO. -- 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/1789356 Title: The wrong background flashes up briefly during the login animation since Yaru was introduced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803230] Re: [MIR] teckit & xxhash, new rdeps of texlive-bin
ack for me, seb told me he would take care of the tests. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to teckit in Ubuntu. https://bugs.launchpad.net/bugs/1803230 Title: [MIR] teckit & xxhash, new rdeps of texlive-bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/teckit/+bug/1803230/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1789356] Re: Dark purple (noise) background flashes up briefly during the login animation since Yaru was introduced
I don't have the time to do a testround again, but I can give pointers
for whoever has time to have a look:
The patch is
https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/gnome-shell/commit/?id=ddc4f511abd64d69c1150a41475d0a1ebac01dbb,
in particular:
systemBackground = new Meta.Background({ meta_display: global.display });
[res, topColor] = Clutter.Color.from_string('#6D2169');
[res, bottomColor] = Clutter.Color.from_string('#370026');
systemBackground.set_gradient(GDesktopEnums.BackgroundShading.VERTICAL,
topColor, bottomColor);
This is hardcoded in the Shell code (I made it conditional by session
type). This was made to match what is in the Yaru.css file:
#lockDialogGroup {
background: none;
background-color: none;
background-gradient-direction: vertical;
background-gradient-start: #6D2169;
background-gradient-end: #370026; }
As I don't have bionic/cosmic eyes as yours, for me, for the short while
this screen appeared, ti seemed the same gradient, with the same
VERTICAL transition.
--
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/1789356
Title:
Dark purple (noise) background flashes up briefly during the login
animation since Yaru was introduced
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789356/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1789356] Re: Dark purple (noise) background flashes up briefly during the login animation since Yaru was introduced
Are you sure it's differently? Look at the diff, it's supposively exactly the same values than Yaru. Please check it and revert the status as needed. ** Changed in: gnome-shell (Ubuntu Cosmic) Assignee: Didier Roche (didrocks) => Daniel van Vugt (vanvugt) -- 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/1789356 Title: Dark purple (noise) background flashes up briefly during the login animation since Yaru was introduced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
The best way to get it fixed is to be able to disable mod extensions, which is something I'm working on, and you can follow it on https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/2. This will probably be for dingo. -- 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/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794951] Re: Calculator (snap) is slow to start on a freshly installed Cosmic machine
I tried with gnome-3-26-1604 rev 74 is still slow fo me at first gnome- calculator application startup (with no ~/snap) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1794951 Title: Calculator (snap) is slow to start on a freshly installed Cosmic machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1794951/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798747] Re: Ticks in gdm do not show
** Merge proposal linked: https://code.launchpad.net/~didrocks/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/357609 -- 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/1798747 Title: Ticks in gdm do not show To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1798747/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798747] [NEW] Ticks in gdm do not show
Public bug reported: [Impact] At the login screen (gdm) the a11y menu has a number of options, such as large text, screen reader etc. If you turn on screen reader you can then hover over the menu items and they will be read to you. If you hover over an option that is enabled, the screen reader will tell you, for example: Screen reader. TICKED The entry in the menu item should have a tick next to it. This is what happens using the default GNOME theme. [Test Case] 1. Install new version from proposed 2. Reboot your laptop 3. Check the accessibility menu in the login screen (GDM) and ensure you have ticks near the label 4. Login and check there is no regression. 5. For bonus point, you can try GDM using vanilla gnome-shell theme by sudo update-alternatives --config gdm3.css + a reboot and GNOME Shell vanilla session (apt install gnome-session + select GNOME session on login screen) [Regression Potential] The new function exposed to gjs is calling realpath and is idempotent: it returns the filename given as a parameter on any error, or the realpath() result if there is any result, not changing the fundamental logic. If there was a regression, the Shell wouldn't even load. By checking the 5. point, we are checking we didn't impact gresources. >From https://github.com/ubuntu/yaru/issues/917. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Assignee: Didier Roche (didrocks) Status: In Progress ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Didier Roche (didrocks) ** Changed in: gnome-shell (Ubuntu) Status: New => In Progress -- 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/1798747 Title: Ticks in gdm do not show To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1798747/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798612] Re: OSD shows volume level = 100% even if volume > 100% on first press
** Description changed: - [ Rationale ] + [ Impact ] Display bug in volume OSD on volume keypress if volume > 100% (amplified) - [ Test case ] + [ Test Case ] 1. Ensure OSD is not displayed on screen avec volume > 100% via the amplified setting. 2. Press volume + or volume - on your keyboard. -> OSD is shown, but volume level is always 100%. 3. Consecutive key press displays correct volume level. Update to new gnome-shell package and ensure that when OSD is displayed, the volume bar is representing current sound volume at step 2. (so > 100%) - [ Regression potentiale ] + [ Regression potential ] If this code change triggers any error, the OSD isn't displayed, but the Shell stays up. ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Didier Roche (didrocks) ** Changed in: gnome-shell (Ubuntu) Status: New => In Progress -- 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/1798612 Title: OSD shows volume level = 100% even if volume > 100% on first press To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1798612/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798612] Re: OSD shows volume level = 100% even if volume > 100% on first press
Upstream MP: https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/266 -- 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/1798612 Title: OSD shows volume level = 100% even if volume > 100% on first press To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1798612/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798612] [NEW] OSD shows volume level = 100% even if volume > 100% on first press
Public bug reported: [ Rationale ] Display bug in volume OSD on volume keypress if volume > 100% (amplified) [ Test case ] 1. Ensure OSD is not displayed on screen avec volume > 100% via the amplified setting. 2. Press volume + or volume - on your keyboard. -> OSD is shown, but volume level is always 100%. 3. Consecutive key press displays correct volume level. Update to new gnome-shell package and ensure that when OSD is displayed, the volume bar is representing current sound volume at step 2. (so > 100%) [ Regression potentiale ] If this code change triggers any error, the OSD isn't displayed, but the Shell stays up. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1798612 Title: OSD shows volume level = 100% even if volume > 100% on first press To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1798612/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1789356] Re: Dark purple (noise) background flashes up briefly during the login animation
Fixed in gnome-shell as this is a separate parameter. Nice catch! ** Package changed: yaru-theme (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Didier Roche (didrocks) ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged -- 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/1789356 Title: Dark purple (noise) background flashes up briefly during the login animation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1789356] Re: Dark purple (noise) background flashes up briefly during the login animation
Fixed in https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/gnome- shell/commit/?id=ddc4f511abd64d69c1150a41475d0a1ebac01dbb ** Description changed: - Dark purple (noise) background flashes up briefly (for a split second) - during the login animation. + [Impact] - The login screen and gnome-shell's system background are meant to be the - same image so that the login procedure can VT switch without the user - noticing. Then the final desktop expands over the system background. - However it appears the login background and system background are not - the same image any more, causing a visible glitch during login. + Dark purple (noise) background flashes up briefly (for a split second) during the login animation. + The login screen and gnome-shell's system background are meant to be the same image so that the login procedure can VT switch without the user noticing. Then the final desktop expands over the system background. However it appears the login background and system background are not the same image any more, causing a visible glitch during login. + + [Test Case] + + 1. Install new version, logout + 2. Log in into GDM + -> Check that at login startup, the background matches GDM ones (same color, same gradient) + 3. Logout, install gnome-session + 4. Reboot so that GDM takes gnome-session into account + 5. Select GNOME session and login + -> At login startup, the background will matche the GNOME default one (from the lockscreen: grey noise), which matches GDM one if reset to default GNOME via update-alternatives. + + [Regression Potential] + + This code is loaded at session startup, if there is a syntax error, the session wouldn't start at all. + This has been of course tested before committed (both on ubuntu and GNOME sessions) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: yaru-theme-gnome-shell 18.10.2 ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Uname: Linux 4.17.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Tue Aug 28 14:19:48 2018 Dependencies: InstallationDate: Installed on 2018-05-26 (93 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1789356 Title: Dark purple (noise) background flashes up briefly during the login animation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790609] Re: Update evince to 3.28.4
** Description changed: - Impact - == + [Impact] New release in the stable 3.28 series. https://gitlab.gnome.org/GNOME/evince/commits/gnome-3-28 https://gitlab.gnome.org/GNOME/evince/blob/gnome-3-28/NEWS - Other Info - == - I am not working on this update now. + [Test Case] + 1. Install new evince version + 2. try opening multiple pdf and ps files, ensure no obvious regression is visible. - Please add --enable-ps to the build options since this version disables - viewing Postscript files as a workaround for security issues in - Ghostscript. We should fix Ghostscript instead. + [Regression Potential] + The visible regression potential is the enable-ps (see comment below), otherwise, the new evince upstream release has been released a while ago with no post-release fixes: https://gitlab.gnome.org/GNOME/evince/commits/gnome-3-28 + + [Other Info] + Please add --enable-ps to the build options since this version disables viewing Postscript files as a workaround for security issues in Ghostscript. We should fix Ghostscript instead. See https://gitlab.gnome.org/GNOME/evince/issues/967 -- 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/1790609 Title: Update evince to 3.28.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1790609/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797355] Re: Once logged in, GDM Shell process CPU usage spiking at 100%
Assigning it to gdm, even if the loop is in mutter, as we are going to workaround it there. ** Package changed: mutter (Ubuntu) => gdm (Ubuntu) ** Package changed: gdm (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1797355 Title: Once logged in, GDM Shell process CPU usage spiking at 100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1797355/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797355] Re: Once logged in, GDM Shell process CPU usage spiking at 100%
didrocks | yes ;) I wonder what would happen if, while this is worked on, we remove the udev rule to not regress some of our nvidia users for 18.10 release next week (as | a workaround) halfline | didrocks: yea the udev rule makes less sense for you indeed halfline | since you default to Xorg for user sessions didrocks | right, so if we keep gdm / wayland and user sessions -> Xorg, that could still be an option didrocks | (until a proper fix is found) halfline | makes sense to me -- 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/1797355 Title: Once logged in, GDM Shell process CPU usage spiking at 100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1797355/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797355] [NEW] Once logged in, GDM Shell process CPU usage spiking at 100%
Public bug reported: This happens on some nvidia card, with the nvidia blob driver (fallbacked to Xorg for gdm). 1. Boot your laptop 2. Log into gdm -> once your user session is loaded, gdm GNOME Shell process goes crazy, up to 100%, continously. GNOME Shell (for user gdm) restarts in loops due to not be able to paint (context lost). More info on the upstream bug: https://gitlab.gnome.org/GNOME/gdm/issues/429#note_344826. #gnome-shell IRC logs: jadahl | so its the context-lost handling going crazy then didrocks | looks like so… didrocks | jadahl: FYI, I have a gdb shell opened right now, tell me if you have time or if I can help for anything jadahl | didrocks: I suppose what we need is a wayt to tell if its a context lost because of gdm switch away, or if its a context lost that should be handled jadahl | can't say I know at hand how to make that distinction didrocks | makes sense (surprised though that it doesn't seem to hit everyone fallbacking to Xorg for gdm). Is it something that should be discussed with halfline? halfline1 | check if its foreground vt i guess... jadahl | didrocks: only nvidia has the context lost thing didrocks | jadahl: Laney has a nvidia card as well, he checked that he's fallback to Xorg as well but doesn't have that issue apparently, which is puzzling… halfline1 | i wouldnt be surprised if theres a driver bug involved didrocks | yeah, I think that I'm on the "unlucky card triggering this nvidia driver bug" case :p ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.30.1-1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 11 12:19:41 2018 InstallationDate: Installed on 2018-05-24 (139 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic rls-cc-incoming ** Tags added: rls-cc-incoming -- 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/1797355 Title: Once logged in, GDM Shell process CPU usage spiking at 100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1797355/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795410] Re: cannot bring up window menu via keybinding (alt-space or otherwise)
** Package changed: ubuntu-meta (Ubuntu) => 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/1795410 Title: cannot bring up window menu via keybinding (alt-space or otherwise) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794024] [NEW] Transition from communitheme snap session to ubuntu
Public bug reported: In Bionic, we ship a communitheme snap, which shows up an additional gdm entry named "ubuntu communitheme". We want those users on Bionic -> Cosmic upgrade (and later, bionic LTS -> f LTS) to fallback to the ubuntu session to not pick the theme in the snap. However, we still want a way for people to install the communitheme session for testing latest edge. Plan is: - remove from ubuntu-session package the communitheme .desktop session files. This way, people will be fallbacked to the ubuntu session. - readd another session package, like communitheme-session, containing those .desktop files. That will be the package that people can use to use the snap theme version. ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1794024 Title: Transition from communitheme snap session to ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1794024/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1793476] Re: Missing French translations for some strings
** Package changed: gnome-shell (Ubuntu) => pkgbinarymangler (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/1793476 Title: Missing French translations for some strings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pkgbinarymangler/+bug/1793476/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
Are you sure this is due to the above patch, can you try without it? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1691678/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790609] Re: Update evince to 3.28.3
** Changed in: evince (Ubuntu Bionic) Assignee: (unassigned) => Didier Roche (didrocks) -- 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/1790609 Title: Update evince to 3.28.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1790609/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783571] Re: Set Yaru as default
** Changed in: ubuntu-meta (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1783571 Title: Set Yaru as default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790996] Re: JS ERROR: ImportError: No JS module 'desktop' found in search path#012
Thanks a lot! I was just looking at the same issue and got directed to the bug. The diff is good, I've just sponsored it to cosmic. Thanks again ;) ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Committed -- 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/1790996 Title: JS ERROR: ImportError: No JS module 'desktop' found in search path#012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1790996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790532] Re: ubuntu-settings-migrate-to-defaults.18.10.0.py crashed with KeyError in __getitem__(): 'DESKTOP_SESSION'
** Changed in: gnome-session (Ubuntu) Assignee: Marco Trevisan (Treviño) (3v1n0) => Didier Roche (didrocks) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1790532 Title: ubuntu-settings-migrate-to-defaults.18.10.0.py crashed with KeyError in __getitem__(): 'DESKTOP_SESSION' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1790532/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783571] Re: Set Yaru as default
As a reminder, ubuntu-settings is failing due to a meson issue: https://github.com/mesonbuild/meson/issues/3914. The stack has been tested locally and everything works well, including transition with removal of older alternatives and fallback to plan Shell for GDM without the theme installed. ** Bug watch added: github.com/mesonbuild/meson/issues #3914 https://github.com/mesonbuild/meson/issues/3914 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1783571 Title: Set Yaru as default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783571] Re: Set Yaru as default
yaru MIR is https://bugs.launchpad.net/ubuntu/+source/yaru- theme/+bug/1783600 ** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1783571 Title: Set Yaru as default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783571] Re: Set Yaru as default
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1783571 Title: Set Yaru as default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1711617] Re: file conflict with gnome-shell-extension-dashtodock
There is no schedule schema changes as of now, so current replaces: is still good and we'll see later on if we fork the schema or not. Sounds good for the current states at least. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Triaged => Fix Released -- 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/1711617 Title: file conflict with gnome-shell-extension-dashtodock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1711617/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 111939] Re: Alt-Tab - Not possible to alt-tab during a drag-and-drop operation
You will have to reimplement something similar to what Unity switcher did I think. The implementation is different, so it needs to be a proper implementation. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/111939 Title: Alt-Tab - Not possible to alt-tab during a drag-and-drop operation To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/111939/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774597] Re: G-C-C privacy option don't allow sending manual report
** Description changed:
[ Impact ]
- * The current label "Manual" is in fact shutting down whoopsie completely
and not providing any graĥical way to set manual reports (which is our default
on 18.04)
- * We want to SRU gnome-initial-setup for 18.04.1 so that sending reports is
linked to sending error report: opt-in -> automated report is set; opt-out ->
no report is set. We need a way to represent those 3 states of error reporting:
-- never
-- manual
-- auto
-
+ * The current label "Manual" is in fact shutting down whoopsie completely
and not providing any graĥical way to set manual reports (which is our default
on 18.04)
+ * We want to SRU apport with a "remember this" option which will trigger
"never" or "auto" mode.
+
[ Test Case ]
- * Install new gnome-control-center version, go to the privacy panel
- * Click on the error reporting line
- * In the model window, play with the switch and toggle, and check in d-feet
the whoopsie state. Basically you can't adapt error reporting mode
(manual/auto) if you decided to not report error mode.
- * Check as well that the main UI toggles between "never/manual/auto"
+ * Install new gnome-control-center version, go to the privacy panel
+ * Click on the error reporting line
+ * In the model window, play with the switch and toggle, and check in d-feet
the whoopsie state. Basically you can't adapt error reporting mode
(manual/auto) if you decided to not report error mode.
+ * Check as well that the main UI toggles between "never/manual/auto"
[ Regression potential ]
- * This code would affect the privacy g-c-c panel.
- * Note that we have 3 new strings to translate ("never" is already
translated in G-C-C). Those are:
- - "Send error reports to Canonical"
- - "Send reports automatically"
- - "Show a dialog for each error before reporting"
+ * This code would affect the privacy g-c-c panel.
+ * Note that we have 3 new strings to translate ("never" is already
translated in G-C-C). Those are:
+ - "Send error reports to Canonical"
+ - "Send reports automatically"
+ - "Show a dialog for each error before reporting"
--
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/1774597
Title:
G-C-C privacy option don't allow sending manual report
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774597] Re: G-C-C privacy option don't allow sending manual report
@Brian: I just had a deeper look after an initial tests, and brought jibel along. Indeed, there are quite some flaws on those options which never worked (but was shipped since 12.04). On top of that, I found another regression that happened probably during the upstart -> systemd transition. Those aren't linked to the current SRU, which are doing the expected thing (and those options were already available before). But we need to fix those. Let me know what you think: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1778694 https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1778697 -- 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/1774597 Title: G-C-C privacy option don't allow sending manual report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774597] Re: G-C-C privacy option don't allow sending manual report
If there is a need for a 3rd party package for it, it means that whoopsie-preferences is broken for quite some years: the automatic option was present in g-c-c for years in ubuntu, and just use whoopsie- preferences API to turn this automatic send mode. Note that the API doesn't report any error in the default install configuration. As you are familiar with the internal of whoopsie and apport, do you mind having a look? As this only introduces a "never" report mode, and the "auto" one was here since whoopsie integration? -- 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/1774597 Title: G-C-C privacy option don't allow sending manual report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774597] Re: G-C-C privacy option don't allow sending manual report
It's an option which was already present (only the "never" one wasn't): whoopsie upload crash reports automatically. See the g-c-c panel from that version to see the option dialog box. -- 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/1774597 Title: G-C-C privacy option don't allow sending manual report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774597] Re: G-C-C privacy option don't allow sending manual report
Translator team emailed. -- 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/1774597 Title: G-C-C privacy option don't allow sending manual report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt (if starting with Shift key). Usually works on the second attempt
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Didier Roche (didrocks) ** Changed in: gnome-shell (Ubuntu Bionic) Assignee: (unassigned) => Didier Roche (didrocks) -- 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/1765261 Title: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt (if starting with Shift key). Usually works on the second attempt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765261/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774597] Re: G-C-C privacy option don't allow sending manual report
** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Didier Roche (didrocks) ** Changed in: gnome-control-center (Ubuntu Bionic) Assignee: (unassigned) => Didier Roche (didrocks) -- 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/1774597 Title: G-C-C privacy option don't allow sending manual report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774597] [NEW] G-C-C privacy option don't allow sending manual report
Public bug reported:
[ Impact ]
* The current label "Manual" is in fact shutting down whoopsie completely and
not providing any graĥical way to set manual reports (which is our default on
18.04)
* We want to SRU gnome-initial-setup for 18.04.1 so that sending reports is
linked to sending error report: opt-in -> automated report is set; opt-out ->
no report is set. We need a way to represent those 3 states of error reporting:
- never
- manual
- auto
[ Test Case ]
* Install new gnome-control-center version, go to the privacy panel
* Click on the error reporting line
* In the model window, play with the switch and toggle, and check in d-feet
the whoopsie state. Basically you can't adapt error reporting mode
(manual/auto) if you decided to not report error mode.
* Check as well that the main UI toggles between "never/manual/auto"
[ Regression potential ]
* This code would affect the privacy g-c-c panel.
* Note that we have 3 new strings to translate ("never" is already translated
in G-C-C). Those are:
- "Send error reports to Canonical"
- "Send reports automatically"
- "Show a dialog for each error before reporting"
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
** Affects: gnome-control-center (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: gnome-control-center (Ubuntu Bionic)
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/1774597
Title:
G-C-C privacy option don't allow sending manual report
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720310] Re: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed
** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1720310 Title: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1720310/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768779] Re: Snap channel selection list not scrollable
The list of real entries are (at that time, it's dynamic): TrackArchChannel VersionRevision Expires at latest all stable 0.1124 candidate^ ^ beta ^ ^ edge 0.1170 edge/gnome-shell-communitheme-pr125 0.1112 2018-05-26T13:54:16.742243 edge/gnome-shell-communitheme-pr128 0.1144 2018-05-29T22:59:41.400161 edge/gnome-shell-communitheme-pr130 0.1108 2018-05-26T09:21:19.157622 edge/gnome-shell-communitheme-pr131 0.1125 2018-05-27T12:05:18.882819 edge/gnome-shell-communitheme-pr136 0.1132 2018-05-27T21:09:57.216625 edge/gtk-communitheme-pr371 0.1123 2018-05-27T10:43:32.369778 edge/gtk-communitheme-pr374 0.1128 2018-05-27T16:17:18.898120 edge/gnome-shell-communitheme-pr143 0.1136 2018-05-28T08:51:24.786638 edge/gtk-communitheme-pr384 0.1159 2018-05-31T08:48:58.912739 edge/gtk-communitheme-pr385 0.1164 2018-05-31T22:17:13.052878 edge/gtk-communitheme-pr387 0.1146 2018-05-30T09:35:43.783124 edge/gnome-shell-communitheme-pr149 0.1148 2018-05-30T14:05:02.010329 edge/gnome-shell-communitheme-pr150 0.1150 2018-05-30T16:23:04.423498 edge/gnome-shell-communitheme-pr151 0.1155 2018-05-30T22:11:56.694347 edge/communitheme-snap-helpers-pr9 0.1156 2018-05-30T22:49:43.618408 edge/gnome-shell-communitheme-pr158 0.1160 2018-05-31T16:11:35.365221 edge/gtk-communitheme-pr392 0.1167 2018-06-01T14:24:25.782118 edge/gtk-communitheme-pr393 0.1168 2018-06-01T14:46:23.289516 edge/gtk-communitheme-pr394 0.1169 2018-06-01T14:46:53.708757 amd64 stable 0.197 candidate^ ^ beta ^ ^ edge 0.1104 edge/ubuntu-communitheme-snap-helpers-1 0.14 2018-05-04T10:05:45.478718 edge/communitheme-snap-helpers-pr1 0.129 2018-05-05T09:31:00.421780 edge/blablab-branch-pr1 0.110 2018-05-04T14:44:43.359591 edge/communitheme-snap-helpers-pr2 0.135 2018-05-09T15:05:08.609020 edge/communitheme-sounds-pr5 0.138 2018-05-10T08:46:42.989211 edge/cursor-communitheme-pr1 0.139 2018-05-10T08:50:04.794461 edge/gtk-communitheme-pr321 0.140 2018-05-10T08:52:08.630168 edge/test-gtk2 0.145 2018-05-11T08:52:14.866723 edge/communitheme-snap-helpers-pr3 0.146 2018-05-11T09:02:37.264041 edge/communitheme-snap-helpers-pr4 0.164 2018-05-13T13:25:53.288391 edge/communitheme-snap-helpers-pr6 0.166 2018-05-16T09:40:08.990495 edge/communitheme-snap-helpers-pr7 0.168 2018-05-20T07:42:54.143890 edge/gnome-shell-communitheme-pr122 0.172 2018-05-21T20:17:17.099928 edge/gnome-shell-communitheme-pr123 0.181 2018-05-23T19:43:13.058809 edge/gnome-shell-communitheme-pr125 0.1105 2018-05-26T13:54:16.742243 edge/gnome-shell-communitheme-pr126 0.180 2018-05-23T18:30:45.643229 edge/gtk-communitheme-pr360 0.186 2018-05-24T18:07:42.761720 edge/gnome-shell-communitheme-pr127 0.188 2018-05-24T21:20:07.959559 edge/gtk-communitheme-pr361 0.189 2018-05-24T21:21:29.565369 edge/gnome-shell-communitheme-pr128 0.1103 2018-05-29T22:59:41.400161
[Bug 1720310] Re: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed
** Changed in: gnome-session (Ubuntu Bionic) Status: New => Triaged ** Changed in: gnome-session (Ubuntu) Status: Confirmed => Triaged ** Changed in: gnome-session (Ubuntu Bionic) Assignee: (unassigned) => Didier Roche (didrocks) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1720310 Title: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1720310/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720310] Re: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed
** Description changed: + [Impact] + + * People having this particular setup: +- removed ubuntu-desktop metapackage from their system +- upgrading from 16.04 to 18.04 (or previously to 17.10) by manually editing /etc/apt/sources.lists without using do-release-upgrade (which reinstalls ubuntu-desktop). + They end up with: + - no ubuntu-dock installed + - and consequentely, the settings migration script would trigger an apport dialog (crashing) due to lack of gsettings schema. + * Even if this is an unsupported case (people shouldn't cowboy sources.list and use our upgrader tools), we can easily prevent this crash, ignoring settings migration in such a case. + + [Test Case] + + 1. Install 16.04 + 2. Remove ubuntu-desktop metapackage + 3. Change your sources.list from "xenial" to "bionic" + 4. apt update && apt full-upgrade + 5. Reboot and log into a new session once upgrade is done. + -> you won't get the ubuntu-dock, but the session migration script shouldn't crash. + + [Regression Potential] + + * The script was crashing (even if there is no settings to migrate, so + it was a no-op). We prevents gsettings to segfault by guarding for + schema existence in the standard way. + + -- + Upgrade... ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: ubuntu-session 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 08:15:13 2017 ExecutablePath: /usr/share/session-migration/scripts/unity-gnome-shell-migration.18.08.py InstallationDate: Installed on 2017-09-25 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterpreterPath: /usr/bin/python3.6 ProcCmdline: /usr/bin/python3 /usr/share/session-migration/scripts/unity-gnome-shell-migration.18.08.py ProcEnviron: - LANGUAGE=ru - PATH=(custom, user) - XDG_RUNTIME_DIR= - LANG=ru_RU.UTF-8 - SHELL=/bin/bash + LANGUAGE=ru + PATH=(custom, user) + XDG_RUNTIME_DIR= + LANG=ru_RU.UTF-8 + SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 3.6.2-1ubuntu4 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 Signal: 5 SourcePackage: gnome-session StacktraceTop: - ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 - ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 + ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Also affects: gnome-session (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1720310 Title: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1720310/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720310] Re: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed
** Changed in: gnome-session (Ubuntu) Assignee: (unassigned) => Didier Roche (didrocks) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1720310 Title: unity-gnome-shell-migration.18.08.py crashed with signal 5 in g_object_new_valist() due to gnome-shell-extension-ubuntu-dock not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1720310/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764355] Re: Visual Studio Code, Slack and other electrons apps crash due to XDG_CONFIG_DIRS keeps getting expanded every login
** Also affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1764355 Title: Visual Studio Code, Slack and other electrons apps crash due to XDG_CONFIG_DIRS keeps getting expanded every login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1764355/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764355] Re: Visual Studio Code, Slack and other electrons apps crash due to XDG_CONFIG_DIRS keeps getting expanded every login
Note that XDG_DATA_DIRS is expanded as well, we should protect against it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1764355 Title: Visual Studio Code, Slack and other electrons apps crash due to XDG_CONFIG_DIRS keeps getting expanded every login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1764355/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764355] Re: Visual Studio Code, Slack and other electrons apps crash due to XDG_CONFIG_DIRS keeps getting expanded every login
** Summary changed: - XDG_CONFIG_DIRS keeps getting expanded every login + Visual Studio Code, Slack and other electrons apps crash due to XDG_CONFIG_DIRS keeps getting expanded every login -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1764355 Title: Visual Studio Code, Slack and other electrons apps crash due to XDG_CONFIG_DIRS keeps getting expanded every login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1764355/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764355] Re: XDG_CONFIG_DIRS keeps getting expanded every login
The I think then an old session is hanging around. How long are you waiting before logging out and back in again? Please, try the following: - login, and wait for *at least* a minute so that everything that is lazy loaded shutdown - logout, and login back in - check XDG_CONFIG_DIRS /!\ Ensure that no tty (no other session with the same user name) is running while doing it. Regardless, we should indeed protect the profile.d script to not append XDG_CONFIG_DIRS unconditionnally. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1764355 Title: XDG_CONFIG_DIRS keeps getting expanded every login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1764355/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764974] Re: Change default interface font size in Community theme
** Package changed: gnome-session (Ubuntu) => ubuntu-settings (Ubuntu) ** Description changed: Change default interface font size in Community theme from 11 to 10. - It won’t impact the default session only the communitheme. + It won’t impact the default session only the communitheme, which isn't + available until you install the snap. Change the key org.gnome.desktop.interface.font-name to ubuntu 10 - See: https://community.ubuntu.com/t/snapping-communitheme/4890 https://github.com/ubuntu/gtk-communitheme/issues/30 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1764974 Title: Change default interface font size in Community theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1764974/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1718850] Re: Mode extensions appear off by default
FYI, I started the discussion on the GNOME Shell mailing list in october: https://mail.gnome.org/archives/gnome-shell-list/2017-October/msg00034.html There is a pending request with patches posted in November on upstream bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=789852 and patches in Tweaks are waiting on the GNOME Shell part to be merged. I migrated everything over gitlab once GNOME Shell project was moved to it: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/1 ** Bug watch added: GNOME Bug Tracker #789852 https://bugzilla.gnome.org/show_bug.cgi?id=789852 -- 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/1718850 Title: Mode extensions appear off by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1718850/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1763736] Re: communitheme not present in gnome software
Adding rls-bb-incoming to inspect the difference between 16.04 and bionic. Happy to modify the snap as needed. ** Tags added: rls-bb-incoming ** Summary changed: - communitheme not present in gnome software + communitheme not present in gnome software on bionic, but it is on 16.04 ** Summary changed: - communitheme not present in gnome software on bionic, but it is on 16.04 + communitheme snap not present in gnome software on bionic, but it is on 16.04 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1763736 Title: communitheme snap not present in gnome software on bionic, but it is on 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1763736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705689] Re: When adding an app to favourites, two icons are created.
I think this isn't specific to ubuntu dock, but rather a dash to dock bug. Does anyone here mind reporting that upstream? https://github.com/micheleg/dash-to-dock/issues (you can then link the bug here) Thanks! -- 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/1705689 Title: When adding an app to favourites, two icons are created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1705689/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1758314] Re: Open new windows in the middle of the screen
** Package changed: mutter (Ubuntu) => ubuntu-settings (Ubuntu) ** Changed in: ubuntu-settings (Ubuntu) Assignee: (unassigned) => Didier Roche (didrocks) -- 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/1758314 Title: Open new windows in the middle of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1758314/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760049] [NEW] [UIFe] Optional (hidden by default) communitheme snap session
Public bug reported: This session isn't displayed and available in GDM by default. If the communitheme snap is installed, 2 new session options appears, selecting the corresponding theme (for GNOME Shell, sound, GTK2&3, cursor). All session/theme assets will be in the snap. We only expose here default gsettings settings, session files and extension override. There are 2 new strings for GDM: * Ubuntu with communitheme snap * Ubuntu with communitheme snap on Wayland This is to give the community a chance to get an easy glimpse of our next default theme, backed by the community. This doesn't impact any default UI has nothing will appear before you install the snap. ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1760049 Title: [UIFe] Optional (hidden by default) communitheme snap session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1760049/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760039] Re: Theme lookup should respect XDG_DATA_DIRS
** Description changed: - mods, extensions and others lookup into each dirs specificied in - XDG_DATA_DIRS. However, this isn't the case for a theme (which can be - referened by a mode in a different XDG_DATA_DIR!) + mods, extensions and others GNOME Shell assets lookup into each dir, + relative to XDG_DATA_DIRS. However, this isn't the case for themes + (which can be referened by a mod in a different XDG_DATA_DIR), harcoding + the global.datadir. - Have the theme finding pattern follow the same logic than others. + The fix is to have the theme finding pattern following the same logic + than others. -- 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/1760039 Title: Theme lookup should respect XDG_DATA_DIRS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760039/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
