Yes, now the option for WPA is not given anywhere, even under the manual
setup. I don't have a network cable handy at the moment to see if there
are any updates available. I don't know what logs might be useful in
this case either.
--
Cannot connect to a WPA enabled network with NetworkManager
I'm not sure, I've retired that laptop. I still have it though so I
will dig it out of storage and give it a try later in the week.
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notification bec
Sorry, I didn't actually mean to hit that button (that set it as a bug
in gnome-power). I do believe that I'm experiencing this problem as
well, however. When on AC the computer will sleep after 2 minutes, but
on battery it never sleeps. Looking through gconf, I saw that /apps
/gnome-power-manag
Sorry, that log has other information from boot (in order to reproduce
the problem, I have to delete the connection from gconf as it only
happens on the first connection attempts). This log contains only the
boot where the config info wasn't present and I had to enter manually.
** Attachment adde
Yes, it still happens on the first connections. I have to manually
enter the network information, and even then, it only connects after
several reattempts.
Here is the syslog as requested.
** Attachment added: "syslog"
http://launchpadlibrarian.net/13010977/syslog
--
Cannot connect to a WPA
I forgot to mention that the suspend option in the quit menu worked
regardless of battery status.
--
Idle/inactive action/autosuspend results in a suspend AND a hibernate
https://bugs.launchpad.net/bugs/136871
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
When I booted from the live cd there was no hibernate option, so I'm not
sure how accurate this is, but performing the same steps above, the
laptop (an IBM T23) wouldn't suspend on battery, but would on AC.
A very quick web search makes it look like hibernate may not be
supported from a live cd?
Yes, this particular problem has been resolved in hardy (mostly). On AC
power the laptop goes to sleep and wakes properly after two minutes. On
battery it does nothing. However, it seems that in gconf the key /apps
/gnome-power-manager/actions/sleep_type_battery is set to 'disabled'
instead of '
Still seems to be happening in gutsy.
--
Terminal Server Client crashes when disconnecting correctly
https://bugs.launchpad.net/bugs/103208
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@li
I've encountered this bug on gutsy as well. In my case I am running the
client full screen, but despite the fact that I'm using the keyboard and
mouse, the screen saver will come on and lock the screen after 10
minutes. It only seems to do this once, however. Once I log back in it
doesn't seem t
Yes, I would say that's the same exact bug. Sorry for the dupe.
--
gnome-power-manager hibernates computer instead of suspend
https://bugs.launchpad.net/bugs/145456
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs m
This is still an issue in gutsy.
--
fail to sleep when lid is closed
https://bugs.launchpad.net/bugs/37626
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/
This has been fixed as of today. Much faster too. thanks.
--
gnome-power-manager doesn't recognize battery removed
https://bugs.launchpad.net/bugs/144830
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing lis
I assume that the wiki page meant tail -f -n0 /var/log/syslog >
/tmp/syslog, rather than tail -n0 /var/log/syslog > /tmp/syslog, which
outputs nothing.
Happily (or I guess unfortunately, depending on how you look at it) I
wasn't able to replicate the crash. However there is still a bug. When
I
** Attachment added: "dmesg.ac.log"
http://launchpadlibrarian.net/9519659/dmesg.ac.log
--
gnome-power-manager hibernates computer instead of suspend
https://bugs.launchpad.net/bugs/145456
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Attachment added: "dmesg.battery.log"
http://launchpadlibrarian.net/9519658/dmesg.battery.log
--
gnome-power-manager hibernates computer instead of suspend
https://bugs.launchpad.net/bugs/145456
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug co
I just noticed something peculiar. I tried setting it so it would sleep
while on AC power, and got the opposite result! That is when the
timeout happened, the computer went to sleep, and when I woke it up and
logged back in, it hibernated. I will try to capture the dmesg log for
each instance.
Public bug reported:
Binary package hint: gnome-power-manager
This is a problem that I just started having in the past few days.
Whenever gnome-power-manager goes to put the computer to sleep, it
actually hibernates instead of sleeping. What's worse is that when I
turn the laptop back on and log
Public bug reported:
Binary package hint: gnome-power-manager
When I remove the battery from my IBM T23, gnome power manager doesn't
show that the battery has been removed. The system tray icon continues
to display that it is charging and that the battery is full (or nearly
full). However, when
I have an IBM T23 with the same problem. I don't know about Feisty (I
never used it because of other problems), but it was working in Gutsy a
few days ago. There were some updates, and now it doesn't seem to be
working. The indicator pops up, but the indicator just stays all the
way at the botto
lspci -vvnn in case they are different.
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/9498165/lspci-vvnn.log
--
IBM T23 resumes with black screen
https://bugs.launchpad.net/bugs/144191
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
I seem to be having this same problem, almost. I was able to get the
screen back by pressing Fn+F3 (the combination that turns the screen
off) then just the Fn key. Interestingly enough, when I tried it the
first two times, the screen was blank. The third time it was not
however. When I logged
Public bug reported:
Binary package hint: gnome
When logging into gnome with the date set incorrectly (about a month in the
past), I got a dialog that told me the date was probably set wrong, which could
cause all manner of bad things. It gave me two options, ignore or adjust date
(or clock,
This still seems to be a problem in gutsy. For me pressing Fn+F3 (the
combo to turn off the display) and then pressing just the Fn key seems
to wake up the display. It seems to happen every time. I haven't tried
using an external display to see if it is being turned on or not.
--
IBM T23: resu
This issue has finally been fixed in ubuntu gutsy with the 2.6.22
kernel.
--
Cannot connect to wireless network with NetworkManager
https://bugs.launchpad.net/bugs/103020
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-b
** Attachment added: "syslog.log"
http://launchpadlibrarian.net/9446773/syslog.log
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/9446771/lspci-vvnn.log
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/9446772/dmesg.log
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
Public bug reported:
Binary package hint: network-manager
I have an IBM Thinkpad T23 with a IBM High Rate Wireless LAN Mini-PCI
Adapter with Modem (Prism 2.5 chipset).
When I have WPA security enabled on my wireless network, I cannot
connect to it with NetworkManager. It is listed under the wir
I just realized, in that last boot I had hostap_pci blacklisted (to see
if it would use the orinoco_pci driver instead). This is the log
without it blacklisted.
** Attachment added: "Most recent dmesg.log (wireless card not recognized,
hostap_pci not blacklisted)"
http://librarian.launchpad.n
Well, after much difficulty, I was able to upgrade the firmware to
1.7.4. Unfortunately, now feisty doesn't recognize the wireless card at
all. However, dapper does, with the orinoco_pci driver, and what's more
is that NetworkManager actually works now. So the new firmware seems to
work, but for
OK, my mistake, I was thinking it was for building the module without
needing the whole kernel source, which now that I think of it doesn't
make a whole lot of sense.
--
hostap-source fails to build
https://bugs.launchpad.net/bugs/105341
You received this bug notification because you are a member
uname -a: Linux conrad 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC
2007 i686 GNU/Linux
--
hostap-source fails to build
https://bugs.launchpad.net/bugs/105341
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs maili
Public bug reported:
Binary package hint: hostap-source
hostap-source will not compile as is from the package repository. The
following error message occurs when building with module-assistant or by
running make in the /usr/src/modules/hostap-source directory
*** Can't build for 2.6 with a non
** Attachment added: "module-assistant build log"
http://librarian.launchpad.net/7257579/hostap-source.buildlog.2.6.20-14-generic.1176249124
--
hostap-source fails to build
https://bugs.launchpad.net/bugs/105341
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I'm not sure what you mean by scanning. If you mean being able to see the
available networks around me, that works fine. The problem is that I can't
seem to connect to any of them, except via the command line. That being said,
1.4.2 is the last version provided by IBM
(http://www-307.ibm.com
The recent updates had a new version of the kernel, but the problem is still
the same.
uname -a: Linux conrad 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007
i686 GNU/Linux
** Attachment added: "dmesg.log"
http://librarian.launchpad.net/7229129/dmesg.log
--
Cannot connect to wireless
** Attachment added: "lspci-vvnn.log"
http://librarian.launchpad.net/7229131/lspci-vvnn.log
--
Cannot connect to wireless network with NetworkManager
https://bugs.launchpad.net/bugs/103020
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Attachment added: "Contents of /etc/network/interfaces"
http://librarian.launchpad.net/7177219/interfaces
--
Cannot connect to wireless network with NetworkManager
https://bugs.launchpad.net/bugs/103020
You received this bug notification because you are a member of Ubuntu
Bugs, which is th
Public bug reported:
Binary package hint: network-manager
Hi, I have an IBM Thinkpad T23 with a IBM High Rate Wireless LAN Mini-
PCI Adapter with Modem (Prism 2.5 chipset).
In feisty, using the NetworkManager applet in gnome, I am unable to
connect to any wireless network, secured or unsecured.
Here is a copy of the system log from when I selected my wireless
network (nynexman) to when the icon went back to the "no connection"
state.
** Attachment added: "Syslog from connection attempt."
http://librarian.launchpad.net/7146381/nm.txt
--
Cannot connect to wireless network with Network
41 matches
Mail list logo
