I'm pretty sure, the second 'backoff=0' should read 'retries=0'.
The loop there increases the backoff time in tenth of seconds for each
successive failure, and after success, both 'backoff' as well as
'retries' should be reset.
--
You received this bug notification because you are a member of
Good news, everyone.
The bug is in fact located within pcmanfm (more precisely, within the
GTK library part of, libfm-gtk1), and has been fixed by the author
within the git repository of this project 9 days ago.
Since I have not read any further discussion about this bug any more and
since I
Hi Luigi.
Yes, you are right.
Use CTRL+ALT+F2, as described in post #24. Then you should be able to
reproduce 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/878993
Title:
x.org lockup
I'd like to confirm the weird behavior reported by kjoe in posts #23 and
#25.
In fact, kjoe, this weird every second time behavior seems to happen
on a per target basis. Try dnd-extracting to target1 (e.g., desktop),
target 2 (some folder), target 1, target 2, and so on, without striving
the
@Nate: I'm sorry for that.
No, at the moment I have no idea, but if you like, we can try to
investigate.
What Ubuntu version do you have? (I use 10.04)
What sound card? (I have SB Live Value)
Can you attach?
1. The output of aplay -L and aplay -l (this is a lower case L)
2. A pulseaudio log
Hi there.
I wonder why no more comments have been posted for over two weeks now.
As far as I am concerned, the problem is still in place, and none of the
workarounds proposed above (using a pure PCM-control; passing
ignore_dB=yes to the module(s)) have worked out for me.
Anyway, I found another
NOTE: In the post above, substitute uncomment by outcomment (step
2).
Sorry,
-- Stefan
BTW: Please nobody get me wrong. PA's idea of simplifying controls is
absolutely right. As soon as the original issue is fixed, I recommend to
immediately switch back to PA controlling the hardware volume.
--
Hi folks.
Thanks for all the comments, especially #127 (Daniel) and #143 (Pebas).
As Daniel mentioned in #127, the problem is based in the way newer PA
versions are merging the PA channel volume settings into the physical
channel volume settings. Furthermore, it seems to be unclear, whether
this
Have you ever taken a look into ~./config/totem/state.ini ?
Normally, it looks like this:
[State]
window_w=800
window_h=600
show_sidebar=false
maximised=false
sidebar_w=206
sidebar_page=properties
where window_w and window_h seem to refer to the window's size WITHOUT
window decorations.
