Bug 321975 - After dbus restart connection to dbus server not restored
Summary: After dbus restart connection to dbus server not restored
Status: RESOLVED UNMAINTAINED
Alias: None
Product: solid
Classification: Unmaintained
Component: general (show other bugs)
Version: 4.10.5
Platform: Other Linux
: NOR normal
Target Milestone: 4.11
Assignee: Lukáš Tinkl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-05 00:03 UTC by Mike Krutov
Modified: 2018-09-04 15:44 UTC (History)
0 users

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


Attachments
Misleading error message. Second part is not displayed til I drag it up. (108.93 KB, image/png)
2013-07-05 00:04 UTC, Mike Krutov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Krutov 2013-07-05 00:03:48 UTC
After i run /etc/init.d/dbus restart, I can't mount any external drives with error message:
"Unexpected error: not connected".
Unmount has different message (and very confusing one), will attach to the bug.

Reproducible: Always

Steps to Reproduce:

1. sudo /etc/init.d/dbus restart
2. plug external hdd/flash drive
3. try to mount

OR
0. have plugged-in and mounted flash drive
<..>
3. try to unmount.

Actual Results:  
Not connected to server error message

Expected Results:  
Drive mounted or unmounted

ps shows that dbus server is started.
Nothing but re-login fixes issue.
It's not that often to /etc/init.d/dbus restart, however I've spent some time while trying to find out what is using my external hdd, because default notification yields only 'Drive is being used by application' and to get connectivity problem information I have to click on notification and scroll it.
At least error message should be fixed.
Comment 1 Mike Krutov 2013-07-05 00:04:29 UTC
Created attachment 80952 [details]
Misleading error message. Second part is not displayed til I drag it up.
Comment 2 Andrew Crouthamel 2018-09-04 15:44:45 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug. Please try again with the latest version and submit a new bug to frameworks-solid if your issue persists. Thank you!