Bug#867619: libpam-cgfs: failed creating cgroups
Package: libpam-cgfs Version: 2.0.7-0ubuntu4 Severity: important Dear Maintainer, I couldn't start my unpriviledged containers anymore, seems like the libpam-cgfs is the culprit, according to the discussion I had here : https://discuss.linuxcontainers.org/t/failed-creating-cgroups/272/6l Installing the ubuntu package solved my issue Using the debian package 2.0.7-1 leads to this type of error while trying to start an unpriviledged container lxc-start 20170707164658.915 INFO lxc_cgroup - cgroups/cgroup.c:cgroup_init:68 - cgroup driver cgroupfs initing for modoboa lxc-start 20170707164658.915 ERRORlxc_cgfs - cgroups/cgfs.c:lxc_cgroupfs_create:909 - Could not set clone_children to 1 for cpuset hierarchy in parent cgroup. lxc-start 20170707164658.915 ERRORlxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: failed to delete /sys/fs/cgroup/blkio/user.slice lxc-start 20170707164658.915 ERRORlxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Read-only file system - cgroup_rmdir: failed to delete /sys/fs/cgroup/perf_event/ lxc-start 20170707164658.915 ERRORlxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Read-only file system - cgroup_rmdir: failed to delete /sys/fs/cgroup/freezer/ lxc-start 20170707164658.915 ERRORlxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: failed to delete /sys/fs/cgroup/pids/user.slice/user-1000.slice/session-138.scope lxc-start 20170707164658.915 ERRORlxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: failed to delete /sys/fs/cgroup/devices/user.slice lxc-start 20170707164658.915 ERRORlxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpu,cpuacct/user.slice lxc-start 20170707164658.915 ERRORlxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Read-only file system - cgroup_rmdir: failed to delete /sys/fs/cgroup/net_cls,net_prio/ lxc-start 20170707164658.915 ERRORlxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Read-only file system - cgroup_rmdir: failed to delete /sys/fs/cgroup/cpuset/ lxc-start 20170707164658.915 ERRORlxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: failed to delete /sys/fs/cgroup/memory/user.slice lxc-start 20170707164658.915 ERRORlxc_cgfs - cgroups/cgfs.c:cgroup_rmdir:209 - Permission denied - cgroup_rmdir: failed to delete /sys/fs/cgroup/systemd/user.slice/user-1000.slice/session-138.scope lxc-start 20170707164658.915 ERRORlxc_start - start.c:lxc_spawn:1119 - Failed creating cgroups. lxc-start 20170707164658.915 ERRORlxc_start - start.c:__lxc_start:1354 - Failed to spawn container "modoboa". -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (980, 'stable'), (500, 'testing-debug'), (90, 'experimental'), (90, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libpam-cgfs depends on: ii libc6 2.24-12 ii libpam-runtime 1.1.8-3.6 ii libpam0g1.1.8-3.6 ii systemd 233-9 libpam-cgfs recommends no packages. libpam-cgfs suggests no packages. -- no debconf information
Bug#863640: retext: I install retext, try to run it, it segfault, please see output below
no worries, I got it running from git :) works fine now thanks a lot On Tue, May 30, 2017 at 9:39 PM, Dmitry Shachnev <mity...@debian.org> wrote: > On Tue, May 30, 2017 at 03:00:25PM +0200, Benoit Barthelet wrote: > > here it is > > > > ➜ ~ python3 -X faulthandler /usr/bin/retext > > Using configuration file: /home/lotso/.config/ReText project/ReText.conf > > Fatal Python error: Segmentation fault > > > > Current thread 0x7f7f0a0b9700 (most recent call first): > > File "/usr/share/retext/ReText/xsettings.py", line 132 in > get_raw_xsettings > > File "/usr/share/retext/ReText/xsettings.py", line 187 in > get_xsettings > > File "/usr/share/retext/ReText/icontheme.py", line 20 in > get_from_xsettings > > File "/usr/share/retext/ReText/icontheme.py", line 49 in > get_icon_theme > > File "/usr/share/retext/ReText/window.py", line 68 in __init__ > > File "/usr/bin/retext", line 74 in main > > File "/usr/bin/retext", line 102 in > > [1]19648 segmentation fault python3 -X faulthandler /usr/bin/retext > > ➜ ~ > > Thank you! > > Fixed upstream in [1], will be in the next upload. Probably too late for > Stretch release though. > > A workaround would be creating a configuration file with contents like > this: > > [General] > iconTheme=Adwaita > > (Replace Adwaita with your favourite icon theme.) > > [1]: https://github.com/retext-project/retext/commit/fb5c5b8aae2ce904 > > -- > Dmitry Shachnev > -- benoit barthelet http://pgp.mit.edu/pks/lookup?op=get=0xF150E01A72F6D2EE
Bug#863640: retext: I install retext, try to run it, it segfault, please see output below
here it is ➜ ~ python3 -X faulthandler /usr/bin/retext Using configuration file: /home/lotso/.config/ReText project/ReText.conf Fatal Python error: Segmentation fault Current thread 0x7f7f0a0b9700 (most recent call first): File "/usr/share/retext/ReText/xsettings.py", line 132 in get_raw_xsettings File "/usr/share/retext/ReText/xsettings.py", line 187 in get_xsettings File "/usr/share/retext/ReText/icontheme.py", line 20 in get_from_xsettings File "/usr/share/retext/ReText/icontheme.py", line 49 in get_icon_theme File "/usr/share/retext/ReText/window.py", line 68 in __init__ File "/usr/bin/retext", line 74 in main File "/usr/bin/retext", line 102 in [1]19648 segmentation fault python3 -X faulthandler /usr/bin/retext ➜ ~ On Tue, May 30, 2017 at 2:57 PM, Dmitry Shachnev <mity...@debian.org> wrote: > On Tue, May 30, 2017 at 02:38:25PM +0200, Benoit Barthelet wrote: > > here is the backtrace, I hope it helps. I have loads of third party > python > > stuff, as for Qt modules I don't think so. > > Thank you, it is more helpful. > > Can you please also run this command and paste the output? > > python3 -X faulthandler /usr/bin/retext > > (The issue is with ctypes, so a Python trace would be more interesting > than a C one.) > > > I also have to add I don't have the /home/lotso/.config/ReText > > project/ReText.conf in question, should I have created it ? > > No, you should not. It will be created automatically when ReText starts > correctly and you open any file. > > -- > Dmitry Shachnev > -- benoit barthelet http://pgp.mit.edu/pks/lookup?op=get=0xF150E01A72F6D2EE
Bug#863640: retext: I install retext, try to run it, it segfault, please see output below
in type_call.lto_priv () at ../Objects/typeobject.c:905 #33 0x5575d647 in PyObject_Call () at ../Objects/abstract.c:2166 #34 0x556d4ee1 in do_call (nk=, na=0, pp_stack=0x7fffd850, func=) at ../Python/ceval.c:4951 #35 call_function (oparg=, pp_stack=0x7fffd850) at ../Python/ceval.c:4747 #36 PyEval_EvalFrameEx () at ../Python/ceval.c:3251 #37 0x556d97bf in _PyEval_EvalCodeWithName () at ../Python/ceval.c:4033 #38 0x556d54c9 in fast_function (nk=, na=, n=, pp_stack=0x7fffda60, func=) at ../Python/ceval.c:4828 #39 call_function (oparg=, pp_stack=0x7fffda60) at ../Python/ceval.c:4745 #40 PyEval_EvalFrameEx () at ../Python/ceval.c:3251 #41 0x556d9286 in _PyEval_EvalCodeWithName () at ../Python/ceval.c:4033 #42 0x556d9f9f in PyEval_EvalCodeEx () at ../Python/ceval.c:4054 #43 PyEval_EvalCode (co=, globals=, locals=) at ../Python/ceval.c:777 #44 0x557a78f2 in run_mod () at ../Python/pythonrun.c:976 #45 0x557a9e1d in PyRun_FileExFlags () at ../Python/pythonrun.c:929 #46 0x557aa5be in PyRun_SimpleFileExFlags () at ../Python/pythonrun.c:396 #47 0x557d84d7 in run_file (p_cf=0x7fffdcd0, filename=0x55c0d330 L"/usr/share/retext/retext.py", fp=0x55d122e0) at ../Modules/main.c:318 #48 Py_Main () at ../Modules/main.c:768 #49 0x55668c01 in main () at ../Programs/python.c:65 #50 0x76cef2b1 in __libc_start_main (main=0x55668b20 , argc=2, argv=0x7fffdee8, init=, fini=, rtld_fini=, stack_end=0x7fffded8) at ../csu/libc-start.c:291 #51 0x557721ba in _start () (gdb) quit A debugging session is active. Inferior 1 [process 18740] will be killed. Quit anyway? (y or n) y On Tue, May 30, 2017 at 2:38 PM, Benoit Barthelet < benoit.barthe...@gmail.com> wrote: > Effectively that wasn't very helpful sorry. > > TIL how to add dbgsym packages ! > > here is the backtrace, I hope it helps. I have loads of third party python > stuff, as for Qt modules I don't think so. > > I also have to add I don't have the /home/lotso/.config/ReText > project/ReText.conf in question, should I have created it ? > > > ➜ ~ gdb python3 > GNU gdb (Debian 7.12-6) 7.12.0.20161007-git > Copyright (C) 2016 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl. > html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "x86_64-linux-gnu". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>. > Find the GDB manual and other documentation resources online at: > <http://www.gnu.org/software/gdb/documentation/>. > For help, type "help". > Type "apropos word" to search for commands related to "word"... > Reading symbols from python3...Reading symbols from > /usr/lib/debug/.build-id/db/fc2e1a3c58b6d241b3f9af7b2fb3a2 > 4b81b90e.debug...done. > done. > (gdb) run /usr/share/retext/retext.py > Starting program: /usr/bin/python3 /usr/share/retext/retext.py > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > [New Thread 0x7fffe2d66700 (LWP 18065)] > Using configuration file: /home/lotso/.config/ReText project/ReText.conf > [New Thread 0x7fffe19f6700 (LWP 18066)] > > Thread 1 "python3" received signal SIGSEGV, Segmentation fault. > __GI___libc_free (mem=0x56182140) at malloc.c:2963 > 2963malloc.c: No such file or directory. > (gdb) bt > #0 __GI___libc_free (mem=0x56182140) at malloc.c:2963 > #1 0x7fffeeea4aa8 in ffi_call_unix64 () from /usr/lib/python3.5/lib- > dynload/_ctypes.cpython-35m-x86_64-linux-gnu.so > #2 0x7fffeeea450a in ffi_call () from /usr/lib/python3.5/lib- > dynload/_ctypes.cpython-35m-x86_64-linux-gnu.so > #3 0x7fffeee9dcb4 in _call_function_pointer (argcount=1, > resmem=0x7fffcb40, restype=, atypes=0x7fffcb00, > avalues=0x7fffcb20, > pProc=0x76d4a330 <__GI___libc_free>, flags=4353) at > ./Modules/_ctypes/callproc.c:813 > #4 _ctypes_callproc () at ./Modules/_ctypes/callproc.c:1151 > #5 0x7fffeee9c461 in PyCFuncPtr_call.lto_priv.76 () at > ./Modules/_ctypes/_ctypes.c:3876 > #6 0x5575d647 in PyObject_Call () at ../Objects/abstract.c:2166 > #7 0x556d4ee1 in do_call (nk=, na=1, > pp_stack=0x7fffce10, func=) at ../Python/ceval.c:4951 > #8 call_function (oparg=, pp_stack=0x7fffce10) at > ../Python/ceval.c:4747 > #9 PyEval_EvalFrameEx () at ../Python/ceva
Bug#863640: retext: I install retext, try to run it, it segfault, please see output below
valFrameEx () at ../Python/ceval.c:3251 #36 0x556d97bf in _PyEval_EvalCodeWithName () at ../Python/ceval.c:4033 #37 0x556d54c9 in fast_function (nk=, na=, n=, pp_stack=0x7fffda70, func=) at ../Python/ceval.c:4828 #38 call_function (oparg=, pp_stack=0x7fffda70) at ../Python/ceval.c:4745 ---Type to continue, or q to quit--- #39 PyEval_EvalFrameEx () at ../Python/ceval.c:3251 #40 0x556d9286 in _PyEval_EvalCodeWithName () at ../Python/ceval.c:4033 #41 0x556d9f9f in PyEval_EvalCodeEx () at ../Python/ceval.c:4054 #42 PyEval_EvalCode (co=, globals=, locals=) at ../Python/ceval.c:777 #43 0x557a78f2 in run_mod () at ../Python/pythonrun.c:976 #44 0x557a9e1d in PyRun_FileExFlags () at ../Python/pythonrun.c:929 #45 0x557aa5be in PyRun_SimpleFileExFlags () at ../Python/pythonrun.c:396 #46 0x557d84d7 in run_file (p_cf=0x7fffdce0, filename=0x55c0d280 L"/usr/share/retext/retext.py", fp=0x55d14360) at ../Modules/main.c:318 #47 Py_Main () at ../Modules/main.c:768 #48 0x55668c01 in main () at ../Programs/python.c:65 #49 0x76cef2b1 in __libc_start_main (main=0x55668b20 , argc=2, argv=0x7fffdef8, init=, fini=, rtld_fini=, stack_end=0x7fffdee8) at ../csu/libc-start.c:291 #50 0x557721ba in _start () (gdb) quit A debugging session is active. Inferior 1 [process 18058] will be killed. Quit anyway? (y or n) y ➜ ~ On Tue, May 30, 2017 at 1:46 PM, Dmitry Shachnev <mity...@debian.org> wrote: > Control: tags -1 moreinfo > > Hi Benoit! > > On Mon, May 29, 2017 at 05:36:22PM +0200, benoit barthelet wrote: > > ➜ ~ retext > > Using configuration file: /home/lotso/.config/ReText > project/ReText.conf > > [1]18072 segmentation fault retext > > Unfortunately this is not useful for determining the crash reason. > > Please install the debug packages libqt5core5a-dbgsym, libqt5gui5-dbgsym, > libqt5widgets5-dbgsym and python3-pyqt5.dbg, and then obtain the stack > trace > using the instructions at https://wiki.debian.org/HowToGetABacktrace. > > Also, please tell whether you have any third-party Python or Qt modules > installed: they may cause problems. > > -- > Dmitry Shachnev > -- benoit barthelet http://pgp.mit.edu/pks/lookup?op=get=0xF150E01A72F6D2EE
Bug#863640: retext: I install retext, try to run it, it segfault, please see output below
Package: retext
Version: 6.0.2-2
Severity: important
Dear Maintainer,
➜ ~ sudo aptitude install retext
The following NEW packages will be installed:
docutils-common{a} python3-docutils{a} python3-enchant{a} python3-markdown{a}
python3-markups{a} python3-pil{a} python3-pygments{a} python3-pyqt5{a}
python3-pyqt5.qtwebkit{a}
python3-roman{a} python3-textile{a} python3-yaml{a} retext
0 packages upgraded, 13 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/4,226 kB of archives. After unpacking 25.0 MB will be used.
Do you want to continue? [Y/n/?] y
(Reading database ... 368111 files and directories currently installed.)
Preparing to unpack .../00-docutils-common_0.13.1+dfsg-2_all.deb ...
Unpacking docutils-common (0.13.1+dfsg-2) ...
Selecting previously unselected package python3-roman.
Preparing to unpack .../01-python3-roman_2.0.0-2_all.deb ...
Unpacking python3-roman (2.0.0-2) ...
Selecting previously unselected package python3-docutils.
Preparing to unpack .../02-python3-docutils_0.13.1+dfsg-2_all.deb ...
Unpacking python3-docutils (0.13.1+dfsg-2) ...
Selecting previously unselected package python3-enchant.
Preparing to unpack .../03-python3-enchant_1.6.7-1_all.deb ...
Unpacking python3-enchant (1.6.7-1) ...
Selecting previously unselected package python3-markdown.
Preparing to unpack .../04-python3-markdown_2.6.8-1_all.deb ...
Unpacking python3-markdown (2.6.8-1) ...
Selecting previously unselected package python3-markups.
Preparing to unpack .../05-python3-markups_2.0.0-1_all.deb ...
Unpacking python3-markups (2.0.0-1) ...
Selecting previously unselected package python3-pil:amd64.
Preparing to unpack .../06-python3-pil_4.0.0-4_amd64.deb ...
Unpacking python3-pil:amd64 (4.0.0-4) ...
Selecting previously unselected package python3-pygments.
Preparing to unpack .../07-python3-pygments_2.2.0+dfsg-1_all.deb ...
Unpacking python3-pygments (2.2.0+dfsg-1) ...
Selecting previously unselected package python3-pyqt5.
Preparing to unpack .../08-python3-pyqt5_5.7+dfsg-5_amd64.deb ...
Unpacking python3-pyqt5 (5.7+dfsg-5) ...
Selecting previously unselected package python3-pyqt5.qtwebkit.
Preparing to unpack .../09-python3-pyqt5.qtwebkit_5.7+dfsg-5_amd64.deb ...
Unpacking python3-pyqt5.qtwebkit (5.7+dfsg-5) ...
Selecting previously unselected package python3-textile.
Preparing to unpack .../10-python3-textile_1%3a2.3.5-1_all.deb ...
Unpacking python3-textile (1:2.3.5-1) ...
Selecting previously unselected package python3-yaml.
Preparing to unpack .../11-python3-yaml_3.12-1_amd64.deb ...
Unpacking python3-yaml (3.12-1) ...
Selecting previously unselected package retext.
Preparing to unpack .../12-retext_6.0.2-2_all.deb ...
Unpacking retext (6.0.2-2) ...
Setting up python3-yaml (3.12-1) ...
Setting up python3-markdown (2.6.8-1) ...
Setting up python3-roman (2.0.0-2) ...
Setting up python3-pil:amd64 (4.0.0-4) ...
Setting up docutils-common (0.13.1+dfsg-2) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for desktop-file-utils (0.23-1) ...
Setting up python3-pyqt5 (5.7+dfsg-5) ...
Setting up python3-pyqt5.qtwebkit (5.7+dfsg-5) ...
Processing triggers for sgml-base (1.29) ...
Setting up python3-enchant (1.6.7-1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for shared-mime-info (1.8-1) ...
Unknown media type in type 'chemical/x-alchemy'
Unknown media type in type 'chemical/x-cache'
Unknown media type in type 'chemical/x-cactvs-ascii'
Unknown media type in type 'chemical/x-cactvs-binary'
Unknown media type in type 'chemical/x-cactvs-table'
Unknown media type in type 'chemical/x-cdx'
Unknown media type in type 'chemical/x-cdxml'
Unknown media type in type 'chemical/x-chem3d'
Unknown media type in type 'chemical/x-cif'
Unknown media type in type 'chemical/x-cml'
Unknown media type in type 'chemical/x-daylight-smiles'
Unknown media type in type 'chemical/x-dmol'
Unknown media type in type 'chemical/x-gamess-input'
Unknown media type in type 'chemical/x-gamess-output'
Unknown media type in type 'chemical/x-gaussian-input'
Unknown media type in type 'chemical/x-gaussian-log'
Unknown media type in type 'chemical/x-genbank'
Unknown media type in type 'chemical/x-gulp'
Unknown media type in type 'chemical/x-hin'
Unknown media type in type 'chemical/x-inchi'
Unknown media type in type 'chemical/x-inchi-xml'
Unknown media type in type 'chemical/x-jcamp-dx'
Unknown media type in type 'chemical/x-macromodel-input'
Unknown media type in type 'chemical/x-mdl-molfile'
Unknown media type in type 'chemical/x-mdl-rdfile'
Unknown media type in type 'chemical/x-mdl-rxnfile'
Unknown media type in type 'chemical/x-mdl-sdfile'
Unknown media type
Bug#855186: installing xdotool circumvent the issue
in case someone on debian looks here first, installing xdotool circumvent the issue see https://sourceforge.net/p/keepass/bugs/1530/ that explains the workaround and my bug report upstream https://sourceforge.net/p/keepass/bugs/1608/ -- benoit barthelet http://pgp.mit.edu/pks/lookup?op=get=0xF150E01A72F6D2EE
Bug#855186: keepass2: ctrl+c ctrl+v doesn't work in openjdk8 apps
Package: keepass2 Version: 2.28+dfsg-1 Severity: important Dear Maintainer, Upgrading keepass2 to 2.35 leads to this issue, 2.28 doesnt have. When I'm in pycharm for instance with keepass 2.35 opened, I cant ctrl+c ctrl+v, nothing is pasted from clipboard. If I close pycharm the copy-paste works fine. I can only paste if I ctrl+c twice. If I use keepass2 2.28 there's no issue. It seems there is a conflict between mono and openjdk on clipboard handling, at least it has been reported here http://askubuntu.com/questions/873815/kubuntu-16-04-lts-and-phpstorm-2016-3-clipboard-issue-cannot-paste So there might be a regression between 2.28 and 2.35 -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (980, 'stable-updates'), (980, 'stable'), (90, 'experimental'), (90, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages keepass2 depends on: ii libmono-corlib4.5-cil4.6.2.7+dfsg-1 ii libmono-system-drawing4.0-cil4.6.2.7+dfsg-1 ii libmono-system-security4.0-cil 4.6.2.7+dfsg-1 ii libmono-system-windows-forms4.0-cil 4.6.2.7+dfsg-1 ii libmono-system-xml4.0-cil4.6.2.7+dfsg-1 ii libmono-system4.0-cil4.6.2.7+dfsg-1 ii libx11-6 2:1.6.4-3 ii mono-runtime 4.6.2.7+dfsg-1 Versions of packages keepass2 recommends: ii xsel 1.2.0-2 Versions of packages keepass2 suggests: pn keepass2-doc pn mono-dmcs pn xdotool -- no debconf information
Bug#852159: mktorrent: upstream changed maintainer, actual version missing new interesting features
Package: mktorrent Version: 1.0-4+b1 Severity: important hello, esmil transmitted the maintenance / development of mktorrent: see https://github.com/Rudde/mktorrent/pull/15 the pull in question adds the ability to put a source to infohash wich tends to become a 'standard' if debian package could change its source that would be awesome, is that possibke ? -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (980, 'stable-updates'), (980, 'stable'), (90, 'experimental'), (90, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mktorrent depends on: ii libc62.24-8 ii libssl1.0.2 1.0.2j-4 mktorrent recommends no packages. mktorrent suggests no packages. -- no debconf information
Bug#838330: upgrading python-libtorrent from 0.16.18-1 to 1.1.0-3 makes deluge daemon unusable
Package: python-libtorrent Version: 0.16.18-1 Severity: important keeping python-libtorrent at 0.16.18-1 solves the issue, upgrading to 1.1.0-3 and the deluge deamon hangs forever without any interesting debug log, deluge devs apparently won't support libtorrent 1.1.0 (http://forum.deluge- torrent.org/viewtopic.php?p=223925#p223925) apologies if this isn't the right place to report, but if upstream decided not to support 1.1.0 libtorrent, deluge users may have issues. looks like arch ran into similar issues (https://bugs.archlinux.org/task/49861) -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (980, 'stable-updates'), (980, 'stable'), (90, 'experimental'), (90, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-libtorrent depends on: ii dpkg 1.18.10 ii libboost-python1.55.0 1.55.0+dfsg-3 ii libboost-system1.55.0 1.55.0+dfsg-4 ii libc6 2.23-5 ii libgcc11:6.1.1-11 ii libstdc++6 6.1.1-11 ii libtorrent-rasterbar7 0.16.18-1 ii python 2.7.11-2 python-libtorrent recommends no packages. python-libtorrent suggests no packages. -- no debconf information
Bug#780290: e17: thumbnail images works fine, videos though only display grey default icon
Package: e17 Version: 0.17.6-1 Severity: normal in a folder with images Enlightenment File Manager displays images thumbnails. it should do the same with videos, however on my system I cant only see the grey default icon. I'd gladly post more information, logs, whatever is necessary but unfortunately my google skills failed short of finding the beginning of a solution, appart from this thread which was not that helpful except it implied somewhat it could be related to gstreamer : https://bbs.archlinux.org/viewtopic.php?id=158259 and this other one which implied the same : http://comments.gmane.org/gmane.comp.window-managers.enlightenment.user/19418 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (980, 'stable-updates'), (980, 'stable'), (90, 'experimental'), (90, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages e17 depends on: ii dbus-x11 1.8.12-3 ii e17-data 0.17.6-1 ii libasound2 1.0.28-1 ii libc6 2.19-13 ii libdbus-1-31.8.12-3 ii libecore-con1 1.8.6-2.1+b2 ii libecore-evas1 1.8.6-2.1+b2 ii libecore-file1 1.8.6-2.1+b2 ii libecore-imf1 1.8.6-2.1+b2 ii libecore-input11.8.6-2.1+b2 ii libecore-ipc1 1.8.6-2.1+b2 ii libecore-x11.8.6-2.1+b2 ii libecore1 1.8.6-2.1+b2 ii libedbus1 1.7.10-1 ii libedje-bin1.8.6-2.1+b2 ii libedje1 1.8.6-2.1+b2 ii libeet11.8.6-2.1+b2 ii libeeze1 1.8.6-2.1+b2 ii libefreet-bin 1.8.6-2.1+b2 ii libefreet1a1.8.6-2.1+b2 ii libeina1 1.8.6-2.1+b2 ii libeio11.8.6-2.1+b2 ii libevas1 1.8.6-2.1+b2 ii libevas1-engines-x [libevas1-engine-software-x11] 1.8.6-2.1+b2 ii libpam0g 1.1.8-3.1 ii libxcb-keysyms10.4.0-1 ii libxcb-shape0 1.10-3+b1 ii libxcb11.10-3+b1 Versions of packages e17 recommends: ii pm-utils 1.4.1-15 e17 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730174: libsqlite3-dev: Incorrect result on query involving LEFT JOIN and transitive constraints
Package: libsqlite3-dev Version: 3.8.1-1 Severity: normal Hello, please forgive me if not doing that appproprietly it's my 1st bug report. I compiled xbmc from git, have an issue described here http://trac.xbmc.org/ticket/14646 it seems the issue is caused by this sqlite version : http://www.sqlite.org/src/info/c620261b5b5dc and fixed by this : http://www.sqlite.org/src/info/9aac4e588c Could you please add it ? thanks -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (980, 'stable-updates'), (980, 'stable'), (90, 'experimental'), (90, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libsqlite3-dev depends on: ii libc6-dev 2.17-93 ii libsqlite3-0 3.8.1-1 libsqlite3-dev recommends no packages. Versions of packages libsqlite3-dev suggests: pn sqlite3-doc none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652298:
for me adding the -- $OPTIONS in the stop function like it's in the start function did the job. *** /etc/init.d/ddclient2012-06-19 18:04:38.0 +0200 --- /etc/init.d/ddclient.diff 2012-06-19 18:00:07.0 +0200 *** *** 77,83 # 2 if daemon could not be stopped # other if a failure occurred start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 \ ! --pidfile $PIDFILE --name $NAME return $? } --- 77,83 # 2 if daemon could not be stopped # other if a failure occurred start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 \ ! --pidfile $PIDFILE --name $NAME -- $OPTIONS return $? }
