Bug 403726 - Cant mount share
Summary: Cant mount share
Status: RESOLVED WORKSFORME
Alias: None
Product: Smb4k
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Alexander Reinholdt
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-29 10:21 UTC by seleko
Modified: 2019-03-23 04:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description seleko 2019-01-29 10:21:00 UTC
SUMMARY
Starting some version of KDE I lost opportunity to mounty share with smb4k. Nothing visible happened. It shows the process of mounting, but share doesn't appear. If I start smb4k from shell window it shows message: "kf5.kauth: Tried to start an invalid action" during the process of mounting. All the folders ~/smb4k/<server/share> created correctly. 
Problem can be reproduced for versions:
smb4k-2.1.1
smb4k-2.9.73

Qt 5.12.0

STEPS TO REPRODUCE
1. Open shell window type "smb4k" hit <Enter>
2. Try to mount share in smb4k interface.
3. 

OBSERVED RESULT
Share doesn't appear.

EXPECTED RESULT
Share appear and accessible.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Leap 15, 
(available in About System)
KDE Plasma Version: 5.13.x-5.14.x
KDE Frameworks Version: 5.54.0
Qt Version: 5.12

ADDITIONAL INFORMATION
Comment 1 Alexander Reinholdt 2019-02-02 14:48:54 UTC
I tried to reproduce your issue on a freshly installed openSUSE Leap 15 system, however, everything worked as expected: mounting was successful. 

Maybe you can provide some additional information?

By the way, for my tests, I switched off the firewall.
Comment 2 seleko 2019-02-04 04:05:13 UTC
Yeah, I know this error doesn't reproduce on fresh install. But I need latest KDE so I updated.
What information could I provide to help narrow search?

libKF5Auth5-5.54.0git.20190107T001612~11fd0d1-13.1.x86_64 -- installed as last hope.
As I understand, I cant enable debug/verbose mode without specifically compiled smb4k, right?
Comment 3 Alexander Reinholdt 2019-02-04 14:14:59 UTC
I do not use openSUSE, so can you please tell me from which repository you installed the latest KDE version, so I can try to reproduce the problem. Maybe I come up with more questions when I set up the system and started the testing. 

By the way, I use KDE neon User Edition, and Smb4K works without problems.
Comment 4 Alexander Reinholdt 2019-02-04 14:26:40 UTC
Ah, sorry, I missed your question about the debug output: Yes, you need to recompiled Smb4K with the '-DCMAKE_BUILD_TYPE=Debug' argument to enable the debug mode.
Comment 5 seleko 2019-02-06 03:31:27 UTC
I used http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Factory repo. Sorry, but cant recompile debug version my own :(
Comment 6 Christoph Feck 2019-02-18 21:44:48 UTC
New information was added with comment #5; changing status for inspection.
Comment 7 Alexander Reinholdt 2019-02-19 12:27:32 UTC
(In reply to seleko from comment #5)
> I used
> http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Factory
> repo. Sorry, but cant recompile debug version my own :(

Ok, thanks. I will try that version out.
Comment 8 Alexander Reinholdt 2019-02-21 18:50:21 UTC
I don't seem to be able to install the packages from Factory. Running 

$ sudo zypper update 

always tells me that the packages won't be installed. What command do I have to run to get them installed?
Comment 9 Bug Janitor Service 2019-03-08 04:33:07 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Bug Janitor Service 2019-03-23 04:33:11 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!