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 mana
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
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 cou
@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.laun
@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
** 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
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, whi
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 subk
** 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
** 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
> 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-dae
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=$(s
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
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
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-a
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
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.ubun
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 Bu
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.ne
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
togg
My SSH key does have a password but nonetheless I dislike this window,
because it interrupts my usual routine:
$ ssh somehost
$ ssh-add
$ ssh somehost
I also noticed that it seems rather random whether the dialog gets the
focus; sometimes the focus just remains on the terminal window,
potentia
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 com
22 matches
Mail list logo
