** Attachment added: 3 Charge history.png
http://launchpadlibrarian.net/9169563/3%20Charge%20history.png
--
power management applet seems very screwy
https://bugs.launchpad.net/bugs/137951
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Attachment added: 7 Charge time accuracy profile.png
http://launchpadlibrarian.net/9169567/7%20Charge%20time%20accuracy%20profile.png
--
power management applet seems very screwy
https://bugs.launchpad.net/bugs/137951
You received this bug notification because you are a member of Ubuntu
** Attachment added: 6 Discharge time profile.png
http://launchpadlibrarian.net/9169566/6%20Discharge%20time%20profile.png
--
power management applet seems very screwy
https://bugs.launchpad.net/bugs/137951
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: 4 Voltage history.png
http://launchpadlibrarian.net/9169564/4%20Voltage%20history.png
--
power management applet seems very screwy
https://bugs.launchpad.net/bugs/137951
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Attachment added: 2 Estimated time history.png
http://launchpadlibrarian.net/9169562/2%20Estimated%20time%20history.png
--
power management applet seems very screwy
https://bugs.launchpad.net/bugs/137951
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: 5 Charge time profile.png
http://launchpadlibrarian.net/9169565/5%20Charge%20time%20profile.png
--
power management applet seems very screwy
https://bugs.launchpad.net/bugs/137951
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
** Attachment added: 1 Power History.png
http://launchpadlibrarian.net/9169558/1%20Power%20History.png
--
power management applet seems very screwy
https://bugs.launchpad.net/bugs/137951
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Public bug reported:
Binary package hint: xkb-data
Hello! I'm using a Dell Latitude D620 laptop, with a French keyboard
(I'm not sure if the others are the same), and I noticed there's no
geometry file for this model in Ubuntu.
If you open the Keyboard Preferences applet, the Layouts tab, and
This is what I have until now. Thanks in advance for helping.
** Attachment added: Geometry of Dell Latitude D620's keyboard
http://launchpadlibrarian.net/9186590/dell%20latitude%20d620.xkb
--
[xkb-data] missing geometry for Dell Latitude D620 keyboard
https://bugs.launchpad.net/bugs/138131
I am using libpam-keyring, not pam-keyring. I'll try to get a screenshot
today.
$ aptitude show ~npam-key
Package: libpam-keyring
New: yes
State: installed
Automatically installed: yes
Version: 0.0.8-6
Priority: optional
Section: universe/admin
Maintainer: Ubuntu MOTU Developers [EMAIL PROTECTED]
(1) redundancy setting console font: as far as I can tell, the
/etc/init.d/console-setup is setting up the console font quite late in
the boot process. However, /usr/share/initramfs-tools/scripts/init-
top/console_setup does (or can do) the same thing much earlier. [...]
This is done
Public bug reported:
Binary package hint: console-tools
Hello! I'm using Ubuntu Gutsy, and for some times I've been hacking
around parts of the boot process, and in particular the set-up of the
text console.
There are a few improvements I've been able to make, and some of them I
think should be
Public bug reported:
Binary package hint: sshfs
Hello! I'm running Gutsy on a laptop, and I use sshfs to mount
directories from various computers around the house. (AFAIK, it's the
safest solution, but I'm open to suggestions.)
It usually runs pretty well, although a bit slow (though I think
Public bug reported:
Binary package hint: sshfs
The SSHFS in the Gutsy repositories is currently version 1.6-1. In the
Sourceforge repositories it already reached 1.8:
http://sourceforge.net/project/showfiles.php?group_id=121684package_id=140425
** Affects: sshfs-fuse (Ubuntu)
Importance:
Public bug reported:
Binary package hint: libpam-keyring
This is on up-to-date Gutsy:
libpam-keyring doesn't work correctly when set-up together with gdm's
autologin feature.
As expected, GDM logins automatically the correct user. However libpam-
keyring fails to retrieve the user's password
Public bug reported:
Binary package hint: ubuntu-minimal
In the current build of Gutsy, there is no kind of boot log, ie a log of
all the messages shown during boot.
There are a couple of bugs in the (two, I think) packages that provide
boot-log functionality that I'd like to link here (either
** Description changed:
Binary package hint: libpam-keyring
This is on up-to-date Gutsy:
libpam-keyring doesn't work correctly when set-up together with gdm's
autologin feature.
As expected, GDM logins automatically the correct user. However libpam-
keyring fails to retrieve
One of the bugs I mentioned above is
https://bugs.launchpad.net/upstart/+bug/98955
There's also a question on this subject:
https://answers.launchpad.net/ubuntu/+question/11985
--
No boot-time logs exists at this time in Gutsy
https://bugs.launchpad.net/bugs/137254
You received this bug
Yes, it seems to be working now. Thanks!
** Changed in: gnome-keyring (Ubuntu)
Status: Incomplete = Fix Released
** Changed in: gnome-keyring-manager (Ubuntu)
Status: New = Fix Released
--
can't create new keyring
https://bugs.launchpad.net/bugs/132054
You received this bug
Public bug reported:
Binary package hint: update-manager
Hello. This is about the latest (and older) update-manager on Gutsy.
I have the update-manager window opened with the Changes tab selected
and expanded, so it shows the changes for every package to be updated.
Imagine there are three
Re-opening (I think). Even if this is not a real error (ie, if not
having a DSDT is a normal situation), this is still a user-interface
bug: it should not be reported as a boot-time error. The message should
be changed to something more descriptive, like file /DSDT.aml not
found, using defaults or
Public bug reported:
Binary package hint: linux-image-2.6.22-9-generic
During boot I get the following warning:
[0.684000] ACPI: EC: Look up EC in DSDT
[0.696000] ACPI Warning (tbutils-0158): Incorrect checksum in table [TCPA]
- 00, should be 9A [20070126]
[0.696000] ACPI: SSDT
Public bug reported:
Binary package hint: ubuntu-desktop
In Gutsy, ubuntu-desktop (up-to-date) depends on serpentine. This is not
a _necessary_ package---some desktop users might not even have a CD
writer.
It should be a recommends rather than depends.
** Affects: ubuntu-meta (Ubuntu)
*** This bug is a duplicate of bug 122039 ***
https://bugs.launchpad.net/bugs/122039
The same is true for cd-paranoia, dvd+rw-tools, nautilus-cd-burner,
wodim --- someone without a CD drive can be desktop user.
Other unnecessary packages (should be recommends): fortune-mod, gnome-
Other items for the list:
cd-paranoia, dvd+rw-tools, nautilus-cd-burner, wodim --- someone without a CD
drive can be desktop user.
fortune-mod --- not really critical
gnome-pilot-conduits --- I don't have a PDA
almost all printer-related packages (foomatic-*, pnm2ppa, cupsys-*)
which are not
*** This bug is a duplicate of bug 122039 ***
https://bugs.launchpad.net/bugs/122039
Thanks, I moved the list of packages there.
--
ubuntu-desktop depends on serpentine
https://bugs.launchpad.net/bugs/133150
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi, thanks for reminding me of this. It's working now, you can close
this safely.
--
Network-config doesn't start the network
https://bugs.launchpad.net/bugs/79633
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Forgot to mention: this is on an up-to-date Gutsy, running on a Dell
Latitude D620 with ipw3945 wireless. The network works.
--
Error getting killswitch power:
org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported
https://bugs.launchpad.net/bugs/133167
You received this
Public bug reported:
Binary package hint: network-manager
I see I keep getting this error in /var/log/daemon.log:
Aug 17 18:10:33 cimer NetworkManager: info Error getting killswitch
power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type
not supported
And I get _lots_ of it. I
I can see this in up-to-date Gutsy every time I shut down.
Strangely I can't find anything in the logs about it, with just one
exception a few days ago:
$ grep Error sending /var/log/*
kern.log:Aug 12 14:35:32 cimer kernel: [75812.852000] ipw3945: Error sending
LEDS_CMD: time out after 500ms.
So right now there is zero possibility to find out what happened during
boot? I see messages spewing all over the console, some of them errors
(that I'm trying to work out), how can I get to them?
--
logd not running
https://bugs.launchpad.net/bugs/98955
You received this bug notification
Someone might want to apply this patch to the /etc/init.d/bootlogd file.
As the old one, it checks if the daemon exists. However, if it doesn't,
it warns the user (the old one failed silently) and points them to this
bug report, which is informative enough.
There's also a 2 sec delay there (it
The attached file is my replacement for /etc/init.d/915resolution
It should do everything the current version does, but (1) it dumps any
output of its binary in /var/log/915resolution and (2) it uses the init-
functions to display messages, including success status, failures and
warnings.
The
Public bug reported:
Binary package hint: 915resolution
On Gutsy (and probably everything else) the startup script of
915resolution doesn't use the /lib/lsb/init-functions for display.
It uses echos and it also allows its binary to spew stuff in the
console. At least on my system the result is
Public bug reported:
Binary package hint: gnome-keyring-manager
This is about Ubuntu Gutsy, freshly updated.
I can't create any new keyrings (including the default one, if there are
none) with the gnome keyring manager. When I try to create a new keyring
(menu KeyringNew Keyring) the new name
I added gnome-keyring to the affects list, as it seems there's the
problem.
--
can't create new keyring
https://bugs.launchpad.net/bugs/132054
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I still have the not working issue even after the latest upgrades.
(But I also have multiple entries, so that might contribute.)
--
multiple non-working Open WithGimp entries
https://bugs.launchpad.net/bugs/121796
You received this bug notification because you are a member of Ubuntu
Bugs, which
I can confirm that it works correctly now, i.e. NM connects itself to
the network after giving it the keyring password.
--
[ipw3945] nm-applet doesn't work unless I start dhclient manually
https://bugs.launchpad.net/bugs/127649
You received this bug notification because you are a member of
Yes, it seems to work now correctly. Thanks!
--
metacity forgets (on Hostname) annotantion on remote apps sometimes
https://bugs.launchpad.net/bugs/90409
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Actually no, the SSID is broadcasted. But your post reminded me to post
a bit more info:
The network is based around a IEEE 802.11 a/b/g router, set up to
function only as g. Security is WPA2-PSK(AES).
$ iwconfig
lono wireless extensions.
eth0 no wireless extensions.
eth1
I've just done a restart and recorded the logs for the entire procedure.
When I log in, the first thing that pops up is the keyring dialog asking
for the keyring password. I started iwevent in a console (so every event
that came up before this doesn't appear), then:
(1) I unlocked the keyring.
Public bug reported:
Binary package hint: network-manager-gnome
Hello! Weird issue with the network-manager applet. (Up-to-date Gutsy,
on a laptop with an Intel ipw3945 chipset, running the 2.6.22-8-generic
kernel.) This started quite some time ago (maybe more than a month), but
I initially
Public bug reported:
Binary package hint: ccache
Ubuntu uses update-alternatives to manage and decide which of several
alternatives can be used for a certain function.
CCache should use this system to allow the user to automatically
configure their system to use ccache on compilation.
**
Public bug reported:
Binary package hint: linux-image-2.6-386
Hello!
I'm running Ubuntu Gutsy on a Dell Latitude D620 laptop with Intel
integrated video. See ddcprobe below.
X runs very well with the intel driver, although I'm using 915resolution
to get the native display resolution programmed
Public bug reported:
Binary package hint: update-manager
This is more a feature request rather than a bug (though it could be
seen as a usability bug). It concerns mainly Gutsy as it's the
development branch, but it applies to the other versions too.
Except for viewing and picking updates,
I noticed something weird: the failure, whatever may be causing it,
appears to be intermittent.
Yesterday I accidentally booted up with the wireless disabled via the
switch, and when I flicked the switch back the wireless turned on. It's
totally weird, this never happened before _and_ I'm sure I
I'm still getting this at least sometimes. I don't use the killswitch
very often because of that, but it seems that the behavior changes from
time to time.
Before Gutsy, nm-applet would display the disconnected status when I
killed the wireless, and automatically re-connected when I reset the
Just to clarify: when I filed this bug, the killswitch worked as long as
wireless was enabled at boot.
Now it just permanently disables wireless.
--
[gutsy] wireless doesn't work after booting with wireless switch off
https://bugs.launchpad.net/bugs/121415
You received this bug notification
That would be very helpful if only suspend worked :)
Time for another bug report...
--
[gutsy] wireless doesn't work after booting with wireless switch off
https://bugs.launchpad.net/bugs/121415
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
I'm sure something can be done about this. I've just done an strace on
the menu opening, it tries to do ~1500 file opens (most of which are for
non-existent files).
First of all, most of those should be preloaded (actually, they should
be cached once, then the cache should be preloaded in one
Should this work correctly by now? I still get white bars around the
panels and the menus, though shadows work correctly around normal
windows.
--
White boxes where there should be shadows
https://bugs.launchpad.net/bugs/116829
You received this bug notification because you are a member of
It happens to me too, on an Intel video card. It happened when I tried
to restart compiz with compiz --replace (it was working OK, just
wanted to reload some settings), then when I tried the same thing using
the Desktop Effects applet.
--
compiz.real crashed with SIGSEGV in exit()
Public bug reported:
Binary package hint: compiz
I started compiz recently (to try it out), and noticed an annoying
effect: Panels don't unhide normally. I have all panels (top and bottom)
set to auto-hide. They normally unhide when I move the mouse to the top
or the bottom. With compiz active
I've been thinking: Shouldn't this bug be left open (or in progress)
until the migration is deemed complete? (It's still a bug even though
it's intentional because it's not wanted behavior, it's a temporary
side-effect of a change, like a (known) regression... right?)
Since there are so many
Public bug reported:
Binary package hint: curl
Somewhere between
https://launchpad.net/ubuntu/+source/curl/7.16.2-4ubuntu1 and
https://launchpad.net/ubuntu/+source/curl/7.16.2-6ubuntu4 the
libcurl4-openssl package disappeared.
I don't know if that's intentional (libcurl4-openssl-dev still
OK. I'll check it out in a few days. I didn't see any comments on that
around the net.
Is there any way of installing something in the meantime without
breaking the installed packages? (Ignoring the mess with openssl?)
--
libcurl4-openssl no longer exists
https://bugs.launchpad.net/bugs/124008
Hello Justin,
Yes, I've kept up with the updates and it's still happening. Note that I
don't think this is a problem with the GIMP itself, it works correctly
when I start it from the command line or the application menu. It's very
likely a problem with the way it registers itself to Nautilus'
Hello again!
I've been scouring the web and the various /usr/share/mime* directories
on my computer, and I can't figure out where is Nautilus keeping the
file that tells it JPEGs can be opened with application X. Anyone can
point me to it, so I can take a look and see what's wrong?
--
multiple
Public bug reported:
Binary package hint: ubuntu-desktop
Hello! This is an exploratory bug report. It is based on Gutsy, which
I'm using right now, but probably applies to the older versions too.
I've just noticed ubuntu-desktop depends on the xsane and espeak
packages. These two are packages I
Public bug reported:
Binary package hint: nautilus
Hello! I've noticed Nautilus crashes (and restarts correctly) when I
open the Property page of certain files (right-click properties).
This happens on Ubuntu Gutsy, freshly updated.
I've seen this with Flash, mpg and avi files, at least:
Public bug reported:
Hello! I've just noticed the following error thrown by Nautilus while
opening a directory:
** Message: Error: GStreamer encountered a general supporting library error.
gstffmpegdemux.c(1062): gst_ffmpegdemux_open (): /play/decodebin0/ffdemux_swf0:
Input/output error
I have just completed a dist-upgrade (and, indeed, xsane was updated),
but GIMP still won't start from the right-click menu. I remind you that
I GIMP starts normally from the Applications menu, and I can open the
images with drag-and-drop just fine.
On the other hand, even if the GIMP would
Update: This bug doesn't happen for me anymore. The killswitch started
working properly somewhere in Feisty, and it's still working on Gutsy.
(But see bug #121415 for a slightly different related problem.)
--
Doesn't reconnect when wireless disabled/re-enabled using kill switch
Public bug reported:
Binary package hint: gimp
Hello! I'm using Gutsy (after updating from Dapper through all
versions).
The right-click Open With menu for image files (at least for JPEGs)
has four consecutive [Open with GIMP Image Editor] options, neither of
which works. (I remember sometimes
I think there are actually two sides to this bug.
On the one hand, I occasionally get the warning that my battery's old or
broken and only has 36-25% maximum capacity left. (Not, this is not the
charge of the battery, but the maximum charge.) I don't know how it
estimates it (presumably from some
About the current charge (since I can't post there, I don't have LJ):
instead of bugging users, the manager could simply do what it did before
it had the new profiling features. (Or, it could initialize the
profile with the old one, instead of blank data.) It will then be at
least as good as the
Public bug reported:
Binary package hint: eclipse
Hello! I have updated to Gutsy recently and I noticed Eclipse throws a
scary warning due to the new GSlice thing:
[EMAIL PROTECTED]:~$ eclipse
using specified vm: /usr/lib/jvm/java
***MEMORY-WARNING***: [12710]: GSlice: g_thread_init() must be
I attached this to Firefox, too, because it owns the library. Firefox
gives the same warning, though I didn't notice instability yet.
--
eclipse reports memory corruption, crashes
https://bugs.launchpad.net/bugs/121413
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: the log file from the last crash
http://launchpadlibrarian.net/8147279/hs_err_pid12862.log
** Also affects: firefox (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
eclipse reports memory corruption, crashes
https://bugs.launchpad.net/bugs/121413
You
Public bug reported:
Binary package hint: eclipse
Hello! I noticed that after a fresh install eclipse throws the following
message to the console:
~$ eclipse
using specified vm: /usr/lib/jvm/java
Could not create /usr/local/lib/eclipse/.eclipseextension. Please run as root:
touch
Public bug reported:
Hello!
I'm using a Dell Latitude D620 laptop, running Gutsy. It has a
ipw3945-based wireless card (I'm not sure where to look for exact
details). The laptop has a wireless switch.
The bug: if I boot up the laptop with the switch in the OFF position,
the wireless is not
True, I just realized that the wording can be confusing (killswitch
on/wireless off).
If the wireless is disabled at boot by the killswitch, it can't be enabled at
all.
If the wireless is enabled at boot, the killswitch works normally and you can
disable/enable the wireless until you shut
OK, so I tried creating a new workspace, with the bug enabled (ie, the
libmozjs file in the normal position), Eclipse crashed. So I hid
(renamed) the file as described above, started Eclipse again, created a
workspace (it worked), stopped Eclipse, and put the file back. Then:
(1) I Started
Hello. I've just looked closer at this, I see a pattern now and I think
I know the problem.
I have pulseaudio running as a system-wide instance, with SCHED_FIFO
enabled. Each time I run a GTK program (eg, gedit) from the console, I
get this message immediately after the command line:
W: main.c:
OK, it seems I'm not done yet. After a reboot I don't get the warning in
the console anymore. The core-util errors are gone, too. However I still
get the
Jun 17 15:19:43 cimer pulseaudio[11929]: main.c: Root priviliges required.
Jun 17 15:19:43 cimer pulseaudio[11932]: main.c: Root priviliges
Public bug reported:
Binary package hint: vlc
$ vlc
VLC media player 0.8.6 Janus
***MEMORY-WARNING***: [12174]: GSlice: g_thread_init() must be called before
all other GLib functions; memory corruption due to late invocation of
g_thread_init() has been detected; this program is likely to
I've looked in http://www.pulseaudio.org/browser/trunk/src/daemon/main.c
and the error seems to come from line 450. The daemon complains that
it's run as a system-wide instance but it's not root. Which is weird
since the daemon was already started (at boot time), and this is
triggered every time a
I didn't mention this before, but I've upgraded to Gutsy now and the
status is the same.
--
pulseaudio fills logs with Root privileges required messages
https://bugs.launchpad.net/bugs/95513
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Bug watch added: PulseAudio sound server #97
http://pulseaudio.org/ticket/97
** Also affects: pulseaudio (upstream) via
http://pulseaudio.org/ticket/97
Importance: Unknown
Status: Unknown
--
pulseaudio fills logs with Root privileges required messages
*** This bug is a duplicate of bug 120278 ***
https://bugs.launchpad.net/bugs/120278
Yes, when I run it like that it doesn't crash anymore.
--
vlc crashes at start
https://bugs.launchpad.net/bugs/120844
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
I have a similar issue on Gutsy, but the errors are a bit different (see
below). The disc plays with no glitches in a hardware player, but the
.dat files can't be copied.
I can't find a cdfs package, only a cdfs-src but that doesn't build
(under Gutsy, at least), I think it's made for a different
Indeed, it seems to have gone back to the old dependency set.
--
Dependency on java2-runtime removed
https://bugs.launchpad.net/bugs/81876
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
In case that's not obvious from the above, aptitude remove evms gets
rid of the problem. I suppose if you don't know what evms is, then
you're probably not using it (unless someone else configured your
system; you should ask them then).
--
Device-mapper errors: dm-linear, lookup failed
Public bug reported:
Hello! I've just updated from Feisty to Gutsy. I'm having a strange
issue with the power manager. (I use Gnome for pretty much everything,
btw.)
Each time I start up the computer, the power manager claims the
battery's total capacity is only 33%, which probably means a bad
Public bug reported:
Binary package hint: udev
Hello! I've updated from Feisty to Gutsy yesterday, and noticed a weird
problem:
Right after boot, a udevd process (there are several in the System
Monitor) keeps hogging the processor. (This means 100% pretty much all
the time. However this is a
Public bug reported:
After updating from Feisty to Gutsy I got only intermittent sound with
Flash (ie, only sometimes, not skippy). After a while it simply didn't
work at all.
I tried reinstalling libflashsupport and I got a No candidate version
found for libflashsupport.
** Affects: Ubuntu
Same here, with a normal Feisty (without xubuntu or kubuntu).
--
update-manager -c -d DOESN'T work for going to Gutsy
https://bugs.launchpad.net/bugs/118862
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
As the second error suggests, file /usr/lib/python2.5/site-
packages/UpdateManager/DistUpgradeFetcher.py doesn't import the os
object/package/whatever it's called. (Sorry, I only learned python by
ear...)
I added import os at the top of that file and the update started.
(I still got the dbus
Public bug reported:
Binary package hint: gdm
File /usr/share/gnome/help/gdm/es/gdm.xml contains a wrong quote;
entity instead of the correct quot; one.
I noticed this during the update from Feisty to Gutsy.
** Affects: gdm (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Public bug reported:
Binary package hint: mono
I have noticed some warnings during the update from Feisty to Gutsy.
I've only managed to copy the snippet below (it happened at least once
before).
If there's a log you need just tell me where to get it from.
***MEMORY-WARNING***:
Update: OK, I've run the update.
The good news: it worked (but see below). I'm happily running Gutsy
right now.
The bad news: it didn't work flawlessly. During the update there were
several error messages. I did run a (probably unnecessary, perhaps
harmful, and certainly lengthy)
Public bug reported:
Binary package hint: gconf2
Hello. I've just updated from Feisty to Gutsy (using the update manager)
and during the update I've seen many warnings like the one below.
***MEMORY-WARNING***: gconftool-2[28570]: GSlice: g_thread_init() must
be called before all other GLib
Public bug reported:
Binary package hint: gnome-app-install
Hi. Not sure if this is a real bug, maybe just a UI bug.
I've just done an update from Feisty to Gutsy, and I noticed these
messages during the update:
..
Setting up gnome-app-install (0.4.2) ...
Caching application data...
I've just realized I didn't mention the work-around I found in this
thread:
I've noticed that the reason for the crashes, all crashes (at least on
my computer) is not actually the network failure but the error dialog. I
have checked the Disable sliding animation/on top style for alert
messages
I've just tried opening a random rar I've got from the net. It works
with unrar and rar-nonfree, but not with only rar-free. However, it may
have been just an unsupported version of file.
--
Does not cooperate with unrar-free
https://bugs.launchpad.net/bugs/39127
You received this bug
If anyone is interested by this bug in the future, the specification was
added at https://blueprints.launchpad.net/ubuntu/+spec/unified-system-
monitoring (there is a link to the wiki there).
Mr Bacher, any comments on the blueprint would be much appreciated :)
--
The History graphs really need
Public bug reported:
Binary package hint: gnome-system-monitor
Hi! This report is about System Monitor 2.18.1.1, running on Ubuntu
Feisty. It would be a nice fix for Gutsy.
Currently the CPU History graph in the System Monitor is a nice tool for
a quick estimate of the current CPU usage, but
Public bug reported:
Binary package hint: gnome-system-monitor
Hi! This report is about System Monitor 2.18.1.1, running on Ubuntu
Feisty. It would be a nice fix for Gutsy.
The System Monitor is a nice tool for a quick estimate of the current
CPU usage, but it could be much more useful if it
I've just tried this (I didn't know about it, thanks!), but it doesn't
seem to work. That is, no matter what channel I pick the keys seem to
move the same slider all the time, the PCM one. I'll have to try some
rebooting tests later, but I can't use the sound right now.
--
volume buttons control
Public bug reported:
On Ubuntu Feisty -- and I presume all older variants -- all commands in
the Keyboard Shortcuts applet are hard-coded. The program is gnome-
keybinding-properties.
The actions list should be completely configurable:
* existing commands should be visible to and changeable
801 - 900 of 1111 matches
Mail list logo
