Re: [Bug 97278] Re: Wired network not enabled upon system boot
*** This bug is a duplicate of bug 83143 *** https://bugs.launchpad.net/bugs/83143 This problem has never been fixed in Ubuntu 7.04 but it's fixed in 7.10. I hope the fix would be backported into the impacted previous release... -- Wired network not enabled upon system boot https://bugs.launchpad.net/bugs/97278 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 83143] Re: does not automatically start the wired connection due to missing link beat
This problem has never been fixed in Ubuntu 7.04 but it's fixed in 7.10. I hope the fix would be backported into the impacted previous release... -- does not automatically start the wired connection due to missing link beat https://bugs.launchpad.net/bugs/83143 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83143] Re: does not automatically start the wired connection due to missing link beat
The problem is fixed for me in Gutsy Tribe 5. My wired ethernet interface is up when I log in the GUI. -- does not automatically start the wired connection due to missing link beat https://bugs.launchpad.net/bugs/83143 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90267] Re: network-manager stops and restarts already ifup'ed interfaces
The problem is fixed for me in Gutsy Tribe 5. My wired ethernet interface is up when I log in the GUI. Before I had to use the network manager applet and pick "wired interface" for it to come up. -- network-manager stops and restarts already ifup'ed interfaces https://bugs.launchpad.net/bugs/90267 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
*** This bug is a duplicate of bug 83143 *** https://bugs.launchpad.net/bugs/83143 Gutsy Tribe 5 is also working fine for me. My wired ethernet interface is up when I'm logged in the GUI. -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 14762] Re: xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
unfortunately, the Gusty Tribes 5 live CD fails the same way. When it launches the GUI, the screen becomes garbled and the only thing to do is to reset. In the previous Ubuntu release, adding the line below in Xorg.conf, fixed the problem . Doing "man nv" in a shell shows what the parameter is used for. line to add in xorg.conf in the "nv" driver section to make Geforce 6600 work properly; Option "CrtcNumber" "0" Thank Timo for looking into this. -- xorg won't start on nvida 6600 card due to nv driver not supporting 6600's https://bugs.launchpad.net/bugs/14762 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/mailman/listinfo/ubuntu-bugs
[Bug 102683] Re: xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
any update on this bug? thanks -- xorg won't start on nvida 6600 card due to nv driver not supporting 6600's https://bugs.launchpad.net/bugs/102683 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83143] Re: does not automatically start the wired connection due to missing link beat
agreed that if the bug is not in that application you should track the problem. Just to correct some of your comment; The hardware which is not working with Feisty has been working PERFECTLY with Debian, Suse, Fedora, Ubuntu Dapper for the longest time. There really is a bug in Feisty somewhere in the networking and that bug was not there in previous release. The bug is also present in the Debian testing release "Lenny". Would be nice to have some suggestion of which subsystem could be the problem. Not sure bug 90267, describe the problem I reported. -- does not automatically start the wired connection due to missing link beat https://bugs.launchpad.net/bugs/83143 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 41979] Re: xserver-xorg crashes when handling newer nvidia cards
The problem where the "nv' driver doesn't auto detect the monitor is not fixed for ALL configuration. On my PC this is not fixed. I need to add manually the line below for it to work; Option "CrtcNumber" "0" -- xserver-xorg crashes when handling newer nvidia cards https://bugs.launchpad.net/bugs/41979 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/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
*** This bug is a duplicate of bug 83143 *** https://bugs.launchpad.net/bugs/83143 Thanks, BTW after a fresh install of latest Debian Etch 4.0, it also show the exact same problem. I assume the fix will also be pushed to Debian. -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 41979] Re: xserver-xorg crashes when handling newer nvidia cards
This seems a duplicate of Bug #102683 . The screenshot is exactly what's
I've got. The problem seems to be with the autodection of monitor.
Try putting back the driver as "nv" and assuming your monitor is plugged in
port 0 of the videocard add the line below in the section describing the "nv"
driver of your /etc/X11/Xorg.cong;
Option "CrtcNumber" "0"
The paragraph describin your driver should look like this ("..." are other
lines that may be there already) ;
Section "Device"
Identifier "nVidia Corporation NV43 [GeForce 6600 GT]"
Driver "nv"
Option "CrtcNumber" "0"
...
EndSection
Fore more description about this option you can do;
$ man nv
Does this dix the problem?
--
xserver-xorg crashes when handling newer nvidia cards
https://bugs.launchpad.net/bugs/41979
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/mailman/listinfo/ubuntu-bugs
[Bug 102683] Re: xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
The screen display I've got when the problem is occuring is identical to the screenshot attached to Bug #41979 The issue is with the autodection of monitor. Adding line; Option "CrtcNumber" "0" makes the problem go away. Is there any new driver we can try to see if the problem is now fixed? We can't expect people to edit their xorg.conf to add this line. thanks -- xorg won't start on nvida 6600 card due to nv driver not supporting 6600's https://bugs.launchpad.net/bugs/102683 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97669] Re: [feisty] Installing from alternate install CD leaves cdrom source in apt's sources.list
I think the bug priority is at least medium -The problem after the install of Feisty (2007-04-15 build) is that it leaves TWO identical entries in "Software Source application" for the CDROM. These entries read as; Cdrom with Ubuntu 7.04 "Feisty Fawn" Officially supported Restricted copyright Then if you try to deselect the one selected by default and re-add it later you have an error message. Here is how to reproduce the problem; 1-in the "installable from CD-ROM/DVD" scroll list in software source. Try to deselect the one selected by default and "close" software source. Then restart software source and re-add the second "cd-rom" by selecting it and click "close" in software source and "close" again to update the package list. You'll be presented with the following error; Could not download all repository indexes The repository might be no longer available or could not be contacted because of network problems. If available an older version of the failed index will be used. Otherwise the repository will be ignored. Check your network connection and the correct writing of the repository address in the preferences. cdrom:[Ubuntu 7.04 _Feisty Fawn_ - Release i386 (20070415)]/dists/feisty/main/binary-i386/Packages.gz: Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs cdrom:[Ubuntu 7.04 _Feisty Fawn_ - Release i386 (20070415)]/dists/feisty/restricted/binary-i386/Packages.gz: Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs In summary; -There should only be one entry for the CD-ROM in first place -There is an error if you try to re-add the CD-ROM if you previously de-selected it -My view is that this bug is medium-high priority thanks -- [feisty] Installing from alternate install CD leaves cdrom source in apt's sources.list https://bugs.launchpad.net/bugs/97669 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102683] Re: xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
Thanks Timo. How will I know this update has been pulled from my computer? The next time I see changes to xserver-xorg-video-nv? Is there any expected timeframe? 1-2 weeks? thanks -- xorg won't start on nvida 6600 card due to nv driver not supporting 6600's https://bugs.launchpad.net/bugs/102683 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
Hi Martin, That network card has been working without problem with Ubuntu 6.06 without a glitch and with many different Linux distro. It's only in Feisty that this problem occurs. Here is the output; $ dmesg | grep link [ 23.772183] audit: initializing netlink socket (disabled) Did you compare the last 4 files sent in my replies above aemon.log, daemon_after.log messages messages_after ? These logs are capture immediately after bootup and then re-capture after pressing on the networking applet then "wired Network". What else would be usefull for you? thanks -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
bug is NOT fixed. Changing the bug status to "unconfirmed". -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
Is there someone with enough privilege to re-open the bug status to "confirmed"? The problem is NOT fixed. Do I need to re-open a new bug with same description? ** Changed in: network-manager (Ubuntu) Status: Fix Released => Unconfirmed -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
sorry, this bug is NOT fixed. Please re open the bug -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
forgot to mention in my reply above that the system got many package updated today and the networking problem is still there. What other information might be usefull to you for debugging? thanks -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
** Attachment added: "messages_after" http://librarian.launchpad.net/7338137/messages_after -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
** Attachment added: "messages" http://librarian.launchpad.net/7338123/messages -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
** Attachment added: "daemon_after.log" http://librarian.launchpad.net/7338122/daemon_after.log -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
In attachement are 4 files. deamon.log (/var/log/daemon.log) and messages (/var/log/messages) take after a clean bootup. I recapture the same file after clicking on the networking applet and on the "wired connection" so that Feisty connect to the network. If you do a diff of the two logs files you'll see intersting things that occured. There was some dhcdbd error messages in the /var/log/messages that appears after clicking the network applet. Before booting the PC, the content of both /var/log/messages and daemon.log was erased to eliminate previous boot noise... $ diff daemon.log daemon_after.log Two lines were a bit scary; 1) eth0: Driver 'dmfe' does not support carrier detection. ^IYou must switch to it manually 2) Deactivating device eth0. Then doing ; $ diff messages messages_after What's that redhat in the path? 1) Apr 16 18:20:58 ubuntu dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason The 4 files are in attachement. The interface file is already attached in a previous comment above. ** Attachment added: "daemon.log" http://librarian.launchpad.net/7338121/daemon.log -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102683] Re: xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
OK, it's understandable that the fix may not be in for Feisty release. It would be appreciated if the investigation can continue as soon as possible. Is there any timeframe estimate for continuing to look into the issue? As soon as you have new things to try out to isolate the problem tell me. thanks again -- xorg won't start on nvida 6600 card due to nv driver not supporting 6600's https://bugs.launchpad.net/bugs/102683 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102683] Re: xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
-Adding this parameter did make the new "nv" driver you asked me to try work all the time. -Here are the "nv" pameters used in xorg.conf; Section "Device" Identifier "nVidia Corporation NV43 [GeForce 6600 GT]" Driver "nv" Option "CrtcNumber" "0" Busid "PCI:1:0:0" Option "AddARGBVisuals""True" Option "AddARGBGLXVisuals" "True" Option "NoLogo""True" EndSection NOTE: some extra option comes from nvidia-glx driver but their don't seem to harm "nv". -in attachement the log produced by "nv" with "CrtcNumber" parameter. -The problem is now to make the driver work all the time after fresh installation. New user can't be expected to add parameters in their xorg.conf. Even Linux literate won't know that they need to tweak this parameter. -How do I revert back (i.e. apt/dpkg commands) to the "nv" driver from Feisty distro to try it out too? I only tried the driver you sent me. -Do you have a new driver that detects the correct monitor that I can try out? thanks veru much ** Attachment added: "Xorg.0.log_newnvwithparam.txt" http://librarian.launchpad.net/7318229/Xorg.0.log_newnvwithparam.txt -- xorg won't start on nvida 6600 card due to nv driver not supporting 6600's https://bugs.launchpad.net/bugs/102683 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102683] Re: xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
Here is the other attachement. In this case the new driver failed. What you want me to do next? thanks very much ** Attachment added: "Xorg.0.log_nvafternv.txt" http://librarian.launchpad.net/7315307/Xorg.0.log_nvafternv.txt -- xorg won't start on nvida 6600 card due to nv driver not supporting 6600's https://bugs.launchpad.net/bugs/102683 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102683] Re: xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
Unfortunately this new driver did not fix the problem. The problem is still there and there is no behavior change with this new driver. This new driver work only ONCE and it's when it's used IMMEDIATELY after the proprietary nVidia driver from the company nVidia. In all other circumstance it fails like described above. I proved I installed the driver like this; $ dpkg -i xserver-xorg-video-nv_2.0.0-0ubuntu3.1_i386.deb I proved I used this new driver; $ diff /usr/lib/xorg/modules/drivers/nv_drv.so nv_drv.so.bak Binary files /usr/lib/xorg/modules/drivers/nv_drv.so and nv_drv.so.bak differ The diff below shows the /var/log/Xorg.0.log difference when the new "nv" driver worked after being invoked after nVidia proprietary driver ran (attached file: Xorg.0.log_nvafternvidia.txt). The other file is after "nv" was relaunched after "nv" ran once, in this scenario the "nv" didn't found the Analog device port A and found the wrong CRTC (attached file: Xorg.0.log_nvafternv.txt). You can see that the file Xorg.0.log_nvafternv.txt is showing you that the driver failed to find "analog device on output A" and it was mistaken by finding there was a monitor CRTC 1. I have only one monitor attached to port 0 as it's detected when "nv" had detected when it worked (after running after nvidia driver). When "nv" ran without problem it found "analog device on output A" and found monitor 0 "Using CRT on CRTC 0". $ diff -Nur Xorg.0.log_nvafternvidia.txt Xorg.0.log_nvafternv.txt --- Xorg.0.log_nvafternvidia.txt2007-04-12 20:21:05.0 -0400 +++ Xorg.0.log_nvafternv.txt2007-04-12 20:21:46.0 -0400 @@ -11,7 +11,7 @@ Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. -(==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 12 20:19:44 2007 +(==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 12 20:21:21 2007 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) @@ -428,7 +428,7 @@ (II) Reloading /usr/lib/xorg/modules//libddc.so (II) NV(0): I2C bus "DDC" initialized. (II) NV(0): Probing for analog device on output A... -(--) NV(0): ...found one +(--) NV(0): ...can't find one (II) NV(0): Probing for analog device on output B... (--) NV(0): ...found one (II) NV(0): Probing for EDID on I2C bus A... @@ -495,8 +495,8 @@ (II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0. (II) NV(0): I2C device "DDC:ddc2" removed. (II) NV(0): ... none found -(--) NV(0): CRTC 0 appears to have a CRT attached -(II) NV(0): Using CRT on CRTC 0 +(--) NV(0): CRTC 1 appears to have a CRT attached +(II) NV(0): Using CRT on CRTC 1 (II) NV(0): Using hsync ranges from config file (II) NV(0): Using vrefresh ranges from config file (II) NV(0): Printing DDC gathered Modelines: @@ -848,5 +848,3 @@ Could not init font path element /usr/X11R6/lib/X11/fonts/misc, removing from list! Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1, removing from list! -(II) Open ACPI successful (/var/run/acpid.socket) -(II) Configured Mouse: ps2EnableDataReporting: succeeded Is there another driver you want me to test? thanks very much P.S. I attach the two new log files; ** Attachment added: "Xorg.0.log_nvafternvidia.txt" http://librarian.launchpad.net/7315304/Xorg.0.log_nvafternvidia.txt -- xorg won't start on nvida 6600 card due to nv driver not supporting 6600's https://bugs.launchpad.net/bugs/102683 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 94095] Re: Ethernet interface not configured at boot time
Hi Robert, My Feisty just got update few minutes ago (april 10). I rebooted and the ethernet connection was not setup after reboot. I had to click again on the small network applet in toolbar and select "Wired Connection". I tried to change the config of the network interface in "Network Settings" to enable Roaming mode. I rebooted and still the network interface is not enabled after I logged in. So I disabled the "Roaming mode", rebooted and did the following commands; Immediately after reboot here is the state of my eth0; $ sudo ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:50:2C:08:B9:02 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:46 errors:0 dropped:0 overruns:0 frame:0 TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:13852 (13.5 KiB) TX bytes:1216 (1.1 KiB) Interrupt:19 Base address:0x9800 Then I tried to bringup and got the following message; $ sudo ifup eth0 ifup: interface eth0 already configured Then I tried to bring down and bring back up and it worked; $ sudo ifdown eth0 There is already a pid file /var/run/dhclient.eth0.pid with pid 4078 killed old client process, removed PID file Internet Systems Consortium DHCP Client V3.0.4 ... $ sudo ifup eth0 There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416 Internet Systems Consortium DHCP Client V3.0.4 Copyright 2004-2006 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth0/00:50:2c:08:b9:02 Sending on LPF/eth0/00:50:2c:08:b9:02 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20 DHCPOFFER from 192.168.0.175 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 192.168.0.175 bound to 192.168.0.100 -- renewal in 65270 seconds. At that point the inerface is fine and up although the applet still beleive the network interface is still off (this was expected). Here is my interface file; ~$ sudo cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface iface eth0 inet dhcp auto eth0 This bug is still not fixed. Are you ok to re-open the bug? Is there any test I can do on my machine or any files I need to check? What should I do to re-open the bug, can we transition the bug from fixed to non fixed. I guess the priority is at least medium if not high. thanks Steve On Tue, 2007-10-04 at 15:28 +, Robert Clark wrote: > This issue was apparently fixed through one of the feisty updates. I > have not had any Ethernet configuration at startup up issues for over a > week now. > > I consider this bug Fixed. Thanks Ubuntu Team! > -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94095] Re: Ethernet interface not configured at boot time
Using Feisty Beta I have same problem. The PC has a single Ethernet card "eth0" using DHCP. When Feisty boots, the eth0 interface is not enabled. The first time I log on after each reboot, I have to click on the small networking applet and click on "wired connection". Then the eth0 is braught up and work fine. The problem is that it should have been enabled by default during the boot of Ubuntu Feisty instead of requiring human intervention after each reboot. I checked in the networking configuration tool under GNOME and KDE don't see any misconfiguration for the networking and interfaces. This was not a problem under dapper. This will confuse new Ubuntu users if their interface is not ON by default. any suggestions? thanks -- Ethernet interface not configured at boot time https://bugs.launchpad.net/bugs/94095 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98795] Re: [Feisty Beta] software-properties-gtk corrupts /etc/apt/source.list
I tested using 0.59.3 the problem seems fixed. Thanks very much I have two questions; Q1 - I find strange that there is two exactly identical entry for CR-ROM. Line 2 and 4 are the same and this shows in the dialog box I put in attachment.; 1:# 2:# deb cdrom:[Ubuntu 7.04 _Feisty Fawn_ - Beta i386 (20070322.2)]/ feisty main restricted 3:deb-src http://archive.ubuntu.com/ubuntu/ feisty restricted main #Added by software-properties 4:deb cdrom:[Ubuntu 7.04 _Feisty Fawn_ - Beta i386 (20070322.2)]/ feisty main restricted 5:# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to 6:# newer versions of the distribution. These lines comes directly from feisty alternate-i386 install. It looks to me there is a problem? Why is there two identical lines? Q2 - Why someone an option in software-properties-gtk is neither cleared or checked but is has a '-' in the box. If you click on it, it become a check mark. If you click again it becomes clear. If you click it becomes checkmark. So what does '-' meant? As a user I'm confused and I can't replace the button in the original setting '-' before leaving the dialog. So I don't know what changes are to be expected coming from that change. Does the tool put a '-' when it's not sure because of some inconsistency in the source.list file? thanks again ** Attachment added: "softsrc.png" http://librarian.launchpad.net/7176687/softsrc.png -- [Feisty Beta] software-properties-gtk corrupts /etc/apt/source.list https://bugs.launchpad.net/bugs/98795 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 100005] Re: grub: feisty linux-image 2.6.20-13, wrong root device in menu.lst
surpise! I just updated Feisty and a new kernel as been downloaded; linux-image-2.6.20-14-generic Beleive it or not, for this kernel I must use root=/dev/sdb7 else kernel stop booting at "Uniform CD-ROM drive Revision: 3.20" In summary, linux-image-2.6.20-12-generic -> the Kernel boot parameter had to be root=/dev/sdb7 linux-image-2.6.20-13-generic -> the Kernel boot parameter had to be root=/dev/hdb7 linux-image-2.6.20-14-generic -> the Kernel boot parameter has to be root=/dev/sdb7 That's interesting! I don't understand what's going on. Any suggestions? thanks -- grub: feisty linux-image 2.6.20-13, wrong root device in menu.lst https://bugs.launchpad.net/bugs/15 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102683] Re: xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
** Attachment added: "nvafternvidiaok" http://librarian.launchpad.net/7176575/nvafternvidiaok -- xorg won't start on nvida 6600 card due to nv driver not supporting 6600's https://bugs.launchpad.net/bugs/102683 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102683] Re: xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
-The 'splash' kernel command line is never used. -I Tried with and without vga=0x31A and it makes no difference. In both case the "nv" driver fails and screen is all garbled. This parameters (vga=0x31A ) is for using the video frame buffer and have high resolution font at the console. -I Found out something very interesting. If I change the video driver in xorg.conf to "nv" and restart X.org it is working only if "nv" is immediately used after the proprietary driver "nvidia" (from nVidia) is used (no computer reboot in between). This look like something on the video card is not initialized properly by "nv" but this thing is left initalized properly after proprietary "nvidia" ran just before "nv" is used. If I try to launch a second time Xorg with "nv", it fails miserably. BUT if I relaunch X.org with the proprietary "nvidia" and then relaunch with "nv" it works again. Here is how I proceed; 1-Boot the PC and go "telinit 1" 2-Edit /etc/X11/xorg.conf and set driver to "nvidia" then launch X.org (by invoking startx ). Xorg start properly. Then exit X.org (CTRL- Backspace) (computer is NOT rebooted). 3-clear /var/log/Xorg.0 and edit /etc/X11/xorg.conf and set driver to "nv" then launch X.org (by invoking startx ). HO SURPRISE, "NV" DRIVER WORKS!! I capture the /var/log/Xorg.0.log as "nvafternvidiaok", then exit X.org (CTRL-Backspace) (computer is NOT rebooted) 4-Launch X.org again (by invoking startx ). NOW "NV" DRIVER FAILS AND SCREEN IS GARBLED!! I capture the /var/log/Xorg.0.log as "nvafternvbad", then exit X.org (CTRL-Backspace) (computer is NOT rebooted) Every time "nv" is used either after "nv" or "vesa", it fails to works. Every time "nv" is used after "nvidia" it works. The video card works with "vesa" driver all the time. Note that I know "nv" was working in the test above as the refresh rate was different than proprietary driver so visually I can see it's not the "nVidia" driver. If you look at the difference of both logs file you see this; $ diff -Nur nvafternvidiaok nvafternvbad --- nvafternvidiaok 2007-04-05 22:03:24.0 -0400 +++ nvafternvbad2007-04-05 22:05:01.0 -0400 @@ -11,7 +11,7 @@ Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. -(==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 5 22:00:22 2007 +(==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 5 22:04:28 2007 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) @@ -429,7 +429,7 @@ (II) Reloading /usr/lib/xorg/modules//libddc.so (II) NV(0): I2C bus "DDC" initialized. (II) NV(0): Probing for analog device on output A... -(--) NV(0): ...found one +(--) NV(0): ...can't find one (II) NV(0): Probing for analog device on output B... (--) NV(0): ...found one (II) NV(0): Probing for EDID on I2C bus A... @@ -496,8 +496,8 @@ (II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0. (II) NV(0): I2C device "DDC:ddc2" removed. (II) NV(0): ... none found -(--) NV(0): CRTC 0 appears to have a CRT attached -(II) NV(0): Using CRT on CRTC 0 +(--) NV(0): CRTC 1 appears to have a CRT attached +(II) NV(0): Using CRT on CRTC 1 (II) NV(0): Using hsync ranges from config file (II) NV(0): Using vrefresh ranges from config file (II) NV(0): Printing DDC gathered Modelines: In summary for some reason when the "nv" driver fails it seems it fails at "Probing for analog device on output A". Also, it seems that when it fails, it think it must use CRTC 1. I only have one monitor attached to the video card. I don't know what this means. Is there anything else I can do? Do you want me to try one instrumented "nv" driver you can give me? thanks ** Attachment added: "nvafternvbad" http://librarian.launchpad.net/7176573/nvafternvbad -- xorg won't start on nvida 6600 card due to nv driver not supporting 6600's https://bugs.launchpad.net/bugs/102683 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102683] Re: xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
The /etc/X11/xorg.conf with vesa anything else you need? thanks again ** Attachment added: "xorg.conf" http://librarian.launchpad.net/7140533/xorg.conf -- xorg won't start on nvida 6600 card due to nv driver not supporting 6600's https://bugs.launchpad.net/bugs/102683 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102683] Re: xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
logs when starting with vesa ** Attachment added: "Xorg.0.log_VESA" http://librarian.launchpad.net/7140512/Xorg.0.log_VESA -- xorg won't start on nvida 6600 card due to nv driver not supporting 6600's https://bugs.launchpad.net/bugs/102683 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102683] Re: xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
Monitor is Viewsonic P225fb 21inchs monitor (tube) $ lspci |grep nVidia 01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600/GeForce 6600 GT] (rev a2) $ cat /proc/cmdline root=/dev/hdb7 ro vga=0x31A Logs are attached when Xorg is using NV driver (Note: after installing nvidia-glx, there are still some parameter left in the xorg.conf file. I assume this is no problem because the "vesa" driver works fine event though those parameters are still there... ) ** Attachment added: "Xorg.0.log_NV" http://librarian.launchpad.net/7140511/Xorg.0.log_NV -- xorg won't start on nvida 6600 card due to nv driver not supporting 6600's https://bugs.launchpad.net/bugs/102683 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 14762] Re: xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
Problem still there. Reported the bug and number is bug # 102683 P.S. I clicked by mistake on a button that makes bug 14762 being reported to "kubuntu-default-settings (Ubuntu)". Unfortunately, there is no undo button... Please ignore the "kubuntu-default-settings (Ubuntu)"... -- xorg won't start on nvida 6600 card due to nv driver not supporting 6600's https://bugs.launchpad.net/bugs/14762 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kubuntu-default-settings in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 102683] xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
Public bug reported: Binary package hint: xserver-xorg-driver-nv During Ubuntu 7.04 Beta installation, the Geforce 6600 has been detected and assigned video driver xorg "nv" in /etc/xorg.conf. This is what was expected. After reboot into newly installed Feisty, Xorg started and video display is all garbled, strecthed and with wrong colors. Possible Workaround found (use at your own risk) - I had to switch to console; CTRL-ALT-F1 - Go in single user mode; $ telinit 1 - Change video driver from "nv" to "vesa" in the xorg.conf; sudo vi /etc/xorg.conf and replace "nv" by "vesa" or $ sudo cp /etc/xorg.conf /etc/xorg.conf.orig; sudo sed s/nv/vesa/ /etc/xorg.conf > /tmp/tst; sudo cp /tmp/tst /etc/xorg.conf -Go back to multiuser graphic mode $ telinit 2 After xorg restarted, Xorg should work properly since it would be using "vesa" driver instead of "nv" driver. Processor used: Intel Pentium IV 2.4GigHz Videocard: BFG Geforce 6600 GT OC 128Meg (AGP video card) It seems the "nv" driver is broken. Feisty is updated as of april 3 and the problem with Xorg "nv" driver is still there. For this PC configuration, it would have been better if Ubuntu installation would have used "vesa" driver for in the xorg.conf file. When the video is gardbled, you can sometime recognize part of the gdm/kdm login screen. The image is very stretched and with all the wrong colors... P.S. There is no linux distro and no Xorg "nv" driver that has ever worked on this PC and this video card. Xorg "vesa" driver works fine. The proprietary driver from Nvidia works perfectly. thanks ** Affects: xorg (Ubuntu) Importance: Undecided Status: Unconfirmed -- xorg won't start on nvida 6600 card due to nv driver not supporting 6600's https://bugs.launchpad.net/bugs/102683 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98795] Re: [Feisty Beta] software-properties-gtk corrupts /etc/apt/source.list
** Summary changed: - software-properties-gtk corrupted /etc/apt/source.list + [Feisty Beta] software-properties-gtk corrupts /etc/apt/source.list -- [Feisty Beta] software-properties-gtk corrupts /etc/apt/source.list https://bugs.launchpad.net/bugs/98795 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97629] Re: Feisty Beta - Cannot disable installer CD repo in Synaptic
This seems also to be related to the bug 98795 I raised. Not only you can't remove CD-ROM but if you click on any options in software source dialog shown by in the screenshot.png dialog will endup by corrupting the source.lust. I think this bug is very serious as no other application that reads the source.list will return the error I put in bug 98795. Try doing an ubuntu software update and you'll see the error message. Unless this bug is corrected. the software source dialog can't be used. New user won't know how to fix source.list once corrupted and will be intimidated to use shell to comment the CD-ROM line in source.list. -- Feisty Beta - Cannot disable installer CD repo in Synaptic https://bugs.launchpad.net/bugs/97629 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 100005] Re: grub: feisty linux-image 2.6.20-13, wrong root device in menu.lst
The computer has many linux partition. It has one main Linux (ubuntu 6.06) partition which is the ONLY ONE having grub installed. Feisty was installed in a separate parition. During feisty installation, grub installation was skipped BUT the dialog box indicated to boot feisty from /dev/sdb7. I added the following grub entry which worked fine (note it's 2.6.20-12); Grub Parameters for that kernel; title Ubuntu 7.04 Hdb7, kernel 2.6.20-12 root (hd1,6) kernel /boot/vmlinuz-2.6.20-12-generic root=/dev/sdb7 ro vga=0x31A initrd /boot/initrd.img-2.6.20-12-generic boot I always used /dev/hdb7 in previous linux installed I found strange to use /dev/sdb7 but someone indicated that feisty was using /dev/sdbNN because of the new libpata... Feisty was running fine with the grub entry above. Trying to use root=/dev/hdb7 with feisty kernel 2.6.20-12 was not working. Then during one feisty update, kernel 2.6.20-13 was installed. Feisty kernel upgrade couldn't update the grub entry above since it's in another linux partition. I had to manually update the grub entry above entry by changing 2.6.20-12 by 2.6.20-13 and leaving root=/dev/sdb7. When booting this new 2.6.20-13, the kernel hang at "Uniform CD-ROM drive Revision: 3.20" and I raised the problem in launchpad. After some more experientation with Linux Kernel SysRequest debuggin feature. I have been able to see the message like "couldn't find /dev/sdb7". I then tried to update the grub entry to pass root=/dev/hdb7. Since then the kernel 2.6.20-13 is working as expected. I do not know if the other people on IRC who indicated that they had the problem, where kernel stop at CD-ROM line, were also using root=/dev/sdbNN instead of root=/dev/hdbNN in their grub menu.lst. Is this something that has changed between kernel 2.6.20-12 and 2.6.20-13? P.S> I would have liked in first place that during feisty install, when skipping the grub installation, the ubuntu installation should write a sample grub menul.lst file in /root updated for the system being installed. thanks Is there any information that could be usefull for you? -- grub: feisty linux-image 2.6.20-13, wrong root device in menu.lst https://bugs.launchpad.net/bugs/15 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 100005] Re: feisty linux-image 2.6.20-13 stop booting at; Uniform CD-ROM driver Revision: 3.20
Problem has been found. Feisty is not the booting partition this PC, hence the kernel parameters in grub are located in another partition. After an update of feisty, I need to changes manually the grub parameters by manually mounting and editing the grub menu.lst. After Feisty upgrade to 2.6.20-13, I updated the grub menu.lst but I had not renamed root=/dev/sdb7 as root=/dev/hdb7. Don't know why in first place /dev/sdb7 was used... Anyway, after setting root=/dev/sdb7, problem went away. As a suggestion, it would be nice if the grub parameters would be suggested to the administrator of the system when a linux-image is upgraded and most importantly after fresh install. I saw the suggested /dev/sdb7 during the CD-ROM install of feisty alternate i386 but I wasn't suggested any other parameters... thanks -- feisty linux-image 2.6.20-13 stop booting at; Uniform CD-ROM driver Revision: 3.20 https://launchpad.net/bugs/15 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 100005] Re: feisty linux-image 2.6.20-13 stop booting at; Uniform CD-ROM driver Revision: 3.20
I meant after setting root=/dev/hdb7, problem went away. -- feisty linux-image 2.6.20-13 stop booting at; Uniform CD-ROM driver Revision: 3.20 https://launchpad.net/bugs/15 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 100005] Re: feisty linux-image 2.6.20-13 stop booting at; Uniform CD-ROM driver Revision: 3.20
** Tags added: cd-rom feisty linux-image -- feisty linux-image 2.6.20-13 stop booting at; Uniform CD-ROM driver Revision: 3.20 https://launchpad.net/bugs/15 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 100005] feisty linux-image 2.6.20-13 stop booting at; Uniform CD-ROM driver Revision: 3.20
Public bug reported: Ubuntu Feisty 7.04 Beta running kernel linux-image-2.6.20-12-generic (for i386) is working fine. Using kernel from linux- image-2.6.20-13-generic make the system hang at line; Uniform CD-ROM drive Revision: 3.20 Some other people on IRC indicated they had the problem and was able to boot that kernel by hammering on the CD-ROM eject button (and if memory is good, by inserting a CD in the drive). This work around never work when I tried it with my kernel 2.6.20-13. Grub Parameters for that kernel; title Ubuntu 7.04 Hdb7, kernel 2.6.20-13 root(hd1,6) kernel /boot/vmlinuz-2.6.20-13-generic root=/dev/sdb7 ro vga=0x31A initrd /boot/initrd.img-2.6.20-13-generic boot thanks ** Affects: linux-source-2.6.20 (Ubuntu) Importance: Undecided Status: Unconfirmed ** Changed in: Ubuntu Sourcepackagename: None => linux-source-2.6.20 -- feisty linux-image 2.6.20-13 stop booting at; Uniform CD-ROM driver Revision: 3.20 https://launchpad.net/bugs/15 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98795] Re: software-properties-gtk corrupted /etc/apt/source.list
** Description changed: Binary package hint: software-properties-gtk After clean install of Ubuntu 7.04 Beta (i386 alternate), update-manager ran and downloaded some package from the net and prompted me to insert CD-ROM to install updated. I didn't want to install packages from CD- ROM, I then clicked "cancel" and wanted to remove CD-ROM from the source.list by using "software sources" application to only specify internet as package source. I Couldn't find how to remove CD-ROM from the selection in software- properties-gtk and didn't want to edit /etc/apt/source.list manually. I then tried to click few options here and there in software-properties- gtk application. In "Third-Party Software tab", there was no entries and still there is no entry. Then I quit software-properties-gtk application to retry update-manager. update-manager wouldn't start and displayed the following error; "Could not initialize the package information A unresolvable problem occurred while initializing the package information. Please report this bug against the 'update-manager' package and include the following error message: 'E:Malformed line 4 in source list /etc/apt/sources.list (dist parse), E:The list of sources could not be read.' " After commenting out line 4 of /etc/apt/source.list the problem disappeared and update-manager ran fine. It seems like software- properties-gtk corrupted the source.list. Here are the first 8 lines of /etc/apt/source.list [actual lines start after the :] 1:# 2:# deb cdrom:[Ubuntu 7.04 _Feisty Fawn_ - Beta i386 (20070322.2)]/ feisty main restricted 3: 4:deb cdrom:[Ubuntu 7.04 _Feisty Fawn_ - Beta i386 (20070322.2)]/ feisty 5:# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to 6:# newer versions of the distribution. 7: 8:deb http://ca.archive.ubuntu.com/ubuntu/ feisty main restricted it seems the line 4 misses "main restricted" at the end of the line. Also it's strange that line 4 seems to be the same as lthe commented line 2 except for the missing "main restricted". This /etc/apt/source.list was never edited manually. + + Mar 31 Update: I re-installed Ubuntu 7.04 beta and made a backup of the + /etc/apt/source.list. I can confirm that just going in software- + properties application and changing one option (i.e. clicking on "source + code") and saving will make the problem show up. The 4 line of the + source.list is malformed and no other application can read the + source.list without error. ** Tags added: 7.04 software-properties source.list -- software-properties-gtk corrupted /etc/apt/source.list https://launchpad.net/bugs/98795 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 14762] Re: xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
Where should I report that the driver nv don't work for Geforce 6600 AGP? -- xorg won't start on nvida 6600 card due to nv driver not supporting 6600's https://launchpad.net/bugs/14762 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98795] Re: software-properties-gtk corrupted /etc/apt/source.list
** Description changed: Binary package hint: software-properties-gtk - After clean install of Ubuntu 7.04 Beta, update-manager ran and - downloaded some package from the net and prompted me to insert CD-ROM to - install updated. I didn't want to install packages from CD-ROM, I then - clicked "cancel" and wanted to remove CD-ROM from the source.list by - using "software sources" application to only specify internet as package - source. + After clean install of Ubuntu 7.04 Beta (i386 alternate), update-manager + ran and downloaded some package from the net and prompted me to insert + CD-ROM to install updated. I didn't want to install packages from CD- + ROM, I then clicked "cancel" and wanted to remove CD-ROM from the + source.list by using "software sources" application to only specify + internet as package source. I Couldn't find how to remove CD-ROM from the selection in software- properties-gtk and didn't want to edit /etc/apt/source.list manually. I then tried to click few options here and there in software-properties- gtk application. In "Third-Party Software tab", there was no entries and still there is no entry. Then I quit software-properties-gtk application to retry update-manager. update-manager wouldn't start and displayed the following error; "Could not initialize the package information A unresolvable problem occurred while initializing the package information. Please report this bug against the 'update-manager' package and include the following error message: 'E:Malformed line 4 in source list /etc/apt/sources.list (dist parse), E:The list of sources could not be read.' " After commenting out line 4 of /etc/apt/source.list the problem disappeared and update-manager ran fine. It seems like software- properties-gtk corrupted the source.list. Here are the first 8 lines of /etc/apt/source.list [actual lines start after the :] 1:# 2:# deb cdrom:[Ubuntu 7.04 _Feisty Fawn_ - Beta i386 (20070322.2)]/ feisty main restricted 3: 4:deb cdrom:[Ubuntu 7.04 _Feisty Fawn_ - Beta i386 (20070322.2)]/ feisty 5:# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to 6:# newer versions of the distribution. 7: 8:deb http://ca.archive.ubuntu.com/ubuntu/ feisty main restricted it seems the line 4 misses "main restricted" at the end of the line. Also it's strange that line 4 seems to be the same as lthe commented line 2 except for the missing "main restricted". This /etc/apt/source.list was never edited manually. -- software-properties-gtk corrupted /etc/apt/source.list https://launchpad.net/bugs/98795 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98795] software-properties-gtk corrupted /etc/apt/source.list
Public bug reported: Binary package hint: software-properties-gtk After clean install of Ubuntu 7.04 Beta, update-manager ran and downloaded some package from the net and prompted me to insert CD-ROM to install updated. I didn't want to install packages from CD-ROM, I then clicked "cancel" and wanted to remove CD-ROM from the source.list by using "software sources" application to only specify internet as package source. I Couldn't find how to remove CD-ROM from the selection in software- properties-gtk and didn't want to edit /etc/apt/source.list manually. I then tried to click few options here and there in software-properties- gtk application. In "Third-Party Software tab", there was no entries and still there is no entry. Then I quit software-properties-gtk application to retry update-manager. update-manager wouldn't start and displayed the following error; "Could not initialize the package information A unresolvable problem occurred while initializing the package information. Please report this bug against the 'update-manager' package and include the following error message: 'E:Malformed line 4 in source list /etc/apt/sources.list (dist parse), E:The list of sources could not be read.' " After commenting out line 4 of /etc/apt/source.list the problem disappeared and update-manager ran fine. It seems like software- properties-gtk corrupted the source.list. Here are the first 8 lines of /etc/apt/source.list [actual lines start after the :] 1:# 2:# deb cdrom:[Ubuntu 7.04 _Feisty Fawn_ - Beta i386 (20070322.2)]/ feisty main restricted 3: 4:deb cdrom:[Ubuntu 7.04 _Feisty Fawn_ - Beta i386 (20070322.2)]/ feisty 5:# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to 6:# newer versions of the distribution. 7: 8:deb http://ca.archive.ubuntu.com/ubuntu/ feisty main restricted it seems the line 4 misses "main restricted" at the end of the line. Also it's strange that line 4 seems to be the same as lthe commented line 2 except for the missing "main restricted". This /etc/apt/source.list was never edited manually. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: Unconfirmed -- software-properties-gtk corrupted /etc/apt/source.list https://launchpad.net/bugs/98795 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 14762] Re: xorg won't start on nvida 6600 card due to nv driver not supporting 6600's
During Ubuntu 7.04 Beta1 installation, Geforce 6600 been detected and assigned video driver "nv" in /etc/xorg.conf After reboot xorg start and video is garbled. Switching to console (CTRL-ALT-F1) and doing "telinit 1". You can change (sudo vi /etc/xorg.conf ) the video driver from "nv" to "vesa". Invoking "telinit 2" and thus restarting xorg will be fine. Processor used: Pentium 4 Videocard: BFG Geforce 6600 GT OC 128Meg (AGP video card) seems the "nv" driver is broken. Ubuntu should have assigned the "vesa" driver for that videocard. -- xorg won't start on nvida 6600 card due to nv driver not supporting 6600's https://launchpad.net/bugs/14762 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
