Home > Unknown Error > Unknown Error Code 150 Kde

Unknown Error Code 150 Kde

Digikam still works, also in normal mode with the camera attached. Application may misbehave. If yes: Click the star below ✰ Reply With Quote 03-Apr-2011,22:25 #3 ceramics View Profile View Forum Posts View Blog Entries View Articles Newcomer Join Date Apr 2011 Location New Zealand Format For Printing -XML -Clone This Bug -Top of page First Last Prev Next This bug is not in your last search results. this contact form

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. As user dolphin shows no files (camera:/). BTW, accessing the pictures in my camera using "camera:/" works nicely here in KDE 4.10 as provided by Opensuse. In KDE Bug Tracking System #264020, Frank78ac (frank78ac) wrote on 2013-06-18: #23 (In reply to comment #5) > [quote]Unknown error code 150 > Bad parameters > Please send a full bug https://bugs.kde.org/show_bug.cgi?id=319311

I'm sure this has happened with 11.3 updates as well. In KDE Bug Tracking System #326607, Frank78ac (frank78ac) wrote on 2013-10-25: #9 Thanks for the quick reply! (In reply to comment #2) > The camera does not appear at all, anywhere. Comment on this change (optional) Email me about changes to this bug report libgphoto Edit New Undecided Unassigned Edit You need to log in to change this bug's status.

Information forwarded to [email protected], Debian Qt/KDE Maintainers : Bug#682561; Package dolphin. (Mon, 23 Jul 2012 18:21:03 GMT) Full text and rfc822 format available. I'm already working on a more robust "startup" code for Dolphin. Reproducible: Always Steps to Reproduce: Login to KDE as common user, connect camera to PC, start Dolphin or Krusader, type camera:/ into address line, press enter (or any similar process, eg. I'm trying to connect my Galaxy Nexus (Android 4.1) and browse some the filesystem. * What exactly did you do (or not do) that was effective (or ineffective)?

I observe continuos problem with camera:/ protocol in KDE 4.x.y - this protocol worked without problem in KDE 3.5.x. In KDE Bug Tracking System #264020, Jirka (zaloha) wrote on 2011-01-22: #15 The "workaround" is to use Digikam, but I don't want to do it - I prefer working with photos Could be, but I'm not really familiar with the details of the interaction between KDirLister and the kioslaves. Read More Here You get the error message: Unknown error code 150 Unspecified error Please send a full bug report at https://bugs.kde.org.

I noticed something was wrong when Dolphin showed my home directory rather than the camera's content. Dolphin does not. However, with two other compact camera's I have been using recently, I have have exactly the same experience: 'Fujifilm' and 'Traveller'. Comment 6 EMR_Kde 2016-10-30 00:54:15 UTC same problem here, Leap 42.1 Format For Printing -XML -Clone This Bug -Top of page Home | New | Browse | Search | [?] |

  • I get nothing at all if I try to connect to "auto detected camera".
  • Dolphin as root sees it under camera: but cannot navigate down to the photos.
  • Cheers Dolphin doesn't work but I can access the camera through a gnome menu.
  • If anyone who cannot fix the problem with the suggestion from comment 14 thinks I'm wrong, please tell me what you think we're doing wrong when we try to access "camera:"
  • kcmshell4 kamera 2.
  • Screenshot of the error.
  • It happens to seem to work for root, because by changing user new session (kdeinit, klauncher, kded, and dbus) is created.
  • I don't know if yours is the same.

Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. have a peek at these guys Affecting: Linux Mint Filed here by: Mauro When: 2014-09-15 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation PowerShot A495 Bus 003 Device 003: ID 1bcf:2c55 Sunplus Innovation Technology Inc. Connect Samsung Galaxy phone via USB to Linux workstation.

Toggle useless messagesView this report as an mbox folder, status mbox, maintainer mbox Report forwarded to [email protected], Debian Qt/KDE Maintainers : Bug#682561; Package dolphin. (Mon, 23 Jul 2012 17:42:04 GMT) Full weblink Message #5 received at [email protected] (full text, mbox, reply): From: mourad To: Debian Bug Tracking System Subject: dolphin: Fail to browse MTP directory Date: Mon, 23 Jul 2012 19:37:41 Yes, but they'll be accessing the usb interface with root permissions via the host. My original configuration was KDE-4.10.5, libgphoto 2.5.2.

Since the underlaying system works and the top KDE application layer does not, my assumption is that it breaks somewhere in the KIO... ? I'm confused on what is wrong. Anyway, try rebooting with a clean KDE session, reconnect the camera, and see if that fixes things for you. navigate here View in Dolphin 3.

However, Gwenview uses a camera:/ URI and works fine. Thank you for reporting this bug and we are sorry it could not be fixed. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates.

Thanks for your feedback!

I installed the camera thru System Settings - Digital Camera as a "Nikon D50 PTP" I then downloaded the latest libgphoto2-2.5.7 and edited "camlibs/ptp2/library.c" and changed the appropriate line for my If I try to browse "Mass Storage Camera" folder : An unknown error 150 is fired (sorry it is in french) : "Code d'erreur 150 inconnu Mauvais paramètres Veuillez envoyer un Click the Portable Media Player that shows up and then Open With File Manager. > Dolphin starts. Acknowledgement sent to Scott Kitterman : Extra info received and forwarded to list.

My very wild guess would be timing issue (kdeinit (its children)/DBus), race during session creation. In KDE Bug Tracking System #326607, Frank78ac (frank78ac) wrote on 2013-10-25: #6 Thanks for the bug report. (In reply to comment #0) > 1. Dolphin does not. his comment is here I did an fdisk -l as requested (results below) and also an lsusb.

Launchpad Janitor (janitor) wrote on 2013-12-19: #3 Status changed to 'Confirmed' because the bug affects multiple users. Application may misbehave. In KDE Bug Tracking System #264020, Emmanuelpescosta099 (emmanuelpescosta099) wrote on 2013-12-17: #32 > I noticed something was wrong when Dolphin showed my home directory rather than > the camera's content. If you experience problems, please add a comment to this bug.

In KDE Bug Tracking System #264020, Frank78ac (frank78ac) wrote on 2014-02-02: #48 I could never reproduce this bug, but I haven't tried in a while, so I just tried it with I can get to the photos using Konquerer. lsusb sees camera correctly. Reproducible: Always Steps to Reproduce: 1.

I am able to reproduce the problem with Kubuntu 13.10 also with konqueror.