GNOME Bugzilla – Bug 729345
Can't launch in absence of /proc/modules on host
Last modified: 2016-03-31 13:22:07 UTC
I'm using GNOME 3.10 on a Gentoo Linux system. I cannot start GNOME Boxes. If I try with command "gnome-boxes" on a terminal I get the following error message: $ gnome-boxes (gnome-boxes:17921): Boxes-ERROR **: util-app.vala:342: Error opening file: No such file or directory Trace/breakpoint trap I tried opening util-app.vala from the source tarball and going to line 342, but I can't understand which file it is referring to in the error message. ----- # emerge -pv gnome-boxes These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] gnome-extra/gnome-boxes-3.10.2 USE="usbredir -smartcard" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB
util-app.vala:342 is part of the check_module_kvm_loaded() method here which parses the content of /proc/modules. Do you have such a file and can you read it (cat /proc/modules) as the user who runs boxes? I guess this method could be changed to: diff --git a/src/util-app.vala b/src/util-app.vala index f4392e3..0db296e 100644 --- a/src/util-app.vala +++ b/src/util-app.vala @@ -339,7 +339,7 @@ public async bool check_module_kvm_loaded () { break; } } catch (GLib.Error error) { - GLib.error (error.message); + debug ("Failed to parse '/proc/modules': %s", error.message); } debug ("check_module_kvm_loaded: " + yes_no (result));
I had no modules support in the kernel when I reported this bug. I now have enabled it and I can read the content of /proc/modules. But I still can't start gnome-boxes, even though I get another error message (segmentation fault). I'm going to file another bug report.
Please also see https://bugzilla.gnome.org/show_bug.cgi?id=730022.
Also, in my opinion GNOME Boxes should work fine even if one doesn't have modules support enabled in the kernel.
(In reply to comment #4) > Also, in my opinion GNOME Boxes should work fine even if one doesn't have > modules support enabled in the kernel. Yeah, its supposed to at least. I enabled it to work w/o that a long time ago so it not working is a bug, not a limitation.
(In reply to comment #5) > (In reply to comment #4) > > Also, in my opinion GNOME Boxes should work fine even if one doesn't have > > modules support enabled in the kernel. > > Yeah, its supposed to at least. I enabled it to work w/o that a long time ago > so it not working is a bug, not a limitation. Err... sorry I misread. You are talking about /proc/modules file, not kvm modules. Anyway, you are still correct.
commit: b9a413f b9a413fe1478473bec698e258418fb5f657a26d7 Author: Zeeshan Ali (Khattak) <zeeshanak@gnome.org> Date: Wed May 21 19:28:13 2014 +0100 util-app: Don't abort on inability to read /proc files Calling GLib.error() implies a call to abort() so its better if we display the error with GLib.critical().
I'm not even sure it's worth a critical. The name of the file which could not be read should be mentioned though as done in comment #1, especially if the error is a critical.
commit: 79490be 79490bed2979d4f169bd112e3d0f561ad4e2e64d Author: Zeeshan Ali (Khattak) <zeeshanak@gnome.org> Date: Thu May 22 12:46:43 2014 +0100 util-app: Turn 2 criticals into warnings These messages are not severe enough to be criticals. https://bugzilla.gnome.org/show_bug.cgi?id=729345 commit: abf9d31 abf9d31ea80f4fa5d51d976620a1854b627b96a4 Author: Zeeshan Ali (Khattak) <zeeshanak@gnome.org> Date: Thu May 22 12:44:47 2014 +0100 util-app: Improved critical messages Ensure path of the file, that we failed to read is included in the messages. https://bugzilla.gnome.org/show_bug.cgi?id=729345
Thanks!