RE: [Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with " Cannotallocate memory"
My solution was simple, Javier: I'm a Windows tech support geek and I'm making the switch for a lot of reasons but I have to admit I dont know Linux like I know Window$ - not yet anyway. Like you, I don't have the time or the experience to chase down the problem or do file surgery on an operating system that's new to me. So I resorted to the nuclear fix - wipe the drive and reinstall. I had the relevant data backed up but it's just as easy to boot with a Knoppix CD against the broken machine and back up the data that way. Once that was done, I reinstalled from the installation CD right over the original partitions. The install works just fine, it's the upgrade that's crashing on us. This was true for my upgrade to 7.04 and again to 7.10. It worked, of course, but it costs time to reconfigure and restore the backed up data. Next time, maybe, I'll be ready to chase down the answers but this is an old bug - more than a year old - and it's affected at least two upgrades to date, so, I figure the developers are either totally stumped or up to their collective eyeballs in a sea of more important issues. Something else you wrote caught my attention, though, <> It's not like Linux folk to sit around on their collective butts. I've looked around and, for a n00by like myself, Ubuntu is easier to maintain and I figure it's a good place to learn as well. Speaker2Software ___ Code & Data: Making Excel Dance since 1994. Software Support & Data Services (ETL) VBA, COBOL, Documentation & Training * P.O. Box 302287; Austin, Texas 78703-2287 ___ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Javier Arántegui Sent: Friday, November 02, 2007 7:12 AM To: [EMAIL PROTECTED] Subject: [Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with " Cannotallocate memory" Hi! How are the things going? I'm not a developer and am unable to apply the simplest patch :-( It's a little bit frustating to be in no men's land. Now my distro is in the middle of the update process so neither I don't get the updates of Kubuntu 7.04 nor I can upgrade :-( Should I wait until the problem is solved or should I look for greener pastures? Javier -- [Snipped, thank you... Now, me want more cookie...] -- [MASTER] [kde] Upgrade tool crashed with " Cannot allocate memory" https://bugs.launchpad.net/bugs/107188 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 113378] Re: [apport] kdeinit crashed with SIGSEGV
** Attachment added: "CoreDump.gz" http://librarian.launchpad.net/7584802/CoreDump.gz ** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/7584803/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/7584804/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/7584805/ProcStatus.txt ** Attachment added: "Registers.txt" http://librarian.launchpad.net/7584806/Registers.txt -- [apport] kdeinit crashed with SIGSEGV https://bugs.launchpad.net/bugs/113378 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdelibs in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 113378] [apport] kdeinit crashed with SIGSEGV
Public bug reported: Binary package hint: kdelibs This is the 2nd Normal startup after a failed upgrade attempt Edgy --> Feisty KDE. Previous startup also caused a KDEInit crash with SIGSEGV. One difference here is that the mouse may be malfunctioning. Previous WinXP boots of this machine have twice showed the left mouse button inop or intermittnet. Reboot of another machine using this mouse via KVM switch also showed inop or intermittent operation. I note that Kontact requires 1-2 left mouse clicks to activate buttons or select objects. right mouse button often works as left button but this may be programming rather than a cross-function error. DJ Brown [EMAIL PROTECTED] Austin, TX ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Tue May 1 10:08:26 2007 Disassembly: 0xb7ce5a25: DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/kdeinit Package: kdelibs4c2a 4:3.5.6-0ubuntu14 PackageArchitecture: i386 ProcCmdline: kdesktop\ [kdeinit] ProcCwd: /home/oldman ProcEnviron: Signal: 11 SourcePackage: kdelibs Stacktrace: #0 0xb7ce5a25 in ?? () StacktraceTop: ?? () ThreadStacktrace: Uname: Linux Beast 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video ** Affects: kdelibs (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] kdeinit crashed with SIGSEGV https://bugs.launchpad.net/bugs/113378 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdelibs in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 111247] Re: [apport] kdeinit crashed with SIGSEGV
** Attachment added: "CoreDump.gz" http://librarian.launchpad.net/7480742/CoreDump.gz ** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/7480743/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/7480744/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/7480745/ProcStatus.txt ** Attachment added: "Registers.txt" http://librarian.launchpad.net/7480746/Registers.txt -- [apport] kdeinit crashed with SIGSEGV https://bugs.launchpad.net/bugs/111247 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 111247] [apport] kdeinit crashed with SIGSEGV
Public bug reported: Binary package hint: kdelibs Action occurred at startup. No apparent problems or strange displays noted. This is a recently upgraded Edgy 2 Feisty upgrade where the KDE Upgrade tool crashed. Reference Bug 108396 related to [MASTER 107188]. No further action has been taken with this boot/partition in case the techs at Canonical wanted another look under the bonnet. Today's startup was due to user not present while Grub cycled through its boot options. (KDE is default boot) The KDE reminder utility actually let me open a reminder for edit. This is the first time that has happened. The app usually ignores my button input or crashes at that point. No other problems apparent with KDE or Linux so far. Security vulnerability:= Unknown DJ Brown [EMAIL PROTECTED] Austin, TX ProblemType: Crash Architecture: i386 Date: Sun Apr 22 18:52:47 2007 Disassembly: 0xb7d59a16: DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/kdeinit Package: kdelibs4c2a 4:3.5.6-0ubuntu14 PackageArchitecture: i386 ProcCmdline: kdesktop\ [kdeinit] ProcCwd: /home/oldman ProcEnviron: Signal: 11 SourcePackage: kdelibs Stacktrace: #0 0xb7d59a16 in ?? () StacktraceTop: ?? () ThreadStacktrace: Uname: Linux Beast 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video ** Affects: kdelibs (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] kdeinit crashed with SIGSEGV https://bugs.launchpad.net/bugs/111247 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdelibs in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
RE: [Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed (edgy -> feisty)
Hello Tzvetan: <> I'd try the "apt dist-upgrade" command as well. Who knows *what* will work at this stage? Sadly, you risk one more machine if it fails again. In most other respects, the KDE upgrade on the main computer is perfect except for the upgrade crash. Wonder what steps I (we) missed after the crash? ...and can the upgrade tool be re-started to finish the job or can we replicate the missed steps manually? DJ Brown Austin, TX In the meantime... The format and re-install of Gnome on my other machine went famously though I'm puzzled. The upgrade tool found my LAN, the Internet, an existing install of Win2K, got the Grub setup correct and yet failed to install Samba?!?!? That feels more like a design choice rather than program failure, though. -Today's Mantra- It is by Caffeine alone I set my mind in motion, It is by the beans of Java, that my thoughts acquire speed, My hands acquire shaking; the shaking becomes a warning, It is by Caffeine alone I set my mind in motion... ~~The Mentat's Mantra (Shamelessly adapted) from the Dune series, Frank Herbert -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tzvetan Mikov Sent: Thursday, April 26, 2007 1:00 PM To: [EMAIL PROTECTED] Subject: [Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed (edgy -> feisty) [Snipped... More bandwidth for the botnets ] -- [MASTER] [kde] Upgrade tool crashed (edgy -> feisty) https://bugs.launchpad.net/bugs/107188 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 107188] Re: [MASTER] [kde] Upgrade tool crashed (edgy -> feisty)
Agreed Madamos: I don't exactly trust it yet but KDE seems to come up normally and run just fine except for a few missing items - things that ran fine in the previous install but are missing now. I'll have to do a bit of an inventory but I can come up with a list. Alas, there are a couple of problems that continue: one is the Adept (?) program installer that dumps mysteriously when I check the two boxes at the upper right looking for all the available application downloads. It takes a few seconds but the window just pops away with no warning or crash report. Still, I'm in the enviable position of being able to leave the machine in its original failed condition in case any of the Ubuntu diagnostic staff want to pick it apart. DJ Brown Austin, TX -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of madamos Sent: Wednesday, April 25, 2007 8:19 AM To: [EMAIL PROTECTED] Subject: [Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed (edgy -> feisty) After a restart things appear to be functioning normally for me. [Snipped] Good stuff! -- [MASTER] [kde] Upgrade tool crashed (edgy -> feisty) https://bugs.launchpad.net/bugs/107188 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 108011] Re: Kubuntu 7.04 Upgrade Tool Crashed
*** This bug is a duplicate of bug 107188 *** https://bugs.launchpad.net/bugs/107188 Hello Pasqual: <> Good question! I'd go with Richard's reply if you want to get up and running. Of course, that implies you have nothing to lose by formatting the Edgy partition and starting over. Richard suggests: <> On the other hand, if yours is a production mahcine, it might be wise to start recovering what data you can before attempting the upgrade/rebuild again. So far, I've been able to restart the botched upgrade and the archive tools seem to work. I even see some of the KDE upgrades/features as well. I just don't trust it any further than I can throw the hardware... Yet! ME? I'm in the enviable position of being available to research this problem but I've no clue as to how to proceed. This is the time when I could use a call from the Tech Support & Research folks. They'd get some decent data and I'd get the Noobie training opportunity of a lifetime. DJ Brown Austin, TX -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pasqual Auer Sent: Saturday, April 21, 2007 7:34 AM To: [EMAIL PROTECTED] Subject: [Bug 108011] Re: Kubuntu 7.04 Upgrade Tool Crashed [Snipped] -- Kubuntu 7.04 Upgrade Tool Crashed https://bugs.launchpad.net/bugs/108011 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 108396] Re: Upgrader Crashed on Upgrade Edgy --> Feisty
<> Have been at a retreat over the weekend - unable to work on the upgrade failure. I have the enviable option to just format the partition and install Feisty via a downloaded ISO image. My current Linux setup is not (yet) a production machine and has no data that can't be recovered. Question: Is there something I can do to help chase this problem down or attempt a recovery from the present situation? Again, since it's not production, I can also delay the upgrade to research other problems. DJ Brown Austin, TX -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Kitterman Sent: Saturday, April 21, 2007 10:24 AM To: [EMAIL PROTECTED] Subject: [Bug 108396] Re: Upgrader Crashed on Upgrade Edgy --> Feisty [snipped - ] -- Upgrader Crashed on Upgrade Edgy --> Feisty https://bugs.launchpad.net/bugs/108396 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 107188] Re: [MASTER] [kde] Upgrade tool crashed (edgy -> feisty)
Hello Michael: <> Unlikely. The chance that we are all using the same theme is vanishingly small... unless we're all using the default KDE theme. I *was* using the default theme, though I tried several on when exploring those options. I also made a few minor tweaks (that I understood, being a noob) and posted the V.I.S.T.A. wall paper. Other than that, it was pretty much default KDE. According to another message I received this morning, there were instructions to (manually?) install 2 upgrades before proceeding with the install. I *believe* my failure to do this is the more likely cause. DJ Brown Austin, TX -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Vogt Sent: Saturday, April 21, 2007 2:16 AM To: [EMAIL PROTECTED] Subject: [Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed (edgy -> feisty) [snipped] -- [MASTER] [kde] Upgrade tool crashed (edgy -> feisty) https://bugs.launchpad.net/bugs/107188 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 108396] Re: Upgrader Crashed on Upgrade Edgy --> Feisty
*** This bug is a duplicate of bug 107188 *** https://bugs.launchpad.net/bugs/107188 Hello Scott: <> If you mean the "kde-356-pre-feisty-upgrade" directions, no. PEBKAC error. I missed that instruction entirely. The updates I *did* install were two items that were waiting in the daemon when I started the machine that evening. One of them was a Daylight Savings Time update as I recall. Immediately after that, I was presented with the upgrade option. DJ Brown Austin, TX -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Kitterman Sent: Saturday, April 21, 2007 12:27 AM To: [EMAIL PROTECTED] Subject: [Bug 108396] Re: Upgrader Crashed on Upgrade Edgy --> Feisty [snipped] -- Upgrader Crashed on Upgrade Edgy --> Feisty https://bugs.launchpad.net/bugs/108396 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
