[Bug 91421] Re: machine doesn't hibernate
** Attachment added: xml for hardware db http://librarian.launchpad.net/6728760/hwdata.xml -- machine doesn't hibernate https://launchpad.net/bugs/91421 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91421] Re: machine doesn't hibernate
** Attachment added: lspci -vvnn http://librarian.launchpad.net/6728763/lspcivvnn.txt -- machine doesn't hibernate https://launchpad.net/bugs/91421 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91421] Re: machine doesn't hibernate
** Attachment added: dmesg http://librarian.launchpad.net/6728769/dmesg.txt -- machine doesn't hibernate https://launchpad.net/bugs/91421 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91421] Re: machine doesn't hibernate
Forgot to mention (though it's in the hardware info above): this is an old Sony Vaio PCG-XG19, with a neomagic graphics chipset. It has a ethernet card inserted. -- machine doesn't hibernate https://launchpad.net/bugs/91421 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 85979] Re: Wrong nice value while upgrading debconf
*** This bug is a duplicate of bug 68267 *** I too see this bug. There were about 390 packages to upgrade today, and they all downloaded. When it started up, it gave me the nice popup. Below is a version of what was displayed in the main window - that is, not the popup. (Actually it was from a later crash.) The first package to fail was bash. I went to a command line and did sudo apt-get update and it told me to do a sudo apt-get --configure -a which I dutifully did. Then I re-ran adept-updater and it got further, but when it reached x11-common it had similar problems. This I fixed again with the apt-get --configure -a , but adept-updater still wouldn't work. So this time I just finished the upgrade on the command line sudo apt-get upgrade and it went fine. Afterwards, there was no further packages shown by adept-updater. I had noticed that adept was one of the packages that had been reinstalled, and I used adept to install firefox. It worked, but I still saw the DESTROY created... message below. Extracting templates from packages: 100% DESTROY created new reference to dead object ' Qt::VBoxLayout', line 342 during global destruction. Preconfiguring packages ... Use of uninitialized value in join or string at /usr/share/perl5/Debconf/DbDrive r/Stack.pm line 104, GEN19 line 3. Use of uninitialized value in join or string at /usr/share/perl5/Debconf/DbDrive r/Stack.pm line 104, GEN39 line 4. Use of uninitialized value in join or string at /usr/share/perl5/Debconf/DbDrive r/Stack.pm line 104, GEN39 line 9. Use of uninitialized value in join or string at /usr/share/perl5/Debconf/DbDrive r/Stack.pm line 104, GEN39 line 17. Segmentation fault (core dumped) (Reading database ... 75336 files and directories currently installed.) Preparing to replace debianutils 2.17.4 (using .../debianutils_2.17.4build1_i386 .deb) ... Unpacking replacement debianutils ... Setting up debianutils (2.17.4build1) ... ... -- Wrong nice value while upgrading debconf https://launchpad.net/bugs/85979 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 67572] Re: Narrowing down time zone location is horridly slow when under vesa driver
I have an old Sony Vaio - PCG-XG19, with a neomagic graphics card. I was installing Kubuntu Herd 5 which I downloaded today. When I tried the install, I never even saw the map. Some of the previous page was still on the display, and there were the dots representing cities, and the tooltip rectangles would display when I'd mouse over cities, but never disappear. I don't think I gave it 30 seconds before I went on (the city displayed was correct anyway), though given how old this machine is it probably would have taken longer. -- Narrowing down time zone location is horridly slow when under vesa driver https://launchpad.net/bugs/67572 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 89092] Re: Unable to connect to an open network, wlassistant can connect
That is what is sort of strange about it. This is not a problem in general with networkmanager and open networks. Usually networkmanager works. But there was something about that particular network that it wouldn't connect to. I have a vague sense it had something to do with the network ssid (maybe having wlan in it or something) because the log file said something about trying to set the ssid to '' as the last thing it did before it gave up. I could see the network in both networkmanager (knetworkmanager, to be precise) and wlassistant, and get the strength of it in both. (The strength was good, at the time). I just couldn't connect to it with networkmanager. I know it's not a hardware/driver problem, because wlassistant can connect. (I don't use it normally, because it doesn't support WPA.) I have never tried wifi-radar, so I don't know what it is. - Mitch On Thu, 8 Mar 2007, Chris Wagner wrote: Hey Mitch, can you connect to any *open* access points (i.e., access points that do not use any encryption)? I have had a problem with network-manager since Dapper, I believe, which prevents me from connecting to open networks. network-manager *will* connect properly to WEP-encrypted networks; I haven't tried WPA. I can connect to any network (non-encrypted or WEP) by using wifi-radar or the command line. -- Unable to connect to an open network, wlassistant can connect https://launchpad.net/bugs/89092 -- Unable to connect to an open network, wlassistant can connect https://launchpad.net/bugs/89092 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89092] Unable to connect to an open network, wlassistant can connect
Public bug reported: Binary package hint: network-manager I am running edgy on a Dell Inspiron 6400. It has a broadcom 1340 (I think it is) and is running wifi under ndsiwrapper, the latest version. For the most part, networkmanager works fine. However, I am visiting a place where I was trying to join a network I don't normally use, and it was unable to join. What is odd is that wlassistant *is* able to make it work. The network is unencrypted, and its name is lbnl-wlan58 Here are the relevant lines from daemon.log when it failed Feb 27 14:50:11 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 Feb 27 14:50:11 localhost NetworkManager: debug info^I[1172605811.359616] nm_device_802_11_wireless_get_activation_ap (): Forcing AP 'lbnl-wlan58' Feb 27 14:50:11 localhost NetworkManager: information^IUser Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / lbnl-wlan58 Feb 27 14:50:11 localhost NetworkManager: information^IDeactivating device wlan0. Feb 27 14:50:11 localhost NetworkManager: WARNING^I nm_device_802_11_wireless_set_essid (): error setting ESSID to '' for device wlan0: Invalid argument Feb 27 14:50:13 localhost NetworkManager: information^IDevice wlan0 activation scheduled... Feb 27 14:50:13 localhost NetworkManager: information^IActivation (wlan0) started... Feb 27 14:50:13 localhost NetworkManager: information^IActivation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Feb 27 14:50:13 localhost NetworkManager: information^IActivation (wlan0) Stage 1 of 5 (Device Prepare) started... Feb 27 14:50:13 localhost NetworkManager: information^IActivation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Feb 27 14:50:13 localhost NetworkManager: information^IActivation (wlan0) Stage 1 of 5 (Device Prepare) complete. Feb 27 14:50:13 localhost NetworkManager: information^IActivation (wlan0) Stage 2 of 5 (Device Configure) starting... Feb 27 14:50:13 localhost NetworkManager: information^IActivation (wlan0/wireless): access point 'lbnl-wlan58' is unencrypted, no key needed. Feb 27 14:50:14 localhost NetworkManager: information^ISUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant^I' Feb 27 14:50:14 localhost NetworkManager: information^ISUP: response was 'OK' Feb 27 14:50:14 localhost NetworkManager: information^ISUP: sending command 'AP_SCAN 1' Feb 27 14:50:14 localhost NetworkManager: information^ISUP: response was 'OK' Feb 27 14:50:14 localhost NetworkManager: information^ISUP: sending command 'ADD_NETWORK' Feb 27 14:50:14 localhost NetworkManager: information^ISUP: response was '0' Feb 27 14:50:14 localhost NetworkManager: information^ISUP: sending command 'SET_NETWORK 0 ssid 6c626e6c2d776c616e3538' Feb 27 14:50:14 localhost NetworkManager: information^ISUP: response was 'OK' Feb 27 14:50:14 localhost NetworkManager: information^ISUP: sending command 'SET_NETWORK 0 key_mgmt NONE' Feb 27 14:50:14 localhost NetworkManager: information^ISUP: response was 'OK' Feb 27 14:50:14 localhost NetworkManager: information^ISUP: sending command 'ENABLE_NETWORK 0' Feb 27 14:50:14 localhost NetworkManager: information^ISUP: response was 'OK' Feb 27 14:50:14 localhost NetworkManager: information^IActivation (wlan0) Stage 2 of 5 (Device Configure) complete. Feb 27 14:50:19 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 Feb 27 14:50:24 localhost NetworkManager: information^Iwpa_supplicant(5332): Global control interface '/var/run/wpa_supplicant-global' Feb 27 14:50:24 localhost NetworkManager: information^Iwpa_supplicant(5332): RX global ctrl_iface - hexdump_ascii(len=50): Feb 27 14:50:24 localhost NetworkManager: information^Iwpa_supplicant(5332): 49 4e 54 45 52 46 41 43 45 5f 41 44 44 20 77 6c INTERFACE_ADD wl Feb 27 14:50:24 localhost NetworkManager: information^Iwpa_supplicant(5332): 61 6e 30 09 09 77 65 78 74 09 2f 76 61 72 2f 72 an0__wext_/var/r Feb 27 14:50:24 localhost NetworkManager: information^Iwpa_supplicant(5332): 75 6e 2f 77 70 61 5f 73 75 70 70 6c 69 63 61 6e un/wpa_supplican Feb 27 14:50:24 localhost NetworkManager: information^Iwpa_supplicant(5332): 74 09 t_ Feb 27 14:50:24 localhost NetworkManager: information^Iwpa_supplicant(5332): CTRL_IFACE GLOBAL INTERFACE_ADD 'wlan0^I^Iwext^I/var/run/wpa_supplicant^I' Feb 27 14:50:24 localhost NetworkManager: information^Iwpa_supplicant(5332): Initializing interface 'wlan0' conf 'N/A' driver 'wext' ctrl_interface '/var/run/wpa_supplicant' bridge 'N/A' Feb 27 14:50:24 localhost NetworkManager: information^Iwpa_supplicant(5332): Initializing interface (2) 'wlan0' Feb 27 14:50:24 localhost NetworkManager: information^Iwpa_supplicant(5332): EAPOL: SUPP_PAE entering state DISCONNECTED Feb 27 14:50:24 localhost NetworkManager: information^Iwpa_supplicant(5332): EAPOL: KEY_RX entering state NO_KEY_RECEIVE Feb 27 14:50:24 localhost NetworkManager:
[Bug 67443] Re: Progress bar is invisible
One further thought: I wonder if this has anything to do with this problem I am seeing here: https://launchpad.net/distros/ubuntu/+source/usplash/+bug/67438 -- Progress bar is invisible https://launchpad.net/bugs/67443 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67442] Re: Edgy RC CD won't shut down
This appears to have been fixed in Edgy release. -- Edgy RC CD won't shut down https://launchpad.net/bugs/67442 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67443] Re: Progress bar is invisible
This problem persists in the Edgy release -- Progress bar is invisible https://launchpad.net/bugs/67443 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64076] Re: Can't install from Edgy CD
The install from Edgy release had no problems. -- Can't install from Edgy CD https://launchpad.net/bugs/64076 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67438] Re: Startup and shutdown screens look corrupted
In the Edgy release, this looks quite a bit better. On the shutdown screen the remove CD press ENTER to continue text was dark blue on black, but was visible. The Ubuntu logo didn't look great, but was okay. -- Startup and shutdown screens look corrupted https://launchpad.net/bugs/67438 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67443] Re: Progress bar is invisible
I should point out that this is the setup I have when I boot directly from the Edgy RC CD, so it isn't possible that I changed anything. When I run that command it replies with Human. Should I see something in the .xsession-errors before I run an install? The only suspicious thing I see before an install is (gnome-panel: 6049) Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24. -- Progress bar is invisible https://launchpad.net/bugs/67443 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67443] Re: Progress bar is invisible
Here is the xorg.conf ** Attachment added: xorg.conf http://librarian.launchpad.net/4930660/xorg.conf -- Progress bar is invisible https://launchpad.net/bugs/67443 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67443] Re: Progress bar is invisible
Sorry, forgot to answer. Yes, this is the Desktop Edgy RC CD. -- Progress bar is invisible https://launchpad.net/bugs/67443 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64076] Re: Can't install from Edgy CD
I tried this with the RC disk, and it appears that there was no longer a problem with the Gnome Settings Manager. -- Can't install from Edgy CD https://launchpad.net/bugs/64076 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67438] Startup and shutdown screens look corrupted
Public bug reported: I have installed Edgy RC on my old Sony Vaio PCG-XG19. During startup and shutdown, the screen shows the logos etc, but the colors are all wrong and it looks all pixellated. The message window is black and impossible to read. I have noticed that the same thing happens whether the boot screen is the ubuntu or kubuntu one. I installed fbset and ran fbset -i, to which it replies /dev/fb0 no such device. xorg.conf reports that the graphics chipset is NeoMagic Corporation NM2380 [MagicMedia 256XL+] I don't know how to grab a screenshot during bootup. If there is a need to see the actual screen, I will take an external digital camera and take a photo. I saw a possibly similar bugs reported here: https://launchpad.net/distros/ubuntu/+source/usplash/+bug/43223 and here: https://launchpad.net/distros/ubuntu/+source/usplash/+bug/21478 The screen corruption looks vaguely similar, but the colors are different, so it may be a different thing going on. ** Affects: usplash (Ubuntu) Importance: Undecided Status: Unconfirmed -- Startup and shutdown screens look corrupted https://launchpad.net/bugs/67438 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67442] Edgy RC CD won't shut down
Public bug reported: When I boot my old Sony Vaio PCG-XG19 from the Edgy RC CD, it works fine and I can install. However, what I cannot do is shutdown or reboot. Whenever I try to shut down the machine having booted it from the CD (whether I did an install or not), I see the machine shutting down, and then it pops open the CD drawer, says remove the CD, close the door, and hit ENTER. When I do this nothing happens. If I hit CTRL-ALT-DEL I see the bar crawl across again as though it were re-shutting down, but it gets to the same point and does the same thing I have to remove the power from the machine to get it to shut down. ** Affects: Ubuntu Importance: Undecided Status: Confirmed -- Edgy RC CD won't shut down https://launchpad.net/bugs/67442 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67438] Re: Startup and shutdown screens look corrupted
I tried one other thing. If you start from the CD, you can hit F4 and adjust the video graphics mode. The default for my machine is VGA, which is what looks corrupted as above. When I switch it to 1024x768x24 everything looks fine. The situation in VGA mode is pretty bad, because I can't read any of the messages that appear in the box, for example during a CD test. -- Startup and shutdown screens look corrupted https://launchpad.net/bugs/67438 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64114] Re: Edgy Beta 1 breaks X on Neomagic chipset
This problem appears to be fixed in Edgy RC 1 -- Edgy Beta 1 breaks X on Neomagic chipset https://launchpad.net/bugs/64114 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67443] Progress bar is invisible
Public bug reported: In the default Gnome theme that I get during an Ubuntu install, the progress bar is not visible. It appears to be white on white. You can see the number of percent and it is changing, but once you get above 50% it becomes very hard to read. The progress bar has the same appearance after the install, and the attached screenshot shows synaptic upgrading my system. I have a Sony Vaoi PCG-XG19 laptop with a NeoMagic chipset. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Progress bar is invisible https://launchpad.net/bugs/67443 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67443] Re: Progress bar is invisible
** Attachment added: This image shows the progress bar about 1/2 way through. Notice you can't see any shading. http://librarian.launchpad.net/4921270/Screenshot.png -- Progress bar is invisible https://launchpad.net/bugs/67443 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67438] Re: Startup and shutdown screens look corrupted
How do I change the video graphics modes other than F4 during a CD boot? -- Startup and shutdown screens look corrupted https://launchpad.net/bugs/67438 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 63694] Re: Upgrading from dapper to edgy fails if KDE 3.5.4 is present
I am retrying this now and will do it with apt-get as requested. Further research has indicated that it appears that I had not installed easyubuntu yet before I did the upgrade. If I am unable to reproduce I will try it with easyubuntu. One point is that I am not suggesting support for anything other than the install process. If it has a possibility of trashing the machine just because I've installed some packages (slightly) outside of the recommended norm I would argue that is a real problem! It should at the very least look for the problematic situation in advance and not run. - Mitch On Wed, 4 Oct 2006, Sarah Hobbs wrote: Seveas: I expect that the kubuntu people do want to support and give clean upgrades for kde 3.5.4 on kubuntu.org -- edgy. After all, we do the sources for them too. -- Upgrading from dapper to edgy fails if KDE 3.5.4 is present https://launchpad.net/bugs/63694 -- Upgrading from dapper to edgy fails if KDE 3.5.4 is present https://launchpad.net/bugs/63694 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63694] Re: Upgrading from dapper to edgy fails if KDE 3.5.4 is present
OK, I have tried this again and have been able to pinpoint a bit better what happened. First of all, I installed from the Dapper CD. Then, I added KDE3.5.4 as described in the link above. (I needed to edit xorg.conf as well, but that's a separate bug.) I rebooted, and then used adept to get the 36 security packages that remained. I rebooted again for good measure. I did *not* install easyubuntu. First, I tried to do it with apt-get, and it wouldn't do the upgrade, as you can see from the attachment below. I then did the upgrade with Adept. As before, it went to about 62% or so, and then it said it had a dependency problem. The package it said it was installing was libqt3-mt. There was a modal popup window, with just the OK button. Because this time I had the show terminal window open, I could see what was going on. What's particularly interesting is that after the popup and the install bar stopped, the terminal windo showed that it continued installing. After a while it seemed to have stopped, and it said that there were dependency problems with the following packages: libqt3-mt libartslc2a libavahi-at3-1 kdelibs4c2a openoffice.org-kde koffice-libs krita I was unable to scroll or copy-paste what was in the terminal buffer without dismissing the modal error window, but when I did this Adept closed. I will reboot this machine shortly, and I will see it if it's fubar. I can already tell that something is wrong, because I cannot reopen Adept. - [EMAIL PROTECTED]:~$ sudo apt-get update sudo apt-get dist-upgrade Ign http://kubuntu.org edgy Release.gpg Get:1 http://security.ubuntu.com edgy-security Release.gpg [189B] Get:2 http://archive.ubuntu.com edgy Release.gpg [189B] Get:3 http://us.archive.ubuntu.com edgy Release.gpg [189B] Get:4 http://us.archive.ubuntu.com edgy-updates Release.gpg [189B] Get:5 http://security.ubuntu.com edgy-security Release [19.6kB] Ign http://kubuntu.org edgy Release Get:6 http://archive.ubuntu.com edgy Release [34.7kB] Ign http://kubuntu.org edgy/main Packages Err http://kubuntu.org edgy/main Packages 404 Not Found Get:7 http://security.ubuntu.com edgy-security/main Packages [14B] Get:8 http://us.archive.ubuntu.com edgy Release [34.7kB] Get:9 http://archive.ubuntu.com edgy/universe Packages [2678kB] Get:10 http://security.ubuntu.com edgy-security/restricted Packages [14B] Get:11 http://security.ubuntu.com edgy-security/main Sources [14B] Get:12 http://security.ubuntu.com edgy-security/restricted Sources [14B] Get:13 http://us.archive.ubuntu.com edgy-updates Release [19.6kB] Get:14 http://us.archive.ubuntu.com edgy/main Sources [273kB] Get:15 http://us.archive.ubuntu.com edgy/restricted Sources [1427B] Get:16 http://archive.ubuntu.com edgy/main Packages [660kB] Get:17 http://us.archive.ubuntu.com edgy-updates/main Packages [14B] Get:18 http://us.archive.ubuntu.com edgy-updates/restricted Packages [14B] Get:19 http://us.archive.ubuntu.com edgy-updates/main Sources [14B] Get:20 http://us.archive.ubuntu.com edgy-updates/restricted Sources [14B] Get:21 http://archive.ubuntu.com edgy/restricted Packages [4617B] Fetched 3726kB in 16s (228kB/s) Failed to fetch http://kubuntu.org/packages/kde-354/dists/edgy/main/binary-i386/Packages.gz 404 Not Found Reading package lists... Done E: Some index files failed to download, they have been ignored, or old ones used instead. [EMAIL PROTECTED]:~$ sudo apt-get update sudo apt-get dist-upgrade Get:1 http://security.ubuntu.com edgy-security Release.gpg [189B] Ign http://kubuntu.org edgy Release.gpg Get:2 http://us.archive.ubuntu.com edgy Release.gpg [189B] Get:3 http://us.archive.ubuntu.com edgy-updates Release.gpg [189B] Get:4 http://archive.ubuntu.com edgy Release.gpg [189B] Hit http://security.ubuntu.com edgy-security Release Hit http://us.archive.ubuntu.com edgy Release Hit http://archive.ubuntu.com edgy Release Ign http://kubuntu.org edgy Release Ign http://kubuntu.org edgy/main Packages Hit http://us.archive.ubuntu.com edgy-updates Release Hit http://security.ubuntu.com edgy-security/main Packages Err http://kubuntu.org edgy/main Packages 404 Not Found Hit http://archive.ubuntu.com edgy/universe Packages Hit http://security.ubuntu.com edgy-security/restricted Packages Hit http://security.ubuntu.com edgy-security/main Sources Hit http://security.ubuntu.com edgy-security/restricted Sources Hit http://us.archive.ubuntu.com edgy/main Sources Hit http://us.archive.ubuntu.com edgy/restricted Sources Hit http://archive.ubuntu.com edgy/main Packages Hit http://archive.ubuntu.com edgy/restricted Packages Hit http://us.archive.ubuntu.com edgy-updates/main Packages Hit http://us.archive.ubuntu.com edgy-updates/restricted Packages Hit http://us.archive.ubuntu.com edgy-updates/main Sources Hit http://us.archive.ubuntu.com edgy-updates/restricted Sources Fetched 4B in 1s (4B/s) Failed to fetch http://kubuntu.org/packages/kde-354/dists/edgy/main/binary-i386/Packages.gz 404 Not Found
Re: [Bug 63694] Re: Upgrading from dapper to edgy fails if KDE 3.5.4 is present
Yep, the machine is toast. When I shut down, I see what I guess is a test screen (with cirles and boxes, colors look wrong). When it tries to reboot, I get nothing. I can't switch to the text consoles using Ctl-Alt-F1 etc. -- Upgrading from dapper to edgy fails if KDE 3.5.4 is present https://launchpad.net/bugs/63694 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64076] Can't install from Edgy CD
Public bug reported: I have tried various ways to install Edgy Beta 1 on my old Sony Vaio PCG-XG19 from the CD. When boot the CD in normal mode, I get an error saying that it can't start the gnome-settings-daemon. This may or may not be related to the issues people are having here: https://launchpad.net/distros/ubuntu/+source/ubiquity/+bug/62895 I suspect it is a bit diffferent, because I get the bugs while booting from the CD, while they are booting from the hard disk. If I just ignore the error and try clicking on the install icon on the desktop, I see a Granting Rights message appear in the taskbar, but then nothing opens. If I click again, it starts the installer, and I can enter everything and the install starts. Then it hangs at 58% while saying it's copying files. If I try to manually start the gnome-settings-daemon in a terminal window, I see something happen (the terminal window bar changes color), but then the machine hangs. If I try to see the messages it gets just a few lines in, and doesn't say anything that seems informative. Following the instructions in another bug, I tried this command from a terminal: sudo env UBIQUITY_DEBUG=1 ubiquity 2/tmp/ubiquity.log But now it hung during the first screen of the installer. I then tried to install from safe graphics mode. Starting the machine from the CD in safe graphics mode I *don't* see the error dialog about the gnome-settings-daemon. When I start a terminal, I can do a ps auxww and see it running. If I double click the install icon, once again I see Granting Rights and then nothing. If I do it again I can start the installer, but I did see something odd. During the startup of the partition manager, it stopped displaying the progress bar. It didn't stop the progress however, and I was able to get throug h all the way through the installer screens and start the install. There was no color to the progress bar all the way through, but the number was increasing. Then it got to 58% again and hung up - same as before. This installer bug might be a duplicate of this one here: https://launchpad.net/distros/ubuntu/+source/bonobo/+bug/56890 but I am not sure, so I am reporting it again. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Can't install from Edgy CD https://launchpad.net/bugs/64076 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64114] Edgy Beta 1 breaks X on Neomagic chipset
Public bug reported: I have a Sony Vaio PCG-XG19. This is rather old machine with a neomagic chipset. I have no problem running Dapper on it. I did the following: *) Start from a virgin machine. *) Install Dapper, don't run any upgrades. *) Edit the /etc/apt/sources.list, change all dapper - edgy *) Using Synaptic, select all upgradable, then apply. *) Wait 2 hours while it does its thing. *) Reboot. The machine starts up. During the boot, the screen colors look wrong - perhaps it is in 16 color mode. X fails to start up. On screen 1 I see a box that asks me if I want to see the X log file, but it times out almost instantly and just gives a login prompt. I have attached xorg.conf and Xorg.log.0 below. I don't see anything wrong with either one. /etc/X11/xorg.conf --- # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. # (Type man /etc/X11/xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section Files FontPath/usr/share/X11/fonts/misc FontPath/usr/share/X11/fonts/cyrillic FontPath/usr/share/X11/fonts/100dpi/:unscaled FontPath/usr/share/X11/fonts/75dpi/:unscaled FontPath/usr/share/X11/fonts/Type1 FontPath/usr/share/X11/fonts/100dpi FontPath/usr/share/X11/fonts/75dpi # path to defoma fonts FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType EndSection Section Module Loadi2c Loadbitmap Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc104 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/input/mice Option Protocol ExplorerPS/2 Option ZAxisMapping 4 5 Option Emulate3Buttons true EndSection Section InputDevice Driverwacom Identifierstylus OptionDevice/dev/wacom # Change to # /dev/input/event # for USB OptionType stylus OptionForceDevice ISDV4 # Tablet PC ONLY EndSection Section InputDevice Driverwacom Identifiereraser OptionDevice/dev/wacom # Change to # /dev/input/event # for USB OptionType eraser OptionForceDevice ISDV4 # Tablet PC ONLY EndSection Section InputDevice Driverwacom Identifiercursor OptionDevice/dev/wacom # Change to # /dev/input/event # for USB OptionType cursor OptionForceDevice ISDV4 # Tablet PC ONLY EndSection Section Device Identifier NeoMagic Corporation NM2380 [MagicMedia 256XL+] Driver neomagic BusID PCI:1:0:0 EndSection Section Monitor Identifier Generic Monitor Option DPMS HorizSync 28-51 VertRefresh 43-60 EndSection Section Screen Identifier Default Screen Device NeoMagic Corporation NM2380 [MagicMedia 256XL+] Monitor Generic Monitor DefaultDepth24 SubSection Display Depth 1 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1024x768 800x600 640x480 EndSubSection SubSection Display
[Bug 63694] Upgrading from dapper to edgy fails if KDE 3.5.4 is present
Public bug reported: I had pretty much a virgin machine that I had built as follows: *) Build a machine from the Ubuntu Dapper CD (*not* Kubuntu). *) Log in and install all updates *) Install easy-ubuntu *) Install the latest version of KDE as described here: http://kubuntu.org/announcements/kde-354.php *) OK, now try to upgrade it using Adept. I edited all the dappers in the repository list to edgys and did a full upgrade, and Apply. *) Ran for quite a long time. After about 60% of the way through, it stopped, claiming that that continuing would break a package or cause some other problem (I don't remember the precise message, unfortunately). I see from the dpkg.log file it was finished with the localization files for openoffice. I don't know if there are any other log files that could tell me more exactly what the problem was. *) The machine was fairly fubar. Adept refused to open again, claiming that there was some configuration problem. It requested using apt-setup and apt-get --update to see if that fixed things, but the former doesn't exist and the latter didn't help. *) The machine refuses to reboot properly. If I don't use safe mode it just hangs, and if I do use safe mode it refuses to talk to the network. The machine is an old Sony Vaio PCG-XG19, if that helps. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Upgrading from dapper to edgy fails if KDE 3.5.4 is present https://launchpad.net/bugs/63694 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63694] Re: Upgrading from dapper to edgy fails if KDE 3.5.4 is present
I will try this again. I am not 100% sure I had easyubuntu on the machine (95% sure). However, I would recommend not rejecting this bug because aside from the easyubuntu part, what I did was in every case precisely what was recommended on the ubuntu/kubuntu sites. The package manager was unable to determine in advance that the upgrade would fail, and left the machine in a pretty fubar state. This would be very bad if it happens to people with real data on their machines. (Not to mention that most people will be upgrading machines with easyubuntu on them.) Is there some way to determine from what's on the machine itself now where it was in the upgrade process so we can at least possibly track down where in the upgrade process it was when it decided to quit? -- Upgrading from dapper to edgy fails if KDE 3.5.4 is present https://launchpad.net/bugs/63694 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60767] Amarok 1.4.3 requires libifp4
Public bug reported: Binary package hint: amarok The instructions for installing Amarok 1.4.3 don't mention that you need libifp4, which is in the universe repository. Following the instructions just says you have an uninstallable package. Probably this needs to be fixed just by changing the documentation. ** Affects: amarok (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Amarok 1.4.3 requires libifp4 https://launchpad.net/bugs/60767 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
