First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 158034
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Daniel Gryniewicz <dang@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: P.L.Hayes <paul@wolfbone.ath.cx>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 158034 depends on: Show dependency tree
Bug 158034 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-12-13 07:23 0000 
I have dbus-1.0.2 and dbus-glib-0.72 installed - I'm not sure why dbus got
installed at all since it isn't in my USE flags but anyway...

When I try to run evince (emerged with USE=-dbus), I get this message:

process 25567: D-Bus library appears to be incorrectly set up; failed to read
machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or
directory
See the manual page for dbus-uuidgen to correct this issue.
  D-Bus not built with -rdynamic so unable to print a backtrace

Well great but I don't want to RTFM etc. because I didn't ask for evince to use
dbus in the first place!

------- Comment #1 From Daniel Gryniewicz 2006-12-17 09:39:45 0000 ------- 
It turns out recent evince wasn't switching dbus support, only detecting it. 
I've added a switch, which should disable it.

However, much of gnome hard deps on dbus, and going forward, you won't be able
to avoid it while using gnome programs.
First Last Prev Next    No search results available      Search page      Enter new bug