[Bug 1695607] Re: Killed Wine application still shown in Gnome launcher
This was still the case in Ubuntu 17.10 (I'll be able to retest and submit new logs soon). - The zombie Wine icons clutter the Gnome Shell launcher and app switcher until there is no space - Moreover Wine leaves the window manager in a really messy state so that Alt-Tab does not trigger app switching in Gnome Shell (and in Unity, windows were placed on top of the shell/launcher/dash) Work-around: - close/loose all applications and restart the session (Wayland) - restart window manager with Alt+F2 and type "r[enter]" (under Xorg) -- 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/1695607 Title: Killed Wine application still shown in Gnome launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695607/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1731757] [NEW] When unlocking keyrings, seahorse should remember choice for "Automatically unlock this keyring"
Public bug reported: As a user, I want to keep some specific secrets under special protection, i.e. only manually unlocked on demand and not at login. Everytime that I manually unlock a keyring, the password dialog contains a preselected checkbox "Automatically unlock this keyring whenever I'm logged in". To preserve the status quo (keyring not automatically unlocked) there is always user interaction required to uncheck the checkbox. In other words, seahorse defaults to reduce the level of security. Expected behavior: - The checkbox should not be preselected. Rationale: 1. While there might exist cases where a user later wants configure a keyring to unlock automatically, this is rather a rare case. It causes much less effort to check the checkbox when you really want to instead of unchecking it every time. 2. This is very very prone to user error. Here, user error affects security. 3. Once the checkbox is checked, this cannot easily be reverted because the password dialog won't appear anymore. - (Maybe) The checkbox should be completely removed. See justification in https://bugzilla.gnome.org/show_bug.cgi?id=576676 (planned to be included 8 years ago) I just found this bug has been reported and discussed upstream 3.5 years ago with a patch submitted that has neither been released nor even reviewed. Now in the 4th subsequent Ubuntu release users can still not benefit from it. Apart from the bug itself, the kind of upstream bug-handling is very disappointing for an app that is at the core of the OS security. See: https://bugzilla.gnome.org/show_bug.cgi?id=725641 Version: seahorse 3.20.0-3.1 System: Ubuntu 17.10 Gnome Shell ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1731757 Title: When unlocking keyrings, seahorse should remember choice for "Automatically unlock this keyring" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1731757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1708828] Re: Tap-to-click does not work in GDM
Lenovo Yoga 2 Pro (but on 17.04, have not tested 17.10 yet) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1708828 Title: Tap-to-click does not work in GDM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1708828/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1708828] Re: Trackpad tap does not work in GDM
A point to consider is that not all touchpads look the same and behave the same. Hardware manufacturers do use their freedom of physical design decisions to drive the user into a natural interaction that fits their vision. By not having visible buttons and requiring significant force for physical clicking, touch tends to feel more natural (as in the name). While not a "significant restriction", the software view is often much simpler than the variety of real hardware outside. This poses rather an inconsistency, and the system does not notify the user about the change of interaction paradigm. This also appears new and inconsistent in comparison to other widespread desktops (Unity) where such enforcements are not active. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1708828 Title: Trackpad tap does not work in GDM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1708828/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1708828] [NEW] Trackpad tap does not work in GDM
Public bug reported: When Gnome Shell crashes or after boot, GDM is shown and asks the user to select an account and type the password. However selecting the account by tapping on it with the trackpad does not work. One has to press hard on the trackpad until it makes a cracking noise. This is probably because the defaults in the input manager for GDM and new user accounts are set to disable "tap to click". 1. The default is inconsistent for users who have this enabled within their account, but unexpectedly encounter the default before logging in. 2. The default (for session login etc.) should be all-encompassing rather than specialized/restrictive. A user being used to click is not hindered by tapping being enabled. A user being used to tap is however hindered by tapping being disabled. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gdm3 3.24.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Aug 5 14:12:39 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-05 (273 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages zesty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1708828 Title: Trackpad tap does not work in GDM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1708828/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1695615] Re: [gdm] lock screen password field resets every second
Steps to reproduce: 1. gnome-shell --replace 2. Lock the screen 3. Unlock the screen and start typing the password -- 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/1695615 Title: [gdm] lock screen password field resets every second To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1695615/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1695615] [NEW] lock screen pasword field resets every second
Public bug reported: After the screen is locked, one normally swipes the screen up and types the password into the password field that is shown. Sometimes, the password field resets the typed text every second (as if the lockscreen is reloaded). Subsequently, when you finish typing your password, the beginning of the password is missing and unlocking fails repeatedly. Workaround: Press Ctrl+Alt+F1 (login screen), click your user account and type the password. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-shell 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 3 15:14:36 2017 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-05 (210 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages zesty -- 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/1695615 Title: lock screen pasword field resets every second To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695615/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1695607] [NEW] killed application still shown in dash
Public bug reported: After a Wine application has been killed by OOM, its icon is still shown in the Gnome Shell dash and marked as running application. The icon is not associated with any process, since no process of the killed application is running. Klicking the icon triggers after some time a dialog " does not respond. [Wait] [Force quit]". When choosing any of these choices, nothing happens and the icon persists in the dash until Gnome Shell is restarted. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-shell 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 3 14:14:20 2017 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-05 (210 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages zesty -- 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/1695607 Title: killed application still shown in dash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695607/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287917] Re: help content is not rendered to device-pixels on high-dpi screen
This bug has been fixed somewhen in WebKitGTK. ** Changed in: yelp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1287917 Title: help content is not rendered to device-pixels on high-dpi screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1287917/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1665382] Re: File operation progress does not complete properly
How can a non-working feature from upstream be merged into a stable Ubuntu release without review/trying out? And if Gnome releases are always work-in-progress, then Ubuntu should not "freeze" the buggy state for half a year, but forward to its users not only security updates but also all feature bugfixes. -- 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/1665382 Title: File operation progress does not complete properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1665382/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1665382] Re: File operation progress does not complete properly
Upstream bug: Bug 773527 - Copy progress popover should close on completion https://bugzilla.gnome.org/show_bug.cgi?id=773527 ** Bug watch added: GNOME Bug Tracker #773527 https://bugzilla.gnome.org/show_bug.cgi?id=773527 -- 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/1665382 Title: File operation progress does not complete properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1665382/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1665382] [NEW] File operation progress does not complete properly
Public bug reported: When copying files, a progress indicator button appears in the toolbar (round "cake" diagram). It also opens a popover that lists all file operations with a progress bar each. Unfortunately the popover 1) covers a huge part of the window, 2) it is opened on all nautilus windows on all workspaces, 3) the progress popover does not close on its own when the operations are completed (circle diagram shows full, but does not disappear) and 4) the unity launcher icon and alt-tab switcher continue displaying the full progress bar. Furthermore, the unconscious need to remove what covers your sight seduces the user to click the nearest "X" to close the popover. However, the "X" aborts file operations leading to corrupted, incompletely copied files. The correct way is to toggle the progress button. However, the toggle-off action is unintuitive because the user did not manually toggle it on. Expected behavior: Popover window opens when the user clicks the progress indicator button, and it only opens on the current workspace. After file operations complete, it closes on its own and the progress bar on the launcher icon disappears. Actual behavior: Popover window opens on all nautilus windows. After file operations complete, they do not close. Ubuntu 16.10 nautilus 1:3.20.3-1ubuntu3.1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/1665382 Title: File operation progress does not complete properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1665382/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1534645] Re: Cannot easily preserve a keyring to be only unlocked manually
This is still the case in Ubuntu 16.10 with seahorse 3.20.0-2ubuntu1 and gnome-keyring 3.20.0-2ubuntu4 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1534645 Title: Cannot easily preserve a keyring to be only unlocked manually To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1534645/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1644830] [NEW] gnome-software process does not quit after closing application window
Public bug reported: Gnome-system-monitor shows a process "gnome-software" that continues running after the application window has been closed. The process constantly takes 100–200MB RAM and was not there after boot/login. Observed behavior: Process does not quit after quitting the application window, although it is neither used nor does it seem to give any other noticeable benefit from the reserved memory. Expected behavior: After closing the application window, it's process ends. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-software 3.20.1+git20161003.0.7ac7d1b-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 25 14:05:31 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-05 (20 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1644830 Title: gnome-software process does not quit after closing application window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1644830/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1581377] [NEW] text-scaling-factor changes from 1.0
Public bug reported: After upgrading from Ubuntu 15.10 to 16.04, org.gnome.desktop.interface .text-scaling-factor is not anymore set to 1.0 (as before upgrade) and it does not want to be set to this value. When setting it via gnome-tweak-tool or dconf-editor, it grows again to 1.1875 which makes all fonts noticeably bigger than normal. This happens with other input too, when inserting 0.5 it will grow to 0.59. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-settings-daemon 3.18.2-0ubuntu3 Uname: Linux 4.2.0-040200rc3-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 13 10:32:11 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-06-06 (341 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to xenial on 2016-05-12 (0 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1581377 Title: text-scaling-factor changes from 1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1581377/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1570701] [NEW] suspend on critical battery state can be prevented by applications
Public bug reported: Some applications prevent the computer from going to suspend mode (applications that display video, eg. chromium, opera, openshot) because they assume it is in the user's interest to keep the screen on even when inactive. This is most times helpful and saves the user from having to move a finger. But on low battery power, the user's inactivity could also be due to absence or sleep, and keeping the computer on until the power is 0.000% causes more damage than it serves the user's interest: - battery drain over time - data loss We can not rely on that every application implements sophisticated power management in the user's interest and has no malicious intentions. It is crucial that the operating system still reserves to have the last word in resource and power management. Steps to reproduce: 1. Watch a video in Opera (36) in full screen 2. Fall asleep 3. After some hours, the computer is either still on (with battery <3%) or already off Expected behavior: When not connected to an external power source and battery has low power (<30%), the usual procedure for suspend is still applied: 1. Notification on inactivity 2. Suspend There may be a way to configure this manually, but I think due to the implications of hardware drain and data loss Ubuntu should come with a reasonable default that serves the interests of general, unconscious users. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-power-manager 3.16.1-1ubuntu1 Uname: Linux 4.2.0-040200rc3-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 15 07:49:47 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-06-06 (313 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) 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 wily -- 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/1570701 Title: suspend on critical battery state can be prevented by applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1570701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1534645] [NEW] Cannot easily preserve a keyring to be only unlocked manually
Public bug reported: Assume you want to create a keyring for secrets that you only need rarely and thus want to access only on demand (not unlock on every login session). Whenever you access/unlock the keyring for the first, second, etc. time, the "Unlock keyring" dialog asks for the password and has a preselected checkbox "Automatically unlock this keyring whenever I'm logged in". This is however not the current setting for this keyring, so it constitutes a change of a setting, which counteracts the (likely) intention of the user. It is to easily to type the password and hit enter, thereby changing this keyring to an automatically unlocked one, and this risk happens repeatedly everytime you unlock it. In case you forgot to uncheck the checkbox, the only way to restore the original setting is hidden (not in keyring → properties, but only by setting a new password). A security-focused application should also not have defaults that tend to decrease security in favor of usability. Having the checkbox preselected gains less extra usability (for the case the user wants to change the keyring to be automatically unlocked: 1 click saved) than that it decreases usability (in case the user wants to keep the keyring manual: 1 click everytime to unselect it). A possible fix is to not preselect the checkbox. version 3.10.2 in Ubuntu 14.04 as well as in the version in Ubuntu 15.10 ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1534645 Title: Cannot easily preserve a keyring to be only unlocked manually To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1534645/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1416084] [NEW] evince opens documents in tiny windows
Public bug reported: When opening a document in evince, it usually used to open in a reasonable window size (I don't know, maybe last used size). However many document now open in an evince window that is as small as possible (like 20px) and requires upscaling every time. Sometimes, the document window starts to reduce its size until it hits the minimum size limit. This could be related to using a high-dpi screen (=scaling-factor set to 2.0). It could be related to bug #1299054. Ubuntu 14.10 Evince 3.14.1-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: evince 3.14.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 29 20:54:35 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-13 (16 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1416084 Title: evince opens documents in tiny windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1416084/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1396626] [NEW] print dialog font selection scrolled to end
Public bug reported: When printing a gedit (plain text) document, it is possible to configure which font is used for printing. When you click on a font button to open the font selector dialog, and type into the search field, the filtered font list is scrolled to the last list item. As a result, the most general font (Arial or Ubuntu) are with high probability hidden from view, and only more specialized fonts (Arial Bold, Arial Bold Italic) are shown in the visible scroll area. The expected behavior is that scroll area defaults to scrolled to top, which users are used to from other applications. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gedit 3.10.4-0ubuntu6 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 26 15:02:10 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (296 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) SourcePackage: gedit UpgradeStatus: Upgraded to utopic on 2014-11-04 (21 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages utopic ** Attachment added: screenshot https://bugs.launchpad.net/bugs/1396626/+attachment/4269012/+files/print_font_selection.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/1396626 Title: print dialog font selection scrolled to end To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1396626/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1380051] [NEW] characters in svg images wiggle
Public bug reported: When zooming an SVG image that contains texts, the positions of characters wiggle. The characters move sidewards closer together or farer away, as if the kerning would be different at every zoom level. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 11 12:51:15 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (250 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: video showing the issue https://bugs.launchpad.net/bugs/1380051/+attachment/4231424/+files/eog-svg-text.mp4 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1380051 Title: characters in svg images wiggle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1380051/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 564072] Re: DPI is not recognized by UBUNTU, so fonts, icons and the whole system is too small
Since this bug is labeled as gtk+2.0, I'd be interested to see also work continued on the gtk+2.0 toolkit. By manually editing gtk+2.0 themes, one can at least double some elements' dimensions and it seems not to break the layout of applications (of course such a theme derivative is then specifically targeted for dpi). So there is definitely something that can be achieved by default, and at a lower level (in the theme engine or even toolkit). Gtk+2.0 is far from disappearing (with distributions pertinaciously sticking to it, as well as all non-native toolkits like java, qt, vcl, xul basing there themes on it) and users will have to deal with it for years. Because of that, better dpi support —be it only partial— is wishable. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/564072 Title: DPI is not recognized by UBUNTU, so fonts, icons and the whole system is too small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/564072/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1318847] [NEW] shotwell shows incorrect time
Public bug reported: Shotwell shows a photo being shot at 11:11 although the original EXIF data give the time as 23:11. By default, the dconf key org.yorba.shotwell.preferences.ui.use-24-hour-time was set to false (…should use AM/PM notation). However it displays the time without AM/PM (at least under German locale). When enabling the dconf key, it still does not use the 24 hour format. This is in so far a problem that the 12 hour format is (at least without Anglo-Saxon AM/PM) incorrect. Preferably Shotwell should make use of the system-wide setting for the 12/24 hour format, which is automatically derived from the localization. For comparison see the documentation for com.canonical.indicator.datetime.time-format=locale-default ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: shotwell 0.18.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 13 01:13:24 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (99 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) SourcePackage: shotwell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- 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/1318847 Title: shotwell shows incorrect time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1318847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287917] [NEW] help content is not rendered to device-pixels on high-dpi screen
Public bug reported: If the global scaling factor is set to something different from 1 on a high-dpi screen, pdfs look blurry because they are rendered to UI units instead of device pixels. org.gnome.desktop.interface.scaling-factor = 2 As I've heard the used setting for the scaling factor might change. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: yelp 3.10.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 4 22:11:28 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (30 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: yelp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: yelp-high-dpi.png https://bugs.launchpad.net/bugs/1287917/+attachment/4007347/+files/yelp-high-dpi.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1287917 Title: help content is not rendered to device-pixels on high-dpi screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1287917/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287915] [NEW] pdf not rendered to device pixels on high-dpi screen
Public bug reported: If the global scaling factor is set to something different from 1 on a high-dpi screen, pdfs look blurry because they are rendered to UI units instead of device pixels. This renders the main advantage of higher- resolution screens (sharp vector fonts/graphics) useless for the moment. org.gnome.desktop.interface.scaling-factor = 2 As I've heard the used setting for the scaling factor might change. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 4 22:02:23 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (30 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) KernLog: SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: evince-high-dpi.png https://bugs.launchpad.net/bugs/1287915/+attachment/4007333/+files/evince-high-dpi.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1287915 Title: pdf not rendered to device pixels on high-dpi screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1287915/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1278098] [NEW] keyboard settings dialog too wide
Public bug reported: The gnome-control-center dialog is not resizable and automatically adjusts to the size of the currently viewed category. The keyboard settings / shortcuts makes the dialog tooo wide, because a translation string does not wrap lines. Make sure that all texts can wrap if they need to. gnome-control-center 14.04.2, German ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: keyboard settings, shortcuts https://bugs.launchpad.net/bugs/1278098/+attachment/3974834/+files/keyboard-settings-too-wide.png -- 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/1278098 Title: keyboard settings dialog too wide To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1278098/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1211937] Re: Nautilus leaks memory right after system start
This is a serious issue because it can happen at unpredictable times, and the memory leak runs with enormous speed. The system locks up so much that I had to hard reboot several times which is not good and can do damage to files. As far as I found out, the issue happens when nautilus tries to generate a thumbnail of a specific file (or a symlink of such a file) that is laying in the Desktop folder. When the file is in another location, nautilus still fails to create a thumbnail but doesn't leak memory. Thumbnail generation should be able to fail (with appropriate error/exception handling) and ignore failed files without impacting the system. ** Attachment added: Zip archive containing a file that causes issues with thumbnailing when it is located in the Desktop folder. https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1211937/+attachment/3778593/+files/file.zip -- 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/1211937 Title: Nautilus leaks memory right after system start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1211937/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1211937] Re: Nautilus leaks memory right after system start
I had expected ubuntu-bug adds more detailed/valuable information about the bug. If there is more info needed, I could reproduce it and give what ever info requested. This was after a fresh install of Ubuntu, but with old user configuration imported. Turning of Nautilus to manage the desktop does indeed workaround the issue, although it shouldn't happen at all. In any case I see this not only as a problem in this nautilus build, but also in resource/RAM management in the OS: A process that requires more RAM than can be afforded to maintain the system's responsiveness should be halted or killed. -- 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/1211937 Title: Nautilus leaks memory right after system start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1211937/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1211937] [NEW] Nautilus leaks memory right after system start
Public bug reported: Directly after logging in, nautilus starts to take more memory with a speed of ~4 MB/s. After 10-20 minutes the system freezes so extremely that it doesn't respond to any input (alt+f1, reisub). This could be caused by something related to the desktop since nautilus is used to render the desktop. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic i686 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 Date: Tue Aug 13 20:52:16 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'640x750+0+24' b'org.gnome.nautilus.window-state' b'sidebar-width' b'152' InstallationDate: Installed on 2013-08-12 (1 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring -- 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/1211937 Title: Nautilus leaks memory right after system start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1211937/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1194683] [NEW] totem leaks memory when playing ogv file
Public bug reported: When playing an ogv file generated from pitivi, Totem leaked around 800-1000MB RAM. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libgstreamer0.10-0 0.10.36-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Wed Jun 26 01:07:29 2013 MarkForUpload: True SourcePackage: gstreamer0.10 UpgradeStatus: Upgraded to raring on 2013-04-26 (60 days ago) ** Affects: gstreamer0.10 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug gnome3-ppa i386 raring third-party-packages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1194683 Title: totem leaks memory when playing ogv file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1194683/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1094971] [NEW] pairing timeout aborts short after first failed try
Public bug reported: After the first try of pairing the Ubuntu notebook with a bluetooth device (phone) failed (phone not ready or pin mistyped), every following try aborts immediately after less than a second (as if the timeout was suddenly shorter). There is no time anymore to read or even transfer the pin. As a work-around I can reboot and connect with the first try which has a normal several-seconds time-out (but could be longer as well). Of course it would be preferable without the need to reboot. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-bluetooth 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic i686 ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 Date: Tue Jan 1 01:15:28 2013 MarkForUpload: True SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-bluetooth (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1094971 Title: pairing timeout aborts short after first failed try To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1094971/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1094517] [NEW] can not add/replace files into sub folder
Public bug reported: I can not add files using dragdrop to an existing zip-archive opened in file-roller. 1. You have a zip file archive.zip which contains a sub-folder. 2. Open the zip file in file-roller. 3. Drag a file from the file manager into the root of the archive. This should be successful. 4. Navigate into the sub-folder. 5. Drag a file from the file manager into the sub-folder. A message pops up: ~An error occured when adding a file to the archive This is similar to bugs +511495 and +181975, but neither the location of the archive nor the added file contain non-ASCII characters or symlinks or network locations (all local). The file extension is zip although it used to work with changed extension. This is very annoying because the more common case is to add/update a file in a sub folder and as work-around I would have to unzip and re-zip again without confusing files and then change the file extension. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: file-roller 3.6.1.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic i686 ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 Date: Sat Dec 29 19:21:45 2012 MarkForUpload: True SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1094517 Title: can not add/replace files into sub folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1094517/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1093759] [NEW] transfer permissions to contained folders does nothing
Public bug reported: I ran nautilus as root (gksudo) in order to copy another user's .gconf folder, which then got the ownership of root. In properties of the .gconf folder, I corrected the permissions and clicked the button to transfer them to all contained files/folders. There was no indication that the process takes time, and the ownership of the contained files/folders was not changed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic i686 ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 Date: Wed Dec 26 09:51:42 2012 GsettingsChanges: MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity -- 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/1093759 Title: transfer permissions to contained folders does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1093759/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 991085] Re: application specific details prompt offers too limited options
This crash happens almost daily and it is quite disturbing to see how apport has been sending (since then) maybe 50-100 worthless bug reports. I would like to help fixing it, but apport does not let me add correct information. If this can't be fixed in totem, because the bug reports can't get through, I'm seriously thinking about uninstalling totem. -- 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/991085 Title: application specific details prompt offers too limited options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/991085/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1058736] [NEW] Benchmark window preselects write test
Public bug reported: Ubuntu 12.10beta2 gnome-disk-utility 3.6.0-0ubuntu1 The Benchmark window contains a rather unobvious checkbox for a write test which is preselected. Since this test is destructive, it should not be preselected on drives that contain partitions or data, and it should be disabled on the drive where the root directory / is located. ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1058736 Title: Benchmark window preselects write test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1058736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1058736] Re: Benchmark window preselects write test
** Attachment added: gnome-disks_write-benchmark.png https://bugs.launchpad.net/bugs/1058736/+attachment/3355993/+files/gnome-disks_write-benchmark.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1058736 Title: Benchmark window preselects write test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1058736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1046177] Re: too many notifications for disk failure warnings
** Attachment added: Dozens of dialogs on top of each other (see the dark black shadow). https://bugs.launchpad.net/bugs/1046177/+attachment/3293450/+files/palimpsest_disk_failure_warning.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1046177 Title: too many notifications for disk failure warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1046177/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1046177] [NEW] too many notifications for disk failure warnings
Public bug reported: When I boot up and there is a disk failure warning, it bombards me with a new dialog every 2 seconds. If I'm not fast enough clicking the dialog away, I end up with dozens if not hundreds of disk failure warning dialogs. This is by far too much in too short time for users to respond to. Expected behavior: If a dialog is already there, it is not necessary to open an identical one. Ubuntu 12.04 gnome-disk-utility 3.0.2-2ubuntu7 ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1046177 Title: too many notifications for disk failure warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1046177/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 414107] Re: Palimpsest GUI impossible to use on small screen
This is still an issue with certain parts of the UI (sorry for adding here, bug reporting seems disabled). The text string for disk failure warning doesn't break lines and forces the dialog to be (estimated) 1500px wide (on a 1280px screen). ** Attachment added: Smart values dialog. Note that the dialog's upper panel has two columns, one of which is left outside of the screen. https://bugs.launchpad.net/gnome-disk-utility/+bug/414107/+attachment/3282783/+files/Bildschirmfoto%20vom%202012-08-29%2023%3A59%3A04.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/414107 Title: Palimpsest GUI impossible to use on small screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/414107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 920014] [NEW] gedit line select doesn't consider automatic word wrapping
Public bug reported: When automatic word wrapping is enabled and you select a line (triple-click or press Pos1+shift+End), gedit selects only one displayed line segment and not the complete line until the end-of-line marker. It leaves the wrapped segments of the line unselected and unaffected by whatever action you do with the selection. You easily end up with not-working code. Ubuntu Oneric Ocelot 11.10 gedit - Version 3.2.3 ** Affects: gedit (Ubuntu) Importance: Undecided Status: New -- 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/920014 Title: gedit line select doesn't consider automatic word wrapping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/920014/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
