This bug seems to have been fixed in upstream on 2017-06-13 (according to the
link in comment #3). But testing that seems to require GTK+3.20.
Perhaps it is time to upgrade to 18.04/bionic beaver...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
In my case this turned out to be a known bug with the "modesetting" graphics
driver, a fix for which would be available in linux 4.11 earliest:
https://bugs.freedesktop.org/show_bug.cgi?id=96572
Perhaps xbacklight works out-of-the-box on Ubuntu 17.10 :)
Googling around suggests Ubuntu 16.04
xbacklight stopped working just now after an 'apt updgrade'. Ubuntu 16.04.3,
Dell XPS-13.
Writing directly to /sys/class/backlight/intel_backlight/brightness still works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Happens for me too, but for me hitting Ctrl-C unfreezes the autocompleter, and
it prints out whatever it has found up till then.
Quite annoying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600173
Repeat with:
$ python
import clang.cindex
index = clang.cindex.Index.create()
Traceback (most recent call last):
File stdin, line 1, in module
File /usr/lib/python2.7/dist-packages/clang/cindex.py, line 2047, in create
return Index(conf.lib.clang_createIndex(excludeDecls, 0))
File
Public bug reported:
cgdb freezes on startup. It starts gdb, but never reaches the point
where the gdb prompt is shown. This repeats on every try.
This happens on ARM with 14.04, but happened also on 13.10.
Compiling cgdb and/or gdb from source did not repeat the issue.
I.e. if using a
If you compile gdb from source and use that as the cgdb backend, does it
repeat?
Does it hang if you start cgdb without a debuggee as command-line parameter?
I might have just reported a dupe:
https://bugs.launchpad.net/ubuntu/+source/cgdb/+bug/1357378
See also:
