Ubuntu 8.04 - confused this new user. Agree with Q.E.D - in addition
supported disc types is wrong. My writer supports +R -R +RW -RW for CD
and DVD. Have written to most of those successfully. Why does this
message always have the same disc types?
--
Confusing error message
https://bugs.launchpad
Public bug reported:
Binary package hint: gdm
while on the gdm login screen hit ctrl-alt-delete
The screen flickers a few times then a dialog comes up saying to the effect
that the starter has crash will try another
on clicking ok the screen flickers and the dialog comes back again, and
again a
*** ctrl-alt-delete SHOULD READ ctrl-alt-backspace
Is it a bug that posters cant edit (with audit trail) their own
posts
--
gdm stuck in loop if killed with ctrl-alt-delete (gutsy)
https://bugs.launchpad.net/bugs/130066
You received this bug notification because you are a member of Ubun
as mentioned in the title I'm using gutsy, I update daily so whatever
version comes with gutsy
hitting ctrl-alt-backspace while in gmd always causes the problem
did you try to replicate this yourself?
--
gdm stuck in loop if killed with ctrl-alt-delete (gutsy)
https://bugs.launchpad.net/bugs/13
Just double checked, behaviour has changed since last update
after hitting ctrl-alt-backspace wait for it to restart and hit
ctrl-alt-backspace
again
the work round has changed slightly after running
sudo /etc/init.d/gdm stop
switch to another console kill (-9) gdm as stop will probably
hang (
please upstream this I can replicate this behaviour with debian Lenny
too...
--
gdm stuck in loop if killed with ctrl-alt-delete (gutsy)
https://bugs.launchpad.net/bugs/130066
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop
You havent yet answered, have you tried to replicate this yourself?
I can replicate this with 3 different machines on Ubuntu Gutsy and
Debian sid
--
gdm stuck in loop if killed with ctrl-alt-delete (gutsy)
https://bugs.launchpad.net/bugs/130066
You received this bug notification because you are
You have been subscribed to a public bug:
this first came to light with Bug #130257
however I think this is possibly related to the window manger...
Currently my version of Nautilus is 2.19.90 (tho this can change daily
with updates so its not very useful info)
right click on say a jpg, clickin
Public bug reported:
Binary package hint: eog
opening an image is *very* slow, running eye of gnome from the
command prompt is also slow and comes up with
** (eog:6550): WARNING **: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
sec
dbus *is* running so this IS a bug either with dbus (the way dpkg set it up) or
with eog
--
[gutsy] image viewer slow to start
https://bugs.launchpad.net/bugs/134616
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for eog in ubuntu.
--
This problem is happening intermittently on closer investigation
to reproduce the bug stop dbus altogether, even without dbus something
like an image viewer should be immediately accessible regardless of
the status of another sub system, otherwise you are trying to make
a stack of cards that bug
look I'm not being funny, but you really are missing the point!
eog should NOT be blocking while it waits for dbus, are you saying if dbus
fails they
whole system should fail?
and by what reckoning do you make dbus a *vital* component
Ubuntu will run quite happily without it (except for very slo
I can replicate this bug EVERY TIME by trying to open an SVG image
eog cannot access dbus until after a reboot and even restarting the
dbus deamon doesnt help
this BUG is a problem with eog and SVG images
--
[gutsy] image viewer slow to start
https://bugs.launchpad.net/bugs/134616
You received t
this is problem with dbus has been confirmed on another machine
it involves SVG images
** Changed in: eog (Ubuntu)
Status: Invalid => New
--
[gutsy] image viewer slow to start
https://bugs.launchpad.net/bugs/134616
You received this bug notification because you are a member of Ubuntu
Desk
the svg issue is very possibly bug #119603 however it is the only way I can
reproduce the dbus bug
this bug effects all applications relying on dbus. dbus cease to respond
properly
even after restart
EOG is the ONLY program that causes dbus to behave in this way
It could well be a dbus problem,
happens *every* and *any* attempt to open an svg here
1 right click an svg image in nautilus
2 select open with "image viewer"
3 open a console and issue
eog
after a wait of approx 20-30 seconds you should see
** (eog:5965): WARNING **: Did not receive a reply. Possible causes include:
Public bug reported:
Binary package hint: glade-3
in glade 3, the component pallet shows different component sections
one of them is for the gnome DB components
it shows a group of blank buttons, which makes them
rather hard to distinguish, especially as the tool tip
seems to take its time!
** A
Public bug reported:
Binary package hint: libgtk2.0-0
This is easiest to reproduce with synaptic but will also work with any gtk app
that disables (greys out) buttons ie gimp
Do something in synaptic that disables the main buttons like click
reload
While a button is still disabled, place the mo
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/134616/comments/11 ?
--
[gutsy] image viewer slow to start
https://bugs.launchpad.net/bugs/134616
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-
see bug #22930
** Changed in: gtk+2.0 (Ubuntu)
Status: New => Invalid
--
(gutsy) gtkbuttons not responding after disabled/enabled cycle
https://bugs.launchpad.net/bugs/137857
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gtk
sorry just noticed this is a duplicate of bug #22930
(couldnt find it with initial posting form)
--
(gutsy) gtkbuttons not responding after disabled/enabled cycle
https://bugs.launchpad.net/bugs/137857
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
I can confirm that changing to clearlooks also makes nautilus right
click "open with " (other apps) menu work
it defiantly looks like a theme problem, or some difference with the
themes that highlights this bug
--
submenu items selection doesn't work correctly
https://bugs.launchpad.net/bugs/121
*** This bug is a duplicate of bug 140540 ***
https://bugs.launchpad.net/bugs/140540
does gnome-terminal run but in a small window, with no font?
If so I'm experiencing this bug too...
--
gnome-appearence-properties fail to run since last update
https://bugs.launchpad.net/bugs/140550
You re
I first noticed this also around 2001 ish, but in windows!!
(is this the first cross platform bug?!)
as nothing has been done in *over* 5 years, I think
some kind of patch would be rather nice...
nullack wrote:
> Looks as though this bug has been around since 2001. Sadly it retains an
> upstream p
Then use the manpower that's introducing new features!
Bug fixes are far more important that new features
___
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/
--
Newly-sen
I noticed this bug over five years ago in Winbloze !!!
reporting this upstream will have little result "theres a workround"
I think submitting a patch upstream that hides then shows a button when
it becomes enabled, might embarrass the people upstream to actually fix
the problem. especially if it
This bug is VERY trivial I happened to be using monodevelop so heres
some mono code with 2 buttons, 1 with the bug and 1 using the work
round
(I have used this workround in c++ before)
protected virtual void OnGoButtonClicked (object sender,
System.EventArgs e)
{
w
why not apply the workround in the installer or synaptic ?
I did look at some of the upstream reports a little while ago, but I
dont remember being convinced that there was any reason why a hack
couldnt be tacked onto the end of the gtk set sensitive code, providing
it respected the visibility sta
I only notice this with a single line at the top and bottom of the
screen
This is a compiz issue as it doesnt happen with compiz turned off
--
2 edge pixel rows on each side of panel are not clickable
https://bugs.launchpad.net/bugs/129673
You received this bug notification because you are a mem
forgot to mention this is along the whole width of the screen
--
2 edge pixel rows on each side of panel are not clickable
https://bugs.launchpad.net/bugs/129673
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
after further stabbing around, I've noticed its 1 pixel round the whole screen
(all edges of the screen)
You can't click to focus a window by clicking say point (0,100) even if this is
where the centre of a window
is
--
2 edge pixel rows on each side of panel are not clickable
https://bugs.laun
31 matches
Mail list logo
