> Unknown Error
> Unknown Error Code 150 Kde
Unknown Error Code 150 Kde
I do suspect that this is a "permissions" problem, but don't know where to set things up in openSuse. dmesg | tail; lsusb; lsb_release -a ** [32457.654052] usb 2-5: Product: Digital Camera Bus 002 Device 002: ID 04cb:01e8 Fuji Photo Film Co., Ltd ** No LSB modules are available. Everything worked fine with 12.04. With Kubuntu 13.10, KDE 4.11.3, Canon PowerShot A495: $ solid-hardware query "Camera.supportedDrivers == 'gphoto'" Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-6' $ lsusb Bus 002 http://fullflash.net/unknown-error/unknown-error-code-259.html
I tried all the ones in your first reply, and camera:/ in Dolphin's location bar gives the following error "Unknown error code 150 Bad parameters Please send a full bug report Comment 12 Emmanuel Pescosta 2013-07-24 20:37:27 UTC I can reproduce this bug with Dolphin and with Krusader. > does accessing the camera work for you in Digikam? KDE 4.10.5, gphoto 2.5.2, dbus 1.6.12). Screenshot of the error. https://bugs.kde.org/show_bug.cgi?id=319311
Comment 32 sylvainsjc 2014-01-28 14:33:01 UTC (In reply to comment #31) > if i run "kdeinit4" in a konsole as user everything works fine. User contributions on this site are licensed under the Creative Commons Attribution Share Alike 4.0 International License. Nothing is visible. I did some fixes since 2010 to the kio slave that probably avoiid the error 150, but I cannot say for sure.
- In KDE Bug Tracking System #326607, wrapperband (drajdoyle) wrote on 2013-10-25: #7 Cheers for the question.
- The process described above works correctly in root mode of Dolphin or Krusader, or in root system session (login to KDE as root).
- PowerShot A495 Bus 003 Device 003: ID 1bcf:2c55 Sunplus Innovation Technology Inc.
At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. I don't know if yours is the same. I just checked that I can access my usb memory stick as my ordinary non root self, and that does work OK. Comment 13 Wilco 2013-08-02 16:08:56 UTC Can reproduce this bug with Dolphin and Konqueror.
Version-Release number of selected component (if applicable): KDE 4.11.3 Comment 1 Germano Massullo 2014-10-22 14:14:55 EDT Created attachment 949513 [details] screenshot Comment 2 Fedora End Of Life 2015-05-29 06:03:55 EDT This Using openSUSE 13.1 live-dvd device notifier does not list the camera (strange because it does with Kubuntu). Back to the top of the source tree ./configure --prefix=/usr --libdir=/usr/lib64 so that the output code will overlay the original installed library. Application may misbehave.
Nothing is visible. Comment 24 Marcus Meissner 2014-01-02 17:24:43 UTC solid-hardware query "Camera.supportedDrivers == 'gphoto'" then take the line with Block.device = '/dev/bus/usb/XXX/YYY' (string) and run ls -l /dev/bus/usb/XXX/YYY getfacl /dev/bus/usb/XXX/YYY please (replace XXX Comment 5 bill p. (aka google01103) 2013-02-10 19:17:27 UTC now in Dolphin as regular user getting: [quote]Unknown error code 150 Bad parameters Please send a full bug report at http://bugs.kde.org.[/quote] Comment Could be, but I'm not really familiar with the details of the interaction between KDirLister and the kioslaves.
I am reasonably certain permissions play no role in this case. Bonuses 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. Comments seem to indicate this is a permission problem with some distributions, but not others. As suggested per https://bugs.kde.org/show_bug.cgi?id=264020#c31.
However, Gwenview uses a camera:/ URI and works fine. have a peek at these guys Posting in the Forums implies acceptance of the Terms and Conditions. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1256591/+editstatus and add the package name in the text box next to the word Package. [This is an automated It comes from the kioslave that tried to access the phone.
However it may be, thank you very much for your efforts to fix the bug! Comment 4 lbickley 2016-09-22 04:00:09 UTC btw: The default device is MTP: per either (see directory /usr/share/kde4/apps/solid/actions/ ): Note: See "exec=..." in script below File: solid_mtp.desktop ------------------------------- [Desktop Entry] X-KDE-Solid-Predicate=PortableMediaPlayer.supportedProtocols == Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) QDBusConnection: session D-Bus connection created before QCoreApplication. http://fullflash.net/unknown-error/unknown-error-code-150.html Mine for reference (reported as generic PTP camera) Code: USB PTP Class Camera usb: USB PTP Class Camera usb:002,003 If detected ok, now type the following Code: cd ~/ mkdir test
As user dolphin shows no files (camera:/). Page 1 of 2 12 Last Jump to page: Results 1 to 10 of 19 Thread: Digikam, I can only access camera as root user; openSuse 11.4 KDE Thread Tools Show Either I will get the same KIO crash (The process for the camera protocol died unexpectedly.) or your error 150.
Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Acknowledgement sent to mourad : New Bug report received and forwarded. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Reply With Quote 03-Apr-2011,21:18 #2 caf4926 View Profile View Forum Posts View Blog Entries Visit Homepage View Articles Global Moderator Join Date Jun 2008 Location The English Lake District. I have a Samsung Galaxy S 3 and I have, eventually, gotten it working on Kubuntu.
Application may misbehave. In KDE Bug Tracking System #264020, Spam-2008 (spam-2008) wrote on 2014-01-03: #43 $ kcmshell4 kamera -> the camera is shown correctly $ dolphin camera:/ Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No It seems it's a bit of a mess and I think it's a KDE mess as Kamera is rather unmaintained. this content Digikam and gphoto2 works fine and so does running dolphin through kdesu.
Bug1045219 - Unknown error code: 150 while browsing Samsung Galaxy S II Summary: Unknown error code: 150 while browsing Samsung Galaxy S II Status: CLOSED EOL Aliases: None Product: Fedora Classification: