Bug#879876: ipython fails after printing help on a variable definition
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
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 outcome of this action? In [1]: s = isinstance? Docstring: isinstance(object, class-or-type-or-tuple) -> bool Return whether an object is an instance of a class or of a subclass thereof. With a type as second argument, return whether that is the object's type. The form using a tuple, isinstance(x, (A, B, ...)), is a shortcut for isinstance(x, A) or isinstance(x, B) or ... (etc.). Type: builtin_function_or_method In [2]: s = isinstance? Traceback (most recent call last): File "", line 1, in File "/usr/lib/python2.7/dist-packages/traitlets/config/application.py", line 658, in launch_instance app.start() File "/usr/lib/python2.7/dist-packages/IPython/terminal/ipapp.py", line 348, in start self.shell.mainloop() File "/usr/lib/python2.7/dist-packages/IPython/terminal/interactiveshell.py", line 440, in mainloop self.interact() File "/usr/lib/python2.7/dist-packages/IPython/terminal/interactiveshell.py", line 423, in interact code = self.prompt_for_code() File "/usr/lib/python2.7/dist-packages/IPython/terminal/interactiveshell.py", line 333, in prompt_for_code pre_run=self.pre_prompt, reset_current_buffer=True) File "/usr/lib/python2.7/dist-packages/prompt_toolkit/interface.py", line 408, in run self._pre_run(pre_run) File "/usr/lib/python2.7/dist-packages/prompt_toolkit/interface.py", line 383, in _pre_run pre_run() File "/usr/lib/python2.7/dist-packages/IPython/terminal/interactiveshell.py", line 410, in pre_prompt self.pt_cli.application.buffer.text = cast_unicode_py2(self.rl_next_input) File "/usr/lib/python2.7/dist-packages/prompt_toolkit/buffer.py", line 372, in text assert self.cursor_position <= len(value) AssertionError If you suspect this is an IPython bug, please report it at: https://github.com/ipython/ipython/issues or send an email to the mailing list at ipython-...@scipy.org You can print a more detailed traceback right now with "%tb", or use "%debug" to interactively debug it. Extra-detailed tracebacks for bug-reporting purposes can be enabled via: %config Application.verbose_crash=True * What outcome did you expect instead? ipython prints help, removes "?" from the repl and works fine -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (500, 'testing-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-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 ipython depends on: ii python-ipython 5.1.0-3 ipython recommends no packages. ipython suggests no packages. -- no debconf information
Bug#853369: dbus-c++: ftbfs with GCC-7
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 logic error and gcc-7 just have shown that explicitly. R.H.
Bug#818269: nfs-common: Failed to get info from "systemctl is-enabled nfs-common"
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 nfs-common.service Failed to get unit file state for nfs-common.service: No such file or directory ecko@debian:~$ With other services, i.e. ssh, it's all right. *** 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)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: -- rpcinfo -- program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000241 udp 35634 status 1000241 tcp 33540 status -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS= NEED_IDMAPD= NEED_GSSD= -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /run/rpc_pipefs [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- -- System Information: Debian Release: 8.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nfs-common depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-59 ii libc6 2.19-18+deb8u3 ii libcap2 1:2.24-8 ii libcomerr2 1.42.12-1.1 ii libdevmapper1.02.1 2:1.02.90-2.2 ii libevent-2.0-5 2.0.21-stable-2 ii libgssapi-krb5-21.12.1+dfsg-19+deb8u2 ii libk5crypto31.12.1+dfsg-19+deb8u2 ii libkeyutils11.5.9-5+b1 ii libkrb5-3 1.12.1+dfsg-19+deb8u2 ii libmount1 2.25.2-6 ii libnfsidmap20.25-5 ii libtirpc1 0.2.5-1 ii libwrap07.6.q-25 ii lsb-base4.1+Debian13+nmu1 ii rpcbind 0.2.1-6+deb8u1 ii ucf 3.0030 Versions of packages nfs-common recommends: ii python 2.7.9-1 Versions of packages nfs-common suggests: pn open-iscsi pn watchdog -- no debconf information
Bug#813696: closed by Michael Biebl <bi...@debian.org> (Bug#813696: fixed in systemd 215-17+deb8u4)
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 an automatic notification regarding your Bug report which was filed against the systemd package: #813696: systemd-nspawn failed to move interface to namespace: File exists It has been closed by Michael Biebl. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Michael Biebl by replying to this email. -- Regards, R.H.
Bug#783711: #783711: redmine: Version number is misleading/wrong
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)
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 their attention; they will reply in due course. As you requested using X-Debbugs-CC, your message was also forwarded to mk.43.e...@gmail.com (after having been given a Bug report number, if it did not have one). Your message has been sent to the package maintainer(s): Debian GNOME MaintainersIf you wish to submit further information on this problem, please send it to 815...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- Regards, R.H.
Bug#813696: Acknowledgement (systemd-nspawn failed to move interface to namespace: File exists)
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 message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. As you requested using X-Debbugs-CC, your message was also forwarded to mk.43.e...@gmail.com (after having been given a Bug report number, if it did not have one). Your message has been sent to the package maintainer(s): Debian systemd MaintainersIf you wish to submit further information on this problem, please send it to 813...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- Regards, R.H.
Bug#815015: gnome-shell crashes after moving 2048-qt to other screen
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. When I repeated this steps, I got "Oh no, something gone wrong!" screen and logout. Here is a "coredumpctl dump" of gnome-shell process: ecko@megapeka:~$ coredumpctl dump 14706 PID: 14706 (gnome-shell) UID: 1000 (ecko) GID: 1000 (ecko) Signal: 5 (TRAP) Timestamp: Ср 2016-02-17 22:06:30 MSK (1min 50s ago) Command Line: /usr/bin/gnome-shell Executable: /usr/bin/gnome-shell Control Group: /user.slice/user-1000.slice/session-19.scope Unit: session-19.scope Slice: user-1000.slice Session: 19 Owner UID: 1000 (ecko) Boot ID: ee9b2006e4574c448aa599a4801ddee0 Machine ID: 50332dd2fce9449cb1add1571d159a99 Hostname: megapeka Coredump: /var/lib/systemd/coredump/core.gnome- shell.1000.ee9b2006e4574c448aa599a4801ddee0.14706.145573599000.xz Message: Process 14706 (gnome-shell) of user 1000 dumped core. Stack trace of thread 14706: #0 0x7fc2c004287b g_logv (libglib-2.0.so.0) #1 0x7fc2c00429ef g_log (libglib-2.0.so.0) #2 0x7fc2bccd2108 n/a (libgdk-3.so.0) #3 0x7fc2bccdd349 n/a (libgdk-3.so.0) #4 0x7fc2bcf9246d _XError (libX11.so.6) #5 0x7fc2bcf8f3a7 n/a (libX11.so.6) #6 0x7fc2bcf8f465 n/a (libX11.so.6) #7 0x7fc2bcf90420 _XReply (libX11.so.6) #8 0x7fc2bcf8bcad XSync (libX11.so.6) #9 0x7fc2c1a1a0df meta_prop_get_values (libmutter.so.0) #10 0x7fc2c1a133ae meta_window_reload_property_from_xwindow (libmutter.so.0) #11 0x7fc2c1a1790a process_property_notify (libmutter.so.0) #12 0x7fc2c1a0d14b handle_other_xevent (libmutter.so.0) #13 0x7fc2c1a0d79b meta_display_handle_xevent (libmutter.so.0) #14 0x7fc2bccd7cb1 n/a (libgdk-3.so.0) #15 0x7fc2bccd828f n/a (libgdk-3.so.0) #16 0x7fc2bccaa2a9 gdk_display_get_event (libgdk-3.so.0) #17 0x7fc2bccd7d32 n/a (libgdk-3.so.0) #18 0x7fc2c003bfd7 g_main_context_dispatch (libglib-2.0.so.0) #19 0x7fc2c003c230 n/a (libglib-2.0.so.0) #20 0x7fc2c003c552 g_main_loop_run (libglib-2.0.so.0) #21 0x7fc2c19eeafc meta_run (libmutter.so.0) #22 0x004021a7 main (gnome-shell) #23 0x7fc2bfa51870 __libc_start_main (libc.so.6) #24 0x004022d4 _start (gnome-shell) Stack trace of thread 14719: #0 0x7fc2bfb10b6d poll (libc.so.6) #1 0x7fc2c003c1cc n/a (libglib-2.0.so.0) #2 0x7fc2c003c552 g_main_loop_run (libglib-2.0.so.0) #3 0x7fc2c0841396 n/a (libgio-2.0.so.0) #4 0x7fc2c00629c5 n/a (libglib-2.0.so.0) #5 0x7fc2bfddc284 start_thread (libpthread.so.0) #6 0x7fc2bfb19a4d __clone (libc.so.6) Stack trace of thread 14712: #0 0x7fc2bfb10b6d poll (libc.so.6) #1 0x7fc2c003c1cc n/a (libglib-2.0.so.0) #2 0x7fc2c003c2dc g_main_context_iteration (libglib-2.0.so.0) #3 0x7fc2c003c319 n/a (libglib-2.0.so.0) #4 0x7fc2c00629c5 n/a (libglib-2.0.so.0) #5 0x7fc2bfddc284 start_thread (libpthread.so.0) #6 0x7fc2bfb19a4d __clone (libc.so.6) Stack trace of thread 14723: #0 0x7fc2bfb10b6d poll (libc.so.6) #1 0x7fc2bbeb5831 n/a (libpulse.so.0) #2 0x7fc2bbea6e51 pa_mainloop_poll (libpulse.so.0) #3 0x7fc2bbea74ee pa_mainloop_iterate (libpulse.so.0) #4 0x7fc2bbea75a0 pa_mainloop_run (libpulse.so.0) #5 0x7fc2bbeb57c6 n/a (libpulse.so.0) #6 0x7fc2b20cc038 n/a (libpulsecommon-7.1.so) #7 0x7fc2bfddc284 start_thread (libpthread.so.0) #8 0x7fc2bfb19a4d __clone (libc.so.6) Stack trace of thread 14724: #0 0x7fc2bfde18cf pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x7fc2b1641d10 PR_WaitCondVar (libnspr4.so) #2 0x7fc2bb899f0e n/a (libmozjs-24.so.0) #3 0x7fc2b1647678 n/a (libnspr4.so) #4 0x7fc2bfddc284 start_thread (libpthread.so.0) #5 0x7fc2bfb19a4d __clone
Bug#800091: netbeans: crashed after loading window
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 *** * What led up to the situation? 1. Install clean version of netbeans 2. Install scala plugin via Tools-Plugins 3. Try to create scala project * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? netbeans crashed * What outcome did you expect instead? Here is some additional info. Console output: ecko@megapeka:~$ netbeans Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on Gtk-Message: Failed to load module "canberra-gtk-module" Hi, what happens if you install libcanberra-gtk3-module? It's already installed, but any time I'm starting netbeans I am getting this error: Gtk-Message: Failed to load module "canberra-gtk-module" # A fatal error has been detected by the Java Runtime Environment: OpenJDK 7 is currently affected by https://bugs.debian.org/798214 Applications which use the GTK look theme can segfault due to the newly enabled atk bridge. What happens if you switch to another theme like Metal or Nimbus? Pardon my ignorance, but how can I do it? When using the GTK theme what happens if you comment out the line in /etc/java-7-openjdk/accessibility.properties The problem has gone after I commented the line, thanks! Thanks Markus
Bug#800091: netbeans: crashed after loading window
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 create scala project * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? netbeans crashed * What outcome did you expect instead? Here is some additional info. Console output: ecko@megapeka:~$ netbeans Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on Gtk-Message: Failed to load module "canberra-gtk-module" # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa4b7ff7823, pid=14878, tid=140343707911936 # # JRE version: OpenJDK Runtime Environment (7.0_85-b01) (build 1.7.0_85-b01) # Java VM: OpenJDK 64-Bit Server VM (24.85-b03 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea 2.6.1 # Distribution: Debian GNU/Linux buildd-unstable (sid), package 7u85-2.6.1-3 # Problematic frame: # V [libjvm.so+0x2f2823] BiasedLocking::revoke_and_rebias(Handle, bool, Thread*)+0x33 # # Core dump written. Default location: /home/ecko/core or core.14878 # # An error report file with more information is saved as: # /home/ecko/hs_err_pid14878.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # http://icedtea.classpath.org/bugzilla # /usr/share/netbeans/8.0.2/platform/lib/nbexec: line 474: 14878 Аварийный останов (core dumped) "/usr/lib/jvm/java-7 -openjdk-amd64/bin/java" -Djdk.home="/usr/lib/jvm/java-7-openjdk-amd64" -classpath "/usr/share/netbeans/8.0.2/platform/lib/boot.jar:/usr/share/netbeans/8.0.2/platform/lib /org-openide-modules.jar:/usr/share/netbeans/8.0.2/platform/lib/org-openide- util.jar:/usr/share/netbeans/8.0.2/platform/lib/org-openide-util- lookup.jar:/usr/lib/jvm/java-7-openjdk-amd64/lib/dt.jar:/usr/lib/jvm/java-7 -openjdk-amd64/lib/tools.jar" -Dnetbeans.default_userdir_root="/home/ecko/.netbeans" -Dnetbeans.running.environment=gnome -Dnetbeans.dirs="/usr/share/netbeans/8.0.2/nb:/usr/share/netbeans/8.0.2/ergonomics:/usr/share/netbeans/8.0.2/ide:/usr/share/netbeans/8.0.2/extide:/usr/share/netbeans/8.0.2/java:/usr/share/netbeans/8.0.2/apisupport:/usr/share/netbeans/8.0.2/webcommon:/usr/share/netbeans/8.0.2/websvccommon:/usr/share/netbeans/8.0.2/enterprise:/usr/share/netbeans/8.0.2/mobility:/usr/share/netbeans/8.0.2/profiler:/usr/share/netbeans/8.0.2/python:/usr/share/netbeans/8.0.2/php:/usr/share/netbeans/8.0.2/identity:/usr/share/netbeans/8.0.2/harness:/usr/share/netbeans/8.0.2/cnd:/usr/share/netbeans/8.0.2/dlight:/usr/share/netbeans/8.0.2/groovy:/usr/share/netbeans/8.0.2/extra:/usr/share/netbeans/8.0.2/javacard:/usr/share/netbeans/8.0.2/javafx:" -Dnetbeans.home="/usr/share/netbeans/8.0.2/platform" '-Dnetbeans.importclass=org.netbeans.upgrade.AutoUpgrade' '-Dnetbeans.accept_license_class=org.netbeans.license.AcceptLicense' '-Xmx1024m' '-client' '-Xss2m' '-Xms32m' '-XX:PermSize=32m' '-Dapple.laf.useScreenMenuBar=true' '-Dapple.awt.graphics.UseQuartz=true' '-Dsun.java2d.noddraw=true' '-Dsun.java2d.dpiaware=true' '-Dsun.zip.disableMemoryMapping=true' '-Dsun.java2d.pmoffscreen=false' '-XX:MaxPermSize=384m' -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath="/home/ecko/.netbeans/8.0.2/var/log/heapdump.hprof" org.netbeans.Main --cachedir "/home/ecko/.cache/netbeans/8.0.2" --userdir "/home/ecko/.netbeans/8.0.2" "--branding" "nb" 0<&0 *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages netbeans depends on: ii default-jdk2:1.7-52 ii libnb-apisupport3-java 8.0.2+dfsg1-4 ii libnb-ide14-java 8.0.2+dfsg1-4 ii libnb-java5-java 8.0.2+dfsg1-4 ii libnb-platform18-java 8.0.2+dfsg1-1 ii openjdk-7-jdk [java7-jdk] 7u85-2.6.1-3 netbeans recommends no packages. netbeans suggests no packages. -- no debconf information # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa4b7ff7823, pid=14878, tid=140343707911936 # # JRE version: OpenJDK Runtime Environment (7.0_85-b01) (build 1.7.0_85-b01) # Java VM: OpenJDK 64-Bit Server VM (24.85-b03 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea 2.6.1 # Distribution: Debian GNU/Linux buildd-unstable (sid), package 7u85-2.6.1-3 # Problematic frame: # V [libjvm.so+0x2f2823] BiasedLocking::revoke_and_rebias(Handle, bool, Thread*)+0x33 # # Core dump written. Default location: /home/ecko/core or core.14878 # # If
Bug#799785: systemsettings: crashes with SIGSEGV when exiting from "Screen" settings
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 systemsettings 2. Go to the "Screen" section 3. Go back * What was the outcome of this action? Program crashed with SIGSEGV. Here is the bt in gdb: #0 0x72bd3982 in QQuickItemPrivate::addToDirtyList() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #1 0x72bd3a23 in QQuickItemPrivate::dirty(QQuickItemPrivate::DirtyType) () from /usr/lib/x86_64 -linux-gnu/libQt5Quick.so.5 #2 0x72bde305 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x73f241c1 in QObject::event (this=0xe25d60, e=) at kernel/qobject.cpp:1245 #4 0x72bddadb in QQuickItem::event(QEvent*) () from /usr/lib/x86_64 -linux-gnu/libQt5Quick.so.5 #5 0x753d4b8c in QApplicationPrivate::notify_helper (this=this@entry=0x68dac0, receiver=receiver@entry=0xe25d60, e=e@entry=0x7fffc413f790) at kernel/qapplication.cpp:3720 #6 0x753da230 in QApplication::notify (this=0x7fffd970, receiver=0xe25d60, e=0x7fffc413f790) at kernel/qapplication.cpp:3503 #7 0x73ef2a8b in QCoreApplication::notifyInternal (this=0x7fffd970, receiver=0xe25d60, event=event@entry=0x7fffc413f790) at kernel/qcoreapplication.cpp:935 #8 0x73ef4bc7 in QCoreApplication::sendEvent (event=0x7fffc413f790, receiver=) at .../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:228 #9 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x68d0d0) at kernel/qcoreapplication.cpp:1552 #10 0x73ef50f8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1410 #11 0x73f49a23 in postEventSourceDispatch (s=0x6d9710) at kernel/qeventdispatcher_glib.cpp:271 #12 0x707a2c3d in g_main_context_dispatch () from /lib/x86_64-linux- gnu/libglib-2.0.so.0 #13 0x707a2f20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x707a2fcc in g_main_context_iteration () from /lib/x86_64-linux- gnu/libglib-2.0.so.0 #15 0x73f49e2f in QEventDispatcherGlib::processEvents (this=0x6d96f0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #16 0x73ef02ca in QEventLoop::exec (this=this@entry=0x7fffd8e0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #17 0x73ef7e3c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1188 #18 0x0042501b in main () * What outcome did you expect instead? Program did not crashed with SIGSEGV and I was very-very happy *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemsettings depends on: ii libc6 2.19-20 ii libkf5auth5 5.14.0-1 ii libkf5completion5 5.14.0-1 ii libkf5configcore5 5.14.0-1 ii libkf5configgui5 5.14.0-1 ii libkf5configwidgets5 5.14.0-1 ii libkf5coreaddons5 5.14.0-1 ii libkf5dbusaddons5 5.14.0-1 ii libkf5i18n5 5.14.0-1 ii libkf5iconthemes5 5.14.0-1 ii libkf5itemviews5 5.14.0-1 ii libkf5kcmutils5 5.14.0-1 ii libkf5khtml5 5.13.0-3 ii libkf5kiowidgets5 5.13.0-1 ii libkf5service55.14.0-1 ii libkf5widgetsaddons5 5.14.0-1 ii libkf5windowsystem5 5.14.0-1 ii libkf5xmlgui5 5.14.0-1 ii libqt5core5a 5.4.2+dfsg-9 ii libqt5dbus5 5.4.2+dfsg-9 ii libqt5gui55.4.2+dfsg-9 ii libqt5widgets55.4.2+dfsg-9 ii libstdc++65.2.1-17 systemsettings recommends no packages. systemsettings suggests no packages. -- no debconf information
Bug#766537: [libmtp9] Unable to open ~/.mtpz-data for reading
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 (VID=0bb4 and PID=2008) is UNKNOWN. is really important. Can you say, what device it is? I will create the bug in the upstream if libmtp does not support it yet. -- Regards, R.H.