** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/26021399/Xorg.0.log
--
Suspend & Hibernate fails - Jaunty 9.04, Dell Inspiron 6000
https://bugs.launchpad.net/bugs/367815
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "lsmod.output.txt"
http://launchpadlibrarian.net/26021428/lsmod.output.txt
--
Suspend & Hibernate fails - Jaunty 9.04, Dell Inspiron 6000
https://bugs.launchpad.net/bugs/367815
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "syslog"
http://launchpadlibrarian.net/26021388/syslog
--
Suspend & Hibernate fails - Jaunty 9.04, Dell Inspiron 6000
https://bugs.launchpad.net/bugs/367815
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
** Attachment added: "dmesg.txt"
http://launchpadlibrarian.net/26021418/dmesg.txt
--
Suspend & Hibernate fails - Jaunty 9.04, Dell Inspiron 6000
https://bugs.launchpad.net/bugs/367815
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Public bug reported:
Linux sniff 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC
2009 i686 GNU/Linux
Suspend and Hibernate simply fails to work. ( focusing on Suspend )
I chose Suspend from the menu, screen fades to black, disk chirps slightly, and
I am presented with the "unlock" scree
That was the hint I needed. Mea culpa :(
/var/log/pm-suspend.log contained the lines:
/usr/lib/pm-utils/sleep.d/45vmware-stop suspend suspend:
/usr/lib/pm-utils/sleep.d/45vmware-stop: 34: Syntax error: "}" unexpected
Returned exit code 2.
Mon Apr 27 23:03:21 CEST 2009: Inhibit found, will not pe
** Summary changed:
- syndaemon gone after resume on intrepid
+ syndaemon gone after resume on intrepid and jaunty
** Tags removed: needs-xorglog
--
syndaemon gone after resume on intrepid and jaunty
https://bugs.launchpad.net/bugs/326117
You received this bug notification because you are a mem
emon()
{
if [ ! "$( pidof syndaemon )" ]; then
export DISPLAY=:0.0
sudo -u gaute syndaemon -d -t -i 2
fi
}
case "$1" in
thaw|resume)
resume_syndaemon
;;
*) exit $NA
;;
esac
exit 0
--
I
Better mimetype :)
** Attachment added: "Xorg.0.log.old.txt"
http://launchpadlibrarian.net/23625015/Xorg.0.log.old.txt
--
syndaemon gone after resume on intrepid
https://bugs.launchpad.net/bugs/326117
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Attachment added: "Xorg.0.log.old"
http://launchpadlibrarian.net/23624991/Xorg.0.log.old
--
syndaemon gone after resume on intrepid
https://bugs.launchpad.net/bugs/326117
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Here are both after a fresh restart, and one suspend/resume.
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/23624988/Xorg.0.log
--
syndaemon gone after resume on intrepid
https://bugs.launchpad.net/bugs/326117
You received this bug notification because you are a member of Ubu
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/22039291/Dependencies.txt
--
syndaemon gone after resume on intrepid
https://bugs.launchpad.net/bugs/326117
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
Public bug reported:
Binary package hint: xfree86-driver-synaptics
I have been digging into this for a while now, and I'm pretty certain it
has not been mentioned anywhere.
The situation:
Ubuntu 8.10, 2.6.27-9-generic, dell inspiron 6000, xserver-xorg-input-
synaptics 0.15.2-0ubuntu7
# cat /et
Status is still "Incomplete"..
Did I miss something?
** Attachment removed: "Xorg.0.log.old.txt"
http://launchpadlibrarian.net/23625015/Xorg.0.log.old.txt
--
syndaemon gone after resume on intrepid
https://bugs.launchpad.net/bugs/326117
You received this bug notification because you are a
"Try out the new rt2x00 module instead. This is the module that will
eventually be merged into the Linux kernel."
Unfortunately, the rt2x00 module seems pretty much unmaintained and is not
reported to support the Linux Wireless Extensions yet. I found some discussion
about this back in July:
htt
" Wedel said on 2007-03-25: (permalink)
I can confirm this bug. I have a rt2500 pcmcia card and i can not connect to
the network."
There is a big chance that your bug is not the same as this bug. Since you have
an RT2500 card, you could be suffering from
https://bugs.launchpad.net/ubuntu/+sou
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/34667799/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/34667800/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/34667801/ProcStatus.txt
** Attachm
Sorry guys, but I seem to be having this exact problem in the released
Karmic.
Dell vostro 1520.
Starting with hw switch off works fine.
Exactly same crash of smbios-wireless-ctl as in comment #56
( posted as Bug #464449 )
Perhaps just need to blacklist vostro 1520 ?
Haven't looked into how th
Just what I was doing, and it seems to have solved the problem.
Found it mentioned in Bug# 441768
V1520A04-32_64.exe did the trick.
Thanks for the quick response anyway :)
--
[Dell Latitude D430, iwl3945] Wireless can't be activated after disabling kill
switch
https://bugs.launchpad.net/bugs
spend
#LidSwitchIgnoreInhibited=yes
$ dconf read
/org/gnome/settings-daemon/plugins/power/lid-close-suspend-with-external-monitor
true
$ systemd-inhibit --list --mode=block
Who: gdm (UID 121/gdm, PID 5935/gsd-power)
What: handle-lid-switch
Why: Multiple displays attached
Mode: block
Who:
I've got this bug on every laptop in the household :-(
an Eee PC 1005HA, an older dell inspiron and my own dell Vostro V131.
I _think_ they all have Intel graphics
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Just to chime in about 1.5.99.902-0ubuntu5.
No crashes for 3 days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/956071
Title:
Xorg crashed with SIGSEGV in XIGetDeviceProperty()
To manage notificat
Public bug reported:
The python3-tqdm (version 4.66.2-2) package is created with version
0.0.0 as the internal version specifier, meaning any attempt at using
Python to check it against a version will fail. I have a python script
using pkg_resources.require() / packaging.requirements which require
Public bug reported:
Binary package hint: unattended-upgrades
DISCLAIMER: I don't code python, and don't usually post patches. So
please bear with me if I stick my foot in my mouth.
BACKGROUND: I have unattended-upgrades running on edgy with a well-
working setup. apache2-common didn't get upgra
Public bug reported:
Binary package hint: apt
DISCLAIMER: I don't code python, and don't usually post patches. So
please bear with me if I stick my foot in my mouth.
BACKGROUND: I have unattended-upgrades running on edgy with a well-
working setup. apache2-common didn't get upgraded automaticall
See aditional info at the parallel bug report
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/133552
I might be best if it was unattended-upgrade honouring a new config
option to produce debug logging, but not debug output to console.
--
Config option to enable debug logging
https://bugs.laun
The line
+ unattended-upgrade --debug
could be
+ unattended-upgrade --debug > /dev/null 2>&1
because unattended-upgrade in debug mode gives extra output "Done
downloading", generating cron mail.
Based on this it might be a better option if unattended-upgrade itself
honoured a new config option
If packages held back by conffile prompt are shown in the logs w/o
debug, I'm personally OK. I can only note that there is still no way to
run with --debug enabled without modifying the /etc/cron.daily/apt
script - but personally, I don't need this. Case closed.
--
Config option to enable debug l
ut by
configuration directive in /etc/apt/apt.conf.d/...
Med vennleg helsing / Best regards
Gaute Lund
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Michael Vogt
> Sent: Tuesday, March 11, 2008 10:01 AM
> To: [EMAIL PROTECTED]
> S
Agree: A more stripped-down grub2-package is appropriate for servers.
Also, for either servers or desktops: There should be a setting in
/etc/default/grub, called GRUB_RECORDFAIL_TIMEOUT or
GRUB_TIMEOUT_AFTER_BOOTFAIL or something. This is today effectively hard
coded to -1 (forever). And it is th
30 matches
Mail list logo
