[Bug 238278] hexchat
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Jun 1 12:39:04 UTC 2019
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238278
Bug ID: 238278
Summary: hexchat
Product: Ports & Packages
Version: Latest
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: ports-bugs at FreeBSD.org
Reporter: timido at ubuntu.com
(gdb) run
Starting program: /usr/local/bin/hexchat
(hexchat:27893): Gtk-WARNING **: 08:16:14.491: Unable to locate theme engine in
module_path: "mist",
(hexchat:27893): Gtk-WARNING **: 08:16:14.492: Unable to locate theme engine in
module_path: "mist",
[New LWP 100859 of process 27893]
[New LWP 100874 of process 27893]
warning: File "/usr/local/lib/libpython3.6m.so.1.0-gdb.py" auto-loading has
been
declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
To enable execution of this file add
add-auto-load-safe-path /usr/local/lib/libpython3.6m.so.1.0-gdb.py
line to your configuration file "/home/Aaron/.gdbinit".
To completely disable this security protection add
set auto-load safe-path /
line to your configuration file "/home/Aaron/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
info "(gdb)Auto-loading safe path"
[Detaching after fork from child process 27894]
[Detaching after fork from child process 27897]
(hexchat:27893): GVFS-RemoteVolumeMonitor-WARNING **: 08:19:18.884: remote
volume monitor with dbus name org.gtk.vfs.HalVolumeMonitor is not supported
(hexchat:27893): GVFS-RemoteVolumeMonitor-WARNING **: 08:19:18.898: remote
volume monitor with dbus name org.gtk.vfs.GPhoto2VolumeMonitor is not supported
[New LWP 100443 of process 27893]
[New LWP 100444 of process 27893]
[LWP 100443 of process 27893 exited]
[LWP 100444 of process 27893 exited]
(hexchat:27893): GVFS-RemoteVolumeMonitor-WARNING **: 08:31:06.606: remote
volume
line to your configuration file "/home/Aaron/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
info "(gdb)Auto-loading safe path"
[Detaching after fork from child process 27894]
[Detaching after fork from child process 27897]
(hexchat:27893): GVFS-RemoteVolumeMonitor-WARNING **: 08:19:18.884: remote
volume monitor with dbus name org.gtk.vfs.HalVolumeMonitor is not supported
(hexchat:27893): GVFS-RemoteVolumeMonitor-WARNING **: 08:19:18.898: remote
volume monitor with dbus name org.gtk.vfs.GPhoto2VolumeMonitor is not supported
[New LWP 100443 of process 27893]
[New LWP 100444 of process 27893]
[LWP 100443 of process 27893 exited]
[LWP 100444 of process 27893 exited]
(hexchat:27893): GVFS-RemoteVolumeMonitor-WARNING **: 08:31:06.606: remote
volume monitor with dbus name org.gtk.vfs.GPhoto2VolumeMonitor is not supported
[New LWP 100235 of process 27893]
[New LWP 100246 of process 27893]
[New LWP 100252 of process 27893]
[LWP 100235 of process 27893 exited]
[LWP 100246 of process 27893 exited]
[LWP 100252 of process 27893 exited]
Thread 1 received signal SIGKILL, Killed.
_umtx_op_err () at /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:37
37 RSYSCALL_ERR(_umtx_op)
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list