the issue was caused by conflict with package 'hibernate'
[code]sudo apt-get remove hibernate[/code]
solves the problem.
however please notice that package [B]hibernate [/B]is required by [B
]laptop-mode-tools[/B] for the auto shutdown at low battery levels
feature.
** Changed in: linux-meta (Ubu
package 'hibernate' is however responsible of a serious issue since it
prevents the system to enter Suspend to RAM (standby) mode. Only
removing it restores this feature!
--
laptop_mode cannot find /usr/sbin/hibernate thus cannot hibernate laptop
https://bugs.launchpad.net/bugs/149324
You receive
see also http://bugzilla.gnome.org/show_bug.cgi?id=483288
with gnome-keyring (2.20-0ubuntu4) gutsy the problem I reported is not
yet solved, hereafter some more details I found out:
the problem described in this bug (that is very similar to the one of GNOME bug
476644) seems to be caused by the i
this is just to add that when string '@include common-pammount' is
included in the above mentioned pam.d files pam-mount works as
expected, it is only gnome-keyring that does not.
For the actual (default) configuration of my gdm and login files please
refer to the mentioned http://bugzilla.gnome.o
same here
--
package gimp 2.4.0~rc3-1ubuntu4 failed to install/upgrade: trying to overwrite
`/usr/share/doc/libgimp2.0/README', which is also in package libgimp2.0
https://bugs.launchpad.net/bugs/148985
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
a temporary workaround to get rid of the broken dependency is going to
/var/cache/apt/archives and issuing command sudo dpkg -i gimp-
python_2.4.0~rc3-1ubuntu4_i386.deb which will downgrade gimp-python to
previous version (if available in cache).
This will prevent "broken packages" message to app
Seems this bug as already been addressed and will be fixed in gnome 2.20.1
release of the keyring manager.
http://bugzilla.gnome.org/show_bug.cgi?id=483288
** Changed in: gnome-keyring-manager (Ubuntu)
Status: New => Fix Committed
--
gnome keyring manager cannot create permanent keyrings
Public bug reported:
Binary package hint: laptop-mode-tools
current version of Gutsy up to date and latest laptop-mode-tools
/etc/init.d/laptop-mode start
* Enabling laptop mode.../usr/sbin/laptop_mode: line 780:
/usr/sbin/hibernate: No such file or directory
laptop mode actu
Workaround: I found that installing unsupported package 'hibernate'
gives laptop-mode-tools the file it required /usr/sbin/hibernate
however I wonder why it doesn't use the the gnome way to hibernate the
laptop (as I could make use of suspend / hibernate without an issue
before installing hibernat
as far as it concerns to me I have laptop-mode-tools enabled and do not
experience the referenced bug #12483.
I have an Intel Santa Rosa platform with 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI
Controller
--
laptop mode should not be activated by default
https://bugs.launchpad.net/bugs/124199
You r
I can confirm this bug with versions previous to Gutsy Tribe 5, however
as of Ubuntu Gutsy Beta this issue seems to be fixed and laptop modes
starts up without issues.
Please note that advice by Tom Gillam unfortunately did not last over
the reboot of the machine and needed to be applied every tim
fix released inside Ubuntu Gutsy Beta
--
laptop mode tools not running
https://bugs.launchpad.net/bugs/123086
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
Public bug reported:
Binary package hint: glipper
glipper causes even 8 wakeups per second!
glipper is a very handy applet, however please developers make it more
energy saving aware!
powertop utility from Intel shows glipper causes always from 3 to 8 wakeups
per second to the CPU.
I really do
Public bug reported:
Binary package hint: linux-image-generic
Standby (aka Suspension to RAM) does not work any more after updates of
the last two days.
After clicking to "Suspend" button the screen becomes black, than
prompts me for the password (as if I had just resumed it from standby).
After
49.003836]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/computer_logicaldev_input_3').
Oct 10 16:00:51 ubuntu gnome-power-manager: (aldeby) Resuming computer
Oct 10 16:00:51 ubuntu gnome-power-manager: (aldeby) suspend failed
--
standby does not work an
** Changed in: laptop-mode-tools (Ubuntu)
Status: New => Fix Released
--
laptop mode should not be activated by default
https://bugs.launchpad.net/bugs/124199
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs m
I found that issuing via shell command
sync; echo 1 > /sys/power/pm_trace; /etc/acpi/sleep.sh force
the system correctly enters standby and correctly resumes!
However it remains that using the Gnome applet it does not work as I described!
Do someone have any idea about what is going on?
--
stan
** Changed in: linux-meta (Ubuntu)
Status: New => Incomplete
--
standby does not work any more
https://bugs.launchpad.net/bugs/151241
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
executing
Code:
sync; echo 1 > /sys/power/pm_trace; /etc/acpi/sleep.sh
does simply nothing...
no outputs either in syslog and in dmesg
how can I further debug this issue?
here attached is my sleep.sh file, can somebody compare with his? maybe
via diff or xxdiff...
** Attachment added: "/etc/ac
Unfortunately I have to confirm this bug is still present with current
and up-to-date Ubuntu Gutsy.
>From time to time, mostly some time after there is no network activity
the network becomes inresponsive, although both ifconfig and iwconfig
show wlan0 still up and NetworkManager applet shows link
here is my lspci -vvv output
** Attachment added: "lspci vvv"
http://launchpadlibrarian.net/9953057/lspci%20vvv
--
iwl4965 drops out from time to time (Santa Rosa)
https://bugs.launchpad.net/bugs/144621
You received this bug notification because you are a member of Ubuntu
Bugs, which is the b
Public bug reported:
Binary package hint: gnome-keyring-manager
versions:
ii gnome-keyring 2.20-0ubuntu1
GNOME keyring services (daemon and tools)
ii gnome-keyring-manager 2.20.0-0ubuntu2
keyring
more error messages provided by nm-applet
** (nm-applet:24977): WARNING **: couldn't connect to daemon at
$GNOME_KEYRING_SOCKET: /tmp/keyring-Zpi3Sl/socket: Connection refused
** (nm-applet:24977): WARNING **: couldn't communicate with gnome
keyring daemon via dbus: The name org.gnome.keyring was
GOSH!!! After this bug has driven me totally crazy I finally focused out
the actual cause of the described issue: character '?'.
Yes that is, if you choose a password for gnome keyring containing the ?
character the keyring cannot open the keyrings any more reproducing the
described misbehavior.
Installing by hand latest 1.1.20 drivers from
http://intellinuxwireless.org/ website has solved the problem for me.
"Error setting Tx power (-11)" message was not related to the problem
described, it was a bug introduced with one of the latest driver
versions, however it has been fixed as well as
** Description changed:
Ubuntu 7.10 with linux-ubuntu-modules-2.6.22 version 2.6.22-14.37
included driver r8169 gets loaded for device with Realtek RTL8101E chipset
which is a Fast Ethernet device.
Problem: Ethernet networking has poor performance (with 100Mbps Full
Duplex link transf
Public bug reported:
Ubuntu 7.10 with linux-ubuntu-modules-2.6.22 version 2.6.22-14.37
included driver r8169 gets loaded for device with Realtek RTL8101E chipset
which is a Fast Ethernet device.
Problem: Ethernet networking has poor performance (with 100Mbps Full
Duplex link transfer rates are
It is very easy to update manually the iwl4965 driver to the latest
build, follow these steps:
1) download the latest iwlwifi driver from www.linuxintelwireless.org
http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-1.1.21.tgz
2) install linux-source: sudo apt-get install linux-source
go in
Matt, thank you for commenting!
As I said in comment #31 after I upgraded iwlwifi drivers to version 1.1.20
(even though with that not-so-smart way) I haven't experienced the described
problem any more.
However, since ubuntu packages ship with an older version of the drivers, users
not manuall
29 matches
Mail list logo
