• Login
  • Register
  • Dolphin Forums
  • Home
  • FAQ
  • Download
  • Wiki
  • Code


Dolphin, the GameCube and Wii emulator - Forums › Dolphin Emulator Discussion and Support › Support v
« Previous 1 ... 270 271 272 273 274 ... 1198 Next »

Multiple strange errors
View New Posts | View Today's Posts

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Thread Modes
Multiple strange errors
03-21-2018, 09:35 AM
#1
CarterCox
Unregistered
 
Hello! So I'm getting strange errors when unsing Dolphin on Arch Linux. I run it from the CLI to see the messages and I get this:

Code:
Can't locate Net/DBus.pm in @INC (you may need to install the Net::DBus module) (@INC contains: /usr/lib/perl5/5.26/site_perl /usr/share/perl5/site_perl /usr/lib/perl5/5.26/vendor_perl /usr/share/perl5/vendor_perl /usr/lib/perl5/5.26/core_perl /usr/share/perl5/core_perl) at -e line 5.
BEGIN failed--compilation aborted at -e line 5.
Aborted (core dumped)

And I can solve it by installing "perl-net-dbus" Then I get this:

Code:
Can't locate X11/Protocol.pm in @INC (you may need to install the X11::Protocol module) (@INC contains: /usr/lib/perl5/5.26/site_perl /usr/share/perl5/site_perl /usr/lib/perl5/5.26/vendor_perl /usr/share/perl5/vendor_perl /usr/lib/perl5/5.26/core_perl /usr/share/perl5/core_perl) at -e line 6.
BEGIN failed--compilation aborted at -e line 6.
Aborted (core dumped)

which I get rid of by installing "perl-x11-protocol". Lastly, I get this one that I can't solve:

Code:
org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
Aborted (core dumped)

What could be the cause of this?

After all this errors Dolphin just closes.


Thanks for any help you can provide!!
Reply
03-22-2018, 01:53 AM
#2
JonnyH Offline
Shameless AMD shill
**********
Developers (Some Administrators and Super Moderators)
Posts: 701
Threads: 0
Joined: May 2017
The perl and dbus errors shouldn't be fatal - the real problem is the "Aborted (core dumped)".

That means it's crashed, and it should have left a core file (where it puts it can be distro-dependent - if it's not in the local directory, it's probably stashed in the systemd journald or some other global place).

If you get that core file, you can run it through gdb to get a backtrace to see exactly where it went wrong - which is likley needed to even start trying to track down what's going on.
Find
Reply
« Next Oldest | Next Newest »


  • View a Printable Version
  • Subscribe to this thread
Forum Jump:


Users browsing this thread: 1 Guest(s)



Powered By MyBB | Theme by Fragma

Linear Mode
Threaded Mode