Some upstream action:
http://bugzilla.gnome.org/show_bug.cgi?id=42834 (requesting the ability to
customize the toolbar)
http://bugzilla.gnome.org/show_bug.cgi?id=509660 (moving the Zoom and View As
controls to the main toolbar, complete with a needs-work patch)
** Bug watch added: GNOME Bug
On Mon, Apr 20, 2009 at 04:51, Matthew Paul Thomas
m...@canonical.comwrote:
This bug needs to be fixed with different code in different programs, so
it's not really appropriate to have them all in the same bug report.
This bug report is about Banshee. Bug 360228 is about Pidgin. Please
report
I wouldn't have expected so—with no upstream attention and no noticeable
updates—so I hadn't attempted again, but I just tried right now and it
seems to be fixed. Whatever it was must've been some growing pains.
** Changed in: gnome-session (Ubuntu)
Status: Triaged = Fix Released
--
*** This bug is a duplicate of bug 343261 ***
https://bugs.launchpad.net/bugs/343261
Bug 343261 covers this for notify-osd and various music players,
including Banshee. I'll update the description there to be clear that
Play/Pause are covered, not just track changes.
** This bug has been
** Summary changed:
- No notification on audio track changes
+ No notification on audio changes (Play, Pause, Next, Previous)
** Description changed:
Binary package hint: notify-osd
I am using notify-osd 0.9.3-0ubuntu1 (with /usr/share/notify_osd folder
renamed to notify-osd) on Ubuntu
On Thu, Mar 19, 2009 at 12:33, Nicolò Chieffo
nicolo.chie...@gmail.comwrote:
The next and previous notifications are shown even if the media player
is not started, so it's not their fault. someone suggested gnome-
settings-daemon
You'll see in the master bug that notify-osd was already
The upstream link should have been updated as per Sebastian in comment
12. Updating now, even though it seems obsolete. :)
** Changed in: gnome-applets
Bugwatch: GNOME Bug Tracker #355074 = GNOME Bug Tracker #370673
Status: Invalid = Unknown
--
gswitchit crash when logging in to
On Wed, Mar 11, 2009 at 04:40, Chris Coulson
chrisccoul...@googlemail.comwrote:
Yes, if you manually start vino-server then enable it in Remote Desktop
Preferences afterwards, this sets the AutostartCondition to true and
causes gnome-session to start another instance. This instance
On Wed, Mar 11, 2009 at 17:24, Chris Coulson
chrisccoul...@googlemail.comwrote:
Are you sure that the first instance actually quit before you tried to
enable the automatic loading via gconf?
Yes, quite sure. `ps -A | grep vino` returns nothing, but then immediately
enabling vino via gconf
Public bug reported:
Binary package hint: gnome-session
Release of Ubuntu: 9.04
Package Version: 2.25.92-0ubuntu1
gnome-session has been consuming all my CPU for about a week, and
recently I've noticed that my daemon.log and syslog files are over 1 GB
in a day.
I'm not sure how to troubleshoot
** Attachment added: daemon.log
http://launchpadlibrarian.net/23722231/daemon.log
--
Consumes all CPU, logs a lot of output
https://bugs.launchpad.net/bugs/340515
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in
** Attachment added: syslog
http://launchpadlibrarian.net/23722234/syslog
--
Consumes all CPU, logs a lot of output
https://bugs.launchpad.net/bugs/340515
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in ubuntu.
--
On Tue, Mar 10, 2009 at 14:29, Chris Coulson
chrisccoul...@googlemail.comwrote:
Thank you for your bug report. First of all, could you disable vino-
server from autostarting by running gconftool-2 --set --type=bool
/desktop/gnome/remote_access/enabled false, then log out and back in
again.
Okay, first of all, deactivating vino immediately brought my CPU back to
normal. So that's good; we know what caused the problem. :)
Here's the output from vino-server:
10/03/2009 21:36:07 Autoprobing TCP port in (all) network interface
10/03/2009 21:36:07 Listening IPv{4,6}://*:5900
10/03/2009
Also, I'm assuming this is more a vino bug than a gnome-session one, but
I won't change the product as I'm not sure of that.
--
Consumes all CPU, logs a lot of output
https://bugs.launchpad.net/bugs/340515
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Bug watch added: GNOME Bug Tracker #573950
http://bugzilla.gnome.org/show_bug.cgi?id=573950
** Also affects: gnome-settings-daemon via
http://bugzilla.gnome.org/show_bug.cgi?id=573950
Importance: Unknown
Status: Unknown
--
Locale settings in shell initialization not used by
On Wed, Feb 11, 2009 at 13:46, Jonathan Marsden
jmars...@fastmail.fmwrote:
Set a language at the gdm screen, and when prompted, tell it to make
this new language/locale the default for your user, and it adds
information to that effect to your ~/.dmrc Then, next time that user
logs in, they
** Summary changed:
- Locale settings not used by GNOME session
+ Locale settings in shell initialization not used by GNOME session
--
Locale settings in shell initialization not used by GNOME session
https://bugs.launchpad.net/bugs/306591
You received this bug notification because you are a
On Sun, Feb 8, 2009 at 00:39, Jonathan Marsden jmars...@fastmail.fm
wrote:
My change to the summary line was trying (apparently inadequately, since
you undid it!) to suggest that the issue is not really locale settings
not respected by Gnome. Locale settings most definitely *are*
respected
** Changed in: meta-gnome2 (Ubuntu)
Status: Incomplete = New
--
Locale settings in shell initialization not used by GNOME session
https://bugs.launchpad.net/bugs/306591
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to meta-gnome2
Changed summary back. To be clear, I am using ZSH as my shell, not Bash;
this problem is not Bash-specific.
** Summary changed:
- Locale settings in ~/.bashrc not used by GNOME session
+ Locale settings not used by GNOME session
--
Locale settings not used by GNOME session
Jonathan, do you have any idea what may be at fault here? I'm interested
in filing this upstream but I'm not sure which Gnome package to target.
--
Locale settings not used by GNOME session
https://bugs.launchpad.net/bugs/306591
You received this bug notification because you are a member of
** Changed in: f-spot (Ubuntu)
Status: Incomplete = Confirmed
--
The program 'f-spot' received an X Window System error
https://bugs.launchpad.net/bugs/286544
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
*** This bug is a duplicate of bug 75324 ***
https://bugs.launchpad.net/bugs/75324
How could this be a duplicate of a bug that predates Hardy? I think
there are separate issues here, and this one seems to be a regression.
Deed is done, and that bug seems to account for this issue, but I
On Wed, Dec 10, 2008 at 7:02 PM, Loye Young [EMAIL PROTECTED] wrote:
Obviously, it's not a small, simple fix.
Contrary to Sarah's assertion, setting focus_on_map to false in
every instance it appears in update-manager *fixes* update-manager:
Update-manager ceases to steal focus when that's
Public bug reported:
Binary package hint: gnome
(Sorry about the package, not sure if this would be gnome-settings-
daemon or something else?)
Originally posted on the forums:
http://ubuntuforums.org/showthread.php?p=6287235.
I want to manually control my LC_TIME settings independent of my
** Changed in: gnome-system-monitor
Bugwatch: Debian Bug tracker #472777 = GNOME Bug Tracker #507797
--
System monitor causes Xorg to consume 100% CPU
https://bugs.launchpad.net/bugs/187383
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
** Also affects: gnome-system-monitor (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472777
Importance: Unknown
Status: Unknown
--
System monitor causes Xorg to consume 100% CPU
https://bugs.launchpad.net/bugs/187383
You received this bug notification because you are
I also use the ATI driver; that seems to be a common factor. (No Desktop
Effects for me.)
** Changed in: f-spot (Ubuntu)
Status: Incomplete = New
--
The program 'f-spot' received an X Window System error
https://bugs.launchpad.net/bugs/286544
You received this bug notification because
On Tue, Dec 2, 2008 at 6:15 PM, Loye Young [EMAIL PROTECTED] wrote:
BTW, the problem isn't metacity. The problem is that update-manager
should not ask for focus in the first place. This is a problem that
has been solved over and over again in other applications.
This is known already. See
This bug was fixed upstream in June, which means it should be part of
8.10. Could anyone who experienced this problem test in 8.10/Intrepid
and post back the details? Thanks!
** Changed in: f-spot (Ubuntu)
Status: Triaged = Incomplete
--
f-spot 2 picasaweb failed to upload
*** This bug is a duplicate of bug 287482 ***
https://bugs.launchpad.net/bugs/287482
srm, thanks for that information!
--
Nereid.exe crashed with SIGSEGV
https://bugs.launchpad.net/bugs/287748
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
*** This bug is a duplicate of bug 279800 ***
https://bugs.launchpad.net/bugs/279800
Changed duplicate marking to reflect older bug with more discussion.
** This bug has been marked a duplicate of bug 279800
GStreamer update (7-Oct-2008, Intrepid) causes Banshee crash
--
Banshee
** This bug is no longer a duplicate of bug 283437
Banshee segfaults with GStreamer error
--
GStreamer update (7-Oct-2008, Intrepid) causes Banshee crash
https://bugs.launchpad.net/bugs/279800
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
*** This bug is a duplicate of bug 287482 ***
https://bugs.launchpad.net/bugs/287482
** This bug is no longer a duplicate of bug 279800
GStreamer update (7-Oct-2008, Intrepid) causes Banshee crash
** This bug has been marked a duplicate of bug 287482
Sync latest GStreamer packages
--
*** This bug is a duplicate of bug 287482 ***
https://bugs.launchpad.net/bugs/287482
** This bug has been marked a duplicate of bug 287482
Sync latest GStreamer packages
--
GStreamer update (7-Oct-2008, Intrepid) causes Banshee crash
https://bugs.launchpad.net/bugs/279800
You received
Public bug reported:
Binary package hint: f-spot
At the moment I can't open F-Spot at all. Same ultimate error if I move
my ~/.gnome2/f-spot folder.
andrew:~ f-spot --debug -v Desktop/virus.png
** Running f-spot in Debug Mode **
** Running Mono with --debug **
[Info 14:05:22.563]
** Description changed:
Binary package hint: f-spot
At the moment I can't open F-Spot at all. Same ultimate error if I move
my ~/.gnome2/f-spot folder.
+
+ Version: 0.5.0.3-0ubuntu1
andrew:~ f-spot --debug -v Desktop/virus.png
** Running f-spot in Debug Mode **
** Running Mono
On Fri, Oct 10, 2008 at 12:02 PM, Pedro Villavicencio
[EMAIL PROTECTED]wrote:
traces are not good, may you run f-spot as: f-spot --debug f-spot-
debug.txt perform the operation to make it crash and after that upload
that file as an attachment to this report?
Did you see mine on bug 267628?
.
--
Andrew Conkling
http://andrewski.net
--
gvfsd-trash crashed with SIGSEGV in g_main_context_prepare()
https://bugs.launchpad.net/bugs/271637
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in ubuntu.
--
desktop-bugs mailing list
This bug has been triaged. Please be aware that there is no additional value in
further confirming the bug. You can show your support for the bug by
subscribing to the bug. There is a bunch of helpful documentation about how to
optimize your time spent on bugs at:
Reopening and confirming. Better stacktraces were uploaded to bug 264537
and bug 267628, but they were removed by Apport. How do I go about
getting the information uploaded now?
** Changed in: f-spot (Ubuntu)
Status: Invalid = Confirmed
--
f-spot.exe crashed with SIGSEGV
*** This bug is a duplicate of bug 189335 ***
https://bugs.launchpad.net/bugs/189335
Can bug 189335 be made public? I'm coming up against a duplicate and I'd
like to examine it more closely.
Anyone with access to it can change the secrecy:
Bruce, please file a new bug on that; this report is for a specific issue
related to gvfsd-trash.
--
gvfsd-trash crashed with SIGSEGV in g_main_context_dispatch()
https://bugs.launchpad.net/bugs/252174
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
On Thu, Jun 26, 2008 at 11:44, Mike Basinger [EMAIL PROTECTED]
wrote:
Was patched upstream, any change if getting this fix in Hardy?
It's not fixed in GNOME yet; the patch was just submitted, but has not been
reviewed or committed yet, right?
** Attachment added: unnamed
Can you try moving your ~/.gnome2/f-spot folder somewhere else (maybe
your Desktop, for example) and then starting a fresh copy of F-Spot?
Also, can you make sure all other extensions are turned off?
** Changed in: f-spot (Ubuntu)
Status: Confirmed = Incomplete
--
F-spot crashes when
On Tue, Jun 10, 2008 at 11:34, tiefflieger [EMAIL PROTECTED]
wrote:
Happened to me, too (sorry for my duplicate bug entry), but maybe my
tries to open f-spot via console give additional hints for tracking down
the problem...?
Don't worry about the duplicate.
As for terminal output, some was
Is anyone still having this problem?
** Changed in: f-spot (Ubuntu)
Status: Triaged = Incomplete
--
f-spot 2 picasaweb failed to upload
https://bugs.launchpad.net/bugs/178303
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to f-spot
On Mon, May 19, 2008 at 5:51 PM, cutlerite [EMAIL PROTECTED] wrote:
However, even when I don't have a video card installed, I still
experience slowness.
...and a decided lack of a screen? You will always have some sort of video
card installed.
And yes, Christopher, the problem with the new
The problem is a general one in GTK+'s FileChooser, which File Roller is
using in the Extract dialog. The bug is already known upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=402349.
** Changed in: fileroller
Importance: Unknown = Undecided
Bugwatch: GNOME Bug Tracker #403985 = None
On Wed, Apr 30, 2008 at 9:51 AM, Andrea Grandi [EMAIL PROTECTED]
wrote:
Sebastien: I've enabled hardy-proposed, installed all the updates
available and rebooted my Ubuntu. I still have that bug: gnome-panel
keeps freezing.
You haven't mentioned this before, but are you using a Google
On Wed, Apr 30, 2008 at 12:59 PM, Andrea Grandi [EMAIL PROTECTED]
wrote:
Yes, I do! Is this a problem?
No, not a problem, just a different issue. See the above comments, namely
this one:
On Tue, Apr 29, 2008 at 8:00 AM, Sebastien Bacher [EMAIL PROTECTED] wrote:
the google calendar issue is
On Sun, Apr 27, 2008 at 11:30 AM, Endolith [EMAIL PROTECTED] wrote:
Can the crossfading backend be enabled by default for Rhythmbox?
Doubtful. The Rhythmbox developers know of a few issues that would prevent
it from being stable enough for default use. You could investigate upstream
on the
On Thu, Apr 24, 2008 at 2:05 PM, Reshey [EMAIL PROTECTED] wrote:
I have the same problem. Around 100 % cpu usage and unresponsive when
using system monitor. Terminal and top works fine.
This was just fixed upstream and hasn't been released in Ubuntu yet. Please
subscribe to the bug and keep
schiebe, flyingian, others: See Sebastian's note on comment 36:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/187383/comments/36
.
** Attachment added: unnamed
http://launchpadlibrarian.net/13591370/unnamed
--
System monitor causes Xorg to consume 100% CPU
*** This bug is a duplicate of bug 84876 ***
https://bugs.launchpad.net/bugs/84876
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 84876, so it is being marked as such. Please look at
On Sat, Apr 12, 2008 at 5:03 AM, Andrea Ratto [EMAIL PROTECTED]
wrote:
Looks like a synchronization problem to me. Did anyone have this on a
single core machine?
Yeah.
Also found a dupe:
https://bugs.launchpad.net/ubuntu/+bug/155164
Thanks, I marked it as such.
** Attachment added:
On Fri, Apr 11, 2008 at 5:24 AM, jhmac77 [EMAIL PROTECTED] wrote:
unsubscribe sent back return to sender
I believe you're looking for this?
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/85776/+subscribe
** Attachment added: unnamed
** This bug is no longer a duplicate of bug 151227
Left-clicking clock applet hangs gnome-panel
--
Clicking on clock applet hangs gnome-panel
https://bugs.launchpad.net/bugs/203527
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
This bug has so little information and isn't reproducible in any one way (at
least based on the reporter's description, which mentions Gutsy not Hardy like
bug 203527) that I don't think it's worth making the master bug, even though
it's older. There seem to be a few issues going on, and the
*** This bug is a duplicate of bug 194505 ***
https://bugs.launchpad.net/bugs/194505
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 194505, so it is being marked as such. Please look
On Wed, Apr 9, 2008 at 3:42 PM, Scott Wegner [EMAIL PROTECTED] wrote:
After looking into the stack-trace and such, it looks
to be a duplicate of bug #214079, which already has a reported fix. Let
me know if you would like to report a new bug anyway, and I can.
When in doubt, do, and Apport
On Thu, Apr 10, 2008 at 8:21 PM, Andrew Conkling [EMAIL PROTECTED]
wrote:
When in doubt, do, and Apport will automatically mark it as a duplicate
once it retraces it. I'd say do it, err on the side of redundancy. :)
Especially since bug 214079 seems to be missing a valid backtrace
Yeah, it's pretty sporadic, hard to reproduce. You can find old crash
reports in /var/crash (you can navigate to there in a file browser
window.) Simply double-click on one and it will be processed. (Also,
I've found that old crash reports do not get re-processed if the crash
report sits in there,
Everyone, this bug is fixed. Update Synaptic and install 0.1.19. (If
it's not available yet, please wait a few hours for it.) Comments about
workarounds are not necessary anymore, unless you're having a different
problem (in which case you should file a new bug report). And there's no
need to
*** This bug is a duplicate of bug 213863 ***
https://bugs.launchpad.net/bugs/213863
On Tue, Apr 8, 2008 at 11:51 AM, Steve Illgen [EMAIL PROTECTED]
wrote:
*** This bug is a duplicate of bug 213863 ***
https://bugs.launchpad.net/bugs/213863
I did the same workaround as emme suggested.
*** This bug is a duplicate of bug 213863 ***
https://bugs.launchpad.net/bugs/213863
Yeah, definitely an annoying bug, but the fix has already been released.
If you don't have 0.1.19 in your updates yet, be sure to refresh and/or
switch your repositories to the main servers.
-Original
On Tue, Apr 8, 2008 at 6:31 PM, adel [EMAIL PROTECTED] wrote:
doesn't work for me because ubuntu boot into read only file system
Sounds like you got yourself into a jam. Did you happen to try one of the
(unsanctioned) workarounds?
Regardless, your best bet is to seek help via the various
On Tue, Apr 8, 2008 at 6:45 PM, dbsoundman [EMAIL PROTECTED] wrote:
I experience in Hardy, no compiz. It is very annoying, because I have
the normal desktop effects enabled, which is generally stable on my
system, but my processor is an Athlon XP, so when I'm multi-tasking (as
always), it
On Tue, Apr 8, 2008 at 6:26 PM, Scott Wegner [EMAIL PROTECTED] wrote:
I was just upgrading my Hardy alpha 5 and got crash on reboot.
Very likely a different bug; could you possibly report a new bug via Apport?
(Apport will mark it as a duplicate if it turns out to be the same issue.)
**
*** This bug is a duplicate of bug 213863 ***
https://bugs.launchpad.net/bugs/213863
On Tue, Apr 8, 2008 at 8:19 PM, alcohen [EMAIL PROTECTED] wrote:
*** This bug is a duplicate of bug 213863 ***
https://bugs.launchpad.net/bugs/213863
Ditto. Broke today after updating.
Already
*** This bug is a duplicate of bug 213863 ***
https://bugs.launchpad.net/bugs/213863
On Tue, Apr 8, 2008 at 6:49 PM, garfield [EMAIL PROTECTED] wrote:
O.k. I understood the message!
DUPLICATE bug # bla bla
This I've been told via E-Mail about 10 times. Habe verstanden!!
I will
On Tue, Apr 8, 2008 at 8:30 PM, dbsoundman [EMAIL PROTECTED] wrote:
Thanks Andrew, I was citing the effects of the problem just as an
example, the main issue is indeed just that the windows steal the focus.
For me, that sets off that chain reaction, because of my not-so-fast
processor. I
On Tue, Apr 8, 2008 at 10:28 PM, vitali [EMAIL PROTECTED] wrote:
Confirmed. A possible workaround should be the following:
1. Download
2. Install this package manually
3. sudo apt-get -f install or sudo apt-get upgrade
No need for these types of workarounds, this is fixed, please don't keep
On Mon, Apr 7, 2008 at 2:02 PM, Andrew Lambert [EMAIL PROTECTED]
wrote:
Just adding my voice to the choir here.
A lot of people have, but there's no need. This is already reported upstream
to the developers.
** Attachment added: unnamed
http://launchpadlibrarian.net/13178382/unnamed
--
This was fixed in 0.11.5 (in Hardy). I can dig up the GNOME Bugzilla bug
number if desired.
** Changed in: rhythmbox (Ubuntu)
Status: Incomplete = Fix Released
--
Rhythmbox does not listen to HAL regarding audio_folders
https://bugs.launchpad.net/bugs/202405
You received this bug
Will, as Sebastian mentioned above, it has to do with the cairo
rendering that was put into the Resources graphs for 2.22/Hardy. It
doesn't always go to 100%; the CPU impact has a lot to do with your
video driver.
--
System monitor causes Xorg to consume 100% CPU
** Bug watch added: GNOME Bug Tracker #507797
http://bugzilla.gnome.org/show_bug.cgi?id=507797
** Also affects: gnome-system-monitor via
http://bugzilla.gnome.org/show_bug.cgi?id=507797
Importance: Unknown
Status: Unknown
--
System monitor causes Xorg to consume 100% CPU
*** This bug is a duplicate of bug 187383 ***
https://bugs.launchpad.net/bugs/187383
Hewus, you're right. They're both related to the updates in Resources.
Thanks for catching.
** This bug has been marked a duplicate of bug 187383
System monitor causes Xorg to consume 100% CPU
--
system
For the Hardy/Resources problem, see bug #202122, to which I attached
the Debian bug also.
** Changed in: gnome-system-monitor (Debian)
Status: New = Invalid
--
Excessive CPU usage by Gnome System Monitor
https://bugs.launchpad.net/bugs/93847
You received this bug notification because
This is not a duplicate of bug #93847; that bug predates the new graphs
in Hardy and has to do with high CPU usage even when not on the
Resources tab.
** This bug is no longer a duplicate of bug 93847
Excessive CPU usage by Gnome System Monitor
** Changed in: gnome-system-monitor (Ubuntu)
Linking to correct upstream bug (which I just reported because I
couldn't find an existing one):
http://bugzilla.gnome.org/show_bug.cgi?id=524830. In sum: g-s-m uses too
much CPU. It is not just a matter of false reporting (like I had
previously incorrectly suggested), and is not related to the
On Thu, Mar 27, 2008 at 9:21 PM, Emilio Pozuelo Monfort [EMAIL PROTECTED]
wrote:
** Bug watch added: Debian Bug tracker #471152
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471152
Thanks, but that's not the right bug. This bug predates the changes in Hardy
and doesn't have anything to
*** This bug is a duplicate of bug 199496 ***
https://bugs.launchpad.net/bugs/199496
No problem, David! That happens and is all just part of the game. :)
It's Apport that helps us easily determine all of the bug shtuff.
-Original Message-
From: Davegod75 [EMAIL PROTECTED]
Date:
Gadget Boy, this problem predates the smooth graphs introduced in Hardy.
This is about g-s-m reporting high CPU usage for itself, even when not
on the Resources tab. This has gotten worse in Hardy, yes, but is about
a preceding issue.
--
Excessive CPU usage by Gnome System Monitor
gQuigs, yes, the graph/Resources issue is known upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=507797.
--
Excessive CPU usage by Gnome System Monitor
https://bugs.launchpad.net/bugs/93847
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
** Also affects: update-manager (Ubuntu)
Importance: Undecided
Status: New
--
'Downloading package information' and 'building dependency tree' progress
dialogs steal focus
https://bugs.launchpad.net/bugs/35876
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 178402 ***
https://bugs.launchpad.net/bugs/178402
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 178402, so it is being marked as such. Please look
On Wed, Mar 12, 2008 at 5:05 AM, Chris [EMAIL PROTECTED] wrote:
What did you guys do that it works now?
I upgraded to Teds gnome-power-manager - 2.22.0-0ubuntu1~ppa1 but
nothing happens when I press the power button.
Be sure to restart gnome-power-manager. Easiest way is simply to log out
On Wed, Mar 12, 2008 at 8:36 AM, Chris [EMAIL PROTECTED] wrote:
Be sure to restart gnome-power-manager. Easiest way is simply to log out
and back in.
I forgot to mention that I logged me out and in, even restarted my PC.
In gnome-power-manager I tried interactive, suspend and shutdown non
Ted, your package works for me; thanks for your work. Did this fix make
it upstream? (Is that even applicable in this case? :)
--
regression: pressing power button no longer brings up logout dialog
https://bugs.launchpad.net/bugs/57872
You received this bug notification because you are a member
On Wed, Mar 5, 2008 at 5:24 AM, Martin Pitt [EMAIL PROTECTED]
wrote:
Can you please all try my newly proposed version in my PPA?
https://launchpad.net/%7Epitti/+archive
I think that finally gets it right. Please report back here. Thank you!
I don't know what changes are in this version, but
On Tue, Mar 4, 2008 at 6:28 AM, sharninder [EMAIL PROTECTED] wrote:
Although has anyone noticed
that the g-p-m display doesn't change as fast as the power settings
display changes in windows.
Well, I've had a different experience with Windows' power management, and
that's certainly not
Yes, that was the necessary information. (I can't do anything with it,
just correcting the status on the bug.)
** Changed in: gvfs (Ubuntu)
Status: Incomplete = Confirmed
--
Applications unable to access Filesystem
https://bugs.launchpad.net/bugs/197352
You received this bug notification
** Summary changed:
- HARDY HERON evolution/nautilus issue: nautilus crashed with SIGSEGV
+ evolution/nautilus issue: nautilus crashed with SIGSEGV
** Description changed:
Binary package hint: nautilus
- This is how the crash occured:
-
+ This is how the crash occurred:
1. clicked on
According to bug #196096 (of which this should be a duplicate, but I'm
not cleaning up 20+ other bug reports), this was fixed today:
This bug was fixed in the package nautilus -
1:2.21.92svn20080303-0ubuntu1
---
nautilus (1:2.21.92svn20080303-0ubuntu1) hardy; urgency=low
* SVN
On Mon, Mar 3, 2008 at 4:18 PM, James Deibele [EMAIL PROTECTED]
wrote:
apport-cli reports no pending crash reports so I can't do that.
Use (IIRC) 'apport-cli -c /path/to/file.crash'.
--
evolution/nautilus issue: nautilus crashed with SIGSEGV
https://bugs.launchpad.net/bugs/196864
You
On Mon, Mar 3, 2008 at 6:58 PM, James Deibele [EMAIL PROTECTED]
wrote:
I have no idea what you are saying. I don't know what IIRC means and I
don't know where files crash.
Sorry James. You should be able to navigate to /var/crash and double-click
on any .crash files listed there, but you
Public bug reported:
Binary package hint: nautilus
Nautilus crashed/restarted after I was deleting some files and
recovering others from the Trash.
ProblemType: Crash
Architecture: i386
Date: Sun Mar 2 00:19:40 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/nautilus
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/12348190/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/12348191/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/12348192/Disassembly.txt
** Attachment
1 - 100 of 340 matches
Mail list logo
