[Bug 1792085] Re: MTP not working/very slow on Bionic
How is this not fixed a year later? Whatever people are working on for the next release that they feel is sexy I hate it. Instead please fix bugs which make the existing system unusable. Then you will be my hero. -- 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/1792085 Title: MTP not working/very slow on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 882307] Re: [list-view] After copying text from a rename entry, file copy menus items are broken
Going on two years and this bug isn't fixed in Ubuntu 12.04.2 LTS \n \l Linux deans2068 3.5.0-36-generic #57~precise1-Ubuntu SMP Thu Jun 20 18:21:09 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Or course this could be a new bug with paste grayed out but a new bug report was entered and was marked as a duplicate of this one (see https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/949468) so others seem to think it is the same root problem. If someone wants to release a new feature I would highly suggest quality control. When copy/paste doesn't work it is hard to tell people how great this product is. -- 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/882307 Title: [list-view] After copying text from a rename entry, file copy menus items are broken To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-gtk/+bug/882307/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1193850] [NEW] gnome-screensaver exposes sensitive data
*** This bug is a security vulnerability *** Public security bug reported: People depend heavily on the lock screen (rightfully or wrongfully) to prevent others from seeing sensitive data. gnome-screensaver can easily expose this sensitive data. Example: During day: 1. Network boot Ubuntu into GUI 2. Open sensitive document 3. CTRL-ALT-F[1-6] and use a TTY 4. Logout of TTY and attend meeting 5. Go home an hour later At this point a user has a reasonable expectation of his or her sensitive document being secure believing a password (or physical access to server) will be needed to see the sensitive information. At night: 6. Record screen with mobile 7. CTRL-ALT-F7 (the document will briefly be displayed before the lock screen) 8. CTRL-ALT-F[1-6] back to the original TTY to hide your tracks 9. Go frame by frame through the video to retrieve the sensitive information I wouldn't call this an enhancement because I spoke to several users and ALL of them had the expectation their data would not be visible. People were especially sensitive to the reading of private chat sessions. Users didn't expect just anyone could go from cubical to cubical at night secretly exposing screens. Whenever a user has a screen lock the locking application needs to ensure contents of the screen won't be visible after the lockout time. If it is really so hard to clear the contents of the screen then turn off output of the video card when the user hits CTRL-ALT-F7 until the sensitive data is gone. cat /etc/issue Ubuntu 12.04.2 LTS \n \l Package: gnome-screensaver Priority: optional Section: gnome Installed-Size: 412 Maintainer: Ubuntu Desktop Team ubuntu-desk...@lists.ubuntu.com Original-Maintainer: Guilherme de S. Pastore gpast...@debian.org Architecture: amd64 Version: 3.4.1-0ubuntu1 Priority: optional Section: universe/gnome Installed-Size: 51 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Original-Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org Architecture: amd64 Source: meta-gnome3 Version: 1:3.0+6ubuntu3 ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1193850 Title: gnome-screensaver exposes sensitive data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1193850/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1193163] [NEW] /etc/shadow owned by root:root after 8.04.x--10.04.x--12.04.2 LTS upgrade
Public bug reported: I upgraded from 8.04.x--10.04.x--12.04.2 LTS, removed Unity (and friends), installed Gnome and found /etc/shadow owned by root:root (though I don't know exactly how it came to be) This causes a problem because the lock screen will tell you that your correct password is incorrect. The lock screen shouldn't tell you that your correct password is incorrect (confusing lies). Instead it should inform you /etc/shadow is owned by other-than root:shadow (helpful truth). ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1193163 Title: /etc/shadow owned by root:root after 8.04.x--10.04.x--12.04.2 LTS upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1193163/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 934618] Re: gdm crashes at startup when autologin enabled: gdm-simple-slave[1605]: CRITICAL: gdm_session_direct_get_username: assertion `session != NULL' failed
This bug is still going strong after more than a year. CRITICAL: gdm_session_direct_get_username: assertion `session != NULL' failed cat /etc/issue: Ubuntu 12.04.2 LTS \n \l uname -r: 3.2.0-48-generic Architecture: i386 gdm Version: 3.0.4-0ubuntu15.1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/934618 Title: gdm crashes at startup when autologin enabled: gdm-simple-slave[1605]: CRITICAL: gdm_session_direct_get_username: assertion `session != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/934618/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 350174] Re: metacity process uses 100% CPU
For me metacity uses 100% CPU because Wireless Network Authentication Required boxes appear every few minutes? and never go away (unless manually closed). Eventually there are hundreds? of them and metacity uses 100% CPU dealing with them. You might not notice them if they appear on a different virtual desktop than the one you are using or if the bar showing your currently running applications is hidden or if the number of windows is so large they only appear a few pixels wide in the task bar or if you accessing your system via ssh or any other such reason. In my mind this is a metacity bug but I am sure others would argue with me that what I want is a feature enhancement. Why doesn't metacity restrict its CPU utilization on a per-client bases so that a single misbehaving application cannot bring down the system? Misbehaving applications are AN EXPECTED behavior. If there was some [high] burstable quota this wouldn't be an issue. If the quota is met and the application is throttled an indicator applet could allow the user to change/remove the quota for the application. cat /etc/issue Ubuntu 12.04.2 LTS \n \l -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/350174 Title: metacity process uses 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/350174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 500780] Re: Super (Windows Key) alone in keyboard shortcuts now broken.
Greetings, I have just finished executing the following test: a) performed a fresh install and did all the upgrades for 10.04 LTS using ISO ubuntu-10.04-desktop-amd64.iso with MD5 3e0f72becd63cad79bf784ac2b34b448 b) started gnome-control-center c) clicked on Keyboard Shortcuts d) added a new Custom Shortcut e) clicked within in the shortcut column to associate a keystroke with the shortcut f) attempted to set MOD4/Super_L/Windows Key as the shortcut keystroke g) test FAILS Thank you very much for taking the time to address this issue. -- Super (Windows Key) alone in keyboard shortcuts now broken. https://bugs.launchpad.net/bugs/500780 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 500747] Re: gdmsetup errors : key not found
I am also getting key not found errors. I did a fresh install of 9.10
i386 a few hours ago. Although I do not know for certain the problems
are related must inform you that I removed many packages which I
believed were not needed as soon as the Ubuntu installer completed. I
then ssh -Xed in and then ran DISPLAY=:0.0 gdmsetup to turn on
autologin but found I could not. Perhaps I somehow removed some needed
package for gdmsetup but if so gdmsetup should have had a dependency
of the package to alert me! gdmsetup also should have had a
dependency on the needed package(s) so that I could simply reinstall
gdmsetup and the needed packages would come along with it. I will be
happy to provide all the logs/etc that you request. Below is the
gdmsetup output:
de...@ubuntu:~$ DISPLAY=:0.0 gdmsetup
** (gdmsetup:3984): WARNING **: Error calling
GetValue('daemon/TimedLoginEnable'): Key not found
** (gdmsetup:3984): WARNING **: Error calling
GetValue('daemon/TimedLoginDelay'): Key not found
** (gdmsetup:3984): DEBUG: init delay=30
** (gdmsetup:3984): DEBUG: GdmUserManager: skipping shell /bin/false
** (gdmsetup:3984): DEBUG: GdmUserManager: Found current seat:
/org/freedesktop/ConsoleKit/Seat7
** (gdmsetup:3984): DEBUG: GdmUserManager: running 'ck-history --frequent
--seat='Seat7' --session-type='''
** (gdmsetup:3984): DEBUG: GdmUserManager: explicitly skipping user: nobody
** (gdmsetup:3984): DEBUG: GdmUserManager: user icon changed
** (gdmsetup:3984): DEBUG: adding monitor for '/home/deans/.face'
** (gdmsetup:3984): DEBUG: Getting list of sessions for user 1000
** (gdmsetup:3984): DEBUG: Found 3 sessions for user deans
** (gdmsetup:3984): DEBUG: GdmUserManager: not adding session without a x11
display: /org/freedesktop/ConsoleKit/Session8
** (gdmsetup:3984): DEBUG: GdmUserManager: not adding session on other seat:
/org/freedesktop/ConsoleKit/Session2
** (gdmsetup:3984): DEBUG: GdmUserManager: not adding session on other seat:
/org/freedesktop/ConsoleKit/Session6
** (gdmsetup:3984): DEBUG: GdmUserManager: history output: deans1
** (gdmsetup:3984): WARNING **: Error calling
GetValue('daemon/AutomaticLoginEnable'): Key not found
** (gdmsetup:3984): WARNING **: Error calling
GetValue('daemon/TimedLoginEnable'): Key not found
** (gdmsetup:3984): WARNING **: Error calling GetValue('daemon/TimedLogin'):
Key not found
** (gdmsetup:3984): DEBUG: init user='(null)' auto=False
Thank you for your time.
--
gdmsetup errors : key not found
https://bugs.launchpad.net/bugs/500747
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 440502] Re: gdmsetup does not let me unlock
My gdmsetup unlock button doesn't function in a later version (no
password prompt at all when I click it).
#apt-cache show gdm | grep -i version
Version: 2.28.1-0ubuntu2.1
Version: 2.28.1-0ubuntu1
# DISPLAY=:0.0 gdmsetup
** (gdmsetup:3984): WARNING **: Error calling
GetValue('daemon/TimedLoginEnable'): Key not found
** (gdmsetup:3984): WARNING **: Error calling
GetValue('daemon/TimedLoginDelay'): Key not found
** (gdmsetup:3984): DEBUG: init delay=30
** (gdmsetup:3984): DEBUG: GdmUserManager: skipping shell /bin/false
** (gdmsetup:3984): DEBUG: GdmUserManager: Found current seat:
/org/freedesktop/ConsoleKit/Seat7
** (gdmsetup:3984): DEBUG: GdmUserManager: running 'ck-history --frequent
--seat='Seat7' --session-type='''
** (gdmsetup:3984): DEBUG: GdmUserManager: explicitly skipping user: nobody
** (gdmsetup:3984): DEBUG: GdmUserManager: user icon changed
** (gdmsetup:3984): DEBUG: adding monitor for '/home/deans/.face'
** (gdmsetup:3984): DEBUG: Getting list of sessions for user 1000
** (gdmsetup:3984): DEBUG: Found 3 sessions for user deans
** (gdmsetup:3984): DEBUG: GdmUserManager: not adding session without a x11
display: /org/freedesktop/ConsoleKit/Session8
** (gdmsetup:3984): DEBUG: GdmUserManager: not adding session on other seat:
/org/freedesktop/ConsoleKit/Session2
** (gdmsetup:3984): DEBUG: GdmUserManager: not adding session on other seat:
/org/freedesktop/ConsoleKit/Session6
** (gdmsetup:3984): DEBUG: GdmUserManager: history output: deans1
** (gdmsetup:3984): WARNING **: Error calling
GetValue('daemon/AutomaticLoginEnable'): Key not found
** (gdmsetup:3984): WARNING **: Error calling
GetValue('daemon/TimedLoginEnable'): Key not found
** (gdmsetup:3984): WARNING **: Error calling GetValue('daemon/TimedLogin'):
Key not found
** (gdmsetup:3984): DEBUG: init user='(null)' auto=False
--
gdmsetup does not let me unlock
https://bugs.launchpad.net/bugs/440502
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 500780] [NEW] Super (Windows Key) alone in keyboard shortcuts now broken.
Public bug reported: I am unable to assign the Windows-Key (Super L) alone to an action in the Keyboard Shortcuts Application (gnome-keybinding-properties) as previously possible. I am only able to assign MOD4+? (windows key + another key). I understand there was previously a bug #12153 where people were rightly upset they couldn't assign the windows key in conjunction with another key to a shortcut. Fixing this bug appears to have created another bug whereby now it is impossible to assign the windows key alone using the gnome control panel. There is no good reason why we should lose the ability to assign an action to the windows key alone (Super L) if the user does not require any windows key combination (MOD4+?) keyboard shortcuts. Of course I am very happy using the Windows key as a modifier is fixed (thank you) but this is not an either-or situation and the old functionality is clearly broken. If you don't want to think of it as Super_L is broken then please consider this bug as MOD4+NOTHING is broken. In fact, if you think of this as MOD4+NOTHING is broken then you can have both MOD4+? keyboard shortcuts and a MOD4+NOTHING shortcut as MOD4+NOTHING is detected on key_up unlike Super_L which is detected on key_down. . lsb_release -rd Description:Ubuntu 9.10 Release:9.10 ** Affects: control-center (Ubuntu) Importance: Undecided Status: New -- Super (Windows Key) alone in keyboard shortcuts now broken. https://bugs.launchpad.net/bugs/500780 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
