I'm having the same problem with both Facebook and Google and 13.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069882
Title:
Windows Live Requires Authorization
To manage notifications about
Mackenzie Morgan skrev 2009-10-30 23:43:
4965 as well? I've got one of those machines too. It's also fine. That one
has
Subsystem: 8086:1100
As I said earlier; I suspect it has something to do with the AP/Router,
mine is fine as well, at home.
Ungoliath, what kind of router do you
Anything more on this? I haven't visited the affected site for a while
so I don't know if the issue remains.
Also, could this bug be moved/duped to Karmic's bug database?
--
[karmic] Wireless LAN disconnects frequently # Chipset Intel 3945ABG @ AP with
WPA
Same issue here, connecting with my laptop resets the AP, a D-Link
Airplus G 2.4GHz wgl-g700ap thereby disconnecting all other devices.
My NIC is a:
01:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan]
Network Connection (rev 02)
The other computer (running Jaunty) has a:
Sorry Bryce, I don't have that laptop any more, so I can't verify if it
still is an issue.
Bryce Harrington skrev:
Hi linus-ussarna,
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't
been any activity in
Nicolò Chieffo skrev:
Wait: the rfkill works as expected:
0 is no kill
1 is software kill
2 is hardware kill
3 is hardware + software kill
you cannot disable hardware kill using an software
OK, but why is it set to 3 or 2 by Fn+F2 (it still has to be the kernel
right?)? Shouldn't
I agree Steve, and so does some other people :-) found these now (didn't
know about rf_kill before I ran into these problems):
http://groups.google.se/group/linux.kernel/browse_thread/thread/3dbe888c7f54a1cd
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1606
Thank you all for the
Nope, it's partially resovled in 180598, the wireless card gets turned
on and off with 108 installed (kind of), but there remains three issues:
- The LED doesn't show the status, it's always lit
- Bluetooth is turned off on the first press of Fn+F2, but is not turned on by
the second
- The
Steve: Thank you for the fix, it helps kind of; please have a look at
bug https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/204378 ,
it probably explains more about the problem with asus.
Nicolò: /sys/devices/platform/asus-laptop/wlan /is/ the controller for
the wlan card, although it
Nicolò Chieffo skrev:
Does this bug still occur, after the release of acpi-support 0.108? I
don't think so...
I'm interested in what happens if you use, instead of the laptop
hotkey, the script from acpi-support:
sudo /etc/acpi/asus-wireless.sh
tell me if this script has the correct
Nicolò Chieffo skrev:
So the hotkey fires 2 acpi events... the first is for wifi, and the
second for bluetooth (not sure).
At the third keypress, the events are the same as the second keypress,
since bluetooth does no more come back on, but this is not our
problem. you should file another
More fun:
After fiddling around for a while with device/rf_kill and asus-
laptop/wlan ksoftirqd hangs with 100% CPU usage :-)
--
[Hardy] acpi-support 106 107 breaks wireless on Asus U1F
https://bugs.launchpad.net/bugs/204378
You received this bug notification because you are a member of Ubuntu
Orkun, are you able to watch movies with the intel driver and XAA? For
me (also 945GM) both vlc and totem crashes. VLC with the following
error:
[EMAIL PROTECTED]:Video $ vlc mega_robot_returns.mov
VLC media player 0.8.6d Janus
** (.:7333): CRITICAL **: gtk_pizza_set_size: assertion `pizza !=
Nicolò Chieffo skrev:
That's right.
Could you tell me if asus-wireless-2.sh is still called? if not we
should be near to the solution
It's not called by Fn+F2, but it's called by the hardware kill-switch
(which uses 5f and 7d)
--
[Hardy] acpi-support 106 107 breaks wireless on Asus U1F
Nicolo: Hm, yes commenting that line from state-funcs works, but stops
the LED going on/off and additionally kills bluetooth permanently (until
reboot that is). I'll try with your patch from the other bug to see if
it helps.
Any ideas as to what happened in 106 that caused this?
--
[Hardy]
Nicolò Chieffo skrev:
This is very strange, especially with bluetooth, that line only
manages the wifi led, and in some cases the wifi switch... try that
patch soon, and tell us the result
I've applied the patch, with varying result. I have a couple of ideas as
to what might be causing it, I
Nicolò Chieffo skrev:
I've seen that your laptop is using asus-wireless-2.sh. This file is
wrong in my opinion. I will try to apply some changes to it, and then I
will upload a patch here.
Actually I think it uses asus-wireless, I was wrong in my first report.
The keycode is 5d and 7e
Checked, it uses both.
Here's two keypresses of Fn+F2:
hotkey ATKD 005d 0021
hotkey ATKD 007d 000b
hotkey ATKD 005d 0022
hotkey ATKD 007e 001f
I think I've found the problem though; you can't control the wireless
card via /sys/class/net/wlan0_rename/device/rf_kill
Forgot to mention that I'm using Nicolò's patch from bug
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/180598
To test my scripts I've commented out events/asus-wireless and events
/asus-wireless-2 to stop them interfering.
--
[Hardy] acpi-support 106 107 breaks wireless on Asus
And the script
** Attachment added: asus-u1f-wireless.sh
http://launchpadlibrarian.net/12795286/asus-u1f-wireless.sh
--
[Hardy] acpi-support 106 107 breaks wireless on Asus U1F
https://bugs.launchpad.net/bugs/204378
You received this bug notification because you are a member of Ubuntu
Bugs,
OK, I've made some scripts for the U1F now, it's ugly as batshit, but
works. TODO is to make it exclusive to the U1F as I don't want to kill
some other models. Also it would probably be a good idea to make asus-
wireless-2 exclusive to the models it's written for ( the U6E )
** Attachment
Just wanted to say THANK YOU! Great work Orkun!
--
html rendering speed WAY decreased. conflict opera / firefox vs compiz
https://bugs.launchpad.net/bugs/204308
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
] ) ; then
toggleAllWirelessStates setLEDAsusWireless 0
fi
does NOT help. The previous version (105) worked perfectly.
I don't recall how to catch the keycodes, if someone would remind me I'd
be happy to help out.
Regards / Linus Harling
** Affects: acpi-support (Ubuntu)
Importance: Undecided
Oops, when I said wireless switch i meant Fn+F2, the physical kill-
switch still works (although it doesn't turn on the wireless as Fn+F2 is
stopping it, or whatever).
--
[Hardy] acpi-support 106 107 breaks wireless on Asus U1F
https://bugs.launchpad.net/bugs/204378
You received this bug
titoose, thats exactly what's happening to mine after the switch to
.22-14, good (or rather; bad) to hear that it's not just mine.
To sum it up:
- resume
- black screen, flash as backlight turns on
- wait a while, then some piece of the log is displayed (in console mode, vt 8?)
- blink, then
Just saw this, which might be the same problem, testing the workaround in a
while:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.22/+bug/123104
--slinkan
--
Gutsy Reboot on Resume, nvidia-glx-new and linux-2.6.22-12
https://bugs.launchpad.net/bugs/146228
You received
Yup, the workaround in bug# 123104 worked, I'm not calling this a dupe
yet though as in our case the laptops suspend, but dies on resume.
Here's the workaround (thanks to Jose de la Rosa):
Workaround with new driver 100.14.19. In /etc/default/acpi-support,
change to:
MODULES=uvcvideo
And the xorg.conf:
** Attachment added: xorg.conf
http://launchpadlibrarian.net/9531048/xorg.conf
--
Gutsy Reboot on Resume, nvidia-glx-new and linux-2.6.22-12
https://bugs.launchpad.net/bugs/146228
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Public bug reported:
Binary package hint: nvidia-glx-new
My Dell Latitude D620 (Quadro NVS 110M) reboots instead of resuming when
opening the lid after suspend using nvidia 100.14.19. Works fine with
nv driver.
Steps to reproduce:
1. Enable nvidia driver in xorg.conf
2. Log out / log in (or
Relevant syslog
** Attachment added: syslog.2.gz
http://launchpadlibrarian.net/9530984/syslog.2.gz
--
Gutsy Reboot on Resume, nvidia-glx-new and linux-2.6.22-12
https://bugs.launchpad.net/bugs/146228
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Hi there, I followed the deps down a bit more, this is where it wouldn't
get any further (I'm not the original poster so my system may be a bit
different, and I do use Xgl from berookid):
-
[EMAIL
31 matches
Mail list logo
