search

olivierkes / manuskript

A open-source tool for writers
http://www.theologeek.ch/manuskript
GNU General Public License v3.0
1.78k stars 236 forks source link

Missing "Manuskript" icon and error messages on startup #678

Open mafinokc opened 5 years ago

mafinokc commented 5 years ago

Please forgive anything I post here that bespeaks ignorance. I am relatively new to Linux.

I'm running Linux Mint 19.2 MATE on an older machine. The package snapd was already installed before I started. I ran the command "sudo snap install --edge manuskript". Another installation of snapd appeared to take place, eventually followed by installation of Manuskript 0.10. I looked for a Manuskript program icon in the Applications list under Menu, but cannot not find one. Searching the file system for "Manuskript" turned up nothing. Manuskript is listed in the snap packages list. I tried running Manuskript from the terminal, and it did start and appear to be stable, but before it started, these messages were displayed:

mark@Linux-clone:~$ snap run manuskript Debug: Web rendering engine used: QWebView Qt: Session management error: None of the authentication protocols specified are supported Running manuskript version 0.10.0. Preferred translation: ['en-US'] (based on available ui languages) Using the builtin translation. propsReply "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.332\" (uid=1000 pid=22259 comm=\"python3 /snap/manuskript/187/bin/manuskript \" label=\"snap.manuskript.manuskript (enforce)\") interface=\"org.freedesktop.DBus.Properties\" member=\"GetAll\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=883 comm=\"/usr/sbin/NetworkManager --no-daemon \" label=\"unconfined\")" nmReply "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.332\" (uid=1000 pid=22259 comm=\"python3 /snap/manuskript/187/bin/manuskript \" label=\"snap.manuskript.manuskript (enforce)\") interface=\"org.freedesktop.NetworkManager\" member=\"GetDevices\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=883 comm=\"/usr/sbin/NetworkManager --no-daemon \" label=\"unconfined\")" "Object path cannot be empty"

So my questions are:

  1. Where is the Manuskript icon, or can the program be run only from the terminal?
  2. What do all of the messages above mean, do I need to do something about them, and if so, what?

Advance thanks to any who come to my assistance.

worstje commented 5 years ago

I don't use Linux very much, so I am not the best person to answer your questions. Regardless, let me give it a shot.

  1. You can find the icons Manuskript uses in the icons/Manuskript directory. I don't know where that is installed when using snap, but if you can find where it installed Manuskript, you should be halfway there, I hope. (Emphasis on 'hope'; I don't know how snap dumps the various files at all.)

    Based on your log, I suspect you'll find the icons at /snap/manuskript/187/icons/Manuskript/.

  2. The error messages suggest security hardening gets in the way. AppArmor is a mechanism that is used on Linux to prevent unauthorized applications from tapping into certain functionality.

    In this case, it appears that Manuskript tried to get in touch with some part of the networking stack, and that that was blocked.

    Also interesting is near the top, it says: Qt: Session management error: None of the authentication protocols specified are supported

    Based on where it pops up, I suspect this error may be thrown as a part of some Qt initialization, most likely when the main QApplication is constructed.

Everything I see in that log appears to be related to security features stopping Manuskript from interacting with various parts of the system, be it the desktop or the networking stack. (Whether these also cause the problem with the missing program icon I cannot say.)

I am not in a position to say whether the Manuskript support for snap installs is flawed/incomplete, or whether it is something about your system, so that is about as helpful as I can be.

@tomwardill was the person who originally implemented the support for snap packaging; perhaps they would be willing to take a look and see what is going on here?