Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
  • Sign in / Register
manjaro-settings-manager
manjaro-settings-manager
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
    • Insights
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 41
    • Issues 41
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Security & Compliance
    • Security & Compliance
    • Dependency List
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • applications
  • manjaro-settings-managermanjaro-settings-manager
  • Issues
  • #2

Closed
Open
Opened Jul 11, 2014 by Philip Müller@philm
  • Report abuse
  • New issue
Report abuse New issue

Removal of linux34 creates dbus issues in unstable

Created by: manjaro

Seems the removal of linux34 creates issues with dbus in MSM. Followed outputs:

pkexec:

[phil@manjaro Arbeitsfläche]$ manjaro-settings-manager
/usr/bin/manjaro-settings-manager: Line 7:  4243 memory error  pkexec "/usr/bin/manjaro-settings-manager-gui" "$@"

sudo -E

[phil@manjaro Arbeitsfläche]$ sudo -E manjaro-settings-manager-gui

(process:2442): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(manjaro-settings-manager-gui:2442): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

gksu

[phil@manjaro Arbeitsfläche]$ gksu manjaro-settings-manager-gui
Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed

Related issues

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
1
Labels
bug
Assign labels
  • View project labels
Reference: applications/manjaro-settings-manager#2