Thanks! Would you mind sharing the commit that fixed the bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862081
Title:
Gnome resizes framebuffer when playing fullscreen video over and over
It seems to be caused by fractional display scaling: The display is
configured to use 150% scaling.
When the scaling is set to 100% (native DPI), mpv and Firefox can play
the video in fullscreen without triggering the bug, everything fine just
like it should be.
When the scaling is set to 200%,
** Description changed:
When I play a video with mpv (or e.g. Firefox), it works just fine.
When this video is fullscreened (e.g. in mpv by pressing f), the screen
quickly turns off, and switches resolution modes in such a rate the
screen is unusable.
The native resolution of the
Public bug reported:
When I play a video with mpv (or e.g. Firefox), it works just fine.
When this video is fullscreened (e.g. in mpv by pressing f), the screen
quickly turns off, and switches resolution modes in such a rate the
screen is unusable.
The native resolution of the screen is 1440p,
This bug looks similar/related to:
https://github.com/systemd/systemd/issues/10123
https://www.spinics.net/lists/linux-fsdevel/msg132837.html
I've attached my hung tasks (sysrq w).
** Bug watch added: github.com/systemd/systemd/issues #10123
https://github.com/systemd/systemd/issues/10123
**
On 18.04 with kernel 4.15.0-46-generic #49-Ubuntu we hit the hang:
[Apr25 10:10] INFO: task kworker/u256:3:48574 blocked for more than 120 seconds.
[ +0.000106] Not tainted 4.15.0-46-generic #49-Ubuntu
[ +0.17] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
Additionally, this patch is required to avoid crashes with Ceph mimic:
https://github.com/collectd/collectd/commit/01cf776f74c6364f0dc3ad07efb0850bc22a03ea
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Funtoo Linux 3.6.0 here.
I found the
load-module module-udev-detect tsched=0
setting somewhere in the ArchLinux wiki:
https://wiki.archlinux.org/index.php/PulseAudio#Glitches.2C_skips_or_crackling
So i added tsched=0, did not help, made it even worse.
Then I additionally changed
Also tracked at ArchLinux:
https://bugs.archlinux.org/task/29850
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985661
Title:
High load average
To manage notifications about this bug go to:
Also tracked at ArchLinux:
https://bugs.archlinux.org/task/29850
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995284
Title:
High idle load on 64bit Ubuntu 12.04 with 3.2.0-24-generic kernel
To
I've got the same problem on a Intel Core2 E6300
(http://ark.intel.com/products/27248/Intel-Core2-Duo-Processor-E6300
-%282M-Cache-1_86-GHz-1066-MHz-FSB%29).
It's clocks are also limited to 600 and 700 Mhz.
System is Ubuntu 11.10 with it's most recent kernel, all other symptoms
also match this
Public bug reported:
my os: arch linux x86_64
since tmux is used as default backend now, we have a few problems using
byobu now:
when multipe users are using the same byobu, it was possible that every
user was working in a different tab, perfect for collaboration.
but now, whenever a user
of course the ~/.byobu directory was deleted after installation
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/898131
Title:
tmux tab switching
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 898440 ***
https://bugs.launchpad.net/bugs/898440
** This bug has been marked a duplicate of bug 898440
tmux tab switching
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have exactly the same issue on my core i5-2520M with hd 3000 sandy
bridge graphics.
These artifacts are very annoying and only occur at the edges of
transparent textures, like you will see on the screenchot.
Same thing occurs in Osmos, but only edges of all textures are visible.
Next thing:
15 matches
Mail list logo