Yes, I also noticed that running a virtual machine in VirtualBox is
almost guaranteed to start this issue immediately – apart from the
sporadic occurrences when having the system with Firefox and Thunderbird
run for several days and doing hibernate/resume over night.
Anthony, is this the PPA you
Thanks @Follow-Me and @Anthony, the hint with the kernel update really
seems to work. :-) I didn't know this was even possible in such an easy
manner with an active 10.04 installation.
Inspired by Anthony's descriptions, I found out yesterday that even the
Lucid-Updates repository[1] features
Also with recent update of gdm (2.30.0-0ubuntu5.2) and linux kernel
(2.6.32.32.38) totem Movie Player didn't regain its video scaling
abilities.
Am I really the only one experiencing this?? How can that be? Any help?
Please!
--
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: totem
Ever since I did a gstreamer upgrade (from the Gstreamer Developers PPA:
https://launchpad.net/~gstreamer-developers/+archive/ppa) a couple of
days ago, the Movie Player (totem 2.30.2 using GStreamer 0.10.32
(prerelease)) will not resize the video
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/769272
Title:
Totem Movie Player not resizing video in fullscreen anymore
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Apparently, with the latest update of some of the GStreamer related
packages Totem Movie Player regained its video scaling abilities:
Upgraded the following packages:
gir1.0-gstreamer-0.10 (0.10.32.2-1~lucid2) to 0.10.32.3-1~lucid1
gstreamer-tools (0.10.32.2-1~lucid2) to 0.10.32.3-1~lucid1
Graham, after testing this by leaving my machine running for several
days, I could confirm that it seems not to be directly related to
suspend-to-ram. However, I got the feeling that after suspend-to-ram it
seems more likely to occur sooner. As an example: with my machine
running continuously for
Oh, I will, of course, have an eye on dpkg and related processes once
this happens again. So far, it has not happened for 3 or 4 days on my
machine (knock on wood), but I also rebooted twice recently, due to the
kernel updates.
--
You received this bug notification because you are a member of
I think what we really need to clarify is what we all mean by
kswapd0 using/causing 100% CPU. Reading through some of the posts here I
get the feeling that some of us (even me) might not really be talking about
the same thing as some of the others, and therefore might indeed have a
similar but
Oh, thank Dog, I'm not the only one with this issue.
I had explained that issue at length in the Ubuntu forums, but never got
any reply: http://ubuntuforums.org/showthread.php?t=1681368
I, too, noticed this behavior ever since mid-January, I think. for the
first weeks, whenever this issue
Yeah, just did that. Sorry, hadn't seen that function before.
Arkadiy, do you suspend-to-RAM your server, as well? For me, this issue
never happened before the first suspend/resume after a full reboot.
Might be a coincidence, though, as I barely ever reboot my machine, but
suspend it to RAM
When kswapd0 starts going berserk on my machine, my swap is usually not
or barely in use (0 or a few kiB of the 3GB). However, once kswapd0 is
given some time to be wicked, it will fill up the swap considerately to
a point (normally not full but a little over half full, I think; last
night it was
I can now confirm that the issue seems unrelated to suspending/resuming.
After a continuous uptime of more than 90 hours, my machine just ran
into this issue again -- not for the first time within these 90 hours,
but for the first time with all previous symptoms and without getting
back to normal
Dammit! And here is the attached log I announced...
** Attachment added: Output of 'top -i' in an interval of about 11 seconds,
showing kswapd0 idle process and high I/O Wait
https://bugs.launchpad.net/ubuntu/+bug/721896/+attachment/1872267/+files/top-monitor.txt
--
You received this bug
Oh dear... please ignore previous attachment. (Mods, please delete if
possible!)
Here is the correct file. Good night!
** Attachment added: [Log] Output of 'top -i' in an interval of about 11
seconds, showing kswapd0 idle process and high I/O Wait
Hello Arkadiy,
have you posted this issue somewhere else and gotten a response there?
For the last two days, this kswapd0 related I/O Wait bussiness has
really been constantly p***ing me off, even though no swap space was
even mounted. And in this bug report it seems like two people don't make
Seems like it's the same issue as this one:
http://askubuntu.com/questions/153691/screen-doesnt-display-after-
resume-using-x-swat-nvidia-drivers
And Bryn there mentioned a thread in the nV News forums, apparently
discussing this very same issue that seems to have started/regressed
with version
** Tags added: lucid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1015305
Title:
lockup on resume after suspend on T420s
To manage notifications about this bug go to:
Sorry!
Edit: [...] I had no such problem with Compiz on Ubuntu 10.04 and Gnome2 [...]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955355
Title:
Compiz does not allow focusing on the desktop with
Confirmed as in #2 with Compiz on Mate Desktop (Linux Mint 15, based on
Ubuntu 13.04), Compiz version 0.9.9.0
(1:0.9.9~daily13.06.19~13.04-0ubuntu1): No matter whether click-to-focus
is set or not.
This worked fine in previous versions; I had not with Compiz on Ubuntu
10.04 and Gnome2 (Mate is a
For me, this issue seems to have been fixed with NVidia's driver version
304.43. \o/
Still on Ubuntu 10.04.4 LTS x86_64, with Linux kernel version
2.6.38-13-generic, I suspended-to-ram and resumed my machine several
times for the last week or so, and all works well.
This just in case somebody
I believe this bug affects me as well, with XFCE4.10 as the DE on Ubuntu
13.10. Whenever I minimize to tray/iconify a window and then restore
from tray, the size of the window will shrink by the size of its
decoration and title bar. Somehow sounds to me like exactly what's
happening in this bug
Hrmpf, it didn't link to the other bugs...
Likely related bugs: bug #1204307, bug #1217286
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287472
Title:
compiz unnecessarily shrinks new windows
To
Adam, are you sure that the window only gets shrunk vertically? Could it
be that it gets shrunk horizontally, as well, but only to a rather small
degree (as the window borders left, right and bottom are only a few or
in some themes even 0 pixels)?
It could have to do with the size of the window
Confirming, as well: 0.8.9-0ubuntu0.16.04.1 from xenial-proposed fixed
the issue for me. Thank you, Devs!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688056
Title:
Package outdated
To manage
@perryhelionsemail: Thank you for putting all this info together and for
staying at it! :)
Just to weigh in: I am affected, too, on an ACER Aspire V 11 Touch (V3
-111P-P06A), N3530 CPU, Intel onboard graphics, 8GB RAM (not original)
and 480 GB SSD (not original), and having the boot flag
@perryhelionsemail - I am really hesitant to removing the max_cstate
boot flag: I had to set this in order to avoid random and total system
freezes. And that bug seems to be anything but fixed:
https://bugzilla.kernel.org/show_bug.cgi?id=109051
So, with due respect to curiosity – not gonna try
27 matches
Mail list logo
