[Bug 969489] Re: lightdm tries (and fails) to start too early?
Avius: When lightdm fails to start, do you get sometimes X started up in safe mode as per Comment 2 from Serge ? Your problem seems different as your your logs show that lightdm can successfully start and connect to the X server, and something happens during your login. Relevant extract from your logs below: [+3.06s] DEBUG: Seat: Display server ready, starting session authentication [...] [+5.80s] DEBUG: Session pid=1330: Started with service 'lightdm', username 'avius' [+5.80s] DEBUG: Session pid=1032: Greeter start authentication for avius [+5.80s] DEBUG: Session pid=1330: Sending SIGTERM [+5.80s] DEBUG: Seat: Setting XDG_SEAT=seat0 [+5.80s] DEBUG: Session: Setting XDG_VTNR=7 [+5.80s] DEBUG: Session pid=1331: Started with service 'lightdm', username 'avius' [+5.80s] DEBUG: Got signal 15 from process 991 [+5.80s] DEBUG: Caught Terminated signal, shutting down Could your problem be related to authentication ? Is your system set to autologin? Have you tried logging into the console and running 'start lightdm'? As per comment #97, lightdm (which in turn starts X) can be started before the display kernel modules are fully loaded (creating a race). The problem is most apparent to people running Ubuntu from an SSD. On my PC, the one line fix delays the lightdm start sufficiently for the kernel display modules to be fully loaded. It's really working on my system: ls -ltr /var/log/Xorg* -rw-r--r-- 1 root root 69099 Sep 13 2013 /var/log/Xorg.failsafe.log.old -penultimate start of X into failsafe mode before performing the workaround -rw-r--r-- 1 root root 69514 Mar 8 14:17 /var/log/Xorg.failsafe.log - last start of X into failsafe mode while getting this down to a one liner in March -rw-r--r-- 1 root root 31975 Mar 28 19:11 /var/log/Xorg.0.log.old -rw-r--r-- 1 root root 30869 Mar 30 10:58 /var/log/Xorg.0.log There are other workarounds from other people in this thread, which seem to have the same effect - for example someone suggests in comment #114 to make the startup verbose, which seems to solve the problem for that person. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
Currently I've been running without issues with the following configuration in /etc/init/lightdm.conf since September 2013. [...] start on ((filesystem and runlevel [!06] and started dbus and plymouth-ready and stopped udevtrigger) # - one line fix or runlevel PREVLEVEL=S) [...] My configuration is: Ubuntu 12.04 64bit Intel SSD 335 Nvidia GTS 650 with NVIDIA drivers. lightdm version 1.2.3-0ubuntu2.4 Additionally, dependencies on the following were not helping to solve the problem: graphics-device-added PRIMARY_DEVICE_FOR_DISPLAY=1 - this event is not fired on my machine graphics-device-added - this event is fired too early - possibly on vesafb load - ligthdm crashes and the fallback mode kicks in. drm-device-added PRIMARY_DEVICE_FOR_DISPLAY=1 - is not fired on my machine -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
Adding some lines to /etc/init/lightdm.conf fixed the problem on my PC (Ubuntu 12.04): start on ((filesystem and runlevel [!06] and started dbus and plymouth-ready and (graphics-device-added PRIMARY_DEVICE_FOR_DISPLAY=1 #added or drm-device-added PRIMARY_DEVICE_FOR_DISPLAY=1 #added or stopped udevtrigger or container)) #added or runlevel PREVLEVEL=S) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
This happens sometimes on my machine: Ubuntu 12.04 64bit Intel SSD 335 Nvidia GTS 650 with NVIDIA drivers. lightdm version 1.2.3-0ubuntu2.3 Tracked it to a race issue - if NVRM module is loaded before lightdm starts, all is OK. (see logs in Post Scriptum) My current configuration in /etc/init/lightdm.conf: start on ((filesystem and runlevel [!06] and started dbus and plymouth-ready) or runlevel PREVLEVEL=S) Post Scriptum: Logs clearly showing that when lightdm is started before the NVRM module is loaded, and dies a horrible death: Sep 13 14:20:07 Pendragon kernel: [5.944960] ADDRCONF(NETDEV_UP): wlan0: link is not ready Sep 13 14:20:07 Pendragon kernel: [6.099801] init: lightdm main process (1127) terminated with status 1 Sep 13 14:20:07 Pendragon kernel: [6.509805] HDMI status: Codec=0 Pin=5 Presence_Detect=0 ELD_Valid=0 Sep 13 14:20:07 Pendragon kernel: [6.533772] HDMI status: Codec=1 Pin=5 Presence_Detect=0 ELD_Valid=0 Sep 13 14:20:07 Pendragon kernel: [6.557710] HDMI status: Codec=2 Pin=5 Presence_Detect=0 ELD_Valid=0 Sep 13 14:20:08 Pendragon kernel: [6.581717] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0 Sep 13 14:20:08 Pendragon kernel: [6.581814] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:03.0/:01:00.1/sound/card1/input10 Sep 13 14:20:08 Pendragon kernel: [6.581890] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:03.0/:01:00.1/sound/card1/input11 Sep 13 14:20:08 Pendragon kernel: [6.581954] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:03.0/:01:00.1/sound/card1/input12 Sep 13 14:20:08 Pendragon kernel: [6.582180] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:03.0/:01:00.1/sound/card1/input13 Sep 13 14:20:08 Pendragon kernel: [6.583236] nvidia :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 Sep 13 14:20:08 Pendragon kernel: [6.583243] nvidia :01:00.0: setting latency timer to 64 Sep 13 14:20:08 Pendragon kernel: [6.583247] vgaarb: device changed decodes: PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem Sep 13 14:20:08 Pendragon kernel: [6.583341] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 319.32 Wed Jun 19 15:51:20 PDT 2013 Sep 13 14:20:08 Pendragon kernel: [6.794290] init: udev-fallback-graphics main process (1380) terminated with status 1 Sep 13 14:20:08 Pendragon kernel: [6.951100] init: plymouth-stop pre-start process (1400) terminated with status 1 Sep 13 14:20:08 Pendragon kernel: [7.533643] cfg80211: Found new beacon on frequency: 2472 MHz (Ch 13) on phy0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 523143] Re: Wireless RFKILL defaults to on (wireless off) and can't be turned off.
Hello pcgaldo, My laptop actually has a hardware switch and the problem described here is not present with mainline. The bug described is specific to Ubuntu's dell-laptop kernel modules. I suggest that you file a separate bug. Best regards, Ciprian -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] Re: Wireless RFKILL defaults to on (wireless off) and can't be turned off.
** Tags added: lucid ** Tags removed: needs-upstream-testing -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] Re: Wireless RFKILL defaults to on (wireless off) and can't be turned off.
Hello Jeremy, I have tested the latest mainline kernel available for Lucid and the problem is not present (Linux ubuntu 2.6.32-02063212-generic #02063212 SMP Tue Apr 27 09:08:28 UTC 2010 x86_64 GNU/Linux). This bug is Ubuntu specific (and probably located in dell-wifi rfkill code). -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] Re: Wireless RFKILL defaults to on (wireless off) and can't be turned off.
apport information ** Tags added: apport-collected ** Description changed: I have a Dell Latitude E6400 with a rfkill switch on the right side of the laptop. Wireless RFKILL defaults to on (wireless off) and can't be turned off. I'm running: Linux ubuntu 2.6.31-19-generic #56-Ubuntu SMP Thu Jan 28 02:39:34 UTC 2010 x86_64 GNU/Linux You can see here that dell-wifi / dell-bluetooth default to Hard blocked:yes. I actually have just the physical switch listed as phy0 correctly shown with Hard blocked: no. cena...@ubuntu:~$ rfkill list 0: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: yes 1: dell-bluetooth: Bluetooth Soft blocked: no Hard blocked: yes 2: hci0: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no When I change the state of the physical switch both the dell-wifi and phy0 change state - but my wireless is still disabled. 0: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no 1: dell-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Seems to be fixed in 2.6.32 - rfkill is still listing 2 switches, but they are in sync and my WiFi works. Best regards, Cip + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. + Architecture: amd64 + ArecordDevices: + List of CAPTURE Hardware Devices + card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] +Subdevices: 2/2 +Subdevice #0: subdevice #0 +Subdevice #1: subdevice #1 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: cenache1495 F pulseaudio + CRDA: Error: [Errno 2] No such file or directory + Card0.Amixer.info: + Card hw:0 'Intel'/'HDA Intel at 0xf6adc000 irq 21' +Mixer name : 'Intel G45 DEVCTG' +Components : 'HDA:111d76b2,10280233,00100302 HDA:80862802,80860101,0010' +Controls : 24 +Simple ctrls : 15 + DistroRelease: Ubuntu 10.04 + InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha amd64 (20100405) + MachineType: Dell Inc. Latitude E6400 + Package: linux (not installed) + PccardctlIdent: + Socket 0: +no product info available + PccardctlStatus: + Socket 0: +no card + ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=/dev/sda3 loop=/hostname/disks/root.disk ro quiet splash + ProcEnviron: + PATH=(custom, no user) + LANG=en_US.utf8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 + Regression: Yes + RelatedPackageVersions: linux-firmware 1.34 + Reproducible: Yes + Tags: lucid networking regression-release needs-upstream-testing + Uname: Linux 2.6.32-21-generic x86_64 + UserGroups: + + dmi.bios.date: 05/11/2009 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A14 + dmi.board.name: 0W620R + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/11/2009:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0W620R:rvr:cvnDellInc.:ct8:cvr: + dmi.product.name: Latitude E6400 + dmi.sys.vendor: Dell Inc. ** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/46183940/AlsaDevices.txt -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/46183944/BootDmesg.txt -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] Card0.Amixer.values.txt
apport information ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/46183954/Card0.Amixer.values.txt -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] Card0.Codecs.codec.0.txt
apport information ** Attachment added: Card0.Codecs.codec.0.txt http://launchpadlibrarian.net/46183956/Card0.Codecs.codec.0.txt -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] AplayDevices.txt
apport information ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/46183941/AplayDevices.txt -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] Card0.Codecs.codec.2.txt
apport information ** Attachment added: Card0.Codecs.codec.2.txt http://launchpadlibrarian.net/46183960/Card0.Codecs.codec.2.txt -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] IwConfig.txt
apport information ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/46183976/IwConfig.txt -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/46183965/CurrentDmesg.txt -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] Lsusb.txt
apport information ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/46184027/Lsusb.txt -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] Lspci.txt
apport information ** Attachment added: Lspci.txt http://launchpadlibrarian.net/46184020/Lspci.txt -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] PciMultimedia.txt
apport information ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/46184028/PciMultimedia.txt -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/46184033/ProcCpuinfo.txt -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/46184040/ProcInterrupts.txt -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] UdevLog.txt
apport information ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/46184072/UdevLog.txt -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] ProcModules.txt
apport information ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/46184044/ProcModules.txt -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] UdevDb.txt
apport information ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/46184064/UdevDb.txt -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] RfKill.txt
apport information ** Attachment added: RfKill.txt http://launchpadlibrarian.net/46184049/RfKill.txt -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/46184113/WifiSyslog.txt -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] Re: Wireless RFKILL defaults to on (wireless off) and can't be turned off.
Hello Jeremy, I've run apport-collect on a kernel which has the bug - see above. -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] Re: Wireless RFKILL defaults to on (wireless off) and can't be turned off.
I have upgraded to Ubuntu 10.04 Beta 2. I can confirm now that the exact same problem is also present in 2.6.32-19-generic #28-Ubuntu SMP Linux Kernel, but does not appear with a mainline kernel loaded. It seems to be caused by one of the Ubuntu- specific RFKILL or dell-laptop patches. -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] Re: Wireless RFKILL defaults to on (wireless off) and can't be turned off.
I am still having the exact same problem with 2.6.31-20-generic. -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 477104] Re: After 9.10 grub update can not boot into Wubi install
Tall Guy, I've had a similar problem (running Vista) which was due to the fact that Windows Vista silently failed to overwrite C:\wubildr. Possible solution: Download wubildr again to your Desktop/Downloads folder first, and only then copy it over C:\wubildr using Explorer. You should get an User Account Control prompt this time asking you for permission to do that. On Wed, Mar 17, 2010 at 9:48 PM, Tall Guy tallguy...@gmail.com wrote: Agostino, Like RonG, I can manually boot into a low graphics mode using the following steps: sh:grublinux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda3 loop=/ubuntu/disks/root.disk ro sh:grubinitrd /boot/initrd.img-2.6.31-14-generic sh:grubboot When I replaced the wubildr from #90, nothing happened and I must still boot manually. -- After 9.10 grub update can not boot into Wubi install https://bugs.launchpad.net/bugs/477104 You received this bug notification because you are a direct subscriber of the bug. Status in GRand Unified Bootloader: New Status in “grub2” package in Ubuntu: Fix Committed Status in “grub2” source package in Lucid: Fix Committed Status in “grub2” source package in Karmic: Fix Committed Bug description: GRUB2 could not read past 4G on NTFS. The patch was http://launchpadlibrarian.net/37322976/debdiff, uploaded to karmic-proposed as 1.97~beta4-1ubuntu5. Test case: Install Ubuntu 9.10 using Wubi Install all available updates. Reboot into Ubuntu. Original report follows: Binary package hint: grub Installed ubuntu 9.10 using Wubi. Performed upgrades. After a grub update could not boot. Get screen: Try (hd0,0) : NTFS5: and then GNU GRUB version 1.97~1.97beta4 [ Minimal Bash-like line editing is supported ... sh:grub Online help does not work for this grub version. Need instructions to recover. I could try a new install, but may recreate the problem after update. Help. To unsubscribe from this bug, go to: https://bugs.launchpad.net/grub/+bug/477104/+subscribe -- Best regards Ciprian Enache -- After 9.10 grub update can not boot into Wubi install https://bugs.launchpad.net/bugs/477104 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 523143] Re: Wireless RFKILL defaults to on (wireless off) and can't be turned off.
** Tags added: karmic ** Tags removed: kernel-series-unknown -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] [NEW] Wireless RFKILL defaults to on (wireless off) and can't be turned off.
Public bug reported: I have a Dell Latitude E6400 with a rfkill switch on the right side of the laptop. Wireless RFKILL defaults to on (wireless off) and can't be turned off. I'm running: Linux ubuntu 2.6.31-19-generic #56-Ubuntu SMP Thu Jan 28 02:39:34 UTC 2010 x86_64 GNU/Linux You can see here that dell-wifi / dell-bluetooth default to Hard blocked:yes. I actually have just the physical switch listed as phy0 correctly shown with Hard blocked: no. cena...@ubuntu:~$ rfkill list 0: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: yes 1: dell-bluetooth: Bluetooth Soft blocked: no Hard blocked: yes 2: hci0: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no When I change the state of the physical switch both the dell-wifi and phy0 change state - but my wireless is still disabled. 0: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no 1: dell-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Seems to be fixed in 2.6.32 - rfkill is still listing 2 switches, but they are in sync and my WiFi works. Best regards, Cip ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 523143] Re: Wireless RFKILL defaults to on (wireless off) and can't be turned off.
Similar bug affecting Acer Laptops previously reported and fixed here : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/405152 -- Wireless RFKILL defaults to on (wireless off) and can't be turned off. https://bugs.launchpad.net/bugs/523143 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 477104] Re: After 9.10 grub update can not boot into Wubi install
Boot process confirmed fixed on my machine, by new Wubildr from Comment 90. I can now also boot with -19. Many thanks to Agostino. Long explanation : I am using Firefox on Windows and have originally tried to download Wubildr directly to C:\wubildr. The overwrite of C:\wubildr failed silently. Sorry for the spam. Thanks to Barbara for the hint. -- After 9.10 grub update can not boot into Wubi install https://bugs.launchpad.net/bugs/477104 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 477104] Re: After 9.10 grub update can not boot into Wubi install
Hello all, Same problem here after upgrade to -19. I've tried replacing the wubildr (comment #90). Problem didn't go away. Managed to boot into -16 and -14 manually with [linux , initrd , boot] sequence. When I tried to see grub.cfg from grub a complete mess was displayed. I've run update-grub2 once and I was still being pushed to the grub2 prompt. I've booted manually again, run update-grub2 and this time I made it to the menu! Still, when I try to boot into -19 the system automatically reboots. I will reinstall the package. My 2cents: Since people can recover via a manual [linux, initrd, boot] sequence grub.cfg must necessarily be readable until root=(loopX) is executed. And it becomes mysteriously unreadable afterwards. On the other hand I needed to do update-grub2 a few times until I managed to get the menu back - somehow the way grub.cfg was stored on disk was making all the difference. -- After 9.10 grub update can not boot into Wubi install https://bugs.launchpad.net/bugs/477104 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 346912] Re: Tracker index corruption (was Tracker does not stop indexing)
The importance of this bug should be very high - it will impact many users that have above a few GBs of indexable data. It might even have blocker potential. Currently I'm learning to live without indexing until this bug is fixed. A possible workaround [needs the tracker-utils package - sudo aptitude install tracker-utils] is to reset databases and clear caches: tracker-processes -r If the workaround is ineffective you might want to uninstall the package: sudo aptitude remove tracker -- Tracker index corruption (was Tracker does not stop indexing) https://bugs.launchpad.net/bugs/346912 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 346912] Re: Tracker does not stop indexing
This bug is also rendering my system (almost) unusable. I have a Core Duo CPU, so one of my core is still free for user tasks, but the usage on the other core is 100%. I've tried deleting the database / cache / logs but nothing works, the tracker will run into the problem again, and again, and again. This is most definitely related to the amount of documents/words being indexed since I have ~15Gb worth of indexable docs. This started to happen once I upgraded to Jaunty, latest devel version. Hopefully a fix will be forthcoming before Jaunty is going final. -- Tracker does not stop indexing https://bugs.launchpad.net/bugs/346912 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 213404] Re: high CPU usage when creating a new message in Evolution
Issue is fixed for me in Evolution 2.22.3.1. Suddenly my notebook became a lot cooler while sending / receiving e-mail. -- high CPU usage when creating a new message in Evolution https://bugs.launchpad.net/bugs/213404 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 232411] Re: Global proxy settings only propagated when application is launched from the command prompt.
Proxy configuration done through System - Preferences - Network Proxy. Proxy is set to - Manual Proxy Configuration, using same proxy for all protocols and using port 8001. This results in the following output in Gnome Terminal : env| grep proxy http_proxy=http://192.168.1.1:8001/ no_proxy=localhost,127.0.0.0/8,*.local By command prompt I mean the Gnome Terminal. Expected behavior is that Google Earth would use the proxy settings if it is launched either from the Terminal or from the Menus. Currently it only respects the settings if launched from the terminal. If launched from the menu it fails to connect to the login/authentication server. The exact error message is : Warning Google Earth could not contact the authentication server to activate your session. The application will continue to operate but will only display data available locally (in cache). For more information please visit: OK Behavior persists across restarts. -- Global proxy settings only propagated when application is launched from the command prompt. https://bugs.launchpad.net/bugs/232411 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 232411] Re: Global proxy settings only propagated when application is launched from the command prompt.
The problem persists through a restart of the computer. I am using gnome. The System-Preferences-Network Proxy setting is ignored when I launch the program from Applications - Internet - Google Earth. [The setting is effective when I launch the program from a terminal.] -- Global proxy settings only propagated when application is launched from the command prompt. https://bugs.launchpad.net/bugs/232411 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 232411] [NEW] Global proxy settings only propagated when application is launched from the command prompt.
Public bug reported: Affected applications: Google Earth. This might be a bug in the application itself. Global proxy configuration is only effective if the application is launched through the command prompt. ** Affects: control-center (Ubuntu) Importance: Undecided Status: New -- Global proxy settings only propagated when application is launched from the command prompt. https://bugs.launchpad.net/bugs/232411 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 213404] Re: high CPU usage when creating a new message
Confirmed. I have an exchange account with global catalog name not filled in. CPU usage spikes to 55%+ on New Message and doesn't go down until I restart evolution. From top: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 5964 arm 20 0 43944 6068 2064 S 31 0.3 20:59.10 gconfd-2 14752 arm 20 0 384m 16m 9976 S 30 0.8 0:16.54 evolution-excha 14749 arm 20 0 621m 57m 21m S 26 2.9 0:17.56 evolution Affected: evolution, evolution-exchange gconfd-2. -- high CPU usage when creating a new message https://bugs.launchpad.net/bugs/213404 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
