Mailinglist Archive: opensuse-bugs (4258 mails)

< Previous Next >
[Bug 1022440] New: Could not start d-bus. Can you call qdbus-qt5
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Sat, 28 Jan 2017 17:33:29 +0000
  • Message-id: <bug-1022440-21960@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1022440


Bug ID: 1022440
Summary: Could not start d-bus. Can you call qdbus-qt5
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: SUSE Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Basesystem
Assignee: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
Reporter: paka@xxxxxxxxxxxxxxx
QA Contact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---

changing from multi-user.target to graphical.target fail and displays "Could
not start d-bus. Can you call qdbus-qt5". Calling qdbus-qt5 sometimes succeeds
and sometimes fails, but still cannot open graphical.target w/o rebooting
directly to "graphical.target" (I normally boot to multi-user).

libqt5-qdbus-5.7.1-1.1.x86_64

this occurs on two local machines, a generic intel desktop:
openSUSE Tumbleweed 20170127
Linux 4.9.5-1-default x86_64
12-thr Intel(R) Core(TM) i7 CPU 970 3193MHz
Mem: 13889/36194MB
Disk: 1395/7083GB
Gfx: NVIDIA Corporation GF106 [GeForce GTS 450] @ 3840x1080

and a toshiba laptop:
openSUSE Tumbleweed 20170127
Linux 4.8.14-1-default x86_64
4-thr Intel(R) Core(TM) i7-5500U CPU 3000MHz
Mem: 1856/11928MB | Disk: 111/489GB
Gfx: Intel Corporation HD Graphics 5500 @ 3840x1080

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
Follow Ups