[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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 computer. Log files for the second computer are attached. Rune ** Attachment added: dmesg.log http://launchpadlibrarian.net/21962727/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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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/324295 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 line. Note: I have not tested WOL from hibernate If I shut down the system from XFCE or by issuing sudo shutdown -h now I cannot wake up my system by sending a WOL packet from another computer. I really want to avoid using suspend as suspend support seems a bit unstable on my computer running as a mythbackend. I also understand that halt -p does not run the shutdown scripts in rc0, rc1 and rc6 which probably is not good for my system services. But it seems like that somewhere during the shutdown scripts WOL is disabled. I have tried setting NETDOWN=no in /etc/init.d/halt to prevent halt from bringing the network interfaces down. I enable WOL with a script in init.d, here is the script: #!/bin/sh ### BEGIN INIT INFO # Provides: wakeonlanconfig # Required-Start: $remote_fs $syslog # Required-Stop: $remote_fs $syslog # Default-Start: 2 3 4 5 S # Default-Stop: 1 6 # Short-Description: Set up Wake On Lan ### END INIT INFO ETHTOOL=/usr/sbin/ethtool DEV=eth1 case $1 in start) echo -n Setting $DEV to wakeonlan... $ETHTOOL -s $DEV wol g; echo done.;; stop) ;; esac exit 0 The Wakeonlan script is run at the following runlevels: locate wakeonlan /etc/init.d/wakeonlanconfig /etc/rc0.d/K20wakeonlanconfig /etc/rc1.d/K20wakeonlanconfig /etc/rc2.d/S20wakeonlanconfig /etc/rc3.d/S20wakeonlanconfig /etc/rc4.d/S20wakeonlanconfig /etc/rc5.d/S20wakeonlanconfig /etc/rc6.d/K20wakeonlanconfig /etc/rcS.d/S20wakeonlanconfig ** Affects: upstart (Ubuntu) Importance: Undecided Status: New -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 has been tested with no encryption as well as WPA2. So, for me resetting the NVRAM of the AP made it possible to associate with kernels 2.6.24.19. 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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 described in comment 1 and onwards of this bug report (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/264881/comments/1). I have done some more testing on my laptop, and made the following observations: - I am unable to associate with my AP using the Intrepid Live CD - iwlist wlan0 scanning never lists my AP (but does list others, using both WEP and WPA encryprtion as well as no encrpytion) - A manual setup using wpasupplicant and /etc/network interfaces for key setup is not successfull - Using my AP, I am also not able to associate using no encryption. With my USB Zydas device my computer connects fine using all 2.6.26 and .27 kernels, but I did notice that after installing linux-backport- modules on 2.6.27-9 I was not able connect with the Zydas device. After removing backport-modules and rebooting I could connect with the Zydas device but not the integrated iwl3945 chipset. 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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 adapters. After choosing create new wireless network, I am not able to associate using both wireless adapters. Attached is excerpts for both network cards. When testing with another unencrypted AP, I can associate using the Zydas device but not the 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
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 USB device. Davidiam, can you please check if you have the same iwl hardware as me ? modinfo iwl3945: filename: /lib/modules/2.6.27-10-generic/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko license:GPL author: Copyright(c) 2003-2008 Intel Corporation version:1.2.26ks description:Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux srcversion: B8570227953474842B9209D alias: pci:v8086d4227sv*sd*bc*sc*i* alias: pci:v8086d4222sv*sd*bc*sc*i* alias: pci:v8086d4227sv*sd1014bc*sc*i* alias: pci:v8086d4222sv*sd1044bc*sc*i* alias: pci:v8086d4222sv*sd1034bc*sc*i* alias: pci:v8086d4222sv*sd1005bc*sc*i* depends:mac80211,led-class,cfg80211,rfkill vermagic: 2.6.27-10-generic SMP mod_unload modversions 586 parm: antenna:select antenna (1=Main, 2=Aux, default 0 [both]) (int) parm: disable:manually disable the radio (default 0 [radio on]) (int) parm: hwcrypto:using hardware crypto engine (default 0 [software]) (int) parm: debug:debug output mask (int) parm: disable_hw_scan:disable hardware scanning (default 0) (int) parm: queues_num:number of hw queues. (int) parm: qos_enable:enable all QoS functionality (int) lspci -vv (extract): 03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02) Subsystem: Intel Corporation Device 1011 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 220 Region 0: Memory at d200 (32-bit, non-prefetchable) [size=4K] Capabilities: [c8] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+ Address: fee0300c Data: 414a Capabilities: [e0] Express (v1) Legacy Endpoint, MSI 00 DevCap:MaxPayload 128 bytes, PhantFunc 0, Latency L0s 512ns, L1 unlimited ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset- DevCtl:Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta:CorrErr+ UncorrErr+ FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap:Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 128ns, L1 64us ClockPM+ Suprise- LLActRep- BwNot- LnkCtl:ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- LnkSta:Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- Capabilities: [100] Advanced Error Reporting ? Capabilities: [140] Device Serial Number 4d-ff-ca-ff-ff-de-18-00 Kernel driver in use: iwl3945 Kernel modules: 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Zydas USB stick without problems using the same computer. Rune ** Attachment added: 2.6.27-7-generic-syslog-part http://launchpadlibrarian.net/18865269/%202.6.27-7-generic-syslog-part -- 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 to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 failed: -28 and as an example I don't get phy0: Selected rate control algorithm 'iwl-3945-rs' Rune ** Attachment added: dmesg-grep-iwl3945 http://launchpadlibrarian.net/18867871/dmesg-grep-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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 ecyptfs before installing the Ubuntu Private directory feature, so maybe this is the reason why my pam.d setup was different, although I cannot recollect wheter I was given the option to keep the pam.d confirguration or install the package maintainer version during upgrade. Anyway, thank you Steve and Dustin for solving this! Regards, Rune -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 ecryptfs cryptographic filesystem (library) ' dpkg -l | grep pam' ii bogofilter 1.1.7-1ubuntu1 a fast Bayesian spam filter (dummy package) ii bogofilter-bdb 1.1.7-1ubuntu1 a fast Bayesian spam filter (Berkeley DB) ii bogofilter-common 1.1.7-1ubuntu1 a fast Bayesian spam filter (common files) ii libpam-ck-connector 0.2.10-1ubuntu8 ConsoleKit PAM module ii libpam-gnome-keyring2.24.1-0ubuntu1 PAM module to unlock the GNOME keyring upon ii libpam-modules 1.0.1-4ubuntu5 Pluggable Authentication Modules for PAM ii libpam-runtime1.0.1-4ubuntu5 Runtime support for the PAM library ii libpam0g 1.0.1-4ubuntu5 Pluggable Authentication Modules library ii python-pam0.4.2-12ubuntu2 A Python interface to the PAM library ** Attachment added: common-auth http://launchpadlibrarian.net/18812503/common-auth -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 ~/.ecryptfs/wrapped- passphrase, run ecryptfs_insert_wrapped_passphrase_into_keyring ~/.ecryptfs/wrapped-passphrase LOGIN_PASSPHRASE'. Result: Received salt warning, and Inserted auth tok with sig [xx...x] into the user session keyring 3. You can list the id's of the keys in the keyring using: 'keyctl show'. Result: keyctl shows two user keys, one match to the result of the command 'ecryptfs_insert_wrapped_passphrase_into_keyring..' and another key. (Note: I already had used ecryptfs earlier in a more manual way for other directories, is the other key my old key and is this creating the problem with automount after reboot ?) 4. Now that you have the passphrase in the keyring, you should be able to mount your encrypted private directory with 'mount.ecryptfs_private'. Result: Using the 'mount.ecryptfs_private' command I can succsessfully mount (and decrypt the contents of) my ~/Private directory. 5. Reboot persistency After applying the above commands and accessing ~/Private, I rebooted and ran 'mount.ecryptfs_private' which again gave the error keyctl_search: Required key not available 'keyctl show' does not list my key, only my old key (see 3). After adding it with 'ecryptfs-insert-wrapped-passphrase-into-keyring ~/.ecryptfs/wrapped-passphrase LOGIN_PASSWORD' and running 'mount.ecryptfs_private' again the ~/Private directory is mounted ok. 6. Summary So it seems like the problem for me is that my wrapped passphrase is not automatically added into the keyring. Is this because I have two keys ? (See note in 3) In another computer I use this is working fine, but on that computer I didn't use ecryptfs prior to using the Ubuntu Private directory feature. Regards, Rune -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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-passphrase' I the message Unable to read salt value from user's .ecryptfsrc file; using default fa0ec2dfef0ab60d305d97d36a5c and the fa0... part is the actual response, which is not my password. 'echo $?' gives 0 I have no funny characters in my login phrase and quoting it does not make a difference to the output. Regards, Rune -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
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_passphrase be generated from different login passwords ? Rune 2008/10/21 Dustin Kirkland [EMAIL PROTECTED] Rune- That fa5c value is your *mount* passphrase, which you have just published to the internet. Consider any data there compromised. Guys- There are 2 passphrases involved. 1) There's your login_passphrase (what you use to login to the system) 2) And there's your mount_passphrase (what is used to mount the ~/Private directory and encrypt/decrypt the data there) When you successfully login to your system, a PAM module in the authentication stack called pam_ecryptfs takes your login_passphrase, and uses that to decrypt a file, ~/.ecryptfs/wrapped-passphrase, which contains your mount_passphrase. If that file is successfully decrypted, your decrypted mount_passphrase will be inserted into your kernel keyring. Then, pam_ecryptfs will attempt to run /sbin/mount.ecryptfs_private, which will try to mount your ~/Private directory using the passphrase which was added to the keyring. If the mount_passphrase not able to be retrieved and added to the kernel keyring, you will get the keyctl_search: Required key not available error. This is what should happen automatically. To find out where the problem is, you can perform each of these steps manually. First, you need to figure out if you can decrypt your mount_passphrase, using 'ecryptfs-unwrap-passphrase ~/.ecryptfs/wrapped-passphrase LOGIN_PASSPHRASE'. You will probably get the salt warning, and then if it succeeds, it will print the mount_passphrase to the screen. When you ran ecryptfs-setup-private, you were able to either choose your own mount_passphrase or have one generated for you. If you had one generated for you, it would be 128-bits of random data, represented by a string of hexadecimal digits. In any case, if ecryptfs-unwrap- passphrase is able to print it to screen, that's good. Check the exit code (echo $?) immediately after running ecryptfs-unwrap-passphrase, and ensure that it's 0. Otherwise, your wrapped-passphrase file is probably encrypted using a different password than the one you supplied. Once you're able to successfully decrypt ~/.ecryptfs/wrapped-passphrase (and please don't post your passphrases here), run 'ecryptfs_insert_wrapped_passphrase_into_keyring ~/.ecryptfs/wrapped- passphrase LOGIN_PASSPHRASE'. This will add the passphrase to the kernel keyring. You can list the id's of the keys in the keyring using: 'keyctl show'. Note that you might need to install the 'keyutils' package. Now that you have the passphrase in the keyring, you should be able to mount your encrypted private directory with 'mount.ecryptfs_private'. If you're still getting keyctl_search: Required key not available, then the wrong passphrase has been inserted into your keyring. You can check what key mount.ecryptfs_private expects with 'cat ~/.ecryptfs/Private.sig'. This signature should match the signature of the key in your keyring, as shown by 'keyctl show'. I would very much appreciate it if the people on this bug experiencing this problem could walk through these steps and please tell me where you are experiencing the failure. :-Dustin ** Changed in: ecryptfs-utils (Ubuntu) Assignee: (unassigned) = Dustin Kirkland (kirkland) Status: Invalid = Incomplete -- Cannot open Private directory after a reboot https://bugs.launchpad.net/bugs/259631 You received this bug notification because you are a direct subscriber of the bug. -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 commands mount.ecryptfs_private and ecryptfs-mount-private still gives the error message keyctl_search: Required key not available. ls -la ~/.ecryptfs shows: drwx-- 2 rune rune 4096 2008-10-14 14:26 . drwxr-xr-x 70 rune rune 4096 2008-10-20 08:51 .. -rw-r--r-- 1 rune rune0 2008-10-14 14:26 auto-mount -rw-r--r-- 1 rune rune0 2008-10-14 14:26 auto-umount -rw-r--r-- 1 rune rune 17 2008-10-14 14:26 Private.sig -r 1 rune rune 48 2008-10-14 14:26 wrapped-passphrase Rune -- Can 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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/bugs/259631 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 listed beneath the intel integrated chipset (network name r-stue, see attached png). Also note that nm-applet shows no bars in the tray icon, but my wireless network connection trought the zyda device is okay, and iwconfig reports this: wmaster0 no wireless extensions. wlan0 IEEE 802.11abg ESSID: Mode:Managed Frequency:2.447 GHz Access Point: Not-Associated Bit Rate:54 Mb/s Tx-Power=15 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Power Management:off Link Quality=63/100 Signal level:-69 dBm Noise level=-97 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 wmaster1 no wireless extensions. eth2 IEEE 802.11bg ESSID:r-stue Mode:Managed Frequency:2.467 GHz Access Point: 00:14:BF:E1:C8:76 Bit Rate=54 Mb/s Tx-Power=0 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Power Management:off Link Quality=100/100 Signal level:32/100 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 ** Attachment added: nm-applet-2.png http://launchpadlibrarian.net/17357502/nm-applet-2.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 to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 tie, with a very log password prefilled in. My wireless network is not listed in the network list, but neighbor networks are. 2. Same thing happened when booting 24-19, but after a couple of times reentering the password it logged on to the wireless network (but during the process of reentering the password it show the long prefilled password as well) But with this kernel, my wireless network is listed in the network list (along with neighbor networks). Attached are the result of `cat /var/log/syslog | grep -i network` using both kernels, as well as dmesg output for both, and the screenshoit of the password dialogue. Regards, Rune ** Attachment added: dmesg-2.6.27-2-generic http://launchpadlibrarian.net/17341651/dmesg-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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 28 17:20:02 UTC 2008 i686 GNU/Linux The strangest thing is that when using 2.6.20, 21 and 27 my wireless network is not listed in nm-applets (but other networks are). When I use the nm-applet menu to connect it seems that it figures out what encryption it has, but it is missing on the list of wireless networks. -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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. When booting Intrepid with old hardy 2.6.24-19 kernel I can connect to my wireless network Attached is an extract of syslog with .27-2 I use WPA2 PSK encryption and the SSID is not hidden. Please also see bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/260339 regarding problems under hardy. Rune ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: linux-2.6.27 -- 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 to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 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. - Attached is an extract of syslog with 27-2 + When booting Intrepid with old hardy 2.6.24-19 kernel I can connect to + my wireless network + + Attached is an extract of syslog with .27-2 I use WPA2 PSK encryption and the SSID is not hidden. Please also see bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/260339 regarding problems under hardy. 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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 author: Copyright(c) 2003-2008 Intel Corporation version:1.2.26k description:Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux srcversion: 885D9CF474C789A0F9E9257 alias: pci:v8086d4227sv*sd*bc*sc*i* alias: pci:v8086d4222sv*sd*bc*sc*i* alias: pci:v8086d4227sv*sd1014bc*sc*i* alias: pci:v8086d4222sv*sd1044bc*sc*i* alias: pci:v8086d4222sv*sd1034bc*sc*i* alias: pci:v8086d4222sv*sd1005bc*sc*i* depends:mac80211,cfg80211 vermagic: 2.6.24-21-generic SMP mod_unload 586 parm: antenna:select antenna (1=Main, 2=Aux, default 0 [both]) (int) parm: disable:manually disable the radio (default 0 [radio on]) (int) parm: hwcrypto:using hardware crypto engine (default 0 [software]) (int) parm: debug:debug output mask (int) parm: disable_hw_scan:disable hardware scanning (default 0) (int) parm: queues_num:number of hw queues. (int) parm: qos_enable:enable all QoS functionality (int) -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 is an extract of syslog. What is weird is that with -20 and -21 my wireless network at home does not show in Network Manager, but other wireless networks do. It seems like everything is okay, except my own network is not detected. I use WPA2 PSK encryption and the SSID is not hidden. Rune ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 associate. Attached is an extract of syslog. What is weird is that with -20 and -21 my wireless network at home does not show in Network Manager, but other wireless networks do. It seems like everything is okay, except my own network is not detected. I use WPA2 PSK encryption and the SSID is not hidden. + network-manager version: + network-manager: + Installed: 0.6.6-0ubuntu5 Rune -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
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 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
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.https://bugs.launchpad.net/bugs/199679 So I have the same problems with two different computers with different Wireless chipsets after the n-m update. Regards, Rune -- [iwl3945] network manager not able to associate to hidden SSID (scan_capa = 0x0) https://bugs.launchpad.net/bugs/200950 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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://bugs.launchpad.net/bugs/200950 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 starting up pulseaudio from the command line, I got everything working.
I now autostart pulseaudio in XFCE, and both mythtv and mpd shares the
sound card.
Mythtv is configured with ALSA:default,
and mpd with
audio_output {
# use the pulse output
type pulse
# name
name My Pulse Device
}
The only thing now is that I have to restart the mpd service, probably
because pulseaudio is is not available when the mpd script is run.
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 subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/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 latest network-manager update (early march 2008) using hardy, I cannot associate with any wireless networks. network-manager version: 0.6.6-0ubuntu1. Attatched is the logging to daemon.log by network-manager. This happens on two laptops, one using Ubuntu hardy with ipw2200 wireless driver, and one using Kubuntu Hardy with iwl3945. Logging attached is from the Kubuntu laptop. Using the Ubuntu Hardy computer (running gnome), I sometimes can associate if I use the kill switch or disable and enable wireless. Seems like this all depends on timing though, I can only associate in something like one out of 10 tries. Other computers have no problems associating with the AP. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- [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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
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 it manually from my user account I get: ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0 ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0 E: socket-server.c: bind(): Address already in use E: socket-server.c: bind(): Address already in use E: module.c: Failed to load module module-native-protocol-tcp (argument: aut h-anonymous=1): initialization failed. E: main.c: Module load failed. E: main.c: failed to initialize daemon. paplay /usr/share/sounds/alsa/Front_Center.wav gives the error Connection failure: Connection refused 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180619] Re: Xorg module VNC cores on keyboard input
I have the same issue after upgrading to hardy. Using the vnc module in xorg.conf worked in gutsy. I use this setup on my mythbuntu based mediacenter, and only have a XFCE desktop installed. This is also how default mythbuntu install enables VNC access. Shouldn't it be possible to use 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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/errors.log: No protocol specified E: client-conf-x11.c: XOpenDisplay() failed *** PULSEAUDIO: Unable to connect: Access denied By giving xhost + and restarting mpd the XOpenDisplay() error disappears, but the error regarding PULSEAUDIO still persists. This happend using the latest ubuntu gutsy as of 16.02.2008, as well as the current Hardy. Pulseaudio was installed using https://wiki.ubuntu.com/PulseAudio on gutsy, and the system was upgraded to hardy using update-manager. I have added mpd and root to all pulseaudio groups (pulse, pulse-access, pulse-rt), but this did not solve the problem. Xine works using native pulse output and mythtv works using ALSA:default output device. Regards, Rune ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192735] Re: mpd no access to soundcard using pulseaudio
I forgot to add the audio_output section of /etc/mpd.conf
audio_output {
typepulse
nameMy MPD PulseAudio
# server localhost # optional
#sinkalsa_output # optional
}
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.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 192735] Re: mpd no access to soundcard using pulseaudio
MPD is running as the user mpd. I manually added mpd to the pulseaudio groups. This is default in the mpd ubuntu package as far as I can remebember from when I installed it. Rune On 17/02/2008, Luke Yelavich [EMAIL PROTECTED] wrote: I'm assuming from where mpd is logging, that you are running mpd as root, orfrom /etc/init.d/mpd. Have you tried running it as a user? By default, PulseAudio runs as the user, which is why mpd cannot find it. ** Changed in: pulseaudio (Ubuntu) Status: New = Incomplete -- 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.launchpad.net/bugs/192735 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 86852] Re: Laptop does not wake up from S3 suspend mode
It works on my Lenovo 3000 N100 type 0768-BJG , with all kernels (e.g 2.6.24-X-generic) after upgrading to Hardy. It also worked using Gutsy with the 2.6.24-X-generic series kernels, except for the wireless network card which didn't work after resuming from suspend. Robert Schumann, is your Lenovo the same type/model ? Rune On 25/01/2008, Evgeny nekr0z Kuznetsov [EMAIL PROTECTED] wrote: Works for me, though... $ uname -a Linux evgkuz 2.6.24-5-generic #1 SMP Thu Jan 24 19:29:14 UTC 2008 x86_64 GNU/Linux -- Laptop does not wake 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 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 184670] /etc/environment is not used when executing terminal commands
Public bug reported: I couldn't find a package that provides /etc/environment using dpkg --search environment Applies to updated hardy as of 20.01.2008 uname-a: Linux rune-laptop 2.6.24-4-generic #1 SMP Mon Jan 14 17:30:39 UTC 2008 i686 GNU/Linux When executing terminal commands in konsole, I get: Command 'iwconfig' is available in '/sbin/iwconfig' The command could not be located because '/sbin' is not included in the PATH environment variable. This is most likely caused by the lack of administrative priviledges associated with your user 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: ubuntu Importance: Undecided Status: New -- /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 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
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 mythtv-frontend is not available. Is your network card fine in (K)NetworkManager after resume ? If so, have you upgraded just your kernel or the complete system ? Rune -- 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 is the bug contact for Ubuntu. -- 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
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 is the bug contact for Ubuntu. -- 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
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 wireless is not working. The wireless interface name has changed from eth1 tom wlan0_rename after switching kernels, but the above link lists this as a registered bug. Wireless works before I suspend, lsmod shows: [EMAIL PROTECTED]:~$ lsmod | grep 3945 iwl3945 167400 0 mac80211 163352 1 iwl3945 After resuming the same modules are listed, and dmesg shows that the card is detected, but NetworkManager fails to identify it. Maybe this can be solved easily ? Attatched: dmesg - which shows an error message after resuming regarding the touchpad. My Laptop is a Lenovo 3000 N100 type 0768-BJG. Rune ** Attachment added: dmesg http://launchpadlibrarian.net/11271433/dmesg_log -- 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 is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 at regular intervals. When booting 2.6.22-13-generic everything is normal. I am using the nvidia-glx-new video driver. ** Affects: linux-source-2.6.22 (Ubuntu) Importance: Undecided Status: New -- Kernel 2.6.22-14-generic upgrade breaks video playback https://bugs.launchpad.net/bugs/151414 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 set up a PAL resolution to my TV using the radeon driver to send a composite sync signal so that my TV can understand the signal properly. This setup worked until I upgraded xserver-xorg-video-ati from 1:6.6.193ubuntu1 to 1:6.7 versions (along with the rest of the xorg) When starting X it reports: (WW) RADEON(0): DDC2/I2C is not properly initialized (WW) RADEON(0): Mode 720x540PAL-Custom is out of range. (WW) RADEON(0): Valid FP modes must be between 320x200-640x480 (WW) RADEON(0): DDC2/I2C is not properly initialized and falls back to a 640*480 resolution. My xorg.conf has not changed during the upgrades. ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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. Using a custom vga to scart cable I got it working with the open source driver, until upgrading the -video-ati driver. The setup did not work with fglrx as the closed driver did not understand the composite part of the modeline (sending a composite sync signal instead of seperate h/v sync) As I understood from searching around, the open source tv-out support is restricted to NTSC an 800x600 resolution, which my TV didn't understand. I though all TV's needed a 720x576 signal of 50/60Hz ? -- 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. -- 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
I searched a bit and followed the guide in https://wiki.ubuntu.com/DebuggingKernelSuspend I captured the dmesg output and got 2 lines similar to the Wiki page: [1.814882] ACPI: (supports S0 S3 S4 S5) [1.815497] Magic number: 15:874:554 [1.815649] hash matches device ptya0 The 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 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
Public bug reported: This bug has occurred under the following setups: Ubuntu Edgy with 2.6.17.10-generic kernel Ubuntu Edgy with suspend2 patched kernel Ubuntu Feisty with 2.6.20-8-generic kernel Ubuntu Feisty with suspend2 patched 2.6.20-6-generic kernel It has been tested with nv and nvidia driver (nvidia-glx package). My laptop is a Lenovo 3000 N100 type 0768-BJG with the latest BIOS firmware. On Edgy I got dmesg error messages about DSDT table, but they dissappeared running feisty. Under Edgy the laptop does not resume, nothing happens except for giving me a unlock dialog from Gnome. In Feisty the laptop does suspend, but when i hit the power button to resume the sleep led disappears, the fan spins up and down and the cd-rom spins up for a couple of seconds and then nothing happens. The screen remains black and the computer does not respond. Hitting caps lock key does not light the Caps Lock led indication. Hibernation works using Feisty kernels without suspend2 patch, using stock nv driver and using nvidia driver when using agp=off as a kernel parameter. Hibernation does not work under Edgy. I got a mysterious tick sound from 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: Ubuntu Importance: Undecided Status: Unconfirmed -- 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] 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] 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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] 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 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
** 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
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.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: 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
