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
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:
** 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
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"
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
** 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 ).
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
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
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
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
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
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
** 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,
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
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:
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.
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
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
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
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
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
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
22 matches
Mail list logo
