Reply to topic

Samsung Galaxy GT-S5830L cell phone not showing in KDE Devic

User avatar Mario Storti
Registered Member
Posts
21
Karma
0
KDE Device Notifier stopped showing my cell phone after upgrade to
Fedora 17/18. (I don't know exactly if it was for F17 or for F18,
since I did the upgrade to F17 and immediately after that I did the
upgrade to F18.) Now I have Fedora 18 64 bit on an Asus G53SX laptop.

I did some research and found many posts related to MTP, suggesting to
install mtpfs, jmtpfs. I followed the recipes with no success.

Strangely enough the cell phone is shown and mounts OK if I use
Gnome. Also if I browse the filesystem within Gimp (in KDE!) I can see
the cell phone sdcard. So I think that is some KDE related problem.

When I go to Device Notifier Settings -> Removable Devices, the phone
is listed, but I can do anything with it. If I hover with the mouse on
the sdcard then a popup shows
UDI:/orgfreedesktop/UDisks2/block_devices/sdb

If I do $ lsusb, I get

Bus 002 Device 004: ID 04e8:689e Samsung Electronics Co., Ltd GT-S5670
[Galaxy Fit]

When I unmount the SDCARD on the phone I get the following in /var/log/messages

Feb 6 21:34:36 kinky kernel: [ 1352.998977] sd 8:0:0:0: [sdb] 7736320
512-byte logical blocks: (3.96 GB/3.68 GiB)
Feb 6 21:34:36 kinky kernel: [ 1353.000549] sd 8:0:0:0: [sdb] Asking
for cache data failed
Feb 6 21:34:36 kinky kernel: [ 1353.000559] sd 8:0:0:0: [sdb] Assuming
drive cache: write through
Feb 6 21:34:36 kinky kernel: [ 1353.003137] sd 8:0:0:0: [sdb] Asking
for cache data failed
Feb 6 21:34:36 kinky kernel: [ 1353.003147] sd 8:0:0:0: [sdb] Assuming
drive cache: write through
Feb 6 21:34:36 kinky kernel: [ 1353.003792] sdb:

Someone on kde@lists.fedoraproject.org suggested me to install the
kio_mtp package, but still the device is not detected. I see that this
package contains a shared library and KDE services. Should I do
something in order to start these services? I looked at Service
Manager and I didn't fin any services related to MTP. Should I do
anything more than just installing the package?

Any help is welcome!!

Kind regards, Mario
User avatar bcooksley
Administrator
Posts
18642
Karma
83
OS
With kio_mtp installed, have you tried opening mtp:/ in Dolphin or Konqueror to see if your device is listed there?


System Settings and Device Actions KCM maintainer
Image
User avatar Mario Storti
Registered Member
Posts
21
Karma
0
bcooksley wrote:With kio_mtp installed, have you tried opening mtp:/ in Dolphin or Konqueror to see if your device is listed there?


If I do that I found nothing in Dolphin.

However, if (I as mentioned before) go to Device Notifier Settings ->
Removable Devices the phone is listed, but I can do anything with
it. If I hover with the mouse on the sdcard then a popup shows
UDI:/orgfreedesktop/UDisks2/block_devices/sdb

I think that the phone is not using MTP. I think this problem is a
misconfiguration or bug of Device Notifier, but I can't solve it.

Thanks! Mario
User avatar bcooksley
Administrator
Posts
18642
Karma
83
OS
Please provide the output of the following command:
Code: Select all
solid-hardware details /org/freedesktop/UDisks2/block_devices/sdb


System Settings and Device Actions KCM maintainer
Image
User avatar Mario Storti
Registered Member
Posts
21
Karma
0
bcooksley wrote:Please provide the output of the following command:
Code: Select all
solid-hardware details /org/freedesktop/UDisks2/block_devices/sdb


Hi, here it is:

Code: Select all
[root@kinky ~]# solid-hardware details /org/freedesktop/UDisks2/block_devices/sdb
udi = '/org/freedesktop/UDisks2/block_devices/sdb'
  parent = '/org/freedesktop/UDisks2/drives/SAMSUNG_GT_S5830L_Card_S58308ac11025'  (string)
  vendor = 'SAMSUNG'  (string)
  product = 'GT-S5830L Card'  (string)
  description = '3.7 GiB Removable Media'  (string)
  Block.major = 8  (0x8)  (int)
  Block.minor = 16  (0x10)  (int)
  Block.device = '/dev/sdb'  (string)
  StorageAccess.accessible = false  (bool)
  StorageAccess.filePath = ''  (string)
  StorageAccess.ignored = false  (bool)
  StorageVolume.ignored = false  (bool)
  StorageVolume.usage = 'FileSystem'  (0x2)  (enum)
  StorageVolume.fsType = 'vfat'  (string)
  StorageVolume.label = ''  (string)
  StorageVolume.uuid = '3663-6266'  (string)
  StorageVolume.size = 3960995840  (0xec180000)  (qulonglong)
[root@kinky ~]#


Thanks! Mario
User avatar bcooksley
Administrator
Posts
18642
Karma
83
OS
Are you able to mount the device manually?


System Settings and Device Actions KCM maintainer
Image
User avatar Mario Storti
Registered Member
Posts
21
Karma
0
bcooksley wrote:Are you able to mount the device manually?


I don't know how to do that!
User avatar bcooksley
Administrator
Posts
18642
Karma
83
OS
There are two possible ways to do this - this way is through UDisks2:
Code: Select all
solid-hardware mount /org/freedesktop/UDisks2/block_devices/sdb


System Settings and Device Actions KCM maintainer
Image
User avatar Mario Storti
Registered Member
Posts
21
Karma
0
bcooksley wrote:There are two possible ways to do this - this way is through UDisks2:
Code: Select all
solid-hardware mount /org/freedesktop/UDisks2/block_devices/sdb


YES! That did worked, and mounts in /run/media/root/3663-6266/. Also I
tried to do `mount' and it did worked

Code: Select all
[root@kinky ~]# mount /dev/sdb /mnt
[root@kinky ~]# ls -l /mnt
total 800
drwxr-xr-x 2 root root 32768 Aug  5  2011 AlarmClockXtreme
drwxr-xr-x 3 root root 32768 Jul  5  2011 Android
...
[root@kinky ~]#


Thanks, thats a big advance for me! At least now I can mount the
device manually.

Now I see that the problem happened when I migrated to Fedora 17/18 (I
don't know exactly which of them caused the problem, because I did
both upgrades almost simultaneously). During the upgrade I saw that
now mounts are in /run/media/<user> instead of /media. May be the
problem related to that? Perhaps for some reason device notifier is
waiting to something being mounted at /media. But wait no... It can't
be that because other removable devices (PHDs, pendrives) are being
detected OK.
User avatar bcooksley
Administrator
Posts
18642
Karma
83
OS
I suspect the move from /media to /run/media is not related here.
It is probably the failure of a rule known as a "Predicate" to match your phone.

To check this, please run:
Code: Select all
solid-hardware query "[ [ [ StorageVolume.ignored == false AND StorageVolume.usage == 'FileSystem' ] OR [ IS StorageAccess AND StorageDrive.driveType == 'Floppy' ] ] OR StorageAccess.ignored == false ]"


System Settings and Device Actions KCM maintainer
Image
User avatar Mario Storti
Registered Member
Posts
21
Karma
0
bcooksley wrote:I suspect the move from /media to /run/media is not related here.
It is probably the failure of a rule known as a "Predicate" to match your phone.

To check this, please run:
Code: Select all
solid-hardware query "[ [ [ StorageVolume.ignored == false AND StorageVolume.usage == 'FileSystem' ] OR [ IS StorageAccess AND StorageDrive.driveType == 'Floppy' ] ] OR StorageAccess.ignored == false ]"


Here it is,

Code: Select all
[root@kinky ~]# solid-hardware query "[ [ [ StorageVolume.ignored == false AND StorageVolume.usage == 'FileSystem' ] OR [ IS StorageAccess AND StorageDrive.driveType == 'Floppy' ] ] OR StorageAccess.ignored == false ]"
udi = '/org/freedesktop/UDisks2/block_devices/dm_2d1'
udi = '/org/freedesktop/UDisks2/block_devices/dm_2d2'
udi = '/org/freedesktop/UDisks2/block_devices/sdb'
[root@kinky ~]#
User avatar bcooksley
Administrator
Posts
18642
Karma
83
OS
Very unusual - that is the exact same predicate which the Device Notifier uses, so it should be showing "Open in File Manager" as an action.
Can you try this under a new user please?


System Settings and Device Actions KCM maintainer
Image
User avatar Mario Storti
Registered Member
Posts
21
Karma
0
bcooksley wrote:Very unusual - that is the exact same predicate which the Device Notifier uses, so it should be showing "Open in File Manager" as an action.
Can you try this under a new user please?


YES! The device is detected and correctly mounted for other user. Should I clean some kind of cache for KDE?
User avatar bcooksley
Administrator
Posts
18642
Karma
83
OS
Please try removing ~/.kde4/share/apps/solid outside of KDE.
Also, try running "kbuildsycoca4 --noincremental".


System Settings and Device Actions KCM maintainer
Image
User avatar Mario Storti
Registered Member
Posts
21
Karma
0
bcooksley wrote:Please try removing ~/.kde4/share/apps/solid outside of KDE.


I don't have a ~/.kde4 directory (but I'm runnin KDE 4, that's sure)
I do have a ~/.kde of course, but there is not ~/.kde/share/apps/solid
directory in there.

Also, try running "kbuildsycoca4 --noincremental".


I did so but it didn't fixed the problem. Thanks!

 
Reply to topic

Bookmarks



Who is online

Registered users: afiestas, avishekk, Baidu [Spider], bcooksley, Bing [Bot], bjoernbalazs, brankko, colomar, Cris70, david_edmundson, einar, Exabot [Bot], ggael, Google [Bot], Heiko Tietze, joshaughnessy, ken300, khsien, koriun, La Ninje, lueck, Majestic-12 [Bot], metalbrick, mmagnusson, ooker, rossdv8, scummos, seal20, starbuck, stavallo, steltsop, steph, SysGhost, valoriez, vHanda, Yahoo [Bot]