[Bug 1876516] Re: Mouse cursor lagging (or freezing) when moving over system tray when wayland session
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-dash- to-panel (Ubuntu) ** Changed in: gnome-shell-extension-dash-to-panel (Ubuntu) Status: Incomplete => 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/1876516 Title: Mouse cursor lagging (or freezing) when moving over system tray when wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dash-to-panel/+bug/1876516/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877850] Re: strange behaviour of shortcuts in ubuntu 20.04
** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877850 Title: strange behaviour of shortcuts in ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877850/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877850] [NEW] strange behaviour of shortcuts in ubuntu 20.04
You have been subscribed to a public bug: There are shortcuts like 'Super + P' to change the display mode or 'Super + l' to go to login screen. However, after i upgraded ubuntu 18.04 to 20.04, if i press P or l or any other character which there is a 'super + key' for it, it's does the same thing. It's like the super key is always on! My keyboard works fine in Unity so it's not a hardware problem. GNOME Shell 3.36.1 Ubuntu 20.04 LTS ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: udev (Ubuntu) Importance: Undecided Status: New ** Tags: 20.04 bot-comment -- strange behaviour of shortcuts in ubuntu 20.04 https://bugs.launchpad.net/bugs/1877850 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857122] Re: New Windows are opened below other windows and require extra clicks to acees
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1857122 Title: New Windows are opened below other windows and require extra clicks to acees To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857122/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865896] Re: totem segfaults on ubuntu-mate 18.04
[Expired for totem (Ubuntu) because there has been no activity for 60 days.] ** Changed in: totem (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1865896 Title: totem segfaults on ubuntu-mate 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1865896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876415] Re: [nvidia+modeset] Fonts in the GNOME shell not shown.
If you would like to make this bug private there is an option to do that at the top-right of this page. -- 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/1876415 Title: [nvidia+modeset] Fonts in the GNOME shell not shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877279] Re: my wallpaper is changed after computer sleep
*** This bug is a duplicate of bug 1855757 *** https://bugs.launchpad.net/bugs/1855757 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1855757, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1855757 [nvidia] Background image corrupted after standby -- 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/1877279 Title: my wallpaper is changed after computer sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857335] Re: System volume slider only works between ~90% and 100%.
** Package changed: gnome-control-center (Ubuntu) => pulseaudio (Ubuntu) ** Summary changed: - System volume slider only works between ~90% and 100%. + System volume slider only works between ~90% and 100% with a USB 2.0 speaker -- 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/1857335 Title: System volume slider only works between ~90% and 100% with a USB 2.0 speaker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1857335/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1855757] Re: [nvidia] Background image corrupted after standby
** Tags added: focal -- 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/1855757 Title: [nvidia] Background image corrupted after standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877547] Re: Dead cursor on 125% scaling on x11
*** This bug is a duplicate of bug 1873052 *** https://bugs.launchpad.net/bugs/1873052 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1873052, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1873052 GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps another not scaled cursor mid screen -- 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/1877547 Title: Dead cursor on 125% scaling on x11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877547/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877434] Re: Slow Gnome 3.36 overall experience
Was that used by some extension? Can you please detail what "the problem" was, or where you got that info? -- 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/1877434 Title: Slow Gnome 3.36 overall experience To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877434/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877547] Re: Dead cursor on 125% scaling on x11
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877547 Title: Dead cursor on 125% scaling on x11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877547/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
Installed flathub as per instructions. Worked okay for about an hour, then reverted back to same problem. Used Unbuntu distro in instructions. I am operating Zorin Lite. Should I use a different distro in setup to solve this problem? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872681] Re: Overview shortcut does not work on non-latin keyboard layout
*** This bug is a duplicate of bug 1871913 *** https://bugs.launchpad.net/bugs/1871913 Hi, I found that not only super key not working but also ctrl. You can enable showing pointer on ctrl click and try. These keyes work only for first and 4-th layout(second, third, fifth and other not work properly). It does not matter if layout is latin or not. -- 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/1872681 Title: Overview shortcut does not work on non-latin keyboard layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872681/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877875] Re: Pressing Alt+F1 with mouse cursor over the Applcations leads to focus move to Applications, the menus are unusable as result
Caused by some mess with customizations from other flavors. The normally installed Ubuntu MATE is not affected. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Invalid ** Changed in: mate-panel (Ubuntu) Status: New => Incomplete ** Changed in: mate-panel (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1877875 Title: Pressing Alt+F1 with mouse cursor over the Applcations leads to focus move to Applications, the menus are unusable as result To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1877875/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872681] Re: Overview shortcut does not work on non-latin keyboard layout
*** This bug is a duplicate of bug 1871913 *** https://bugs.launchpad.net/bugs/1871913 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872681 Title: Overview shortcut does not work on non-latin keyboard layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872681/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
The issue appears to be in /usr/lib/x86_64-linux- gnu/libgnutls.so.30.14.10 with the function _gnutls_recv_new_session_ticket around line 758 of session_ticket.c. The code reads two bytes and assigns the result to the variable ticket_len. Unfortunately this value is zero. A few lines later when the variable is used in a memory allocation call, the call fails and the code returns GNUTLS_E_MEMORY_ERROR. I'm not sure what is causing the value to be zero. Attached is a copy of the gdb output, maybe someone who is familiar with GnuTLS can help. ** Attachment added: "gdb.txt" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+attachment/5369555/+files/gdb.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1855757] Re: [nvidia] Background image corrupted after standby
Bug also affects Ubuntu 20.04 -- 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/1855757 Title: [nvidia] Background image corrupted after standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877876] Re: white line at gedit with the dark windows skin
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1857191, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1877876 Title: white line at gedit with the dark windows skin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1877876/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877876] [NEW] white line at gedit with the dark windows skin
Public bug reported: With the dark window skin enabled type marker in gedit turns into a white line, so you can't see what your typing. Description:Ubuntu 20.04 LTS Release:20.04 gedit: Geïnstalleerd: 3.36.1-1 Kandidaat: 3.36.1-1 Versietabel: *** 3.36.1-1 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Schermafdruk van 2020-05-10 17-08-43.png" https://bugs.launchpad.net/bugs/1877876/+attachment/5369529/+files/Schermafdruk%20van%202020-05-10%2017-08-43.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1877876 Title: white line at gedit with the dark windows skin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1877876/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877875] [NEW] Pressing Alt+F1 with mouse cursor over the Applcations leads to focus move to Applications, the menus are unusable as result
Public bug reported: Steps to reproduce: 1. Have Ubuntu MATE 20.04 LTS installed 2. Login to session, choose Traditional desktop layout in MATE Tweak 3. Move move cursor over Applications menu 4. Press + to open Applications menu 5. Press or Expected results: * focus moves with or to corresponding one of the menu items - Applications, Places, System Actual results: * focus is stuck on Applications menu, about which mouse cursor is located (see screencast) ProblemType: Bug DistroRelease: Ubuntu Kylin 20.04 Package: mate-panel 1.24.0-2 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.4.0-29.33-lowlatency 5.4.30 Uname: Linux 5.4.0-29-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun May 10 18:57:48 2020 InstallationDate: Installed on 2020-04-22 (17 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200422) SourcePackage: mate-panel UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Affects: mate-panel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "menus.gif" https://bugs.launchpad.net/bugs/1877875/+attachment/5369525/+files/menus.gif ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1877875 Title: Pressing Alt+F1 with mouse cursor over the Applcations leads to focus move to Applications, the menus are unusable as result To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1877875/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685754]
This issue was fixed in systemd by https://github.com/systemd/systemd/pull/15318. Debian cherry-picked that change into 245.4-3, so Debian bullseye and buster-backports have the fix, as does Ubuntu 20.04 (focal). -- 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/1685754 Title: 'systemd --user' unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685754] Re: 'systemd --user' unduly forces umask=0022
** Also affects: systemd via https://github.com/systemd/systemd/issues/6077 Importance: Unknown Status: Unknown -- 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/1685754 Title: 'systemd --user' unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
** Tags removed: focal ** Summary changed: - gnome-terminal unduly forces umask=0022 + 'systemd --user' unduly forces umask=0022 ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Invalid ** Changed in: dbus (Ubuntu) Status: Confirmed => Invalid ** Changed in: gnome-session Status: New => Invalid ** Changed in: nautilus Status: Confirmed => Invalid -- 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/1685754 Title: 'systemd --user' unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 256373] Re: rhythmbox tag editing issue (back button in file property menu becomes inactive)
Further to my comment #13 I can now confirm a slight variation of this bug with rhythmbox 3.4.2 in Ubuntu 18.04. When the song is moved to the end of the list, the forward button should be disabled but it isn't. It seems there are other minor issues in respect of the currently highlighted file once another file is moved after the renaming. ** Tags added: bionic ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/256373 Title: rhythmbox tag editing issue (back button in file property menu becomes inactive) To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/256373/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877434] Re: Slow Gnome 3.36 overall experience
As it appears the problem persisted. The problem was in the upower service and i managed to fix it by installing the file containing the missing libusbmuxd.so.4 file from http://archive.ubuntu.com/ubuntu/pool/main/libu/libusbmuxd/libusbmuxd4_1.0.10-2_amd64.deb Now everything works as it should -- 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/1877434 Title: Slow Gnome 3.36 overall experience To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877434/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877854] Re: Ubuntu 20.04. Appearance > Dock setting fails with 2 monitors. Shows on both.
*** This bug is a duplicate of bug 1866088 *** https://bugs.launchpad.net/bugs/1866088 Thanks for reporting. However, these problems have already been reported are and in the process of being fixed. I'm marking this as a duplicate of bug 1866088, a fix will be released shortly. Also, bug 1877108 will fix the remaining issue. ** This bug has been marked a duplicate of bug 1866088 Problems with the Dock setting of "Show on" in the Appearance tab -- 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/1877854 Title: Ubuntu 20.04. Appearance > Dock setting fails with 2 monitors. Shows on both. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1877854/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877854] [NEW] Ubuntu 20.04. Appearance > Dock setting fails with 2 monitors. Shows on both.
Public bug reported: Environment --- Ubuntu 20.04 LTS package: gnome-shell-extension-ubuntu-dock/focal,focal,now 67ubuntu20.04.5 Number of monitors: 2 Background -- I upgraded from 18.04 to 20.04 after the official launch date. The dock also didn't work properly on 18.04 with two monitors. You had to select the wrong monitor to have the dock on the side you really wanted. What I expect to happen --- I expect to have the dock on the monitor I choose. What really happens --- Now focusing on 20.04 which is my current version. When I first installed it, the Dock was showing on one side but after changing the initial setting just for the sake of testing, the dock shows always on both monitors no matter what setting I choose. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: focal upgrade-software-version ** Tags added: gnome ** Description changed: Environment --- Ubuntu 20.04 LTS package: gnome-shell-extension-ubuntu-dock/focal,focal,now 67ubuntu20.04.5 Number of monitors: 2 - Background -- I upgraded from 18.04 to 20.04 after the official launch date. The dock also didn't work properly on 18.04 with two monitors. You had to select the wrong monitor to have the dock on the side you really wanted. What I expect to happen --- I expect to have the dock on the monitor I choose. What really happens --- Now focusing on 20.04 which is my current version. When I first installed it, the Dock was showing on one side but after changing the initial setting just for the sake of testing, the dock shows on both monitors no matter what setting I choose. ** Description changed: Environment --- Ubuntu 20.04 LTS package: gnome-shell-extension-ubuntu-dock/focal,focal,now 67ubuntu20.04.5 Number of monitors: 2 Background -- - - I upgraded from 18.04 to 20.04 after the official launch date. The dock - also didn't work properly on 18.04 with two monitors. You had to select - the wrong monitor to have the dock on the side you really wanted. + I upgraded from 18.04 to 20.04 after the official launch date. The dock also didn't work properly on 18.04 with two monitors. You had to select the wrong monitor to have the dock on the side you really wanted. What I expect to happen --- I expect to have the dock on the monitor I choose. What really happens --- Now focusing on 20.04 which is my current version. When I first installed it, the Dock was showing on one side but after changing the initial setting just for the sake of testing, the dock shows on both monitors no matter what setting I choose. ** Description changed: Environment --- Ubuntu 20.04 LTS package: gnome-shell-extension-ubuntu-dock/focal,focal,now 67ubuntu20.04.5 Number of monitors: 2 Background -- I upgraded from 18.04 to 20.04 after the official launch date. The dock also didn't work properly on 18.04 with two monitors. You had to select the wrong monitor to have the dock on the side you really wanted. - What I expect to happen --- I expect to have the dock on the monitor I choose. What really happens --- - - Now focusing on 20.04 which is my current version. When I first - installed it, the Dock was showing on one side but after changing the - initial setting just for the sake of testing, the dock shows on both - monitors no matter what setting I choose. + Now focusing on 20.04 which is my current version. When I first installed it, the Dock was showing on one side but after changing the initial setting just for the sake of testing, the dock shows on both monitors no matter what setting I choose. ** Tags added: foc upgrade-software-version ** Tags removed: foc gnome ** Tags added: focal ** Description changed: Environment --- Ubuntu 20.04 LTS package: gnome-shell-extension-ubuntu-dock/focal,focal,now 67ubuntu20.04.5 Number of monitors: 2 Background -- I upgraded from 18.04 to 20.04 after the official launch date. The dock also didn't work properly on 18.04 with two monitors. You had to select the wrong monitor to have the dock on the side you really wanted. What I expect to happen --- I expect to have the dock on the monitor I choose. - What really happens --- - Now focusing on 20.04 which is my current version. When I first installed it, the Dock was showing on one side but after changing the initial setting just for the sake of testing, the dock shows on both monitors no matter what setting I choose. + Now focusing on 20.04 which is my current version. When I first installed it, the Dock was showing on one side but after changing the
[Bug 1877852] Re: Evolution not showing unread count in dock, missing build-dep
** Attachment added: "evo-counter.png" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1877852/+attachment/5369430/+files/evo-counter.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1877852 Title: Evolution not showing unread count in dock, missing build-dep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1877852/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877852] [NEW] Evolution not showing unread count in dock, missing build-dep
Public bug reported: Evolution has the ability to show the unread messages count in the Dock app icon, this works for the Ubuntu Dock GNOME extension as well as for Dash to Dock and indeed the old unity7 dock ... simply re-compiling the current focal evolution package with an added libunity-dev build dependency like below makes this feature work fine. --- evolution-3.36.1/debian/control.in 2020-04-15 14:27:07.0 + +++ evolution-3.36.1-unity/debian/control.in2020-05-10 12:26:31.687948740 + @@ -55,6 +55,7 @@ libcryptui-dev, libgnome-autoar-0-dev (>= 0.1.1), libgnome-autoar-gtk-0-dev (>= 0.1.1), + libunity-dev (>=7.1.4), Standards-Version: 4.5.0 X-Ubuntu-Use-Langpack: yes Vcs-Git: https://salsa.debian.org/gnome-team/evolution.git ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Description changed: Evolution has the ability to show the unread messages count in the Dock app icon, this works for the Ubuntu Dock GNOME extension as well as for Dash to Dock and indeed the old unity7 dock ... simply re-compiling the current focal evolution package with an added libunity-dev build dependency like below makes this feature work fine. --- evolution-3.36.1/debian/control.in2020-04-15 14:27:07.0 + +++ evolution-3.36.1-unity/debian/control.in 2020-05-10 12:26:31.687948740 + @@ -55,6 +55,7 @@ - libcryptui-dev, - libgnome-autoar-0-dev (>= 0.1.1), - libgnome-autoar-gtk-0-dev (>= 0.1.1), - + libunity-dev (>=7.1.4), - Standards-Version: 4.5.0 - X-Ubuntu-Use-Langpack: yes - Vcs-Git: https://salsa.debian.org/gnome-team/evolution.git + libcryptui-dev, + libgnome-autoar-0-dev (>= 0.1.1), + libgnome-autoar-gtk-0-dev (>= 0.1.1), + + libunity-dev (>=7.1.4), + Standards-Version: 4.5.0 + X-Ubuntu-Use-Langpack: yes + Vcs-Git: https://salsa.debian.org/gnome-team/evolution.git ** Description changed: Evolution has the ability to show the unread messages count in the Dock app icon, this works for the Ubuntu Dock GNOME extension as well as for Dash to Dock and indeed the old unity7 dock ... simply re-compiling the current focal evolution package with an added libunity-dev build dependency like below makes this feature work fine. --- evolution-3.36.1/debian/control.in2020-04-15 14:27:07.0 + +++ evolution-3.36.1-unity/debian/control.in 2020-05-10 12:26:31.687948740 + @@ -55,6 +55,7 @@ libcryptui-dev, libgnome-autoar-0-dev (>= 0.1.1), libgnome-autoar-gtk-0-dev (>= 0.1.1), - + libunity-dev (>=7.1.4), + + libunity-dev (>=7.1.4), Standards-Version: 4.5.0 X-Ubuntu-Use-Langpack: yes Vcs-Git: https://salsa.debian.org/gnome-team/evolution.git -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1877852 Title: Evolution not showing unread count in dock, missing build-dep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1877852/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869522] Re: Simple Scan doesn't work
Retasking to the simple-scan package in Ubuntu. ** Package changed: gnome-software (Ubuntu) => simple-scan (Ubuntu) -- 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/1869522 Title: Simple Scan doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1869522/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1874219] Re: PC suspends after 20 minutes at the login screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed -- 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/1874219 Title: PC suspends after 20 minutes at the login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1874219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877847] [NEW] causes freezeups with zsh related to .histfile.LOCK
Public bug reported: This problem only happens to me when I select the Ubuntu WM, not under Cinnamon. I see it in gnome-terminal. After I enter a command, like "ls" or "cd" into gnome-terminal and press Enter, the desktop icons blink out for a split-second, and while they do, the command does not finish. This makes it annoying for me to work in the command-line, since I'm used to most programs responding immediately. >From my experience, it looks like when a program is already running, like Vim, and I ask it to do a disk operation, this "blinking out" and "freezing" does not happen. I'm attaching a video of this happening. I've noticed this line in journalctl -b: Mai 10 13:24:55 agentydragon kernel: mce: CPU3: Package temperature/speed normal Mai 10 13:24:55 agentydragon kernel: mce: CPU1: Package temperature/speed normal Mai 10 13:24:55 agentydragon kernel: mce: CPU2: Package temperature/speed normal Mai 10 13:24:55 agentydragon kernel: mce: CPU0: Package temperature/speed normal Mai 10 13:24:56 agentydragon wpa_supplicant[1011]: wlp4s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-67 noise= txrate=13 Mai 10 13:25:07 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:10 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:12 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:14 agentydragon dbus-daemon[3143]: [session uid=1000 pid=3143] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.1' (uid=1000 pid=3139 comm="/usr/libexec/tracker-miner-fs " label="> Mai 10 13:25:14 agentydragon systemd[3110]: Starting Tracker metadata database store and lookup manager... Mai 10 13:25:14 agentydragon dbus-daemon[3143]: [session uid=1000 pid=3143] Successfully activated service 'org.freedesktop.Tracker1' Mai 10 13:25:14 agentydragon systemd[3110]: Started Tracker metadata database store and lookup manager. Mai 10 13:25:14 agentydragon dbus-daemon[3143]: [session uid=1000 pid=3143] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.1' (uid=1000 pid=3139 comm="/usr/libexec/tracker-mi> Mai 10 13:25:14 agentydragon systemd[3110]: Starting Tracker metadata extractor... Mai 10 13:25:14 agentydragon tracker-extract[49035]: Set scheduler policy to SCHED_IDLE Mai 10 13:25:14 agentydragon tracker-extract[49035]: Setting priority nice level to 19 Mai 10 13:25:14 agentydragon dbus-daemon[3143]: [session uid=1000 pid=3143] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract' Mai 10 13:25:14 agentydragon systemd[3110]: Started Tracker metadata extractor. Mai 10 13:25:15 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:18 agentydragon gnome-shell[5836]: JS ERROR: TypeError: fileItem is undefined _updateDesktopIfChanged@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:349:17 _monitorDesktopFolder/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:311:94 Mai 10 13:25:18 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.viminfo.tmp«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:21 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:25 agentydragon systemd[3110]: tracker-extract.service: Succeeded. Mai 10 13:25:25 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:37 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:48 agentydragon tracker-store[49001]: OK Mai 10 13:25:48 agentydragon systemd[3110]: tracker-store.service: Succeeded. Mai 10 13:25:59 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der
[Bug 1868660] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist()
i got this error when hovering with the mouse over the system tray as described in the bug report however Iam using X11 and not wayland i have the following crash files: -rw-r- 1 root root 95M Mai 10 13:15 _usr_bin_gnome-shell.1000.crash -rw-r--r-- 1 root root0 Mai 10 13:15 _usr_bin_gnome-shell.1000.upload -rw--- 1 root root 37 Mai 10 13:15 _usr_bin_gnome-shell.1000.uploaded -rw-r- 1 root root 2,4M Mai 10 13:15 _usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.crash -rw-r--r-- 1 root root0 Mai 10 13:15 _usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.upload -rw--- 1 root root 37 Mai 10 13:15 _usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.uploaded -- 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/1868660 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1868660/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877841] Re: with the dark theme, the active line is highlighted and I cannot see the text I am typing.
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1857191, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1877841 Title: with the dark theme, the active line is highlighted and I cannot see the text I am typing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1877841/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877841] [NEW] with the dark theme, the active line is highlighted and I cannot see the text I am typing.
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 Public bug reported: 1) Release: 20.04 2) Version: 3.36.1-1 3) Expected: I have the Dark theme on. On opening Gedit, the active line is all white. When I typed, I expected to see letters. 4) What happened: Nothing appeared. I thought it had locked up. I tapped on the Enter key and it went to the next line, revealing the text I had typed on the previously active line. So, it seems like with Dark theme on the text is white and same as the highlight. When I switched back to Standard theme, no problems. The text was black, the blank space is white and the highlight is slightly off-white (beige maybe, not good with the naming of colors). It's perfectly legible. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 17:35:24 2020 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2020-05-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_PH:en LANG=en_PH.UTF-8 SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-05-10 17-54-58.png" https://bugs.launchpad.net/bugs/1877841/+attachment/5369386/+files/Screenshot%20from%202020-05-10%2017-54-58.png ** Description changed: 1) Release: 20.04 2) Version: 3.36.1-1 - 3) Expected: I have the Dark theme on. On opening Gedit, the active line is all white. When I typed, I expected to see letters. - 40 Nothing appeared. I thought it had locked up. I tapped on the Enter key and it went to the next line, revealing the text I had typed on the previously active line. So, it seems like with Dark theme on the text is white and same as the highlight. When I switched back to Standard theme, no problems. The text was black, the blank space is white and the highlight is slightly off-white (beige maybe, not good with the naming of colors). It's perfectly legible. + 3) Expected: I have the Dark theme on. On opening Gedit, the active line is all white. When I typed, I expected to see letters. + 4) Nothing appeared. I thought it had locked up. I tapped on the Enter key and it went to the next line, revealing the text I had typed on the previously active line. So, it seems like with Dark theme on the text is white and same as the highlight. When I switched back to Standard theme, no problems. The text was black, the blank space is white and the highlight is slightly off-white (beige maybe, not good with the naming of colors). It's perfectly legible. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 17:35:24 2020 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2020-05-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=en_PH:en - LANG=en_PH.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=en_PH:en + LANG=en_PH.UTF-8 SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: 1) Release: 20.04 2) Version: 3.36.1-1 3) Expected: I have the Dark theme on. On opening Gedit, the active line is all white. When I typed, I expected to see letters. - 4) Nothing appeared. I thought it had locked up. I tapped on the Enter key and it went to the next line, revealing the text I had typed on the previously active line. So, it seems like with Dark theme on the text is white and same as the highlight. When I switched back to Standard theme, no problems. The text was black, the blank space is white and the highlight is slightly off-white (beige maybe, not good with the naming of colors). It's perfectly legible. + 4) What happened: Nothing appeared. I thought it had locked up. I tapped on the Enter key and it went to the next line, revealing the text I had typed on the previously active line. So, it seems like with Dark theme on the text is white and same as the highlight. When I switched back to Standard theme, no problems. The text was black, the blank space is white and the highlight is slightly off-white (beige maybe, not good with the naming of colors). It's perfectly legible. ProblemType: Bug
