Bug#861112: xsane: always crashes on start

2017-05-19 Thread Aaro Koskinen
Hi, On Fri, May 19, 2017 at 11:44:56AM +0200, Wolfgang Schweer wrote: > On Fri, May 19, 2017 at 09:47:51AM +0200, John Paul Adrian Glaubitz wrote: > > On 05/17/2017 10:57 PM, Andreas Henriksson wrote: > > >> It's disabling Avahi support (I don't have such daemon) > > IMO a daemon isn't needed,

Bug#861112: xsane: always crashes on start

2017-05-07 Thread Aaro Koskinen
Hi, On Fri, May 05, 2017 at 08:04:26PM +0200, John Paul Adrian Glaubitz wrote: > On 05/05/2017 07:16 PM, Aaro Koskinen wrote: > > I think Jörg Frings-Fürst has analyzed and fixed this bug already - he > > provided me test packages (libsane_1.0.25-4~test1_amd64.deb etc.) offline

Bug#861112: xsane: always crashes on start

2017-05-05 Thread Aaro Koskinen
Hi, On Fri, May 05, 2017 at 03:33:34PM +0200, John Paul Adrian Glaubitz wrote: > There previously has been a race condition in the sane-backends net code > which Laurent Vivier found [1]. He had come up with a suggested patch to > address the issue, but the patch was never merged to the Debian

Bug#861112: xsane: always crashes on start

2017-04-25 Thread Aaro Koskinen
Hi, Seems to happen also with scanimage: $ scanimage -L scanimage: thread-watch.c:171: avahi_threaded_poll_lock: Assertion `p' failed. Aborted A.

Bug#861112: xsane: always crashes on start

2017-04-24 Thread Aaro Koskinen
Hi, On Mon, Apr 24, 2017 at 10:21:47PM +0200, John Paul Adrian Glaubitz wrote: > Control: tags -1 moreinfo > > Hi Aaro! > > > xsane with 1 network scanner defined in /etc/sane.d/net.conf > > crashes always on start: > > Would you mind sharing your net.conf file with this bug report so > that

Bug#861112: xsane: always crashes on start

2017-04-24 Thread Aaro Koskinen
Package: xsane Version: 0.999-5 Severity: grave Justification: renders package unusable Dear Maintainer, xsane with 1 network scanner defined in /etc/sane.d/net.conf crashes always on start: $ xsane xsane: thread-watch.c:171: avahi_threaded_poll_lock: Assertion `p' failed. Aborted Before the

Bug#854079: firefox-esr: firefox dies immediately on arm64

2017-02-10 Thread Aaro Koskinen
Hi, On Tue, Feb 07, 2017 at 02:57:31PM +, Riku Voipio wrote: > The patch needed a bit of changing but after applying and compiling, > firefox now indeed works on arm64. Thanks. > > Build package at: https://people.debian.org/~riku/firefox/ Yeah, this version works - thanks! A.

Bug#852639: [Pkg-tigervnc-devel] Bug#852639: tigervnc-standalone-server: mouse pointer stuck in upper left corner

2017-02-04 Thread Aaro Koskinen
Hi, On Sat, Feb 04, 2017 at 03:31:27PM +0100, Joachim Falk wrote: > I have investigated this some more. I assume you used the code from > https://github.com/zohead/fbvnc for fbvnc. Yes, with some local fixes. > With this code, I can reproduce the bug. I assume the problem is that fbvnc > does

Bug#854079: firefox-esr: firefox dies immediately on arm64

2017-02-03 Thread Aaro Koskinen
Package: firefox-esr Version: 45.7.0esr-1 Severity: important Dear Maintainer, Firefox crashes right after startup: $ time firefox Xlib: extension "RANDR" missing on display ":0". Segmentation fault real0m12.336s user0m10.940s sys 0m0.703s $ time firefox-esr -safe-mode Xlib:

Bug#852639: [Pkg-tigervnc-devel] Bug#852639: tigervnc-standalone-server: mouse pointer stuck in upper left corner

2017-01-26 Thread Aaro Koskinen
Hi, On Thu, Jan 26, 2017 at 02:14:36PM +0100, Ola Lundqvist wrote: > For my understanding. How do you connect to the server? I'm connecting from a remote host with ssh port forwarding and using fbvnc client. This works fine with tightvnc on both arm64 and armhf using older Debian rootfs. But

Bug#852639: tigervnc-standalone-server: mouse pointer stuck in upper left corner

2017-01-25 Thread Aaro Koskinen
Package: tigervnc-standalone-server Version: 1.7.0+dfsg-2 Severity: important Dear Maintainer, VNC server is honoring the mouse movement, but the pointer is always displayed/stuck in the upper left corner regardless what the actual position is. Server started with: vncserver :0 -geometry

Bug#834844: release-notes: document that mips* arches now require a R2 CPU

2016-08-25 Thread Aaro Koskinen
Hi, On Thu, Aug 25, 2016 at 12:10:09PM +0100, James Cowgill wrote: > + The 32-bit MIPS support (both big and little endian) now requires a > + processor supporting MIPS32 Release 2 of the MIPS instruction set. > + Notably the Loongson-2E/2F and systems based on them (including the

Bug#811351: additional request...

2016-01-20 Thread Aaro Koskinen
Also if you add new blob, there should be also one for RS485 (there is a GPIO to select between RS232/RS485). > Andrew wrote: > > I was going to take Aaro Koskinen patches, since they have Tested-by: > > etc. > > > > How about you ask Aaro to add the comment? I can

Bug#781892: (Hardware?) problem with denormal values on mipsel

2015-05-26 Thread Aaro Koskinen
Hi, On Tue, May 26, 2015 at 10:13:35AM +0100, James Cowgill wrote: On Sun, 2015-05-24 at 22:32 +0300, Aaro Koskinen wrote: On Fri, May 22, 2015 at 11:00:18PM +0100, James Cowgill wrote: On Sat, 2015-05-23 at 00:04 +0300, Aaro Koskinen wrote: On Fri, May 22, 2015 at 05:27:14PM +0100

Bug#781892: (Hardware?) problem with denormal values on mipsel

2015-05-24 Thread Aaro Koskinen
Hi, On Fri, May 22, 2015 at 11:00:18PM +0100, James Cowgill wrote: On Sat, 2015-05-23 at 00:04 +0300, Aaro Koskinen wrote: On Fri, May 22, 2015 at 05:27:14PM +0100, James Cowgill wrote: Yep it's a hardware problem. The following assembly dies (raises SIGILL) at 'sqrt.s' on the Loongsons

Bug#781892: (Hardware?) problem with denormal values on mipsel

2015-05-22 Thread Aaro Koskinen
Hi, On Fri, May 22, 2015 at 05:27:14PM +0100, James Cowgill wrote: Yep it's a hardware problem. The following assembly dies (raises SIGILL) at 'sqrt.s' on the Loongsons and works everywhere else: === .set mips2 .text .global main .type main, @function

Bug#660960: tight loop attempting to madvise(..., MADV_DONTNEED) locked memory

2012-07-31 Thread Aaro Koskinen
The madvice() busy loop will occur on all systems where page size is bigger than 4KB. From supported architectures, e.g. MIPS and SPARC suffer because of this. See e.g. http://lists.debian.org/debian-mips/2012/07/msg00043.html iceweasel is unusable on these platforms. :-( -- To UNSUBSCRIBE,

Bug#533047: initscripts: bootmisc.sh: error messages if /var/log/dmesg missing

2009-06-14 Thread Aaro Koskinen
Package: initscripts Version: 2.86.ds1-61 Severity: minor Tags: patch bootmisc.sh will display error messages (No such file etc) if /var/log/dmesg is missing. savelog should not be called if the file is not present. -- System Information: Debian Release: 5.0.1 APT prefers stable APT