gnunet-gtk and gnunet-qt should depend on gnunet-tools
Bug #134307 reported by
Schmirrwurst
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnunet-gtk (Ubuntu) |
Fix Released
|
Undecided
|
Luke Yelavich | ||
| gnunet-qt (Ubuntu) |
Fix Released
|
Undecided
|
Luke Yelavich | ||
Bug Description
If you don't install gnunet-tools you get the following error message:
gnunet qt doesn't start, here is the output from the terminal :
aoû 23 18:00:58 ERROR: Failed to run /usr//bin/
aoû 23 18:00:58 ERROR: `fopen' failed on file `/home/
I'm on Kubuntu Gusty tribe 4 and gnunet-qt v0.7.1
Revision history for this message
| Chris Wagner (chris-wagner) wrote | #1 |
Revision history for this message
| Chris Wagner (chris-wagner) wrote | #2 |
Revision history for this message
| Markus Golser (golserma) wrote | #3 |
| Changed in gnunet: | |
| status: | New → Confirmed |
| description: | updated |
| Changed in gnunet-gtk: | |
| assignee: | nobody → themuso |
| status: | New → In Progress |
| Changed in gnunet-qt: | |
| assignee: | nobody → themuso |
| status: | Confirmed → In Progress |
Revision history for this message
| Luke Yelavich (themuso) wrote | #4 |
| Changed in gnunet-gtk: | |
| status: | In Progress → Fix Released |
Revision history for this message
| Luke Yelavich (themuso) wrote | #5 |
| Changed in gnunet-qt: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
This doesn't seem to be specific to gnunet-qt; it affects gnunet-gtk as well.
I think the problem is, actually, that the base "gnunet" package needs to be installed. I installed that package, and the error that you mention went away, but now I have a new one (!). I've never had good luck with gnunet...
Even if this is resolved by installing the "gnunet" package, I still consider it a bug. There should be a better error message. The ubuntu packages for gnunet-qt and gnunet-gtk should either depend on the gnunet package or they should be patched to give a reasonable error message when you attempt to run them without that config file.