[Bug 1841894] Re: Wayland: Image of mouse cursor left on screen after unlock
I'm on Fedora 30 and also experiencing this. Dual monitors (one rotated, portrait right) on Wayland, but not using any scaling. Happens every time when waking up from sleep. AMD Vega 56 graphics card. Bug report (not by me) on Red Hat Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1745055 ** Bug watch added: Red Hat Bugzilla #1745055 https://bugzilla.redhat.com/show_bug.cgi?id=1745055 -- 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/1841894 Title: Wayland: Image of mouse cursor left on screen after unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1257920] [NEW] Left/right Ctrl/Alt/Shift key limitation not respected for language input shortcuts
Public bug reported: I know there are a lot of bugs on the text entry source keyboard switch shortcut. I hope this is not a duplicate. I couldn't find it reported anywhere. The problem: Specifying keys such as Shift L, Shift R, Alt L, Alt R, Ctrl L, and Ctrl R in the Switch to next source using box does not always limit the switch to being executed to the specified key, in other words, if you specified to use Key L, sometimes Key R will execute the language switch, and vice versa. This occurs in the following cases: I have two input languages selected: Primary: English (US) Secondary (Swedish) 0. Set keyboard switch to Alt+Shift L (use Alt L to define the shortcut, not sure if this matters, but just in case) 1. Press Alt L+Shift L (Alt L first and Shift L second) 1.1 Note that language input switches to the next source -- All good so far 2. Press Alt L+Shift L again in the reverse order (Shift L first and Alt L second) 2.1 Note that language input switches to the next source -- This is OK, order shouldn't matter 3. Press Alt L+Shift R (Alt L first and Shift R second) 3.1 Note that language input does not switch to the next source -- It shouldn't since we specified to use Shift L, not Shift R, so this is still good 4. Press Alt L+Shift R again in the reverse order (Shift R first and Alt L second) 4.1 Note that language input switches to the next source -- This is not good, Shift R should not execute the switch since we specifically defined the shortcut to use Shift L 5. Press Alt R+Shift L (Alt R first and Shift L second) 5.1 Note that language input switches to the next source under specific conditions (only if you are switching from primary to secondary language, not vice versa) -- This is not good, it should switch every time 6. Press Alt R+Shift L again in the reverse order (Shift L first and Alt R second) 6.1 Note that language input switches to the next source under specific conditions (only if you are switching from primary to secondary language, not vice versa) -- This is not good, it should switch every time 7. Press Alt R+Shift R (Alt R first and Shift R second) 7.1 Note that language input does not switch to the next source -- It shouldn't, so this is good 8. Press Alt R+Shift R again in the reverse order (Shift R first and Alt R second) 8.1 Note that language input switches to the next source under specific conditions (only if you are switching from primary to secondary language, not vice versa) -- This is not good, Shift R should not execute the switch since we specifically defined the shortcut to use Shift L In summary if you define the shortcut to be Alt+Shift L problems occur when pressing in 4 out of 8 combinations (order included): Alt L+Shift R (Shift-key first), Alt R+Shift L (Shift-key first), Alt R+Shift L (Alt-key first), and Alt R+Shift R (Shift-key first). Now, finally you can repeat this exercise for any permutation of combinations of the Shift L, Shift R, Alt L, Alt R, Ctrl L, and Ctrl R keys (set shortcut to Alt L+Shift, Alt+Ctrl L, Alt L+Ctrl, ..., Shift+Ctrl R, Shift R+Ctrl) and you'll find similar problems, but not always identical to the behaviour outlined above. However, I have not had the desired to map this all out :-) Hopefully the example above, with Alt+Shift L, will be enough to round up the problem in the code. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45.1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Dec 4 15:17:19 2013 InstallationDate: Installed on 2013-10-26 (39 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- 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/1257920 Title: Left/right Ctrl/Alt/Shift key limitation not respected for language input shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1257920/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1253187] Re: Unable to unmount Nexus 4: The connection is closed
Bug reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=719322 ** Bug watch added: GNOME Bug Tracker #719322 https://bugzilla.gnome.org/show_bug.cgi?id=719322 -- 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/1253187 Title: Unable to unmount Nexus 4: The connection is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1253187/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1253203] Re: Nautilus does not respect show/hide hidden files setting on mounted MTP device
Upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=719324 ** Bug watch added: GNOME Bug Tracker #719324 https://bugzilla.gnome.org/show_bug.cgi?id=719324 -- 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/1253203 Title: Nautilus does not respect show/hide hidden files setting on mounted MTP device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1253203/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1253187] Re: Unable to unmount Nexus 4: The connection is closed
Running Ubuntu 13.10 and Android 4.3. -- 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/1253187 Title: Unable to unmount Nexus 4: The connection is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1253187/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1253187] [NEW] Unable to unmount Nexus 4: The connection is closed
Public bug reported: When I click the eject triangle next to my Nexus 4 in Nautilus this error message appears (see title/screenshot). I am uncertain whether the phone actually unmounts or not so that it is safe to disconnect it. After the error message appears I can still access the phone content at /run/user/1000/gvfs/mtp..., which suggests that the phone is still mounted. sudo umount /run/user/1000/gvfs properly unmounts the phone. Expected behaviour: To receive a confirmation message from Nautilus saying it is now safe to disconnect the phone. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 20 13:25:42 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'685x847+753+24' b'org.gnome.nautilus.window-state' b'sidebar-width' b'174' InstallationDate: Installed on 2010-04-30 (1300 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-10-18 (33 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Attachment added: Untitled window_002.png https://bugs.launchpad.net/bugs/1253187/+attachment/3913479/+files/Untitled%20window_002.png -- 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/1253187 Title: Unable to unmount Nexus 4: The connection is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1253187/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1253203] [NEW] Nautilus does not respect show/hide hidden files setting on mounted MTP device
Public bug reported: To reproduce: 1. Connect MTP device (in my case Nexus 4, Android 4.3) with USB cable . The device auto-mounts in Nautilus. 2. Select/unselect Show hidden files (or press Ctrl-H several times) 3. Note that hidden files are always shown, regardless of setting. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 20 13:59:27 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'685x847+65+24' b'org.gnome.nautilus.window-state' b'sidebar-width' b'174' InstallationDate: Installed on 2010-04-30 (1300 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-10-18 (33 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- 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/1253203 Title: Nautilus does not respect show/hide hidden files setting on mounted MTP device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1253203/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 689139] Re: Shotwell doesn't import across symbolic link
Still not fixed in Shotwell 0.15 (Ubuntu 13.10). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/689139 Title: Shotwell doesn't import across symbolic link To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/689139/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 567219] Re: After last updates evince become very slow to open PDF documents
** Changed in: evince (Ubuntu) Status: New = Confirmed -- After last updates evince become very slow to open PDF documents https://bugs.launchpad.net/bugs/567219 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 567219] Re: After last updates evince become very slow to open PDF documents
I've had this same problem for at least several weeks. In addition, evince is very slow to close. If I click the close window button it takes a good several seconds, sometimes more than 10s, for the window to close. Often that meas that a warning pop-up appears saying that evince is unresponsive. However, if I just wait a few more seconds evince always tend close eventually. As mentioned above, the startup and close slowness seems intermittent. It sometimes occurs, sometimes not, even on the same document. CPU usage seems unaffected during these mini-freezes. -- After last updates evince become very slow to open PDF documents https://bugs.launchpad.net/bugs/567219 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 353186] Re: Can't define primary screen in dual screen setup
*** This bug is a duplicate of bug 216144 *** https://bugs.launchpad.net/bugs/216144 Well, the third step may be a little dangerous, since you can end up with two screens turned off unless the external was turned on already. This worked for me: xrandr --output VGA1 --primary; xrandr --output VGA1 --auto --pos 0x0 --output LVDS1 --auto --left-of VGA1 -- Can't define primary screen in dual screen setup https://bugs.launchpad.net/bugs/353186 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 260492] Re: opening a directory using an application change associations incorrectly
I can confirm that the problem still exists. I upgraded from hardy to intrepid RC1 on Oct 25th, and ever since baobab was started whenever I clicked a location under the Places menu. I resolved this simply by removing the following problematic line in .local/share/applications/mimeapps.list: [Added Associations] inode/directory=baobab-usercreated.desktop; -- opening a directory using an application change associations incorrectly https://bugs.launchpad.net/bugs/260492 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 260492] Re: opening a directory using an application change associations incorrectly
Sebastian: I went back and looked at a backed up version of .local/share/applications/mimeapps.list from my hardy installation (i.e. what I had before I upgraded to intrepid RC1). I was surprised to see that my hardy and intrepid mimeapps.list files are identical. So, just to be clear, I had the buggy line [Added Associations] inode/directory=baobab-usercreated.desktop; also in my hardy installation. However, I didn't experience any problems in hardy. Strange... Let me know what I can do to help further. -- opening a directory using an application change associations incorrectly https://bugs.launchpad.net/bugs/260492 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
