Package Details: kazam 1.4.5-9

Git Clone URL: https://aur.archlinux.org/kazam.git (read-only, click to copy)
Package Base: kazam
Description: Screencast and screenshot application created with design in mind
Upstream URL: https://launchpad.net/kazam
Keywords: screencast
Licenses: GPL
Submitter: Maxwel
Maintainer: heavysink (lilac)
Last Packager: heavysink
Votes: 135
Popularity: 0.000469
First Submitted: 2012-05-21 21:04 (UTC)
Last Updated: 2020-06-12 07:05 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

wskorodecki commented on 2018-08-27 16:28 (UTC)

@getaceres Perhaps you don't have python3-keybinder package?

yodalee commented on 2018-08-27 13:56 (UTC)

If you run into problem with ValueError: Invalid section name: 'DEFAULT' The fix is: edit the file "/usr/lib/python3.7/site-packages/kazam/backend/config.py" Replace line 77: ConfigParser.init(self, self.DEFAULTS[0]['keys'] with ConfigParser.init__(self) can fix this issue.

getaceres commented on 2018-08-27 10:11 (UTC) (edited on 2018-08-27 10:12 (UTC) by getaceres)

Hello @wslorodecki. I'm getting this error when trying to run your archlinux branch:

jose@jose-pc:~/Programs/kazam$ git status On branch archlinux Your branch is up to date with 'origin/archlinux'.

nothing to commit, working tree clean jose@jose-pc:~/Programs/kazam$ ./bin/kazam WARNING Kazam - Running from local directory, AppIndicator icons could be missing. /home/jose/Programs/kazam/kazam/backend/prefs.py:342: 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 Gst Traceback (most recent call last): File "./bin/kazam", line 163, in <module> app = KazamApp(datadir, dist, args.debug, args.test, args.nosound, args.silent) File "/home/jose/Programs/kazam/kazam/app.py", line 126, in init self.indicator = KazamIndicator(prefs.silent) File "/home/jose/Programs/kazam/kazam/frontend/indicator.py", line 232, in init super(KazamIndicator, self).init() File "/home/jose/Programs/kazam/kazam/frontend/indicator.py", line 98, in init gi.require_version('Keybinder', '3.0') File "/usr/lib/python3.7/site-packages/gi/init.py", line 130, in require_version raise ValueError('Namespace %s not available' % namespace) ValueError: Namespace Keybinder not available</module>

argenis commented on 2018-08-24 02:55 (UTC) (edited on 2018-08-24 02:55 (UTC) by argenis)

Thanks @wslorodecki I just using and running the app

wskorodecki commented on 2018-08-23 16:50 (UTC)

TL;DR: I've just fixed one line in code which should help. Details: This is because the current Python version which you are using to run Kazam does not contain Kazam modules, i.e the "/usr/lib/python3.7/site-packages/kazam" directory does not exist. This may be easily fixed by reinstalling Kazam directly from AUR (using yaourt etc.) but if you try to run Kazam from local directory of my cloned repository it will still try to load modules from that system directory, but these files are not fixed so this will not be enough. I've just fixed one line of code to force loading modules from local directory instead, if appropriate.

argenis commented on 2018-08-23 12:39 (UTC) (edited on 2018-08-23 12:40 (UTC) by argenis)

I tried @wslorodecki suggestion, but a get this:

WARNING Kazam - Running from local directory, AppIndicator icons could be missing. Traceback (most recent call last): File "./bin/kazam", line 97, in <module> from kazam.version import * ModuleNotFoundError: No module named 'kazam'</module>

wskorodecki commented on 2018-08-23 07:59 (UTC)

I'm not a Python developer so I'm not sure if changes that I've applied are 100% valid, but after that Kazam is working fine on my environment: https://github.com/wskorodecki/kazam/commit/504e68f4f2451e30b4614f63793f26c1b33b3f40

The fastest way to get Kazam running again is to clone the "archlinux" branch and start Kazam from local directory: ./bin/kazam

andheisus commented on 2018-08-19 04:38 (UTC)

After an update set I can no longer open kazam, and am getting errors I am not sure how to interpret:

$ kazam /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/bin/kazam:75: DeprecationWarning: dist() and linux_distribution() functions are deprecated in Python 3.5 dist = platform.linux_distribution() Traceback (most recent call last): File "/usr/bin/kazam", line 146, in <module> from kazam.app import KazamApp File "/usr/lib/python3.7/site-packages/kazam/app.py", line 35, in <module> from kazam.backend.prefs import * File "/usr/lib/python3.7/site-packages/kazam/backend/prefs.py", line 478, in <module> prefs = Prefs() File "/usr/lib/python3.7/site-packages/kazam/backend/prefs.py", line 119, in init self.config = KazamConfig() File "/usr/lib/python3.7/site-packages/kazam/backend/config.py", line 76, in init ConfigParser.init(self, self.DEFAULTS[0]['keys']) File "/usr/lib/python3.7/configparser.py", line 638, in init self._read_defaults(defaults) File "/usr/lib/python3.7/configparser.py", line 1216, in _read_defaults self.read_dict({self.default_section: defaults}) File "/usr/lib/python3.7/configparser.py", line 753, in read_dict self.set(section, key, value) File "/usr/lib/python3.7/site-packages/kazam/backend/config.py", line 127, in set self.add_section(section) File "/usr/lib/python3.7/configparser.py", line 1205, in add_section super().add_section(section) File "/usr/lib/python3.7/configparser.py", line 655, in add_section raise ValueError('Invalid section name: %r' % section) ValueError: Invalid section name: 'DEFAULT'</module></module></module>

Is there a way to fix this? It won't open in the xfce whisker menu or the terminal. Thanks.

silenx commented on 2018-04-25 12:40 (UTC) (edited on 2018-04-25 12:50 (UTC) by silenx)

I'm also interested in kazam, version 1.5.3 ( unstable ) have more some little feature ( example mouse click highlight )

gccstr commented on 2018-04-19 22:42 (UTC)

@Bachsau thinking about it, but for now taking care if something it's required (but no one is blaming about nothing), probably a deletion will happen in a future.