Hi Mark,


you are right, it is freia. I'm new to devuan and a long time debian user;-)


On my laptop there is still debian testing with xfce and colord 1.4.8-2
and on that it works.

However, on the laptop there is no scanner software installed! Maybe
that can have an effect.


On my main PC there is devuan (freia) installed and sane and scanner
software.

I'm not familiar with gdb or gdb backtrace. Assuming one has to start
manually a debug version of

colord-sane. This is not the same as crashing a just starting
colord-sane due to connecting android device.

But maybe it will show something.


If you can give me a short guide what to do, than I can try to make a
gdb backtrace.


regards

Reiner


Am 19.01.26 um 10:53 schrieb Mark Hindley:
> Control: tags -1 moreinfo
>
> Reiner,
>
> Thanks for this.
>
> On Sat, Jan 17, 2026 at 12:26:42PM +0100, Reiner wrote:
>> Package: colord
>> Version: 1.4.8-2devuan1
>>
>> System is devuan testing (forky) amd64
> Presumably really freia?
>
>> After connecting an android device like google pixel2 or google pixel9a
>> there is no
>>
>> device listed in thunar. Further investigation with dmesg shows a chrashed
>> (segfault) colord-sane.
> There are 2 Debian bugs which reference colord-sane segfaults[1][2]. Is your
> issue the same? A quick search reveals many instances of colord-sane segfaults
> in libusb, some longstanding.
>
> The first requirement will be to get a gdb backtrace of the colord-sane
> segfault.
>
> Mark
>
>
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707628
>
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743979
>