kazam fails with “PyGIWarning: Gtk was imported without specifying a version first…”
After installing kazam screen casting software, it is not launching.
I am using Ubuntu 17.04.
Update:
/usr/bin/kazam:32: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk
/usr/lib/python3/dist-packages/kazam/frontend/window_area.py:30: PyGIWarning: Wnck was imported without specifying a version first. Use gi.require_version('Wnck', '3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk, GObject, Gdk, Wnck, GdkX11
/usr/lib/python3/dist-packages/kazam/backend/gstreamer.py:35: PyGIWarning: Gst was imported without specifying a version first. Use gi.require_version('Gst', '1.0') before import to ensure that the right version gets loaded.
from gi.repository import GObject, Gst
/usr/lib/python3/dist-packages/kazam/frontend/indicator.py:148: PyGIWarning: AppIndicator3 was imported without specifying a version first. Use gi.require_version('AppIndicator3', '0.1') before import to ensure that the right version gets loaded.
from gi.repository import AppIndicator3
/usr/lib/python3/dist-packages/kazam/frontend/indicator.py:97: PyGIWarning: Keybinder was imported without specifying a version first. Use gi.require_version('Keybinder', '3.0') before import to ensure that the right version gets loaded.
from gi.repository import Keybinder
Segmentation fault (core dumped)
python3 pygtk kazam
add a comment |
After installing kazam screen casting software, it is not launching.
I am using Ubuntu 17.04.
Update:
/usr/bin/kazam:32: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk
/usr/lib/python3/dist-packages/kazam/frontend/window_area.py:30: PyGIWarning: Wnck was imported without specifying a version first. Use gi.require_version('Wnck', '3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk, GObject, Gdk, Wnck, GdkX11
/usr/lib/python3/dist-packages/kazam/backend/gstreamer.py:35: PyGIWarning: Gst was imported without specifying a version first. Use gi.require_version('Gst', '1.0') before import to ensure that the right version gets loaded.
from gi.repository import GObject, Gst
/usr/lib/python3/dist-packages/kazam/frontend/indicator.py:148: PyGIWarning: AppIndicator3 was imported without specifying a version first. Use gi.require_version('AppIndicator3', '0.1') before import to ensure that the right version gets loaded.
from gi.repository import AppIndicator3
/usr/lib/python3/dist-packages/kazam/frontend/indicator.py:97: PyGIWarning: Keybinder was imported without specifying a version first. Use gi.require_version('Keybinder', '3.0') before import to ensure that the right version gets loaded.
from gi.repository import Keybinder
Segmentation fault (core dumped)
python3 pygtk kazam
Open a shell and typekazam
[Enter]. What happens when you do that?
– Tomáš Pospíšek
Dec 1 '17 at 20:44
see the updated ques
– Gaurab Kumar
Dec 1 '17 at 20:48
can you transform that into text, so it becomes copy/pastable and searchable?
– Tomáš Pospíšek
Dec 1 '17 at 20:51
Did you search for the problem? Try this search: google.ch/search?q=PyGIWarning+kazam. The first hit leads to this: github.com/sconts/kazam/issues/4 Can you walk on from there?
– Tomáš Pospíšek
Dec 2 '17 at 10:59
Those are just warnings and will not cause an application to crash. It should be fixed though by the Kazam developers by just doing what it says: addgi.require_version(lib, version)
for each warning. I think it's best to ask on the Kazam GitHub page about this issue, they should walk you through on how to debug that segfault.
– Timo
Dec 3 '17 at 8:42
add a comment |
After installing kazam screen casting software, it is not launching.
I am using Ubuntu 17.04.
Update:
/usr/bin/kazam:32: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk
/usr/lib/python3/dist-packages/kazam/frontend/window_area.py:30: PyGIWarning: Wnck was imported without specifying a version first. Use gi.require_version('Wnck', '3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk, GObject, Gdk, Wnck, GdkX11
/usr/lib/python3/dist-packages/kazam/backend/gstreamer.py:35: PyGIWarning: Gst was imported without specifying a version first. Use gi.require_version('Gst', '1.0') before import to ensure that the right version gets loaded.
from gi.repository import GObject, Gst
/usr/lib/python3/dist-packages/kazam/frontend/indicator.py:148: PyGIWarning: AppIndicator3 was imported without specifying a version first. Use gi.require_version('AppIndicator3', '0.1') before import to ensure that the right version gets loaded.
from gi.repository import AppIndicator3
/usr/lib/python3/dist-packages/kazam/frontend/indicator.py:97: PyGIWarning: Keybinder was imported without specifying a version first. Use gi.require_version('Keybinder', '3.0') before import to ensure that the right version gets loaded.
from gi.repository import Keybinder
Segmentation fault (core dumped)
python3 pygtk kazam
After installing kazam screen casting software, it is not launching.
I am using Ubuntu 17.04.
Update:
/usr/bin/kazam:32: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk
/usr/lib/python3/dist-packages/kazam/frontend/window_area.py:30: PyGIWarning: Wnck was imported without specifying a version first. Use gi.require_version('Wnck', '3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk, GObject, Gdk, Wnck, GdkX11
/usr/lib/python3/dist-packages/kazam/backend/gstreamer.py:35: PyGIWarning: Gst was imported without specifying a version first. Use gi.require_version('Gst', '1.0') before import to ensure that the right version gets loaded.
from gi.repository import GObject, Gst
/usr/lib/python3/dist-packages/kazam/frontend/indicator.py:148: PyGIWarning: AppIndicator3 was imported without specifying a version first. Use gi.require_version('AppIndicator3', '0.1') before import to ensure that the right version gets loaded.
from gi.repository import AppIndicator3
/usr/lib/python3/dist-packages/kazam/frontend/indicator.py:97: PyGIWarning: Keybinder was imported without specifying a version first. Use gi.require_version('Keybinder', '3.0') before import to ensure that the right version gets loaded.
from gi.repository import Keybinder
Segmentation fault (core dumped)
python3 pygtk kazam
python3 pygtk kazam
edited Dec 28 '18 at 11:18
Sourav Ghosh
38529
38529
asked Dec 1 '17 at 19:04
Gaurab KumarGaurab Kumar
10115
10115
Open a shell and typekazam
[Enter]. What happens when you do that?
– Tomáš Pospíšek
Dec 1 '17 at 20:44
see the updated ques
– Gaurab Kumar
Dec 1 '17 at 20:48
can you transform that into text, so it becomes copy/pastable and searchable?
– Tomáš Pospíšek
Dec 1 '17 at 20:51
Did you search for the problem? Try this search: google.ch/search?q=PyGIWarning+kazam. The first hit leads to this: github.com/sconts/kazam/issues/4 Can you walk on from there?
– Tomáš Pospíšek
Dec 2 '17 at 10:59
Those are just warnings and will not cause an application to crash. It should be fixed though by the Kazam developers by just doing what it says: addgi.require_version(lib, version)
for each warning. I think it's best to ask on the Kazam GitHub page about this issue, they should walk you through on how to debug that segfault.
– Timo
Dec 3 '17 at 8:42
add a comment |
Open a shell and typekazam
[Enter]. What happens when you do that?
– Tomáš Pospíšek
Dec 1 '17 at 20:44
see the updated ques
– Gaurab Kumar
Dec 1 '17 at 20:48
can you transform that into text, so it becomes copy/pastable and searchable?
– Tomáš Pospíšek
Dec 1 '17 at 20:51
Did you search for the problem? Try this search: google.ch/search?q=PyGIWarning+kazam. The first hit leads to this: github.com/sconts/kazam/issues/4 Can you walk on from there?
– Tomáš Pospíšek
Dec 2 '17 at 10:59
Those are just warnings and will not cause an application to crash. It should be fixed though by the Kazam developers by just doing what it says: addgi.require_version(lib, version)
for each warning. I think it's best to ask on the Kazam GitHub page about this issue, they should walk you through on how to debug that segfault.
– Timo
Dec 3 '17 at 8:42
Open a shell and type
kazam
[Enter]. What happens when you do that?– Tomáš Pospíšek
Dec 1 '17 at 20:44
Open a shell and type
kazam
[Enter]. What happens when you do that?– Tomáš Pospíšek
Dec 1 '17 at 20:44
see the updated ques
– Gaurab Kumar
Dec 1 '17 at 20:48
see the updated ques
– Gaurab Kumar
Dec 1 '17 at 20:48
can you transform that into text, so it becomes copy/pastable and searchable?
– Tomáš Pospíšek
Dec 1 '17 at 20:51
can you transform that into text, so it becomes copy/pastable and searchable?
– Tomáš Pospíšek
Dec 1 '17 at 20:51
Did you search for the problem? Try this search: google.ch/search?q=PyGIWarning+kazam. The first hit leads to this: github.com/sconts/kazam/issues/4 Can you walk on from there?
– Tomáš Pospíšek
Dec 2 '17 at 10:59
Did you search for the problem? Try this search: google.ch/search?q=PyGIWarning+kazam. The first hit leads to this: github.com/sconts/kazam/issues/4 Can you walk on from there?
– Tomáš Pospíšek
Dec 2 '17 at 10:59
Those are just warnings and will not cause an application to crash. It should be fixed though by the Kazam developers by just doing what it says: add
gi.require_version(lib, version)
for each warning. I think it's best to ask on the Kazam GitHub page about this issue, they should walk you through on how to debug that segfault.– Timo
Dec 3 '17 at 8:42
Those are just warnings and will not cause an application to crash. It should be fixed though by the Kazam developers by just doing what it says: add
gi.require_version(lib, version)
for each warning. I think it's best to ask on the Kazam GitHub page about this issue, they should walk you through on how to debug that segfault.– Timo
Dec 3 '17 at 8:42
add a comment |
2 Answers
2
active
oldest
votes
The problem with this segmentation fault is in Kazam hotkeys bindings.
Maybe the system cannot give some keybingings to Kazam, thus we get an exception.
The rough solution is to remove Kazam’s global keybingings:
Open the file:
/usr/lib/python3/dist-packages/kazam/frontend/indicator.py
Find these strings (about line 100 or so):
Keybinder.bind("<Super><Ctrl>R", self.cb_hotkeys, "start-request")
Keybinder.bind("<Super><Ctrl>F", self.cb_hotkeys, "stop-request")
Keybinder.bind("<Super><Ctrl>P", self.cb_hotkeys, "pause-request")
Keybinder.bind("<Super><Ctrl>W", self.cb_hotkeys, "show-request")
Keybinder.bind("<Super><Ctrl>Q", self.cb_hotkeys, "quit-request")
Comment them out:
#Keybinder.bind("<Super><Ctrl>R", self.cb_hotkeys, "start-request")
#Keybinder.bind("<Super><Ctrl>F", self.cb_hotkeys, "stop-request")
#Keybinder.bind("<Super><Ctrl>P", self.cb_hotkeys, "pause-request")
#Keybinder.bind("<Super><Ctrl>W", self.cb_hotkeys, "show-request")
#Keybinder.bind("<Super><Ctrl>Q", self.cb_hotkeys, "quit-request")
Save the file.
Run Kazam.
You’re awesome.
After that, you cannot use those hotkeys though, but at least Kazam will work.
not work for me..
– Chan Kim
Oct 11 '18 at 6:32
add a comment |
Solved: I just needed to install python3-xlib:
sudo apt-get update
sudo apt-get install python3-xlib
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f982233%2fkazam-fails-with-pygiwarning-gtk-was-imported-without-specifying-a-version-fir%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The problem with this segmentation fault is in Kazam hotkeys bindings.
Maybe the system cannot give some keybingings to Kazam, thus we get an exception.
The rough solution is to remove Kazam’s global keybingings:
Open the file:
/usr/lib/python3/dist-packages/kazam/frontend/indicator.py
Find these strings (about line 100 or so):
Keybinder.bind("<Super><Ctrl>R", self.cb_hotkeys, "start-request")
Keybinder.bind("<Super><Ctrl>F", self.cb_hotkeys, "stop-request")
Keybinder.bind("<Super><Ctrl>P", self.cb_hotkeys, "pause-request")
Keybinder.bind("<Super><Ctrl>W", self.cb_hotkeys, "show-request")
Keybinder.bind("<Super><Ctrl>Q", self.cb_hotkeys, "quit-request")
Comment them out:
#Keybinder.bind("<Super><Ctrl>R", self.cb_hotkeys, "start-request")
#Keybinder.bind("<Super><Ctrl>F", self.cb_hotkeys, "stop-request")
#Keybinder.bind("<Super><Ctrl>P", self.cb_hotkeys, "pause-request")
#Keybinder.bind("<Super><Ctrl>W", self.cb_hotkeys, "show-request")
#Keybinder.bind("<Super><Ctrl>Q", self.cb_hotkeys, "quit-request")
Save the file.
Run Kazam.
You’re awesome.
After that, you cannot use those hotkeys though, but at least Kazam will work.
not work for me..
– Chan Kim
Oct 11 '18 at 6:32
add a comment |
The problem with this segmentation fault is in Kazam hotkeys bindings.
Maybe the system cannot give some keybingings to Kazam, thus we get an exception.
The rough solution is to remove Kazam’s global keybingings:
Open the file:
/usr/lib/python3/dist-packages/kazam/frontend/indicator.py
Find these strings (about line 100 or so):
Keybinder.bind("<Super><Ctrl>R", self.cb_hotkeys, "start-request")
Keybinder.bind("<Super><Ctrl>F", self.cb_hotkeys, "stop-request")
Keybinder.bind("<Super><Ctrl>P", self.cb_hotkeys, "pause-request")
Keybinder.bind("<Super><Ctrl>W", self.cb_hotkeys, "show-request")
Keybinder.bind("<Super><Ctrl>Q", self.cb_hotkeys, "quit-request")
Comment them out:
#Keybinder.bind("<Super><Ctrl>R", self.cb_hotkeys, "start-request")
#Keybinder.bind("<Super><Ctrl>F", self.cb_hotkeys, "stop-request")
#Keybinder.bind("<Super><Ctrl>P", self.cb_hotkeys, "pause-request")
#Keybinder.bind("<Super><Ctrl>W", self.cb_hotkeys, "show-request")
#Keybinder.bind("<Super><Ctrl>Q", self.cb_hotkeys, "quit-request")
Save the file.
Run Kazam.
You’re awesome.
After that, you cannot use those hotkeys though, but at least Kazam will work.
not work for me..
– Chan Kim
Oct 11 '18 at 6:32
add a comment |
The problem with this segmentation fault is in Kazam hotkeys bindings.
Maybe the system cannot give some keybingings to Kazam, thus we get an exception.
The rough solution is to remove Kazam’s global keybingings:
Open the file:
/usr/lib/python3/dist-packages/kazam/frontend/indicator.py
Find these strings (about line 100 or so):
Keybinder.bind("<Super><Ctrl>R", self.cb_hotkeys, "start-request")
Keybinder.bind("<Super><Ctrl>F", self.cb_hotkeys, "stop-request")
Keybinder.bind("<Super><Ctrl>P", self.cb_hotkeys, "pause-request")
Keybinder.bind("<Super><Ctrl>W", self.cb_hotkeys, "show-request")
Keybinder.bind("<Super><Ctrl>Q", self.cb_hotkeys, "quit-request")
Comment them out:
#Keybinder.bind("<Super><Ctrl>R", self.cb_hotkeys, "start-request")
#Keybinder.bind("<Super><Ctrl>F", self.cb_hotkeys, "stop-request")
#Keybinder.bind("<Super><Ctrl>P", self.cb_hotkeys, "pause-request")
#Keybinder.bind("<Super><Ctrl>W", self.cb_hotkeys, "show-request")
#Keybinder.bind("<Super><Ctrl>Q", self.cb_hotkeys, "quit-request")
Save the file.
Run Kazam.
You’re awesome.
After that, you cannot use those hotkeys though, but at least Kazam will work.
The problem with this segmentation fault is in Kazam hotkeys bindings.
Maybe the system cannot give some keybingings to Kazam, thus we get an exception.
The rough solution is to remove Kazam’s global keybingings:
Open the file:
/usr/lib/python3/dist-packages/kazam/frontend/indicator.py
Find these strings (about line 100 or so):
Keybinder.bind("<Super><Ctrl>R", self.cb_hotkeys, "start-request")
Keybinder.bind("<Super><Ctrl>F", self.cb_hotkeys, "stop-request")
Keybinder.bind("<Super><Ctrl>P", self.cb_hotkeys, "pause-request")
Keybinder.bind("<Super><Ctrl>W", self.cb_hotkeys, "show-request")
Keybinder.bind("<Super><Ctrl>Q", self.cb_hotkeys, "quit-request")
Comment them out:
#Keybinder.bind("<Super><Ctrl>R", self.cb_hotkeys, "start-request")
#Keybinder.bind("<Super><Ctrl>F", self.cb_hotkeys, "stop-request")
#Keybinder.bind("<Super><Ctrl>P", self.cb_hotkeys, "pause-request")
#Keybinder.bind("<Super><Ctrl>W", self.cb_hotkeys, "show-request")
#Keybinder.bind("<Super><Ctrl>Q", self.cb_hotkeys, "quit-request")
Save the file.
Run Kazam.
You’re awesome.
After that, you cannot use those hotkeys though, but at least Kazam will work.
answered Dec 25 '17 at 9:25
Sasha MaximALSasha MaximAL
1217
1217
not work for me..
– Chan Kim
Oct 11 '18 at 6:32
add a comment |
not work for me..
– Chan Kim
Oct 11 '18 at 6:32
not work for me..
– Chan Kim
Oct 11 '18 at 6:32
not work for me..
– Chan Kim
Oct 11 '18 at 6:32
add a comment |
Solved: I just needed to install python3-xlib:
sudo apt-get update
sudo apt-get install python3-xlib
add a comment |
Solved: I just needed to install python3-xlib:
sudo apt-get update
sudo apt-get install python3-xlib
add a comment |
Solved: I just needed to install python3-xlib:
sudo apt-get update
sudo apt-get install python3-xlib
Solved: I just needed to install python3-xlib:
sudo apt-get update
sudo apt-get install python3-xlib
answered Dec 15 '17 at 6:48
Gaurab KumarGaurab Kumar
10115
10115
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f982233%2fkazam-fails-with-pygiwarning-gtk-was-imported-without-specifying-a-version-fir%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Open a shell and type
kazam
[Enter]. What happens when you do that?– Tomáš Pospíšek
Dec 1 '17 at 20:44
see the updated ques
– Gaurab Kumar
Dec 1 '17 at 20:48
can you transform that into text, so it becomes copy/pastable and searchable?
– Tomáš Pospíšek
Dec 1 '17 at 20:51
Did you search for the problem? Try this search: google.ch/search?q=PyGIWarning+kazam. The first hit leads to this: github.com/sconts/kazam/issues/4 Can you walk on from there?
– Tomáš Pospíšek
Dec 2 '17 at 10:59
Those are just warnings and will not cause an application to crash. It should be fixed though by the Kazam developers by just doing what it says: add
gi.require_version(lib, version)
for each warning. I think it's best to ask on the Kazam GitHub page about this issue, they should walk you through on how to debug that segfault.– Timo
Dec 3 '17 at 8:42