Page 1 of 1
digikam not starting
Posted:
Mar 25th, '14, 07:00by barry-m
my system was all Mageia3 but I have just upgraded digikam to Mageia 4 from the d/l DVD. Digikam still fails to start, from a terminal I get 'Illegal instruction".
Running strace -f digikam ends with ' +++ killed by SIGKILL +++ Illegal instruction'. The upgrade did not fix the problem
I see problems have occurred with nvidia drivers. Mine is not nvidia.
What tests can I make to trace the problem
thanks
Re: digikam not starting
Posted:
Mar 26th, '14, 02:43by doktor5000
Did you try an urpmi --auto-update after the upgrade via DVD?
Please provide the output from urpmi --list-media active.
After trying doing that, please try digikam under a freshly created user, does the problem persist?
Re: digikam not starting
Posted:
Mar 26th, '14, 09:17by oldcodger
FWIW I have Digikam running on two machines, one pc an one laptop. No problems. That would seem to say that your problem is local to your setup.
I know it's not an answer but it should narrow down the search for you.
Re: digikam not starting
Posted:
Mar 26th, '14, 22:12by doktor5000
Can you try to move away / rename at least (do NOT delete them, or your digikam settings will be reset to defaults) as normal user
- Code: Select all
~/.kde4/share/apps/digikam
~/.kde4/share/config/digikamrc
Or maybe there's an issue with your album, to locate it in your home directory you could run as normal user:
- Code: Select all
find ~ -iname "*digikam*"
Re: digikam not starting
Posted:
Mar 30th, '14, 09:34by barry-m
Since my 1st msg I have done a full install of Mageia4 on a clean ptn, then ran update from Mageia control centre. When I run digikam from a terminal I still get the 'illegal instruction' msg.
This has created a new digikamrc file. All updates are installed.
strace -f digikam exits with +++ killed by SIGILL +++
fstab was backed up before the install, and copied back after. The following were then reactivated with 'mount -a '. ~/Photos, ~/Movies, ~/Documents, ~/store are each on separate ptns and are now accessable and have no problems
I think this has dealt with all the suggestions, thanks
More ideas welcome
Re: digikam not starting
Posted:
Mar 30th, '14, 10:58by doktor5000
barry-m wrote:I think this has dealt with all the suggestions, thanks
Nope.
doktor5000 wrote:Please provide the output from urpmi --list-media active.
After trying doing that, please try digikam under a freshly created user, does the problem persist?
When reinstalling, did you keep your /home or did you format it/create a new one?
FWIW, digikam works fine here on several boxes.
Re: digikam not starting
Posted:
Mar 31st, '14, 01:16by barry-m
[root@TheBox barry]$ urpmi --list-media active
Unknown option: list-media Not an option on the man page, what have I missed?
No package named active
The problem is the same with a new user.
/home was copied to another ptn, the / ptn reformatted so giving a new /home. Then .bashrc copied back to the new /home dir
Re: digikam not starting
Posted:
Mar 31st, '14, 01:21by Ken-Bergen
It should be
- Code: Select all
urpmq --list-media active
Re: digikam not starting
Posted:
Mar 31st, '14, 01:45by barry-m
Is this related to bug 10815?
Re: digikam not starting
Posted:
Mar 31st, '14, 01:48by barry-m
- Code: Select all
[barry@TheBox ~]$ urpmq --list-media active
Mageia 4 DVD core
Mageia 4 DVD non free
Core Updates (distrib1)
Nonfree Updates (distrib2)
Tainted Updates (distrib3)
Core 32bit Updates (distrib4)
Nonfree 32bit Updates (distrib5)
Tainted 32bit Updates (distrib6)
Core Release (distrib7)
Core Updates (distrib9)
Core Updates Testing (distrib11)
Core Backports (distrib13)
Core Backports Testing (distrib15)
Nonfree Release (distrib17)
Nonfree Updates (distrib19)
Nonfree Updates Testing (distrib21)
Nonfree Backports Debug (distrib24)
Tainted Release (distrib27)
Tainted Updates (distrib29)
Tainted Updates Testing (distrib31)
Tainted Backports (distrib33)
Tainted Backports Debug (distrib34)
Core 32bit Release (distrib37)
Core 32bit Updates (distrib38)
Core 32bit Updates Testing (distrib39)
Core 32bit Backports (distrib40)
Nonfree 32bit Release (distrib42)
Nonfree 32bit Updates (distrib43)
Nonfree 32bit Updates Testing (distrib44)
Nonfree 32bit Backports (distrib45)
Tainted 32bit Release (distrib47)
Tainted 32bit Updates (distrib48)
Tainted 32bit Updates Testing (distrib49)
Re: digikam not starting
Posted:
Apr 6th, '14, 00:54by barry-m
Have now tried to run using gdm /usr/bin/digikam - so looks like opencv is the problem.
How do I fix this? please
(gdb) run
Starting program: /usr/bin/digikam
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Program received signal SIGILL, Illegal instruction.
0x00007fffee7ad562 in cv::initInterTab2D(int, bool) () from /lib64/libopencv_imgproc.so.2.4
(gdb)
(gdb) where
#0 0x00007fffee7ad562 in cv::initInterTab2D(int, bool) () from /lib64/libopencv_imgproc.so.2.4
#1 0x00007fffee763bf2 in _GLOBAL__sub_I_imgwarp.cpp () from /lib64/libopencv_imgproc.so.2.4
#2 0x00007ffff7decaba in call_init.part.0 () from /lib64/ld-linux-x86-64.so.2
#3 0x00007ffff7decba3 in _dl_init_internal () from /lib64/ld-linux-x86-64.so.2
#4 0x00007ffff7ddf1ea in _dl_start_user () from /lib64/ld-linux-x86-64.so.2
#5 0x0000000000000001 in ?? ()
#6 0x00007fffffffe37d in ?? ()
#7 0x0000000000000000 in ?? ()
(gdb)