Bug 45048 - After upgrade to 4.2 the kde usb-mounting is broken
After upgrade to 4.2 the kde usb-mounting is broken
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: X.Org
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-21 12:14 CEST by Christina Scheinig
Modified: 2020-07-03 20:52 CEST (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.091
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2017071321000661
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christina Scheinig univentionstaff 2017-07-21 12:14:55 CEST
In a customer environment it was no longer possible to mount an usb-hdd, logged in as administrator in the KDE GUI.
Mounting the usb-hdd via command line is still possible and is a workaround for the customer at the moment.

I could reproduce the issue in my test environment.

The error message in "Dolphin" is:
Beim Zugriff auf „58,9 GiB Wechselmedium“ ist ein Fehler aufgetreten, die Meldung lautet: An unspecified error has occurred: Not authorized to perform operation

____________________________________________________________________________________________________________

Maybe in this context the logfile-message is part of the problem:
view /home/Administrator/.xsession-errors

New PolkitAgentListener  0x1d6e620
Adding new listener  PolkitQt1::Agent::Listener(0x1ee8680) for  0x1d6e620
"Cannot create unix session: No session for pid 2215"

** (process:2215): CRITICAL **: polkit_agent_listener_register_with_options: assertion 'POLKIT_IS_SUBJECT (subject)' failed
"Cannot register authentication agent!"

(process:2215): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

_______________________________________________________________________________________________________________

Maybe this is interesting:
http://forums.debian.net/viewtopic.php?f=10&t=117163
----
root@ucs:/home/Administrator# dpkg -l |grep sysv
ii  systemd-sysv                                        215-17+deb8u5A~4.2.0.201701111554              amd64        system and service manager - SysV links
ii  sysv-rc                                             2.88dsf-59A~4.2.0.201703021459                 all          System-V-like runlevel change mechanism
ii  sysvinit                                            2.88dsf-59A~4.2.0.201703021459                 amd64        System-V-like init utilities - transitional package
ii  sysvinit-utils  
----

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764511
----
root@ucs:/home/Administrator# dpkg -l |grep polki
ii  libpolkit-agent-1-0:amd64                           0.105-15~deb8u2                                amd64        PolicyKit Authentication Agent API
ii  libpolkit-backend-1-0:amd64                         0.105-15~deb8u2                                amd64        PolicyKit backend API
ii  libpolkit-gobject-1-0:amd64                         0.105-15~deb8u2                                amd64        PolicyKit Authorization API
ii  libpolkit-qt-1-1                                    0.103.0-1.6.201403261810                       amd64        PolicyKit-qt-1 library
ii  polkit-kde-1                                        0.99.1-1                                       amd64        KDE dialogs for PolicyKit
----
Comment 1 Ingo Steuwer univentionstaff 2020-07-03 20:52:28 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.