Re: Fwd: [darktable-user] darktable suddenly refuses to launch on Manjaro

2023-08-30 Thread Jean-Luc 

Le 25/08/2023 à 14:31, Bruce Williams a écrit :

No, I had not!
This was the error thrown by the terminal:

an error occurred while trying to execute gdb. please check if gdb is 
installed on your system.

backtrace written to /tmp/darktable_bt_XHGFA2.txt
zsh: segmentation fault (core dumped)  darktable


[.../...]

Hello,

And sorry to come so late.
There has already been a discussion about such an error involving gdg 
(gnu debug).

IIRC, such error is related to some corrupted config or db file.
Might be worth restoring the files at the time you updated to 4.4 and 
see what happens...


Rgrds,

J.-Luc


darktable user mailing list
to unsubscribe send a mail to [email protected]

Fwd: Fwd: [darktable-user] darktable suddenly refuses to launch on Manjaro

2023-08-28 Thread Bruce Williams 
Manuel,
While launching from the command line with this:
darktable --configdir ~/.config/darktable/test
...does work, when I go into preferences/processing, the last 3 lines which
all pertain to opencl are greyed out.
No option to enable them. They all say "not available".

Then, you suggested:
1) First, make a backup of the current config directory.
2) Copy the default darktablerc into your config:
$ cp ~/.config/darktable/test/darktablerc  ~/.config/darktable/
3) Roll back the library.db and data.db from darktable's own snapshots,
from most recent to oldest, e.g.
$ cd ~/.config/darktable
$ cp data.db-snp-20230716172500 data.db
$ cp library.db-snp-20230716172500 library.db

Did that, and darktable does now launch from the icon on the taskbar. 1
small step for a man... no giant leap for mankind just yet.
OpenCL is still not available.
Nor is the ability to multiselect images in the lighttable view. That's a
new twist. I've never seen that not be possible.




Romano,
You suggested restoring via Timeshift.
I just opened Timeshift, which I have set to capture 1x weekly and 5x daily
backups.
But bizarrely, it is set to EXCLUDE both /root and the user home directory
(and all files therein, in both instances... so I'm not sure exactly what
it is backing up!)




David,
That's actually sounding like a decent plan, to be honest. I might just go
that route.


darktable user mailing list
to unsubscribe send a mail to [email protected]

Re: Fwd: [darktable-user] darktable suddenly refuses to launch on Manjaro

2023-08-27 Thread David Vincent-Jones 
After some considerable level of frustration I backed-up the .config 
folder and then totally removed dt from my system. I then reinstalled 
from scratch but reused just a couple of the old config files before 
totally rebuilding the library.


In the process I lost a couple of small convenience settings but the 
frustration is gone as everything is now in tip-top shape.


On 2023-08-27 04:57, Manuel Presnitz wrote:

Hi Bruce,


* $ darktable --configdir /path/to/temporary/configdir This will create a

THAT made it launch.
Which is both a good thing and a bad thing.

Great, as dt is working with the default config, I assume that with your system
is everything fine. You could double-check and enable OpenCL with the
default config and see if dt still works.

If you dn't have some external control panels (I think these are interfaced
over MIDI), I would neither mind at the moment about the libportmidi,
nor the fontconfig error.


No, I don't think I have a backup of my original config.

Darktabe usually writes periodic snapshots of the config/library itself.
So I would now try to:

1) First, make a backup of the current config directory.
2) Copy the default darktablerc into your config:
 $ cp ~/.config/darktable/test/darktablerc  ~/.config/darktable/
3) Roll back the library.db and data.db from darktable's own snapshots,
 from most recent to oldest, e.g.
 $ cd ~/.config/darktable
 $ cp data.db-snp-20230716172500 data.db
 $ cp library.db-snp-20230716172500 library.db

Check inbetween if dt is starting up.

Cumbersome task, but if you don't want to start again from a default
configuration, that's my best guess...

Regards,
Manuel.




When I launched it from the command line, although it launched, the
command
line gave me this:

   ~  darktable --configdir ~/.config/darktable/test

 1 ✘
Fontconfig error: "/etc/fonts/fonts.conf", line 29: not well-formed
(invalid token)
Fontconfig error: Cannot load config file from /etc/fonts/fonts.conf
 1.3400 [lib_load_module] failed to open `midi': libportmidi.so.2:
cannot open shared object file: No such file or directory

Not sure if anyone understands what all that means, and if that might be
the cause of the issue?



darktable user mailing list
to unsubscribe send a mail [email protected]




darktable user mailing list
to unsubscribe send a mail [email protected]



darktable user mailing list
to unsubscribe send a mail to [email protected]

Re[8]: Fwd: [darktable-user] darktable suddenly refuses to launch on Manjaro

2023-08-27 Thread Manuel Presnitz 
Hi Bruce,

>> * $ darktable --configdir /path/to/temporary/configdir This will create a
> THAT made it launch.
> Which is both a good thing and a bad thing.

Great, as dt is working with the default config, I assume that with your system
is everything fine. You could double-check and enable OpenCL with the
default config and see if dt still works.

If you dn't have some external control panels (I think these are interfaced
over MIDI), I would neither mind at the moment about the libportmidi,
nor the fontconfig error.

> No, I don't think I have a backup of my original config.

Darktabe usually writes periodic snapshots of the config/library itself.
So I would now try to:

1) First, make a backup of the current config directory.
2) Copy the default darktablerc into your config:
$ cp ~/.config/darktable/test/darktablerc  ~/.config/darktable/
3) Roll back the library.db and data.db from darktable's own snapshots,
from most recent to oldest, e.g.
$ cd ~/.config/darktable
$ cp data.db-snp-20230716172500 data.db
$ cp library.db-snp-20230716172500 library.db

Check inbetween if dt is starting up.

Cumbersome task, but if you don't want to start again from a default
configuration, that's my best guess...

Regards,
Manuel.



> When I launched it from the command line, although it launched, the
> command
> line gave me this:
>
>    ~  darktable --configdir ~/.config/darktable/test
>
>  1 ✘
> Fontconfig error: "/etc/fonts/fonts.conf", line 29: not well-formed
> (invalid token)
> Fontconfig error: Cannot load config file from /etc/fonts/fonts.conf
> 1.3400 [lib_load_module] failed to open `midi': libportmidi.so.2:
> cannot open shared object file: No such file or directory
>
> Not sure if anyone understands what all that means, and if that might be
> the cause of the issue?
>
> 
darktable user mailing list
to unsubscribe send a mail to [email protected]




darktable user mailing list
to unsubscribe send a mail to [email protected]

Fwd: Fwd: Fwd: Re[2]: Fwd: [darktable-user] darktable suddenly refuses to launch on Manjaro

2023-08-27 Thread Bruce Williams 
Jörn,
No, I definitely had not updated Manjaro between the last successful launch
of darktable, and when it failed.

As for the contents of /etc/fonts/fonts.conf, I don't appear to have either
the directory or the file


*cd ~/etc

cd: no such file or directory: /home/audio2u/etc*

There IS a fonts.conf file in my Home directory though.
Its contents don't extend to line 29, though. Here are the contents of that
file:


























* ~/.fonts  rgb true
   hintslight true
 *

No, I did not mount a camera, although I MAY have had a USB key attached at
the time. Not sure now.
Attempting to launch darktable with camera control disabled yielded this:


























































































































































































*darktable -d camctl

 This GDB supports auto-downloading debuginfo from the
following URLs:  >Enable debuginfod for this session? (y
or [n]) [answered N; input not from terminal]Debuginfod has been
disabled.To make this setting permanent, add 'set debuginfod enabled off'
to .gdbinit.[New LWP 1913][New LWP 1914][New LWP 1915][New LWP 1916][New
LWP 1917][New LWP 1918][New LWP 1919][New LWP 1920][New LWP 1921][New LWP
1922][New LWP 1923][New LWP 1924][New LWP 1925][Thread debugging using
libthread_db enabled]Using host libthread_db library
"/usr/lib/libthread_db.so.1".0x7f6c50cfa8b7 in wait4 () from
/usr/lib/libc.so.6warning: Currently logging to
/tmp/darktable_bt_CGS091.txt.  Turn the logging off and on to make the new
setting effective.#0  0x7f6c50cfa8b7 in wait4 () at
/usr/lib/libc.so.6#1  0x7f6c5119df82 in  () at
/usr/bin/../lib/darktable/libdarktable.so#2  0x7f6c50c3e710 in  () at /usr/lib/libc.so.6#3  0x7f6c50c8fdb4 in
pthread_mutex_lock () at /usr/lib/libc.so.6#4  0x7f6c510c263c in
dt_cache_get_with_caller () at /usr/bin/../lib/darktable/libdarktable.so#5
 0x7f6c51138252 in dt_image_cache_get () at
/usr/bin/../lib/darktable/libdarktable.so#6  0x7f6c5113930d in
dt_image_set_raw_aspect_ratio () at
/usr/bin/../lib/darktable/libdarktable.so#7  0x7f6c510c3ea5 in
dt_collection_update () at /usr/bin/../lib/darktable/libdarktable.so#8
 0x7f6c510d133e in dt_collection_update_query () at
/usr/bin/../lib/darktable/libdarktable.so#9  0x7f6c510c5199 in
dt_collection_new () at /usr/bin/../lib/darktable/libdarktable.so#10
0x7f6c510e4317 in dt_init () at
/usr/bin/../lib/darktable/libdarktable.so#11 0x55e7d683c03d in  ()#12
0x7f6c50c27cd0 in  () at /usr/lib/libc.so.6#13 0x7f6c50c27d8a in
__libc_start_main () at /usr/lib/libc.so.6#14 0x55e7d683c0b5 in
 ()=  Id   Target IdFrame *
1Thread 0x7f6c3f49e680 (LWP 1910) "darktable" 0x7f6c50cfa8b7 in
wait4 () from /usr/lib/libc.so.6  2Thread 0x7f6c3efff6c0 (LWP 1913)
"pool-spawner"  0x7f6c50d0ee2d in syscall () from /usr/lib/libc.so.6  3
   Thread 0x7f6c3e7fe6c0 (LWP 1914) "gmain" 0x7f6c50d0365f in
poll () from /usr/lib/libc.so.6  4Thread 0x7f6c3dffd6c0 (LWP 1915)
"pool"  0x7f6c50d0ee2d in syscall () from /usr/lib/libc.so.6  5
   Thread 0x7f6c3d7fc6c0 (LWP 1916) "gdbus" 0x7f6c50d0365f in
poll () from /usr/lib/libc.so.6  6Thread 0x7f6c3cdd86c0 (LWP 1917)
"worker 0"  0x7f6c50c894ae in ?? () from /usr/lib/libc.so.6  7
 Thread 0x7f6c26c0 (LWP 1918) "worker 1"  0x7f6c50c894ae in ??
() from /usr/lib/libc.so.6  8Thread 0x7f6c2f7fe6c0 (LWP 1919) "worker
2"  0x7f6c50c894ae in ?? () from /usr/lib/libc.so.6  9Thread
0x7f6c2effd6c0 (LWP 1920) "worker 3"  0x7f6c50c894ae in ?? () from
/usr/lib/libc.so.6  10   Thread 0x7f6c2e7fc6c0 (LWP 1921) "kicker"
 0x7f6c50cd58f5 in clock_nanosleep () from /usr/lib/libc.so.6  11
Thread 0x7f6c2dffb6c0 (LWP 1922) "worker res 0"  0x7f6c50c894ae in ??
() from /usr/lib/libc.so.6  12   Thread 0x7f6c2d7fa6c0 (LWP 1923) "worker
res 1"  0x7f6c50c894ae in ?? () from /usr/lib/libc.so.6  13   Thread
0x7f6c2cff96c0 (LWP 1924) "worker res 2"  0x7f6c50c894ae in ?? () from
/usr/lib/libc.so.6  14   Thread 0x7f6c13fff6c0 (LWP 1925) "gphoto_update"
0x7f6c50cd58f5 in clock_nanosleep () from
/usr/lib/libc.so.6=Thread 14 (Thread 0x7f6c13fff6c0 (LWP 1925)
"gphoto_update"):#0  0x7f6c50cd58f5 in clock_nanosleep () at
/usr/lib/libc.so.6#1  0x7f6c50ce7fb7 in nanosleep () at
/usr/lib/libc.so.6#2  0x7f6c50b3d1c1 in g_usleep () at
/usr/lib/libglib-2.0.so.0#3  0x7f6c51312f6b in dt_update_cameras_thread
() at /usr/bin/../lib/darktable/libdarktable.so#4  0x7f6c50c8c9eb in
 () at /usr/lib/libc.so.6#5  0x7f6c50d10ebc in  () at
/usr/lib/libc.so.6Thread 13 (Thread 0x7f6c2cff96c0 (LWP 1924) "worker res
2"):#0  0x7f6c50c894ae in  () at /usr/lib/libc.so.6#1
 0x7f6c50c

Re: Fwd: Fwd: Re[2]: Fwd: [darktable-user] darktable suddenly refuses to launch on Manjaro

2023-08-27 Thread Jörn Rink 
Am Sun, 27 Aug 2023 12:30:54 +1000
hat Bruce Williams  (Bruce Williams) folgendes
geschrieben:

> *Maybe you've already tried that, but if not, here's how to do it:*
> 
> 
> 
> 
> 
> 
> 
> 
> 
> * $ darktable --configdir /path/to/temporary/configdir This will
> create a new default profile at "/path/to/temporary/configdir" and
> should leave your working profile alone. But you do have a backup of
> it, right?! If darktable now starts with it's defaults settings,
> something with your config and/or image database is fishy...*
> 
> 
> Ah-hah!
> THAT made it launch.
> Which is both a good thing and a bad thing.
> No, I don't think I have a backup of my original config.
> When I launched it from the command line, although it launched, the
> command line gave me this:
> 
>    ~  darktable --configdir ~/.config/darktable/test
> 
>  1 ✘
> Fontconfig error: "/etc/fonts/fonts.conf", line 29: not well-formed
> (invalid token)
> Fontconfig error: Cannot load config file from /etc/fonts/fonts.conf
> 1.3400 [lib_load_module] failed to open `midi': libportmidi.so.2:
> cannot open shared object file: No such file or directory
> 
> Not sure if anyone understands what all that means, and if that might
> be the cause of the issue?
> 
> 
> darktable user mailing list
> to unsubscribe send a mail to
> [email protected]
> 

Hi Bruce,
sorry, i only have Fedora, which is a rpm based (redhat) distribution,
and never get in touched with Manjaro.
My thoughts yesterday was: Could it be, that you update Manjaro und
startet successfully darktable the last time without a reboot? And
than, after the reboot a few days later you get the error?

Nevertheless, i looked in my fontconfig, but i saw nothing interesting
in line 29. The fontconfig is not so long, so perhaps you can post it
here.

Googling the libportmidi.so.2 error, which could be the root cause
gives a hint, that dt crashed, when someone connected his Oly EM5 to the
system with "mount camera".

So, perhaps, is anything mounted (or plugged in) when you start dt?
One guy ask him, to start dt with:
darktable -d camctl
that should not be the solution, but perhaps a hint to stdout in the
console.

On my system, there is also no libportmidi installed and i am
wondering, why it is needed.

what gives:
ldd /usr/bin/darktable | grep midi

where /usr/bin/darktable is the path to dt, which you can get with

which darktable?

greetings from germany,


darktable user mailing list
to unsubscribe send a mail to [email protected]

Fwd: Fwd: Re[2]: Fwd: [darktable-user] darktable suddenly refuses to launch on Manjaro

2023-08-26 Thread Bruce Williams 
*Maybe you've already tried that, but if not, here's how to do it:*









* $ darktable --configdir /path/to/temporary/configdir This will create a
new default profile at "/path/to/temporary/configdir" and should leave your
working profile alone. But you do have a backup of it, right?! If darktable
now starts with it's defaults settings, something with your config and/or
image database is fishy...*


Ah-hah!
THAT made it launch.
Which is both a good thing and a bad thing.
No, I don't think I have a backup of my original config.
When I launched it from the command line, although it launched, the command
line gave me this:

   ~  darktable --configdir ~/.config/darktable/test

 1 ✘
Fontconfig error: "/etc/fonts/fonts.conf", line 29: not well-formed
(invalid token)
Fontconfig error: Cannot load config file from /etc/fonts/fonts.conf
1.3400 [lib_load_module] failed to open `midi': libportmidi.so.2:
cannot open shared object file: No such file or directory

Not sure if anyone understands what all that means, and if that might be
the cause of the issue?


darktable user mailing list
to unsubscribe send a mail to [email protected]

Re: Fwd: Fwd: [darktable-user] darktable suddenly refuses to launch on Manjaro

2023-08-26 Thread David Vincent-Jones 

Hi Bruce,

Similar problem here. Running Manjaro/Arch on my old laptop. Current 
daily version


Ran 'darktable -d opencl' ... dt opened and then crashed.

Trace attached:

David

On 2023-08-25 23:11, Bruce Williams wrote:

*Is that just a "plain" run of darktable, which gave the gbd error?*








* You should be able to just start darktable from a terminal emulator like
"Konsole" by typing "darktable" at the prompt. And there's no reason gbd
should be called in that case. Also, is it possible you had done a system
update without immediately rebooting the system, and in that case, did
darktable stop working after a reboot (or restart, logout/login cycle)?
Programs don't just stop working on a system where nothing changed...*



Yes, I just typed 'darktable' at the prompt in konsole.
And as previously stated, I had not updated my system since the last time
darktable had run.
That's what I find confusing.


darktable user mailing list
to unsubscribe send a mail [email protected]


darktable user mailing list
to unsubscribe send a mail to [email protected] is darktable 4.5.0+376~g7c63ad7634 reporting a segfault:

warning: Currently logging to /tmp/darktable_bt_A3G391.txt.  Turn the logging 
off and on to make the new setting effective.
#0  0x7f1545689700 in  () at /usr/lib/libc.so.6
#1  0x7f154568fec2 in pthread_mutex_lock () at /usr/lib/libc.so.6
#2  0x7f1545abcc20 in dt_cache_testget () at 
/usr/bin/../lib/darktable/libdarktable.so
#3  0x7f1545b650df in dt_mipmap_cache_get_with_caller () at 
/usr/bin/../lib/darktable/libdarktable.so
#4  0x7f1545b658a1 in dt_mipmap_cache_get_with_caller () at 
/usr/bin/../lib/darktable/libdarktable.so
#5  0x7f1545d3ed3c in dt_view_image_get_surface () at 
/usr/bin/../lib/darktable/libdarktable.so
#6  0x7f1545cb29c9 in  () at /usr/bin/../lib/darktable/libdarktable.so
#7  0x7f1545cb48be in  () at /usr/bin/../lib/darktable/libdarktable.so
#8  0x7f1544c85039 in  () at /usr/lib/libgtk-3.so.0
#9  0x7f1544f35e9c in  () at /usr/lib/libgtk-3.so.0
#10 0x7f1545486bc9 in g_signal_emit_valist () at 
/usr/lib/libgobject-2.0.so.0
#11 0x7f1545486d34 in g_signal_emit () at /usr/lib/libgobject-2.0.so.0
#12 0x7f1544f484d3 in  () at /usr/lib/libgtk-3.so.0
#13 0x7f1544d0a465 in gtk_container_propagate_draw () at 
/usr/lib/libgtk-3.so.0
#14 0x7f1544d0a576 in  () at /usr/lib/libgtk-3.so.0
#15 0x7f1544f483ba in  () at /usr/lib/libgtk-3.so.0
#16 0x7f1544d0a465 in gtk_container_propagate_draw () at 
/usr/lib/libgtk-3.so.0
#17 0x7f1544d0a576 in  () at /usr/lib/libgtk-3.so.0
#18 0x7f1544f483ba in  () at /usr/lib/libgtk-3.so.0
#19 0x7f1544d0a465 in gtk_container_propagate_draw () at 
/usr/lib/libgtk-3.so.0
#20 0x7f1544d0a576 in  () at /usr/lib/libgtk-3.so.0
#21 0x7f1544ddc988 in  () at /usr/lib/libgtk-3.so.0
#22 0x7f1544c8c34d in  () at /usr/lib/libgtk-3.so.0
#23 0x7f1544f35db3 in  () at /usr/lib/libgtk-3.so.0
#24 0x7f15454676c0 in g_closure_invoke () at /usr/lib/libgobject-2.0.so.0
#25 0x7f1545495e79 in  () at /usr/lib/libgobject-2.0.so.0
#26 0x7f15454864cc in g_signal_emit_valist () at 
/usr/lib/libgobject-2.0.so.0
#27 0x7f1545486d34 in g_signal_emit () at /usr/lib/libgobject-2.0.so.0
#28 0x7f1544f484d3 in  () at /usr/lib/libgtk-3.so.0
#29 0x7f1544d0a465 in gtk_container_propagate_draw () at 
/usr/lib/libgtk-3.so.0
#30 0x7f1544d0a576 in  () at /usr/lib/libgtk-3.so.0
#31 0x7f1544f483ba in  () at /usr/lib/libgtk-3.so.0
#32 0x7f1544d0a465 in gtk_container_propagate_draw () at 
/usr/lib/libgtk-3.so.0
#33 0x7f1544d0a576 in  () at /usr/lib/libgtk-3.so.0
#34 0x7f1544da6ef1 in  () at /usr/lib/libgtk-3.so.0
#35 0x7f1544d0ad71 in  () at /usr/lib/libgtk-3.so.0
#36 0x7f1544d17bdc in  () at /usr/lib/libgtk-3.so.0
#37 0x7f1544da7795 in  () at /usr/lib/libgtk-3.so.0
#38 0x7f1544f483ba in  () at /usr/lib/libgtk-3.so.0
#39 0x7f1544d0a465 in gtk_container_propagate_draw () at 
/usr/lib/libgtk-3.so.0
#40 0x7f1544d0a576 in  () at /usr/lib/libgtk-3.so.0
#41 0x7f1544cb5f01 in  () at /usr/lib/libgtk-3.so.0
#42 0x7f1544d0ad71 in  () at /usr/lib/libgtk-3.so.0
#43 0x7f1544d17bdc in  () at /usr/lib/libgtk-3.so.0
#44 0x7f1544cb6475 in  () at /usr/lib/libgtk-3.so.0
#45 0x7f1544f483ba in  () at /usr/lib/libgtk-3.so.0
#46 0x7f1544d0a465 in gtk_container_propagate_draw () at 
/usr/lib/libgtk-3.so.0
#47 0x7f1544d0a576 in  () at /usr/lib/libgtk-3.so.0
#48 0x7f1544da6ef1 in  () at /usr/lib/libgtk-3.so.0
#49 0x7f1544d0ad71 in  () at /usr/lib/libgtk-3.so.0
#50 0x7f1544d17bdc in  () at /usr/lib/libgtk-3.so.0
#51 0x7f1544da7795 in  () at /usr/lib/libgtk-3.so.0
#52 0x7f1544f483ba in  () at /usr/lib/libgtk-3.so.0
#53 0

Fwd: Fwd: [darktable-user] darktable suddenly refuses to launch on Manjaro

2023-08-25 Thread Bruce Williams 
*Is that just a "plain" run of darktable, which gave the gbd error?*








* You should be able to just start darktable from a terminal emulator like
"Konsole" by typing "darktable" at the prompt. And there's no reason gbd
should be called in that case. Also, is it possible you had done a system
update without immediately rebooting the system, and in that case, did
darktable stop working after a reboot (or restart, logout/login cycle)?
Programs don't just stop working on a system where nothing changed...*



Yes, I just typed 'darktable' at the prompt in konsole.
And as previously stated, I had not updated my system since the last time
darktable had run.
That's what I find confusing.


darktable user mailing list
to unsubscribe send a mail to [email protected]

Fwd: Re[2]: Fwd: [darktable-user] darktable suddenly refuses to launch on Manjaro

2023-08-25 Thread Bruce Williams 
Hmmm, disabling opencl didn't seem to help

darktable --disable-opencl

 ✔

This GDB supports auto-downloading debuginfo from the following URLs:
 
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to
.gdbinit.
[New LWP 2433]
[New LWP 2434]
[New LWP 2435]
[New LWP 2436]
[New LWP 2450]
[New LWP 2451]
[New LWP 2452]
[New LWP 2453]
[New LWP 2454]
[New LWP 2455]
[New LWP 2456]
[New LWP 2457]
[New LWP 2458]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
0x7fdc96afa8b7 in wait4 () from /usr/lib/libc.so.6
warning: Currently logging to /tmp/darktable_bt_AFP891.txt.  Turn the
logging off and on to make the new setting effective.
#0  0x7fdc96afa8b7 in wait4 () at /usr/lib/libc.so.6
#1  0x7fdc96f9df82 in  () at /usr/bin/../lib/darktable/libdarktable.so
#2  0x7fdc96a3e710 in  () at /usr/lib/libc.so.6
#3  0x7fdc96a8fdb4 in pthread_mutex_lock () at /usr/lib/libc.so.6
#4  0x7fdc96ec263c in dt_cache_get_with_caller () at
/usr/bin/../lib/darktable/libdarktable.so
#5  0x7fdc96f38252 in dt_image_cache_get () at
/usr/bin/../lib/darktable/libdarktable.so
#6  0x7fdc96f3930d in dt_image_set_raw_aspect_ratio () at
/usr/bin/../lib/darktable/libdarktable.so
#7  0x7fdc96ec3ea5 in dt_collection_update () at
/usr/bin/../lib/darktable/libdarktable.so
#8  0x7fdc96ed133e in dt_collection_update_query () at
/usr/bin/../lib/darktable/libdarktable.so
#9  0x7fdc96ec5199 in dt_collection_new () at
/usr/bin/../lib/darktable/libdarktable.so
#10 0x7fdc96ee4317 in dt_init () at
/usr/bin/../lib/darktable/libdarktable.so
#11 0x55e8403fa03d in  ()
#12 0x7fdc96a27cd0 in  () at /usr/lib/libc.so.6
#13 0x7fdc96a27d8a in __libc_start_main () at /usr/lib/libc.so.6
#14 0x55e8403fa0b5 in  ()

=

 Id   Target IdFrame
* 1Thread 0x7fdc8538f680 (LWP 2431) "darktable" 0x7fdc96afa8b7
in wait4 () from /usr/lib/libc.so.6
 2Thread 0x7fdc84fff6c0 (LWP 2433) "pool-spawner"  0x7fdc96b0ee2d
in syscall () from /usr/lib/libc.so.6
 3Thread 0x7fdc847fe6c0 (LWP 2434) "gmain" 0x7fdc96b0365f
in poll () from /usr/lib/libc.so.6
 4Thread 0x7fdc83ffd6c0 (LWP 2435) "pool"  0x7fdc96b0ee2d
in syscall () from /usr/lib/libc.so.6
 5Thread 0x7fdc837fc6c0 (LWP 2436) "gdbus" 0x7fdc96b0365f
in poll () from /usr/lib/libc.so.6
 6Thread 0x7fdc82cd26c0 (LWP 2450) "worker 0"  0x7fdc96a894ae
in ?? () from /usr/lib/libc.so.6
 7Thread 0x7fdc824d16c0 (LWP 2451) "worker 1"  0x7fdc96a894ae
in ?? () from /usr/lib/libc.so.6
 8Thread 0x7fdc81cd06c0 (LWP 2452) "worker 2"  0x7fdc96a894ae
in ?? () from /usr/lib/libc.so.6
 9Thread 0x7fdc814cf6c0 (LWP 2453) "worker 3"  0x7fdc96a894ae
in ?? () from /usr/lib/libc.so.6
 10   Thread 0x7fdc80cce6c0 (LWP 2454) "kicker"0x7fdc96ad58f5
in clock_nanosleep () from /usr/lib/libc.so.6
 11   Thread 0x7fdc7bfff6c0 (LWP 2455) "worker res 0"  0x7fdc96a894ae
in ?? () from /usr/lib/libc.so.6
 12   Thread 0x7fdc7b7fe6c0 (LWP 2456) "worker res 1"  0x7fdc96a894ae
in ?? () from /usr/lib/libc.so.6
 13   Thread 0x7fdc7affd6c0 (LWP 2457) "worker res 2"  0x7fdc96a894ae
in ?? () from /usr/lib/libc.so.6
 14   Thread 0x7fdc7a7fc6c0 (LWP 2458) "gphoto_update" 0x7fdc96ad58f5
in clock_nanosleep () from /usr/lib/libc.so.6

=

Thread 14 (Thread 0x7fdc7a7fc6c0 (LWP 2458) "gphoto_update"):
#0  0x7fdc96ad58f5 in clock_nanosleep () at /usr/lib/libc.so.6
#1  0x7fdc96ae7fb7 in nanosleep () at /usr/lib/libc.so.6
#2  0x7fdc96cec1c1 in g_usleep () at /usr/lib/libglib-2.0.so.0
#3  0x7fdc97112f6b in dt_update_cameras_thread () at
/usr/bin/../lib/darktable/libdarktable.so
#4  0x7fdc96a8c9eb in  () at /usr/lib/libc.so.6
#5  0x7fdc96b10ebc in  () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7fdc7affd6c0 (LWP 2457) "worker res 2"):
#0  0x7fdc96a894ae in  () at /usr/lib/libc.so.6
#1  0x7fdc96a8bd40 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7fdc96fac6ae in  () at /usr/bin/../lib/darktable/libdarktable.so
#3  0x7fdc96a8c9eb in  () at /usr/lib/libc.so.6
#4  0x7fdc96b10ebc in  () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7fdc7b7fe6c0 (LWP 2456) "worker res 1"):
#0  0x7fdc96a894ae in  () at /usr/lib/libc.so.6
#1  0x7fdc96a8bd40 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7fdc96fac6ae in  () at /usr/bin/../lib/darktable/libdarktable.so
#3  0x7fdc96a8c9eb in  () at /usr/lib/libc.so.6
#4  0x7fdc96b10ebc in  () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7fdc7bfff6c0 (LWP 2455) "worker res 0"):
#0  0x7fdc96a894ae in  () at /usr/lib/libc.so.6
#1  0x7fdc96a8bd40 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7fdc96fac6ae in  () at /usr/bin/

Re[2]: Fwd: [darktable-user] darktable suddenly refuses to launch on Manjaro

2023-08-25 Thread Manuel Presnitz 


> You should be able to just start darktable from a terminal emulator
> like  "Konsole" by typing "darktable" at the prompt.

And while at it, try to start darktable without OpenCL (the last seg
faults I experienced have all been caused by that), like so:

$ darktable --disable-opencl


Regards,
Manuel.



darktable user mailing list
to unsubscribe send a mail to [email protected]

Re: Fwd: [darktable-user] darktable suddenly refuses to launch on Manjaro

2023-08-25 Thread Remco Viëtor 
On vendredi 25 août 2023 14:31:53 CEST Bruce Williams wrote:
> No, I had not!
> This was the error thrown by the terminal:
> 
> an error occurred while trying to execute gdb. please check if gdb is
> installed on your system.
> backtrace written to /tmp/darktable_bt_XHGFA2.txt
> zsh: segmentation fault (core dumped)  darktable
> 
> I tried "nano /tmp/darktable_bt_XHGFA2.txt" but it appears to have nothing
> in the text file.
> 

Is that just a "plain" run of darktable, which gave the gbd error?

You should be able to just start darktable from a terminal emulator like 
"Konsole" by typing "darktable" at the prompt. And there's no reason gbd 
should be called in that case.

Also, is it possible you had done a system update without immediately 
rebooting the system, and in that case, did darktable stop working after a 
reboot (or restart, logout/login cycle)? Programs don't just stop working on a 
system where nothing changed...

> 
> -- Forwarded message -
> From: Jesus Arocho 
> Date: Fri, Aug 25, 2023 at 10:19 PM
> Subject: Re: [darktable-user] darktable suddenly refuses to launch on
> Manjaro
> To: Bruce Williams 
> 
> 
> 
> On 8/25/23 07:45, Bruce Williams wrote:
> 
> Hi all,
> I'm running Manjaro, and have had darktable 4.4 running just fine in recent
> days.
> But tonight, I tried to launch it, the icon appears for a second, and then
> disappears.
> System monitor does not show it amongst the running applications.
> 
> System specs:
> 
> Operating System: Manjaro Linux
> KDE Plasma Version: 5.27.7
> KDE Frameworks Version: 5.108.0
> Qt Version: 5.15.10
> Kernel Version: 6.1.44-1-MANJARO (64-bit)
> Graphics Platform: X11
> Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor
> Memory: 31.3 GiB of RAM
> Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2
> Manufacturer: Micro-Star International Co., Ltd.
> Product Name: MS-7B79
> System Version: 2.0
> 
> I do not have auto updating of the system running due to some issues with
> the GUI version of PAMAC. I do manual system updates via the command line,
> and I have not done any since I last ran dt.
> If anyone can point me in the right direction to get it launching, I would
> be most thankful.
> 
> Have you tried to launch darktable from a terminal window to see if an
> error message is displayed?
> 
> 
> darktable user mailing list
> to unsubscribe send a mail to [email protected]





darktable user mailing list
to unsubscribe send a mail to [email protected]

Fwd: [darktable-user] darktable suddenly refuses to launch on Manjaro

2023-08-25 Thread Bruce Williams 
#0  0x7fc70eed58f5 in clock_nanosleep () at /usr/lib/libc.so.6
#1  0x7fc70eee7fb7 in nanosleep () at /usr/lib/libc.so.6
#2  0x7fc70eef8f1e in sleep () at /usr/lib/libc.so.6
#3  0x7fc70f3ac993 in  () at /usr/bin/../lib/darktable/libdarktable.so
#4  0x7fc70ee8c9eb in  () at /usr/lib/libc.so.6
#5  0x7fc70ef10ebc in  () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7fc6f57586c0 (LWP 3922) "worker 3"):
#0  0x7fc70ee894ae in  () at /usr/lib/libc.so.6
#1  0x7fc70ee8bd40 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7fc70f3acca2 in  () at /usr/bin/../lib/darktable/libdarktable.so
#3  0x7fc70ee8c9eb in  () at /usr/lib/libc.so.6
#4  0x7fc70ef10ebc in  () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7fc6f5f596c0 (LWP 3921) "worker 2"):
#0  0x7fc70ee894ae in  () at /usr/lib/libc.so.6
#1  0x7fc70ee8bd40 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7fc70f3acca2 in  () at /usr/bin/../lib/darktable/libdarktable.so
#3  0x7fc70ee8c9eb in  () at /usr/lib/libc.so.6
#4  0x7fc70ef10ebc in  () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7fc6f675a6c0 (LWP 3920) "worker 1"):
#0  0x7fc70ee894ae in  () at /usr/lib/libc.so.6
#1  0x7fc70ee8bd40 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7fc70f3acca2 in  () at /usr/bin/../lib/darktable/libdarktable.so
#3  0x7fc70ee8c9eb in  () at /usr/lib/libc.so.6
#4  0x7fc70ef10ebc in  () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7fc6f6f5b6c0 (LWP 3919) "worker 0"):
#0  0x7fc70ee894ae in  () at /usr/lib/libc.so.6
#1  0x7fc70ee8bd40 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7fc70f3acca2 in  () at /usr/bin/../lib/darktable/libdarktable.so
#3  0x7fc70ee8c9eb in  () at /usr/lib/libc.so.6
#4  0x7fc70ef10ebc in  () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7fc6f77fe6c0 (LWP 3918) "gdbus"):
#0  0x7fc70ef0365f in poll () at /usr/lib/libc.so.6
#1  0x7fc70ed6cc2f in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fc70ed0efef in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#3  0x7fc70e10f28c in  () at /usr/lib/libgio-2.0.so.0
#4  0x7fc70ed41d75 in  () at /usr/lib/libglib-2.0.so.0
#5  0x7fc70ee8c9eb in  () at /usr/lib/libc.so.6
#6  0x7fc70ef10ebc in  () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7fc6f7fff6c0 (LWP 3917) "pool"):
#0  0x7fc70ef0ee2d in syscall () at /usr/lib/libc.so.6
#1  0x7fc70ed65533 in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0
#2  0x7fc70ecda115 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fc70ecda277 in g_async_queue_timeout_pop () at
/usr/lib/libglib-2.0.so.0
#4  0x7fc70ed44bee in  () at /usr/lib/libglib-2.0.so.0
#5  0x7fc70ed41d75 in  () at /usr/lib/libglib-2.0.so.0
#6  0x7fc70ee8c9eb in  () at /usr/lib/libc.so.6
#7  0x7fc70ef10ebc in  () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7fc6fc9fe6c0 (LWP 3916) "gmain"):
#0  0x7fc70ef0365f in poll () at /usr/lib/libc.so.6
#1  0x7fc70ed6cc2f in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fc70ed0d0e2 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fc70ed0d132 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fc70ed41d75 in  () at /usr/lib/libglib-2.0.so.0
#5  0x7fc70ee8c9eb in  () at /usr/lib/libc.so.6
#6  0x7fc70ef10ebc in  () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7fc6fd1ff6c0 (LWP 3915) "pool-spawner"):
#0  0x7fc70ef0ee2d in syscall () at /usr/lib/libc.so.6
#1  0x7fc70ed64ca7 in g_cond_wait () at /usr/lib/libglib-2.0.so.0
#2  0x7fc70ecda144 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fc70ed442fe in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fc70ed41d75 in  () at /usr/lib/libglib-2.0.so.0
#5  0x7fc70ee8c9eb in  () at /usr/lib/libc.so.6
#6  0x7fc70ef10ebc in  () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7fc6fd65e680 (LWP 3913) "darktable"):
#0  0x7fc70eefa8b7 in wait4 () at /usr/lib/libc.so.6
#1  0x7fc70f39df82 in  () at /usr/bin/../lib/darktable/libdarktable.so
#2  0x7fc70ee3e710 in  () at /usr/lib/libc.so.6
#3  0x7fc70ee8fdb4 in pthread_mutex_lock () at /usr/lib/libc.so.6
#4  0x7fc70f2c263c in dt_cache_get_with_caller () at
/usr/bin/../lib/darktable/libdarktable.so
#5  0x7fc70f338252 in dt_image_cache_get () at
/usr/bin/../lib/darktable/libdarktable.so
#6  0x7fc70f33930d in dt_image_set_raw_aspect_ratio () at
/usr/bin/../lib/darktable/libdarktable.so
#7  0x7fc70f2c3ea5 in dt_collection_update () at
/usr/bin/../lib/darktable/libdarktable.so
#8  0x7fc70f2d133e in dt_collection_update_query () at
/usr/bin/../lib/darktable/libdarktable.so
#9  0x7fc70f2c5199 in dt_collection_new () at
/usr/bin/../lib/darktable/libdarktable.so
#10 0x7fc70f2e4317 in dt_init () at
/usr/bin/../lib/darktable/libdarktable.so
#11 0x55c587e6403d in  ()
#12 0x7fc70ee27cd0 in  () at /usr/lib/libc.so.6
#13 0x7fc70ee27d8a in __libc_start_main () at /usr/lib/libc.so.6
#14 0x55c587e640b5 in

Fwd: [darktable-user] darktable suddenly refuses to launch on Manjaro

2023-08-25 Thread Bruce Williams 
No, I had not!
This was the error thrown by the terminal:

an error occurred while trying to execute gdb. please check if gdb is
installed on your system.
backtrace written to /tmp/darktable_bt_XHGFA2.txt
zsh: segmentation fault (core dumped)  darktable

I tried "nano /tmp/darktable_bt_XHGFA2.txt" but it appears to have nothing
in the text file.


-- Forwarded message -
From: Jesus Arocho 
Date: Fri, Aug 25, 2023 at 10:19 PM
Subject: Re: [darktable-user] darktable suddenly refuses to launch on
Manjaro
To: Bruce Williams 



On 8/25/23 07:45, Bruce Williams wrote:

Hi all,
I'm running Manjaro, and have had darktable 4.4 running just fine in recent
days.
But tonight, I tried to launch it, the icon appears for a second, and then
disappears.
System monitor does not show it amongst the running applications.

System specs:

Operating System: Manjaro Linux
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Kernel Version: 6.1.44-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7B79
System Version: 2.0

I do not have auto updating of the system running due to some issues with
the GUI version of PAMAC. I do manual system updates via the command line,
and I have not done any since I last ran dt.
If anyone can point me in the right direction to get it launching, I would
be most thankful.

Have you tried to launch darktable from a terminal window to see if an
error message is displayed?


darktable user mailing list
to unsubscribe send a mail to [email protected]