Hi, this bug was marked a dupe of this bug:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/364023
But, that bug is a dupe of this bug:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/34321
If you feel this bug is another dupe, please set it.
** This bug is no longer a
*** This bug is a duplicate of bug 34321 ***
https://bugs.launchpad.net/bugs/34321
** This bug has been marked a duplicate of bug 34321
should not write the session when changing automatic session saving option
--
Applications are restarted at launch even though Automatically remember
** Summary changed:
- should not write the session when changing automatic session saving option
+ should delete the saved session when unmarking automatic session saving option
** Description changed:
I've found that gnome-session doesn't properly handle turning off
automatic session
** Description changed:
There is no settings button in gnome-screensaver, thus I am unable to
change the settings for any screensaver.
+
+ Note: this bug is marked, upstream, as won't fix. Here is the given
+ explanation why:
+
Hey Lumpy,
I think you may have the wrong idea about this bug. From the upstream report,
it looks like the issue might be that gstreamer is simply not handling the
situation correctly, and thus is a gstreamer bug. Unfortunately, the upstream
report is not all that clear, but it is assigned!
alright, Imma gonna try to file this upstream.
** Package changed: ubuntu = gnome-session (Ubuntu)
--
Applications are restarted at launch even though Automatically remember
running applications when logging out is disabled
https://bugs.launchpad.net/bugs/364023
You received this bug
** Bug watch added: GNOME Bug Tracker #586299
http://bugzilla.gnome.org/show_bug.cgi?id=586299
** Also affects: gnome-session via
http://bugzilla.gnome.org/show_bug.cgi?id=586299
Importance: Unknown
Status: Unknown
--
Applications are restarted at launch even though
ok, I filed this bug under gnome-session, since that is the package of
gnome-session-properties, and thats the dialog that contains the
malfunctioning option.
--
Applications are restarted at launch even though Automatically remember
running applications when logging out is disabled
have you tried medibuntu?
** Changed in: totem (Ubuntu)
Status: New = Incomplete
--
Totem Player doesn plays DVDs
https://bugs.launchpad.net/bugs/361887
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in ubuntu.
--
well, it looks like the codec is not installed.. You should try
medibuntu.org
--
Totem Player doesn plays DVDs
https://bugs.launchpad.net/bugs/361887
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in ubuntu.
--
desktop-bugs
yeah, I've been getting this too. I'm on a full size desktop. For me,
it seems like the declared screen border isn't moving correctly when the
panels autohide. There is this snap to place feature that snaps the
border of a window, which has been on computers for many years.
In this case, the
o yeah, and this is a regression from intrepid in jaunty
--
Expanded auto-hide panel at bottom still subtracted from desktop size
https://bugs.launchpad.net/bugs/96
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in
your welcome, and take care
** Changed in: gcalctool (Ubuntu)
Status: Incomplete = Invalid
--
gcalctool squared negative number gives a negative result
https://bugs.launchpad.net/bugs/327890
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
To answer your question literally: ( - 6 ) square equal
That gives 36
I looked at windows calc, and it suffers from the same problem, just in
different ways. If I hit: 6 + 5 square equal and that gives 31. What
if I wanted (6+5)^2 and not 6+5^2? I checked my own, 10 year old hand
held
-(6)^2 should evaluate to -36. Its (-6)^2 that evaluates to 36.
Now, gcalc is evaluating the expression correctly, but maybe you could argue
that the UI is non intuitive. You hit 6, then hit the change polarity button,
then hit the square button. Maybe its reasonable to expect gcalc to enter
** Summary changed:
- FreeCell Soltaire Fullscreen bug
+ AisleRiot FreeCell Soltaire Fullscreen bug
--
AisleRiot FreeCell Soltaire Fullscreen bug
https://bugs.launchpad.net/bugs/296028
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
another workaround is to move or resize the window in that brief moment
that the window is un-fullscreen (ie, hit F11 and then _quickly_ grab
one of the window decorators to move or resize)
This method does require fast mousing skills, but is doable since
another aspect of this bug is that the
well, I'll be darned, this bug is still present. For me, the way to
produce the error message is to go to Places Computer, then double
click an unmounted drive. An authentication window will popup. WAIT,
until an additional dialog box pops up, with a fairly generic message
like Opening such
just for reference, I've tested with the old gedit. I get about 177
seconds load time on my computer. I ran it twice. I'll test the
loading speed of the new package, as soon as it hits the repos.
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
well, It just hit the repos as I wrote that message. I confirm that the
patch works as intended. 177 second cpu burn is now a 10 second cpu
burn. I also opened up the filebrowser pane, and it seemed to be
working. I then went to /var/lib/dpkg/info, and the same 10 second burn
took place, but
Martin Pitt and mac_v, because of the nature of the bug that I
originally reported, I'm curious which folder you are testing gedit on.
This bug ended up being about the file browser plugin, and the negative
behaviour was wholly dependent on what folder the file resided in. This
patch aims to
well, the original bug was in the filebrowser plugin So, disabling
it is the workaround, but it is also an indicator if you have the same
bug. Anyway, I don't know.
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
https://bugs.launchpad.net/bugs/276094
You received this
Maybe we could ask the upstream guys to allow for a custom message on codecs
that fail to install through totem's autoinstaller. Then, whoever packages
totem can just customise the message for whatever distro they are using. For
ubuntu, the message would probably include at least the
well, if you guys want me to reopen this bug, I can. If you are quite
sure of yourself about this bug, and its reproducibility, then lets
reopen. BTW, you guys can open the bug yourself too.
But, you may want to wait till the release candidate is released, to
see if this bug is still around.
reopening this bug, because I figured out whats going on. Brasero uses
/tmp for its scratch work space, whatever, whereas RAM should be used.
This is a bug. I don't understand why brasero uses /tmp.
I'm going to redo the summary to reflect my findings.
** Changed in: brasero (Ubuntu)
** Summary changed:
- cd burning causes severe unresponsiveness, and other foul smells
+ brasero hashes the harddrive, causing slowdowns
** Description changed:
- I am having lots of trouble burning a cd image. The default tool makes
- my computer INCREDIBLY laggy. It always lags, and
well, the error message has gone away, so its time to invalidate this
bug. But, there is still a lingering problem. Before, the drive was
mounted, and an error message was displayed. Now, the drive is mounted.
The ORIGINAL behaviour was to mount the drive and then also open a
nautilus window
Public bug reported:
Binary package hint: gedit
I don't know why, or if any other folder is affected. But, I tried to
open a few files in /var/lib/dpkg/info/ and they all caused the cpu
burn.
A condition for this to happen is that gedit must be closed prior to
opening the file. If gedit is
I can confirm the additional breakage that Pablo is describing. I will
file an upstream bug report.
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
https://bugs.launchpad.net/bugs/276094
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Bug watch added: GNOME Bug Tracker #554362
http://bugzilla.gnome.org/show_bug.cgi?id=554362
** Also affects: gedit via
http://bugzilla.gnome.org/show_bug.cgi?id=554362
Importance: Unknown
Status: Unknown
--
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
forget this for now, since there are many changes to the way the
keyboard is handled...
** Changed in: gnome-control-center (Ubuntu)
Status: New = Invalid
--
keytouch should be connected with gnome-keybindings-properties
https://bugs.launchpad.net/bugs/264209
You received this bug
** Bug watch added: GNOME Bug Tracker #553132
http://bugzilla.gnome.org/show_bug.cgi?id=553132
** Also affects: gstreamer via
http://bugzilla.gnome.org/show_bug.cgi?id=553132
Importance: Unknown
Status: Unknown
--
[intrepid] [hardy] webcam works in Ekiga, but not cheese
Claudiu: if you are having trouble with gstreamer-properties AND cheese,
then its not a cheese problem; its a gstreamer problem. Cheese relies
upon gstreamer for its connection to the webcam.So, I think this bug
should be under gstreamer, not cheese. Ill change it, but feel free to
change it
I had something similar happen to me, so Im switching to confirmed.
Hope that makes sense.
** Changed in: gnome-control-center (Ubuntu)
Status: New = Confirmed
--
gnome-keyboard-properties crashed with SIGSEGV in
g_cclosure_marshal_VOID__VOID()
https://bugs.launchpad.net/bugs/268636
You
because there are apparent issues with keyboards in intrepid right now,
Im gona hold off on filing this upstream. Maybe after the intrepid
release?
--
keytouch should be connected with gnome-keybindings-properties
https://bugs.launchpad.net/bugs/264209
You received this bug notification because
mk, I left it open because its still a bug in hardy, but I guess it
makes sense to close. Hardy LTS is just about security fixes? And bugs
like these are left to the biyearly releases? The more I think about
it, the more sense it makes.
--
cd burning causes severe unresponsiveness, and other
Public bug reported:
Binary package hint: gnome-control-center
This is a wish item. Keytouch is a program that automatically sets up
the keys of those non-standard keyboards, you know the ones with those
multimedia keys, whatever. gnome-keybindings-properties should have a
connection with
** Description changed:
Binary package hint: gnome-control-center
This is a wish item. Keytouch is a program that automatically sets up
the keys of those non-standard keyboards, you know the ones with those
multimedia keys, whatever. gnome-keybindings-properties should have a
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/17210277/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/17210278/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/17210279/Disassembly.txt
** Attachment
I opened up Brasero
--
gvfs-hal-volume-monitor crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/252046
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for gvfs.
--
desktop-bugs mailing list
This happens for me when I try to mount different partitions on my disk,
and just in the way described. Changing status to confirmed since it is
unclear what information was being requested.
** Changed in: nautilus (Ubuntu)
Status: Incomplete = Confirmed
--
Unable to mount location --
** Bug watch added: GNOME Bug Tracker #549946
http://bugzilla.gnome.org/show_bug.cgi?id=549946
** Also affects: nautilus via
http://bugzilla.gnome.org/show_bug.cgi?id=549946
Importance: Unknown
Status: Unknown
--
Unable to mount location -- Internal error: No mount object for
Turns out, the disk was a bad burn, so Its good that itt stopped at 93%
maybe?
I burned again, and there were no bugs, but it was still laggy.
--
cd burning causes severe unresponsiveness, and other foul smells
https://bugs.launchpad.net/bugs/262867
You received this bug notification because
I'm using a clean install of Intrepid, and these issues are non-
existent! Even during the expected hiccups of lag, the system remains
responsive to user input.And certainly, the case of my computer
being lagged down during the whole burning process is gone.
Cheers
--
cd burning causes
Public bug reported:
I am having lots of trouble burning a cd image. The default tool makes
my computer INCREDIBLY laggy. It always lags, and watching the memory,
it looks like it has NO method of caching at all. I figured the lag
stems from IO wait stemming from dispersed harddrive requests.
can you post/link to an example of an mp3 which causes the crash?
--
rhythmbox crashes on mp3 file
https://bugs.launchpad.net/bugs/231762
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in ubuntu.
--
desktop-bugs mailing list
I am unable to reproduce this myself. Subscribing to see how others
handle this.
--
Totem freezes after several pauses
https://bugs.launchpad.net/bugs/231739
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in ubuntu.
--
*** This bug is a duplicate of bug 89072 ***
https://bugs.launchpad.net/bugs/89072
** This bug has been marked a duplicate of bug 89072
Totem-mozilla doesn't request codecs
--
No gstreamer easy codec install for embedded video
https://bugs.launchpad.net/bugs/199940
You received this bug
I guess this has been fixed upstream (2.23.x)
see: http://bugzilla.gnome.org/show_bug.cgi?id=484947#c3
I also assume launchpad will update itself eventually.
--
Totem-mozilla doesn't request codecs
https://bugs.launchpad.net/bugs/89072
You received this bug notification because you are a member
49 matches
Mail list logo
