![]() Registered Member ![]()
|
I just lost my Devises in Dolphin on the lower right hand side. So nothing shows when I plug in my external hard driver in the USB. I can't even do a backup of my files any more. This has never happened in the past. I really can use some help from developers please.....
Has anyone ran into this after this new update, or have found a solution to fix this? This really sucks! ![]() Developers ....Please help!! |
![]() Registered Member ![]()
|
Same here. It was yesterday's 'solid' updates that caused the problem in dolphin.
Until the issue is solved there are two work-rounds: 1 - install the package: thunar devices are still shown 2 - rollback the three faulty packages: libkf5solid5 libkf5solid5-data qml-module-org-kde-solid to versions 32 (the updated versions are numbered 33) and then lock these. |
![]() KDE Developer ![]()
|
The Neon builds have imported this upstream change:
https://cgit.kde.org/solid.git/commit/? ... d1b0bb952b but did not include the additional change: https://cgit.kde.org/solid.git/commit/? ... ae140f980b
|
![]() Registered Member ![]()
|
Sorry I should have added that if you mount the drive in thunar it then shows in dolphin.
|
![]() Registered Member ![]()
|
@gfielding,
You are a life saver! Thank you. I see the drive now after I installed thunar, but can you tell me exactly how to roll back step by step? |
![]() Registered Member ![]()
|
The steps are:
1 - install the package: synaptic if not already installed. 2 - Open synaptic and enter: solid in the search box. 3 - Click on one of the packages to roll-back, then click on the top menu 'package', then 'Force Version' and select the previous version. Do the same with the other two versions and then apply. 4 - You can lock these three packages but Discover overides this, so you have to be careful when you do updates in Discover and just take the ticks out for the three packages just to update the other packages. |
![]() Registered Member ![]()
|
FYI, this issue is already fixed properly, so if you upgrade your system, it will fix the bug.
|
![]() Registered Member ![]()
|
|
![]() Registered Member ![]()
|
@gfielding, @bshah
It is fixed now as bshah mentioned. Thank you guys , and developers, to jump on this so quick! ![]() |
![]() Registered Member ![]()
|
Hi,
I have a similar issue, when plugging in any USB driver nor Dolphin, nor the "Device Notifier" catches it even though dmesg reports the device has been recognized by the system. > [Sat Jan 27 21:25:21 2018] usb 1-4: new high-speed USB device number 13 using xhci_hcd > [Sat Jan 27 21:25:21 2018] usb 1-4: New USB device found, idVendor=0781, idProduct=5571 > [Sat Jan 27 21:25:21 2018] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > [Sat Jan 27 21:25:21 2018] usb 1-4: Product: Cruzer Fit > [Sat Jan 27 21:25:21 2018] usb 1-4: Manufacturer: SanDisk > [Sat Jan 27 21:25:21 2018] usb 1-4: SerialNumber: 4C532008920426123521 > [Sat Jan 27 21:25:21 2018] usb-storage 1-4:1.0: USB Mass Storage device detected > [Sat Jan 27 21:25:21 2018] scsi host3: usb-storage 1-4:1.0 > [Sat Jan 27 21:25:23 2018] scsi 3:0:0:0: Direct-Access SanDisk Cruzer Fit 1.26 PQ: 0 ANSI: 5 > [Sat Jan 27 21:25:23 2018] sd 3:0:0:0: Attached scsi generic sg1 type 0 > [Sat Jan 27 21:25:23 2018] sd 3:0:0:0: [sdb] 31266816 512-byte logical blocks: (16.0 GB/14.9 GiB) > [Sat Jan 27 21:25:23 2018] sd 3:0:0:0: [sdb] Write Protect is off > [Sat Jan 27 21:25:23 2018] sd 3:0:0:0: [sdb] Mode Sense: 43 00 00 00 > [Sat Jan 27 21:25:23 2018] sd 3:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA > [Sat Jan 27 21:25:23 2018] sdb: sdb1 > [Sat Jan 27 21:25:23 2018] sd 3:0:0:0: [sdb] Attached SCSI removable disk Was this solved for the KDE Neon User Edition? |
![]() Registered Member ![]()
|
I have just tried a usb drive (user version of kde neon) and it was reconised fine. Perhaps try a different usb drive as a double check.
|
![]() Registered Member ![]()
|
Didn't you read the tread? It's already fixed. Just refresh the Synaptic Package manager, or Discover, and do an update. The update will fix it.
![]() |
![]() Registered Member ![]()
|
Yes... Last dist-upgrade fixed the issue... Thanks...
|
Registered users: bartoloni, Bing [Bot], Google [Bot], q.ignora, watchstar