I can't stand the global menu. I've switched away from unity as a result.
As a developer, I constantly have a bunch of 'layers' of windows open.
For example, I might have a terminal window open in the background, my
IDE over top of that, and finally my web browser for testing the site
I'm
Can't submit a bug using apport. It pops up and asks if we want to send
an error report--clicking yes/continue/whatever gives a dialog saying
the error has already been reported. It doesn't behave like 'normal' by
opening a browser window to the existing bug report, it just quits.
--
You
(also, attempting to change the bug to reference 'unity' instead of
'glib' is an exercise in futility. Searching for 'unity' returns an
error that there are too many results. Trying unity-panel-service,
unity-panel, unity panel, unity app, etc... returns no projects found.)
** Package changed:
Public bug reported:
Just upgraded my workstation to 11.10 for testing. It regularly goes to
(sleep?) after about 30ish minutes.
The screen is still on with a blinking cursor displayed in the upper left. The
power and reset button lights on my workstation flash like it's in sleep mode.
This is fixed for me under 10.04 and 10.10.
** Changed in: gnome-keyring (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
https://bugs.launchpad.net/bugs/521253
Upgraded from 10.04 to 10.10 and got nailed by this bug.
** Tags added: regression-proposed
--
seahorse agent doesn't work with gnupg smartcard readers
https://bugs.launchpad.net/bugs/185563
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
Yes, I am seeing it on Karmic. I do not see it on my test laptop
running Lucid--but I never ran into the issue on Karmic on that machine.
I can reproduce the crash every time now on my home laptop running
Karmic.
--
Crash when trying to connect to ~20 hosts via SSH simultaneously
Public bug reported:
Binary package hint: gnome-screensaver
On my HP Mini netbook testing Lucid, gnome-screensaver asks for a password like
it normally should.
After entering the password and hitting enter, it says 'Checking...' and hangs.
I gave it an hour, then I switched to the console and
Public bug reported:
Binary package hint: gnome-keyring
I use cssh to manage multiple boxes.
It started happening rarely when I would connect to about 16 machines.
Now that I'm over 20 machines, it crashes every time.
I've had to split my cssh list in half to keep the ademon from crashing.
** Attachment added: gdb-gnome-keyring-daemon.txt
http://launchpadlibrarian.net/39133198/gdb-gnome-keyring-daemon.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/39133199/Dependencies.txt
** Attachment added: XsessionErrors.txt
This has started popping up on my laptop again pretty regularly. I will
attempt to get a backtrace...
--
Simultaneous SSH attempts cause gnome-keyring to crash: Error reading response
length from authentication socket.
https://bugs.launchpad.net/bugs/352921
You received this bug notification
Happened when I did a 'Reset and Clear'
--
gnome-terminal assert failure:
Vte:ERROR:/build/buildd/vte-0.22.0/./src/vtestream-file.h:30:_xread: assertion
failed: (fd || !len)
https://bugs.launchpad.net/bugs/435367
You received this bug notification because you are a member of Ubuntu
Desktop
Fixed for me in Jaunty.
I can lock my screen by setting the shortcut MOD4+L.
It also works correctly when connected to a Windows machine via rdesktop.
--
Cannot use Windows key in keyboard shortcuts
https://bugs.launchpad.net/bugs/12153
You received this bug notification because you are a member
For the last few days I've been running 2.26.0-0ubuntu4. It hasn't crashed
yet, and I've been hammering it.
I will try upgrading tonight when I get home and see if the issue still exists
for me.
--
Simultaneous SSH attempts cause gnome-keyring to crash: Error reading response
length from
Public bug reported:
Binary package hint: gnome-keyring
If I try to ssh to a single machine at a time, I am signed in automatically
using my ssh key.
If I try to ssh to multiple machines at the same time, I get the following
error:
Error reading response length from authentication socket.
How do I go about debugging the gnome-keyring-daemon?
I have tried killing the one that starts automatically with gnome and running
it manually from the command line, but then I run into problems with it not
setting environment variables correctly so cssh doesn't work as it should.
--
Looking through other debugging info, I found out about the .xsession-errors
file in my home dir.
Looking there, I see the following lines repeated hundreds of times:
Gnome.Keyring.KeyringException: Unknown error
at Gnome.Keyring.Ring.SendRequest (System.IO.MemoryStream stream) [0x0]
at
After doing more digging, I noticed lots of firefox processes running that
looked similar to:
/usr/lib/firefox-3.0.6/firefox -no-remote -ProfileManager http://ubuntu.com/
where ubuntu.com was any one of 20 URLs I had tried to open earlier.
I seem to recall my initial firefox session being opened
Public bug reported:
Binary package hint: gnome-terminal
I use mutt as my email client.
For any URL I receive and need to view, I usually right-click and select open
link. This usually opens firefix (if it's not running) and displays the URL.
If firefox is already running, it opens a new tab
Sebastien--if it's a duplicate bug, use the Mark as Duplicate link
near the top left of the page. (Two lines under the bug description)
and select the bug that is a duplicate. That way everyone knows which
bug is the 'master' and which bugs are the dupes. It also helps so the
subscribers of the
If the bug has already been reported, would you care to flag this as a
duplicate? I've looked for dupes of this bug but haven't found any.
I am also suffering from this problem, and my screen looks exactly like
what you see in Screenshot-2.png.
I am unable to switch from fullscreen to normal.
I
Disabling all desktop effects makes totem behave normally.
This is not the best solution, but it is a workaround.
--
Totem became stuck in fullscreen mode, but would still show windowed controls
https://bugs.launchpad.net/bugs/249219
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: gnome-terminal
In 8.04 I ran gnome-terminal with many tabs open, including one with irssi.
Irssi uses ALT-1, ALT-2, etc... to change between screens.
In Intrepid, gnome-terminal overrides those keys and assigns them to it's own
tabs.
If I hit ALT-1, I
LiveCD doesn't matter.
What matters is that upgrading a system to Gutsy caused certain settings to not
behave correctly.
But that's in the past now. Too late to fix it since we're already at 8.04.
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete = Invalid
--
synaptics
This happens to me about 75% of the time when I close evolution (either via
File-Exit or hitting the close 'X').
The difference between the link in comment 4 is that I am connecting over the
exchange/outlook web access method and not IMAP.
--
gnome-panel crashed with SIGSEGV in
I reported this almost 5 months ago. I got tired of this annoying issue and
eventually reinstalled 7.10 on my laptop. That fixed it.
It wasn't anything to do with a heavy load though--the cpufreq applet showed
things were scaled back to 25%
--
Gnome shutdown dialog takes a long time to show
I am running Gutsy and having trouble too.
Mine lets me set it--it shows up as Mod4+L in the shortcuts dialog, but the key
combo won't activate the screensaver.
If I set it to something like CTRL+ALT+L it works perfectly.
--
Cannot use Windows key in keyboard shortcuts
Meh. My Gutsy broke as well.
--
Cannot use Windows key in keyboard shortcuts
https://bugs.launchpad.net/bugs/12153
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I think I understand what Basilio is saying.
No, it's not a software problem with the x synaptics driver.
Yes, it is a bug in Gutsy that needs to be taken care of.
So it's been reassigned to the correct component that will handle the upgrade
issue.
--
synaptics touchpad won't left click, right
I had two lines in hosts set as 127.0.0.1:
127.0.0.1 localhost
127.0.0.1 mylaptop
I changed it to:
127.0.0.1 localhost mylaptop
My issues disappeared.
My issue popped up when I'd try to shutdown the box.
Go to System-Quit and it would take about 10 seconds to pop up the shutdown
dialog.
--
I started testing Gutsy a few days ago. This issue is fixed in Gutsy.
--
Cannot use Windows key in keyboard shortcuts
https://bugs.launchpad.net/bugs/12153
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs mailing
It is difficult to reproduce, but I believe I have tracked down the core issue.
The problem stopped happening very shortly after I posted the bug.
One of the network techs at the office said someone made a bad cable and they
were getting a lot of packet loss between one machine and the switch.
As
I usually run into this once or twice a month.
As soon as it pops up, I'll get it to you.
--
Evolution hangs with soup_connection_reserve and soup_connection_send_request
errors
https://bugs.launchpad.net/bugs/128985
You received this bug notification because you are a member of Ubuntu
Desktop
Public bug reported:
Binary package hint: evolution
I start evolution from the command-line and get the following until I
hit CTRL+C:
$ evolution
CalDAV Eplugin starting up ...
(evolution-2.10:6734): libsoup-CRITICAL **: soup_connection_reserve:
assertion `SOUP_IS_CONNECTION (conn)' failed
I have done a completely fresh install of Feisty on my laptop. (Compaq Presario
2100)
In keyboard preferences I set the keyboard model to Laptop/notebook Compaq
(eg. Presario) Internet Keyboard
On the layout options tab I set the Alt/Win key behavior to Super is mapped
to the win-keys (default)
Sorry--I didn't see the replies to the bug until just now. For some reason I
missed the emails.
I finally ended up reformatting the box and doing a clean install of Edgy, and
I no longer have the old screen.
I suppose this can be closed as unfounded...
--
Unlock Dialog Text Confusing
Finally fixed this on my end after reading through a few bugs.
Everyone seems to be suggesting that you remove the file .gtkrc-1.2-gnome2 and
that you paste some info into .gtkrc.mine.
The funny part is that looking in .gtkrc-1.2-gnome2 you will probably
see an incude line for .gtkrc.mine. So
This has apparently been fixed. A few weeks ago it showed back up.
--
Move to Another Workspace context menu no longer exists
https://launchpad.net/bugs/69568
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Public bug reported:
After my workspace starts to get cluttered, I usually start right-
clicking on title bars and hitting 'W' '2'. Normally that would select
the Move to Another Workspace and then select Workspace 2.
The Move to Another Workspace context menu is no longer exists. I can
Move
Public bug reported:
Go to System-Administration-Services
Error message pops up The configuration could not be loaded You are
not allowed to access the system configuration.
I am in the sudoers file.
** Affects: gnome-system-tools (Ubuntu)
Importance: Undecided
Assignee: Ubuntu
Darn. I thought I had rebooted the box. It's working now.
So apparently this is caused by an earlier version of Ubuntu (say
Dapper?) and when upgrading to Edgy the admin group isn't created?
--
Admin tools require admin group membership
https://launchpad.net/bugs/59946
--
desktop-bugs
This is fixed in edgy. (Aside from the stupid jiggling window--but
that's not really a bug, just a personal preference.)
--
Unlock dialog takes way too long on incorrect password
https://launchpad.net/bugs/44263
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
My bug was marked as a dupe of this bug. (Bug 69145)
I had a similar issue. No admin group. I apt-get dist-upgrade'd from
dapper.
After creating the admin group and adding myself, I still get the same
issue as mentioned in my bug.
Starting the services admin app gives an error:
The
Public bug reported:
Forgive me if this is a dupe. Browser crashed during a submit, but I
can't find the bug anywhere.
I'll be blunt. I hate the new dapper xscreensaver unlock dialog. It
has a few flaws that I think detract from the user experience in Ubuntu.
If I type in an incorrect
44 matches
Mail list logo
