Manual configuration doesn't seem to work either.
sudo /etc/init.d/NetworkManager stop
sudo /etc/init.d/networking restart
Produces:
wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:24:2b:40:1c:d9
Sending on LPF/wlan0/00:24:2b:40
** Attachment added: "full daemon.log since problem began"
http://launchpadlibrarian.net/23337844/daemon.log
--
[jaunty] Network Manager no longer sees wireless networks
https://bugs.launchpad.net/bugs/337076
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment removed: "daemon.log"
http://launchpadlibrarian.net/23336701/daemon.log
** Attachment added: "log from trying to connect using "connect to hidden
wireless network""
http://launchpadlibrarian.net/23337835/daemon.log
--
[jaunty] Network Manager no longer sees wireless networ
just a note: the wireless is working on my CQ-50 running 8.04, so the
network is OK. Below is ifconfig, iwconfig, and daemon.log. I left
wmaster0 in the output of ifconfig because I'm not actually sure what it
is.
ifconfig:
wlan0 Link encap:Ethernet HWaddr 00:24:2b:40:1c:d9
UP BRO
Public bug reported:
Binary package hint: network-manager
An update today (March 2) broke the wireless on my Compaq CQ-60-216DX.
There wasn't actually a network-manager update, so that's not really the
problem, but the wireless module is still loaded, so I'm not sure what
package to tag.
I've in
*** This bug is a duplicate of bug 335885 ***
https://bugs.launchpad.net/bugs/335885
Confirmed here. It seems to be related to the upgrade from python 2.5
--> 2.6, as far as I can tell. Synaptic tried to remove the following
packages to complete the upgrade:
apturl
deluge
deluge-common
deluge
** Attachment added: "dmesg"
http://launchpadlibrarian.net/22588465/dmesg
--
suspend only works once
https://bugs.launchpad.net/bugs/206952
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
I'm running Ubuntu minimal (Intrepid) as a stand alone xbmc box. Like
everybody else, I get one successful suspend every reboot. On the second
suspend the screen goes blank like it's going to suspend, but then
immediately comes back. pm-suspend.log shows no error messages, but also
shows no log for
For me, all I have to do is set the panels to unexpanded, log out, then
log back in. The bottom panel usually moves to the top, though I have
seen it the other way around. It does it with the 'original" panels as
well as with newly created panels.
This was an upgrade system and not a clean install
wxmaxima does work both in gutsy and the latest feisty
--
Maxima frontends cannot connect
https://bugs.launchpad.net/bugs/85474
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@lists.ubuntu.c
Public bug reported:
Binary package hint: gnome-panel
gnome-panel 2.19.5-0ubuntu5 in gutsy/7.10 moves when I log out and log
back in. Sometimes the top moves to the bottom, and sometimes the bottom
moves to the top. Both of my panels are *not* expanded, and the only way
to move them back is to ex
I'm not sure whether this should be filed as a new report or not,
because it seems slightly different. However, Amarok has started locking
up when I launch it again. This time, however, the window opens but
becomes unresponsive nearly immediately. I have tried purging the
configuration files as wel
I noted the versions in the original report, 5.10.0 for Maxima and 0.7.1
for wxmaxima. I did forget to mention, though, that I was running Feisty
Herd 4 on x86.
Maxima does indeed work at the command line.
--
Maxima frontends cannot connect
https://launchpad.net/bugs/85474
--
ubuntu-bugs maili
Public bug reported:
Binary package hint: maxima
When running Maxima 5.10.0 and wxmaxima 0.7.1 in Ubuntu Feisty wxmaxima
displays "Not connected to maxima!" when any command is entered. There
is no output when running wxmaxima from the console.
** Affects: maxima (Ubuntu)
Importance: Undeci
My system is a dist-upgrade of Edgy that was a dist-upgrade of Dapper,
so it could very likely be related to that. I had been using 1.4.4 in
Feisty with no incident though.
--
Amarok freezes on Kubuntu Feisty
https://launchpad.net/bugs/84967
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubunt
Sorry Andrew, I posted that last comment before I saw yours. You were
correct; that solved the problem. I lost my collection, settings, etc.
obviously, but at least it works!
--
Amarok freezes on Kubuntu Feisty
https://launchpad.net/bugs/84967
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
I just tested forcing the edgy version of 1.4.5. It produces the same
results. Rolling even further back to 1.4.4 from Medibuntu (unsupported,
I know) results in the process not even starting.
--
Amarok freezes on Kubuntu Feisty
https://launchpad.net/bugs/84967
--
kubuntu-bugs mailing list
kubu
I have the same problem. I get the following output in console:
Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use
amarokapp.
kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x8098f00 ): KAccel
object already contains an acti
18 matches
Mail list logo
