[Bug 990965] Re: unexpected right click behavior in nautilus
I still hate it :( Is there a way to get the old behaviour back? -- 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/990965 Title: unexpected right click behavior in nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/990965/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 878739] Re: terminal scrolls up when resized taller
I have the same problem, I believe. I'm not using Unity but gnome-shell in fallback mode. When I'm resizing my terminal, it will often scroll all the way up so that I have to type something to get my screen back in the view. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/878739 Title: terminal scrolls up when resized taller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/878739/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 422012] Re: Protected files hidden by Trash
As far as I understand (unfortunately, I can't find any documentation on this) files that are deleted from the trash are first moved to expunged (because moving files is fast), and then are slowly deleted from expunged (slowly because deleting a lot of files takes time and doing it too fast could slow down the whole computer). This means that having files in expunged is not necessarily a problem, as long as these files get deleted over time. If there are files in expunged that do not vanish over time, the output from the following command could probably help the maintainers in figuring this bug out: LANG=C ls -l ~/.local/share/Trash/expunged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/422012 Title: Protected files hidden by Trash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/422012/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 795475] Re: [iOS5 devices do not work] Unhandled lockdown error (-4)
@Bobby: I downgraded to lucid to escape Unity and Gnome3. Now that it works, I won't risk another upgrade in the foreseeable future, sorry :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/795475 Title: [iOS5 devices do not work] Unhandled lockdown error (-4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/795475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 795475] Re: [iOS5 devices do not work] Unhandled lockdown error (-4)
@pitti: I can confirm that the proposed update to 0.9.7-1ubuntu1.2 on lucid fixes this issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/795475 Title: [iOS5 devices do not work] Unhandled lockdown error (-4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/795475/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 197288] Re: New windows are put in the background when a window has Always on Top set
** Summary changed: - [hardy] new windows are put in background when a window has always on top set + New windows are put in the background when a window has Always on Top set -- New windows are put in the background when a window has Always on Top set https://bugs.launchpad.net/bugs/197288 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 314545] Re: gnome-screensaver bad password timeout
This just happend to me; the last time was a few month ago. I waited about 5-10 minutes, then I could type in my password again. -- gnome-screensaver bad password timeout https://bugs.launchpad.net/bugs/314545 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 269934] Re: application icons are faded and hard to distinguish
I've posted a patch on the GNOME bugtracker, and I also created a PPA that contains the patched package: https://launchpad.net/~martin.von.wittich/+archive/libwnck-nodimming Add the software source ppa:martin.von.wittich/libwnck-nodimming to your computer and run sudo apt-key adv --keyserver subkeys.pgp.net --recv-keys C26F50B5 ; then start update-manager, check for updates and install them. After you relogin, the icons should no longer be greyed out. This will of course be reverted as soon as Ubuntu releases another update for libwnck, but I'll try to keep at it and patch the updates too. -- application icons are faded and hard to distinguish https://bugs.launchpad.net/bugs/269934 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 395302] Re: kills X session during upgrade
Seinding HUP to gdm does not terminate it. OK, you're right, I tried it :) It rather sounds like d-bus crashed during the upgrade Seems you are right again: martin /var/log # zgrep dbus syslog.1 Oct 14 19:57:29 martin dbus-daemon: Reloaded configuration [...] Oct 14 20:05:20 martin dbus-daemon: Reloaded configuration Oct 14 20:11:52 martin avahi-daemon[32252]: dbus_bus_get_private(): Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory [...] Oct 14 20:11:52 martin init: dbus main process ended, respawning Oct 14 20:12:38 martin init: dbus main process ended, respawning Oct 14 20:12:50 martin init: dbus main process ended, respawning Oct 14 20:12:50 martin init: dbus main process (5278) killed by KILL signal Oct 14 20:12:50 martin init: dbus main process ended, respawning Oct 14 20:12:50 martin init: dbus main process (5352) terminated with status 1 Oct 14 20:12:50 martin init: dbus main process ended, respawning Oct 14 20:12:50 martin init: Unable to connect to the system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused I'll attach the complete syslog and apt/term.log. Can you reproduce this somehow? I have no idea how. I tried to run a few dbus related postinsts, but that caused nothing. Can you please check afterwards with status dbus and status hal whether they are running or stopped? When it happens again, I'll try to login via ssh, and post the results. -- kills X session during upgrade https://bugs.launchpad.net/bugs/395302 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 395302] Re: kills X session during upgrade
** Attachment added: syslog.1.gz http://launchpadlibrarian.net/33750898/syslog.1.gz -- kills X session during upgrade https://bugs.launchpad.net/bugs/395302 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 395302] Re: kills X session during upgrade
** Attachment added: term.log.gz http://launchpadlibrarian.net/33750922/term.log.gz -- kills X session during upgrade https://bugs.launchpad.net/bugs/395302 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 395302] Re: kills X session during upgrade
Hmm, I'm still experiencing gdm restarts during some upgrades; the last
one was today, when upgrading from gdm 2.28.0-0ubuntu14 to gdm
2.28.0-0ubuntu17. I believe the HUP from the postinst file could be
causing this, but as I don't want to reboot my computer again, I shrink
from trying it:
PID=$(status gdm 2/dev/null | awk '/[0-9]$/ { print $NF }')
[ -z $PID ] || kill -HUP $PID
What makes this even worse is that after gdm is restarted, neither the
mouse nor the keyboard are working anymore. The only escape is rebooting
the computer via Alt+SysRq+RSEIUB.
--
kills X session during upgrade
https://bugs.launchpad.net/bugs/395302
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 197288] Re: [hardy] new windows are put in background when a window has always on top set
Workaround does not seem to work for me (jaunty). -- [hardy] new windows are put in background when a window has always on top set https://bugs.launchpad.net/bugs/197288 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 267263] Re: seahorse-applet crashed with SIGSEGV in panel_applet_factory_main_closure()
Strange. The version I fixed myself worked, but the new upstream version crashes again. I've already purged seahorse-plugins and installed it again, that didn't help. Can anyone confirm this? Unfortunately, apport won't report this crash, all I see is segfaults in dmesg: [ 3378.789276] seahorse-applet[10703]: segfault at 80 ip b7fa7b50 sp bfcdcec0 error 4 in libpanel-applet-2.so.0.2.44[b7fa2000+d000] [ 3948.368733] padevchooser[6689]: segfault at 65726f ip b785d5d2 sp bff93ed0 error 4 in libgobject-2.0.so.0.1800.0[b7834000+3c000] [ 4331.552415] seahorse-applet[11172]: segfault at 80 ip b7fa8b50 sp bfade4c0 error 4 in libpanel-applet-2.so.0.2.44[b7fa3000+d000] [ 4349.241463] seahorse-applet[11178]: segfault at 80 ip b7f3bb50 sp bfa70c50 error 4 in libpanel-applet-2.so.0.2.44[b7f36000+d000] [ 4507.854260] seahorse-applet[11252]: segfault at 80 ip b7fc3b50 sp bfaf8ce0 error 4 in libpanel-applet-2.so.0.2.44[b7fbe000+d000] -- seahorse-applet crashed with SIGSEGV in panel_applet_factory_main_closure() https://bugs.launchpad.net/bugs/267263 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 267263] Re: seahorse-applet crashed with SIGSEGV in panel_applet_factory_main_closure()
Oh, OK. I thought the fix would have already made it in the most recent release. My bad. Don't worry on packaging it, I have restored the version I fixed myself and it's working for me. -- seahorse-applet crashed with SIGSEGV in panel_applet_factory_main_closure() https://bugs.launchpad.net/bugs/267263 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 267263] Re: seahorse-applet crashed with SIGSEGV in panel_applet_factory_main_closure()
The bug has been marked as a duplicate; the real bug is here: http://bugzilla.gnome.org/show_bug.cgi?id=549833 . Sounds like there's just a single line missing, but they haven't fixed it yet. -- seahorse-applet crashed with SIGSEGV in panel_applet_factory_main_closure() https://bugs.launchpad.net/bugs/267263 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 267263] Re: seahorse-applet crashed with SIGSEGV in panel_applet_factory_main_closure()
OK, I've submitted a patch upstream that hopefully fixes the issue without breaking anything else. -- seahorse-applet crashed with SIGSEGV in panel_applet_factory_main_closure() https://bugs.launchpad.net/bugs/267263 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 267263] Re: seahorse-applet crashed with SIGSEGV in panel_applet_factory_main_closure()
Fixed upstream. -- seahorse-applet crashed with SIGSEGV in panel_applet_factory_main_closure() https://bugs.launchpad.net/bugs/267263 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 267263] Re: seahorse-applet crashed with SIGSEGV in panel_applet_factory_main_closure()
Oh well, too late :) -- seahorse-applet crashed with SIGSEGV in panel_applet_factory_main_closure() https://bugs.launchpad.net/bugs/267263 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 59616] Re: keyboard not working after logging in via gdm due toslow keys feature being accidentally enabled
I just tried it again, and I think I've found the underlying issue. As I disabled the option 'Keyboard Preferences' - 'Allow to turn accessibility features on and off from the keyboard', I had to reactivate this to test it. As I now know, the required action is to hold SHIFT for 8 seconds to toggle the 'Slow Keys' feature, and I did just that. After 8 seconds, a dialog popped up, asking me Do you want to activate Slow Keys? (possible answers: 'Don't activate', 'Activate') - just as expected. What I did not expect though was this: the feature gets enabled as soon as the dialog pops up; only when you hit 'Don't activate', it will get disabled again. And to make this even worse: the dialog tends to remain hidden behind maximized windows. In the beginning, it would pop up over my maximized Firefox window, but after I did this several times, it will only pop under the Firefox window. So if I didn't know about this, the 'slow keys' feature would now be enabled, I wouldn't know why. If I would now minimize all windows, I would see that dialog; but most users (as I did back then I guess) will freak out and e.g. try to re-login or to reboot the computer, leading to a permanently enabled 'slow keys' feature. My suggested fix: disable 'Allow to turn accessibility features on and off from the keyboard' by default (I don't think there are really people relying on this), and fix that dialog so it won't enable the 'slow keys' feature until the user has clicked on 'Activate'. Additionally, the focused button in that dialog should be 'Don't activate' (why focus the 'Help' button?!), and a warning like WARNING: if you don't know what the Slow Keys feature is, don't enable it! You will have problems with typing when you activate it! would be nice. BTW - this is a duplicate: https://bugs.launchpad.net/ubuntu/+bug/41427 this could be a duplicate: https://bugs.launchpad.net/ubuntu/+bug/195805 (I tested it, you also need to hold CTRL+ALT+F1 for a moment when you want to switch consoles with slow keys enabled. I won't test CTRL+ALT+BACKSPACE though ;)) -- keyboard not working after logging in via gdm due toslow keys feature being accidentally enabled https://bugs.launchpad.net/bugs/59616 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 187127] Re: ssh always asks to unlock private key with no password set
My SSH key does have a password but nonetheless I dislike this window, because it interrupts my usual routine: $ ssh somehost ssh asks me for my passphrase, I realise that I haven't added the key to the ssh-agent yet. I press STRG+C... $ ssh-add I enter my passphrase into the agent $ ssh somehost ssh gets the key from the agent I also noticed that it seems rather random whether the dialog gets the focus; sometimes the focus just remains on the terminal window, potentially leading users to typing their passphrases in plain text into the terminal window. For me it means that hitting ESC will do nothing, and I have to use the mouse to close the window. That is just plain wrong: I'm forced to use the mouse to close a graphical dialog that pops up while I'm working in the terminal. I think the possibility to store the passphrase in seahorse is generally a nice feature, but it should not pop up a graphical window in the terminal. -- ssh always asks to unlock private key with no password set https://bugs.launchpad.net/bugs/187127 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 59616] Re: keyboard not working after logging in via gdm
I just had the same problem and I can confirm that the slow keys feature was the reason for this. As the option Allow to turn on accessibility features on and off from the keyboard was set, I guess I accidentally enabled it with some obscure key combination (the help doesn't state which key combination would enable slow keys, though). It's not a bug, it's a feature :) Seeing the amount of confusion this has created, there is apparently a need for some kind of notification bubble that informs users that are desperately hitting keys about this. -- keyboard not working after logging in via gdm https://bugs.launchpad.net/bugs/59616 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
