*** This bug is a duplicate of bug 852406 ***
https://bugs.launchpad.net/bugs/852406
** This bug has been marked a duplicate of bug 852406
Phantom battery appears after resume from suspend
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subs
*** This bug is a duplicate of bug 852406 ***
https://bugs.launchpad.net/bugs/852406
** This bug is no longer a duplicate of bug 882160
Extra battery detected which does not exist and is considered empty
** This bug has been marked a duplicate of bug 852406
Phantom battery appears after
System settings now has a "System Info" icon, which shows the 64-bit in
the OS type field of the overview.
Fixed if you ask me, this bug can be closed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu.
h
I can't get the Maverick behavior to work in Oneiric.
http://mail.gnome.org/archives/commits-list/2010-November/msg06088.html
seems to state that earlier mentioned solutions will not work.
I consider this a problem with Oneiric and can't find how to fix it so
the behavior is like reported above.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/882160
Title:
Extra battery detected which does not exist and is considered empty
To manage notifications about this bug
Public bug reported:
After a supsend, gnome-power-manager detects a second battery which is
empty. The battery shows up in the panel icon.
When I start gnome-power-statistics, from the commandline, it lists the second
battery and then aborts:
$ gnome-power-statistics
(gnome-power-statistics:363
I was not able to reproduce this bug with the latest versions in
maverick.
** Changed in: empathy (Ubuntu)
Status: Incomplete => Invalid
--
empathy-av crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/649184
You received this bug notification because you are a m
** Visibility changed to: Public
--
empathy-av crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/649184
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in ubuntu.
--
desktop-bugs mailing list
desktop-b
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/40134634/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/40134635/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/40134636/ProcStatus.txt
** Attachm
Public bug reported:
Binary package hint: gnome-system-monitor
After installing Ubuntu, it is not clear to the user wether they are
using a 32bit or a 64bit version.
The System Monitor System tab should contain architecture information so
people know whether they are running 32bit or 64bit. It i
*** This bug is a duplicate of bug 412789 ***
https://bugs.launchpad.net/bugs/412789
** This bug has been marked a duplicate of bug 412789
The window selector menu in the panel randomly fails to show some of my open
windows. Also, when waking from a sleeping state, the panel does not updat
I've got a git checkout and rand valgrind, the leaks that are definite
according to valgrind:
libio (from glib)
launchpadintegration bug #483610
glibc nns (g_option_context_parse)
libfontconfig in a call of FcConfigParseAndLoad XML_ParseBuffer
from g_type_create_instance into fontconfig
g_object_
1) I reset the parameter gconftool -u
/apps/gnome-power-manager/notify/perhaps_recall
The recall message came back again after a reboot.
2) I downloaded the rules file. I began with
MD5 27e7f10f85cce16411e20af5437fe956
/lib/udev/rules.d/95-devkit-power-battery-recall-ibm.rules
And after the copy
$ hexdump -C /sys/class/dmi/id/product_name
36 34 36 36 39 4d 47 0a |64669MG.|
0008
I'm not really sure when I last saw the battery reccall message, but I
told it to not show it again and that worked for me (in karmic with the
latest updates).
All hardware
Clicking "test", as suggested in the report, works perfectly with me on
Karmic, 64 bit, Firefox 3.5, totem 2.27.2-0ubuntu4. I can't reproduce
this bug on Karmic at this moment.
--
totem plugin wont play sound on mywoot.net
https://bugs.launchpad.net/bugs/331099
You received this bug notification
I've seen this bug all through Jaunty and the development releases of karmic,
I'm still seeing the bug in Karmic at this date.
gnome-session: 2.27.5-0ubuntu1
--
Missing suspend icon with non-human theme
https://bugs.launchpad.net/bugs/277309
You received this bug notification because you are a m
2.27.5-0ubuntu2~ppa4 did not solve the problem for me. Here is what I have for
On Battery Power, When battery power is critically low.
>From Combobox to verbose result
Suspend -> suspend
Hibernate -> blank
Shutdown -> hibernate
This was just after an "gconftool-2 --recursive-unset /apps/gnome-pow
The settings are off-by-one for me, and it looks like storing the settings
work. And the settings take effect as soon as they are set. Your log showed:
TI:17:26:54 TH:0x207f070FI:gpm-prefs-core.c
FN:gpm_prefs_action_combo_changed_cb,267
- Changing /apps/gnome-power-manager/buttons/li
Upon futher investigation, settings are stored. The problem was specific to
which option I choose, the problem is an off by one thing. For "On Battery
Power", "Wehn laptop lid is closed" the options are:
Blank Screen
Suspend
Hibernate
Shutdown
If I choose Hibernate, --verbose shows
- Changing /
** Attachment added: "Log showing the output of running gnome-power-preferences
--verbose two times"
http://launchpadlibrarian.net/29759981/gnome-power-preferences_verbose.log
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/29759983/Dependencies.txt
** Attachment add
Public bug reported:
Binary package hint: gnome-power-manager
Actions:
Open gnome-power-preferences
Change settings
Close gnome-power-preferences
Result:
Power management does not follow the set options. Opening the preference window
again, shows the settings according to some default and do no
** Attachment added: "gnome-power-bugreport.txt"
http://launchpadlibrarian.net/29434530/gnome-power-bugreport.txt
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete => New
** Tags added: apport-collected
--
Incorrect recall warning for Lenovo T61
https://bugs.launchpad.ne
** Attachment added: "DevkitPower.txt"
http://launchpadlibrarian.net/29434526/DevkitPower.txt
--
Incorrect recall warning for Lenovo T61
https://bugs.launchpad.net/bugs/403564
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-powe
** Attachment added: "GConfNonDefault.txt"
http://launchpadlibrarian.net/29434527/GConfNonDefault.txt
--
Incorrect recall warning for Lenovo T61
https://bugs.launchpad.net/bugs/403564
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gn
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/29434525/Dependencies.txt
--
Incorrect recall warning for Lenovo T61
https://bugs.launchpad.net/bugs/403564
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-po
Architecture: amd64
DistroRelease: Ubuntu 9.10
Package: gnome-power-manager 2.27.2-0ubuntu2
PackageArchitecture: amd64
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
Uname: Linux 2.6.31-3-generic x86_64
UserGroups: adm admin aud
*** This bug is a duplicate of bug 402287 ***
https://bugs.launchpad.net/bugs/402287
I personally do not consider this a duplicate. Not being able to hide
the recall message, and the recall message being wrong (not contain the
correct information as the battery is not being recalled) are two
d
Public bug reported:
Binary package hint: gnome-power-manager
I've got a Lenovo battery with:
ASM P/N: 92P1142
FRU P/N: 92P1141
(top right corner of label)
So, I get a recall warning pointing me to the website[1]. I can't run
the automated checking system, so I called support. Turns out: there i
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/24687469/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/24687470/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/24687471/Disassembly.txt
** Attachm
** Bug watch added: GNOME Bug Tracker #533219
http://bugzilla.gnome.org/show_bug.cgi?id=533219
** Also affects: gvfs via
http://bugzilla.gnome.org/show_bug.cgi?id=533219
Importance: Unknown
Status: Unknown
--
anonymous ftp PASS command sent without argument
https://bugs.launchpad
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/23129437/Dependencies.txt
--
anonymous ftp PASS command sent without argument
https://bugs.launchpad.net/bugs/334540
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Public bug reported:
Binary package hint: gvfs
When connecting to an anonymous FTP account on an FTP server, the gvfs-
backend for ftp does not send an argument with the PASS command. This
means that for any RFC959 compliant server will not allow the anonymous
entry and send back an error message
Ah, I think I found the problem then, unmarking it is not saved because
gedit core-dumps every time you close it. So it probably doesn't save
the preferences because of the core-dump then.
This should be fixed as soon as the core-dump is fixed.
** Attachment added: "Gedit core dump"
http://la
Did you use a 64 bit version of Ubuntu?
I'm using the following, so please try to get as close to this configuration as
possible:
2.6.28-4-generic #11-Ubuntu SMP Fri Jan 16 21:50:52 UTC 2009 x86_64 GNU/Linux
Package: gedit Version: 2.25.4-0ubuntu1
No compiz installed
Intel GMA965 / X3100 graphics
This is not a Xubuntu bug. In Jaunty using the plain vanilla Ubuntu
(64bit) and Gnome, starting gedit from a terminal will start it with
"Always on visible workspace".
To reproduce:
- Open a gnome-terminal
- Type gedit
- Right click on the window bar of gedit, observe the Workspace visibility
sta
Here is the last part, which should contain the problem. I'm not sure what I
should be looking for, but I have seen this:
(16:29:51) [0xb41500] [rb_shell_player_get_playing_song_duration]
rb-shell-player.c:3385: Did not get playing entry : return -1 as length
Attached is the last part of the l
I ran that, but that log also included a complete listing of my library
of songs and information about my file system layout. So I would have to
read that log and remove the lines out of it before I'm going to post
that here. I don't have time for that now, so please consider asking for
a more spec
I'm confirming this bug and have have a way of reproducing it: increase
the system load.
To reproduce:
1. First make sure you have allot of load on your HD and the location bar is
visible in nautilus. You can introduce system load by reading allot of files
from disk, for example: cat * */* > /de
I've made a screencast of what happens. It's terrible quality, but I
think it shows the point.
Searching in the automatic playlist (as shown in the movie) will skip to
other songs and eventually completely stop when the result list is
empty.
If I type something that doesn't result in any songs qu
Yes, it happens with the "My Top Rated" list. Trying it out a bit, I
also had the following result, which is generally the same. It does seem
to be some kind of timing issue, so it might help to have more numbers
in your automatic list (you can also just create one which includes all
your music).
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/16437774/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/16437775/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/16437776/ProcStatus.txt
--
Search
Public bug reported:
Binary package hint: rhythmbox
There seems to be some kind of race condition that, given the right
timing, will stop the current song from playing if search results are
empty.
To reproduce:
1) Use an automatic playlist (not sure this is needed)
2) Play a song from the playli
Public bug reported:
Binary package hint: gnome-keyring
There is a situation where a focus conflict seems to arise. When this
happens, I can't change anything or enter the required password. The
only thing that is possible is moving to another terminal and killing
the keyring applicaiton.
Steps
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/7511490/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://librarian.launchpad.net/7511491/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://librarian.launchpad.net/7511492/ProcStatus.txt
--
Mouse
Public bug reported:
Binary package hint: totem
This is a very low priority feature-request like bug. Because I can
imagine it being fixed easily, it might be worth mentioning.
When the user gets an error report or message box from totem, when totem
is in full screen mode, the cursor will stay h
Public bug reported:
Binary package hint: gnome-control-center
My new SlimStar 310 keyboard has some keys are not registered. There needs to
be a new keyboard layout, along with some setkeycodes to get the kernel to
support some of the keys.
Some of the keys include e011 and e02d (from kernel m
Here is a complete report from the "Problem report for" help program.
Due to the ease with which this problem is recreated I havn't taken the
time to install the debugsysms for the used program. And the problem can
simply be avoided by clicking more slowely or simply turning on shuffle
so it is imp
Public bug reported:
Using a automatic playlist with only unrated (rating=0) songs, rhythmbox
will crash if you click on the songs rating quickly and repeatedly
(songs will be removed from the list if their rating goes up). This is
probably a race condition problem.
To reproduce the bug:
1) Make
48 matches
Mail list logo