[Bug 370173] Re: laptop overheats and suddenly shuts down/off
Thanks, Eloi :) Yeah, I think the best way to find out is a step-by-step installation anew. I just don't have time for this and if you do - you could probably help many people! I hope my situation will help someone too.. for vmware processes could be the cause - I'm not a linux expert neither, just advanced user, but I still don't know how to test vmware startup modules to check if they really were the problem.. If someone of the debian development reading this - I'm ready to try and test these things out, just tell me how :) Good luck! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/370173 Title: laptop overheats and suddenly shuts down/off -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 370173] Re: laptop overheats and suddenly shuts down/off
** Also affects: acpi (Debian) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/370173 Title: laptop overheats and suddenly shuts down/off -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 370173] Re: laptop overheats and suddenly shuts down/off
Hello Eloi Espanol, I will describe in details my situation after BIOS upgrade (hope it can help): After upgrading BIOS I had the sensors applet showing ACPI temperature (110 C) again, but it was different: - Before upgrade: it was 110C all the time since booting and the laptop was laggy and slow all the time. - After upgrade: it booted okay, but in one hour or two, when I was working in some "heavy" program (VMware Workstation, Photoshop) - I heard my fan starting to work loudly and I saw again temp-applet showing ACPI 110C. But! I think this applet doesn's show the temperature quite right - cause there are only two temperatures it showed me - 27C or 110C (and it didn't change for any other throughout the day). So, I looked through the System Tools > Log File Viewer: and I didn't find the message I saw before BIOS upgrade "Critical temperature reached (110 C), shutting down." Just another message kinda "ACPI ... 110C" (didn't save it). I also saw this in the syslog: fan PNP0C0B:00: registered as cooling_device0 ACPI: Fan [FAN0] (off) fan PNP0C0B:01: registered as cooling_device1 ACPI: Fan [FAN1] (off) And I thought maybe something was wrong here, but laptop fan worked OK, since I heard it working and changing the speed sometimes. And now, when everything's fine - this message is still there and the fans work fine. So, I thought about two variants left to try: either the laptop fans were in dust (I didn't clean it after buying) or maybe it's something connected with VMware Workstation processes (there are many of the running at boot and running all the time when VMware isn't even in use). Cause when I tried to remember when this laggy problem started to occur on my previous system - Ubuntu 10.10 (the one I had before installing Debian, and before Debian I had 3 or 4 previous versions of Ubuntu and it worked OK) - I remembered I had recently upgraded VMware Workstation to the last version (v.7.1.3-324285.). Also, just after I installed Debian 6.0 - I worked on my laptop for one or two days without having this problem - it took me to finish tuning up my system and installing everything I need. One of the last programs I installed was exactly the last version of VMware. And here the laggy problem began (as fas as I remember)! So, I tried both: 1) I thouroughly vacuum-cleaned the fans (laptop shut down of course :) 2) AND, I downgraded VMware Workstation to previous version 7.1.2-301548. And the problem's gone... I worked in Photoshop for couple of hours with large files and everything worked fine, I didn't work in VMware though. But it's already two days I don't have this problem again. And after cleaning the fans - I almost don't hear it working, it's not loud at all - there were pretty much dust in there. Maybe all this is too much detailed, but I don't really know what helped to solve my problem - maybe it was vmware processes , or maybe it was the dust.. OH, and another note! I upgraded BIOS to v10, not v11. When I was googling this laggy problem, I once read in some bug report that people who upgraded their DELL BIOS to v11 had this problem occur again (on Windows 7 though) - and the solution was to downgrade BIOS to v10. Maybe it could help you too, but I think you should find out more information about this variant before downgrading. Hope I could help you in some way :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/370173 Title: laptop overheats and suddenly shuts down/off -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 370173] Re: laptop overheats and suddenly shuts down/off
I had almost the same issue with the only difference that it didn't shut down, but every single program was very-very-very slow and nothing helped. Computer: DELL Studio 1558 laptop (purchased about 6 months ago) The error I saw at every boot-reboot-shutdown was: "Critical temperature reached (110C), shutting down." Laptop behaviour: everything very slow, hdd temp=42-50 C, ACPI temp = 110C (I monitored it in the gnome-panel applet "computertemp") System: I was running Ubuntu 10.10 and this bug didn't appear immediately after upgrade (clean reinstall from 10.04). Last week I moved to Debian 6.0 (squeeze) due to my personal preferences and also hoping this bug to dissapear - but it didn't! Today I've found the fix: BIOS Update! Just performed the update (I had BIOS version A04 - updated to version A10) Now, everything looks and feels normal and smooth again! (computertemp shows "ACPI temp=27C") I found 2 ways to do it: 1) under Linux - through libsmbios package (explanations given for Debian, not Ubuntu, though) http://www.ducea.com/2007/08/27/dell-bios-firmware-updates-on-debian/ 2) via Windows 7 Live CD (not Windows XP, cause the DELL Studio 1558 BIOS doesn't support WinXP and you will have a Blue Screen of death with acpi.sys error!) I used the second way, cause there is no bios update file for linux for this laptop - why? explained here http://answerpot.com/showthread.php?1534809-Studio%201558%20BIOS%20updates%20not%20available ("Quite a few desktop and notebook systems don't have a method to update BIOS that's supported by firmware-tools. :-( In particular, this model has its Windows-executable BIOS in a package format that firmware-extract doesn't recognize.") Hope it will help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/370173 Title: laptop overheats and suddenly shuts down/off -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 327793] Re: Window decorations in title bar missing with compiz enabled
I have the same problem with the window decorations. I found to solve it but just until the next reboot I have compiz settings off, and I even had my compiz uninstalled when this problem occurred. Temporary solution: I turn Compiz effects to Normal > I wait for it to apply > "Keep settings" > Turn back to Compiz effects Off (for when it's on - it slows down everything). Today I found what the problem is - it is XORG! I've tried the solution proposed by w4w4n and I found out that my xorg.conf file is gone! I remember there was some xorg updates recently - so, I suppose, the bug is due to these recent xorg updates which, apparently, deleted the existant xorg.cong file !without backup! I have a xorg.conf backup - but I cannot reach it for the moment (I'm far from home). What should I do to reconfigure xorg without failure? Thanks, I hope it will help! -- Window decorations in title bar missing with compiz enabled https://bugs.launchpad.net/bugs/327793 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 155992] Re: contacts crashes when attempting to pick contact using catagory pull down
This bug is still present in Ubuntu Karmic - evolution completely crashes when I press Contacts button to see my contacts. The same was with the previous ubuntu releases (interpid, jaunty - I had them all installed before too). So, it appears that this bug is known since 2007 and still wasn't repaired? Regards, Greya -- contacts crashes when attempting to pick contact using catagory pull down https://bugs.launchpad.net/bugs/155992 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 316877] Re: Nautilus freezes completely when accessing large exterior hard drive (500Gb)
I found what the problem is - it's some incompatibility of nautilus and NTFS filesystem of my external drive. When I have nautilus hanging and try to unmount it via terminal - it responds that the drive is busy and cannot be unmounted, "lsof" does not respond either. I've tested my drive on another Ubuntu 8.10 machine with all the latest updates installed and had the same nautilus freeze. When connected to Windows - my drive works fine (NTFS with NTFS). Moreover, my NTFS drive must be fragmented a lot (I didn't perform any defragmenting for a long time), so it probably adds some compatibility problems too (it works slowly sometimes even in Windows). My solution: I will format my external drive in ext3 filesystem, 'cause nautilus with 500Gb external drive in ext3 works fine. However, this linux-NTFS problem should be corrected in the nearest future, for not all people may want to format their drives in ext3. Thanks! :) -- Nautilus freezes completely when accessing large exterior hard drive (500Gb) https://bugs.launchpad.net/bugs/316877 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 316877] Re: Nautilus freezes completely when accessing large exterior hard drive (500Gb)
That's what I did, bt succeeded only on the second nautilus process running (the first one remained freezed forever). I can't type "thread apply bt" cause when I attach gdb to the first nautilus process when I have it hanging - it doesn't show the expected behavior - after I type at (gdb) "attach " (process no.) it starts but stops at the line like [New Thread 0xb6ad1930 (LWP 8125)] and never continues, it doesn't act as expected and doesn't end up by (gdb) for I can type "thread apply bt". When I start another nautilus process and attach gdb to it - it acts as extected and ends by (gdb) line and I type "thread apply bt". -- Nautilus freezes completely when accessing large exterior hard drive (500Gb) https://bugs.launchpad.net/bugs/316877 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 316877] Re: Nautilus freezes completely when accessing large exterior hard drive (500Gb)
I have disconnected my external drive (I can't browse any of its directories anyway) and without it nautilus works correctly, this bug didn't show up. In case it does - I'll surely tell you :) I have also connected this external drive to another computer (but running Windows) to see if it's not broken or something - it works fine. Maybe I should test this bug on my virtual Ubuntu 8.10 (I have one installed in vmware)? In this case I can test it without last updates installed and then install all last updates and test again - to see if this bug will reproduce. (But external drive will be connected a bit differently in virtual ubuntu, I guess?) -- Nautilus freezes completely when accessing large exterior hard drive (500Gb) https://bugs.launchpad.net/bugs/316877 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 316877] Re: Nautilus freezes completely when accessing large exterior hard drive (500Gb)
That's exactly what I do. I mean there that when I have nautilus hanging and when I attach gdb to it - I do in terminal: gdb, then: attach (nautilus process no.) - it stops at the line like this [New Thread 0xb6ad1930 (LWP 8125)] and nothing happens then, it doesn't end by the line with (gdb) something like ... Loaded symbols for /usr/lib/gtk-2.0/2.10.0/engines/libmurrine.so 0xb8075430 in __kernel_vsyscall () (gdb) where I can type "thread apply bt" (in comparison with the succeeded log-file attached above) And everything I type in this terminal window where the gdb attach process didn't finalize correctly - nothing works, I can't even get back my ordinary startup line "(user)@(computername):~$". So, as I described above: - I try to open any nautilus window to start another nautilus process with another process no. - I open another tab in terminal where I attach gdb to this second nautilus process - and this time it succeeds to perform the gdb attach correctly. I don't know why, but when trying to attach gdb to the first hanging nautilus process - it doesn't work. -- Nautilus freezes completely when accessing large exterior hard drive (500Gb) https://bugs.launchpad.net/bugs/316877 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 316877] Re: Nautilus freezes completely when accessing large exterior hard drive (500Gb)
** Attachment added: "gdb-nautilus+glib-2" http://launchpadlibrarian.net/21248021/gdb-nautilus%2Bglib-2 -- Nautilus freezes completely when accessing large exterior hard drive (500Gb) https://bugs.launchpad.net/bugs/316877 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 316877] Re: Nautilus freezes completely when accessing large exterior hard drive (500Gb)
1. I've installed debug symbols for glib (the debug packages I could find in repository), 2. ran nautilus, got it to hang and 3. tried to attach gdb to it - but it couldn't attach properly - it hang and didn't pass to the next line with (gdb). 4. "Force Quit" nautilus window, everything on desktop disappeared, nautilus freezed 5. run nautilus again (tried to open home/[user] directory) - no window opened but another nautilus process appeared (pidof nautilus ==> 8125), i.e. I had 2 nautilus processes 6. attached gdb to this second nautilus process and copied everything from terminal into ==> gdb-nautilus+glib.txt 7. I disconnected the external hard drive where nautilus freezed and nautilus restarted, everything on desktop reappeared, but nautilus windows still don't open 8. ran nautilus again, attached gdb to it =see=> gdb-nautilus+glib-2 (I guess I'm missing some debug libraries there) Please, instruct me more precisely if I'm doing something wrong, I'm not such an advanced user :) Thanks! ** Attachment added: "gdb-nautilus+glib" http://launchpadlibrarian.net/21248001/gdb-nautilus%2Bglib -- Nautilus freezes completely when accessing large exterior hard drive (500Gb) https://bugs.launchpad.net/bugs/316877 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 316877] Re: Nautilus freezes completely when accessing large exterior hard drive (500Gb)
I did as Sebastian said and saved all I had in terminal into txt file attached. Does it help now? What's interesting - nautilus hung again and it could be killed by gdb, then I could reopen nautilus window, but it still works incorrectly. Thank you for your help! ** Attachment added: "gdb-nautilus.txt" http://launchpadlibrarian.net/21215076/gdb-nautilus.txt -- Nautilus freezes completely when accessing large exterior hard drive (500Gb) https://bugs.launchpad.net/bugs/316877 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 316877] Re: Nautilus freezes completely when accessing large exterior hard drive (500Gb)
** Attachment added: "gdb-nautilus-freezed.txt" http://launchpadlibrarian.net/21206332/gdb-nautilus-freezed.txt -- Nautilus freezes completely when accessing large exterior hard drive (500Gb) https://bugs.launchpad.net/bugs/316877 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 316877] Re: Nautilus freezes completely when accessing large exterior hard drive (500Gb)
** Attachment added: "gdb-nautilus-2.txt" http://launchpadlibrarian.net/21206321/gdb-nautilus-2.txt -- Nautilus freezes completely when accessing large exterior hard drive (500Gb) https://bugs.launchpad.net/bugs/316877 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 316877] Re: Nautilus freezes completely when accessing large exterior hard drive (500Gb)
So, I've tried to do what's described in the wiki. This is the first time I debug a program, so I probably did something not quite correctly, cause I couldn't get "(gdb) backtrace full" in the beginning. But somehow I managed to have it working (following all the instructions). I will attach several gdb logs: 1) Backtrace through running the program ==> gdb-nautilus-1.txt How I got this log: I tried to start the program as described gdb nautilus 2>&1 | tee gdb-nautilus.txt (gdb) handle SIG33 pass nostop noprint (gdb) set pagination 0 (gdb) run Then in the so opened nautilus window I tried to access some directories (external drive, File system) - nautilus hung up and nothing could open there except for my Desktop and Documents directory, but this time I could "Stop" it (through Stop button) and close the nautilus window. So, I tried to continue in terminal with "(gdb) backtrace full" - it wrote me "No stack", and for "(gdb) info registers" - it wrote "No registers". (as I've got no backtrace in gdb-nautilus.txt, I don't attach it) Then I've restarted the procedure all over to try it again - at this stage nautilus was probably already not working - you will see it in the log - nautilus didn't open through "(gdb) run", but! I could get the backtrace this time (gdb-nautilus-1.txt) :) The I had to reboot cause no desktop again and nautilus not working((( and performed step 2 below 2) Backtrace for "Already running programs" ==> gdb-nautilus-1.txt This time I did: pidof nautilus replied: 7185 Then gdb 2>&1 | tee gdb-nautilus-2.txt (gdb) handle SIG33 pass nostop noprint (gdb) set pagination 0 (gdb) attach 7185 Then (gdb) continue no nautilus window opened (I don't know whether it should have opened). So, I opened nautilus /home/greya/ and tried to go to File System from the left panel - nautilus freezed completely. I did "Fore Quit" - everything on desktop disappeared again, nautilus not working. 3) Then, in this completely freezed state I tried to do the backtrace procedure again to see what errors it will show. I did again : pidof nautilus replied: 7185 Then gdb 2>&1 | tee gdb-nautilus-freezed.txt (gdb) handle SIG33 pass nostop noprint (gdb) set pagination 0 (gdb) attach 7185 and that's what it replied this time: Attaching to process 7185 ptrace: Operation not permitted. (gdb) Hangup detected on fd 0 error detected on stdin (see gdb-nautilus-freezed.txt) OUHH! now I cannot attach you the log files from my home directory - While I was writing all this - nautilus must have hang up again!!! I only opened the 3 log files concerned to copy some lines in here and now when I try to attach a file here - my home directory doesn't open. I had to copy these files onto my Desktop to attach them here!!! And in general, when nautilus hangs up and when I can stop it quickly (stop button) - I cannot access not only the external drive, but File System directories, my home directory neither (as now) :(( ** Attachment added: "gdb-nautilus-1.txt" http://launchpadlibrarian.net/21206318/gdb-nautilus-1.txt -- Nautilus freezes completely when accessing large exterior hard drive (500Gb) https://bugs.launchpad.net/bugs/316877 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 316877] [NEW] Nautilus freezes completely when accessing large exterior hard drive (500Gb)
Public bug reported: Binary package hint: nautilus I'm running Ubuntu 8.10 (kernel 2.6.27-9-generic ; gnome 2.24.1) on Sony Vaio CS190 Bug found after last update today (update concerned cups package mainly, as I remember), yesterday I was able to perform actions that I'll describe below. Actions performed > Open large Music directory (about 60 Gb) on my external drive through a link in my home directory (this is the first time I encountered this bug), Open ANY directory on my external drive BUG > Nautilus hangs and freezes completely when I try to access my external USB 500Gb drive - I cannot neither "Kill process" nor "End process" in System monitor -> where nautilus process shows Status : Zombie, Memory : N/A, do_exit So, I try to close the nautilus window where I tried to open the above-mentioned directory - it shows options Cancel/Force Quit. And when I click "Force Quit" option - everything on my desktop disappears and does not reappear, even within 3-5 minutes (I waited expressly to see if it will restart by itself - No!). Moreover, the nautilus process in System Monitor is still there! So, everything I can see is the desktop wallpaper without anything of my data on it and the launch panels. In this state, I also tried to find and kill the process through "top" command in terminal - nautilus isn't in the list. Then, I tried to open the mentioned external directory through typing in terminal "nautilus /media/(name of my external drive)" and when typing the name of the drive - it stops typing neither I can't delete anything I typed. The only thing that helps to restart nautilus is COMPLETE REBOOT, cause Logging Off (Ctrl+Alt+Backspace) does not help neither - in this case I also see only desktop wallpaper and panels. After complete reboot - everything works, but when I try to open the external drive again - everything repeats again! :( I have already rebooted 3 times! I'm not an advanced user, so, please feel free to correct my actions if I'm doing something wrong. I hope it can be solved quite quickly, for nautilus is not the last and not the least important part of the system :) Thank you. Greya ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: cs190 freeze intrepid nautilus sony ubuntu vaio -- Nautilus freezes completely when accessing large exterior hard drive (500Gb) https://bugs.launchpad.net/bugs/316877 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 277827] Re: [GM45] 3D much slower in Intrepid than in Hardy
*** This bug is a duplicate of bug 252094 *** https://bugs.launchpad.net/bugs/252094 I can also confirm problems with 3D at Intel GM45 (kernel 2.6.27-9, sony vaio cs190, intrepid) - it's not working at playing some simple 3D games, for example, or the majority of 3D screensavers ~$ glxgears: 2994 frames in 5.0 seconds = 598.697 FPS 3428 frames in 5.0 seconds = 685.464 FPS 3402 frames in 5.0 seconds = 680.383 FPS... Hope it can get fixed in future upgrades and Jaunty! -- [GM45] 3D much slower in Intrepid than in Hardy https://bugs.launchpad.net/bugs/277827 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