** Attachment added: "lspci -v"
http://librarian.launchpad.net/4659684/lspciv.txt
--
[edgy] network-admin does not display access points
https://launchpad.net/bugs/63972
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "dmesg"
http://librarian.launchpad.net/4659683/dmesg.txt
--
[edgy] network-admin does not display access points
https://launchpad.net/bugs/63972
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: gnome-system-tools
This may or may not be related to bug:
https://launchpad.net/distros/ubuntu/+source/linux-meta/+bug/63886
I will attach my lspci -v command, but in short I am using an Atheros
chipset.
My problem is that network-admin does not show m
Thanks for the response. Seeing I didn't know the nature of the problem
I wasn't 100% certain of the package the problem existed in.
If they cannot help because the driver is in the restricted set then
perhaps there should be an easy way to use a different kernel seeing I
know this WAP was accessa
** Attachment added: "/etc/init.d/networking start"
http://librarian.launchpad.net/4657098/netstart.txt
--
[Edgy] Unable to connect to some access points
https://launchpad.net/bugs/63886
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubunt
** Attachment added: "/etc/init.d/networking stop"
http://librarian.launchpad.net/4657099/netstop.txt
--
[Edgy] Unable to connect to some access points
https://launchpad.net/bugs/63886
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-
** Attachment added: "iwconfig output"
http://librarian.launchpad.net/4657096/iwconfig.txt
--
[Edgy] Unable to connect to some access points
https://launchpad.net/bugs/63886
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "lspci -v output"
http://librarian.launchpad.net/4657097/lspciv.txt
--
[Edgy] Unable to connect to some access points
https://launchpad.net/bugs/63886
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: network-manager
I tried searching to see if someone already logged this bug, but I'm not
even 100% certain what the problem is...
I'll try to give as much info as possible but feel free to ask for extra
info if needed.
I have a 802.11G WAP at home, whic
** Attachment added: "ifconfig output"
http://librarian.launchpad.net/4657095/ifconfig.txt
--
[Edgy] Unable to connect to some access points
https://launchpad.net/bugs/63886
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
All of the log output was taken while at the location.
** Attachment added: "dmesg output"
http://librarian.launchpad.net/4657094/dmesg.txt
--
[Edgy] Unable to connect to some access points
https://launchpad.net/bugs/63886
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lis
Public bug reported:
Hi there,
I have been attempting to upload some pictures to Gallery via the f-spot that
is included with Knot 3. f-spot can connect to my gallery and it can also get a
listing of my albums, however when trying to create a new album it crashes. I
will attach the log.
** Aff
** Attachment added: "crash log"
http://librarian.launchpad.net/4363798/_usr_lib_f-spot_f-spot.exe.1000.crash
--
f-spot/mono crashes when creating a new gallery album
https://launchpad.net/bugs/61577
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/l
This is not just happening in a Dapper->Edgy update. I have just done a
fresh install of Knot 3 and I have encountered the same issue after my
first 'apt-get update && apt-get dist-upgrade'. Aptitude seems to work
around part of the problem, but does not fix it completely.
--
Error during Dapper-
Public bug reported:
Binary package hint: esound
Hi there,
This seems to be happening to me more and more. I start up my computer from a
cold boot and log into Gnome. Sound appears to work (i.e. the login sound goes
off and xmms works). However applications that use OSS (like Cedega) complain
Many Java applications are still written for java 1.4.2. I have seen
other gtk themes work fine in 1.4.2 and 1.5.x. That being said there
should be a way to get it to function properly with the existing GTK
interface in Java.
--
Java incompatibilities with GTK theme -- Dapper Flight 5
https://lau
16 matches
Mail list logo