Im sorry, but I cannot test it anymore. I dont have the machine, I
mailed it to the person I installed it for shortly after reporting the
bug. If it comes back to me for updating at some point I can try Lucid
Lynx on it from a USB stick and see if that fixes it. As it is the
machine is on the othe
Oops, lspci -vnvn omitted the Wlan card as it was turned off after
causing the panic. Attached lspci with it here.
** Attachment added: "lspci-vnvn_WITH_wlan_enabled.log"
http://launchpadlibrarian.net/39395073/lspci-vnvn_WITH_wlan_enabled.log
--
kernel crashes when toggling off wlan on Eee P
How would I go about to disable the Fn-F2 keycombo completely, so it
would not be pressed accidentally? It is fine if it could only be
toggled via BIOS - better than to have the machine hang if accidentally
pressed.
--
kernel crashes when toggling off wlan on Eee PC 701SD
https://bugs.launchpad.n
I uploaded the Apport - generated kernel crash report here:
http://koti.welho.com/mauserman/linux/linux-image-2.6.31-19-generic.0.crash
(If someone else is able to attach the file directly to this report,
please do so - for some reason uploading it via Apport or Launchpad
fails for me, I will leav
Bah, Launchpad had an error after my browser sent the 120 mb crash
report and failed to upload it. I will see if I can upload it somewhere
else and will post a link here ASAP.
--
kernel crashes when toggling off wlan on Eee PC 701SD
https://bugs.launchpad.net/bugs/522119
You received this bug not
** Attachment added: "version.log"
http://launchpadlibrarian.net/39213316/version.log
--
kernel crashes when toggling off wlan on Eee PC 701SD
https://bugs.launchpad.net/bugs/522119
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "uname-a.log"
http://launchpadlibrarian.net/39213309/uname-a.log
--
kernel crashes when toggling off wlan on Eee PC 701SD
https://bugs.launchpad.net/bugs/522119
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "lspci-vnvn.log"
http://launchpadlibrarian.net/39213306/lspci-vnvn.log
--
kernel crashes when toggling off wlan on Eee PC 701SD
https://bugs.launchpad.net/bugs/522119
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/39213300/dmesg.log
--
kernel crashes when toggling off wlan on Eee PC 701SD
https://bugs.launchpad.net/bugs/522119
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
Public bug reported:
This bug affects at least Jaunty, Karmic and Lucid Lynx alpha 2 - I
tested the behaviour on each with the latest kernels for the releases. I
also tested its behaviour with EB4 that is based on Debian unstable,
that kernel crashes as well. I suspect that Hardy is affected as we
Yep, thats true. I will look into it today. My own Eee 701 4GB and 901
both work perfectly now...Its the bloody Realtek chipset on the 701SD ;)
I suppose the SD model of the 701 is not so common either, since the 900
series was introduced and the older ones phased out around the time.
--
Turning
No difference, still hangs the machine.
--
Turning wifi "off" using Fn+F2 on Eee PC with Ralink rt2860 results in kernel
panic (rfkill)
https://bugs.launchpad.net/bugs/404626
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
Ah, there is a new 2.6.31-20 kernel available in proposed, going to try
that.
--
Turning wifi "off" using Fn+F2 on Eee PC with Ralink rt2860 results in kernel
panic (rfkill)
https://bugs.launchpad.net/bugs/404626
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Kernel 2.6.31-19, Eee PC 701SD with 8GB SSD, toggling wlan with Fn-F2
still causes a kernel panic. Vanilla Karmic. I just tried it now. I
don't know if I have time for extensive troubleshooting, since this is
not my own laptop, but I was supposed to upgrade it to Karmic and then
mail it back ASAP.
After using the Eee 901 for a couple of days now since switching the
memory, Ive not had crashes as yet. So it was probably a faulty memory
stick and not a bug. Thanks in any case ;)
--
Kernel panic occurs randomly under normal use on Eee pc 901, Ubuntu 9.10 fully
patched
https://bugs.launchpad.
I found a fitting memory module of 512 megs, and swapped that in for the
901. I will report back on whether that solves the issues, or if they
seem to persist anyway after Ive used this for a while.
--
Kernel panic occurs randomly under normal use on Eee pc 901, Ubuntu 9.10 fully
patched
https:/
I suppose I could see if I could find a replacement memory stick cheaply
and check if switching the memory has any effect on this - Ive not had
reported errors on memory test though, but havent run them for extended
periods. One would think that others would be reporting similar crashes
if this was
** Attachment added: "kern.log"
http://launchpadlibrarian.net/36205549/kern.log
--
Kernel panic occurs randomly under normal use on Eee pc 901, Ubuntu 9.10 fully
patched
https://bugs.launchpad.net/bugs/489558
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Now I got a similar crash with wlan disabled from BIOS, Apport and
crashdump installed, apport did not generate any crash file, and when
trying apport-retrace -s -R /var/crash/linux-image*.crash it says ERROR:
"/var/crash/linux-image*.crash" is neither an existing report file nor a
crash ID. So it
I will install the crashdump tools as well.
--
Kernel panic occurs randomly under normal use on Eee pc 901, Ubuntu 9.10 fully
patched
https://bugs.launchpad.net/bugs/489558
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Ok, I think I can try the without wireless bit at leastI have access
to wired network at home, and also use a 3G modem so I could easily try
using it with the wlan disabled. I will try to report back in a few days
when Ive had some time to test-use the laptop.
Ill report back if I get more dat
** Attachment added: "dmesg"
http://launchpadlibrarian.net/36198345/dmesg
--
Kernel panic occurs randomly under normal use on Eee pc 901, Ubuntu 9.10 fully
patched
https://bugs.launchpad.net/bugs/489558
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I also turned on Apport now, if it might catch it the next time it happens...
On Jaunty, I never got an Apport report of the crash even when I had it running
though, so Im not holding my breath. Any suggestions on how to further pinpoint
the issue are welcome...
--
Kernel panic occurs randomly
** Attachment added: "syslog"
http://launchpadlibrarian.net/36198338/syslog
--
Kernel panic occurs randomly under normal use on Eee pc 901, Ubuntu 9.10 fully
patched
https://bugs.launchpad.net/bugs/489558
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Attachment added: "faillog"
http://launchpadlibrarian.net/36198355/faillog
--
Kernel panic occurs randomly under normal use on Eee pc 901, Ubuntu 9.10 fully
patched
https://bugs.launchpad.net/bugs/489558
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "lspci-vnvn.log"
http://launchpadlibrarian.net/36198297/lspci-vnvn.log
--
Kernel panic occurs randomly under normal use on Eee pc 901, Ubuntu 9.10 fully
patched
https://bugs.launchpad.net/bugs/489558
You received this bug notification because you are a member of Ubuntu
B
** Attachment added: "kern.log"
http://launchpadlibrarian.net/36198327/kern.log
--
Kernel panic occurs randomly under normal use on Eee pc 901, Ubuntu 9.10 fully
patched
https://bugs.launchpad.net/bugs/489558
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Attachment added: "version.log"
http://launchpadlibrarian.net/36198310/version.log
--
Kernel panic occurs randomly under normal use on Eee pc 901, Ubuntu 9.10 fully
patched
https://bugs.launchpad.net/bugs/489558
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Attachment added: "uname-a.log"
http://launchpadlibrarian.net/36198305/uname-a.log
--
Kernel panic occurs randomly under normal use on Eee pc 901, Ubuntu 9.10 fully
patched
https://bugs.launchpad.net/bugs/489558
You received this bug notification because you are a member of Ubuntu
Bugs, w
The latest crash happened at 14.47 local time (the time in the logs).
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/36198290/dmesg.log
--
Kernel panic occurs randomly under normal use on Eee pc 901, Ubuntu 9.10 fully
patched
https://bugs.launchpad.net/bugs/489558
You receiv
Public bug reported:
About once to several times per day of normal use, my Eee pc 901 totally
hangs ie. kernel panic. When this happens, I cannot even get into
virtual terminals, system does not respond to SysRq magic keys either
(ie, I cannot reboot with the SysRq keystrokes either). Only way to
Yup, this still happens with 2.6.31-15-generic I installed from Karmic-
proposed - disabling wlan still crashes kernel.. I guess the "fix"
reported earlier was only because there was no ralink module / no driver
present in the kernel for testing the Huawei fix.
Any hope of getting the fix in the s
My lsusb:
Bus 002 Device 006: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem
/ E270 HSDPA/HSUPA Modem
My connection now works, with the caveats above - ie. NM did not
automatically detect it the first time, it did not show up in Mobile
broadband devices list before creating a profile
This really should have been fixed before release. Lots of people are having a
difficult time because of this issue.
Ive just been trying to tell, over IRC, how to get the kernel 2.6.31-15
installed when you have no network connection as the Huawei modem was the sole
way to connect.
Now she has
Or perhaps its best to wait a while for this to (maybe) be fixed via
regular updates...
--
Turning wifi "off" using Fn+F2 on Eee PC with Ralink rt2860 results in kernel
panic (rfkill)
https://bugs.launchpad.net/bugs/404626
You received this bug notification because you are a member of Ubuntu
Bug
Yup, no such module exists.
Any suggestions on how to proceed to get wlan working, preferably so also
Huawei modem works?
Can I somehow add that driver module only?
--
Turning wifi "off" using Fn+F2 on Eee PC with Ralink rt2860 results in kernel
panic (rfkill)
https://bugs.launchpad.net/bugs/40
Addition, even thou perhaps OT - I have now tried both 2.6.31-5 and 2.6.32-rc5
kernels -
I can turn the wifi led on and off, BUT Network manager never sees any wireless
connection. None.
I can turn it on and off as many times as I wish, but NM never registers the
connection - not even when I boo
I should add that before, on Intrepid and Jaunty, the modem worked
perfectly, but the USB memory part never showed up, which it does now.
--
Huawei E169 USB dongle not working with kernel 2.6.31-12.40
https://bugs.launchpad.net/bugs/446146
You received this bug notification because you are a memb
On the Eee pc now - I have the Huawei E220 dongle, I installed the 2.6.31-5
kernel.
The modem worked on first connection, both the USB memory part and the modem
showed up - the modem had been configured already previously on Jaunty so no
configuration was needed now. It works normally as far as
I installed that kernel to fix my wlan problems, but didnt yet try my
Huawei with it. I will report back when I have the time to test it -
should be today.
--
Huawei E169 USB dongle not working with kernel 2.6.31-12.40
https://bugs.launchpad.net/bugs/446146
You received this bug notification beca
Great
This is the worst one so far - in addition to suspend at times hanging my
machine and wlan toggle not working properly on my Eee pcs. Guess what I use
for internet connectivity - yup, a Huawei modem.
Regressions, regressionsIt worked from Hardy onwards (with wvdial
but still).
--
With the mainline 2.6.31-15 kernel someone provided above, switching
wlan on and off no longer crashes the machine, BUT network manager does
not see the wlan after turning it on again. I think this might be the
same issue that in Jaunty needed the kernel boot option "options pciehp
pciehp_force=1 p
My Eee 901 also periodically hangs when suspending, or resuming from
suspend. Is this perhaps related? I took a picture of the screen the one
time I was able to get into a terminal before it went completely
unresponsive. Sadly the picture is out of focus so its hard to make out
what it says. Last f
Addition - I have the ralink wireless.
--
Turning wifi "off" using Fn+F2 on Eee PC with Ralink rt2860 results in kernel
panic (rfkill)
https://bugs.launchpad.net/bugs/404626
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
Confirm on Eee pc 901 with Karmic Release Candidate. (Its been that way
since Jaunty unless one installed some scripts to fix it, like Fewts
addons for the Eee from Statux)
See here for Statux's Fewts (angry) comments on this issue (he stopped
maintaining the Eee pc addons due to this issue among
I should get Karmic alpha 4 installed on my memory card as well..
I wasnt able to get it on a USB stick using unetbootin, I guess it was because
Karmic used GRUB2.
Ill have to look into it and try running Karmic (I guess you could run it off a
CD and then make a bootable USB via Karmic itself). I
:(
Does this mean I need to open a new bug report again?
I do not have UXA enabled, and I am still getting these crashes and hard locks
on Jaunty.
I dont know why Apport does not generate a report upon crash, though - except
when it hard locks - I guess nothing gets done at that point as even the
OK..
I have now tried running apport, but so far it has not generated any reports,
even thou X has crashed twice. First time hard lock, had to power down. Second
time, dropped to login prompt again, but still no report..
Completely random still, like with Liam O'Reilly. I have found a few
other
I am also now waiting for my Eee 901 to crash again, now I have X server
and display driver debug symbols installed and Apport running. I hope it
crashes as often as yesterday now that I can hope to trace it :)
On this machine, the crashes happen more often with XFCE than Gnome (I
have tried bot X
Bryce Harrington:
Will do that, I installed the x server debug symbols and started Apport in the
background. I will post the results in the bug report Liam O'Reilly started
when this next crashes, since my crashes sound similar at least on the surface.
Thank you.
--
[i945GME] drm:i915_getparam
These are definitely a cause for a serious crash, these have happened always
with Jaunty.
The log entries always looked the same right before X goes.
With vanilla Ubuntu, and not Xfce, this tends to cause a hard lock, ie. even
Alt-SysRq-K does not work, but you need to hold the power button for
Aug 12 21:15:33 gekko-laama gdm[23569]: WARNING: gdm_slave_xioerror_handler:
Vakava X-virhe – :0 käynnistetään uudelleen
This line says "Serious X-error - :0 restarting", in finnish.
The [drm:i915_get_vblank_counter] always seems to precede X crashing, ie.
something with the Intel driver, still?
My Asus Eee pc 901 with the Intel 945Gme chipset has its Xserver crash several
times per day.
This behaviour has never disappeared and my original report was marked as a
duplicate of a bug that has been fixed now.
https://bugs.launchpad.net/bugs/337116
Today X has crashed 3 times, this is syslo
*** This bug is a duplicate of bug 348428 ***
https://bugs.launchpad.net/bugs/348428
Yesterday I downgraded the Intel driver package only to Intrepids version
xserver-xorg-video-intel-2.4 , howto here:
https://wiki.ubuntu.com/ReinhardTartler/X/RevertingIntelDriverTo2.4
I have now had the eee
*** This bug is a duplicate of bug 348428 ***
https://bugs.launchpad.net/bugs/348428
I now installed Xubuntu Jaunty on my Eee pc 901 after having had crashes
described in bug linked above.
At first I thought everything was ok, but today X has crashed twice, screen
goes black, gdm restarts an
I dont know whether I should comment here -
https://bugs.launchpad.net/bugs/337116
or on this one...
I now installed Xubuntu Jaunty on my Eee pc 901 after having had crashes
described in bug linked above.
At first I thought everything was ok, but today X has crashed twice, screen
goes black, gd
I noticed this too, updated today, installed from Jaunty Beta amd64.
Gnome is unusably slow on a dualcore - sucks up between 50-90% idling
from login onwards - this happens every time I log in to Gnome. The
problem is only with Gnome - Im now running XFCE and everything works
right and smooth, with
Seems Compiz segfaulted there too?
--
[i945] xserver crashes at random on Asus eeepc 901, user returned to login
screen
https://bugs.launchpad.net/bugs/337116
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
"Kernel log had no entries at the time of the crashes." I was referring
to the hard locks with this, when X simply crashes and restarts, in my
kern.log there is something odd going on at the time mentioned.
Heres the syslog entries at that same time, 11th of 3. 2009.
Mar 11 10:56:35 Nokkalaama k
Okay, here is the kern.log from my latest crash.
I havent had time to do backtrace or install it on this computer yet, Ill see
if I can do that later.
Could this bug at least be marked important? It is rather severe - X can fail
at any arbitrary time, and its happened about a dozen times at least
I can confirm this. Similar X crash has happened at least about ten
times on my 901, running Ubuntu-Eee 8.04.1 with Array.org kernel. Does
not matter if I run compiz or not. Usually I get back to login screen
after the crash. A few times it has resulted in a total lockup, with
sound repeating a sho
If I remember correctly, make install flac wasnt necessary. I think make - then
copy the flac plugin for xmms from the build directory to xmms plugins dir was
enough.
Ive moved to Audacious since xmms is still missing the plugin and Audacious is
working pretty well for me now.
--
[GUTSY] XMMS
My mobo is Asus M2N - Nvidia chipset.
--
Hardy -- pm-suspend RUINS PARTITION TABLE
https://bugs.launchpad.net/bugs/203537
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://l
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/203537 eh, sloppy
today.
--
Returning from suspend doesnt work right in Hardy 64 bit, resulting in file
system damage
https://bugs.launchpad.net/bugs/212171
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Sorry, said my mobo wrong. Its M2N by Asus, with Nvidia chipset. Desktop
computer.
This seems to be a duplicate of
https://bugs.launchpad.net/ubuntu/+bug/212171 , please merge / remove as
appropriate?
--
Returning from suspend doesnt work right in Hardy 64 bit, resulting in file
system damage
h
Seems also root is missing files - I cant log in even as root to Gnome.
I only have access to root terminal and users failsafe terminal. GDM
does come up - but logging in as any user produces an error saying
seahorse.bin does not exist.
--
Returning from suspend doesnt work right in Hardy 64 bit,
I made a separate bug report of this, since Im running 64 bit Hardy. The
first description here tells almost exactly what happened to me
yesterday. I am running Hardy alpha 5, updated to latest packages
yesterday. I tried suspending, then woke ut up - keyboard and mouse
didnt work, not even ctrl-al
Public bug reported:
I tried suspending on Hardy 64 bit version, updated to latest packages
yesterday - Installed from Hardy alpha 5. Running kernel 2.6.24-14-rt
(realtime kernel, stock from repos) as of yesterday. Dont know what the
relevant package is.
After trying to return from suspend, the p
Bah, left an error in that comment...
So to recap:
I installed fresh Hardy alpha 5, Firefox would not start.
Installed updates, also Firefox update. Tested - will not start. No
output.
Shut down machine, power it up today- test Firefox - it works fine so
far.
--
Firefox or Swiftfox will not sta
Weird...Now Firefox will start :)
I dont know if it was some update, didnt see any Firefox related ones..Or maybe
it was that the machine was shut down and booted up today.
Before making that bug report, I tried to launch Firefox several times, thru
terminal, Run app and menu. It gave no output a
Public bug reported:
Binary package hint: firefox-3.0
I installed Hardy Heron alpha 5, Firefox wouldnt start. It gives no
output at all in terminal, simply fails to execute anything. I also
installed latest Swiftfox, same thing - it wont start, no terminal
output.
Today I updated to latest packa
Youre saying its still unfixed in Hardy?
I havent been able to get my XMMS to play any FLACs now on my 64-bit
system..Even tried installing the plugin from Feistys repos, no cigar.
Luckily Audacious works...
--
[GUTSY] XMMS is missing the Flac plugin from repositories
https://bugs.launchpad.net/
What worries me a little is that this bug has been reported already in
Feisty at least, and kernel 2.6.20, and nothing has happened. From what
Ive read on the forums, this wireless card worked flawlessly on Dapper,
and has not worked since. Not enough impact to address the bug, or what
is the case?
There seems to be a bug in DWL-610 driver...See this report:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/157519
May be that blacklisting the driver and using Windows driver with
Ndiswrapper may work, I have not tried this yet. My problems started
when I first typed in the WE
I confirm this as well with Gutsy 7.10 on Thinkpad a21m with D-Link Air
DWL-610 card. The card worked until I entered my WEP password for the
first time causing a kernel panic. Now I get a kernel panic every time I
insert the card or boot up with the card attached.
See also this other older bug re
Heres the relevant posts on Ubuntu forums as well..
http://ubuntuforums.org/showthread.php?p=4002248#post4002248
http://ubuntuforums.org/showthread.php?t=590258&highlight=dwl+610
--
Ubunty 7.10 total crash with D-Link DWL-610 when trying to use WEP key
https://bugs.launchpad.net/bugs/157519
You r
DWL-610 also causes problems on Gutsy. It worked until I entered my WEP
password for the first time. Entering the WEP caused a kernel panic, and
now I get a kernel panic every time I insert the card, or if its
inserted when booting. I havent installed ndiswrapper.
Heres couple of links to people o
I found another solution (the most obvious one lol)...Compile the XMMS
plugin from source.
You need to first install "xmms-dev" package from Gutsy repos, as well
as the basic "flac" package. Then surf on to Flac homepage at
http://flac.sourceforge.net/ and grab the source tarball (I suppose its
be
Federico: yes, sounds like the same bug, on my system also it hanged every time
I tried to add a torrent...I had the same Azureus tarball working in Dapper,
Edgy and Feisty and then the problem appeared after installing the Gutsy
alpha..
Havent tested this now after Gutsy final since I moved
I confirm this bug on Nvidia FX 5200 as well. I had first installed the new
Nvidia driver 100.14.19 and rebooted, everything worked fine. Then I updated to
newest packages, including Compiz, and I get the same error as people above and
compiz wont start - gives the Comparing resolution (1280x102
And heres the terminal output of running Azureus...
[EMAIL PROTECTED]:~/azureus$ ./azureus
Starting Azureus...
Java exec found in PATH. Verifying...
Suitable java version found [java = 1.6.0_02]
Configuring environment...
Loading Azureus:
java -Xms16m -Xmx128m -cp
"/home/dromedar/azureus/Azureus2
Yes, thank you for your response. I know this is an unsupported Azureus
version, but I had the feeling it might be Java related more than
Azureus related, since it has always worked before (have used the same
Azureus version with both Edgy and Feisty and their testing versions).
Also there seems to
Public bug reported:
Binary package hint: xmms
Gutsys repositories seem to be missing the Flac plugin for XMMS. Hence,
XMMS cannot play Flac audio.
** Affects: xmms (Ubuntu)
Importance: Undecided
Status: New
--
[GUTSY] XMMS is missing the Flac plugin from repositories
https://bug
Public bug reported:
Ive been running two test systems for Gutsy, both are clean installs
from alpha 4 and not upgrades. Running latest up to date packages as of
today.
Running Azureus 2.5.0.4 from the tarballed binary they distribute, on both my
systems (both Pentium 4 machines).
Azureus will c
More info, I deleted old .azureus folder and untarred the azureus
folder, meaning a clean install, and the bug still persists - azureus
crashes every time I try to add torrents.
--
Azureus crashed when starting a new torrent
https://bugs.launchpad.net/bugs/80666
You received this bug notification
I am using Sun Java 1.6, and Azureus crashes every time I try to add new
torrents. It simply hangs. It works otherwise, ie. seeding torrents
started before I installed Gutsy alpha. Confirmed behaviour with latest
updates today, on two different machines. Java bug most likely?
--
Azureus crashed w
Bug is still there for me, tested on two machines with latest Feisty
yesterday, fresh Beta install and then updated to latest packages. Both
machines have 2 ethernet cards, other one is static LAN and other DHCP
internet. On both machines, when booting up the DHCP connection is down,
and when using
Nope :( still broken with latest updates. As described above.
--
network-manager in feisty is broken
https://launchpad.net/bugs/82715
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This is as of today (25.3.) still broken in the way I described above,
using two wired interfaces. Im running Feisty Herd 5 updated to all
latest packages. Still am unable to configure 2 interfaces using the
network manager, can only have one active interface at a time.
--
network-manager in feis
Also, Nautilus doesnt remember the widths of the columns if theyre
changed. When you close and reopen Nautilus window, the columns revert
to their original widths. Happens every time.
--
[Feisty] "Name" column width in nautilus
https://launchpad.net/bugs/93381
--
ubuntu-bugs mailing list
ubuntu
I also have broken network manager with only wired networks in use. I
have two generic Ethernet cards that have always worked before, and
which are guaranteed Linux-supported by manufacturers (from Hoary till
Dapper have always worked).
I installed Herd 5 yesterday and updated to latest packages.
I also have broken network manager with only wired networks in use. I
have two generic Ethernet cards that have always worked before, and
which are guaranteed Linux-supported by manufacturers (from Hoary till
Dapper have always worked).
I installed Herd 5 yesterday and updated to latest packages.
I also have broken network manager. I have two generic Ethernet cards
that have always worked before, and which are guaranteed Linux-supported
by manufacturers (from Hoary till Dapper have always worked).
I installed Herd 5 yesterday and updated to latest packages. At first
both network interfaces
Public bug reported:
Trying to install from Live cd, installer starts fine, could select keyoboard
and timezone. When installer should start the partitioner, it crashes. Screen
is frozen and filled with corrupted graphics. System responds to
ctrl-alt-bckspace or virtual terminal.
Tried install
Public bug reported:
When trying to install from text mode cd of Herd 2, installer crashes after
"Detecting cdrom" is succesful (after selecting language etc) and installer
should next start the partitioner.
It also crashes the same way when i try to run "Verify disc": crashes after
succesfully
Now I also installed SSH server on both boxes, and tried moving files
with both scp and the Nautilus interface. SSH transfers on LAN work at
the same slow speed as SMB and NFS, so only HTTP protocol seems to
utilize full ethernet speed. Im at a loss to explain what might cause
it. Ive also disabled
Today I reinstalled and reconfigured all Samba components (samba-common,
samba, smbfs), and the problem persists still. Sometimes speed goes up
to 3-5 megs one way, but still works slowly moving files the other way
around (ie. when I move stuff from box 1 to box 2, its slow, but when
moving files f
Public bug reported:
In Dapper final release, both SMB and NFS mounts accessed across LAN
(100mbit ethernet) transfer data at about 1/10 rate of what it should
be. Meaning a transfer rate of 300-700 kilos/sec, when it normally is
closer to 10 megabytes.
The problem is there with both Samba and NF
98 matches
Mail list logo
