[Bug 977804] Re: Unity crashes when many windows are opened (intel_do_flush_locked failed: No space left on device)
I've updated the mesa packages this morning as I found them in precise- updates, but still have the same problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977804 Title: Unity crashes when many windows are opened (intel_do_flush_locked failed: No space left on device) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/977804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 977804] Re: Unity crashes when many windows are opened
Same here on a Asus Eee PC 100H sporting an Intel 945GSE (on lspci: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977804 Title: Unity crashes when many windows are opened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/977804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 962395] Re: drive icon disappears from unity launcher while still mounted
This happens also when you have a terminal open and cd'ed to a folder in the drive, so it can't be unmounted: a window is shown and you can choose to remove the drive anyway or cancel the operation, choosing the latter option result in the drive still mounted but the icon is disappeared in the launcher. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/962395 Title: drive icon disappears from unity launcher while still mounted To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/962395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 356807] Re: rt_ioctl_giwscan log spam removal or fix
*** This bug is a duplicate of bug 373680 *** https://bugs.launchpad.net/bugs/373680 I agree with some users above, it's not a duplicate bug. I'm on Ubuntu Lucid Lynx with kernel 2.6.34-020634-generic on an Asus EeePC 1000H, wi-fi did not work out of the box so I had to recompile RT2860 drivers from Ralink sources (version 2.4.0.0 from their website): my dmesg got spammed with rt_ioctl_giwscan messages, but no problem with wi-fi connection. I commented out -DDBG flag from config.mk and compiled it again, now the messages are gone. The issue is definitely that flag, I think it should be disabled: if there are performance/connection problems, error messages should appear regardless of debug messages enabling, shouldn't they? -- rt_ioctl_giwscan log spam removal or fix https://bugs.launchpad.net/bugs/356807 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 437862] Re: device key_bitmask has changed
This happens to me too with Karmic on an Asus EeePC 1000H netbook : if I switch to VT (CTRL+ALT+F1) and then back to X (ALT+F7) then the netbook keyboard doesn't work anymore, unlike the USB keyboard which I also have. No problem with touchpad or USB mouse. By the end of Xorg.0.log, after three switch-to-VT-then-back-to-X's, I found the attached lines. As you can see, there is always a series of reopening of the devices, but while all the others succeed, the builtin keyboard fails: (--) ETPS/2 Elantech Touchpad: touchpad found (II) Asus EeePC extra buttons: Device reopened after 1 attempts. (II) Power Button: Device reopened after 1 attempts. (II) Video Bus: Device reopened after 1 attempts. (II) USB Keyboard: Device reopened after 1 attempts. (II) USB Keyboard: Device reopened after 1 attempts. (II) Sleep Button: Device reopened after 1 attempts. (II) Power Button: Device reopened after 1 attempts. (EE) AT Translated Set 2 keyboard: device key_bitmask has changed (EE) AT Translated Set 2 keyboard: Device has changed - disabling. (II) Macintosh mouse button emulation: Device reopened after 1 attempts. (II) Logitech Optical USB Mouse: Device reopened after 1 attempts. ** Attachment added: Final lines of Xorg.0.log after switching to VT and then back to X three times. http://launchpadlibrarian.net/36798699/Xorg.0.log -- device key_bitmask has changed https://bugs.launchpad.net/bugs/437862 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 437862] Re: device key_bitmask has changed
I confirm also that this seems to be happening only when you are in X for the first time since booting the PC: after the above problems, I quit the session, gdm restarts, I can type the password with the netbook keyboard, then if I switch to VT and then back to X, the same keyboard now works like a charm, and Xorg.0.log now displays these lines instead of those above: (--) ETPS/2 Elantech Touchpad: touchpad found (II) Asus EeePC extra buttons: Device reopened after 1 attempts. (II) Power Button: Device reopened after 1 attempts. (II) Video Bus: Device reopened after 1 attempts. (II) USB Keyboard: Device reopened after 1 attempts. (II) USB Keyboard: Device reopened after 1 attempts. (II) Sleep Button: Device reopened after 1 attempts. (II) Power Button: Device reopened after 1 attempts. (II) AT Translated Set 2 keyboard: Device reopened after 1 attempts. (II) Macintosh mouse button emulation: Device reopened after 1 attempts. (II) Logitech Optical USB Mouse: Device reopened after 1 attempts. As you can see, now there's no device key_bitmask has changed and Device has changed - disabling. Hope this helps whomever the bug will be assigned to. -- device key_bitmask has changed https://bugs.launchpad.net/bugs/437862 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 455357] Re: karmic: volume muted on login
It happens to me as well, both on Ubuntu (on an Asus EEE PC 1000H) and Xubuntu (on a different, older laptop from an Italian assembler). They're up to date with the last updates, but that still happens. -- karmic: volume muted on login https://bugs.launchpad.net/bugs/455357 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 269891] Re: WPA supplicant cannot scan for AP's after suspend
This seems to be the case for me, too. I have Jaunty 9.04 on a Asus EeePC 100H. The kernel is 2.6.30-generic, which has the driver for rt2860 version 1.8.1.1. I have no problem on statup: as soon as I get into my account, Network Manager is already getting the wi-fi working. If I suspend or hibernate the system, on resume Network Manager shows no wi-fi network, while `iwlist ra0 scan` does. Looking at daemon.log, it seems that it's waiting for wpasupplicant: --- Jul 2 02:04:32 lopo-netbook NetworkManager: info Waking up... Jul 2 02:04:32 lopo-netbook NetworkManager: info (eth0): now managed Jul 2 02:04:32 lopo-netbook NetworkManager: info (eth0): device state change: 1 - 2 Jul 2 02:04:32 lopo-netbook NetworkManager: info (eth0): bringing up device. Jul 2 02:04:32 lopo-netbook NetworkManager: info (eth0): preparing device. Jul 2 02:04:32 lopo-netbook NetworkManager: info (eth0): deactivating device (reason: 2). Jul 2 02:04:32 lopo-netbook NetworkManager: info Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Jul 2 02:04:32 lopo-netbook NetworkManager: info Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Jul 2 02:04:32 lopo-netbook NetworkManager: info (ra0): now managed Jul 2 02:04:32 lopo-netbook NetworkManager: info (ra0): device state change: 1 - 2 Jul 2 02:04:32 lopo-netbook NetworkManager: info (ra0): bringing up device. Jul 2 02:04:32 lopo-netbook NetworkManager: info (ra0): preparing device. Jul 2 02:04:32 lopo-netbook NetworkManager: info (ra0): deactivating device (reason: 2). Jul 2 02:04:32 lopo-netbook NetworkManager: info (ra0): device state change: 2 - 3 Jul 2 02:04:32 lopo-netbook NetworkManager: info (ra0): supplicant interface state: starting - ready --- After the last line, nothing happens for tens of minutes. I thought it was watiting for wpasupplicant, so I tried to `killall wpa_supplicant`: - Jul 2 02:05:20 lopo-netbook NetworkManager: info (ra0): supplicant manager state: idle - down Jul 2 02:05:20 lopo-netbook NetworkManager: info (ra0): device state change: 3 - 2 Jul 2 02:05:20 lopo-netbook NetworkManager: info (ra0): deactivating device (reason: 10). Jul 2 02:05:20 lopo-netbook NetworkManager: WARN nm_device_wifi_set_ssid(): error setting SSID to '(null)' for device ra0: Network is down Jul 2 02:05:20 lopo-netbook NetworkManager: WARN nm_device_wifi_disable_encryption(): error setting key for device ra0: Network is down Jul 2 02:05:20 lopo-netbook NetworkManager: WARN nm_device_wifi_set_mode(): error setting card ra0 to mode 2: Network is down Jul 2 02:05:20 lopo-netbook NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed Jul 2 02:05:20 lopo-netbook NetworkManager: info Trying to start the supplicant... Jul 2 02:05:20 lopo-netbook NetworkManager: info (ra0): supplicant manager state: down - idle Jul 2 02:05:20 lopo-netbook NetworkManager: info (ra0): device state change: 2 - 3 Jul 2 02:05:21 lopo-netbook NetworkManager: info (ra0): supplicant interface state: starting - ready -- Once again, no network list (and no associating) in Network Manager. I tried to kill wpa_supplicant again, and now my wi-fi SSID showed in the list, NM tried to associate with it, but without success: -- Jul 2 02:06:21 lopo-netbook NetworkManager: info (ra0): supplicant manager state: idle - down Jul 2 02:06:21 lopo-netbook NetworkManager: info (ra0): device state change: 3 - 2 Jul 2 02:06:21 lopo-netbook NetworkManager: info (ra0): deactivating device (reason: 10). Jul 2 02:06:21 lopo-netbook NetworkManager: WARN nm_device_wifi_set_ssid(): error setting SSID to '(null)' for device ra0: Network is down Jul 2 02:06:21 lopo-netbook NetworkManager: WARN nm_device_wifi_disable_encryption(): error setting key for device ra0: Network is down Jul 2 02:06:21 lopo-netbook NetworkManager: WARN nm_device_wifi_set_mode(): error setting card ra0 to mode 2: Network is down Jul 2 02:06:21 lopo-netbook NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed Jul 2 02:06:21 lopo-netbook NetworkManager: info Trying to start the supplicant... Jul 2 02:06:21 lopo-netbook NetworkManager: info (ra0): supplicant manager state: down - idle Jul 2 02:06:21 lopo-netbook NetworkManager: info (ra0): device state change: 2 - 3 Jul 2 02:06:22 lopo-netbook NetworkManager: info (ra0): supplicant interface state: starting - ready Jul 2 02:06:27 lopo-netbook NetworkManager: info Activation (ra0) starting connection 'Auto Alice-43549390' Jul 2 02:06:27 lopo-netbook NetworkManager: info (ra0): device state change: 3 - 4 Jul 2 02:06:27
