Project

General

Profile

Bug #11738

DT 2.2.5 stuck when portable phone connected by USB for charging

Added by Sergei Rybalko 2 months ago. Updated 27 days ago.

Status:
Closed: invalid
Priority:
Low
Assignee:
-
Category:
-
Target version:
Start date:
09/13/2017
Due date:
% Done:

0%

Affected Version:
2.2.5
System:
Debian
bitness:
64-bit
hardware architecture:
amd64/x86

Description

DT stuck when portable phone connected by USB for charging. I found it accidentally. Once I attached my portable phone by USB for charging and open DT for edit, in several seconds DT stuck and crashed after. I repeated opening with same result. After some time I realized that the only change I did was plugging my phone to USB. When I unplugged it DT stared working fluently as previously.


Related issues

Related to darktable - Bug #10624: Having mounted a Smartphone may be confusing Incomplete 08/31/2015

History

#1 Updated by Tobias Ellinghaus 2 months ago

  • Related to Bug #10624: Having mounted a Smartphone may be confusing added

#2 Updated by Tobias Ellinghaus 2 months ago

  • Status changed from New to Incomplete
  • % Done changed from 0 to 20

In the past we saw hangs when a phone was attached. Crashes are new. Do you happen to have a backtrace? /tmp/dt* might have one.

#3 Updated by Sergei Rybalko 2 months ago

Tobias Ellinghaus wrote:

In the past we saw hangs when a phone was attached. Crashes are new. Do you happen to have a backtrace? /tmp/dt* might have one.

OK, it will not crash it will stuck and become unresponsive.

#4 Updated by Tobias Ellinghaus 2 months ago

Could you try running dt in gdb, wait for it to hang and get a backtrace?

The steps are:

gdb darktable
r

wait for the deadlock and switch back to the terminal

ctrl-c
set pagination off
set logging file gdb.txt
set logging on
thread apply all bt full
q
y

Then attach gdb.txt to this bug.

#5 Updated by Sergei Rybalko about 2 months ago

After update my system and restart the computer I cannot reproduce this bug

Tobias Ellinghaus wrote:

Could you try running dt in gdb, wait for it to hang and get a backtrace?

The steps are:

[...]

wait for the deadlock and switch back to the terminal

[...]

Then attach gdb.txt to this bug.

#6 Updated by Tobias Ellinghaus about 2 months ago

  • Status changed from Incomplete to Closed: invalid
  • % Done changed from 20 to 0

Thanks for getting back to us. Should it happen again we can just re-open the bug.

#7 Updated by Roman Lebedev 27 days ago

  • Target version set to 2.4.0

Also available in: Atom PDF