Bug#1079663: mypaint segfaults on aarch64
Package: mypaint
Version: 2.0.1-10+b2
Severity: important
Dear Maintainer,
mypaint does not seem to work on (at least some) aarch64/arm64 systems. It
segfaults in PyObject after attempting to paint a stroke (i.e. just clicking in
the default canvas after startup crashes the program). My platform is MNT
Reform with Rockchip RK3588, but it was also reported crashing on NXP
i.MX8MPlus.
Here is a gdb full backtrace:
(gdb) bt full
#0 0x004ff798 in _PyInterpreterState_GET () at
../Include/internal/pycore_pystate.h:133
tstate =
interp =
state =
ptr =
#1 get_state () at ../Objects/obmalloc.c:866
interp =
state =
ptr =
#2 _PyObject_Malloc (nbytes=56, ctx=0x0) at ../Objects/obmalloc.c:1563
state =
ptr =
#3 PyObject_Malloc (size=56) at ../Objects/obmalloc.c:801
#4 0x00520c08 in PyUnicode_New (maxchar=127, size=15) at
../Objects/unicodeobject.c:1251
obj =
unicode =
data =
kind = 1
is_ascii = 1
struct_size = 40
char_size = 1
starts = 0xf50b98c8 "_get_tile_numpy"
end = 0xf50b98d7 ""
u =
writer = {buffer = 0x0, data = 0x0, kind = 0, maxchar = 0, size =
281473890436336, pos = 5232112, min_length = 281473890436960, min_char = 0,
overallocate = 0 '\000', readonly = 0 '\000'}
startinpos = 0
endinpos = 0
errmsg =
error_handler_obj = 0x0
exc = 0x0
#5 unicode_decode_utf8 (s=, size=15,
error_handler=error_handler@entry=_Py_ERROR_UNKNOWN, errors=errors@entry=0x0,
consumed=consumed@entry=0x0)
at ../Objects/unicodeobject.c:4693
starts = 0xf50b98c8 "_get_tile_numpy"
end = 0xf50b98d7 ""
u =
writer = {buffer = 0x0, data = 0x0, kind = 0, maxchar = 0, size =
281473890436336, pos = 5232112, min_length = 281473890436960, min_char = 0,
overalloca--Type for more, q to quit, c to continue without paging--
te = 0 '\000', readonly = 0 '\000'}
startinpos = 0
endinpos = 0
errmsg =
error_handler_obj = 0x0
exc = 0x0
#6 0x00520b9c in PyUnicode_DecodeUTF8Stateful (consumed=0x0,
errors=0x0, size=, s=) at
../Objects/unicodeobject.c:4826
size =
#7 0x004fd5f0 in PyObject_GetAttrString (v=0xdfb1b500,
name=) at ../Objects/object.c:918
w =
res =
#8 0x004bfe18 in _PyObject_CallMethod_SizeT (obj=,
name=, format=0xf50b98c0 "(iii)") at ../Objects/call.c:755
tstate = 0x0
callable =
va = {__stack = 0x0, __gr_top = 0xbf40c5e0, __vr_top =
0xf7d20558 , __gr_offs = -136118000, __vr_offs = 65535}
retval =
#9 0xf5072b00 in tile_request_start(MyPaintTiledSurface2*,
MyPaintTileRequest*) (tiled_surface=0x19dfbc0, request=0xbf40c760)
at lib/pythontiledsurface.cpp:41
self = 0x19dfbc0
readonly = 0
tx = 1
ty = 5
rgba = 0x0
#10 0xf501f028 in process_tile_internal
(tiled_surface=tiled_surface@entry=0x19dfbc0, request_start=0xf501e640
, request_end=0xf501e650 ,
op_queue=0x19dfc90, tx=1, ty=5) at mypaint-tiled-surface.c:512
tile_index = {x = 1, y = 5}
op = 0x2ca05e0
request_data = {tx = 1, ty = 5, readonly = 0, buffer = 0x0, context =
0x0, thread_id = 3, mipmap_level = 0}
mipmap_level = 0
rgba_p =
mask = {0 , 59584, 48960, 65535, 0}
#11 0xf5020780 in tiled_surface2_process_tile
(self=self@entry=0x19dfbc0, tx=, ty=) at
mypaint-tiled-surface.c:892
#12 0xf5020808 in mypaint_tiled_surface2_end_atomic._omp_fn.0 () at
mypaint-tiled-surface.c:1156
self =
tiles = 0x19e0970
tiles_n =
--Type for more, q to quit, c to continue without paging--
tiles = 0xf4f3ed8c
tiles_n =
#13 0xf4f3ed8c in gomp_thread_start (xdata=) at
../../../src/libgomp/team.c:129
team = 0x22ee340
task = 0x22eeb20
data =
local_fn = 0xf5020780
local_data =
#14 0xf7d12fbc in start_thread (arg=0xf7ff5e40) at
./nptl/pthread_create.c:444
ret =
pd = 0xf7ff5e40
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {281473890447744,
281473890447744, 48, 281474842451520, 281474839424256, 11, 281473881997312,
281473890447744, 281473881997312, 0, 281473890445840, 10575254300997217827, 0,
10575254302212598063, 0, 0, 0, 0, 0, 0, 0, 0}, mask_was_saved = 0}}, priv =
{pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype =
0}}}
not_first_call = 0
#15 0xf7d7e5cc in thread_start () at
../sysdeps/unix/sysv/linux/aarch64/clone3.S:76
(gdb)
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: arm64 (aarch64)
Foreign Architectures: i386, armhf, amd64
Kernel: Linux 6.9.7-mnt-reform-arm64 (SMP w/8 CPU thread
Bug#1079292: libgtk-3-0t64: segfault in gdk_window_get_toplevel() crashes waybar when clicking any tray icon
Package: libgtk-3-0t64 Version: 3.24.43-2 Severity: important X-Debbugs-Cc: lu...@mntre.com Dear Maintainer, Some of our MNT Reform aarch64 users (which runs unstable by default), and I, also on my amd64 PC, upgraded the libgtk-3-0t64 today. This renders tray icon functionality in waybar, a popular wayland task bar, unusable. Clicking any tray icon makes waybar crash and exit. Running waybar under gdb reveals a segfault in libgtk-3's gdk_window_get_toplevel(): Thread 1 "waybar" received signal SIGSEGV, Segmentation fault. 0x76d40485 in gdk_window_get_toplevel (window=0xa0080) at ../../../gdk/gdkwindow.c:2488 Download failed: Invalid argument. Continuing without source file ./debian/build/deb/../../../gdk/gdkwindow.c. 2488../../../gdk/gdkwindow.c: No such file or directory. (gdb) bt #0 0x76d40485 in gdk_window_get_toplevel (window=0xa0080) at ../../../gdk/gdkwindow.c:2488 #1 0x7651a8a5 in () at /lib/x86_64-linux-gnu/libgtk-layer-shell.so.0 #2 0x77115002 in gtk_tooltip_position (tooltip=0x55dbc1c0, display=0x0, new_tooltip_widget=, device=0x55907630) at ../../../gtk/gtktooltip.c:975 #3 gtk_tooltip_show_tooltip (display=display@entry=0x558c1b20) at ../../../gtk/gtktooltip.c:1051 #4 0x771151cf in tooltip_popup_timeout (data=0x558c1b20) at ../../../gtk/gtktooltip.c:1129 #5 0x76d259db in gdk_threads_dispatch (data=0x55dbe050) at ../../../gdk/gdk.c:769 #6 0x768f0bbe in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x768ede1f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x768efea7 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x768f04c0 in g_main_context_iteration () at /lib/x86_64-linux- gnu/libglib-2.0.so.0 #10 0x76be748d in g_application_run () at /lib/x86_64-linux- gnu/libgio-2.0.so.0 #11 0x555b6660 in waybar::Client::main(int, char**) () #12 0x555b4d05 in main () This problem was not present with the previous version of libgtk-3-0t64. Best, Lukas (minute) -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 6.9.9-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libgtk-3-0t64 depends on: ii adwaita-icon-theme 43-1 ii hicolor-icon-theme 0.17-2 ii libatk-bridge2.0-0t64 2.51.90-4 ii libatk1.0-0t64 2.51.90-4 ii libc6 2.38-11 ii libcairo-gobject2 1.18.0-3+b1 ii libcairo2 1.18.0-3+b1 ii libcloudproviders0 0.3.6-1 ii libcolord2 1.4.6-2.2 ii libcups2t642.4.7-1.2+b1 ii libepoxy0 1.5.10-1 ii libfontconfig1 2.14.1-4 ii libfribidi01.0.13-3 ii libgdk-pixbuf-2.0-02.42.10+dfsg-3+b3 ii libglib2.0-0t642.80.2-1 ii libgtk-3-common3.24.43-2 ii libharfbuzz0b 8.3.0-2 ii libpango-1.0-0 1.52.2+ds-1 ii libpangocairo-1.0-01.52.2+ds-1 ii libpangoft2-1.0-0 1.52.2+ds-1 ii libwayland-client0 1.22.0-2.1 ii libwayland-cursor0 1.22.0-2.1 ii libwayland-egl11.22.0-2.1 ii libx11-6 2:1.8.7-1 ii libxcomposite1 1:0.4.5-1 ii libxcursor11:1.2.1-1 ii libxdamage11:1.1.6-1+b1 ii libxext6 2:1.3.4-1+b1 ii libxfixes3 1:6.0.0-2 ii libxi6 2:1.8-1+b1 ii libxinerama1 2:1.1.4-3 ii libxkbcommon0 1.6.0-1+b1 ii libxrandr2 2:1.5.2-2+b1 ii shared-mime-info 2.2-1 Versions of packages libgtk-3-0t64 recommends: ii libgtk-3-bin 3.24.43-2 ii librsvg2-common 2.58.0+dfsg-1 Versions of packages libgtk-3-0t64 suggests: ii gvfs 1.54.0-4 Versions of packages libgtk-3-0t64 is related to: pn appmenu-gtk3-module pn fcitx-frontend-gtk3 pn gcin-gtk3-immodule pn gtk-vector-screenshot pn gtk3-engines-xfce pn gtk3-im-libthai pn hime-gtk3-immodule ii ibus-gtk3 1.5.29-1 pn imhangul-gtk3 ii libcanberra-gtk3-module 0.30-10 pn libcaribou-gtk3-module pn libgtk3-nocsd0 pn maliit-inputcontext-gtk3 pn packagekit-gtk3-module pn scim-gtk-immodule pn topmenu-gtk3 pn uim-gtk3 pn uim-gtk3-immodule -- no debconf information
Bug#1050587: linux: cpufreq-dt requires manually loading cpufreq-dt-platdev (6.5 regression)
I encountered the same issue on MNT Reform with Banana Pi CM4 module (Amlogic A311D / meson g12b). The processor operates at lowest speed and toolig can't display CPU freqs, until the cpufreq-dt-platdev module is loaded manually.
Bug#1022232: libffi8 3.4.3-3 breaks all wayland clients on arm64/aarch64
I have identified the breaking patch, it is: https://github.com/libffi/libffi/pull/739/files Reverting debian/patches/739.diff and rebuilding the library fixes the issue. If possible, please drop this patch until the issue is addressed by upstream.
Bug#1022232: libffi8 3.4.3-3 breaks all wayland clients on arm64/aarch64
I've tried all recent versions from snapshots. libffi8_3.4.3-2_arm64.deb still works, while libffi8_3.4.3-3_arm64.deb breaks.
Bug#1022232: libffi8 3.4.3-3 breaks all wayland clients on arm64/aarch64
Package: libffi8 Version: 3.4.3-3 Severity: important Dear Maintainer, Since an `apt upgrade` yesterday on Debian unstable on an aarch64 system (imx8mq based, cortex-a53), all wayland compositors and clients stopped working, including sway, wayfire and weston. I narrowed it down to garbage data in the wayland client/server communication (or a data alignment issue). The most common failure was clients reporting "wl_shm@4: error 1: invalid size (0)" after the first wl_commit. `weston-info` shows bizarre data like negative screen sizes. Copying in libffi.so.8.1.0 (instead of libffi.so.8.1.1) from a rescue system made everything work again, and copying libffi.so.8.1.1 to the good system made things break there. Thanks, Lukas F. Hartmann -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: arm64 (aarch64) Foreign Architectures: i386, armhf, amd64 Kernel: Linux 5.19.0-reform2-arm64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libffi8 depends on: ii libc6 2.35-3 libffi8 recommends no packages. libffi8 suggests no packages. -- no debconf information
Bug#963148: binutils-avr: avr-ld is broken on aarch64
Package: binutils-avr Version: 2.26.20160125+Atmel3.6.2-1 Severity: important Dear Maintainer, If I enter the following: avr-ld I get: Illegal instruction So I can't link avr programs on my aarch64 platform with Debian. If I build binutils-avr myself from the original sources, it works. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 5.7.0-rc6+ (SMP w/4 CPU cores; PREEMPT) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages binutils-avr depends on: ii libc6 2.30-8 ii zlib1g 1:1.2.11.dfsg-2 binutils-avr recommends no packages. Versions of packages binutils-avr suggests: ii binutils 2.34-8
Bug#953542: Cross-Check with arch linux version
So I downloaded a similar build, 73.0-1 for Arch Linux arm64 and replaced /usr/lib/firefox on my Debian sid installation with the respective contents of that build. And it works. So my guess is that it's something with the Debian build. The build I tried is "firefox-73.0-1-aarch64.pkg.tar.xz" from http://tardis.tiny-vps.com/aarm/packages/f/firefox/
Bug#953542: Workaround
The name argument to BuildSymbolName in the trace (stack position 2) contains: "inlineStorageLatin1 = "copyfile\000\000\000\000\000\000\000" I grepped for copyfile in /usr/lib/firefox and got a hit in omni.ja. omni.ja is a zipfile, extracting it yields a FFI definition of "copyfile" in modules/osfile/osfile_unix_back.jsm. Commenting out this block and re-zipping omni.ja allows me to launch firefox without segfaulting: /*libc.declareLazyFFI( SysFile, "copyfile", "copyfile", ctypes.default_abi, /* return*/ Type.negativeone_or_nothing, /* source*/ Type.path, Type.path, Type.void_t.in_ptr, Type.uint32_t );*/
Bug#953542: Backtrace
I downgraded to 73.0.1-1 via snapshot and installed the fitting dbgsym package. This way, I retrieved the following backtrace which shows that the crash seems to be related to the JS engine: Thread 21 "DOM Worker" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f662ff1a0 (LWP 3628)] JS_GetClass (obj=obj@entry=0x7f) at ./js/src/jsapi.cpp:1600 1600./js/src/jsapi.cpp: No such file or directory. (gdb) (gdb) bt #0 0x007ff22cad08 in JS_GetClass(JSObject*) (obj=obj@entry=0x7f) at ./js/src/jsapi.cpp:1600 #1 0x007ff223ba98 in js::ctypes::GetABICode (obj=0x7f) at ./js/src/ctypes/CTypes.cpp:843 #2 0x007ff223ba98 in js::ctypes::FunctionType::BuildSymbolName(JSContext*, JSString*, JSObject*, js::ctypes::StringBuilder&) (cx=0x7f66df, name=0x7f65f71740, typeObj=, result=...) at ./js/src/ctypes/CTypes.cpp:6634 #3 0x007ff22458bc in js::ctypes::Library::Declare(JSContext*, unsigned int, JS::Value*) (cx=0x7f66df, argc=, vp=) at ./js/src/ctypes/Library.cpp:353 #4 0x007ff2263d74 in CallJSNative(JSContext*, bool (*)(JSContext*, unsigned int, JS::Value*), js::CallReason, JS::CallArgs const&) (args=..., reason=(unknown: -191729664), native=0x7ff22456d0 , cx=0x7f66df) at ./build-browser/dist/include/js/CallArgs.h:284 #5 0x007ff2263d74 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct, js::CallReason) (cx=cx@entry=0x7f66df, args=..., construct=construct@entry=js::NO_CONSTRUCT, reason=reason@entry=js::CallReason::Call) at ./js/src/vm/Interpreter.cpp:544 #6 0x007ff2264de0 in InternalCall (reason=js::CallReason::Call, args=..., cx=0x7f66df) at ./js/src/vm/Interpreter.cpp:608 #7 0x007ff2264de0 in js::Call(JSContext*, JS::Handle, JS::Handle, js::AnyInvokeArgs const&, JS::MutableHandle, js::CallReason) (cx=cx@entry=0x7f66df, fval=..., fval@entry=..., thisv=..., args=..., rval=..., reason=reason@entry=js::CallReason::Call) at ./js/src/vm/Interpreter.cpp:625 #8 0x007ff23f9894 in js::fun_apply(JSContext*, unsigned int, JS::Value*) (cx=0x7f66df, argc=, vp=0x7f664fe4b8) at ./build-browser/dist/include/js/RootingAPI.h:675 #9 0x007ff2263d74 in CallJSNative(JSContext*, bool (*)(JSContext*, unsigned int, JS::Value*), js::CallReason, JS::CallArgs const&) (args=..., reason=, native=0x7ff23f95b0 , cx=0x7f66df) at ./build-browser/dist/include/js/CallArgs.h:284 #10 0x007ff2263d74 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct, js::CallReason) (cx=0x7f66df, args=..., construct=js::NO_CONSTRUCT, reason=) at ./js/src/vm/Interpreter.cpp:544 #11 0x007ff2258774 in InternalCall (reason=, args=..., cx=) at ./js/src/vm/Interpreter.cpp:608 #12 0x007ff2258774 in js::CallFromStack(JSContext*, JS::CallArgs const&) (args=..., cx=) at ./js/src/vm/Interpreter.cpp:612 #13 0x007ff2258774 in Interpret(JSContext*, js::RunState&) (cx=0x7f66df, state=...) at ./js/src/vm/Interpreter.cpp:3039 #14 0x007ff22638e0 in js::RunScript(JSContext*, js::RunState&) (cx=cx@entry=0x7f66df, state=...) at ./js/src/vm/Interpreter.cpp:424 #15 0x007ff2263eb0 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct, js::CallReason) (cx=cx@entry=0x7f66df, args=..., construct=construct@entry=js::NO_CONSTRUCT, reason=reason@entry=js::CallReason::Call) at ./js/src/vm/Interpreter.cpp:580 #16 0x007ff2264de0 in InternalCall (reason=js::CallReason::Call, args=..., cx=0x7f66df) at ./js/src/vm/Interpreter.cpp:608 #17 0x007ff2264de0 in js::Call(JSContext*, JS::Handle, JS::Handle, js::AnyInvokeArgs const&, JS::MutableHandle, js::CallReason) (cx=0x7f66df, fval=..., thisv=..., args=..., rval=..., reason=js::CallReason::Call) at ./js/src/vm/Interpreter.cpp:625 #18 0x007ff2265688 in js::SpreadCallOperation(JSContext*, JS::Handle, unsigned char*, JS::Handle, JS::Handle, JS::Handle, JS::Handle, JS::MutableHandle) (cx=0x7f66df, script=..., pc=0x7f664926a1 "y\263\001", thisv=..., callee=..., arr=..., newTarget=..., res=...) at ./js/src/vm/Interpreter.cpp:5048 #19 0x007ff22578ac in Interpret(JSContext*, js::RunState&) (cx=0x7f66df, state=...) at ./build-browser/dist/include/js/RootingAPI.h:1172 #20 0x007ff22638e0 in js::RunScript(JSContext*, js::RunState&) (cx=cx@entry=0x7f66df, state=...) at ./js/src/vm/Interpreter.cpp:424 #21 0x007ff2263eb0 in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct, js::CallReason) (cx=cx@entry=0x7f66df, args=..., construct=construct@entry=js::NO_CONSTRUCT, reason=reason@entry=js::CallReason::Getter) at ./js/src/vm/Interpreter.cpp:580 #22 0x007ff22649f8 in InternalCall (reason=js::CallReason::Getter, args=..., cx=0x7f66df) at ./js/src/vm/Interpreter.cpp:608 #23 0x007ff22649f8 in js::Call(JSContext*, JS::Handle, JS::Handle, js::AnyInvoke
Bug#953542: firefox 73.0.1 segfaults on startup on arm64 (wayland and X)
Package: firefox Version: 73.0.1-1+b1 Severity: important Dear Maintainer, I just upgraded the firefox package to 73.0.1 from 72, which worked fine, including hardware accelerated compositing and WebGL. Now, trying to launch firefox results in an immediate segfault. reportbug recommends to install firefox-dbgsym to get a full trace, but this package is not available for arm64. The computer is MNT Reform 2, which is based on NXP i.MX8M (Cortex-A53 and Vivante GC7000, using etnaviv drivers and mesa), and 4GB of LPDDR4. The desktop environment is the sway compositor (wayland, based on wlroots). With Firefox 72, I used MOZ_ENABLE_WAYLAND=1. Unsetting this variable has no effect on the crash. Running Firefox 73 in Xwayland results in the same segfault, so it doesn't appear to be a wayland problem. Removing ~/.mozilla does not influence the problem, either. Running firefox from gdb reveals: Thread 34 "DOM Worker" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f674be1a0 (LWP 3246)] 0x007ff2acbd08 in ?? () from /usr/lib/firefox/libxul.so Relevant GL info: Extended renderer info (GLX_MESA_query_renderer): Vendor: etnaviv (0x) Device: Vivante GC7000 rev 6214 (0x) Version: 20.1.0 Accelerated: yes Video memory: 0MB Unified memory: yes Preferred profile: compat (0x2) Max core profile version: 0.0 Max compat profile version: 2.1 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 2.0 OpenGL vendor string: etnaviv OpenGL renderer string: Vivante GC7000 rev 6214 OpenGL version string: 2.1 Mesa 20.1.0-devel (git-06dc280a57) OpenGL shading language version string: 1.20 Best Regards, Lukas F. Hartmann -- Package-specific info: -- Addons package information -- System Information: Debian Release: 10.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: arm64 (aarch64) Kernel: Linux 5.4.0-rc6-next-20191108+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages firefox depends on: ii debianutils 4.8.6.1 ii fontconfig2.13.1-2 ii libatk1.0-0 2.34.1-1 ii libc6 2.29-6 ii libcairo-gobject2 1.16.0-4 ii libcairo2 1.16.0-4 ii libdbus-1-3 1.12.16-1 ii libdbus-glib-1-2 0.110-4 ii libevent-2.1-72.1.11-stable-1 ii libffi7 3.3-3 ii libfontconfig12.13.1-2+b1 ii libfreetype6 2.10.1-2 ii libgcc-s1 10-20200211-1 ii libgdk-pixbuf2.0-02.40.0+dfsg-1 ii libglib2.0-0 2.62.1-1 ii libgtk-3-03.24.12-1 ii libnspr4 2:4.24-1 ii libnss3 2:3.50-1 ii libpango-1.0-01.42.4-7 ii libsqlite3-0 3.30.1+fossil191229-1 ii libstartup-notification0 0.12-6 ii libstdc++610-20200211-1 ii libx11-6 2:1.6.7-1 ii libx11-xcb1 2:1.6.8-1 ii libxcb-shm0 1.13.1-2 ii libxcb1 1.13.1-2 ii libxcomposite11:0.4.4-2 ii libxdamage1 1:1.1.4-3+b3 ii libxext6 2:1.3.3-1+b2 ii libxfixes31:5.0.3-1 ii libxrender1 1:0.9.10-1 ii libxt61:1.1.5-1+b3 ii procps2:3.3.15-2 ii zlib1g1:1.2.11.dfsg-1 Versions of packages firefox recommends: ii libavcodec58 7:4.2.1-2 Versions of packages firefox suggests: pn fonts-lmodern pn fonts-stix | otf-stix ii libcanberra0 0.30-7 ii libgssapi-krb5-2 1.17-3 ii libgtk2.0-02.24.32-4 ii pulseaudio 13.0-3 -- no debconf information
Bug#905144: parted: useless warning and error when working with image file
Package: parted Version: 3.2-21+b1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I'm trying to make a script that creates a system image with partitions. As I'm working with an image file, I do not need root permissions. But every start of parted makes it complain: sh: 1: dmidecode: not found WARNING: You are not superuser. Watch out for permissions. Example invocation: dd if=/dev/zero of=reform-system.img bs=1M count=8000 /sbin/parted reform-system.img mklabel gpt * What outcome did you expect instead? I find it unusual for a unix/linux command to complain preemptively about not having root permissions, especially if they are not necessary. Parted should also not try to use dmidecode if dealing with a file, IMHO. *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: armhf, i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages parted depends on: ii libc6 2.27-3 ii libparted23.2-21+b1 ii libreadline7 7.0-3 ii libtinfo6 6.1+20180210-4 parted recommends no packages. Versions of packages parted suggests: pn parted-doc -- no debconf information
Bug#772485: sparkleshare: setup window not resizable, hard to use with high DPI
Package: sparkleshare Version: 1.2-0.1 Severity: minor Dear Maintainer, The Sparkleshare Setup UI is hard to use on high DPI screens/setups such as "retina" displays, because it is not resizable. Screenshot: http://dump.mntmn.com/sparkle-ui-problem.png Cheers, Lukas (mntmn) -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sparkleshare depends on: ii git 1:2.1.3-1 ii gnome-icon-theme3.12.0-1 ii gvfs1.22.1-1 ii libc6 2.19-13 ii libglib2.0-cil 2.12.10-5 ii libgtk2.0-cil 2.12.10-5 ii libjs-jquery1.7.2+dfsg-3.2 ii libmono-corlib4.5-cil 3.2.8+dfsg-8 ii libmono-posix4.0-cil3.2.8+dfsg-8 ii libmono-system-core4.0-cil 3.2.8+dfsg-8 ii libmono-system-xml4.0-cil 3.2.8+dfsg-8 ii libmono-system4.0-cil 3.2.8+dfsg-8 ii libnotify0.4-cil0.4.0~r3032-7 ii libwebkit1.1-cil0.3-6 ii mono-runtime3.2.8+dfsg-8 Versions of packages sparkleshare recommends: ii python 2.7.8-2 ii python-nautilus 1.1-4 sparkleshare 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#293454: qjackctl: Display does not resize with font
Hi Rui, I understand what you mean in terms that you want a compact interface, which is still no problem with the patch. The problem becomes apparent when you use a higher DPI display (sometimes called "retina display" or "hi-dpi") where assumptions about reasonable pixel sizes do not apply anymore. Here it becomes important that UIs are scalable nicely and play together with the user defined DPI and theme settings. I guess this would also help visually impaired users. Cheers, Lukas On December 1, 2014 5:05:32 PM CET, Rui Nuno Capela wrote: >On 12/01/2014 01:00 PM, Jaromír Mikeš wrote: >> >> >> 2014-11-30 16:07 GMT+01:00 Lukas F. Hartmann > <mailto:lu...@mnt.mn>>: >> >> Hello Lukas, >> >> Dear Maintainer, >> >> This bug is especially obvious on high resolution displays. Also, >> the buttons >> do not resize vertically, only horizontally, which leads to a >> cramped UI with >> bigger font sizes. >> >> I attached a patch to fix these problems. The patch also removes >the >> manual >> indentation of the left-aligned status labels in the main status >> display and >> rather increases the overall margin of the status display. >> >> The interface is now fully scalable and looks good when disabling >> the "shiny >> background" bitmap option. I would recommend to drop this bitmap >and >> its toggle >> option to reduce code and settings complexity for a feature that >> does not >> (IMHO) increase end user value. >> >> >> Thank you for the patch, I am forwarding it upstream. >> Maybe Rui also have some idea how to improve "shiny background" to be >> scalable too. >> > >well, it wasn't ever supposed to scale as to grow in screen space that >is. > >from the cradle, it was designed to stayy as is, as *low profile* as >much as it's possible. > >tbh. once you get those settings "au point", or "al dente", whatever >semantics better suits you, the least you get qjackctl pesking your >screen estate the better :) > >byee >-- >rncbc aka Rui Nuno Capela >rn...@rncbc.org -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#293454: qjackctl: Display does not resize with font
Package: qjackctl Version: 0.3.12-1 Followup-For: Bug #293454 Dear Maintainer, This bug is especially obvious on high resolution displays. Also, the buttons do not resize vertically, only horizontally, which leads to a cramped UI with bigger font sizes. I attached a patch to fix these problems. The patch also removes the manual indentation of the left-aligned status labels in the main status display and rather increases the overall margin of the status display. The interface is now fully scalable and looks good when disabling the "shiny background" bitmap option. I would recommend to drop this bitmap and its toggle option to reduce code and settings complexity for a feature that does not (IMHO) increase end user value. Best regards, Lukas F. Hartmann (mntmn) -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages qjackctl depends on: ii jackd 5 ii libasound21.0.28-1 ii libc6 2.19-13 ii libgcc1 1:4.9.1-19 ii libjack-jackd2-0 [libjack-0.116] 1.9.10+20140719git3eb0ae6a~dfsg-2 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libstdc++64.9.1-19 ii libx11-6 2:1.6.2-3 qjackctl recommends no packages. Versions of packages qjackctl suggests: ii pulseaudio-utils 5.0-13 -- no debconf information diff --git a/src/qjackctlMainForm.ui b/src/qjackctlMainForm.ui index 52b379f..0bce179 100644 --- a/src/qjackctlMainForm.ui +++ b/src/qjackctlMainForm.ui @@ -61,7 +61,7 @@ 32767 - 28 + 32767 @@ -95,7 +95,7 @@ 32767 - 28 + 32767 @@ -127,8 +127,8 @@ - 260 - 80 + 32767 + 32767 @@ -142,7 +142,7 @@ - 2 + 8 0 @@ -169,9 +169,6 @@ false - - 2 - @@ -268,9 +265,6 @@ false - - 2 - @@ -324,9 +318,6 @@ false - - 2 - @@ -396,7 +387,7 @@ 32767 - 28 + 32767 @@ -427,7 +418,7 @@ 32767 - 28 + 32767 @@ -461,7 +452,7 @@ 32767 - 28 + 32767 @@ -495,7 +486,7 @@ 32767 - 28 + 32767 @@ -526,7 +517,7 @@ 32767 - 28 + 32767 @@ -560,7 +551,7 @@ 32767 - 28 + 32767 @@ -593,8 +584,8 @@ - 48 - 28 + 32767 + 32767 @@ -621,8 +612,8 @@ - 48 - 28 + 32767 + 32767 @@ -652,8 +643,8 @@ - 48 - 28 + 32767 + 32767 @@ -691,8 +682,8 @@ - 48 - 28 + 32767 + 32767 @@ -719,8 +710,8 @@ - 48 - 28 + 32767 + 32767 @@ -751,7 +742,7 @@ 32767 - 28 + 32767
Bug#771131: compton: 13" rMBP freezes on suspend with compton running
Package: compton Version: 0.1~beta2-1 Severity: normal Dear Maintainer, My system will reproducibly freeze as soon as I press the "suspend" button in the XFCE4 Logout panel when compton is running. When I do a "killall compton" before doing the suspend, the computer will suspend fine and awake correctly later. It is impossible to get out of the frozen state except if i hold down the power button for 10 seconds (then the computer will forcibly shut down and the session is lost). Cheers, Lukas F. Hartmann (mntmn) -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages compton depends on: ii libc6 2.19-13 ii libconfig91.4.9-2 ii libdbus-1-3 1.8.10-1 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libpcre3 1:8.35-3.1 ii libx11-6 2:1.6.2-3 ii libxcomposite11:0.4.4-1 ii libxdamage1 1:1.1.4-2 ii libxext6 2:1.3.3-1 ii libxfixes31:5.0.1-2+b1 ii libxinerama1 2:1.1.3-1+b1 ii libxrandr22:1.4.2-1+b1 ii libxrender1 1:0.9.8-1+b1 compton recommends no packages. compton 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#771022: roxterm: Segmentation fault when trying to edit current shortcut scheme
Tony Houghton writes: Hi Tony, Thanks for your quick reply! You are right. When setting EDITOR before starting roxterm, it does not crash. It crashes reliably when EDITOR is not set. Cheers, Lukas > On 25/11/14 23:18, Lukas F. Hartmann wrote: >> >> I freshly installed roxterm and started it from xfce4-terminal. When going >> to the menu Preferences > Edit Current Shortcuts Scheme, roxterm crashes >> with: Segmentation fault. > > I think I know what this is, but for some reason I didn't get round to > releasing a fixed version. Can you try setting the EDITOR environment > variable before running roxterm? If it works correctly with that set > I'll go ahead and release the fixed version which checks EDITOR > properly, hopefully it'll be just in time for jessie. > > If it still crashes with EDITOr set please install roxterm-gtk3-dbg and > get a stack backtrace. In that case it would probably also help to see > ~/.config/roxterm.sourceforge.net/Global and whichever file it > references in ~/.config/roxterm.sourceforge.net/Shortcuts. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#771022: roxterm: Segmentation fault when trying to edit current shortcut scheme
Package: roxterm Version: 2.9.4-1 Severity: normal Dear Maintainer, I freshly installed roxterm and started it from xfce4-terminal. When going to the menu Preferences > Edit Current Shortcuts Scheme, roxterm crashes with: Segmentation fault. I use xfce4 and compton. Best Regards, Lukas -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages roxterm depends on: ii roxterm-gtk3 2.9.4-1 roxterm recommends no packages. roxterm 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#770834: pulseaudio: MacBook 13"/2013: Only silence in microphone input (not muted)
Package: pulseaudio
Version: 5.0-13
Severity: normal
Dear Maintainer,
I am running Debian Jessie on a MacBook Pro Retina 13" from 2103. Audio works
fine except for microphone input, which always stays silent, regardless of mu
ting/unmuting or volume settings or fiddling with alsamixer.
The pavucontrol vumeter for Input Devices > Built-in Audio Analog Stereo >
Port:Internal Microphone stays in a zero state.
Alsamixer shows two Microphone capture devices ("Internal Microphone" and
"Internal Microphone 1") while pavucontrol shows one stereo device. When I
press
space on "Internal microphone 1", the input in pavucontrol appears muted. When
I unmute it, the volume meter is at 100% for a fraction of a second and then
goes down to zero. If I record directly after switching to "Internal
Microphone 1", only a single "plop" noise is recorded and then silence. This
does not
happen for "Internal Microphone" where only silence is recorded.
I would expect to see a working volume meter when enabling the microphone in
pavucontrol and to have working audio recording in client tools such as audaci
ty.
Thanks for looking into this or pointing to a more appropriate bug reporting
place,
Cheers,
Lukas F. Hartmann (mntmn)
-- relevant lspci line
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family
High Definition Audio Controller (rev 04)
-- relevant output of pacmd list-sources
* index: 2
name:
driver:
flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY
DYNAMIC_LATENCY
state: RUNNING
suspend cause:
priority: 9959
volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100%
/ 0.00 dB
balance 0.00
base volume: 19193 / 29% / -32.00 dB
volume steps: 65537
muted: no
current latency: 0.00 ms
max rewind: 0 KiB
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
Stereo
used by: 1
linked by: 1
configured latency: 20.00 ms; range is 0.50 .. 371.52 ms
card: 0
module: 6
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "CS4206 Analog"
alsa.id = "CS4206 Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xa061 irq 47"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1b.0"
sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "1e20"
device.product.name = "7 Series/C210 Series Chipset Family High
Definition Audio Controller"
device.form_factor = "internal"
device.string = "front:0"
device.buffering.buffer_size = "65536"
device.buffering.fragment_size = "32768"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Built-in Audio Analog Stereo"
alsa.mixer_name = "Intel PantherPoint HDMI"
alsa.components = "HDA:10134206,106b3b00,00100302
HDA:80862806,80860101,0010"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
ports:
analog-input-internal-mic: Internal Microphone (priority 8900,
latency offset 0 usec, available: unknown)
properties:
device.icon_name = "audio-input-microphone"
active port:
-- Package-specific info:
File '/etc/default/pulseaudio' does not exist
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap
