Bug#879876: ipython fails after printing help on a variable definition

2017-10-31 Thread Reverend Homer
I've got zero feedback, but with latest ipython upgrade (5.5.0-1) problem has gone. Thank you, this bug can be closed now.

Bug#879876: ipython fails after printing help on a variable definition

2017-10-26 Thread Reverend Homer
Package: ipython Version: 5.1.0-3 Severity: normal Dear Maintainer, * What led up to the situation? Nothing unusual, just "apt install python-ipython ipython" * What exactly did you do (or not do) that was effective (or ineffective)? In [1]: s = isinstance? * What was the

Bug#853369: dbus-c++: ftbfs with GCC-7

2017-08-17 Thread Reverend Homer
Hi, I've faced with exact the same issue building buildroot on my fedora with gcc-7. I'm pretty sure that replacing ::write(_fd_write, '\0', 1); with char nullch = '\0'; ::write(_fd_write, , 1); should do the trick. Moreover, I think that original line was

Bug#818269: nfs-common: Failed to get info from "systemctl is-enabled nfs-common"

2016-03-15 Thread Reverend Homer
Package: nfs-common Version: 1:1.2.8-9 Severity: normal Dear Maintainer, I am using clean Debian Jessie + LXDE install. After installing nfs-common package, when I typing "systemctl is-enabled nfs-common.service" (from user or from root), I get ecko@debian:~$ systemctl is-enabled

Bug#813696: closed by Michael Biebl <bi...@debian.org> (Bug#813696: fixed in systemd 215-17+deb8u4)

2016-03-14 Thread Reverend Homer
Hi, thanks for your job! I've just created a virtual machine with Debian stable (8.3), and looks like problem is still reproducible :( Version of systemd: 215-17+deb8u3. Is my version correct? Or I should use exactly 215-17+deb8*u4*? 14.03.2016 0:39, Debian Bug Tracking System пишет: This is

Bug#783711: #783711: redmine: Version number is misleading/wrong

2016-02-24 Thread Reverend Homer
Hi, any progress with that? Looks like the version is still wrong. -- Regards, R.H.

Bug#815015: Acknowledgement (gnome-shell crashes after moving 2048-qt to other screen)

2016-02-24 Thread Reverend Homer
ping? 17.02.2016 22:18, Debian Bug Tracking System пишет: Thank you for filing a new Bug report with Debian. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for

Bug#813696: Acknowledgement (systemd-nspawn failed to move interface to namespace: File exists)

2016-02-24 Thread Reverend Homer
ping? Can anyone tell me sth about that? I'm copying this mail to Michael Biebl too. Looking forward to read his comment. 04.02.2016 15:39, Debian Bug Tracking System пишет: Thank you for filing a new Bug report with Debian. This is an automatically generated reply to let you know your

Bug#815015: gnome-shell crashes after moving 2048-qt to other screen

2016-02-17 Thread Reverend Homer
Package: gnome-shell Version: 3.18.1-1 Severity: normal Dear Maintainer, I am using gnome-shell with two screen configuration. So I installed 2048-qt, run it and wanted to move this window to my second screen. After that all gui froze for a couple of seconds and 2048-qt came to first screen.

Bug#800091: netbeans: crashed after loading window

2015-09-29 Thread Reverend Homer
Hi Markus, thanks for support! 27.09.2015 07:24, Markus Koschany пишет: Am 26.09.2015 um 19:58 schrieb Reverend Homer: Package: netbeans Version: 8.0.2+dfsg1-4 Severity: normal Tags: upstream Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate

Bug#800091: netbeans: crashed after loading window

2015-09-26 Thread Reverend Homer
Package: netbeans Version: 8.0.2+dfsg1-4 Severity: normal Tags: upstream Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? 1. Install clean version of netbeans 2. Install scala plugin via Tools-Plugins 3. Try to

Bug#799785: systemsettings: crashes with SIGSEGV when exiting from "Screen" settings

2015-09-22 Thread Reverend Homer
Package: systemsettings Version: 4:5.4.1-1 Severity: normal Tags: upstream Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? 1. Run

Bug#766537: [libmtp9] Unable to open ~/.mtpz-data for reading

2015-09-10 Thread Reverend Homer
Hi Andreas, >Unable to open ~/.mtpz-data for reading, MTPZ disabled. This text does not contain any important information and does not affect at work of libmtp. Actually, I think that git version does not consist this error message at any initialization of libmtp. But this >Device 0