(old)Puppy Linux Discussion Forum

I have tried Puppy 3.0 on 3 computers and Pidgin does not start. Any one have this prob

type pidgin in a terminal and past back what it says.

Same problem here ... this is puppy 3.00 booted straight off CD, first run However having saved the session (pup_save + optional files) and rebooted, it works both from command line and from desktop icon

paul

I had this exact problem, but after trying it in the console, it worked and has worked since. strange but true.

type these into the terminal:
/etc/init.d/messagebus reload
/etc/init.d/messagebus restart

I had this problem and this cured it for me. Thankyou Wolf Pup

Weird after rebooting puppy 3.0 the second time with a save file Pidgin works great. Too much of a noob to know why.

This D-Bus dependency is a new thing in Slackware 12, and I know nothing about it. I don't like it when another dependency is added that doesn't seem to improve the performance of the application, but it does add another layer of complexity and potential trouble.
I'm having a grumble, probably there were good reasons for having it.

be interesting to know why the problem seems only to manifest when puppy is "live" rather than "installed" in some way

paulh177 wrote:be interesting to know why the problem seems only to manifest when puppy is "live" rather than "installed" in some way

Pidgin worked fine when I used the live CD, but after either a frugal or full install, that is when it would not start.

Hello Wolf pup,
Thank you for your advice, my Pidgin is flying in puppy 3.00 seamonkey.
Michael.

I tried all-but Pidgin do not start after I installed Puppy 3.0 on my USB flash. Who had the same problems and solved it? I tried all, what I found in the forum.

pidgin
process 4064: 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
Aborted
# /etc/init.d/messagebus reload
Reloading system message bus configuration...
killall: dbus-daemon: no process killed
# /etc/init.d/messagebus reload
Reloading system message bus configuration...
killall: dbus-daemon: no process killed
# pidgin
process 4175: 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
Aborted
#

uli27

you forgot to type in /etc/init.d/messagebus restart after entering /etc/init.d/messagebus reload

Sorry for bringing up an old thread, but I have this problem with Pidgin in Puppy 3.01 too I made custom version from Unleashed (a Puplet?), where my default IM is Pidgin. Saving session is not an option, because I want everything to work from Live CD from first bootup.
After using this command: "dbus-uuidgen --ensure" Pidgin launches without problems.
Do I need to add this line to startup scripts (although it must be run only once, after the system installation to hard drive), or is there any other solution to this problem?

My answer to this issue was to set the dbus machine id: ...from here.

steve_s wrote:My answer to this issue was to set the dbus machine id:

Code: Select all

dbus-uuidgen > /var/lib/dbus/machine-id

...from here.

Well I hope he wasn't holding his breath for 16Months for that answer lol
check out the posted date on his post
ttuuxxx

ttuuxxx wrote:

steve_s wrote:My answer to this issue was to set the dbus machine id:

Code: Select all

dbus-uuidgen > /var/lib/dbus/machine-id

...from here.

Well I hope he wasn't holding his breath for 16Months for that answer lol
check out the posted date on his post
ttuuxxx

Ha! Yeah, I know..it was more for future reference for myself and others...I envision that being one of those, "Now, how did I do that dbus reset thing again?" scenarios so now at least I've got it posted somewher I can find...

steve_s wrote:
Ha! Yeah, I know..it was more for future reference for myself and others...I envision that being one of those, "Now, how did I do that dbus reset thing again?" scenarios so now at least I've got it posted somewher I can find...

hey steve I guess theres over 3000 unanswered post on here, well that one, you better get started, it will be a long night for you, LOL
kidding
ttuuxxx

ttuuxxx wrote:

steve_s wrote:
Ha! Yeah, I know..it was more for future reference for myself and others...I envision that being one of those, "Now, how did I do that dbus reset thing again?" scenarios so now at least I've got it posted somewher I can find...

hey steve I guess theres over 3000 unanswered post on here, well that one, you better get started, it will be a long night for you, LOL
kidding
ttuuxxx

or I have been fiddling with dbus simply because a lot of things seem to need it, or think they need it. The trouble is if dbus is installed without the machine-id file being created puppy crashes on my machines taking the desktop wallpaper, icons and all with it.

The only way to recover is to drop out of X to a terminal and set up the machine-id file as previously mentioned by steve_s.