[Bug 1558537] Re: Windows being ejected into wrong workspaces
Same bug in 19.04 Gnome Compiz flashback. I'm pretty damn fed up with it by now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558537 Title: Windows being ejected into wrong workspaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1558537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558537] Re: Windows being ejected into wrong workspaces
Same bug in Ubuntu 16.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558537 Title: Windows being ejected into wrong workspaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1558537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558537] Re: Windows being ejected into wrong workspaces
** Description changed: Compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 Ubuntu 14.04.4 LTS, Gnome session flashback Lenovo ThinkPad W520 + NVIDIA GF106GLM [Quadro 2000M] binary driver - version 352.63 from nvidia-352 (proprietary, tested) (because default open source driver caused unusably slow refresh rate) Problem: Windows being ejected into wrong workspaces. Cleanup after the disruption takes about 1.5 minutes and is a tedious clicking chore. Situation 1: When I switch from laptop's internal screen to external, windows move between workspaces. When switching, the workspace-switcher stretches twice as wide as normal, when Ubuntu uses both displays at the same time, "side by side". Guess: It seems that all window positions are stored as a distance from the edge of the first workspace, not in relation to workspace number. Situation 2: After updating and restarting, when relaunching all applications, all the windows open in the workspace that I happen to be at, and not even in the same positions where I left them. Guess: It appears that neither of the responsible bodies, operating system or application, try to remember the locations of windows, and some applications (VLC, document viewer, file browser, image viewer) do not remember anything from their previous state. Could the operating system take a more assertive role in keeping my session intact? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558537 Title: Windows being ejected into wrong workspaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1558537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558537] Re: Windows being ejected into wrong workspaces
Sometimes when Ubuntu comes out of screen saver, it stretches one workspace and its windows double wide, which makes no sense in any situation. The windows get thrown around when I press Fn+F7 to return to normal state. ** Attachment added: "Double wide workspace and window" https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1558537/+attachment/4630117/+files/Ubuntu14.04_LenovoW520_workspace_stretch.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558537 Title: Windows being ejected into wrong workspaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1558537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558537] [NEW] Windows being ejected into wrong workspaces
Public bug reported: Compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 Ubuntu 14.04.4 LTS, Gnome session flashback Lenovo ThinkPad W520 Problem: Windows being ejected into wrong workspaces. Cleanup after the disruption takes about 1.5 minutes and is a tedious clicking chore. Situation 1: When I switch from laptop's internal screen to external, windows move between workspaces. When switching, the workspace-switcher stretches twice as wide as normal, when Ubuntu uses both displays at the same time, "side by side". Guess: It seems that all window positions are stored as a distance from the edge of the first workspace, not in relation to workspace number. Situation 2: After updating and restarting, when relaunching all applications, all the windows open in the workspace that I happen to be at, and not even in the same positions where I left them. Guess: It appears that neither of the responsible bodies, operating system or application, try to remember the locations of windows, and some applications (VLC, document viewer, file browser, image viewer) do not remember anything from their previous state. Could the operating system take a more assertive role in keeping my session intact? ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: rls-x-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558537 Title: Windows being ejected into wrong workspaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1558537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
** Description changed: Error: - Kernel foolishly shuts down the computer when it overheats. + Kernel foolishly shuts down the computer when it overheats because of the underlying bug "Overheat due to slow fans when on 'auto'" + ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/751689 ). /var/log/kern.log W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature reached (100 C), shutting down + (Hardware is ok: when the fan is forced to full speed, no overheating.) Consequence: Shutting down destroys session in Ubuntu, Gnome, and all applications that can't remember their latest conscious state (most applications). Attempted repair, failed: Laptop has suspending ability, but I can't find the setting for the kernel to make the computer suspend instead of shutting down. Repair suggestions: 1. Persistence of session, so that everything would reappear after the restart. (this would also make updating less disruptive) - 2. Do not heat the machine like crazy; speed up fans or slow down processes. (problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end) + 2. Do not heat the machine like crazy; speed up fans or slow down processes. (fix the slow fan bug affecting Lenovo Thinkpads and fix thermald failing to throttle CPU) 3. Put the computer to suspend when it's too hot. - (The problem has remained the same from at least Ubuntu 11.10 through - 14.04) + The problem has remained the same from at least Ubuntu 11.10 through + 14.04 . + ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-62-generic 3.13.0-62.102 ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2171 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 3 13:42:28 2015 HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256 InstallationDate: Installed on 2013-12-29 (612 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 4063B22 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-62-generic N/A linux-backports-modules-3.13.0-62-generic N/A linux-firmware 1.127.15 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET92WW (3.22 ) dmi.board.name: 4063B22 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4063B22 dmi.product.version: ThinkPad W500 dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
I accepted it being a common hardware issue many messages up. Which is easier; fixing the kernel to be non-destructive for these machines, or physically overhauling all overheating laptops running Linux? The "opening windows in a house fire" -parable is inaccurate. What I'm suggesting for the house fire is "automatically open all water taps for cooling and to alert people, maximize ventilation to remove smoke, and text all phones in the approximate GPS location of the house with the warning: detected house fire growing at #address - vacate the building immediately bringing your relatives and valuables outside with you". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
The thermald throttling malfunctioning is interesting. Yes, I believe my laptop is among the several % of portables having cooling issues due to old age and/or on-the-edge design. Like I said, it's a common ailment. Just google "ubuntu laptop overheating" to find out how common. What are we supposed to do to fix that? Approach thermal grease manufacturers about the short life of their products? Solving my problem overhauling my computer is not fixing the problem, it's cover up. Now how about fixing all the ways the kernel is behaving badly in all those overheating machines? Things for software to do in an overheating case (from the original bug report): -use the fan up to its maximum speed (not up to what a designer years ago assumed would probably be enough) -throttle the CPU (thermald troubleshooting in progress) -in a heat emergency, suspend in 1 second instead of shutting down wasting 8 seconds and my session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
It doesn't matter whether this machine has the common old-age ailment of dried thermal grease or not. It's part of normal ageing, so Linux needs to be able to handle it in a non-destructive way. Now Linux is being bullheadedly intolerant to common ailments. It's like a doctor letting an old patient suffer from an indefinitely drug- relievable illness and saying "no, you must buy an expensive life- threatening surgery to correct the underlying root cause". (This parable is apt, because in my computer one insert brass nut has popped off the case and is now spinning in its cavity with the screw, so I would have to do something drastic to even reach the thermal grease.) What kind of an attitude is that to the continual improvement of Linux? https://en.wikipedia.org/wiki/Continual_improvement_process Will it ever be smart if you avoid making it smarter? Or have I mistaken about the goal of Linux development? Even my car from 1995 (Nissan) is smarter than this: in the case of overheating, it can protect itself gracefully in many ways; it doesn't kill the engine demanding immediate cooling system repair - it starts doing every possible cooling action and avoiding various heating actions in the order of least annoyance to the user. Then it informs the user about the heat problem, so that they can help. Then it files an error report about having overheated. Quite a lot better than Linux in 2015. The concept of "failing safely" should be applied here. https://en.wikipedia.org/wiki/Fail-safe Users of these ailing (or just dusty) computers are now suffering of abrupt forced shut downs when they could easily be given lesser evils (noisier fan, slower processing, suspending for a bit every once in a while). All the opportunities to remedy the situation should be taken, because as nothing always works, a low number of actions taken will more likely fail in someone's computer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
Speaking to Lenovo won't automatically fix the issue, because it is way harder to get people to install bios updates than to accept kernel updates. Fan control disengaged mode works: fan runs 4700 RPM, which keeps temperature down at 84 C after several minutes at full load. Unfortunately in disengaged mode the fan always runs 4700 RPM, no matter what temperature or load. So, make the system switch between fan control modes according to temperature and its growth rate to narrowly avoid hitting 100 C (it needs to be done on many affected Lenovos). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
Responses to the points above I disagree with: * fan not running at full speed in disengaged mode in a thermal emergency "... so it never exceeds a top speed of 3500 RPM. This matches the original thermal design by the manufacturer." -When reality acutely requires full speed, it is madness to refer to original designs. "... we would see lots of owners with your machine reporting this bug..." -Where are the 100 automated error reports of my previous overheat crashes? I quess nowhere, because Apport doesn't catch them - it is not considered an error to shut down in a self-caused thermal emergency. I procrastinated filing this bug report for 3 years, because "surely someone will notice all these crashes any day now". Then it took many days of persistent work to find out how to file a kernel bug report using Apport, because there is no such option in the menu; you have to ask Ubuntu support to find out the trick. It is too difficult, so don't expect people to do it. How many users even know how to launch Apport? There is no "Report a bug" in Gnome menu. * shutting down when supposed to suspend as a reaction to overheat, unnecessarily destroying session "when a critical thermal event occurs one has a very short time window to react. ... the machine is desperately trying to save itself from breaking." -Then why not suspend in 1 second, but instead shut down in 8 seconds? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
Attachment from "sudo thermald --no-daemon --dbus-enable --loglevel=debug | tee thermald.log". ** Attachment added: "A few minutes full load over 30% base load" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+attachment/4457110/+files/thermald-lenovo-W500-2015.09.04.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
** Description changed: - Error: + Error: Kernel foolishly shuts down the computer when it overheats. /var/log/kern.log W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature reached (100 C), shutting down Consequence: Shutting down destroys session in Ubuntu, Gnome, and all applications that can't remember their latest conscious state (most applications). Attempted repair, failed: - Laptop has sleeping ability, but I can't find the setting for the kernel to make the computer suspend instead of shutting down. + Laptop has suspending ability, but I can't find the setting for the kernel to make the computer suspend instead of shutting down. Repair suggestions: 1. Persistence of session, so that everything would reappear after the restart. (this would also make updating less disruptive) 2. Do not heat the machine like crazy; speed up fans or slow down processes. (problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end) - 3. Put the computer to sleep when it's too hot. + 3. Put the computer to suspend when it's too hot. (The problem has remained the same from at least Ubuntu 11.10 through 14.04) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-62-generic 3.13.0-62.102 ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: user 2171 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: user 2171 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 3 13:42:28 2015 HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256 InstallationDate: Installed on 2013-12-29 (612 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 4063B22 PccardctlIdent: - Socket 0: -no product info available + Socket 0: + no product info available PccardctlStatus: - Socket 0: -no card + Socket 0: + no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.13.0-62-generic N/A - linux-backports-modules-3.13.0-62-generic N/A - linux-firmware 1.127.15 + linux-restricted-modules-3.13.0-62-generic N/A + linux-backports-modules-3.13.0-62-generic N/A + linux-firmware 1.127.15 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET92WW (3.22 ) dmi.board.name: 4063B22 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4063B22 dmi.product.version: ThinkPad W500 dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
I might renew the cooler paste some day. Why isn't the fan being run in disengaged mode at 5100 RPM by the kernel in a thermal emergency? Surely that would be easier to do than to have every Lenovo W500's cooler pastes renewed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
Installed kernel Linux 4.2.0-040200-generic . Ensured it was running. Problem remains the same: overheating with fan speed staying low (up to 3600 out of 5000rpm) after several minutes at 90-96C. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
The hardware was disassembled and everything was fine. Fan kept speed well after blowing into it. I drilled extra holes to the case bottom to aid air flow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
If thermald is supposed to throttle CPU according to temperature, it doesn't work. Whatever is throttling the CPU seems to be unaware of temperature, because the more I load the machine, the more reliably "cpufreq-info -w" returns "2801000" while temperature is at 90-95 C. Only when there is less load, does the CPU run at lower frequencies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
Attachment from "powerstat -za 1 480". ** Attachment added: "Intermittent full load over 30% base load" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+attachment/4456951/+files/powerstat-lenovo-W500-2015.09.03.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
running "powerstat -Da 1 60" returns "Device does not have any RAPL domains, cannot power measure power usage." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491797] [NEW] Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
Public bug reported: Error: Kernel foolishly shuts down the computer when it overheats. /var/log/kern.log W500 kernel: [1448.648529] thermal thermal_zone1: critical temperature reached (100 C), shutting down Consequence: Shutting down destroys session in Ubuntu, Gnome, and all applications that can't remember their latest conscious state (most applications). Attempted repair, failed: Laptop has sleeping ability, but I can't find the setting for the kernel to make the computer suspend instead of shutting down. Repair suggestions: 1. Persistence of session, so that everything would reappear after the restart. (this would also make updating less disruptive) 2. Do not heat the machine like crazy; speed up fans or slow down processes. (problematic Lenovo Thinkpad W500 fan on low speed right up to the fiery end) 3. Put the computer to sleep when it's too hot. (The problem has remained the same from at least Ubuntu 11.10 through 14.04) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-62-generic 3.13.0-62.102 ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24 Uname: Linux 3.13.0-62-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2171 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 3 13:42:28 2015 HibernationDevice: RESUME=UUID=991e1383-ff5b-46c1-84c4-c904e1d81256 InstallationDate: Installed on 2013-12-29 (612 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 4063B22 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-62-generic root=UUID=bd426989-b545-41b3-97b8-de9410f27aa6 ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-62-generic N/A linux-backports-modules-3.13.0-62-generic N/A linux-firmware 1.127.15 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-27 (494 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET92WW (3.22 ) dmi.board.name: 4063B22 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn4063B22:pvrThinkPadW500:rvnLENOVO:rn4063B22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4063B22 dmi.product.version: ThinkPad W500 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
As recommended on irc/Freenode/#ubuntu-kernel ; -installed linux-generic-lts-vivid -ensured that new kernel is running -ensured that thermald is running The problem remains the same: overheating with fan speed staying low (3500 out of 5000rpm) after several minutes at 95C. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491797] Re: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost
I can't see how that information could be helpful in fixing the problem. It doesn't matter whether there's a common hardware ailment involved in this particular overheating or not. The software is acting like an idiot and wasting all its chances to remedy the situation: -fan not running at full speed in disengaged mode in a thermal emergency -CPU not throttling in a thermal emergency (unless the frequency readings are wrong) -shutting down when supposed to suspend as a reaction to overheat, unnecessarily destroying session -destroying session in a shut down/restart cycle (I heard rumours this may be fixed later in Snappy with containers) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491797 Title: Shuts down when supposed to suspend as a reaction to self-caused overheat, session lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
