[Bug 1831332] Re: Huge stack of credential dialogs when switching user
[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/1831332 Title: Huge stack of credential dialogs when switching user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors
Thanks to nugai's comment#25, this works for me: 1. Create a screen layout in `~/.config/monitors.xml`. 2. Copy the file to `/var/lib/gdm3/.config/` and change ownership: sudo cp ~/.config/monitors.xml /var/lib/gdm3/.config/ sudo chown gdm:gdm /var/lib/gdm3/.config/monitors.xml The monitor layout will persist across restarts and screen locks. -- 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/1874217 Title: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882410] [NEW] GNOME Shell crashed with signal 5
Public bug reported: A couple of times a day, I'm noticing all of the window dressing suddenly disappear from all of my open applications, then a second or two later returning. Opening up /var/log/syslog I see: Jun 6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518. Jun 6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f. Jun 6 20:47:40 eva gnome-shell[335243]: toggling down object GInotifyFileMonitor that's already queued to toggle down Jun 6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5 Jun 6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 0x557e3a0446a0 == Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with result 'core-dump'. Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11... Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID vendor "ACI", prod id 8434 Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using hsync ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using vrefresh ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Printing DDC gathered Modelines: Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1600x900"x0.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz eP) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) Jun 6 20:47:40 eva gsd-media-keys[26011]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell” on object at path /org/gnome/Shell Jun 6 20:47:41 eva gnome-shell[338452]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. Jun 6 20:47:41 eva
[Bug 1875528] Re: Extra frozen / stuck mouse cursor after auto screen lock / sleep
Experiencing same problem, in most cases displays that go into sleep modus (or you turn them off and on again) don't remove themselves from the display driver. But some displays gets removed form the gpu(or xorg, i don't know) display driver and the re-added. So basically this happens when you displays are re-arranging cause you added or removed a display (either manually or automatically by the display itself). This problem is viewable in multi-monitor setup, where 1 monitor is programmed to detach himself from the gpu when going to sleep or off, and the other(s) are just turning the screen black, but stay connected to the gpu. When you turn off you (problem) display, you actually see linux re-arranging windows/applications on the screen(s) that don't detach themselves from the gpu. Seeing this happen, I came to this conclusion, that some display detach themselves from the gpu when going to sleep, and therefore linux thinks a display is being removed and re-arranges everything. During this re-arrangement process a duplicate cursor is created and becomes frozen, a new cursor is created and becomes your primary cursor that behaves normally. possible fix for this is linux resetting all cursors in xorg/gpu driver when completing such re-arrangement process. I have zero understanding of xorg or gpu driver programming, but i do know that xorg is programmed to be able to have multiple cursors. So my suspicion is with xorg programming. I hope this gets fixed, It's really annoying, when you are working and have tons of apps open, you are required to log out and restart your workspace, which can be a hasle and time consuming. -- 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/1875528 Title: Extra frozen / stuck mouse cursor after auto screen lock / sleep To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1875528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882399] [NEW] Window placements
Public bug reported: When moving a chrome pop-up window (file selection for upload), moving this window moves the original window. Also: the new window don't launch to the last closed position as they used to in 18.04. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags removed: des -- 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/1882399 Title: Window placements To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862698] Re: Do not ship preinstalled Remmina with gnome-session file
I've just added a compile time option to enable/disable the installation of those files, so that we can provide a package to those users that needs the session files. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1862698 Title: Do not ship preinstalled Remmina with gnome-session file To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1862698/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882394] [NEW] xrdp configured, connects successful then terminates
Public bug reported: xrdp is setup, connections to client work: mstsc connects to client, authentication is successful, then starts x11, starts session, terminates session, terminates x11, closes connection. All without any visible error. Any idea why? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xrdp 0.9.12-1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 6 23:33:49 2020 InstallationDate: Installed on 2019-09-09 (271 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=de_DE TERM=screen PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: xrdp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xrdp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xrdp in Ubuntu. https://bugs.launchpad.net/bugs/1882394 Title: xrdp configured, connects successful then terminates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1882394/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876609] Re: gnubiff applet crashes when mail is received signal 5 in XGetWindowProperty
Crash in gnome-flashback most likely is https://gitlab.gnome.org/GNOME /gnome-flashback/-/commit/bd970ecf9cbebebcabc8befad2df83132a1920c4. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1876609 Title: gnubiff applet crashes when mail is received signal 5 in XGetWindowProperty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1876609/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876609] Re: gnubiff applet crashes when mail is received signal 5 in XGetWindowProperty
** Project changed: gnome-panel => gnome-panel (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1876609 Title: gnubiff applet crashes when mail is received signal 5 in XGetWindowProperty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1876609/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876609] [NEW] gnubiff applet crashes when mail is received signal 5 in XGetWindowProperty
You have been subscribed to a public bug: I had been using gnubiff in the gnome panel in Ubuntu 16.04. I recently did an in-place upgrade from 16.04 to 18.04. Now X crashes whenever mail is received. In place upgrade from Ubuntu 16.04 to 18.04 gnubiff from package gnubiff 2.2.17-build1 In Gnome Flashback (Metacity) display manager. Add gnubiff to gnome-panel Then receive mail Gnubiff icon moves down the panel so its not completely visible. Then X dies and I'm sent back to the login page. I try login again and I'm immediately logged out again with the same error. I can login with Ubuntu ( display manager ) ok Then I can use dconf-editor to remove gnubiff from the panel org.gnome.gnome-panel.layout remove 'gnubiff-applet' from this list. After that I can login using Gnome Flashback (Metacity) without error. Then I get a ubuntu-bug popup Ubuntu 18.04 has experienced an internal error. /usr/bin/gnome-panel gnome-panel crashed with signal 5 in XGetWindowProperty() ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New -- gnubiff applet crashes when mail is received signal 5 in XGetWindowProperty https://bugs.launchpad.net/bugs/1876609 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. -- 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."
Sorry for not using this correctly, but can't seem to add Distributions or packages in the "affects" section. Claws-Mail Ubuntu 18.04, as others have said, wont connect pop3 or imap because of this error. -- 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/gnutls/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882377] [NEW] path bar flickering when path is longer than the space in the header bar
Public bug reported: This is copy of my upstream bug report: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1512 The issue will not be fixed because the upcoming version of nautilus has a changed pathbar design which prevents it. (See conversation on the gnome bug tracker). This bug looks also a lot like an old bug in launchpad on 13.04, could be the same issue. https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1167710 -- Affected version Other: Ubuntu 20.04 with Nautilus 3.36.2-0ubuntu1 Nightly flatpak: No Steps to reproduce: Open Nautilus/Files open a nested folderpath structure untill the names of the path do not fit in the pathbar anymore Hover the mouse over the first or the last folder name visible in the path Current behaviour: The path bar starts flickering (probably alternating the display of the visible/not visible folders?(see attached screencast) Expected behaviour: No flickering, but moving the displayed path when ascending deeper in the folder structure. Additional information: 1) I have also tested if this depends on the number of folders or on the length of the folder name the issue is also triggered with a shallow path with only a few very long folder names and not with >10 2 letter wide folder names 2)I've tested both the Ubuntu Yaru theme and the gnome default Adwaita light them, it occurs in both so does not seem to be theme specific. 3) The issue seems to be fixed in the nightly build. ** Affects: nautilus Importance: Unknown Status: Unknown ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screencast" https://bugs.launchpad.net/bugs/1882377/+attachment/5381022/+files/nautilus_pathbar_behaviour_2020-06-02.mp4.webm ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1512 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1512 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/1512 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1882377 Title: path bar flickering when path is longer than the space in the header bar To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1882377/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1243532] Re: Custom keyboard shortcuts don't work until logout
I have created a new bug report for the issue on Cinnamon (bug #1882375) since it is likely cinnamon-specific und unrelated to this bug; cinnamon uses cinnamon-settings-daemon instead of gnome-settings-daemon. -- 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/1243532 Title: Custom keyboard shortcuts don't work until logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1243532/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882375] [NEW] Cinnamon custom keyboard shortcuts don't work until logout
Public bug reported: Description:Ubuntu 20.04 LTS Release:20.04 cinnamon: 4.4.8-4 cinnamon-settings-daemon: 4.4.0-3 Steps to Reproduce: - on Cinnamon desktop, run cinnamon-settings - go to Keyboard > Shortcuts > Custom Shortcuts - add a custom shortcut, or edit the command or shortcut of an existing custom shortcut Expected behavior: the shortcut should become active immediately Actual behavior: the shortcut does not work until you log out and log in again This seems similar to bug #1243532, but I'm reporting this as a new bug now because it is cinnamon-specific. Other shortcuts (e.g. Close Window) are updated immediately, this only affects custom shortcuts. I think this bug appeared in 20.04. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- 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/1882375 Title: Cinnamon custom keyboard shortcuts don't work until logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1882375/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 640418] Re: Please add support for bash highlight in gedit
Could we reopen this, please?
gedit has highlighting for sh, but not for bash.
Most of the time, this works fine for bash, but sometimes it goes wrong.
For example, use a command substitution that contains a quote within
case-esac as follows.
#!/bin/bash
case ${SOMETHING} in
( 'a' )
FILENAME="$( readlink "${ARG}" )"
;;
esac
CONFUSING_LINE="case esac"
Starting from the line with the command substitution, gedit thinks that
the rest of the file is within quotes — except those that are parts that
are actually within quotes! This makes it confusing to edit a large
script.
Thank you
** Changed in: gedit (Ubuntu)
Status: Expired => Confirmed
--
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/640418
Title:
Please add support for bash highlight in gedit
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/640418/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881712] Re: gnome-software says connection is metered while is not
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed -- 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/1881712 Title: gnome-software says connection is metered while is not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1881712/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
This option work only with hybrid graphics. If you select "NVIDIA On-Demand" all will run on intel\amd integrated GPU(but you can run selected app on nvidia discrete GPU). Without integrated GPU this workaround don't work. -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
I can confirm that the problem is present with both the intel and the modesetting driver on Braswell systems. The exact symptoms differ for each, but in both cases it is triggered when the mouse touches the left limit of the screen. With modesetting, it seems to "stick" until you move the mouse away from the left side. With intel, touching the left side starts a flickering that persists even after you move the mouse away. Mainly, just the mouse cursor flickers, but the whole screen will flicker when doing graphics intensive tasks like fullscreen video or gaming. Sometimes, the mouse flicker can be so bad it becomes nearly invisible. I have made full report on the bug report thread opened by Salvatore. The good news is I found a workaround, you can use xrandr to scale the display to 0.x0. and this prevents the issues in both intel and modesetting. This can be done in your .xprofile in your home directory to take effect at login. It does come with a slight performance penalty, but it's preferable to the glitching that happens otherwise (at least until someone fixes the regression). xrandr --output HDMI-3 --mode 1920x1080 --scale 0.x0. Replace "HDMI-3" with the name of your display (can be found by running xrandr with no options). -- 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/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1767654/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882362] [NEW] Focus not where it should be
Public bug reported: Steps to reproduce: 0. Make sure you have an image file in your desktop, and that you have a folder somewhere in your filesystem that contains at least one file of any kind. Make also sure you have no window open, or otherwise do Show Desktop so that your desktop is visible. 1. Open a nautilus window and navigate to the a folder that has some files in it. So now a Nautilus window is in foreground with a folder open showing the contents of the folder 2. Make sure this window is not maximized, and move it around so that, on the background, you can see your desktop, and specifically, an image file that is in your desktop. Remember, at this stage the Nautilus window with the folder is in the foreground, focused. 3. Click on some file within the nautilus window to select it. 4. Click on the desktop background. Then click on some file on the desktop. Then on another one. Then finally on one particular image file that you have in your desktop. Now the desktop has focus and something in it is selected. NOTE: you can skip step 4, and you would observe the issue allthesame and it would still be bad. But the fact that explicitly including this step 4 you can observe the issue, makes it even more egregious. 5. Double ckick on the image file in the desktop, so as to open it in the default image viewer Now the image viewer window is in the foreground. 6. Close the image viewer window 7. Hit the Delete key. ** EXPECTED ** After step 6, focus should return to the desktop, where the image file was selected. Hence, hitting the Delete key should delete it ** OBSERVED ** For some random nonsensical reason, after step 6, the Nautilus window with the folder is focused, and hence, when you hit the delete key you delete whatever file was selected in it. This is a HUGE issue which may cause you to delete the wrong content without even realising it. And if you don't realise soon enough, you may be unable to undelete it. Just one more of a gazillion bugs that make Nautilus not only unusable, but also DANGEROUS. One of the most essential components of a Desktop operating system and yet one of the most broken ones. Fucking pathetic. I'm done with this crap, I will get rid of Ubuntu and install some other distro. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 6 15:45:50 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1464x887+768+660'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2429 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial ** Description changed: Steps to reproduce: 0. Make sure you have an image file in your desktop, and that you have a - folder somewhere that contains at least one file of any kind. Make also - sure you have no window open, or otherwise do Show Desktop so that your - desktop is visible. + folder somewhere in your filesystem that contains at least one file of + any kind. Make also sure you have no window open, or otherwise do Show + Desktop so that your desktop is visible. 1. Open a nautilus window and navigate to the a folder that has some files in it. So now a Nautilus window is in foreground with a folder open showing the contents of the folder 2. Make sure this window is not maximized, and move it around so that, on the background, you can see your desktop, and specifically, an image file that is in your desktop. Remember, at this stage the Nautilus window with the folder is in the foreground, focused. 3. Click on some file within the nautilus window to select it. 4. Click on the desktop. Then click on some file on the desktop. Then on another one. Then finally on one particular image file that you have in your desktop. Now the desktop has focus and something in it is selected. NOTE: you can skip step 4, and you would observe the issue allthesame and it would still be bad. But the fact that explicitly including this step 4 you can observe the issue, makes it even more egregious. 5. Double ckick on the image file in the desktop, so as to open it in the default image viewer Now the image viewer window is in the foreground. 6. Close the image viewer window - 7.
[Bug 1882361] [NEW] Dead/frozen mouse pointer after login
Public bug reported: A dead/frozen copy of the mouse pointer remains on the screen, after login. This issue has been previously reported by other users. The dead mouse pointer goes away if you switch the the Scale on Display Settings to any alternative and then back to your desired scale. Using an AMD Ryzen processor with a Radeon Vega graphics chip and default Gnome desktop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 06:41:46 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-10 (27 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882361 Title: Dead/frozen mouse pointer after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882361/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1750146] Re: Xbox (One) Wireless Controller won't connect
Launchpad has imported 4 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=198919. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-02-24T15:44:25+00:00 jebeld17 wrote: ** SEE THE ORIGINAL BUG REPORT IN LAUNCHPAD HERE: https://bugs.launchpad.net/gnome-control-center/+bug/1750146 ** Xbox One Wireless Controllers refuse to connect via bluetooth with Ubuntu 17.10 in the gnome-control-center. Placing the controller into pairing mode makes it visible on the Bluetooth Devices list and the device pairs, but does not make the full connection needed to pull the controller out of pairing mode. This renders my controller unusable with my Ubuntu PC unless I want to resort to using the wire (microUSB). Please fix. See the attached system information below. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13 Uname: Linux 4.13.0-32-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 17 09:26:14 2018 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1750146/comments/3 On 2018-05-03T01:07:37+00:00 jebeld17 wrote: I've tried on Ubuntu 18.04 LTS and I'm still getting the same issues. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1750146/comments/8 On 2018-05-03T01:07:56+00:00 jebeld17 wrote: I've tried on Ubuntu 18.04 LTS and I'm still getting the same issues. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1750146/comments/9 On 2020-06-05T20:42:57+00:00 noelboettcher2004 wrote: Same issues with Ubuntu 20.04 LTS with the 5.7.0 Kernel. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1750146/comments/14 ** Changed in: linux Status: Unknown => Confirmed ** Changed in: linux Importance: Unknown => High -- 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/1750146 Title: Xbox (One) Wireless Controller won't connect To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1750146/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882348] [NEW] Gnome shell 'Show Applications' app names commonly truncated
Public bug reported: The way people browse their apps and is key to discoverability for new Linux users. Despite the grid layout including quite a lot of space, whenever apps have more than about 12-13 characters in their name they get truncated and even when you hover over the icons it still doesn't display the names of the apps. Therefore you are left not knowing what the app is unless you know the icon or launch the app to discover the full name. This is surprising common. A few examples: Firefox Web Br... LibreOffice Imp... LibreOffice Wri... Language Supp... Document Sca... Document Vie... Passwords and ... Visual Studio C... Software & Up... While we know or can guess what most of them are, there's loads of space so why can't we give two lines for app names so all reasonably named apps have their names displayed in full? ** 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/1882348 Title: Gnome shell 'Show Applications' app names commonly truncated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882348/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1570227] Re: Open Recent Items show as always empty in Gedit
Thank you so much jimmack (jim-oss-ltd), after 4 years I got it to work now! -- 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/1570227 Title: Open Recent Items show as always empty in Gedit To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1570227/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882342] [NEW] Ubuntu 20 Charging Indicator Blinks
Public bug reported: https://askubuntu.com/questions/1240326/charging-indicator-blinks- unexpectedly-on-tecno-winpad-10a-ubuntu-20-04 I'd the same problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 15:00:10 2020 InstallationDate: Installed on 2020-05-04 (32 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1882342 Title: Ubuntu 20 Charging Indicator Blinks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1882342/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
