[Bug 749663] [NEW] Both jackd1 and jackd2 throw xruns constantly
Public bug reported: I start jack via qjackctl taking all defaults. It throws xruns constantly, at about the rate of 10 per second. I tried disabling my wifi, which caused IRQ conflicts with firewire on my 8.04 system, but it didn't help. I tried installing jackd1, since my hardware is single- core, but that also exhibits the same problem. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: jackd 5 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 Architecture: amd64 Date: Sun Apr 3 15:44:14 2011 Dependencies: InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110402) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: jackd-defaults UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: jackd-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/749663 Title: Both jackd1 and jackd2 throw xruns constantly -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 432794] Re: gnome-panel freeze/infinite loop/memory leak
I'm also experiencing this problem, for about the last month. It didn't occur immediately after dist-upgrade from 10.04 to 10.10, but after a subsequent update, and update-manager requested a restart. for me, gnome-panel locks up immediately upon login, before even drawing itself to the desktop. I login, I get the startup tune, then nothing, just a blank desktop. I can ctrl-alt-f2 to a console, where top shows gnome-panel locking up one of my four cores, and memory being eaten. It starts at approx 350M, but within a few days, it's up to 3GB. I don't know if this is a gnome-panel function or not, but I can't alt-f2 to launch an application, but if I right-click on the desktop, I get a menu which includes the option to 'create launcher', so I've used that to launch a terminal and the chromium browser, which has allowed me the minimal functionality to submit this report. I followed a suggestion from an earlier comment, and renamed the following directories in my home directory: .gconf. .gconfd, .gnome2, and .gnome2_private. When I logged out and logged in again, they were recreated, but the lockup and missing panel continues. System is an Athlon II X4 635 with 4GB memory, and ATI RS880 [Radeon HD 4200] graphics. Dual monitor, but only one default panel. Kernel is currently 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 02:41:37 UTC 2010 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/432794 Title: gnome-panel freeze/infinite loop/memory leak -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 103719] Re: Won't return from suspend on emachines M6810
On Fri, 20 Mar 2009, Adam Plumb wrote: > Maybe someone else with an M6810 (would be rare, the laptop is almost 5 > years old) can confirm. Otherwise, I would call this one fixed for > jaunty. > I have an M6810 running Ubuntustudio 8.04. The -rt kernel was reportedly broken in 8.10, so I was advised not to upgrade. I'm still waiting to hear of others' positive experience with the -rt kernel in 9.04 before I'm willing to risk an upgrade. -- Won't return from suspend on emachines M6810 https://bugs.launchpad.net/bugs/103719 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 293873] Re: fails to fetch online maps.
Found the problem. Ubuntu (and I'm told other Debian derivatives) installs libgeotiff in a non-standard location, so when compiling under ubuntu, an override is necessary at the './configure' step: ./configure CPPFLAGS="-I/usr/include/geotiff" Reference: http://www.xastir.org/wiki/index.php/HowTo:Ubuntu_8.10 Secondly, since the 'make install' installs the binaries in a different location than the ubuntu package, it was necessary to `rm -R ~/.xastir/` and let xastir rebuild it on its first invocation. -- fails to fetch online maps. https://bugs.launchpad.net/bugs/293873 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 293873] Re: fails to fetch online maps.
Well, recompiling from source didn't work for me: sudo apt-get build-dep xastir sudo apt-get source xastir sudo chown -R rtg.rtg xastir-1.9.2/ cd xastir-1.9.2 ./configure make ends with: map_tif.c:1312: error: ‘TIFFTAG_PHOTOMETRIC’ undeclared (first use in this function) map_tif.c:1312: error: ‘photometric’ undeclared (first use in this function) map_tif.c:1313: error: ‘PHOTOMETRIC_RGB’ undeclared (first use in this function) map_tif.c:1316: error: ‘TIFFTAG_ROWSPERSTRIP’ undeclared (first use in this function) map_tif.c:1316: error: ‘rowsPerStrip’ undeclared (first use in this function) map_tif.c:1321: error: ‘TIFFTAG_BITSPERSAMPLE’ undeclared (first use in this function) map_tif.c:1321: error: ‘bitsPerSample’ undeclared (first use in this function) map_tif.c:1326: error: ‘TIFFTAG_SAMPLESPERPIXEL’ undeclared (first use in this function) map_tif.c:1326: error: ‘samplesPerPixel’ undeclared (first use in this function) map_tif.c:1331: error: ‘TIFFTAG_PLANARCONFIG’ undeclared (first use in this function) map_tif.c:1331: error: ‘planarConfig’ undeclared (first use in this function) map_tif.c:1384: error: ‘PHOTOMETRIC_PALETTE’ undeclared (first use in this function) map_tif.c:1385: error: ‘TIFFTAG_COLORMAP’ undeclared (first use in this function) map_tif.c:1387: warning: implicit declaration of function ‘TIFFError’ map_tif.c:1387: warning: implicit declaration of function ‘TIFFFileName’ map_tif.c:1482: warning: implicit declaration of function ‘my_GTIFProj4FromLatLong’ map_tif.c:1488: warning: implicit declaration of function ‘GTIFPCSToImage’ map_tif.c:1919: error: ‘PHOTOMETRIC_MINISBLACK’ undeclared (first use in this function) map_tif.c:1936: error: ‘PHOTOMETRIC_MINISWHITE’ undeclared (first use in this function) map_tif.c:1979: warning: implicit declaration of function ‘TIFFScanlineSize’ map_tif.c:2400: error: ‘TIFFTAG_GEOPIXELSCALE’ undeclared (first use in this function) map_tif.c:2400: error: ‘qty’ undeclared (first use in this function) map_tif.c:2541: error: ‘row’ undeclared (first use in this function) map_tif.c:2591: error: ‘current_right’ undeclared (first use in this function) map_tif.c:2604: error: ‘current_line_width’ undeclared (first use in this function) map_tif.c:2655: warning: implicit declaration of function ‘TIFFReadScanline’ make[3]: *** [map_tif.o] Error 1 make[3]: Leaving directory `/home/rtg/xastir-1.9.2/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/rtg/xastir-1.9.2/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/rtg/xastir-1.9.2' make: *** [all] Error 2 -- fails to fetch online maps. https://bugs.launchpad.net/bugs/293873 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 293873] Re: fails to fetch online maps.
Confirmed. New install of Kubuntu 8.10. Updated to current on all packages. `sudo apt-get install xastir` then `xastir &` launched the program. After configuring my station location, I enabled tigermap.geo, and immediately got the error mentioned above in the konsole window from which I launched xastir. Libcurl was not pulled in as a dependency by apt as I installed xastir, I don't know if it was part of the base distro. Wget is present, as `which wget` from the same konsole which launched xastir returns '/usr/bin/wget' I have not yet tried recompiling from source. -- fails to fetch online maps. https://bugs.launchpad.net/bugs/293873 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 223206] Re: Can't upgrade Kubuntu Feisty to Gutsy
Oh my goodness this is old. I have no recollection how I got around it. I probably just trashed the installation and loaded clean. Might as well close this as 'too old, irrelevant now' -- Can't upgrade Kubuntu Feisty to Gutsy https://bugs.launchpad.net/bugs/223206 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to adept in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 223226] Re: Upgrade from kubuntu Dapper requires manual intervention and kdm shutdown
On Mon, 6 Oct 2008, kko wrote: > "So why does it take six months to get a one-line change made to a single > web page???" > > Hmm well, there's a limited number of eyes looking at bugs and of people > fixing things, so patience is a virtue. You did mention you're impatient > though. :-) Yes, I posess the best of qualities: Impatience when I want to get something done, and Procrastination when I have to do something myself. > > Then again, it seems the fact that 'kdm' did require manual stopping > wasn't actually expected. Perhaps there are other remedies for the issue > that may allow dist-upgrades directly from X in the future also for > Kubuntu? (Not a huge priority for me, but may be more important from the > developers' / other users' point of view.) > Somehow, the gnome folks have accomplished a dist-upgrade from within the gui, but from my old knowledge of X, the server dies when its initial process terminates, so any attempt to restart kdm, which I believe is X's 'initial process', will cause X to die and all the subordinate applications to spill their guts on the floor. So if it is indeed possible to upgrade kdm or even X itself while it is running, it sems to me somewhat akin to changing the engine while speeding down the freeway. That's clearly above my pay grade. So the one-line warning on the web page would be considered a 'circumvention' rather than a 'resolution', but I still think it would save a few people some grief if that were added to the published procedure. -- Upgrade from kubuntu Dapper requires manual intervention and kdm shutdown https://bugs.launchpad.net/bugs/223226 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 223226] Re: Upgrade from kubuntu Dapper requires manual intervention and kdm shutdown
Thank you kko for confirming this bug and parsing the evidence out of the log file for easy readibility. I gave a suggested resolution in one of my first posts: A one-line warning in the web page, instructing the user to use the server update process from a console TTY, not from an terminal window within KDE. It was a DUH! when I encountered it, and realized (too late) that the server edition doesn't have a gui, so it would make sense to run the server upgrade process from a tty, but I'm impatient, and I'm reading instructions on a web page in a graphical browser, so I just open a terminal window and start typing as I'm told. It would save someone else the dope-slap if the web page had that one-line reminder. So why does it take six months to get a one-line change made to a single web page??? -- Upgrade from kubuntu Dapper requires manual intervention and kdm shutdown https://bugs.launchpad.net/bugs/223226 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 12637] Re: LCD Brightness on Laptop Always Set Very Low at Boot
I'm happy to report that after upgrading my ubuntustudio install on an emachines M6810 to hardy (amd64), I got a full-brilliance display on the first boot! -- LCD Brightness on Laptop Always Set Very Low at Boot https://bugs.launchpad.net/bugs/12637 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
Re: [Bug 219685] Re: package update-manager 1:0.81.2 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Couldn't configure pre-depend audacious-plugins for audacious-plugins-ext
*** This bug is a duplicate of bug 221382 *** https://bugs.launchpad.net/bugs/221382 I did `apt-get remove audacious-plugins`, which also forced the removal of audacious and ubuntustudio-audio. I then ran `do-release-upgrade`, which completed the upgrade process. I then did `apt-get install ubuntustudio-audio`, which pulled in audacious and about a dozen other packages. So now I have a functioning hardy system, I think. My broadcom wifi stopped working, so I re-ran the fwcutter script, or actually, the restricted-drivers widget prompted me and ran it for me. However, on first boot, a message popped up about 'can't load human theme', and now I have a plain black wallpaper, which I don't mind since I'm an old text terminal kinda guy, anyway. -- package update-manager 1:0.81.2 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Couldn't configure pre-depend audacious-plugins for audacious-plugins-extra, probably a dependency cycle. https://bugs.launchpad.net/bugs/219685 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 188705] Re: The update manager can't update Ubuntu 7.10 to 8.04
*** This bug is a duplicate of bug 221382 *** https://bugs.launchpad.net/bugs/221382 That's not the point. Of course a reinstall works. But an upgrade is supposed to work as well... -- The update manager can't update Ubuntu 7.10 to 8.04 https://bugs.launchpad.net/bugs/188705 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223226] Re: Upgrade from kubuntu Dapper requires manual intervention and kdm shutdown
** Description changed: I just upgraded from Dapper to Hardy (Kubuntu) using the command-line process described on the web site. Several issues actually: - part-way into the upgrade, it tells me that kdm has to be manually shut down before it can proceed. Grrr! I'm running this in a root konsole window. That message should be in the procedure listed on the web, such as "Log out of KDE, and log into a root console session first". The good news is that after I accepted the option to abort, and I got myself to a text console, re-issuing the same update-manager -d command got it quickly going where it left off. + part-way into the upgrade, it tells me that kdm has to be manually shut down before it can proceed. Grrr! I'm running this in a root konsole window. That message should be in the procedure listed on the web, such as "Log out of KDE, and log into a root console session first". The good news is that after I accepted the option to abort, and I got myself to a text console, re-issuing the same do dist-upgrade -d command got it quickly going where it left off. As it's proceeding, it tells me several times that I'll need to do something manually later. The first time, I think I can remember it, but soon the list of manual interventions gets too long for my memory, and I'm too lazy to transcribe all this stuff off the screen, so I believe there should be somewhere a log of all these upgrade messages stashed somewhere for later review, and the end of the upgrade process should present an option to print the list of manual interventions needed right after the reboot. -- Upgrade from kubuntu Dapper requires manual intervention and kdm shutdown https://bugs.launchpad.net/bugs/223226 You received this bug notification because you are a member of Kubuntu Team, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 223226] Re: Upgrade from kubuntu Dapper requires manual intervention and kdm shutdown
** Attachment added: "apt.log" http://launchpadlibrarian.net/13983377/apt.log ** Attachment added: "apt-term.log" http://launchpadlibrarian.net/13983378/apt-term.log ** Attachment added: "main.log" http://launchpadlibrarian.net/13983379/main.log ** Attachment added: "main_pre_req.log" http://launchpadlibrarian.net/13983380/main_pre_req.log -- Upgrade from kubuntu Dapper requires manual intervention and kdm shutdown https://bugs.launchpad.net/bugs/223226 You received this bug notification because you are a member of Kubuntu Team, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 223226] Re: Upgrade from Dapper requires manual intervention
Here are the logs. The evidence is in apt-term.log, although it isn't easy to see. It's surrounded by curses escape sequences... -- Upgrade from kubuntu Dapper requires manual intervention and kdm shutdown https://bugs.launchpad.net/bugs/223226 You received this bug notification because you are a member of Kubuntu Team, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 223226] Re: Upgrade from Dapper requires manual intervention
Well, the first one was about manually configuring nut. There was something about manually converting postgresql databases. There were lots of errors from some perl module telling me that it couldn't set locale because of some missing file, and listed three environment variables it was trying to set, and said it was defaulting to LANG=C. I wish you could tell me that all those messages were archived in a file somewhere... How did your party go the other night? Sorry I didn't make it, but I chose to go to the Dance for the Earth in A2 instead. -- Upgrade from Dapper requires manual intervention https://bugs.launchpad.net/bugs/223226 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223226] Re: Upgrade from Dapper requires manual intervention
Issue #1, here's the web page I followed: http://www.ubuntu.com/getubuntu/upgrading#head-db224ea9add28760e373240f8239afb9b817f197 Towards the bottom of that page, is the following: Network upgrade for Kubuntu desktops (recommended) To upgrade from Kubuntu 6.06 to 8.04 over the Internet, use the same procedure as for Ubuntu server, below. Network upgrade for Ubuntu servers (recommended) If you run an Ubuntu server, you should use the new server upgrade system. 1.. I believe this should read: To upgrade from Kubuntu 6.06 to 8.04 over the Internet, 1. Log out of KDE, and log in as root to a console TTY session. 2. Use the same procedure as for Ubuntu server, below. -- Upgrade from Dapper requires manual intervention https://bugs.launchpad.net/bugs/223226 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223226] [NEW] Upgrade from Dapper requires manual intervention
Public bug reported: I just upgraded from Dapper to Hardy (Kubuntu) using the command-line process described on the web site. Several issues actually: part-way into the upgrade, it tells me that kdm has to be manually shut down before it can proceed. Grrr! I'm running this in a root konsole window. That message should be in the procedure listed on the web, such as "Log out of KDE, and log into a root console session first". The good news is that after I accepted the option to abort, and I got myself to a text console, re-issuing the same update-manager -d command got it quickly going where it left off. As it's proceeding, it tells me several times that I'll need to do something manually later. The first time, I think I can remember it, but soon the list of manual interventions gets too long for my memory, and I'm too lazy to transcribe all this stuff off the screen, so I believe there should be somewhere a log of all these upgrade messages stashed somewhere for later review, and the end of the upgrade process should present an option to print the list of manual interventions needed right after the reboot. ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: I just upgraded from Dapper to Hardy (Kubuntu) using the command-line process described on the web site. Several issues actually: - part-way into the upgrade, it tells me that kdm has to be manually shut down before it can proceed. Grrr! I'm running this in a root console window. That message should be in the procedure listed on the web, such as "Log out of KDE, and log into a root console session first". The good news is that after I accepted the option to abort, and I got myself to a text console, re-issuing the same update-manager -d command got it quickly going where it left off. + part-way into the upgrade, it tells me that kdm has to be manually shut down before it can proceed. Grrr! I'm running this in a root konsole window. That message should be in the procedure listed on the web, such as "Log out of KDE, and log into a root console session first". The good news is that after I accepted the option to abort, and I got myself to a text console, re-issuing the same update-manager -d command got it quickly going where it left off. As it's proceeding, it tells me several times that I'll need to do something manually later. The first time, I think I can remember it, but soon the list of manual interventions gets too long for my memory, and I'm too lazy to transcribe all this stuff off the screen, so I believe there should be somewhere a log of all these upgrade messages stashed somewhere for later review, and the end of the upgrade process should present an option to print the list of manual interventions needed right after the reboot. -- Upgrade from Dapper requires manual intervention https://bugs.launchpad.net/bugs/223226 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223206] [NEW] Can't upgrade Kubuntu Feisty to Gutsy
Public bug reported: Binary package hint: adept-updater Adept offered me a version upgrade. I made sure I had refreshed the repositories, and applied all available updates, then I asked for the version upgrade. It showed me the release announcement for Gutsy, and then told me it was downloading the upgrade tool. When that finished, it told me to click 'finish, and told me that adept would close, and the upgrade tool would launch. I clicked finish, that dialog box closed, but nothing else happened. Adept stayed put, and nothing else opened up. ** Affects: adept (Ubuntu) Importance: Undecided Status: New -- Can't upgrade Kubuntu Feisty to Gutsy https://bugs.launchpad.net/bugs/223206 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 149396] Re: Remote desktop crashes X,Ubuntu 64
Just encountered this: Upgraded my Kubuntu Dapper box to Hardy using update-manager -d. This box had been set up with vnc support in xorg. Next time I attempted to connect from my workstation in the garage(Kubuntu feisty using vncviewer), I can log in, and get the desktop displayed, but with the first keystroke or mouse click in the remote desktop, the vncviewer crashes, and when I re-launch it and log in again, I see the KDM login screen, indicating that it crashed the xorg server on the Hardy machine. -- Remote desktop crashes X,Ubuntu 64 https://bugs.launchpad.net/bugs/149396 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 222568] [NEW] package update-manager 1:0.81.2 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Couldn't configure pre-depend audacious-plugins for audacious-plugins-extra
Public bug reported: Binary package hint: update-manager Attempting to upgrade ubuntustudio on AMD64 to Hardy. Went to bed when it told me it needed four hours to download over 1000 packages. Got up to this message. ProblemType: Package Architecture: amd64 Date: Sat Apr 26 02:11:26 2008 DistroRelease: Ubuntu 7.10 ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Couldn't configure pre-depend audacious-plugins for audacious-plugins-extra, probably a dependency cycle. Package: update-manager 1:0.81.2 PackageArchitecture: all SourcePackage: update-manager Title: package update-manager 1:0.81.2 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Couldn't configure pre-depend audacious-plugins for audacious-plugins-extra, probably a dependency cycle. Uname: Linux studio 2.6.22-14-rt #1 SMP PREEMPT RT Tue Feb 12 03:54:33 UTC 2008 x86_64 GNU/Linux ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package -- package update-manager 1:0.81.2 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Couldn't configure pre-depend audacious-plugins for audacious-plugins-extra, probably a dependency cycle. https://bugs.launchpad.net/bugs/222568 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 222568] Re: package update-manager 1:0.81.2 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Couldn't configure pre-depend audacious-plugins for audacious-plugins-extra,
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/13936782/Dependencies.txt -- package update-manager 1:0.81.2 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Couldn't configure pre-depend audacious-plugins for audacious-plugins-extra, probably a dependency cycle. https://bugs.launchpad.net/bugs/222568 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 196858] Re: Video not detected Hardy KDE 4
Here's the dmesg output. see file attached. These are the lines that look to me to be video related, and they don't say anything unusual to me: /snip/ [ 24.140033] Console: colour VGA+ 80x25 [ 24.140042] console [tty0] enabled /snip/ [ 25.865200] Boot video device is :01:00.0 /snip/ [ 78.380016] Linux agpgart interface v0.102 /snip/ [ 79.276752] agpgart: Detected SiS chipset - id:1840 [ 79.291599] agpgart: AGP aperture is 64M @ 0xd000 /snip/ [0.00] Linux version 2.6.24-8-generic ([EMAIL PROTECTED]) (gcc version 4.2.3 (Ubuntu 4.2.3-1ubuntu2)) #1 SMP Thu Feb 14 20:40:45 UTC 2008 (Ubuntu 2.6.24-8.14-generic) [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000f - 0010 (reserved) [0.00] BIOS-e820: 0010 - 0eff (usable) [0.00] BIOS-e820: 0eff - 0eff8000 (ACPI data) [0.00] BIOS-e820: 0eff8000 - 0f00 (ACPI NVS) [0.00] BIOS-e820: fffc - 0001 (reserved) [0.00] 0MB HIGHMEM available. [0.00] 239MB LOWMEM available. [0.00] Entering add_active_range(0, 0, 61424) 0 entries of 256 used [0.00] Zone PFN ranges: [0.00] DMA 0 -> 4096 [0.00] Normal 4096 ->61424 [0.00] HighMem 61424 ->61424 [0.00] Movable zone start PFN for each node [0.00] early_node_map[1] active PFN ranges [0.00] 0:0 ->61424 [0.00] On node 0 totalpages: 61424 [0.00] DMA zone: 32 pages used for memmap [0.00] DMA zone: 0 pages reserved [0.00] DMA zone: 4064 pages, LIFO batch:0 [0.00] Normal zone: 447 pages used for memmap [0.00] Normal zone: 56881 pages, LIFO batch:15 [0.00] HighMem zone: 0 pages used for memmap [0.00] Movable zone: 0 pages used for memmap [0.00] DMI 2.3 present. [0.00] ACPI: RSDP signature @ 0xC00FC390 checksum 0 [0.00] ACPI: RSDP 000FC390, 0014 (r0 AMI ) [0.00] ACPI: RSDT 0EFF, 0028 (r1 AMIINT SiS730SX 1000 MSFT 10B) [0.00] ACPI: FACP 0EFF0030, 0074 (r1 AMIINT SiS730SX 1000 MSFT 10B) [0.00] ACPI: DSDT 0EFF00B0, 2D2C (r1SiS 730S 100 MSFT 10B) [0.00] ACPI: FACS 0EFF8000, 0040 [0.00] ACPI: BIOS age (1997) fails cutoff (2000), acpi=force is required to enable ACPI [0.00] ACPI: Disabling ACPI support [0.00] Allocating PCI resources starting at 1000 (gap: 0f00:f0fc) [0.00] swsusp: Registered nosave memory region: 0009f000 - 000a [0.00] swsusp: Registered nosave memory region: 000a - 000f [0.00] swsusp: Registered nosave memory region: 000f - 0010 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60945 [0.00] Kernel command line: BOOT_IMAGE=/casper/vmlinuz boot=casper initrd=/casper/initrd.gz quiet splash -- [0.00] Local APIC disabled by BIOS -- you can enable it with "lapic" [0.00] mapped APIC to b000 (011ec000) [0.00] Enabling fast FPU save and restore... done. [0.00] Enabling unmasked SIMD FPU exception support... done. [0.00] Initializing CPU#0 [0.00] PID hash table entries: 1024 (order: 10, 4096 bytes) [0.00] Detected 1294.287 MHz processor. [ 24.140033] Console: colour VGA+ 80x25 [ 24.140042] console [tty0] enabled [ 24.140589] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) [ 24.141145] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) [ 24.157911] Memory: 231460k/245696k available (2161k kernel code, 13676k reserved, 997k data, 364k init, 0k highmem) [ 24.157926] virtual kernel memory layout: [ 24.157927] fixmap : 0xfff4b000 - 0xf000 ( 720 kB) [ 24.157929] pkmap : 0xff80 - 0xffc0 (4096 kB) [ 24.157931] vmalloc : 0xcf80 - 0xff7fe000 ( 767 MB) [ 24.157933] lowmem : 0xc000 - 0xceff ( 239 MB) [ 24.157935] .init : 0xc041b000 - 0xc0476000 ( 364 kB) [ 24.157937] .data : 0xc031c5ed - 0xc0415dc4 ( 997 kB) [ 24.157939] .text : 0xc010 - 0xc031c5ed (2161 kB) [ 24.157944] Checking if this processor honours the WP bit even in supervisor mode... Ok. [ 24.158043] SLUB: Genslabs=11, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1 [ 24.238059] Calibrating delay using timer specific routine.. 2590.04 BogoMIPS (lpj=5180084) [ 24.238136] Security Framework initialized [ 24.238154] SELinux: Disabled at boot. [ 24.238204] AppArmor: AppArmor initialized [ 24.238216] Failure registering capabilities with primary securit
Re: [Bug 196858] Re: Video not detected Hardy KDE 4
On Sat, 1 Mar 2008, Dereck Wonnacott wrote: > Please attach your X server configuration file > (/etc/X11/xorg.conf) > and X server log file (/var/log/Xorg.0.log) to the > bug report /etc/X11/xorg.conf is present, but is a zero-length, empty file. /var/log/Xorg.0.log is non-existant, as is anything /X* in that directory. Actually, I think the problem is much deeper than X. lshw tells me that there is no driver claiming the video hardware. That info comes from /proc doesn't it? And is a kernel thing, right? I happened to find it when I wanted to take a peek at KDE4, but if the kernel doesn't know what driver to load, and xorg can't even build its own config, we're a long way from trying out new eye candy! -- Video not detected Hardy KDE 4 https://bugs.launchpad.net/bugs/196858 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 196858] Re: Video not detected Hardy KDE 4
I think you missed the first line of my report. I was runing a daily build of the LiveCD, and the problem was manifest by X not coming up at all. I won't be able to run a browser to log into launchpad, so I'll try it again, and see if I can find those files and ftp or sneakernet them to another machine for submission... -- Video not detected Hardy KDE 4 https://bugs.launchpad.net/bugs/196858 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 196858] Re: Video not detected Hardy KDE 4
Ditto on another system with ATI Radeon RV100 QY(Radeon 7000/VE) -- Video not detected Hardy KDE 4 https://bugs.launchpad.net/bugs/196858 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 196858] [NEW] Video not detected Hardy KDE 4
Public bug reported: Hardy daily build 20080220 KDE 4.0 Booting liveCD on AMD Duron 1.3G, 256M system with SIS video, the system appears to hang before KDM comes up. Looking closer, I found a shell prompt buried within the boot messages, so I decided to investigate. Neither dmesg nor tail /var/log/messages revealed any clues, so I tried startx, and got a message that /etc/X11/X did not exist. I ran lshw, and learned this about my video card: *display UNCLAIMED description: VGA compatible controller Product: 630/730 PCI/AGP Video Display Adapter ...so it appears that an appropriate driver for my card was not found. I attempted to run `sudo dpkg-reconfigure xserver-xorg` which has cleaned up other hw-detection problems, and I was told that xserver-xorg is not installed, and no information is available. ** Affects: ubuntu Importance: Undecided Status: New -- Video not detected Hardy KDE 4 https://bugs.launchpad.net/bugs/196858 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 12637] Re: LCD Brightness on Laptop Always Set Very Low at Boot
Well, I saw the problem with Ubuntu, Kubuntu, and Ubuntustudio x86_64 at the 7.10 release, so I don't think it's a desktop issue. Also, last night I managed to boot clumsily without X and gdm, and I also saw the problem when there was no X launching, so that kinda confirms it for me that its not X. It might not be the kernel VGA driver, but what else starts up at boot, does not depend on X, and could be modifying the display backlight level? I'm tied up on an intractible DSL problem for a client right now, so I can't even think about downloading an Ubuntu hardy alpha CD until later tonight... And besides, the Kubuntu hardy alpha CD did NOT show the problem, so whatever they did to make a 'generic' kernel that works on x86 as well as x86_64 either fixed or masked the problem. -- LCD Brightness on Laptop Always Set Very Low at Boot https://bugs.launchpad.net/bugs/12637 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 12637] Re: LCD Brightness on Laptop Always Set Very Low at Boot
Here's some more info. I went to system/administration/services, and disabled gdm, thinking I'd reboot to a console, just to see if this was a kernel problem, or possibly an xorg problem, since it's happening just milliseconds before the screen blanks to switch to X. Well, that wasn't clean at all! it kills gdm immediately, which blew away my X session, as well as all the apps running, leaving me at a very ugly console with a huge font, reminiscent of my old commodore VIC-20. I managed to reboot, and it did come up without X, but with the same ugly huge font, so I only saw about 10 lines of text, and my prompt was somewhere below the bottom of the screen, so I was typing blind. ...but the important part is that the screen dimmed, so this is definitely NOT an X issue, it's in the kernel. I also focussed my eyes at the top of the screen during the boot, and I was able to see that the [PCI} allocation... error that was displayed there came up DIM, just before the screen blanks, so the actual sequence is something like this: 'Kernel is alive' 'kernel mapping tables...' (backlight goes to dim) '[PCI] allocation'... Once I logged in at the console, I ran startx, and was able to get my desktop. I again went to system/administration/services and re-enabled gdm, which AGAIN took immediate action, which in this case tried to start a second X server, which failed once, but eventually succeeded (as :1), leaving me at the gdm prompt. I have no idea which virtual console I was on, but ctrl-alt-f7 got me back to the X session. I probably should file a bug elswhere for this usability issue... Or just go back to school. In this new age of upstart, how do I cleanly do a one-time reboot to a normal console? On my old redhat or suse systems, I always had runlevel 3, but I discovered a while back that in ubuntu runlevel 3 is the same as runlevel 5, and now with upstart, I have no idea if 'runlevels' even exist anymore, and if they do, how to configure and specify them? System/administration/services certainly has no visible 'runlevel-like' distinctions, /etc/inittab is gone grrr... There is no 'upstart' directory under /etc. There is no upstart manpage. Where do I look for clues? `man init` is still there. scroll to the bottom, its author is Scott James Remnant. So he calls the project upstart, but the binary is still init, just to confuse us, right? OK, the manpage mentions /etc/event.d. Go browse... rc-default seems to fall thru to runlevel 2. Looking at the /etc/rcn.d directories, I find that runlevel 1 would not start X, but all others 2 - 5 do. So I can probably edit one of those other directories to create a multiuser without X runlevel, but I still don't know how to pass a one-time parm thru grub to select that level. More studying to do, and I'm tired. I'm going to bed now... -- LCD Brightness on Laptop Always Set Very Low at Boot https://bugs.launchpad.net/bugs/12637 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 12637] Re: LCD Brightness on Laptop Always Set Very Low at Boot
Just booted the Hardy alpha 4 live CD (Kubuntu amd_64), and the LiveCD session booted up normally, without dimming the LCD! Since this is a working laptop now, I don't want to do a complete reinstall with the hardy alpha. Is there a way I can install just the kernel package from the hardy CD, and have it be a grub option in my normal Gutsy system? (actually ubuntustudio 7.10 w/ kernel 2.6.22-14-rt) I tried opening the liveCD in synaptic, but the only linux-image packages it finds on the CD appear to be older than the kernel I have installed in Gutsy... I notice from the package descriptions in adept that Hardy is using a 'generic' kernel for both x86 and x86_64, as well as UP and SMP. The plain x86 kernel in 7.04 didn't exhibit this problem, so is the problem now fixed, or is this 'generic' kernel really an x86 32bit kernel under the covers? Under Gutsy, the symptoms seem to be: 'Kernel is active' at bottom of screen 'kernel mapping tables...' at bottom of screen then [PCI] appears at the top of the screen, and the screen dimms, almost simultaneously, I can't really tell which is first. -- LCD Brightness on Laptop Always Set Very Low at Boot https://bugs.launchpad.net/bugs/12637 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 88691] Re: Dim LCD backlight on boot
*** This bug is a duplicate of bug 12637 *** https://bugs.launchpad.net/bugs/12637 I missed your request for info a month ago. I'm downloading hardy alpha 4 now, will test against that. I've also marked this as a duplicate of bug#12637, which appears to be the same problem on the gateway-branded version of the same machine. ** This bug has been marked a duplicate of bug 12637 LCD Brightness on Laptop Always Set Very Low at Boot -- Dim LCD backlight on boot https://bugs.launchpad.net/bugs/88691 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 88691] Re: Dim LCD backlight on boot
Don't do that! The bug is still there in Gutsy. -- Dim LCD backlight on boot https://bugs.launchpad.net/bugs/88691 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 24533] Re: Fail to boot smp kernel
I had also reported and confirmed this bug earlier. This weekend, I built up a test system (Dual PIII-550 w/ Radeon 7000 video) I booted it with a Hardy Alpha 4 server(already on HDD), then used aptitude to install kubuntu-desktop. I was able to startx, and the KDE desktop came up fine. I then launched adept, intending to install the 686 SMP kernel to test whether the bug was still there or not, and discovered that hardy doesnt have a 686 kernel! In fact, you've taken the 'generic' concept quite far, and are using one kernel for x86 and x86_64, UP and SMP alike. I ran uname -a, and found 2.6.24-7-server, and ran lshw and found both CPUs detected. So I guess the bottom line is this bug has been squashed in Hardy. Thank you! -- Fail to boot smp kernel https://bugs.launchpad.net/bugs/24533 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
Re: [Bug 12637] Re: LCD Brightness on Laptop Always Set Very Low at Boot
On Thu, 20 Sep 2007, Robert Drake wrote: > If I get the chance, I'll start throwing "got here" kprintf's in the > kernel in places before "Kernel is Active" to see what I find. > On my emachines M6810, the 'Kernel alive' message comes on bright, followed by a message beginning 'kernel mapping tables... ending with something that might be an address. THEN, the screen dims. So you might want to insert your debug flags after those messages, not before. -- LCD Brightness on Laptop Always Set Very Low at Boot https://bugs.launchpad.net/bugs/12637 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
Re: [Bug 88692] Re: Touchpad not fully functional
The bug was still present in the released version of feisty. I have not tried installing any of the gutsy milestones, since that machine is in 'production' use right now. Perhaps if I could locate a spare drive sled for it, I could again do test installs on it. -- Touchpad not fully functional https://bugs.launchpad.net/bugs/88692 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 12637] Re: LCD Brightness on Laptop Always Set Very Low at Boot
I don't know if I'm up to the challenge of compiling my own kernels. I haven't done that since about 1.2.x sometime... And that was just to config in a driver. I'm an old PL/I & COBOL programmer, and quite 'C' challenged. One item of note: this happens with amd_64 kernels only. Last week, I did an installation of ubuntustudio on this machine, and was pleased to discover that the LCD didn't go dim on me. But then disappointed to discover that it installed a 32 bit kernel, and gnome. So I went back to Kubuntu amd_64, then installed the ubuntustudio-audio packages (less one that's broken on amd64) So it may be that some of that vga-init code isn't 64-bit clean. There's another video bug open on this machine, but that has to do with xorg properly detecting the widescreen 1280x800 mode, and is probably unrelated to this lower-level vga bug. -- Rick Green "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety." -Benjamin Franklin -- LCD Brightness on Laptop Always Set Very Low at Boot https://bugs.launchpad.net/bugs/12637 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 103719] Re: Won't return from suspend on emachines M6810
With the feisty release kernel (2.6.20-15) The problem is still there. As well as an additional problem: I can hibernate the machine just once. After returning from hibernate, the system is in a 'screen locked' state, which wakes up with a stroke on the touchpad, and I can unlock the screen and continue working. However, If I attempt to hibernate the machine again, it goes dark, into a screenlock state, but never powers down. -- Won't return from suspend on emachines M6810 https://bugs.launchpad.net/bugs/103719 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 103719] Re: Won't return from suspend on emachines M6810
Sorry, I got that 'demidecode' from a comment/info request on a similar bug #81548... -- Won't return from suspend on emachines M6810 https://bugs.launchpad.net/bugs/103719 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 103163] Re: Unable to commit changes
see also bug #'s 104542 and 105139 -- Unable to commit changes https://bugs.launchpad.net/bugs/103163 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for adept in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 103163] Re: Unable to commit changes
The original problem seems to have been fixed (fail to commit) with todays' daily build (20070410), the 'version upgrade' problem is still there, but different: the message offering a new version is still there, but the 'next' button is now labelled 'version upgrade' and is not grayed out. The message, however, still refers to a 'next' button, which now is not there. When you click on 'version upgrade, it immediately fails with an error retrieving the release announcement, and a misleading indication that it might be attributable to a bad network connection. (patently false, since I just successfully downloaded and installed 8 packages). I noticed two other bugs filed this morning addressing this issue as well -- Unable to commit changes https://bugs.launchpad.net/bugs/103163 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for adept in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 71856] Re: KDesktop crash on KDE-initiated restart (SIGSEGV 11)
I ran dpkg-reconfigure -phigh xserver-xorg (see bug #89289 ) and rebooted. X and kde came up with the right resolution, and no crash this time. -- KDesktop crash on KDE-initiated restart (SIGSEGV 11) https://bugs.launchpad.net/bugs/71856 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdeutils in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 71856] Re: KDesktop crash on KDE-initiated restart (SIGSEGV 11)
same - immediate crash as KDE starts. First launch of daily build 20070407 on amd64 backtrace attached ** Attachment added: "kdesktop.backtrace" http://librarian.launchpad.net/7214003/kdesktop.backtrace -- KDesktop crash on KDE-initiated restart (SIGSEGV 11) https://bugs.launchpad.net/bugs/71856 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdeutils in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 103558] Re: Regression: k3b fails to verify
here's the 'debug info' produced by k3b while trying to burn the 0407 daily build. System --- K3b Version: 1.0 KDE Version: 3.5.6 QT Version: 3.3.7 Kernel: 2.6.20-14-generic Devices --- Slimtype COMBO LSC-24082K JBK2 (/dev/hdc, ) [CD-R, CD-RW, CD-ROM, DVD-ROM] [DVD-ROM, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R] Used versions --- cdrecord: 1.1.2 cdrecord --- scsidev: '/dev/hdc' devname: '/dev/hdc' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.2 SCSI buffer size: 64512 Beginning DMA speed test. Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. TOC Type: 1 = CD-ROM Driveropts: 'burnfree' atapi: 1 Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'Slimtype' Identification : 'COMBO LSC-24082K' Revision : 'JBK2' Device seems to be: Generic mmc2 DVD-ROM. Current: 0x0009 (CD-R) Profile: 0x0010 (DVD-ROM) Profile: 0x000A (CD-RW) Profile: 0x0009 (CD-R) (current) Profile: 0x0008 (CD-ROM) Profile: 0x0002 (Removable disk) Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE FORCESPEED Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R Drive buf size : 1422080 = 1388 KB FIFO size : 12582912 = 12288 KB Speed set to 4234 KB/s Track 01: data 698 MB Total size: 802 MB (79:29.20) = 357690 sectors Lout start: 802 MB (79:31/15) = 357690 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 5 Is not unrestricted Is not erasable Disk sub type: Medium Type B, low Beta category (B-) (4) ATIP start of lead in: -12369 (97:17/06) ATIP start of lead out: 359849 (79:59/74) Disk type:Short strategy type (Phthalocyanine or similar) Manuf. index: 69 Manufacturer: Moser Baer India Limited Manufacturer is guessed because of the orange forum embargo. The orange forum likes to get money for recent information. The information for this media may not be correct. Blocks total: 359849 Blocks current: 359849 Blocks remaining: 2159 Forcespeed is OFF. Starting to write CD/DVD at speed 24.0 in real SAO mode for single session. Last chance to quit, starting real write in 2 seconds. 1 seconds. 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Performing OPC... Sending CUE sheet... Writing pregap for track 1 at -150 Starting new track at sector: 0 Track 01:0 of 698 MB written. Track 01:1 of 698 MB written (fifo 100%) [buf 99%] 0.4x. Track 01:2 of 698 MB written (fifo 100%) [buf 99%] 11.3x. Track 01:3 of 698 MB written (fifo 100%) [buf 99%] 11.7x. Track 01:4 of 698 MB written (fifo 100%) [buf 99%] 11.4x. Track 01:5 of 698 MB written (fifo 100%) [buf 99%] 11.7x. Track 01:6 of 698 MB written (fifo 100%) [buf 99%] 11.4x. Track 01:7 of 698 MB written (fifo 100%) [buf 99%] 11.8x. Track 01:8 of 698 MB written (fifo 100%) [buf 99%] 11.4x. Track 01:9 of 698 MB written (fifo 100%) [buf 99%] 11.9x. Track 01: 10 of 698 MB written (fifo 100%) [buf 99%] 11.5x. Track 01: 11 of 698 MB written (fifo 100%) [buf 99%] 11.8x. Track 01: 12 of 698 MB written (fifo 100%) [buf 99%] 11.6x. Track 01: 13 of 698 MB written (fifo 100%) [buf 99%] 11.9x. Track 01: 14 of 698 MB written (fifo 100%) [buf 99%] 11.6x. Track 01: 15 of 698 MB written (fifo 100%) [buf 99%] 12.0x. Track 01: 16 of 698 MB written (fifo 100%) [buf 99%] 11.6x. Track 01: 17 of 698 MB written (fifo 100%) [buf 99%] 12.0x. Track 01: 18 of 698 MB written (fifo 100%) [buf 99%] 11.7x. Track 01: 19 of 698 MB written (fifo 100%) [buf 99%] 12.1x. Track 01: 20 of 698 MB written (fifo 100%) [buf 99%] 11.7x. Track 01: 21 of 698 MB written (fifo 100%) [buf 99%] 12.1x. Track 01: 22 of 698 MB written (fifo 100%) [buf 99%] 11.8x. Track 01: 23 of 698 MB written (fifo 100%) [buf 99%] 12.2x. Track 01: 24 of 698 MB written (fifo 100%) [buf 99%] 11.8x. Track 01: 25 of 698 MB written (fifo 100%) [buf 99%] 12.2x. Track 01: 26 of 698 MB written (fifo 100%) [buf 99%] 11.9x. Track 01: 27 of 698 MB written (fifo 100%) [buf 99%] 12.2x. Track 01: 28 of 698 MB written (fifo 100%) [buf 99%] 11.9x. Track 01: 29 of 698 MB written (fifo 100%) [buf 99%] 12.3x. Track 01: 30 of 698 MB written (fifo 100%) [buf 99%] 11.9x. Track 01: 31 of 698 MB written (fifo 100%) [buf 99%] 12.3x. Track 01: 32 of 698 MB written (fifo 100%) [buf 99%] 12.0x. Track 01: 33 of 698 MB written (fifo 100%) [buf 99%] 12.4x. Track 01: 34 of 698 MB written (fifo 100%) [buf 99%] 12.8x. Track 01: 35 of 698 MB written (fifo 100%) [buf 99%] 12.4x. Track 01: 36 of 698 MB written (fifo 100%) [buf 99%] 12.8x.
[Bug 103988] Re: [apport] ubiquity crashed with ImportError in ()
** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/7193329/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/7193330/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/7193331/ProcStatus.txt ** Attachment added: "Traceback.txt" http://librarian.launchpad.net/7193332/Traceback.txt ** Attachment added: "UbiquitySyslog.gz" http://librarian.launchpad.net/719/UbiquitySyslog.gz -- [apport] ubiquity crashed with ImportError in () https://bugs.launchpad.net/bugs/103988 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 103988] [apport] ubiquity crashed with ImportError in ()
Public bug reported: Binary package hint: ubiquity Booted from Feisty desktop amd64 daily build 20070406, after frist having verified CD integrity. Clisked on 'install' icon on desktop. Received crash message. ProblemType: Crash Architecture: amd64 Date: Sat Apr 7 04:51:31 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/lib/ubiquity/bin/ubiquity InterpreterPath: /usr/bin/python2.5 Package: ubiquity 1.4.7 PackageArchitecture: amd64 ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity kde-ui ProcCwd: /home/ubuntu ProcEnviron: PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', 'kde-ui'] SourcePackage: ubiquity Uname: Linux ubuntu 2.6.20-14-generic #2 SMP Mon Apr 2 16:32:46 UTC 2007 x86_64 GNU/Linux ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] ubiquity crashed with ImportError in () https://bugs.launchpad.net/bugs/103988 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 103558] Re: Feisty beta ISO testing
with the 20070405 build, I experienced the same problem, and one additional problem: The CDR came up with DMA support off. WHen I started k3b, it notified me that DMA was off, but for the next few minutes, my system was incredibly unresponsive. Even the cursor! It took me several minutes to move the cursor to a konsole window so I could enable DMA. Finally, k3b finished initializing, the drive door opened (I had pressed the button immediately after launching k3b), and the cursor became responsive. I enabled DMA on hdc, and proceeded to burn the disk. Again, it quit after the burn phase and notified me that the verification job was improperly initialized. ** Summary changed: - Feisty beta ISO testing + Regression: k3b fails to verify -- Regression: k3b fails to verify https://bugs.launchpad.net/bugs/103558 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 103719] Re: Won't return from suspend on emachines M6810
** Attachment added: "dmidecode.txt" http://librarian.launchpad.net/7192533/dmidecode.txt -- Won't return from suspend on emachines M6810 https://bugs.launchpad.net/bugs/103719 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 103719] Re: Won't return from suspend on emachines M6810
[EMAIL PROTECTED]:~$ uname -a Linux rtg-laptop 2.6.20-14-generic #2 SMP Mon Apr 2 16:32:46 UTC 2007 x86_64 GNU/Linux [EMAIL PROTECTED]:~$ sudo lspci -vv >kerndebug.txt [EMAIL PROTECTED]:~$ sudo lspci -vvn >>kerndebug.txt [EMAIL PROTECTED]:~$ sudo demidecode >>kerndebug.txt sudo: demidecode: command not found ** Attachment added: "kerndebug.txt" http://librarian.launchpad.net/7179548/kerndebug.txt -- Won't return from suspend on emachines M6810 https://bugs.launchpad.net/bugs/103719 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 103719] Re: Won't return from suspend on emachines M6810
/var/log/kern.log.0 ** Attachment added: "kern.log.0" http://librarian.launchpad.net/7179507/kern.log.0 -- Won't return from suspend on emachines M6810 https://bugs.launchpad.net/bugs/103719 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 103719] Won't return from suspend on emachines M6810
Public bug reported: Binary package hint: linux-source-2.6.20 My AMD_64 laptop, an emachines M6810, refuses to wake up from suspend. I was tracking bug # 74877, but when that was apparently fixed at 2.4.20-14 for the HP laptops, and I continue to have the problem, I was asked to open a new one, specific to my hardware. Suspend appears to work, taking a while, but leaving the machine in a mostly-dark state, with the power light flashing slowly. Pressing any key on the keyboard causes the power light to come on steady, but that's the only indication, no screen or HDD activity happens. ** Affects: linux-source-2.6.20 (Ubuntu) Importance: Undecided Status: Unconfirmed -- Won't return from suspend on emachines M6810 https://bugs.launchpad.net/bugs/103719 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 74877] Re: regression: suspend does not work on hp nw8240 with feisty
I hate to rain on the parade, but suspend STILL doesn't work on an emachines M6810 with kernel 2.6.20-14-generic x86_64 This is feisty daily build 20070405, with the -14 kernel installed by adept updater. -- regression: suspend does not work on hp nw8240 with feisty https://bugs.launchpad.net/bugs/74877 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 103589] Re: ubuntustudio-audio not installable
Reference bug# 32460 -- ubuntustudio-audio not installable https://bugs.launchpad.net/bugs/103589 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 103589] ubuntustudio-audio not installable
Public bug reported: Binary package hint: ubuntustudio-audio The package 'supercollider' has been broken on amd_64 for over a year. Since it's listed as a dependency on ubuntustudio-audio, it makes that package uninstallable. I believe that the supercollider dependency should be removed from ubuntustudio-audio until such time as the amd64 build problems are resolved. ** Affects: ubuntustudio-meta (Ubuntu) Importance: Undecided Status: Unconfirmed -- ubuntustudio-audio not installable https://bugs.launchpad.net/bugs/103589 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 103163] Re: Unable to commit changes
Testing daily build 20070405... INstall went well, and initial run of adept updater also worked, installing 5 packages and upgrading 29. ...however, at the end of the run, I was left with a message "A new version of Kubuntu is available! Click next if you wish to upgrade now." WTF? this is a fresh install of TODAY's daily build! ANd it's tellin me I should upgrade??? To what? ...its a moot point anyway. The 'Next' button is grayed out... My only active option is 'Quit' -- Unable to commit changes https://bugs.launchpad.net/bugs/103163 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for adept in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 103558] Re: Feisty beta ISO testing
Just noticed - this version of k3b is calling /usr/bin/wodim ISTR that it was using cdrecord just a few days ago... -- Feisty beta ISO testing https://bugs.launchpad.net/bugs/103558 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for k3b in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 103558] Feisty beta ISO testing
Public bug reported: Binary package hint: k3b Kubuntu amd64 desktop feisty beta daily build 20070404. Package k3b - trying to burn the 20070405 iso. Writing successfully completed. Internal error: Verification job improperly initialized. The 0404 daily build seems to be a regression. I earlier reported problems with adept - I can't apply updates or install packages after installation (Bug #103163) A week or two ago, there were bugs filed where I could post an overall 'test report' on a given install test, but those seem to have been closed, at least I can't find them anymore with a search for 'iso testing'. Why? Those should be left open until the final release date. ** Affects: k3b (Ubuntu) Importance: Undecided Status: Unconfirmed -- Feisty beta ISO testing https://bugs.launchpad.net/bugs/103558 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for k3b in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 99825] Re: Installer crashed at 'manual partition'
Confirmed on daily build 20070331 -- Installer crashed at 'manual partition' https://launchpad.net/bugs/99825 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103163] Unable to commit changes
Public bug reported: Binary package hint: adept-manager Fresh install of Feisty Kubuntu amd64 daily build 20070404. Ran adept updater, which found about 30 packages to update. However, during the run it spit out a message that changes couldn't be committed. I was not able to determine which package was broken. I then opened up Adept manager, thinking I'd install one package at a time until I found the culprit. As I opened Adept, it immediately spit out the message "You will not be able to change your system settings in any way(install, remove, or upgrade software), because another process is using the packaging system database" I checked ps aux for other adept processes, and found none, so I rebooted, thinking that'd clean out any orphans. However, after the reboot, I attempted to open adept, and it immediately spit out the same error ** Affects: adept (Ubuntu) Importance: Undecided Status: Unconfirmed -- Unable to commit changes https://bugs.launchpad.net/bugs/103163 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 102979] Unexpected 'NEXT' button behavior
Public bug reported: Binary package hint: ubiquity INstalling Kubuntu Feisty Beta daily build 20070404, Step 5 of 6. After filling out the form uning the keyboard, I tab until the 'Next' button is hilighted (actually outlined by a dashed box), and hit enter. Nothing happens. I am forced to move my hands to the mouse, hover the cursor over that button, and click the left button. Then it proceeds forward... I saw several other bugs reporting strange behaviour with the next button, but they all referred to an upstream GTK issue, and had to do with a mouse click not being noticed if the cursor just happened to be hovering over a button when a dialog window opens. There was also a mention that the kubuntu version of the installer uses libqt, not GTK. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: Unconfirmed -- Unexpected 'NEXT' button behavior https://bugs.launchpad.net/bugs/102979 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 71856] Re: KDesktop crash on KDE-initiated restart (SIGSEGV 11)
Got an immediate crash on first launch of Kubuntu Feisty beta daily build 20070402 after install. backtrace attached. ** Attachment added: "KDesktop_backtrace.txt" http://librarian.launchpad.net/7117707/KDesktop_backtrace.txt -- KDesktop crash on KDE-initiated restart (SIGSEGV 11) https://bugs.launchpad.net/bugs/71856 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdeutils in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 99660] Re: Installer crashed
Got past this point with Kubuntu daily build 20070402 amd_64 Thank you! -- Installer crashed https://bugs.launchpad.net/bugs/99660 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 32460] Re: [UNMETDEPS] Uninstallable on AMD64
Confirmed: Still uninstallable on Kubuntu Feisty daily build 20070322.1 amd_64 -- [UNMETDEPS] Uninstallable on AMD64 https://launchpad.net/bugs/32460 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99825] Re: Installer crashed at 'manual partition'
** Attachment added: "/var/log/syslog" http://librarian.launchpad.net/7099956/syslog ** Tags added: regression -- Installer crashed at 'manual partition' https://launchpad.net/bugs/99825 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99825] Re: Installer crashed at 'manual partition'
** Attachment added: "/var/log/partman" http://librarian.launchpad.net/7099954/partman -- Installer crashed at 'manual partition' https://launchpad.net/bugs/99825 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99825] Installer crashed at 'manual partition'
Public bug reported:
Binary package hint: ubiquity
This appeared as I selected 'manual partition' in step 4 of the
installer.
Traceback (most recent call last):
File "/usr/lib/ubiquity/ubiquity/frontend/kde-ui.py", line 2559, in data
return QVariant(item.data(index.column()))
File "/usr/lib/ubiquity/ubiquity/frontend/kde-ui.py", line 2655, in data
return QVariant(self.partman_column_name())
File "/usr/lib/ubiquity/ubiquity/frontend/kde-ui.py", line 2686, in
partman_column_name
return ' %s' % get_string('partman/text/unusable', self.locale)
AttributeError: TreeItem instance has no attribute 'locale'
Attempting install on emachines M6810 with Kubuntu daily build 20070401 amd_64.
This is a regression. daily build 20070322.1 installed without problems.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Installer crashed at 'manual partition'
https://launchpad.net/bugs/99825
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 12637] Re: LCD Brightness on Laptop Always Set Very Low at Boot
Confirmed again on Kubuntu Feisty daily build 20070401 amd_64 -- LCD Brightness on Laptop Always Set Very Low at Boot https://launchpad.net/bugs/12637 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 40503] Re: Synaptics touchpad detection (regression)
I've been having this same problem occur with Feisty, from herd 4 thru today's daily build (20070401) I'm running Kubuntu AMD_64. laptop-detect returns true. on herd-5,the last one I installed, dpkg --reconfigure xserver-xorg did correctly detect both the touchpad and the monitor, giving me the proper resolution. ** Attachment added: "casper.log from 20070401 Kubuntu livecd" http://librarian.launchpad.net/7099875/casper.log -- Synaptics touchpad detection (regression) https://launchpad.net/bugs/40503 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89289] Re: Wrong resolution on initial install - Radeon 9600 Laptop LCD
OK, Here's a copy of casper.log from a live session Kubuntu daily build 20070401 amd_64 ** Attachment added: "csper.log from live session" http://librarian.launchpad.net/7099830/casper.log -- Wrong resolution on initial install - Radeon 9600 Laptop LCD https://launchpad.net/bugs/89289 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84592] Re: feisty shutdown eject doesn't
with amd64 desktop daily build 20070322.1(k) on emachines laptop: Appears to be fixed. CD ejects OK after liveCD session. -- feisty shutdown eject doesn't https://launchpad.net/bugs/84592 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 88687] Re: qtparted abnormal exit
> code, I'm thinking that maybe a checkbox on the autopartitioning page > for whether you want to trust the installer or exert more fine-grained > control would be best and easiest to implement. Until that's done, would you please change the word 'guided' to 'automatic' so that it's clear that no guidance is possible? -- qtparted abnormal exit https://launchpad.net/bugs/88687 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 87814] Re: Kubuntu 7.04 chash at update
*** This bug is a duplicate of bug 68267 *** Which tool did you use? I had this experience with adept, and I was successful in completing the update with 'apt-get upgrade' on the command line. -- Kubuntu 7.04 chash at update https://launchpad.net/bugs/87814 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88697] Re: dpkg: invalid nice value
*** This bug is a duplicate of bug 68267 *** I got the error three times: First, when the adept window just said 'preparing...' Second, when adept said 'preparing update for x11-common' and a third time, soon after, when I didn't catch the package name in question. I also got it when using adept to install a single package 'adept'. However, when I went to the command line to execute 'apt-get install adept', it not only did that, but noticed five packages only partly installed, including x11-common, and it successfully finished the job on those. I guess what needs to be done, is another fresh install, and then an immediate 'apt-get update; apt-get upgrade' rather than using the GUI for the initial update. I'm well beyond that point now, working on some sound issues, so I won't get a chance to do another fresh install until herd 6 comes around. -- dpkg: invalid nice value https://launchpad.net/bugs/88697 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 89878] Re: Screen blanks, locks during install of herd 5
Actually, I wasn't able to get this to repeat. It occurred on an AMD64 with 512MB RAM as I was exploring the K menu (not actually opening any apps) while ubiquity was doing the initial load. The system didn't crash - just the screen went blank. I could see the hdd light blinking, so the file load was still continuing in the background. When I stroke the touchpad, or press a key, the normal 'unlock screen' dialog opens up. The problem is that there's no password for the 'ubuntu' user, so I didn't know how to unlock it again. When I started over, and sat on my hands during the load, it worked fine, so there's the possibility that I somehow fat-fingered some hotkey to lock the screen. Is there such a hotkey defined in the X config of the LiveCD? If so, is it recoverable? Since there's no password defined for the 'ubuntu' user that is active in a liveCD session, how would one unlock the screen in that case? -- Screen blanks, locks during install of herd 5 https://launchpad.net/bugs/89878 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88697] Re: dpkg: invalid nice value
*** This bug is a duplicate of bug 68267 *** I see someone marked this as a duplicate of #68267. WHy would anyone think this is a problem with x11-common? It seems clear from my experience, and comments on others also marked as dups to 68267, that the problem clearly happens when running adept or adept-updater, and does not occur if I run apt-get upgrade in a Konsole window. Wouldn't that indicate that the problem is in adept? Not the package which happens to be in the process of being upgraded? -- dpkg: invalid nice value https://launchpad.net/bugs/88697 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 89988] Re: [apport] jackd crashed with SIGSEGV in start_thread()
another note: jackd -d alsa did not crash, in fact I was able to start ardour and make and play back a simple recording. At the time of the crash, no firewire audio device was plugged in. I don't actually own any device supported by freebob, I was trying to get the software loaded and configured before I arrange to borrow one... -- [apport] jackd crashed with SIGSEGV in start_thread() https://launchpad.net/bugs/89988 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89779] Re: Regression [feisty] HP TC4200 fails to resume properly after suspend
Also experiencing this problem on an emachines m6810 AMD_64 with ATI Radeon 9600. Suspend is slow, but eventually goes down, leaving power light blinking. When I touch any key, the power light comes back on solid, but the video never comes back. Pwr cycle and reboot is necessary. -- Regression [feisty] HP TC4200 fails to resume properly after suspend https://launchpad.net/bugs/89779 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89988] Re: [apport] jackd crashed with SIGSEGV in start_thread()
** Attachment added: "CoreDump.gz" http://librarian.launchpad.net/6639670/CoreDump.gz ** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/6639671/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/6639672/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/6639673/ProcStatus.txt ** Attachment added: "Registers.txt" http://librarian.launchpad.net/6639674/Registers.txt ** Attachment added: "ThreadStacktrace.txt" http://librarian.launchpad.net/6639675/ThreadStacktrace.txt -- [apport] jackd crashed with SIGSEGV in start_thread() https://launchpad.net/bugs/89988 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89988] [apport] jackd crashed with SIGSEGV in start_thread()
Public bug reported: Fresh install of Feisty herd 5. installed jackd, jackctl. Modprobe raw1394, jackd -d freebob produced this SYSSEGV immediately. ProblemType: Crash Architecture: amd64 Date: Mon Mar 5 18:46:17 2007 Disassembly: 0x2ad1ae10: DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/jackd Package: jackd 0.102.20-1 PackageArchitecture: amd64 ProcCmdline: jackd -d freebob ProcCwd: /home/rtg ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 Signal: 11 SourcePackage: jack-audio-connection-kit Stacktrace: #0 0x2ad1ae10 in ?? () #1 0x2b4732eeb2a5 in start_thread () from /lib/libpthread.so.0 #2 0x2b47333d45dd in clone () from /lib/libc.so.6 #3 0x in ?? () StacktraceTop: ?? () start_thread () from /lib/libpthread.so.0 clone () from /lib/libc.so.6 ?? () Uname: Linux rtg-laptop 2.6.20-9-generic #2 SMP Sun Feb 25 22:59:06 UTC 2007 x86_64 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video ** Affects: jack-audio-connection-kit (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] jackd crashed with SIGSEGV in start_thread() https://launchpad.net/bugs/89988 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 89878] Screen blanks, locks during install of herd 5
My second attempt to install went without a hitch, as I forced myself to sit on my hands and not explore the LiveCD system while ubiquity was busy... -- Screen blanks, locks during install of herd 5 https://launchpad.net/bugs/89878 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88692] Re: Touchpad not fully functional
Herd 5 now: same problem on initial install. While researching another problem (#89289), I was prompted to run 'dpkg-reconfigure -phigh xserver-xorg' This re-created the xorg.conf file, and did indeed detect the synaptic touchpad. The vertical scroll area and the double-tap-and-drag selection technique now works! Here's the area of xorg.conf as built by dpkg-reconfigure: Section "InputDevice" Identifier "Synaptics Touchpad" Driver "synaptics" Option "SendCoreEvents""true" Option "Device""/dev/psaux" Option "Protocol" "auto-dev" Option "HorizScrollDelta" "0" EndSection : -- Touchpad not fully functional https://launchpad.net/bugs/88692 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89289] Re: Wrong resolution on initial install - Radeon 9600 Laptop LCD
Here's the xorg.conf as produced by dpkg-reconfigure -phigh xserver- xorg. ** Attachment added: "xorg.conf produced by dpkg-reconfigure" http://librarian.launchpad.net/6634504/xorg.conf.reconfigure -- Wrong resolution on initial install - Radeon 9600 Laptop LCD https://launchpad.net/bugs/89289 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89289] Re: Wrong resolution on initial install - Radeon 9600 Laptop LCD
OK, here's a herd 5 update: LiveCD, as well as initial install gave me 1024x768. xorg.conf is attached. At a suggestion I read on another (nv, but similar) bug report, I switched to a text console, logged in as root, ran dpkg-reconfigure -phigh xserver-xorg, then rebooted. It came up in the proper 1280x800 resolution, and it even detected the touchpad. However, it didn't detect the radeon chip, but rather called it a 'generic video card', but that doesn't seem to matter, it's only an identifier, the driver and busid values are the same, and it works! Then, I saved that xorg.conf by renaming it, and restarted X as you suggested to let it do its own detection. It appears that the resolution is finer than 1024x768, but I don't think its 1280x800. X didn't create an xorg.conf, and the system settings/monitor&display applet refuses to launch. Also, the synaptic touchpad wasn't detected, so I'm back to no Vscroll area. ** Attachment added: "original xorg.conf from herd5 install" http://librarian.launchpad.net/6634491/xorg.conf.20070305123956 -- Wrong resolution on initial install - Radeon 9600 Laptop LCD https://launchpad.net/bugs/89289 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88697] Re: dpkg: invalid nice value
*** This bug is a duplicate of bug 85979 *** Fresh install of Feisty herd 5 X86_64 Adept updater tells me there are 115 updates, two packages to remove. After downloading, window shows a progress bar labelled 'preparing...' at 0%. A second window opens labelled 'Debconf on rtg-laptop' with the message 'Incorrect nice value; Please enter an integer between -20 and 19', but no input box. 'Next' does nothing. 'Cancel' closes the window and the updater appears to continue. At 5% 'Preparing upgrade of x11-common...', I get the same message window again. This time, clicking 'cancel' causes the following message window to appear in the center of the adept updater window: "Could not commit changes - Adept Updater. There was an error committing changes. Possibly there was a problem downloading some packages or the commit would break packages" This was followed almost immediately by the appearance of a third 'incorrect nice value message window. I close this window, then click OK in the 'could not commit changes' dialog. The adept updater window shows 'Update complete', and offers me only a 'Quit' option. Why don't I have a warm fuzzy about this message??? I click 'quit' and the window closes. I open a Konsole window, and enter 'ps aux | grep adept', and am presented with three PIDs: adept-notifier, kio-file, and kio-http, all in status S. I issue 'sudo apt-get upgrade' as I did on herd 4, and I am presented with 77 to upgrade, and 35 not fully installed or removed. The upgrade proceeds without further prompting. A second upgrade, followed by a dist-upgrade, present no further packages to be upgraded or installed. -- dpkg: invalid nice value https://launchpad.net/bugs/88697 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 89898] CD drive locked while restarting Feisty
Public bug reported: Feisty Herd 4 and Herd 5 X86_64 When restarting a liveCD session, or restarting into the freshly-installed system, theCD fails to eject as earlier releases did. I'm left with a message on the screen that tells me to remove the CD and press enter. When I press the CD tray eject button, nothing happens, apparently the drive is still locked. I press enter, and while the BIOS POST routine is executing, I can open the CD drawer just in time to have the system boot from the HDD instead. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- CD drive locked while restarting Feisty https://launchpad.net/bugs/89898 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89878] Screen blanks, locks during install of herd 5
Public bug reported: Binary package hint: ubiquity While installing Herd 5 (Kubuntu X86_64), after partitioning, at about the 70% mark while installing files, my screen went from the X desktop, to a text console (probably pty0, it had the kernel messages on it, with 'Kernel active' at the bottom) I waited a minute, and when it didn't restore itself, I hit alt-f7 to get back to X. WHat I got was a black screen with a dialog box saying that the screen was locked, and I am prompted to enter the password for the 'ubuntu' user. Hitting enter with the password field blank, or any simple password I guessed (password, user, ubuntu, root, toor) simply said 'unlock failed'. Looks like its time to reboot and restart the install... Hope it goes different. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: Unconfirmed -- Screen blanks, locks during install of herd 5 https://launchpad.net/bugs/89878 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88687] Re: qtparted abnormal exit
Installing herd 5 - Apparently a change has been made to ubiquity. WHen I select 'manual partitioning', I now get a disk summary within the ubiquity window, that looks different from gparted or qtparted. Since I didn't really want to repartition, I had to poke a bit before I discovered that a right-click, and selecting 'edit' would allow me to set the mount point of each partition. -- qtparted abnormal exit https://launchpad.net/bugs/88687 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 12637] Re: LCD Brightness on Laptop Always Set Very Low at Boot
Still happening on Feisty herd 5 Kubuntu live CD. -- LCD Brightness on Laptop Always Set Very Low at Boot https://launchpad.net/bugs/12637 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89289] Wrong resolution on initial install - Radeon 9600 Laptop LCD
Public bug reported: Binary package hint: xorg Initial install of Feisty Herd 4 on emachines M6810 showed problems with hardware detection in xorg: LCD is 1280x800, but X came up as 1024x768 KCD backlight very dim on boot (Bug # 88691) Touchpad not fully functional (Bug #88692) I had initiall reported this as a comment on #79016, but further investigation has shown that my problem was caused by improper detection of the monitor, not the graphics chipset. The monitor was detected as a generic LCD: Section "Monitor" Identifier "Generic Monitor" Option "DPMS" HorizSync 28-51 VertRefresh 43-60 EndSection Section "Screen" Identifier "Default Screen" Device "ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]" 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" Depth 15 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "1024x768" "800x600" "640x480" EndSubSection EndSection ** Affects: xorg (Ubuntu) Importance: Undecided Status: Unconfirmed -- Wrong resolution on initial install - Radeon 9600 Laptop LCD https://launchpad.net/bugs/89289 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 79016] Re: Wrong resolution with an nvidia GeForceGo 7300
Done, #89289 -- Wrong resolution with an nvidia GeForceGo 7300 https://launchpad.net/bugs/79016 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 79016] Re: Wrong resolution with an nvidia GeForceGo 7300
On Fri, 2 Mar 2007, Duncan Lithgow wrote: > Richard, please make a seperate bugreport for your problem. If they're > similar then you can mention that here. > > I did: #88691 (LCD backlight set to dim at boot) #88692 (touchpad not fully functional) -- Wrong resolution with an nvidia GeForceGo 7300 https://launchpad.net/bugs/79016 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88692] Re: Touchpad not fully functional
More info: initial install mis-identified the touchpad. This might explain the limited functionality. Snippet from xorg.conf: 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 -- Touchpad not fully functional https://launchpad.net/bugs/88692 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79016] Re: Wrong resolution with an nvidia GeForceGo 7300
I'm on herd 4, AMD_64 with ATI radeon 9600. While I've messed with the X config using the system settings GUI, so I can't be absolutely sure, here is the relevant section of xorg.conf.1, which I think is the original one from the installation: 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 "Device" Identifier "ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]" Driver "ati" 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 "ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]" 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" Depth 15 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "1024x768" "800x600" "640x480" EndSubSection EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" InputDevice "stylus" "SendCoreEvents" InputDevice "cursor" "SendCoreEvents" InputDevice "eraser" "SendCoreEvents" EndSection ...so it appears that it detected the radeon correctly, but missed it on the touchpad and monitor. Somehow, in my playing, I ended up with this monitor definition: Section "Monitor" identifier "Generic Monitor" modelname "Custom 1" modeline "[EMAIL PROTECTED]" 25.2 640 656 752 800 480 490 492 525 -vsync -hsync modeline "[EMAIL PROTECTED]" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync modeline "[EMAIL PROTECTED]" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync modeline "[EMAIL PROTECTED]" 65.0 1024 1048 1184 1344 768 771 777 806 -vsync -hsync modeline "[EMAIL PROTECTED]" 64.995 1152 1178 1314 1472 768 771 777 806 +hsync +vsy nc modeline "1280x854" 80.0 1280 1309 1460 1636 854 857 864 896 +hsync +vsync gamma 1.0 EndSection ...so I've got a better display now. The control panel GUI is telling me its set at 1280x800, but as I look at it, xorg.conf has only 1280x854 defined, so there's some interpolation going on, and I probably could get a clearer display if I found a modeline that matched properly. When herd 5 comes out, I'll do a clean install again, and see if the detection has improved. -- Wrong resolution with an nvidia GeForceGo 7300 https://launchpad.net/bugs/79016 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 12637] Re: LCD Brightness on Laptop Always Set Very Low at Boot
Bug confirmed still present on emachines M6810 with kernel 2.6.20-9 x86_64 (Feisty herd 4+) AMD Athlon 64 3200+; ATI Radeon mobility 9600 Just before it dimms, the graphical screen is replaced by a text screen, and I see the words 'Kernel is Active' briefly appear at the bottom. -- LCD Brightness on Laptop Always Set Very Low at Boot https://launchpad.net/bugs/12637 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88697] Re: dpkg: invalid nice value
Back to the root console apt-get update;apt-get upgrade; apt-get dist-upgrade' followed by a reboot, and now I can use adept again. I successfully installed the xastir package, as well as the 10 dependencies it pulled in. SO this was apparently fixed by one of the ~200 packages updated since the herd 4 release. -- dpkg: invalid nice value https://launchpad.net/bugs/88697 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88697] going backwards...
I ran 'apt-get install apt' from a root console. It upgraded 11 packages, including apt-utils, adept-manager, adept-installer, adept-updater, and adept-notifier. Then I tried another adept run. 'Full upgrade' told me it would upgrade 195 packages, but when I clicked 'apply changes', the adept window closed immediately. I tried starting adept again, but no window appears. ps aux shows 5 PIDs in status S or Ss referencing 'adept'. Rebooting... A window pops up asking for my password. It wants to restart an active adept-manager session. The adept window opens, and 'ps aux | grep adept' shows four pids. 'Full upgrade' indicates install 5, upgrade 194. 'Apply changes' gives the same popup and error message as before. -- dpkg: invalid nice value https://launchpad.net/bugs/88697 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 88697] Re: dpkg: invalid nice value
I keep trying... I ran 'apt-get install adept' from a root shell, and it told me that adept was already at the current level. It then went on to tell me that there were 5 packages not fully installed, and it gave me 5 'setting up...' messages for x11-common, libxau6, libxdmcp6, libxcb1, libxcb-xlib0. I went back to adept, and attempted a 'full upgrade' which presented 5 install, 205 upgrade. As it began, I clicked on 'show detail' just before the 'invalid nice value' popped up. The last lines in the 'show details window are: Preconfiguring packages ... Use of uninitialized value in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 104, line 4. /usr/share/perl5/Debconf/DbDriver/Stack.pm line 104, line 9. hth, -- dpkg: invalid nice value https://launchpad.net/bugs/88697 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 88697] Re: dpkg: invalid nice value
Additional info: I just ran adept from the K menu, ran 'fetch updates' and learned that adept is upgradable. I requested installation, and again got the same error. The popup window is labelled 'Debconf on rtg-laptop', the message requests an integer between '-20 and 19', and the active buttons are 'Help', 'Next>', and 'Cancel'. Help and Next do nothing, and Cancel aborts the entire installation (at 19% complete). A second popup appears, saying 'There was an error committing changes. Possibly there was a problem downloading some packages or the commit would break packages" I'll certainly reinstall from scratch when herd 5 comes out, but in the meantime, is there a magic dpkg incantation I can run from the command line to force the install without nice'ing it? -- dpkg: invalid nice value https://launchpad.net/bugs/88697 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 88697] dpkg: invalid nice value
Public bug reported: Binary package hint: adept after installing Kubuntu Herd 4 X86_64 on emachines M6810, I ran adept-updater by clicking on the quickstart notification icon next to the clock. It presented me with 200+ updates. Downloading them seemed to go quickly, but as they were being installed, I got a pop-up window with the message 'dpkg: Invalid nice value. Enter a value between -19 and +20' But there is no input box, only 'continue' and 'abort' buttons. 'Continue does nothing. 'abort' seems to abort the installation of all packages. I then launched adept from the menu, and selected the package build- essential. When I clicked on 'apply changes', it again downloaded them normally, and gave me the same 'invalid nice value' popup as it began to install them. ** Affects: adept (Ubuntu) Importance: Undecided Status: Unconfirmed -- dpkg: invalid nice value https://launchpad.net/bugs/88697 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88692] Touchpad not fully functional
Public bug reported: Binary package hint: xorg Feisty Herd 4 (X86_64) on emachines M6810. Synaptics touchpad only partially works. Cursor movement OK. single-tap sometimes works, but not on all buttons. Double-tap/drag does not work. Scroll area at right of touchpad not recognized as a scrollwheel, but simply moves cursor along verticle line. ** Affects: xorg (Ubuntu) Importance: Undecided Status: Unconfirmed -- Touchpad not fully functional https://launchpad.net/bugs/88692 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88691] Dim LCD backlight on boot
Public bug reported: Binary package hint: xorg Feisty Herd 4 on emachines M6810 (Radeon Mobility 9600). On boot, screen is very dark. I must use fn-F8 hotkey to raise backlight brightness in order to make screen usable. This is both in 'liveCD mode, and after installation to HD. ** Affects: xorg (Ubuntu) Importance: Undecided Status: Unconfirmed -- Dim LCD backlight on boot https://launchpad.net/bugs/88691 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
