Well, it happened again, and after reboot I tailed a few log files and
saw nothing too indicative (to me), so I plan B'd it and copied all the
log files with modification times around the lock up. They're tarred,
bzipped, and attached.
I hope you see something I didn't.
** Attachment added: "Log
I can confirm this problem; my HP/Compaq nc8230 with an internal and
external battery, and I have the same problem (see attachment).
Moreover, this wasn't always an issue; with KDE 4.1 this image offset
didn't happen.
The same thing occurs whether the widget is on the desktop or in the
panel.
**
I can confirm this issue. Also, at some point, clicking on the message
*did* cancel the suspend; I can't remember if this is while I was
running KDE 4.2 from the PPA or after 4.2 entered general release.
--
[KDE] click to block auto-suspend does not work.
https://bugs.launchpad.net/bugs/356924
Y
Looking through old bug reports, I noticed and remembered this one.
This hasn't happened in months; no hardware or major software changes
(other than updates from repository).
This ticket can be closed.
--
X(?) locks up after a few minutes
https://bugs.launchpad.net/bugs/287648
You received thi
I was actually running apt-get from the command line (sudo apt-get
update && sudo apt-get dist-upgrade) and got the Python-2.5 crash -- no
interruptions or errors in the updates, though.
--
Using Adept, upgrade - python2.5 crashed with DBusException in call_blocking()
https://bugs.launchpad.net/b
Well, it didn't happen for about two weeks, but it happened against last
Thursday(-ish). I'll check log files and see what I can find, and I'll
definitely check them after I reboot next time.
On Fri, Nov 7, 2008 at 10:25 AM, Daniel Hahler <[EMAIL PROTECTED]>
wrote:
> Do you still think it gets t
Public bug reported:
When I start a Windows XP VM in virtualbox, everything runs fine for
10-15 minutes, then X/KDE/something stops responding. Already-running
processes continue to work, and when I move the mouse the pointer moves
around the screen (so it's not simply a failure to redraw), but c
OK, I'm not sure how to modify this, but about an hour after I reported
this, it happened again without virtualbox having been started since
boot. It would appear to be an X.org issue that's triggered by (among
other things) virtualbox?
--
X(?) locks up after a few minutes
https://bugs.launchpad
A further followup: trying to join WEP & unencrypted networks via
command-line (sudo iwconfig eth1 ...) also does not work, so this is not
(just) a problem with knetworkmanager but with ipw2200 and/or the
kernel.
Unless I'm talking out of my [censored].
--
ipw2200 driver no longer works with wp
I am also having this issue, except it appears to apply to ALL 802.11
networks, not just WPA. Some dumps:
[EMAIL PROTECTED]:~$ dmesg | grep ipw2200
[ 31.284166] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver,
1.2.2kmprq
[ 31.284174] ipw2200: Copyright(c) 2003-2006 Intel Corporation
Just tried creating an /etc/modprobe.d/ipw2200 with the line "option
ipw2200 associate=0". I no longer get the "Failed to send
SYSTEM_CONFIG" errors, but neither does it connect (to anything).
The hardware I'm using, incidentally, is an HP/Compaq nc8230, and the
wireless radio status light doesn'
I actually was connected to a WPA2 network a few weeks ago with no issues,
though I didn't think about it until I saw this e-mail.
I'm using Kubuntu Jaunty, up-to-date, with the Network Manager widget as the
front end for networkmanager.
On Sun, Jul 12, 2009 at 12:19 AM, Alsandair Sneachta <
alsa
Public bug reported:
This error occurred during a release upgrade from Ubuntu 13.10 to 14.04
alpha.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python3-plainbox 0.4-4
ProcVersionSignature: Ubuntu 3.5.0-47.71-generic 3.5.7.30
Uname: Linux 3.5.0-47-generic x86_64
NonfreeKernelModules:
13 matches
Mail list logo
