[Bug 559890] Re: Mythvideo segfault if I try to playback m2ts video file

Please close this, the problem has disappeared after a mythtv upgrade (0.23-fixes). Rune -- Mythvideo segfault if I try to playback m2ts video file https://bugs.launchpad.net/bugs/559890 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -

[Bug 559925] Re: Mythvideo segfault if I try to playback m2ts video file

Please close this, the problem has disappeared after a mythtv upgrade (0.23-fixes). Rune -- Mythvideo segfault if I try to playback m2ts video file https://bugs.launchpad.net/bugs/559925 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 559925] Re: Mythvideo segfault if I try to playback m2ts video file

The link is wrong, https://bugs.launchpad.net/bugs/559890 points to the same segfault using autobuilds. -- Mythvideo segfault if I try to playback m2ts video file https://bugs.launchpad.net/bugs/559925 You received this bug notification because you are a member of Ubuntu Bugs, which is subscrib

[Bug 559925] Re: Mythvideo segfault if I try to playback m2ts video file

The segfault also happens with the latest 0.23 packages from weeklybuilds. I initially registered bug https://bugs.launchpad.net/bugs/559925, but since it was automatically closed I removed weeklybuilds packages and reinstalled the lucid packages to have a valid bug report. -- Mythvideo segfaul

[Bug 559925] Re: Mythvideo segfault if I try to playback m2ts video file

** Visibility changed to: Public -- Mythvideo segfault if I try to playback m2ts video file https://bugs.launchpad.net/bugs/559925 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.co

[Bug 559890] Re: Mythvideo segfault if I try to playback m2ts video file

** Visibility changed to: Public -- Mythvideo segfault if I try to playback m2ts video file https://bugs.launchpad.net/bugs/559890 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 324295] Re: WOL does not work when using shutdown, but works with suspend (S3) and "halt -p"

** Attachment added: "uname-a.log" http://launchpadlibrarian.net/21962734/uname-a.log -- WOL does not work when using shutdown, but works with suspend (S3) and "halt -p" https://bugs.launchpad.net/bugs/324295 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 324295] Re: WOL does not work when using shutdown, but works with suspend (S3) and "halt -p"

** Attachment added: "lspci.vnvn.log" http://launchpadlibrarian.net/21962732/lspci.vnvn.log -- WOL does not work when using shutdown, but works with suspend (S3) and "halt -p" https://bugs.launchpad.net/bugs/324295 You received this bug notification because you are a member of Ubuntu Bugs, wh

[Bug 324295] Re: WOL does not work when using shutdown, but works with suspend (S3) and "halt -p"

I suspect I have the same problem with my mythtv frontend computer, after issuing "halt -p" I can wake the computer using WOL. When using "shutdown -h now" or XFCE shutdown menu choice I am not able to wake up the computer using WOL. I am unable to test S3 mode because suspend is broken on this c

[Bug 324295] Re: WOL does not work when using shutdown, but works with suspend (S3) and "halt -p"

** Attachment added: "version.log" http://launchpadlibrarian.net/21899005/version.log ** Attachment removed: "dmesg.log" http://launchpadlibrarian.net/21898986/dmesg.log -- WOL does not work when using shutdown, but works with suspend (S3) and "halt -p" https://bugs.launchpad.net/bugs/32

[Bug 324295] Re: WOL does not work when using shutdown, but works with suspend (S3) and "halt -p"

** Attachment added: "dmesg.log" http://launchpadlibrarian.net/21899156/dmesg.log -- WOL does not work when using shutdown, but works with suspend (S3) and "halt -p" https://bugs.launchpad.net/bugs/324295 You received this bug notification because you are a member of Ubuntu Bugs, which is sub

[Bug 324295] Re: WOL does not work when using shutdown, but works with suspend (S3) and "halt -p"

** Attachment added: "uname-a.log" http://launchpadlibrarian.net/21898999/uname-a.log -- WOL does not work when using shutdown, but works with suspend (S3) and "halt -p" https://bugs.launchpad.net/bugs/324295 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 324295] Re: WOL does not work when using shutdown, but works with suspend (S3) and "halt -p"

** Attachment added: "dmesg.log" http://launchpadlibrarian.net/21898986/dmesg.log -- WOL does not work when using shutdown, but works with suspend (S3) and "halt -p" https://bugs.launchpad.net/bugs/324295 You received this bug notification because you are a member of Ubuntu Bugs, which is sub

[Bug 324295] Re: WOL does not work when using shutdown, but works with suspend (S3) and "halt -p"

** Attachment added: "lspci-vnvn.log" http://launchpadlibrarian.net/21898991/lspci-vnvn.log -- WOL does not work when using shutdown, but works with suspend (S3) and "halt -p" https://bugs.launchpad.net/bugs/324295 You received this bug notification because you are a member of Ubuntu Bugs, wh

[Bug 324295] [NEW] WOL does not work when using shutdown, but works with suspend (S3) and "halt -p"

Public bug reported: Binary package hint: upstart I am not sure whether this is the fault of upstart, or some other package, but the problem is: Wake-on-LAN works in the following situations: 1) when suspending the system to S3 (using pm-suspend) 2) When issuing "sudo halt -p" from the command

[Bug 264881] Re: iwl3945 not able to associate with kernel 2.6.26 and 2.6.27

This bug is now solved for me ! I am using a Linksys WRT54Gv4 with DD-WRT v23 SP2 firmware, and have been experiencing problems with assoicating with this AP as described in the first comment in this bug report. But after resetting the NVRAM of my router, I am able to associate with my AP. This h

[Bug 264881] Re: iwl3945 not able to associate with kernel 2.6.26 and 2.6.27

@Alan For me it has not worked since 2.6.24-19-generic, including 2.6.27-9, with and without backport-modules, so I suspect that I am experiencing a different bug than you. Rune -- iwl3945 not able to associate with kernel 2.6.26 and 2.6.27 https://bugs.launchpad.net/bugs/264881 You received th

[Bug 264881] Re: iwl3945 not able to associate with kernel 2.6.26 and 2.6.27

Leann, Installing kernel 2.6.27-11-generic and linux-backport-modules for -11 from proposed does not solve my association problem. Regards Rune -- iwl3945 not able to associate with kernel 2.6.26 and 2.6.27 https://bugs.launchpad.net/bugs/264881 You received this bug notification because you a

[Bug 264881] Re: iwl3945 not able to associate with kernel 2.6.26 and 2.6.27

** Attachment added: "..using the zydas device" http://launchpadlibrarian.net/20543526/daemon.log-zydas -- iwl3945 not able to associate with kernel 2.6.26 and 2.6.27 https://bugs.launchpad.net/bugs/264881 You received this bug notification because you are a member of Ubuntu Bugs, which is su

[Bug 264881] Re: iwl3945 not able to associate with kernel 2.6.26 and 2.6.27

** Attachment added: "Excerpt of daemon log when using the iwl3945 chipset" http://launchpadlibrarian.net/20543509/daemon.log-iwl3945 -- iwl3945 not able to associate with kernel 2.6.26 and 2.6.27 https://bugs.launchpad.net/bugs/264881 You received this bug notification because you are a memb

[Bug 264881] Re: iwl3945 not able to associate with kernel 2.6.26 and 2.6.27

When testing with the Jantu 2.6.28 kernel, I am not able to connect to my AP with my iwl3945 device as well as the Zydas USB device. I tested with kernel https://edge.launchpad.net/ubuntu/jaunty/i386/linux- image-2.6.28-3-generic/2.6.28-3.4 My wireless network is not listed in n-m under any of the

[Bug 264881] Re: iwl3945 not able to associate with kernel 2.6.26 and 2.6.27

Leann, Using kernel 2.6.27-7-generic I am affected by https://bugs.launchpad.net/bugs/294667 when installing the backport modules, so I am unable with this kernel and backport module version. Using kernel 2.6.27-9-generic the backport modules loads fine, but I cannot associate with my AP as descr

Re: [Bug 264881] Re: iwl3945 not able to associate with kernel 2.6.26 and 2.6.27

Reloading iwl3945 module doesn't help for me. Geek87, did wireless work for you using 2.6.24-19-generic (in Hardy) ? Wireless was working fine on my computer until 2.6.24-19-generic, after this (in both Hardy and Intrepid) it has been completely broken. It does however work fine with an Zydas US

[Bug 264881] Re: iwl3945 not able to associate with kernel 2.6.26 and 2.6.27

Also, using 2.6.27-7 I get a different dmesg output than XaRs and myself (using 2.6.27-2, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264881/comments/3). I get lots of [12455.744842] iwl3945: No space for Tx [12455.744846] iwl3945: Error sending REPLY_LEDS_CMD: iwl3945_enqueue_hcmd

[Bug 264881] Re: iwl3945 not able to associate with kernel 2.6.26 and 2.6.27

Truxpin, My wireless connection worked fine until I upgraded to 24-21 in hardy, and later all intrepid kernels. Do you get similar errors in your syslog as I get ? See attached part of syslog where I attempt to associate (at a distance of 1 m from the AP). I can successfully associate with a Zyd

[Bug 259631] Re: Cannot open Private directory after a reboot

Steve, I ran 'sudo pam-auth-update --force' and checked both "eCryptfs Key/Mount Management" and "ConsoleKit Session Management" which were unchecked. After rebooting my laptop the ~/Private directory automounted. It was not intentional to keep an old pam.d configuration. I was already using e

[Bug 259631] Re: Cannot open Private directory after a reboot

** Attachment added: "common-session" http://launchpadlibrarian.net/18812515/common-session -- Cannot open Private directory after a reboot https://bugs.launchpad.net/bugs/259631 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ub

[Bug 259631] Re: Cannot open Private directory after a reboot

** Attachment added: "common-password" http://launchpadlibrarian.net/18812512/common-password -- Cannot open Private directory after a reboot https://bugs.launchpad.net/bugs/259631 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 259631] Re: Cannot open Private directory after a reboot

Dustin, Attached are the pam.d files. 'dpkg -l | grep ecryptfs': ii ecryptfs-utils 53-1ubuntu10 ecryptfs cryptographic filesystem (utilities ii libecryptfs0 53-1ubuntu10 ecryptf

[Bug 259631] Re: Cannot open Private directory after a reboot

Test Result 1. First, you need to figure out if you can decrypt your mount_passphrase, using 'ecryptfs-unwrap-passphrase ~/.ecryptfs/wrapped- passphrase LOGIN_PASSPHRASE'. Result: Received salt warning, command printed the hex digits and returned 0 2. Once you're able to successfully decrypt ~/.

Re: [Bug 259631] Re: Cannot open Private directory after a reboot

Thank you for your response, I will test this shortly. Please not that the output I posted is not the complete output of the unwrap command. In any case, is it possible to take the mount_passphrase and reverse it in order to compare it to the original login_passphrase ? Or can one mount_passphras

[Bug 259631] Re: Cannot open Private directory after a reboot

I have been running Intrepid since alpha3, and installed it using the command line instructions in the release notes. I did however already have ecryptfs as I already used it in a more manual way. (adding the passphrase=login password using ecyprfs-manager). When running 'ecryptfs-unwrap-passphras

[Bug 259631] Re: Can open Private directory after a reboot

Dustin, ecryptfs-unwrap-passphrase ~/.ecryptfs/wrapped-passphrase [LOGIN_PASSPHRASE] (with my actual login password) returns Unable to read salt value from user's .ecryptfsrc file; using default fa0ec2d.. Clicking the link in ~/Private after this does not mount the directory, and the co

[Bug 259631] Re: Can open Private directory after a reboot

The bug "Can't open Private Directory after reboot" affects me as well. I am positive that I have the same passphrase as my login password, and get the same error message "keyctl_search: Required key not available" Rune -- Can open Private directory after a reboot https://bugs.launchpad.net/b

[Bug 260339] Re: iwl3945 not able to associate with kernel above 2.6.24-19-generic

I've added a bug against 2.6.26 and 2.6.27 as well, this bug contains dmesg output for both 2.6.24 and .27. Please see bug https://bugs.launchpad.net/bugs/264881 Regards, Rune -- iwl3945 not able to associate with kernel above 2.6.24-19-generic https://bugs.launchpad.net/bugs/260339 You receiv

[Bug 264881] Re: iwl3945 not able to associate with kernel 2.6.26 and 2.6.27

I tested a bit further with as Wireless USB device, reported by lsusb as a "ZyDAS 802.11b/g USB2 WiFi". With this device I can associate with my network using kernel 2.6.27-2. Please note that nm-applet lists my network (with a bar of around 80%) under the Zydas device, but the network is not lis

[Bug 264881] Re: iwl3945 not able to associate with kernel 2.6.26 and 2.6.27

** Attachment added: "nm-password.png" http://launchpadlibrarian.net/17341662/nm-password.png -- iwl3945 not able to associate with kernel 2.6.26 and 2.6.27 https://bugs.launchpad.net/bugs/264881 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed t

[Bug 264881] Re: iwl3945 not able to associate with kernel 2.6.26 and 2.6.27

** Attachment added: "syslog-2.6.24.19-generic" http://launchpadlibrarian.net/17341659/syslog-2.6.24.19-generic -- iwl3945 not able to associate with kernel 2.6.26 and 2.6.27 https://bugs.launchpad.net/bugs/264881 You received this bug notification because you are a member of Ubuntu Bugs, whi

[Bug 264881] Re: iwl3945 not able to associate with kernel 2.6.26 and 2.6.27

** Attachment added: "syslog-2.6.27-2-generic" http://launchpadlibrarian.net/17341656/syslog-2.6.27-2-generic -- iwl3945 not able to associate with kernel 2.6.26 and 2.6.27 https://bugs.launchpad.net/bugs/264881 You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 264881] Re: iwl3945 not able to associate with kernel 2.6.26 and 2.6.27

** Attachment added: "dmesg-2.6.24-19-generic" http://launchpadlibrarian.net/17341654/dmesg-2.6.24-19-generic -- iwl3945 not able to associate with kernel 2.6.26 and 2.6.27 https://bugs.launchpad.net/bugs/264881 You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 264881] Re: iwl3945 not able to associate with kernel 2.6.26 and 2.6.27

Leann, I've attached various logs that I hope can support the debugging. Some strange things (see nm-password.png): 1. When upgrading to intrepid, and booting into 27-2, nm-applet did not detect my network, but when I chose "connect to other wireless network" it reasks for the passphrase each

[Bug 264881] Re: iwl3945 not able to associate with kernel 2.6.26 and 2.6.27

** Attachment added: "syslog2" http://launchpadlibrarian.net/17295630/syslog2 ** Tags added: linux-2.6.27 ** Description changed: My iwl3945 card works fine when using kernel 2.6.24-19-generic an earlier, but after upgrading to 2.6.24-21-generic (on hardy) it is no longer able to assoc

[Bug 264881] [NEW] iwl3945 not able to associate with kernel 2.6.26 and 2.6.27

Public bug reported: My iwl3945 card works fine when using kernel 2.6.24-19-generic an earlier, but after upgrading to 2.6.24-21-generic (on hardy) it is no longer able to associate. After upgrading to Intrepid I am not able to associate with my wireless network with either 2.6.26-5 or 2.6.27-2.

[Bug 260339] Re: iwl3945 not able to associate with kernel above 2.6.24-19-generic

An typing error snuck into the last comment, please replace 2.6.19, 20 and 21 with 2.6.24-19,20 and 21 ** Attachment added: "syslog2" http://launchpadlibrarian.net/17295223/syslog2 -- iwl3945 not able to associate with kernel above 2.6.24-19-generic https://bugs.launchpad.net/bugs/260339 You

[Bug 260339] Re: iwl3945 not able to associate with kernel above 2.6.24-19-generic

I upgraded my system to Intrepid, and experience the same problems with kernel 2.6.27. I kept the 2.6.19 kernel on my system, and using this kernel I am still able to associate with my wireless network. Attached is syslog using kernel (uname -a): Linux rune-laptop 2.6.27-2-generic #1 SMP Thu Aug

[Bug 260339] Re: iwl3945 not able to associate with kernel above 2.6.24-19-generic

I have both linux-ubuntu-modules and linux-backports-modules installed (for both working kernel -19 as well as for -20 and -21 which is not working) Attatched is the result of modinfo iwl3945. Regards, Rune filename: /lib/modules/2.6.24-21-generic/updates/iwl3945.ko license:GPL au

[Bug 150175] Re: ATI Radeon driver does not accept custom PAL resolution

Unfortunately I am not able to retest using intrepid, since my mythfrontend now is diskless (based on mythbuntu-diskless). I also bought a new TV and now use DVI->HDMI output for mythtv. Rune -- ATI Radeon driver does not accept custom PAL resolution https://bugs.launchpad.net/bugs/150175 You r

[Bug 260339] Re: iwl3945 not able to associate with kernel above 2.6.24-19-generic

** Description changed: Binary package hint: linux-image-2.6.24-20-generic My iwl3945 card works fine when using kernel 2.6.24-19-generic an earlier, but after upgrading to 2.6.24-21-generic it is no longer able to associate. When testing with 2.6.24-20-generic it also fails to ass

[Bug 260339] Re: iwl3945 not able to associate with kernel above 2.6.24-19-generic

** Attachment added: "/var/log/syslog" http://launchpadlibrarian.net/16999350/syslog -- iwl3945 not able to associate with kernel above 2.6.24-19-generic https://bugs.launchpad.net/bugs/260339 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to U

[Bug 260339] [NEW] iwl3945 not able to associate with kernel above 2.6.24-19-generic

Public bug reported: Binary package hint: linux-image-2.6.24-20-generic My iwl3945 card works fine when using kernel 2.6.24-19-generic an earlier, but after upgrading to 2.6.24-21-generic it is no longer able to associate. When testing with 2.6.24-20-generic it also fails to associate. Attached

Re: [Bug 180619] Re: Xorg module VNC cores on keyboard input

I have switched to the x11vnc package, which works fine with latest Xorg (though I am not sure if it supports a login manager or if only existing X user sessions are available). Regards, Rune ** Attachment added: "unnamed" http://launchpadlibrarian.net/15443905/unnamed -- Xorg module VNC c

Re: [Bug 200950] Re: [iwl3945] network manager not able to associate to hidden SSID (scan_capa = 0x0)

Alexander, Please note that I also have a problem with Hidden SSID on another computer, running updated Ubuntu Hardy with the ipw2200 chipset, see bug https://bugs.launchpad.net/bugs/199679. So I have the same problems with two different computers with diff

Re: [Bug 199679] Re: [ipw2200] Cannot connect with network manager 0.6.6-0ubuntu1

Yes, I can confirm that associationg with a network with SSID hidden does not work. Associating with a network with SSID broadcast does work with hardy and the iwl driver. rune -- [ipw2200] Cannot connect with network manager 0.6.6-0ubuntu1 https://bugs.launchpad.net/bugs/199679 You received t

[Bug 192735] Re: mpd no access to soundcard using pulseaudio

No, I did only have this one line. There was a similar line without the "auth", but it was commented out. But after doing a apt-get remove --purge on all pulseaudio packages, and installing them again using "apt-get install pulseaudio pulseaudio-esound-compat pulseaudio-modules-gconf", and sta

[Bug 200950] Re: [iwl3945] network manager not able to associate

Note: Association problem described in the bug report for both computers (Kubuntu/iwl3945 and Ubuntu/ipw2200) are solved by enabling SSID broadcast. -- [iwl3945] network manager not able to associate https://bugs.launchpad.net/bugs/200950 You received this bug notification because you are a membe

[Bug 200950] Re: [iwl3945] network manager not able to associate

Network Manager can associate fine with my AP after I enabled SSID broadcast. Attached is the syslog after enabling SSID broadcast on the AP. Regards Rune ** Attachment added: "syslog" http://launchpadlibrarian.net/12607205/syslog -- [iwl3945] network manager not able to associate https://

[Bug 200950] Re: [iwl3945] network manager not able to associate

Note: My wireless AP does not broadcast the SSID. I will test with Broadcast enabled to see if nm can associate. -- [iwl3945] network manager not able to associate https://bugs.launchpad.net/bugs/200950 You received this bug notification because you are a member of Ubuntu Bugs, which is subscrib

Re: [Bug 192735] Re: mpd no access to soundcard using pulseaudio

After adding "load-module module-native-protocol-tcp auth-anonymous=1" to /etc/pulse/default.pa I cannot get pulseaudio to start. The above ine was insertet at de end of the config file. After rebooting the computer, pulseaudio (or ps aux | grep pulse) does not show pulse running. When starting

[Bug 200950] Re: [iwl3945] network manager not able to associate

** Attachment added: "Complete /var/log/syslog" http://launchpadlibrarian.net/12588813/syslog -- [iwl3945] network manager not able to associate https://bugs.launchpad.net/bugs/200950 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -

[Bug 200950] Re: [hardy] network manager not able to associate

** Attachment added: "daemon.log with network-manager logging" http://launchpadlibrarian.net/12569974/daemon.log%20network-manager -- [hardy] network manager not able to associate https://bugs.launchpad.net/bugs/200950 You received this bug notification because you are a member of Ubuntu Bugs

[Bug 200950] [NEW] [hardy] network manager not able to associate

Public bug reported: Binary package hint: network-manager System: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.04 DISTRIB_CODENAME=hardy DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)" uname -a: Linux rune-laptop 2.6.24-12-generic #1 SMP Sat Mar 8 02:29:24 UTC 2008 i686 GNU/Linux After the la

[Bug 180619] Re: Xorg module VNC cores on keyboard input

It seems like there is a similar bug reported for Debian in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444697 Rune -- Xorg module VNC cores on keyboard input https://bugs.launchpad.net/bugs/180619 You received this bug notification because you are a member of Ubuntu Bugs, which is subscr

[Bug 180619] Re: Xorg module VNC cores on keyboard input

this configuration ? Rune Evjen -- Xorg module VNC cores on keyboard input https://bugs.launchpad.net/bugs/180619 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

Re: [Bug 192735] Re: mpd no access to soundcard using pulseaudio

"paplay /usr/share/sounds/alsa/Front_Center.wav" results in audioble audio. Regards, Rune -- mpd no access to soundcard using pulseaudio https://bugs.launchpad.net/bugs/192735 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. --

Re: [Bug 192735] Re: mpd no access to soundcard using pulseaudio

t; mpd no access to soundcard using pulseaudio > https://bugs.launchpad.net/bugs/192735 > You received this bug notification because you are a direct subscriber > of the bug. > -- hilsen Rune Evjen mailto:[EMAIL PROTECTED] -- mpd no access to soundcard using pulseaudio https://bugs.launch

[Bug 192735] Re: mpd no access to soundcard using pulseaudio

I forgot to add the audio_output section of /etc/mpd.conf audio_output { type"pulse" name"My MPD PulseAudio" # server "localhost" # optional #sink"alsa_output" # optional } Rune -- mpd no access to soundcard using pul

[Bug 192735] [NEW] mpd no access to soundcard using pulseaudio

Public bug reported: Binary package hint: pulseaudio Version info: uname -r: 2.6.24-8-generic pulseaudio Version: 0.9.9-1ubuntu2 mpd : Version: 0.13.1-3ubuntu1 After changing from esound to pulseaudio, MPD is not able to access the sound card. MPD logs the following errors in /var/log/mpd/erro

Re: [Bug 86852] Re: Laptop does not wake up from S3 suspend mode

ake up from S3 suspend mode > https://bugs.launchpad.net/bugs/86852 > You received this bug notification because you are a direct subscriber > of the bug. > -- hilsen Rune Evjen mailto:[EMAIL PROTECTED] -- Laptop does not wake up from S3 suspend mode https://bugs.launchpad.net/bugs/86852 You r

[Bug 184670] Re: /etc/environment is not used when executing terminal commands

This problem is solved after the updates of today. -- /etc/environment is not used when executing terminal commands https://bugs.launchpad.net/bugs/184670 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list

[Bug 184670] /etc/environment is not used when executing terminal commands

er account. bash: iwconfig: command not found file /etc/environment contains: PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" LANG="en_US.UTF-8" It seems like the PATH environment variable from /etc/environment is not used. Rune Evjen ** Affects:

[Bug 86852] Re: Laptop does not wake up from S3 suspend mode

Resume works after upgrading to hardy. Touchpad works after resume as well after adding i8042.reset as a kernel booting option. -- Laptop does not wake up from S3 suspend mode https://bugs.launchpad.net/bugs/86852 You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 86852] Re: Laptop does not wake up from S3 suspend mode

Evgeny, thank you for your tip regarding the touchpad. Regarding my last post, my wireless network card is still detected and modules are loaded for it after resume, but KNetworkManager does not see the network interface. I have only upgraded the kernel, haven't upgraded to hardy as it seems myth

[Bug 86852] Re: Laptop does not wake up from S3 suspend mode

I am currently running Gutsy, but tested with the hardy kernel, using this link: http://ubuntuforums.org/showthread.php?t=646755 uname -a: Linux rune-laptop 2.6.24-3-generic #1 SMP Thu Jan 3 23:30:29 UTC 2008 i686 GNU/Linux Resume from suspend now works, but after resuming the touchpad and wirel

[Bug 151414] Re: Kernel 2.6.22-14-generic upgrade breaks video playback

This problem no longer applies to my laptop running kernel 2.6.22-14-generic. The only change to my system that was kernel-specific was the update of linux-ubuntu-modules-2.6.22-14-generic -- Kernel 2.6.22-14-generic upgrade breaks video playback https://bugs.launchpad.net/bugs/151414 You recei

[Bug 151414] Kernel 2.6.22-14-generic upgrade breaks video playback

Public bug reported: Binary package hint: linux-image-2.6.22-14-generic When booting 2.6.22-14-generic video playback is distorted (showing only a red/green pattern with lines). I have tested video playback with mythtv frontend application and Kaffeine. Also I notice a flicker in the X screen a

[Bug 150175] Re: ATI Radeon driver does not accept custom PAL resolution

There were numerous problems. 1. fglrx driver support tv-out through s-video, but has a bug which makes VideoOverlay/Xv useless (only covers top third of the screen). 2. I had problems enabling tv-out on the open source ati driver, my TV did not sync som I got a diagonal rolling picture. 3. Usin

[Bug 150175] Re: ATI Radeon driver does not accept custom PAL resolution

** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/9856415/Xorg.0.log -- ATI Radeon driver does not accept custom PAL resolution https://bugs.launchpad.net/bugs/150175 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu.

[Bug 150175] ATI Radeon driver does not accept custom PAL resolution

Public bug reported: Binary package hint: xserver-xorg-video-ati I am using a self-made VGA to SCART cable to connect my 32" TV to my mythbuntu mediacenter, because of the problems with Xv support on s-video output using the fglrx driver. The setup uses the radeon driver and a custom modeline to

[Bug 150175] Re: ATI Radeon driver does not accept custom PAL resolution

** Attachment added: "xorg.conf" http://launchpadlibrarian.net/9856413/xorg.conf -- ATI Radeon driver does not accept custom PAL resolution https://bugs.launchpad.net/bugs/150175 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu.

[Bug 86852] Re: Laptop does not wake up from S3 suspend mode

Wiki page says that the only solution is to remove the module, but I am not sure how to do this with ptya0, which is not a module but a pseudo-tty ? Hope this is useful. Regards, Rune Evjen -- Laptop does not wake up from S3 suspend mode https://launchpad.net/bugs/86852 -- ubuntu-bugs mailing

[Bug 86852] Re: Laptop does not wake up from S3 suspend mode

** Attachment added: "kern.log.0" http://librarian.launchpad.net/6494588/kern.log.0 -- Laptop does not wake up from S3 suspend mode https://launchpad.net/bugs/86852 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 86852] Re: Laptop does not wake up from S3 suspend mode

When I read kern0.log I noticed that it didnt't include the last two days, so here is ker.long if this helps you. Thanks for helping out! Rune ** Attachment added: "kern.log" http://librarian.launchpad.net/6494593/kern.log -- Laptop does not wake up from S3 suspend mode https://launchpad.n

[Bug 86852] Re: Laptop does not wake up from S3 suspend mode

** Attachment added: "sudo dmidecode" http://librarian.launchpad.net/6494570/sudo_dmidecode -- Laptop does not wake up from S3 suspend mode https://launchpad.net/bugs/86852 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 86852] Re: Laptop does not wake up from S3 suspend mode

** Attachment added: "sudo lspci -vvn" http://librarian.launchpad.net/6494569/sudo_lspci_-vvn -- Laptop does not wake up from S3 suspend mode https://launchpad.net/bugs/86852 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 86852] Re: Laptop does not wake up from S3 suspend mode

Thank you for your reply! BIOS is updated to latest version. (V2.03, 6 dec 2006) uname -a: Linux feisty-laptop 2.6.20-6-generic #1 SMP Mon Feb 5 15:42:24 CET 2007 i686 GNU/Linux ** Attachment added: "sudo lspci -vv" http://librarian.launchpad.net/6494567/sudo_lspci_-vv -- Laptop does not

[Bug 86852] Re: Laptop does not wake up from S3 suspend mode

** Attachment added: "dmidecode" http://librarian.launchpad.net/6494386/dmidecode.log -- Laptop does not wake up from S3 suspend mode https://launchpad.net/bugs/86852 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 86852] Attachments: Laptop does not wake up from S3 suspend mode

Looking through other S3 posts I attach the following: ** Attachment added: "lspci -vv" http://librarian.launchpad.net/6494371/lspci-vv.log -- Laptop does not wake up from S3 suspend mode https://launchpad.net/bugs/86852 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://list

[Bug 86852] Re: Laptop does not wake up from S3 suspend mode

** Attachment added: "dmesg" http://librarian.launchpad.net/6494384/dmesg.log -- Laptop does not wake up from S3 suspend mode https://launchpad.net/bugs/86852 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 86852] Re: Laptop does not wake up from S3 suspend mode

** Attachment added: "lspci -vvn" http://librarian.launchpad.net/6494383/lspci-vvn.log -- Laptop does not wake up from S3 suspend mode https://launchpad.net/bugs/86852 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 86852] Laptop does not wake up from S3 suspend mode

my hard driver every couple of minutes under edgy, so I went for running only feisty since it seems stable on my computer. I can provide any relevant log needed using Feisty kernels. My Feisty installation is stock except for running Compiz and VMWare server. Regards, Rune Evjen ** Affects: Ub