On Sun, 26 Jul 2020, Michael Tokarev wrote:
[ https://bugs.debian.org/948658 ]
Hi Matti!
Is this problem with audio input still exist with current version of qemu in
testing,
the 5.0 one?
Thanks!
/mjt
Yes, the hang is still reproducible with 5.0-13, but I've been using the
workaround I
Hello,
I ran into this problem myself (using "URxvt*font: xft:Terminus:pixelsize=20"
font spec), and seems it is some kind of bug in rxvt-unicode.
Xterm does not suffer from this issue with the same font spec.
The issue seems to reside in src/rxvtfont.C rxvt_font_xft::draw()
with the
On Sat, 18 Jan 2020, Michael Gilbert wrote:
control: tag -1 moreinfo
control: severity -1 minor
On Sat, Jan 18, 2020 at 3:35 PM Matti Hamalainen wrote:
"virtual desktop" works, but is not a feasible option as on a 2560x1440 screen
a 640x480 resolution game will be minuscule.
winecfg can be
Hello!
After some more digging, I've tracked the problem to the audio input /
capture-side of the code. If I leave out the QEMU_ALSA_ADC_DEV="null"
environment variable, the freeze does not happen, but Qemu spews
hundreds of errors, following lines repeat many times:
--
alsa: Could not
Attaching a full 'thread apply all bt' backtrace of all the Qemu threads
in the hang/freeze situation, just in case.
--
] ccr/TNSP ^ pWp :: c...@tnsp.org :: https://tnsp.org/~ccr/
] https://tnsp.org/hg/ -- https://www.openhub.net/accounts/ccr
] PGP key: 7BED 62DE 898D D1A4 FC4A F392 B705
Did some additional testing, it seems that the QEMU_AUDIO_DAC_TRY_POLL=0
I mentioned previously is not needed with Qemu 4.1, but I'm sure it was
needed with an older Qemu version, I could not get any sound with
the ALSA+dmix config I have without it back then.
In any case, I tested Qemu
On Tue, 14 Jan 2020, Michael Tokarev wrote:
Can you please try one more thing here, - namely, getting a backtrace?
Qemu being unresponsible means it is the main thread which is blocked,
so getting a backtrace should be easy - please install the qemu-system-x86
debug package (after adding
Hello,
Submitted a report to libgphoto2 Github issue tracker:
https://github.com/gphoto/libgphoto2/issues/265
--
] ccr/TNSP ^ pWp :: c...@tnsp.org :: https://tnsp.org/~ccr/
] https://tnsp.org/hg/ -- https://www.openhub.net/accounts/ccr
] PGP key: 7BED 62DE 898D D1A4 FC4A F392 B705 E735
On Sat, 28 Apr 2018, Herbert Fortes wrote:
Em 27-04-2018 21:26, Matti Hämäläinen escreveu:
Hello,
I tested against the current upstream GIT version
(91a8425a4fa27def793fa9db2bcb4a71c26c927b)
of libgphoto2, and the problem exists there as well.
If gphoto debug logs are needed, I can provide
Hello,
I tested against the current upstream GIT version
(91a8425a4fa27def793fa9db2bcb4a71c26c927b)
of libgphoto2, and the problem exists there as well.
If gphoto debug logs are needed, I can provide ones against working 2.5.16
and non-working, but they are rather large (about 100M
Not reproducible anymore, is tagged fixed-upstream and is extremely old.
I suggest this can be closed.
--
] ccr/TNSP ^ pWp :: ccr tnsp org :: http://tnsp.org/~ccr/
] PGP key: 7BED 62DE 898D D1A4 FC4A F392 B705 E735 307B AAE3
Hello again!
After some more detective work, I noticed that the issue did not occur on
self-compiled WindowMaker from the git-repo, which made me think what the
debian packaged version might be doing differently ...
It turns out that the deb passes "--enable-randr" flag to wmaker
Hi,
It seems that the programs that trigger/suffer from this bug are all
using libSDL 1.2. The way libSDL 2.0 (and few other programs that I
tested, like Stellarium) handle fullscreen seems to be different and
are not affected.
However, as the problems are not exhibited when using Wmaker
Hi!
After apt-getting the Abiword source and doing some poking around, I
finally managed to uncover what the problem was and it is a bit silly.
As background information, I semi-recently converted my system from
ISO-8859-1 to using UTF-8 unicode, but apparently I had forgotten to
change
On Wed, 24 Oct 2012, Dmitry Smirnov wrote:
Hi Matti,
Would you be able to reproduce with older kernel from testing please?
Yep. Same result with vanilla / stock Debian testing kernel
Linux mos6502 3.2.0-3-686-pae #1 SMP Mon Jul 23 03:50:34 UTC 2012 i686 GNU/Linux
ii
On Wed, 24 Oct 2012, Dmitry Smirnov wrote:
On Wed, 24 Oct 2012 12:57:02 Matti Hämäläinen wrote:
Would you be able to reproduce with older kernel from testing please?
Yep. Same result with vanilla / stock Debian testing kernel
Thank you very much for trying that.
Unfortunately I can't
Ummm... I'm not involved with Debian, but XMMS1 is dead, buried and was
removed from Debian in 2008.
In my opinion, this is not a Debian bug, as the package is not supported
and isn't even in the Squeeze repositories.
--
] ccr/TNSP^DKD^pWp :: ccr tnsp org :: http://ccr.tnsp.org/
] PGP
On Sun, 11 Jul 2010, Craig Small wrote:
On Mon, Jul 05, 2010 at 06:32:42PM +0300, Matti H?m?l?inen wrote:
Invoking 'pstree -a' without other arguments results in segmentation fault (at
Hello,
I've tested this on two different setups and both work fine. Are you
able to run a strace on the
On Wed, 28 Oct 2009, A. Costa wrote:
Thread 1 (Thread 0xb7137a40 (LWP 11836)):
#0 0xb7da075a in ?? () from /lib/libglib-2.0.so.0
#1 0xb7da0faf in g_filename_from_uri () from /lib/libglib-2.0.so.0
#2 0xb7fb59f5 in vfs_file_test () from /usr/lib/libaudcore.so.1
Package: schism
Version: 2:0+20080403-1
Severity: normal
Currently schism package defines Recommends for various related packages,
but according to Debian policy Suggests would be more appropriate for these.
http://www.debian.org/doc/debian-policy/ch-relationships.html
-- System Information:
20 matches
Mail list logo
