[Bug 471627] Re: WARNING: at /build/buildd/linux-2.6.31/net/mac80211/scan.c:281 ieee80211_scan_completed+0xcf/0x3f0 [mac80211]()
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/34982511/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/34982512/AplayDevices.txt ** Attachment added: "ArecordDevices.txt" http://launchpadlibrarian.net/34982513/ArecordDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/34982514/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/34982515/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec.0.txt" http://launchpadlibrarian.net/34982516/Card0.Codecs.codec.0.txt ** Attachment added: "Card0.Codecs.codec.1.txt" http://launchpadlibrarian.net/34982518/Card0.Codecs.codec.1.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/34982519/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/34982522/Dependencies.txt ** Attachment added: "IwConfig.txt" http://launchpadlibrarian.net/34982523/IwConfig.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/34982524/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/34982525/Lsusb.txt ** Attachment added: "OopsText.txt" http://launchpadlibrarian.net/34982526/OopsText.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/34982527/PciMultimedia.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/34982528/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/34982529/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/34982531/ProcModules.txt ** Attachment added: "RfKill.txt" http://launchpadlibrarian.net/34982534/RfKill.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/34982535/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/34982537/UdevLog.txt ** Attachment added: "WifiSyslog.txt" http://launchpadlibrarian.net/34982539/WifiSyslog.txt -- WARNING: at /build/buildd/linux-2.6.31/net/mac80211/scan.c:281 ieee80211_scan_completed+0xcf/0x3f0 [mac80211]() https://bugs.launchpad.net/bugs/471627 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 471627] [NEW] WARNING: at /build/buildd/linux-2.6.31/net/mac80211/scan.c:281 ieee80211_scan_completed+0xcf/0x3f0 [mac80211]()
Public bug reported: i dont know... ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bili 1484 F pulseaudio CRDA: Error: [Errno 2] No existe el fichero รณ directorio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd240 irq 22' Mixer name : 'Realtek ALC883' Components : 'HDA:10ec0883,10250090,0012 HDA:14f12bfa,1025007f,0009' Controls : 24 Simple ctrls : 14 Date: Mon Nov 2 21:30:42 2009 DistroRelease: Ubuntu 9.10 Failure: oops HibernationDevice: RESUME=UUID=1ddf744d-ec24-4ef6-a95c-d7f39bc7c597 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) MachineType: Acer Aspire 5630 NonfreeKernelModules: nvidia Package: linux-image-2.6.31-14-generic 2.6.31-14.48 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=2b6c9fd8-7807-4590-b03a-b19341d19a67 ro quiet splash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic RelatedPackageVersions: linux-backports-modules-2.6.31-14-generic N/A linux-firmware 1.24 SourcePackage: linux Tags: kernel-oops Title: WARNING: at /build/buildd/linux-2.6.31/net/mac80211/scan.c:281 ieee80211_scan_completed+0xcf/0x3f0 [mac80211]() Uname: Linux 2.6.31-14-generic i686 dmi.bios.date: 02/13/2007 dmi.bios.vendor: Acer dmi.bios.version: V3.50 dmi.board.name: Grapevine dmi.board.vendor: Acer dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV3.50:bd02/13/2007:svnAcer:pnAspire5630:pvrV3.50:rvnAcer:rnGrapevine:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5630 dmi.product.version: V3.50 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 kernel-oops -- WARNING: at /build/buildd/linux-2.6.31/net/mac80211/scan.c:281 ieee80211_scan_completed+0xcf/0x3f0 [mac80211]() https://bugs.launchpad.net/bugs/471627 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 373932] Re: Ubuntu's partition manager is buggy.
** Summary changed: - Ubuntu's installer's partition manager is too ambiguous + Ubuntu's partition manager is buggy. ** Tags added: manager partition -- Ubuntu's partition manager is buggy. https://bugs.launchpad.net/bugs/373932 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 373932] Re: Ubuntu's installer's partition manager is too ambiguous
Original description missed the mark by a little. See second comment (by Bili Joe Campbell). The importance of this bug should be elivated, as it can really confuse people and cause them to screw up their installations. ** Package changed: ubiquity (Ubuntu) => gparted (Ubuntu) ** Changed in: gparted (Ubuntu) Status: Triaged => Confirmed -- Ubuntu's partition manager is buggy. https://bugs.launchpad.net/bugs/373932 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 373932] Re: Ubuntu's installer's partition manager is too ambiguous
When the partition manager first opens, some of the time (much of the time) the display just shows an empty device and reports no OS installed, even when there are partitions and an OS on that device. The display simply needs to be refreshed. A workaround (if you have more than one HDD) is to point the partition manager at another device, and then back to the one you want to see. When I do this, all the partitions show up correctly, and any existing OS on that device is recognized and correctly reported. -- Ubuntu's installer's partition manager is too ambiguous https://bugs.launchpad.net/bugs/373932 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 278888] Re: System has been getting slower and slower, over time
The problem is still there and has gotten a little worse. I created another user, and the problem does not exist under that login. That login also has a lot less complexity regarding plugins, themes, etc, so it may just be that I have the UI loaded down past the point of reason. I am planing on updating to the newest version soon though. I've been real busy lately though. I'll post when I do upgrade. Thanks for the follow-up, Bili -- Original message -- From: Dan Trevino > Thank you for taking the time to report this bug and helping to make > Ubuntu better. You reported this bug a while ago and there hasn't been > any activity in it recently. We were wondering if this is still an issue > for you. Can you try with the latest Ubuntu release? Thanks in advance. > > -- > System has been getting slower and slower, over time > https://bugs.launchpad.net/bugs/27 > You received this bug notification because you are a direct subscriber > of the bug. -- System has been getting slower and slower, over time https://bugs.launchpad.net/bugs/27 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 278888] [NEW] System has been getting slower and slower, over time
Public bug reported: Ubuntu 8.04.1: DELL Optiplex GX 270, 2.8GHz Hyperthreading Pentium 4, 4GB RAM. Over the past several months, my system has been progressively slowing down, taking longer and longer to launch programs, open windows, etc. At first it was so slight I thought I was imagining it, but as time progressed, it became obvious that things were, indeed, slowing down. The most noticeable (and annoying) aspect is that scrolling through a large document, a long web page, or a file browser window with enough entries to be several pages long, the scroll speed sometimes slows to a crawl--sometimes even stopping altogether, for a second or two. When the slow-down is more than just a little bit, the window that is scrolling turns Black and White. Sometimes, it takes so long to scroll from one end of the window to the other, I have time to launch other programs, open other file browser windows, etc., to see how quickly they respond. Often, they respond normally, but sometimes it takes significantly longer than normal to get a response. I recently checked both the System Monitor, and top, to see what processes were using up all the time. The system monitor shows 2 CPUs for the Hyperthreading processor, and both showed a steady 100% usage. The top four processes appeared to be using all the CPU cycles. These were Nautilus, FireFox (running Pandora Radio), totem, and gnome panel. They exchanged positions often, but were consistently the top four, and all show between 25% and 85% processor use (it varies for each one, over time). Everything else in the list shows 0% processor use--most show "sleeping". Sometimes top showed Nautilus using more than 100% of the CPU (top apparently sees only one CPU, or has no way of displaying more than one). A few days ago, I experienced the impossible. The system had been running quite slowly--launching programs, and opening file browser windows happened much slower than normal. I clicked on a thumbnail for a picture file, and the response seemed unusually slow. In fact, after 20 seconds or so, I decided the system must not have registered the click, so I clicked again. Nothing. I figured the window must have locked up (there were 540+ thumbnails in it), so I tried to close it. No response. After a few minutes, I realized that I was looking at a totally frozen Linux system (OMG, what will I tell my Windows using friends?). It was so frozen up, it wouldn't even respond to the power button to initiate a controlled shutdown. So I held the power button down, until the computer itself did an abrupt shutdown. I held my breath (because I thought I had just lost hours of work) and restarted the machine. Well, for a die hard, sopabox preachin Linux fan such as my self, having Linux freeze up on me was traumatic enough, but... when the system restarted, it returned to EXACTLY the state it had been when it froze (except it was not frozen). I had MS WORD running under CrossOver, and it came up with the same 3 documents opened, and the cursor on the exact letter it had been on, in all three documents, 3 FireFox Internet browser windows with several tabs each opened, returned to the exact sites, pages, and positions they had been on, right down to the cursors being right where they were, and the Thumbnail I had clicked on that set of the freeze was highlighted, with the cursor positioned over it, and after about a second, the picture opened. Oh, and Pandora Radio even started back up. So the freeze up was very disconcerting, but the unattended recovery of the state of the system, with zero data loss or corruption, was mind- bogglingly impressive. BUT, the problem of the system often (but not always) being so sluggish, is annoying, and is all too reminiscent of the old Windows problem of the Registry getting overcrowded and corrupted, causing the system to slow down. But Linux doesn't do that! Anyway, I really hope I don't have to resort to the old Windows trick in desperation of wiping the hard drive clean, and starting all over with a fresh install, in order to get this machine to be responsive again. I don't have a machine with a 2.8GHz, Hyperthreading processor in it, because I want mediocre performance. And I don't exclusively run Linux because I want weird system problems. So, I hope a fix can be found for this soon, as I can't put up with it much longer--especially because it continues to get worse. I don't hold out much hope though, for anyone being able to duplicate this bug, as it has taken nearly four months for it to get this bad. I can't say whether the progressive slow-down started as soon as the system was installed, or whether it ran normally for a time, because, at first, it was so subtle I wasn't sure it was real, or my imagination. Also, none of my 3 other Ubuntu 8.04.1 machines are doing this. They have been running 8.04.1 for as long as this machine, but don't get nearly as much use. I wish I could give more helpful information, but, at
[Bug 250718] Re: FireFox Downloads window "Clean" button causes bizare behaviour
** Description changed: Binary package hint: firefox With a rather long list of downloads (may not be relevant), clicking the "clean" button caused close buttons on Firefox main window, and download window to fail to respond. Processor (one of two processors shown in system monitor for a Pentium 4 in hyperthreading mode) was driven to 100% and stayed there. If the download window, or a console window, or the system monitor window was moved, it left behind thousands of copies (like a deck of cards, fanned out), and drove the other processor to 100% (fell back to a lower value when stopped moving window. Had to use "Force Misbehaving Application to Quit" feature to close downloads window--FireFox's main window disappeared at the same time, but FireFox continued to run (on trying to open FireFox, got the message that session was already running and must be stopped before opening another. Used "top" to get pid for FireFox and then used "kill" shell command to end the invisible FireFox session. System then appeared to return to normal operation. After going through this cycle several times, when I opened the Downloads window, it was empty, and no longer seemed to cause strange behavior. Using Ubuntu 7.10, FireFox version 2.0.0.16 Note: Entire system seems to have been running slower lately. Not by much, but I don't think it's just my imagination. I would like to provide more information, as per your document "DebuggingProcedures", but since the Downloads window is now empty (i.e., at some point, the "clean" function did work), I can no longer reproduce the bug. If it occurs again, I'll try to supply additional - information + information. + + ADDENDUM: I have now had this situation occur three times, since I originally submitted this report. The first time, after the re-login screen, I was taken to the preview of my pending post. No problem--should happen every time. The second time, I received the following error message: "Your request could not be processed because a security token was missing or mismatched. If this occurred unexpectedly, please inform the administrator and describe the action you performed before you received this error." The third time, I received an error message I had not seen before, which read: "vBulletin Message + Your submission could not be processed because you have logged in since the previous page was loaded. + Please push the back button and reload the previous window." + I hope this additional information helps. ProblemType: Bug Architecture: i386 Date: Mon Jul 21 23:37:04 2008 DistroRelease: Ubuntu 7.10 Package: firefox 2.0.0.16+1nobinonly-0ubuntu0.7.10 PackageArchitecture: i386 SourcePackage: firefox Uname: Linux Lauren 2.6.22-15-generic #1 SMP Fri Jul 11 19:25:33 UTC 2008 i686 GNU/Linux -- FireFox Downloads window "Clean" button causes bizare behaviour https://bugs.launchpad.net/bugs/250718 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 250718] Re: FireFox Downloads window "Clean" button causes bizare behaviour
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/16227282/Dependencies.txt ** Attachment added: "ExtensionSummary.txt" http://launchpadlibrarian.net/16227283/ExtensionSummary.txt ** Attachment added: "pluginreg.dat.txt" http://launchpadlibrarian.net/16227284/pluginreg.dat.txt ** Attachment added: "profiles.ini.txt" http://launchpadlibrarian.net/16227285/profiles.ini.txt -- FireFox Downloads window "Clean" button causes bizare behaviour https://bugs.launchpad.net/bugs/250718 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 250718] [NEW] FireFox Downloads window "Clean" button causes bizare behaviour
Public bug reported: Binary package hint: firefox With a rather long list of downloads (may not be relevant), clicking the "clean" button caused close buttons on Firefox main window, and download window to fail to respond. Processor (one of two processors shown in system monitor for a Pentium 4 in hyperthreading mode) was driven to 100% and stayed there. If the download window, or a console window, or the system monitor window was moved, it left behind thousands of copies (like a deck of cards, fanned out), and drove the other processor to 100% (fell back to a lower value when stopped moving window. Had to use "Force Misbehaving Application to Quit" feature to close downloads window--FireFox's main window disappeared at the same time, but FireFox continued to run (on trying to open FireFox, got the message that session was already running and must be stopped before opening another. Used "top" to get pid for FireFox and then used "kill" shell command to end the invisible FireFox session. System then appeared to return to normal operation. After going through this cycle several times, when I opened the Downloads window, it was empty, and no longer seemed to cause strange behavior. Using Ubuntu 7.10, FireFox version 2.0.0.16 Note: Entire system seems to have been running slower lately. Not by much, but I don't think it's just my imagination. I would like to provide more information, as per your document "DebuggingProcedures", but since the Downloads window is now empty (i.e., at some point, the "clean" function did work), I can no longer reproduce the bug. If it occurs again, I'll try to supply additional information ProblemType: Bug Architecture: i386 Date: Mon Jul 21 23:37:04 2008 DistroRelease: Ubuntu 7.10 Package: firefox 2.0.0.16+1nobinonly-0ubuntu0.7.10 PackageArchitecture: i386 SourcePackage: firefox Uname: Linux Lauren 2.6.22-15-generic #1 SMP Fri Jul 11 19:25:33 UTC 2008 i686 GNU/Linux ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- FireFox Downloads window "Clean" button causes bizare behaviour https://bugs.launchpad.net/bugs/250718 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 224854] Re: _usr_sbin_firestarter.0.crash
** Attachment added: "_usr_sbin_firestarter.0.crash" http://launchpadlibrarian.net/14050105/_usr_sbin_firestarter.0.crash -- _usr_sbin_firestarter.0.crash https://bugs.launchpad.net/bugs/224854 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 224854] [NEW] _usr_sbin_firestarter.0.crash
Public bug reported:
Binary package hint: firestarter
Recently upgraded Ubuntu 7.10 to 8.04. On first boot, could not execute
"sudo" commands ("Unable to resolve host "casi""). Also could not
access Synaptic from menu. Second boot produced a flurry of 7 "Crash
detected" reports, each opening a tab in Firefox on Launchpad. Each tab
required that I log in, but, after the first tab I was already logged
in. Subsequent tabs would not let me proceed without logging in, and
when I did, all the bug report information was wiped off the page to
display "You are already logged in", so all but one bug report was lost.
The third boot rendered the system unusable (wouldn't finish booting
because it could not locate the root filesystem, though the error
message gave the correct UUID for my HDD. In any case, through some
trickery, I have recovered much of the crash information for the
remaining bugs. The report for this one is attached (as a text file).
I hope this helps some.
Sincerely,
Bili Joe
** Affects: firestarter (Ubuntu)
Importance: Undecided
Status: New
--
_usr_sbin_firestarter.0.crash
https://bugs.launchpad.net/bugs/224854
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 150465] Re: file-roller crashed with SIGSEGV
I had recently upgraded from Ubuntu 7.10 to 8.04. There must have been some transmission errors in the data coming off the Internet during the update, as I ended up with a very buggy system. I restored my original system, from a tar archive, on top of the 8.04 installation (may not have been a good idea?). On first boot, I discovered that I could not "sudo" (unable to resolve host "casi", was the message, as best I can remember), and I was unable to access certain things from the menu--most n otably the Synaptic update manager. On second boot, I received a flurry of "crash detected" messages that came in so fast I was unable to deal with them. The first one opened Firefox on a Launchpad page--the successive ones opened additional Launchpad pages. The top page (last crash report) required me to sign in, which I did, then proceeded to fill in the requested information. When I went to the next page, it too blocked me from doing anything, until I logged in, but when I tried to log in, it wiped the page clean and posted the notice that I was already logged in, so the information for the bug report was lost. All the other pages did the same thing, so only one bug got reported. The next boot resulted in the system hanging, during boot up. The message was that the root drive could not be found. It posted the correct UUID for my HDD, but then said it didn't exist, and dropped me into a shell. I read through the script files, and found where the message was coming from, but was unable to determine the source of the failure. Since then, I have tricked the system into working--sort of--and have recovered some of the information the system had created for the crash reports. The info related to this particular crash follows: ProblemType: Crash Architecture: i386 Date: Fri Apr 25 01:24:40 2008 DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/bin/file-roller NonfreeKernelModules: cdrom ProcCmdline: file-roller file:///home/bili/Documents/BitTorrent%20meta%20files/BitTorrent%20seed%20files/HOT%20DRUNK%20BITCHES%20-%20Fucking%20at%20a%20Sex%20Orgy%20Party%20-%20Cute%20Girls%20Fucking%20Till%20They%20CUMMM!!/HOT%20DRUNK%20BITCHES%20-%20Fucking%20at%20a%20Sex%20Orgy%20Party%20-%20Cute%20Girls%20Fucking%20Till%20They%20CUMMM!!.rar ProcCwd: /home/bili ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_CA.UTF-8 SHELL=/bin/bash Package: file-roller 2.20.0-0ubuntu1 PackageArchitecture: i386 Registers: eax0x0 0 ecx0x0 0 edx0x1 1 ebx0x8107868 135297128 esp0xbfb16780 0xbfb16780 ebp0xbfb167b8 0xbfb167b8 esi0x846e7e0 138864608 edi0x -1 eip0x80760a7 0x80760a7 <[EMAIL PROTECTED]> eflags 0x10246 [ PF ZF IF RF ] cs 0x73115 ss 0x7b123 ds 0x7b123 es 0x7b123 fs 0x0 0 gs 0x3351 SourcePackage: file-roller Stacktrace: #0 0x080760a7 in ?? () #1 0x080ba890 in ?? () #2 0x0010 in ?? () #3 0x in ?? () StacktraceTop: ?? () ?? () ?? () ?? () ThreadStacktrace: . Thread 1 (process 8070): #0 0x080760a7 in ?? () #1 0x080ba890 in ?? () #2 0x0010 in ?? () #3 0x in ?? () Title: file-roller crashed with SIGSEGV -- file-roller crashed with SIGSEGV https://bugs.launchpad.net/bugs/150465 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 223515] Re: Cannot "sudo".
Thanks! As soon as I can get back on the machine, I'll try that. Right now, I get dumped to a shell, in the middle of the boot process, because the system can't make contact with the root filesystem. The error message shows the correct UUID for the drive, but then says it doesn't exist. I think I may have to resort to the old Windows (yechk) method of Blast'n'Build here, and just start over. But I do appreciate your advice and, if I get back on before I resort to BnB, I'll check out the hosts file--or if I have similar trouble after a rebuild. Thanks again for your time, Bili Joe -- Original message -- From: trollord <[EMAIL PROTECTED]> > Just check that your /etc/hosts looks like > 127.0.0.1 localhost > 127.0.1.1 Casi > and your /etc/hostname looks like > Casi > > and you should be aok. > > > ** Changed in: upgrade-system (Ubuntu) > Sourcepackagename: None => upgrade-system > > -- > Cannot "sudo". > https://bugs.launchpad.net/bugs/223515 > You received this bug notification because you are a direct subscriber > of the bug. -- Cannot "sudo". https://bugs.launchpad.net/bugs/223515 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 223495] Re: pstops crashed with SIGSEGV
Unfortunately, I cannot give you this additional information. I wish I could, but, after a couple more glitchy reboots, the system is now completely dead. It seems it can no longer find the root file system. It reports a correct UUID, but then says it doesn't exist. I waded through the script files, and found where the message was coming from, but it used a #DEFINE for the name/UUID of the filesystem, and I couldn't find where the value was assigned to that variable. It dumps me into a shell (one I am not familiar with), and I am tired of fudging around trying to get a system I already know is fraught with problems to start--it wasn't really usable anyway. My plan now is to install a clean copy of 7.10, and then restore my backup over that. It was when I tried to restore the backup over the messed up 8.04 that things really went South. I got a message that there were upgrades available (after the "restore"); there were 664 of them. I let them install, but several gave me t he message I couldn't "upgrade" from 8.04 to 7.10. For an install on another machine, I downloaded the ISO file (for 8.04), but came up with a bad MD5 check. A second try got me a clean download, and resulted in a clean disk, and [apparently] a clean install (this one is the 64 bit version, the other was the i386 version). So, I am guessing that, if I got a glitched download of the ISO file, I very well might have gotten a glitched download of something during the upgrade. So, I'm going to try to get back to where I started, and try the whole thing again. If I have any problems the second time, I'll take more complete notes, and try to get you better information to work with. For now, I'm going to blame it on corrupted data coming in from the internet, during the upgrade. Thanks for your help, and let me know if there is anything more I can do for you. Sincerely, Bili Joe -- Original message -- From: Martin Pitt <[EMAIL PROTECTED]> > To walk through the crash reports one by one it should be enough to > open /var/crash/ in the file browser and click on the ones you want to > report (the ones which happened as your user, at least). However, apport > is not supposed to report all at the same time (it doesn't do that > here), so I wonder what's wrong on your system. > > What is the output of > > ls -l /var/crash > > ? What happens if you do > > sudo touch /var/crash/* > > ? You should get notifications about the crashes, with an offer to > submit them (they shouldn't open firefox tabs straight away). > > -- > pstops crashed with SIGSEGV > https://bugs.launchpad.net/bugs/223495 > You received this bug notification because you are a direct subscriber > of the bug. -- pstops crashed with SIGSEGV https://bugs.launchpad.net/bugs/223495 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 223515] Re: Cannot "sudo".
I added the information you requested to the bug report. Hope it helps. Bili -- Original message -- From: Jeroen Tietema <[EMAIL PROTECTED]> > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Unfortunately we can't fix it, because your description > didn't include enough information. You may find it helpful to read "How > to report bugs effectively" [WWW] > http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful > if you would then provide a more complete description of the problem. > > We have instructions on debugging some types of problems at [WWW] > http://wiki.ubuntu.com/DebuggingProcedures > > At a minimum, we need: > 1. the specific steps or actions you took that caused you to encounter the > problem, > 2. the behavior you expected, and > 3. the behavior you actually encountered (in as much detail as possible). > Thanks! > > ** Changed in: ubuntu >Status: New => Incomplete > > -- > Cannot "sudo". > https://bugs.launchpad.net/bugs/223515 > You received this bug notification because you are a direct subscriber > of the bug. -- Cannot "sudo". https://bugs.launchpad.net/bugs/223515 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 223515] Re: Cannot "sudo".
Relevant information: The following occurred immediately after upgrading my Ubuntu 7.10 to Ubuntu 8.04, both Desktop-i386 versions. I am running a DELL Optiplex GX270, with a 2.8 GHz Dual core Pentium-4, 3/4 of a Gig of RAM, and a 40Gb hard disk. The system had been performing flawlessly, ever since I replaced Windows XP with Ubuntu 7.10, six months or so ago. Item A: 1) I went to the menu, System/Administration, and clicked on "Synaptic Package Manager". 2) I expected the result I have always gotten, which is, a brief pause, followed by the Synaptic Package Manager window opening. 3) The result I got... the cursor changed to the little whirly thing for a second or two, then returned to its normal appearance. The window did not open. Repeated tries resulted in the same scenario. Therefore, no access to Synaptic through the menu. Item B: 1) I entered the following at the prompt in a terminal window: CODE: - sudo gedit /boot/grub/menu.lst - 2) I expected, as has always happened in the past, to be asked for my password and, after supplying it, for a "gedit" window to open on the /boot/grub/menu.lst file. 3) What I got instead was the following: QUOTE: -- [EMAIL PROTECTED]:~$ sudo gedit /boot/grub/menu.lst sudo: unable to resolve host Casi [EMAIL PROTECTED]:~$ _ -- Hope this helps. I have ADD and tend to be a bit wordy. Sorry. -- Cannot "sudo". https://bugs.launchpad.net/bugs/223515 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 223495] Re: pstops crashed with SIGSEGV
I added some information to my report, and attached a list of possible "culprit" files. Please look there for the info. Thanks. BiliJoe -- Original message -- From: Till Kamppeter <[EMAIL PROTECTED]> > Can you post the file which you have sent to the printer so that pstops > crashed? pstops is a print filter and so it only gets executed when > something is sent to the printer. > > > ** Changed in: cupsys (Ubuntu) >Status: New => Incomplete > > -- > pstops crashed with SIGSEGV > https://bugs.launchpad.net/bugs/223495 > You received this bug notification because you are a direct subscriber > of the bug. -- pstops crashed with SIGSEGV https://bugs.launchpad.net/bugs/223495 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 223495] Re: pstops crashed with SIGSEGV
First off, this was under a fresh upgrade to 8.04, NOT 7.10. As far as the printer is concerned, I don't think "I" was sending anything to the printer, but the system issued a flurry of crash reports--so fast they piled up and I couldn't respond to them all and even lost track of which notification window went with which crash report. It also opened Firefox, and opened the Launchpad sign in window for each crash, in rapid succession. Two bug reports got lost, because, after I signed in and dealt with the topmost one (I assume the last one), the other screens wouldn't let me do anything until I logged in--but I was already logged in, so when I tried to log in again (which was the only thing it would let me do), it posted a notice that I was already logged in, which overwrote the bug report information that had been on the screen, and the "back" button just took me back to the sign in screen. So, like I said, two bug reports got lost in the scramble. I've never seen such a flurry of crash reports before. There must have been five of them inside ten seconds or less. I simply got overwhelmed and lost track. Sorry. in my panic, I may have tried to capture the reports that were being overwritten, by trying to print them--I don't remember. And there is no unaccounted for pages from my printer, so, if I did try to print, nothing got printed. Actually, at that point, I don't think my printer was available--I think the only option was to print to a PDF file. Attached is a list of the PDF files currently on my system. I'm pretty sure I didn't [intentionally] create any of them, so any that are not a "normal" part of the system or some software package, may be what triggered the "print" activity. I wish I could offer you more information, but I simply got caught off guard by all the crashes on the first boot of an upgraded system. I have multiple problems now, but I don't think any of them is related to printing. I just printed a test document, and it went OK, except now, I get a very different window when I select "print". Besides listing my printer, it lists "Print to File" (which is the default), PDF, and then the printer. When I select the printer, almost all the options (like "print selection", "Print range of pages", Printer Setup", etc., are grayed out. I seem to only have the option to print the entire file, with the default settings. I hope some of this helps. I'm fried, and may go back to 7.10, if I can't get things working right today. ** Attachment added: "PDF_files.txt" http://launchpadlibrarian.net/13996109/PDF_files.txt -- pstops crashed with SIGSEGV https://bugs.launchpad.net/bugs/223495 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 223515] [NEW] Cannot "sudo".
Public bug reported: After upgrading from 7.10 to 8.04, I cannot access Synaptic from the menu, and I cannot execute any "sudo" anything from a terminal window. I get the message "sudo: unable to resolve host Casi". Casi is, and has always been this computer's name. I had to log in as root, in order to change my /boot/grub/menu.lst file, so I could see the messages generated at boot-up. They went by too fast to read, but one that mentioned starting some service had a big red "[FAILED]" following it. This is ugly; this is the fourth, major, show stopping bug I have encountered in the hour since I did the upgrade. I'll wait till tomorrow, (and use my Windows machine (ugh)) to scan the forums, and check for updates and fixes, but if it doesn't look very rosy tomorrow morning, I'm going to roll back to the backuped version of 7.10, which was running flawlessly, before the upgrade. Please fix these problems SOON, or I'm going to end up with egg on my face, in front of my friends who are [still] staunch supporters of Windows. I don't want to have to admit to them that I wasted a day and a half upgrading, and then rolling back a Linux installation. ** Affects: ubuntu Importance: Undecided Status: New -- Cannot "sudo". https://bugs.launchpad.net/bugs/223515 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 223495] Re: pstops crashed with SIGSEGV
** Attachment added: "CoreDump.gz" http://launchpadlibrarian.net/13979151/CoreDump.gz ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/13979152/Dependencies.txt ** Attachment added: "Disassembly.txt" http://launchpadlibrarian.net/13979153/Disassembly.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/13979154/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/13979155/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/13979156/Registers.txt ** Visibility changed to: Public -- pstops crashed with SIGSEGV https://bugs.launchpad.net/bugs/223495 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 223495] [NEW] pstops crashed with SIGSEGV
Public bug reported: Binary package hint: cupsys I don't know if this is a new bug or not. Three messages popped up so fast I didn't have time to read them, then Firefox opened up three launchpad sessions, all asking me to log in. I logged into this one, but when I went to the other tabs and tried to log in, it told me that I was already logged in and erased all the information about the crashes it had just reported. All I know is I just upgraded from 7.10 to 8.04 and now every time I log in I get pummeled with crash reports, and I can't "sudo" any more, so I am now logged in as root, in order to get access to synaptec so I can re-install "locate" so I can find my menu.lst file, so I can modify it so I can see what the is going on during boot up (I'm sure I have its location in my notes, but I still want "locate", which I used to have). I'm about ten minutes away from hosing this installation, and restoring from the backup I am SOOO glad I made, before I started this upgrade. What in the Blue Blazes is happening? I thought this was a post-beta, release-ready version. I thought it was only Microsoft that was cruel enough to make their users finish Beta testing for them. PLEASE GET THIS FIXED!!! [EMAIL PROTECTED] ProblemType: Crash Architecture: i386 Date: Sun Apr 27 16:45:24 2008 DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/lib/cups/filter/pstops NonfreeKernelModules: cdrom Package: cupsys 1.3.7-1ubuntu3 PackageArchitecture: i386 ProcCmdline: Photosmart_3200 131 bili Upgrading\ your\ existing\ Ubuntu\ installation\ |\ Ubuntu 1 media=Letter\ sides=one-sided\ finishings=3\ number-up=1\ outputorder=reverse\ PrintoutMode=Draft\ job-uuid=urn:uuid:ab80f992-7805-37bc-6aac-78bab8091f6e /var/spool/cups/d00131-001 ProcCwd: / ProcEnviron: PATH=/usr/lib/cups/filter:/usr/bin:/usr/sbin:/bin:/usr/bin LANG=en_CA Signal: 11 SourcePackage: cupsys Stacktrace: #0 0x0804dc6f in ?? () #1 0x in ?? () StacktraceTop: ?? () ?? () ThreadStacktrace: Title: pstops crashed with SIGSEGV Uname: Linux Casi 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux UserGroups: ** Affects: cupsys (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash need-i386-retrace -- pstops crashed with SIGSEGV https://bugs.launchpad.net/bugs/223495 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 211150] [NEW] Kill Application button leaves message box on screen forever.
Public bug reported: When FireFox (with 26 tabs open) appeared to hang up trying to close, I pressed the "Force a misbehaving application to quit" button. A message box appeared on the screen with the button's icon, and the message "Click on a window to force the application to quit. To cancel press ." FireFox was running full screen, so I just clicked somewhere on the screen. Nothing happened. After quite some time, the FireFox window turned all white, but the window title text and the message box remained. After another long pause, the FireFox window finally closed, but the message box remained. I tried pressing , but it did not clear the box. The message box remained on the screen, staying on top of everything else. It is still there now, on top of this report screen. I assume I am going to have to restart Ubuntu, in order to get it to go away. I've tried everything else I can think of. Even if I switch to "Desk 2" the message box stays put, ending up in the middle of the second desktop display. Not critical, but could be a real pain, if you were in the middle of something where rebooting would be inconvenient, and the message box was obscuring your view of what you were doing. I hope this is an easy one to fix. I am running release 7.10. I don't know which package I was using; FireFox was the only application that was running, but the "kill application" function is not part of FireFox--I was trying to use it to force FireFox to quit. I notice that if I click the button now, the cursor turns to a cross hair --that did not happen when I clicked the button while Fire Fox was [apparently] hung. The message box appeared, but the cursor remained an arrow. This text is about to go behind the message window, so I won't be able to see what I type, so I am going to end this report. I think I have given you all the information I can anyway. I will play around some, to see if I can duplicate the bug, and possibly identify which package is involved. ** Affects: ubuntu Importance: Undecided Status: New -- Kill Application button leaves message box on screen forever. https://bugs.launchpad.net/bugs/211150 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
