CONTENTS DELETED
The author has deleted this message.
|
I have exactly the same issue.
|
Same here. I finally gave up and re-installed back to 1.9 and re-built my database.
Kodachrome, "The color of memories." On Apr 14, 2011, at 5:58 PM, bowens44 <[hidden email]> wrote: > I have exactly the same issue. > > -- > View this message in context: http://digikam.1695700.n4.nabble.com/Update-problems-tp3450947p3451032.html > Sent from the digikam-users mailing list archive at Nabble.com. > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Last thing I did yesterday was update. So your messages made me curious
this morning. Yep same issue! Tried to run digikam from console and that works!!!!!!!!!!!! On 15-04-11 05:18, Stewart & Jenny wrote: > Same here. I finally gave up and re-installed back to 1.9 and re-built my database. > > > Kodachrome, "The color of memories." > > > > > On Apr 14, 2011, at 5:58 PM, bowens44<[hidden email]> wrote: > >> I have exactly the same issue. >> >> -- >> View this message in context: http://digikam.1695700.n4.nabble.com/Update-problems-tp3450947p3451032.html >> Sent from the digikam-users mailing list archive at Nabble.com. >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
I updated ubuntu again, and saw some lensfuc stuff passing by. Now the
whole issue is solved. Digikam start normaly. hoorah! Hurray! Another day of happy digikamming is on itś way. That will keep the dokter away. kind regards Rinus On 15-04-11 08:44, sleepless wrote: > Last thing I did yesterday was update. So your messages made me curious > this morning. Yep same issue! > > Tried to run digikam from console and that works!!!!!!!!!!!! > > On 15-04-11 05:18, Stewart& Jenny wrote: >> Same here. I finally gave up and re-installed back to 1.9 and re-built my database. >> >> >> Kodachrome, "The color of memories." >> >> >> >> >> On Apr 14, 2011, at 5:58 PM, bowens44<[hidden email]> wrote: >> >>> I have exactly the same issue. >>> >>> -- >>> View this message in context: http://digikam.1695700.n4.nabble.com/Update-problems-tp3450947p3451032.html >>> Sent from the digikam-users mailing list archive at Nabble.com. >>> _______________________________________________ >>> Digikam-users mailing list >>> [hidden email] >>> https://mail.kde.org/mailman/listinfo/digikam-users >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users >> > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Jenny Torango
That's my bad in packaging. I made a workaround for the problem to use the import camera feature in beta4 by preloding libusb.so. Otherwise beta4 crashes if you try to import from a device that use libgphoto as backend. I pointed the preload to a file that is only in package libusb-dev. I'll upload a fix for this but meanwhile you can install libusb-dev to make it work again. You can also start digikam from command line.
If anyone wonders the preloading happens in /usr/share/applications/kde4/digikam.desktop that I tweaked in beta4 as a workaround. I think there is a real fix for the bug I made the workaround for will be available in beta5. Sorry for the mishap. /Philip On Fri, Apr 15, 2011 at 5:18 AM, Stewart & Jenny <[hidden email]> wrote: Same here. I finally gave up and re-installed back to 1.9 and re-built my database. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Phillip , Thank you for the response and all the work you have done on this. It's excellent!
Launching from the terminal does allow Digikam to run. I have libusb-dev installed but still can't launch from the menu. I still get "Could not launch digiKam Failed to execute child process "LD_PRELOAD=/usr/lib/libusb.so" (No such file or directory)" The file does exist $ locate libusb.so /lib32/libusb.so /usr/lib/libusb.so |
The update on my kubuntu-backports PPA is now available. This problem in all cases should be fixed on Ubuntu 10.10 with digikam2 package 2.0.0~beta4+maverick~ppa3kde46 and you don't need libusb-dev with the update. If more people have this kind of problem I'll remove the workaround but it should work (works fine for me here).
/Philip On Fri, Apr 15, 2011 at 1:56 PM, bowens44 <[hidden email]> wrote: Phillip , Thank you for the response and all the work you have done on this. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Have anyone with this problem tried the update and if so could he/she confirm if it solved the problem or if it still remain.
/Philip On Fri, Apr 15, 2011 at 3:18 PM, Philip Johnsson <[hidden email]> wrote: The update on my kubuntu-backports PPA is now available. This problem in all cases should be fixed on Ubuntu 10.10 with digikam2 package 2.0.0~beta4+maverick~ppa3kde46 and you don't need libusb-dev with the update. If more people have this kind of problem I'll remove the workaround but it should work (works fine for me here). _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
The update did not make a difference for me.
I still get "Could not launch digiKam Failed to execute child process "LD_PRELOAD=/usr/lib/libusb.so" (No such file or directory)" |
If you still get "Failed to execute child process "LD_PRELOAD=/usr/lib/libusb.so" (No such file or directory)" after the update there is something wrong as there shouldn't be any more references to /usr/lib/libusb.so anymore but "/lib/libusb-0.1.so.4"
Are you sure that no packages are hold back or something that when you update? Make sure that the package version number of package digikam2 is 2.0.0~beta4+maverick~ppa3kde46. /Philip
On Fri, Apr 15, 2011 at 10:51 PM, bowens44 <[hidden email]> wrote: The update did not make a difference for me. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
I did an apt-get --purge remove digikam2* kipi*
I then reinstalled digikam2 I still get "Could not launch digiKam Failed to execute child process "LD_PRELOAD=/usr/lib/libusb.so" (No such file or directory)" when launching from the menu. ~$ sudo dpkg -l | grep digikam* ii digikam2 2:2.0.0~beta4+maverick~ppa3kde46 digital photo management application for KDE ii digikam2-data 2:2.0.0~beta4+maverick~ppa3kde46 digikam architecture-independant data i'm not sure what is happening but if it's just me then obviously something is wrong on my side. |
Look if you have saved a custom menu entry for Digikam. Check in ~/.local/share/applications/ if you have a file called kde4-digikam.desktop or maybe digikam.desktop. In that case it's a user saved menu entry that overrides the updated system wide menu. If you have it and remove it you might need to log out and in again to repopulate the menu with the system wide version of the menu file.
If you do this with the KDE Menu Editor you should have "LD_PRELOAD=/lib/libusb-0.1.so.4 digikam -caption "%c" %i" in the field "Command:" for the Digikam menu entry. The "LD_PRELOAD=/lib/libusb-0.1.so.4" is a workaround against crashes in beta4 when you try to import images from a camera that uses libgphoto2, usually PTP cameras. The old workaround was "LD_PRELOAD=/usr/lib/libusb.so" but shouldn't be used by non developers. Hope this make any sense. /Philip On Sat, Apr 16, 2011 at 12:04 AM, bowens44 <[hidden email]> wrote: I did an apt-get --purge remove digikam2* kipi* _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
CONTENTS DELETED
The author has deleted this message.
|
In reply to this post by Philip Johnsson
CONTENTS DELETED
The author has deleted this message.
|
In reply to this post by david-vj
David,
That warning you get is something else and have nothing to do with this problem with the workaround or packaging. If the workaround brings problems to some I might better remove it but then beta4 will crash when you try to import pictures from many cameras. /Philip On Sat, Apr 16, 2011 at 12:37 AM, David Vincent-Jones <[hidden email]> wrote:
Interim feedback: _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
CONTENTS DELETED
The author has deleted this message.
|
David,
Do you get any error messages if you start Digikam 2.0 beta4 from command line with this as command "LD_PRELOAD=/lib/libusb-0.1.so.4 digikam" (without the "")? Looks like the problem for you is with preload. Btw, are you using Digikam with KDE or Gnome? /Philip On Sat, Apr 16, 2011 at 1:07 AM, davidvj <[hidden email]> wrote: Not fully tested but: _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Philip Johnsson
I deleted kde4-digikam.desktop, logged out and back in. Things have changed, now I get:
"Could not launch digiKam Failed to execute child process "LD_PRELOAD=/usr/lib/libusb-0.1.so.4" (No such file or directory)" file does exist in the specified directory. ~$ locate libusb-0.1.so.4 /lib/libusb-0.1.so.4 /lib/libusb-0.1.so.4.4.4 /lib32/libusb-0.1.so.4 /lib32/libusb-0.1.so.4.4.4 /usr/lib/libusb-0.1.so.4 /usr/lib32/libusb-0.1.so.4 |
In reply to this post by Philip Johnsson
CONTENTS DELETED
The author has deleted this message.
|
Free forum by Nabble | Edit this page |