The problem is gone on version 2.6.31-1.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: linux-image-2.6.26-2-amd64
Version: 2.6.26-19lenny1
Severity: important
I'm using an Asus A8V motherboard, which has an onboard VIA VT8233/A/8235/8237
AC97 Audio Controller (not sure, just
picket it from lspci). I updated my kernel to 2.6.30-bpo.2-amd64, from
lenny-backports, so I cou
Nico Golde wrote:
This doesn't look like a bug in obconf to me but in lxde
common as it starts openbox with:
openbox --config-file $XDG_CONFIG_HOME/openbox/lxde-rc.xml
I guess in your case $XDG_CONFIG_HOME seems to be empty.
obconf then gets this path by gdk_x11_get_xatom_by_name("_OB_CONFIG
Package: obconf
Version: 2.0.3-3
Severity: normal
When running obconf under a lxde session (lxsession-lite), I get the
following error message on a popup dialog whenever I try to change
something: "An error occurred while trying to save the config file
'/openbox/lxde-rc.xml'". The command line o
The error also occurs with linux-image-2.6.28-11-versatile from
http://launchpadlibrarian.net/25604477/linux-image-2.6.28-11-versatile_2.6.28-11.42_armel.deb.
I guess the problem is on qemu...
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe"
Axel Allende Lira escreveu:
Hi there.
I managed to track the error while doing a removal for orphaned
packages. Here's the log:
r...@terrier:/home/axel# deborphan
libart-2.0-2
libgnomecups1.0-1
libgnomeprint2.2-data
libaiksaurus-1.2-data
libgail-common
r...@terrier:/home/axel# ap
Hi there.
I managed to track the error while doing a removal for orphaned
packages. Here's the log:
r...@terrier:/home/axel# deborphan
libart-2.0-2
libgnomecups1.0-1
libgnomeprint2.2-data
libaiksaurus-1.2-data
libgail-common
r...@terrier:/home/axel# apt-get remove `deborphan`
Lendo listas de pa
Axel Allende Lira escreveu:
It looks like updating qemu somehow fixed it... I can still downgrade in
case you need me to reproduce the bug again.
Nope, it didn't... but it's much less frequent now, I guess there's no
easy way to track that panic message. And now it waits f
Package: linux-image-2.6.26-2-versatile
Version: 2.6.26-15lenny3
Severity: critical
Justification: causes serious data loss
-- System Information:
Debian Release: 5.0.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: armel (armv5tejl)
Kernel: Linux 2.6.28-6-versatile
Locale: L
9 matches
Mail list logo
