Bug#1053171: smplayer has one incompatibility with mpv (Bookworm)
Package: smplayer Version: 22.7.0~ds0-1 amd64 Severity: normal Generally smplayer works fine with installed mpv 0.35.0-3 in Bookworm. However there is one use case where I need a dirty hack to get it working: Watching TV via dvb-c and importing the channels.conf (generated by w-scan). When configuring smplayer via the GUI by Options -> Settings -> TV and Radio -> Search channels on start-up it does not find the working channels.conf in ~/.config/mpv/channels.conf. I could not find any file/location where I could configure the search path manually. Luckily the "mouse over" on this item displays a bubble help indicating that it is looking for the channels.conf in ~/.mplayer directory. This path should be updated to search both mpv's and mplayer's configuration directories. So I created the not existing directory (mkdir ~/.mplayer) and set a symlink ln -s ~/.config/mpv/channels.conf ~/.mplayer/ That way smplayer lets me select channels and watch TV as expected. In other configuration items there is no need and smplayer uses mpv as an alternative to mplayer without any tricks. Regards, Alf
Bug#1035665: grub-efi-amd64: GRUB command "halt" generates 1 "unsafe shutdown" on NVMe-SSD (Samsung 980)
Package: grub-efi-amd64
Version: 2.06-12
Severity: important
Tags: d-i
Dear Maintainer,
* What led up to the situation?
Select a command line in GRUB-menu ("c") and enter "halt to shutdown the PC.
Acording to official documentation on grub 2.06
(https://www.gnu.org/software/grub/manual/grub/grub.html paragraph 16.3.31) it
should perform a shutdown using APM.
After every "halt" command the PC powers off and at next boot my NVMe-SSD,
Samsung 980 has the SMART-attribute "unsafe shutdowns" increased by 1.
This indicates that the SSD's Buffers have not been transferred to NAND before
the power is cut.
Remark: said SSD uses host memory buffer (HMB), a technique becoming popular.
Those unsafe shutdowns do NOT happen when I perform a "poweroff" or "shutdown
-h" on a booted system (here Bookworm).
I tried to verify that it is not a single issue by discussing this issue in the
German debianforum and got the same beheaviour on similar hardware confirrmed.
https://debianforum.de/forum/viewtopic.php?t=186800#p1326586
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/nvme0n1p4 / ext4 rw,relatime,errors=remount-ro,stripe=32 0 0
/dev/nvme0n1p6 /home/ingo/data ext4 rw,noatime,errors=remount-ro,stripe=32 0 0
/dev/nvme0n1p1 /boot/efi vfat
rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
0 0
*** END /proc/mounts
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root 419e6a3e-0a83-4f46-b3cb-dcd21f7bc2ec
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=1024x768
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=de_DE
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=7
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=7
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root 419e6a3e-0a83-4f46-b3cb-dcd21f7bc2ec
insmod png
if background_image /usr/share/desktop-base/emerald-theme/grub/grub-16x9.png;
then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/09_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry 'Debian Bookworm on nvme0n1p4' {
search --fs-uuid --set=root 419e6a3e-0a83-4f46-b3cb-dcd21f7bc2ec
linux /vmlinuz root=UUID=419e6a3e-0a83-4f46-b3cb-dcd21f7bc2ec ro quiet
initrd /initrd.img
}
menuentry 'Debian Service System on nvme0n1p2' {
search --fs-uuid --set=root f137f033-f121-4857-9b00-f8ecaa32fff8
# linux /vmlinuz root=UUID=f137f033-f121-4857-9b00-f8ecaa32fff8 ro quiet
nvme_core.default_ps_max_latency>
linux /vmlinuz root=UUID=f137f033-f121-4857-9b00-f8ecaa32fff8 ro quiet
initrd /initrd.img
}
menuentry 'Debian Test System on nvme0n1p5' {
search --fs-uuid --set=root 689af3dd-5898-4c3c-a688-366815c0f79f
linux /vmlinuz root=UUID=689af3dd-5898-4c3c-a688-366815c0f79f ro quiet
initrd /initrd.img
}
menuentry "" {
normal
}
menuentry " Reboot" {
reboot
}
#menuentry " Shutdown" {
#halt
#}
menuentry "" {
normal
}
### END /etc/grub.d/09_custom ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian
Bug#1026060: Bug: #1026060 -- mpv: dvb playback does not work anymore
On Sun, 23 Apr 2023 12:49:19 +0200 Alf wrote: Hi Nicholas But that's also not true - it now works as before after switching the settings under "General" -> "Video" -> "Output driver" from "vaapi" to "libmpv" - that's all! I only use smplayer because of the comfortable way to zap between different channels. So with using "libmpv" I have definitely higher CPU-load (~12%) compared to mpv using vaapi (~1-2%)., but that's no issue for me. First of all many thanks for the hint to look for SMPlayer settings which led to get it working by changing "Output driver". Further investigating the configuration also led to a solution for the higher CPU load: SMPlayer seems not to evaluate my $HOME/.config/mpv/mpv.conf where I have hardware accelleration enabled. I now have set it additionally in SMPlayers configuration under Setting-> Advanced -> Mplayer/mpv -> Options --hwdec=vaapi (Attention: different to mpv.conf the option needs to be prefixed with 2 dashes) This way CPU load in SMPlayer drops down to only 1-2% - precisely as in MPV native. Also logs of smplayer are similar to mpv native: AO: [pipewire] 48000Hz stereo 2ch floatp VO: [gpu] 1280x720 vaapi[nv12] INFO_VIDEO_DSIZE=1280x720 MPV_VERSION=mpv 0.35.1 You can monitor GPU usage with the tool "intel-gpu-top" from the Debian-repo. Watch the ENGINE "Video". Any output !0 indicates hardware decoding. Also my first setting for "Video" -> "Output driver" may be changed back to "Default". That gives the same result, also other selections work, i.e. "gpu" but not all enable HW-decoding. Just "vaapi" throws errors. Sorry for using this bug report to describe configuration hints for SMPlayer, but such informnation is hardly available in the web. Thanks, Alf
Bug#1026060: Bug: #1026060 -- mpv: dvb playback does not work anymore
Here for completeness (just in case you want to dig into smplayer's vaapi issue): $ vainfo libva info: VA-API version 1.17.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_17 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.17 (libva 2.12.0) vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 23.1.1 () vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc VAProfileNone : VAEntrypointStats VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointFEI VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointFEI VAProfileH264High : VAEntrypointEncSliceLP VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointFEI VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointFEI VAProfileHEVCMain : VAEntrypointEncSliceLP VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointEncSliceLP VAProfileVP9Profile0: VAEntrypointVLD VAProfileVP9Profile0: VAEntrypointEncSliceLP VAProfileVP9Profile1: VAEntrypointVLD VAProfileVP9Profile1: VAEntrypointEncSliceLP VAProfileVP9Profile2: VAEntrypointVLD VAProfileVP9Profile2: VAEntrypointEncSliceLP VAProfileVP9Profile3: VAEntrypointVLD VAProfileVP9Profile3: VAEntrypointEncSliceLP VAProfileHEVCMain12 : VAEntrypointVLD VAProfileHEVCMain12 : VAEntrypointEncSlice VAProfileHEVCMain422_10 : VAEntrypointVLD VAProfileHEVCMain422_10 : VAEntrypointEncSlice VAProfileHEVCMain422_12 : VAEntrypointVLD VAProfileHEVCMain422_12 : VAEntrypointEncSlice VAProfileHEVCMain444: VAEntrypointVLD VAProfileHEVCMain444: VAEntrypointEncSliceLP VAProfileHEVCMain444_10 : VAEntrypointVLD VAProfileHEVCMain444_10 : VAEntrypointEncSliceLP VAProfileHEVCMain444_12 : VAEntrypointVLD VAProfileHEVCSccMain: VAEntrypointVLD VAProfileHEVCSccMain: VAEntrypointEncSliceLP VAProfileHEVCSccMain10 : VAEntrypointVLD VAProfileHEVCSccMain10 : VAEntrypointEncSliceLP VAProfileHEVCSccMain444 : VAEntrypointVLD VAProfileHEVCSccMain444 : VAEntrypointEncSliceLP VAProfileAV1Profile0: VAEntrypointVLD VAProfileHEVCSccMain444_10 : VAEntrypointVLD VAProfileHEVCSccMain444_10 : VAEntrypointEncSliceLP
Bug#1026060: Bug: #1026060 -- mpv: dvb playback does not work anymore
Hi Nicholas and Thomas, I have to correct my comment about "smplayer" -> got it working, my fault! I probably choose the wrong wording when saying "What now does not work: smplayer". It stopped working at the same time when mpv was upgradet to v0.35.* and stopped working. Correct I should have said "smplayer did not start working after update to mpv_0.35.1-4". But that's also not true - it now works as before after switching the settings under "General" -> "Video" -> "Output driver" from "vaapi" to "libmpv" - that's all! I only use smplayer because of the comfortable way to zap between different channels. So with using "libmpv" I have definitely higher CPU-load (~12%) compared to mpv using vaapi (~1-2%)., but that's no issue for me. For completeness here the full output when playing with mpv: $ mpv dvb://ARD [dvbin] Tuning to channel "ARD"... [dvbin] dvb_tune DVB-C ANNEX A Freq: 33000 [ffmpeg] NULL: non-existing PPS 0 referenced [ffmpeg/video] h264: non-existing PPS 0 referenced [ffmpeg/video] h264: decode_slice_header error [ffmpeg/video] h264: no frame! [ffmpeg/video] h264: non-existing PPS 0 referenced [ffmpeg/video] h264: non-existing PPS 0 referenced [ffmpeg/video] h264: decode_slice_header error [ffmpeg/video] h264: no frame! [ffmpeg/video] h264: non-existing PPS 0 referenced [ffmpeg/video] h264: non-existing PPS 0 referenced [ffmpeg/video] h264: decode_slice_header error [ffmpeg/video] h264: no frame! (+) Video --vid=1 (h264 1280x720 50.000fps) (+) Audio --aid=1 (ac3 2ch 48000Hz) File tags: Title: ARD [ffmpeg/video] h264: co located POCs unavailable [ffmpeg/video] h264: co located POCs unavailable Using hardware decoding (vaapi). AO: [pipewire] 48000Hz stereo 2ch floatp VO: [gpu] 1280x720 vaapi[nv12] AV: 00:02:42 / 00:02:45 (98%) A-V: 0.000 Cache: 3.3s/4MB Exiting... (Quit) Info regarding my GPU: Alder Lake CPU Core i5-12400 Firmware für UHD-Grafik 730: # dmesg | grep firmware [0.994151] i915 :00:02.0: firmware: direct-loading firmware i915/adls_dmc_ver2_01.bin [0.994647] i915 :00:02.0: [drm] Finished loading DMC firmware i915/adls_dmc_ver2_01.bin (v2.1) [0.999702] i915 :00:02.0: firmware: direct-loading firmware i915/tgl_guc_70.bin [0.999828] i915 :00:02.0: firmware: direct-loading firmware i915/tgl_huc.bin [1.086191] i915 :00:02.0: [drm] GuC firmware i915/tgl_guc_70.bin version 70.5.1 [1.086192] i915 :00:02.0: [drm] HuC firmware i915/tgl_huc.bin version 7.9.3 If you need more information to enable/improve vaapi for this GPU please let me know. Regards, Alf Am 23.04.23 um 01:21 schrieb Nicholas D Steeves: Dear Thomas and Alf, Thank you for confirming that this fix for DVB support works as it should. Thomas, if you have a few minutes of free time, would you please review the rest of this email, and consider verifying whether or not mpv_0.35.1-4 introduces a regression in smplayer? I hypothesise that mpv_0.35.1-3 works no better, but we need to be sure that mpv_0.35.1-4 doesn't cause any harm...if it does then smplayer will need a fix too (maybe just a rebuild). Alf writes: (+) Video --vid=1 (h264 1280x720 50.000fps) Ok, h264. (+) Audio --aid=1 (mp2 2ch 48000Hz) File tags: Title: arte HD(Unitymedia) [ffmpeg/video] h264: co located POCs unavailable Here is a thread about what this message means: https://www.mail-archive.com/ffmpeg-devel@ffmpeg.org/msg80351.html Using hardware decoding (vaapi). AO: [pipewire] 48000Hz stereo 2ch s16p VO: [gpu] 1280x720 vaapi[nv12] "nv12" is a colour space and pixel format thing. Yes, I had to look this up, because I've never seen "nv12" before. https://wiki.videolan.org/YUV
Bug#1026060: Bug: #1026060 -- mpv: dvb playback does not work anymore
Found detailled information on my hardware as I noted on first installation in Debian-Stretch: $ /opt/bin/mediaclient -e List of Media Hardware Devices device 0: [Sundtek MediaTV Pro (USB 2.0)] DVB-C, DVB-T, ANALOG-TV, FM-RADIO, REMOTE-CONTROL, OSS-AUDIO, RDS [INFO]: STATUS: STANDBY [BUS]: ID: 3-1.4 [SERIAL]: ID: U120820070038 [DVB-C,DVB-T]: FRONTEND: /dev/dvb/adapter0/frontend0 DVR: /dev/dvb/adapter0/dvr0 DMX: /dev/dvb/adapter0/demux0 [ANALOG-TV]: VIDEO0: /dev/video1 VBI0: /dev/vbi0 [FM-RADIO]: RADIO0: /dev/radio0 RDS: /dev/rds0 [REMOTECONTROL]: INPUT0: /dev/mediainput0 [OSS]: OSS0: /dev/dsp0
Bug#1026060: Bug: #1026060 -- mpv: dvb playback does not work anymore
Am 19.04.23 um 23:02 schrieb Nicholas D Steeves: Dear Alf and James, I agree that DVB support is important, and I just uploaded mpv_0.35.1-4 (to sid/unstable). That release will close this bug, but please test this it ASAP and confirm that it works with your DVB hardware. Yes, I know it might take a day to become available...sorry about that. I just updated mpv to version 0.35.1-4 from Sid - and can confirm that the issue has been fixed. All works as some time ago with v34.*. ... (+) Video --vid=1 (h264 1280x720 50.000fps) (+) Audio --aid=1 (mp2 2ch 48000Hz) File tags: Title: arte HD(Unitymedia) [ffmpeg/video] h264: co located POCs unavailable Using hardware decoding (vaapi). AO: [pipewire] 48000Hz stereo 2ch s16p VO: [gpu] 1280x720 vaapi[nv12] AV: 00:11:15 / 00:11:19 (99%) A-V: 0.000 Cache: 4.1s/5MB Hardware here is a quite old "Sundtek TV-Stick" from 2017 with their driver. I am watching DVB-C television with it and the channels.conf is unchanged. THANKS for your fast response and the fix! What now does not work: "smplayer". It only plays sound but no video. SMplayer-Protocol continously spits huge amounts of these messagen: [12:23:52:227] MPVProcess::parseLine: "[vo/vaapi] vaPutSurface() failed (invalid parameter)" But that's not an issue as long as "mpv" does the job. Alf
Bug#1026060: mpv: dvb playback does not work anymore
As Thomas Viehweger wrote, DVB support ist missing since upgrade to v 0.35.*. It can be clearly seen by executing mpv --list-protocols "dvb://" is no longer included. I searched all change.logs on Debian and also Upstream (https://github.com/mpv-player/mpv/releases) and I could not find any entry regarding removal/depreciation of dvb protocol. So it is definitely a regression and the severity of the bug should be raised to "serious". Regards, Alf
Bug#1032256: blueman: auto-connect incomplete, needs additional "bluetoothctl connect " to work
Am 04.03.23 um 23:08 schrieb Christopher Schramm: Hi Alf, those protocols are completely run by the audio server, which in your case seems to be PipeWire. blueman does not have any stake in it. Hi Christopher, does that also apply to the creation of these missing nodes as reported back to bluetoothctl after the second connect command? [Hama Freedom Light]# connect 3C:F8:A8:B9:CE:A1 Attempting to connect to 3C:F8:A8:B9:CE:A1 [NEW] Endpoint /org/bluez/hci0/dev_3C_F8_A8_B9_CE_A1/sep2 [NEW] Endpoint /org/bluez/hci0/dev_3C_F8_A8_B9_CE_A1/sep1 [NEW] Transport /org/bluez/hci0/dev_3C_F8_A8_B9_CE_A1/sep1/fd0 Connection successful [CHG] Device 3C:F8:A8:B9:CE:A1 ServicesResolved: yes [CHG] Transport /org/bluez/hci0/dev_3C_F8_A8_B9_CE_A1/sep1/fd0 Volume: 0x0060 (96) If yes, could you please assign/move this bug to pipewire Regards, Alf
Bug#1032256: blueman: auto-connect incomplete, needs additional "bluetoothctl connect " to work
but modem not available: AT+CGMI? Mär 01 16:39:09 xpc kernel: input: Hama Freedom Light (AVRCP) as /devices/virtual/input/input27 Mär 01 16:39:09 xpc Thunar[4070]: thunar-volman: Nicht unterstützter Eingabegerätetyp »(null)«. Mär 01 16:39:09 xpc systemd-logind[871]: Watching system buttons on /dev/input/event20 (Hama Freedom Light (AVRCP)) Mär 01 16:39:10 xpc Thunar[4075]: thunar-volman: Nicht unterstützter Eingabegerätetyp »/dev/input/event20«. I do not have the knowledge for further debugging this complicated bluetooth attitude. My guess currently is, the first auto-connect is with AVRCP profile only and the ear-buds are waiting for further information and/or callback. The second (manual) connect then registers the selected profile and completes connection. Regards, Alf -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-5-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages blueman depends on: ii adwaita-icon-theme43-1 ii bluez 5.66-1 ii bluez-obexd 5.66-1 ii dbus 1.14.6-1 ii dbus-user-session [default-dbus-session-bus] 1.14.6-1 ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4 ii gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+b1 ii gir1.2-glib-2.0 1.74.0-3 ii gir1.2-gtk-3.03.24.36-4 ii gir1.2-nm-1.0 1.42.0-1 ii gir1.2-pango-1.0 1.50.12+ds-1 ii gnome-icon-theme 3.12.0-5 ii libbluetooth3 5.66-1 ii libc6 2.36-8 ii libpulse-mainloop-glib0 16.1+dfsg1-2+b1 ii librsvg2-common 2.54.5+dfsg-1 ii polkitd 122-3 ii python3 3.11.2-1 ii python3-cairo 1.20.1-5+b1 ii python3-gi3.42.2-3+b1 ii python3-gi-cairo 3.42.2-3+b1 ii xfce4-notifyd [notification-daemon] 0.7.3-1 Versions of packages blueman recommends: pn pulseaudio-module-bluetooth blueman suggests no packages. -- no debconf information
Bug#1028834: Pluma no longer reopens a saved file at last cursor position
After yesterday's big update for Debian-Bookworm automagically this bug disappeared. However said upgrade did not contain anything that refers to pluma - mysterious.
Bug#1029352: netcfg: broken ifupdown support for ethernet interface
Similar Trouble here: A smoothly running Debian-Bookworm system here with ethernet eno1 managed by ifupdown, wlp1s0 is managed by NetworkManager. After today's bigger Update consisting of: qttranslations5-l10n:amd64 (5.15.7-2, 5.15.8-2), qtbase5-dev-tools:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5quickcontrols2-5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qml-module-qtquick-shapes:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qml-module-qtquick-layouts:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5core5a:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qml-module-qtquick-window2:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qt5-gtk-platformtheme:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), solaar:amd64 (1.1.8+dfsg-1, 1.1.8+dfsg-2), qml-module-qt-labs-settings:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), python3-pyqt5.qtopengl:amd64 (5.15.7+dfsg-3+b1, 5.15.7+dfsg-3+b3), libqt5charts5:amd64 (5.15.7-2, 5.15.8-2), libqt5qml5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), pyqt5-dev-tools:amd64 (5.15.7+dfsg-3+b1, 5.15.7+dfsg-3+b3), libqt5x11extras5:amd64 (5.15.7-2, 5.15.8-2), libmediastreamer12:amd64 (1:5.1.64+dfsg-3+b2, 1:5.1.64+dfsg-3+b3), qml-module-qtquick-controls2:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5quickshapes5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qml-module-qt-labs-platform:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5network5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qml-module-qtquick-localstorage:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5dbus5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5multimedia5-plugins:amd64 (5.15.7-2, 5.15.8-2), python3-pyqt5:amd64 (5.15.7+dfsg-3+b1, 5.15.7+dfsg-3+b3), libqt5quick5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5test5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qtwayland5:amd64 (5.15.7-2, 5.15.8-2), libqt5waylandcompositor5:amd64 (5.15.7-2, 5.15.8-2), libqt5widgets5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), python3-scipy:amd64 (1.8.1-20, 1.8.1-21), qml-module-qtcharts:amd64 (5.15.7-2, 5.15.8-2), libqt5gui5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5multimediagsttools5:amd64 (5.15.7-2, 5.15.8-2), python3-jsonschema:amd64 (4.9.1-3, 4.10.3-1), libqt5multimedia5:amd64 (5.15.7-2, 5.15.8-2), libqt5printsupport5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), ifupdown:amd64 (0.8.39+b1, 0.8.40), libqt5xml5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5opengl5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), linphone-desktop:amd64 (4.4.10-2+b1, 4.4.10-2+b2), libqt5texttospeech5:amd64 (5.15.7-2, 5.15.8-2), xfonts-encodings:amd64 (1:1.0.4-2.1, 1:1.0.4-2.2), libqt5sql5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qml-module-qtgraphicaleffects:amd64 (5.15.7-2, 5.15.8-2), qml-module-qt-labs-folderlistmodel:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5svg5:amd64 (5.15.7-2, 5.15.8-2), libqt5multimediawidgets5:amd64 (5.15.7-2, 5.15.8-2), libqt5quicktemplates2-5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qml-module-qtqml-models2:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qml-module-qtquick-privatewidgets:amd64 (5.15.7-2, 5.15.8-2), qtspeech5-speechd-plugin:amd64 (5.15.7-2, 5.15.8-2), qml-module-qtquick-controls:amd64 (5.15.7-2, 5.15.8-2), qml-module-qtquick-templates2:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5sql5-sqlite:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), libqt5qmlmodels5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), xfonts-scalable:amd64 (1:1.0.3-1.2, 1:1.0.3-1.3), xfce4-screenshooter:amd64 (1.10.2-1, 1.10.3-1), libqt5designer5:amd64 (5.15.7-2, 5.15.8-2), qml-module-qtquick2:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qml-module-qtquick-dialogs:amd64 (5.15.7-2, 5.15.8-2), libqt5qmlworkerscript5:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), python3-dbus.mainloop.pyqt5:amd64 (5.15.7+dfsg-3+b1, 5.15.7+dfsg-3+b3), libqt5waylandclient5:amd64 (5.15.7-2, 5.15.8-2), libqt5help5:amd64 (5.15.7-2, 5.15.8-2), qml-module-qtqml:amd64 (5.15.7+dfsg-2, 5.15.8+dfsg-2), qt5-gtk2-platformtheme:amd64 (5.0.0+git23.g335dbec-4+b6, 5.0.0+git23.g335dbec-4+b7) and subsequent reboot I did not get any network connection. systemctl restart networking brought my ethernet interface up again and all was fine. Applying Cyril's trick to substitute "allow-hotplug" by "auto" in /etc/network/interfaces resolved it for the moment.
Bug#1028834: pluma: Pluma no longer reopens a saved file at last cursor position
Package: pluma Version: 1.26.0-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? opening a previously saved file (filesize covering multiple pages of plain text) again displays at a random position some where inside the document. Cursor is placed somewhere in the visible range of text. * What exactly did you do (or not do) that was effective (or ineffective)? Works fine since years until including Bullsey with version 1.24 of pluma * What was the outcome of this action? * What outcome did you expect instead? Reopening a file at the position from which it was last saved/closed and cursor at its previous location. *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-6-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pluma depends on: ii gir1.2-peas-1.01.34.0-1+b1 ii gir1.2-pluma-1.0 1.26.0-1 ii iso-codes 4.12.0-1 ii libatk1.0-02.46.0-4 ii libc6 2.36-7 ii libcairo2 1.16.0-7 ii libenchant-2-2 2.3.3-2 ii libgdk-pixbuf-2.0-02.42.10+dfsg-1+b1 ii libgirepository-1.0-1 1.74.0-2 ii libglib2.0-0 2.74.4-1 ii libgtk-3-0 3.24.36-1 ii libgtksourceview-4-0 4.8.3-1 ii libice62:1.0.10-1 ii libpango-1.0-0 1.50.12+ds-1 ii libpeas-1.0-0 1.34.0-1+b1 ii libsm6 2:1.2.3-1 ii libx11-6 2:1.8.3-3 ii libxml22.9.14+dfsg-1.1+b2 ii mate-desktop-common1.26.0-1 ii pluma-common 1.26.0-1 Versions of packages pluma recommends: ii zenity 3.43.0-1 pluma suggests no packages. -- no debconf information
Bug#1024256: birdtray: Process birdtray dumped core on halt or logout
On Wed, 16 Nov 2022 18:50:02 +0100 Adam Borowski wrote:> ... On the other hand, the unread mails count is broken since the last Thunderbird update, and that's the main point of birdtray for me. Thus I'm looking forward to the release, but as new commits continue to come, I'm hurrying slowly. It is probably worth to mention that the "unread mail notification" is only broken on fresh installs of Bookworm/Sid - I see it here too. However I have another system here which is a upgrade from Bullseye to Bookworm I performed in Jan. 2022. That system still displays the number of unread mails and a blinking icon - however that system also shows a significant delay until the desktop is populated after login.
Bug#1025907: package-update-indicator no longer alerts user to available updates
This Bug is caused by upgrading from packagekit_1.2.5-3_amd64.deb to packagekit_1.2.6-1_amd64.deb when it migrated to testing on 2022-12-07. I downloaded the latest 1.2.5* version from https://snapshot.debian.org/package/packagekit/1.2.5-4/#packagekit_1.2.5-4, downgraded and apt-pinned it and: -> package-update-indicator works like a charm as it used to do since long So this Bug should be assigned to packagekit_1.2.6-1 rather.
Bug#1021488: solved
This bug isn't really a bug, found the resolution today: The settings which I claimed to be missing/ignored in cups-pdf are now available in job specific settings of the printing dialog (xfce4 desktop) and are persistent thus surviving reboots. This was absolutely different compared to how it was in Bullseye where there was no such possibility neither in the printing dialog nor in the settings of the printing object on the desktop. As this is a complete fresh installation of Bookworm there was no such notification during install. Also explanations in cups-pdf.conf do not mention that change. Sorry, Alf
Bug#1021488: printer-driver-cups-pdf: cups-pdf ignores some settings in /etc/cups/cups-pdf.conf
Package: printer-driver-cups-pdf
Version: 3.0.1-14
Severity: important
Dear Maintainer,
* What led up to the situation?
Just printing to cups-pdf printer results in a filename with suffix "job-ID" and not
stripped suffix "txt" as configured.
Example:
Input file = Bookworm.txt (plain text)
Output file = Bookworm.txt__enable-job_32.pdf
* What exactly did you do (or not do) that was effective (or ineffective)?
Whatever changes in cups-pdf.conf I do, be it "Key: Label", "Key: TitlePref" or
"Key: PDFVer"
will result in a similar output filename.
* What outcome did you expect instead?
Output filename should be just
Bookworm.pdf
and PDF-version should be 1.4.
Debug log clearly shows that my settings
Label 0 (default)
TitlePref 1
PDFVer 1.4 (default)(
are not respected:
/var/log/cups/cups-pdf-PDF_log:
l
Sun Oct 9 12:51:25 2022 [DEBUG] GSCall = "%s -q -dCompatibilityLevel=%s
-dNOPAUSE -dBATCH -dSAFER -sDEVICE=pdfwrite -sOutputFile="%s"
-dAutoRotatePages=/PageByPage -dAutoFilterColorImages=false -dColorImageFilter=/FlateEncode
-dPDFSETTINGS=/prepress -c -f %s"
Sun Oct 9 12:51:25 2022 [DEBUG] Grp= "lpadmin"
Sun Oct 9 12:51:25 2022 [DEBUG] GSTmp = "TMPDIR=/var/tmp"
Sun Oct 9 12:51:25 2022 [DEBUG] Log= "/var/log/cups"
Sun Oct 9 12:51:25 2022 [DEBUG] PDFVer = "1.2"
Sun Oct 9 12:51:25 2022 [DEBUG] PostProcessing = ""
Sun Oct 9 12:51:25 2022 [DEBUG] Out= "${HOME}/PDF"
Sun Oct 9 12:51:25 2022 [DEBUG] Spool =
"/var/spool/cups-pdf/SPOOL"
Sun Oct 9 12:51:25 2022 [DEBUG] UserPrefix = ""
Sun Oct 9 12:51:25 2022 [DEBUG] RemovePrefix = ""
Sun Oct 9 12:51:25 2022 [DEBUG] OutExtension = "pdf"
Sun Oct 9 12:51:25 2022 [DEBUG] Cut= 3
Sun Oct 9 12:51:25 2022 [DEBUG] Truncate = 64
Sun Oct 9 12:51:25 2022 [DEBUG] DirPrefix = 0
Sun Oct 9 12:51:25 2022 [DEBUG] Label = 2
Sun Oct 9 12:51:25 2022 [DEBUG] LogType= 7
Sun Oct 9 12:51:25 2022 [DEBUG] LowerCase = 1
Sun Oct 9 12:51:25 2022 [DEBUG] TitlePref = 0
Sun Oct 9 12:51:25 2022 [DEBUG] DecodeHexStrings = 1
Sun Oct 9 12:51:25 2022 [DEBUG] FixNewlines= 0
Sun Oct 9 12:51:25 2022 [DEBUG] AllowUnsafeOptions = 0
Sun Oct 9 12:51:25 2022 [DEBUG] AnonUMask =
Sun Oct 9 12:51:25 2022 [DEBUG] UserUMask = 0077
Sun Oct 9 12:51:25 2022 [DEBUG] *** End of Configuration ***
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.19.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages printer-driver-cups-pdf depends on:
ii cups2.4.2-1+b1
ii cups-client 2.4.2-1+b1
ii ghostscript 9.56.1~dfsg-1
ii libc6 2.35-2
ii libcups22.4.2-1+b1
ii libpaper-utils 1.1.28+b1
printer-driver-cups-pdf recommends no packages.
Versions of packages printer-driver-cups-pdf suggests:
ii system-config-printer 1.5.16-1
-- Configuration Files:
/etc/cups/cups-pdf.conf changed:
Out ${HOME}/PDF
Label 0
TitlePref 1
Grp lpadmin
DecodeHexStrings 1
-- no debconf information
Bug#998516: bridge-utils: Kernel assigns same MAC-address to the bridge on 2 similar network devices
Package: bridge-utils Version: 1.7-1 Severity: serious Dear Maintainer, * What led up to the situation? Having 2 tiny servers (APU2.C4 and APU.2D4) in my local net each having 3 ethernet interfaces assigned to a bridge "br0" (configured in /etc/network/interfaces). Upgrading from Bustser to Bullseye worked fine for the first box, the bridge received a new MAC assigned by the kernel as described in the listchanges. After reconfiguring that in the roter everything was working as before. Upgrading the second box in the same network segment lead to almost complete blocking of traffic in my local network and the 2nd box was not detected by the router. Connecting via serial console and checking network setup revealed: The second box got precisely the SAME MAC address as the first box! After using bridge_hw to assign the old MAC based on the MAC of one interface solved the problem. Conclusion is that hardware addresses should be unique in general, but the current way generates same address also if the MAC's of involved interfaces differs - see here: apu enp1s0 00:0d:b9:47:83:e8 - (Eth1) enp2s0 00:0d:b9:47:83:e9 - (Eth2) enp3s0 00:0d:b9:47:83:ea - (Eth3) br0 00:0d:b9:47:83:e8 => 4a:0f:ba:96:49:a5 apu2enp1s0 00:0d:b9:4e:76:a0 - (Eth1) enp2s0 00:0d:b9:4e:76:a1 - (Eth2) enp3s0 00:0d:b9:4e:76:a2 - (Eth3) br0 00:0d:b9:4e:76:a0 => 4a:0f:ba:96:49:a5 -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bridge-utils depends on: ii libc6 2.31-13+deb11u2 bridge-utils recommends no packages. Versions of packages bridge-utils suggests: ii ifupdown 0.8.36 -- no debconf information
Bug#979061: xfce4-screenshooter missleading/false panel icon
Package: xfce4-screenshooter Version: 1.9.8-1 Severity: normal Dear Maintainer, * What led up to the situation? updating from Buster to Bullseye * What exactly did you do (or not do) that was effective (or ineffective)? The icon sits in the panel at a size of 32x32 pixels and shows a monitor with a crossed-out screen. This lets one assume that it will i.e. switch-off the monitor or just kill the X-server. Not knowing what it was in earlier versions you never would guess it will take a screenshot. Having a look at the icon file at higher resolutions reveals that it should represent a scissor and a dotted rectangle which indictes something to be cut out. Additionally the light blue color spoils the look when sitting in a dark panel. I am using the greybird theme and not bluebird. * What outcome did you expect instead? A timy neutral (in color) panal icon showing a camera like in Buster and earlier versions of Debian. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xfce4-screenshooter depends on: ii libc62.31-6 ii libcairo21.16.0-4 ii libexo-2-0 4.16.0-1 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.4-1 ii libgtk-3-0 3.24.24-1 ii libsoup2.4-1 2.72.0-2 ii libx11-6 2:1.6.12-1 ii libxext6 2:1.3.3-1.1 ii libxfce4ui-2-0 4.16.0-1 ii libxfce4util74.16.0-1 ii libxfixes3 1:5.0.3-2 ii libxml2 2.9.10+dfsg-6.3+b1 Versions of packages xfce4-screenshooter recommends: ii libxfce4panel-2.0-4 4.14.4-1 xfce4-screenshooter suggests no packages. -- no debconf information
Bug#979059: xfce4-screenshooter missleading/false panel icon
Package: xfce4-screenshooter Version: 1.9.8-1 Severity: normal Dear Maintainer, * What led up to the situation? updating from Buster to Bullseye * What exactly did you do (or not do) that was effective (or ineffective)? The icon sits in the panel at a size of 32x32 pixels and shows a monitor with a crossed-out screen. This lets one assume that it will i.e. switch-off the monitor or just kill the X-server. Now knowing what it was in earlier versions you never would guess it will do a screenshot. Having a look at the icon file at higher resolutions reveals that it should represent a scissor and a dotted rectangle which indictes something to be cut out. Additionally the light blue color spoils the look when sitting in a dark panel. I am using the greybird theme and not bluebird. * What outcome did you expect instead? A timy neutral (in color) panal icon showing a camera like in Buster and earlier versions of Debian. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xfce4-screenshooter depends on: ii libc62.31-6 ii libcairo21.16.0-4 ii libexo-2-0 4.16.0-1 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.4-1 ii libgtk-3-0 3.24.24-1 ii libsoup2.4-1 2.72.0-2 ii libx11-6 2:1.6.12-1 ii libxext6 2:1.3.3-1.1 ii libxfce4ui-2-0 4.16.0-1 ii libxfce4util74.16.0-1 ii libxfixes3 1:5.0.3-2 ii libxml2 2.9.10+dfsg-6.3+b1 Versions of packages xfce4-screenshooter recommends: ii libxfce4panel-2.0-4 4.14.4-1 xfce4-screenshooter suggests no packages. -- no debconf information
Bug#898726: Fixed in version xfce4-sensors-plugin 1.3.92-1 from experimental
I faced the same problem (wanting to monitor fan2, but showed the value of AVCC in Volts) in Bullseye. Super I/O chip in Bullseye needs following module: nct6775 instead of formerly w83627ehf, while "sensors-detect" still reports the old module (address 0xa00, driver `w83627ehf') - should be fixed as well. In Buster I was lucky to get it right with this lines in ~/.config/xfce4/panel/xfce4-sensors-plugin-31.rc: [Chip2_Feature10] Id=-1 Address=10 Name=CPU-Fan Color=#00B000 Show=true Min=248,00 Max=3500,00 However in Bullseye I had no success even after hours to fiddle around. Finally, before reporting the bug, I checked with xfce4-sensors-plugin 1.3.92-1 from experimental and can confirm that this resolves the problem for me. To complete the information, here the output of "sensors" in Bullseye: $ sensors coretemp-isa- Adapter: ISA adapter Package id 0: +39.0°C (high = +85.0°C, crit = +105.0°C) Core 0:+37.0°C (high = +85.0°C, crit = +105.0°C) Core 1:+33.0°C (high = +85.0°C, crit = +105.0°C) Core 2:+35.0°C (high = +85.0°C, crit = +105.0°C) Core 3:+39.0°C (high = +85.0°C, crit = +105.0°C) acpitz-acpi-0 Adapter: ACPI interface temp1:+27.8°C (crit = +106.0°C) temp2:+29.8°C (crit = +106.0°C) nct6775-isa-0a00 Adapter: ISA adapter Vcore: 896.00 mV (min = +0.00 V, max = +1.74 V) in1: 768.00 mV (min = +0.00 V, max = +0.00 V) ALARM AVCC:3.39 V (min = +2.98 V, max = +3.63 V) +3.3V: 3.41 V (min = +2.98 V, max = +3.63 V) in4: 1.26 V (min = +0.00 V, max = +0.00 V) ALARM in5: 752.00 mV (min = +0.00 V, max = +0.00 V) ALARM in6: 1.08 V (min = +0.00 V, max = +0.00 V) ALARM 3VSB:3.34 V (min = +2.98 V, max = +3.63 V) Vbat:3.30 V (min = +2.70 V, max = +3.63 V) fan1: 270 RPM (min =0 RPM, div = 64) fan2: 329 RPM (min =0 RPM, div = 64) fan3: 397 RPM (min =0 RPM, div = 64) fan4: 0 RPM (div = 128) SYSTIN: +34.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = CPU diode CPUTIN: +39.5°C (high = +80.0°C, hyst = +75.0°C) sensor = CPU diode AUXTIN:+127.0°C (high = +80.0°C, hyst = +75.0°C) sensor = CPU diode PECI Agent 0: +38.5°C (high = +80.0°C, hyst = +75.0°C) (crit = +105.0°C) PCH_CHIP_TEMP: +65.0°C (high = +80.0°C, hyst = +75.0°C) PECI Agent 1:+0.0°C (high = +80.0°C, hyst = +75.0°C) (crit = +72.0°C) PCH_CPU_TEMP:+0.0°C cpu0_vid: +0.000 V intrusion0:ALARM beep_enable: disabled My guess for the problem is that some counter flips over at more than 8 sensors per adapter, so the value of line 2 (3.39V) is taken as output for sensor in line 10 (fan2) in the sample above. This way also the naming from line 10 was asigned to sensor 2 (double fan2 enties). The working entry in ~/.config/xfce4/panel/xfce4-sensors-plugin-31.rc now is like this: [Chip2_Feature10] Address=10 Name=CPU-Fan Color=#00B000 Show=true Min=301,00 Max=3500,00 Regards, Alf
Bug#952565: Please depend on libkf5windowsystem
Package: liblxqt0-dev Version: 0.14.2~71-g3aefce0-1 Severity: normal Would really reduce surprises :P Cheers Alf -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.18-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages liblxqt0-dev depends on: ii liblxqt0 0.14.2~71-g3aefce0-1 ii libqt5xdg-dev3.4.1~4-gfc98e31-1 ii libqt5xdgiconloader-dev 3.4.1~4-gfc98e31-1 ii lxqt-build-tools 0.7.0~7-g0fc5eeb-1 liblxqt0-dev recommends no packages. liblxqt0-dev suggests no packages. -- no debconf information
Bug#952266: lxqt-config: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTAT
Hi Lucas, the relevant part in the build log is this one: -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29") -- Checking for modules 'xcb;xcb' -- Found xcb, version 1.13.1 -- Found xcb, version 1.13.1 -- Found XCB: /usr/lib/x86_64-linux-gnu/libxcb.so;/usr/lib/x86_64-linux-gnu/libxcb.so -- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.11") -- Checking for module 'xorg-libinput' -- Found xorg-libinput, version 0.29.0 -- Checking for module 'xi' -- Found xi, version 1.7.9 -- Checking for module 'libudev' -- Found libudev, version 244 -- Checking for modules 'xcb;xcb;xcb-randr' -- No package 'xcb-randr' found CMake Error at /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146 (message): Could NOT find XCB (missing: XCB_LIBRARIES) Call Stack (most recent call first): /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:393 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake/lxqt-build-tools/find-modules/FindXCB.cmake:52 (find_package_handle_standard_args) lxqt-config-brightness/CMakeLists.txt:5 (find_package) Anyways - somewhat has changed so the package now need the additional build dependency libxcb-randr0-dev Will add and upload soon. Cheers Alf
Bug#929834: additional information
I meanwhile ended up using the buster-backports kernel 5.4.0-0.bpo.3-amd64. It seems the only way to avoid the nasty bug having to switch VT to get the monitor back on after blanking/power save. The Intel X11-driver has other drawbacks. While dealing with that problem quite often (also when upgrading 2 Lenovo-Tx20 laptops) I observed following with Ivy-Bridge and Sandy-Bridge CPU's): This problem manly happens when I first boot into another OS and thereafter into Buster without power cycle. Happens i.e. when you upgrade Stretch using a VT and finally reboot. Also happens when I save the complete Buster partition for backup using i.e. Clonezilla or on my PC where I have dual-boot with Stretch and Buster. This problem seems to dissappear with time when further exclusively booting Buster. Could it be that in Buster the GPU is not reset/initialized correctly and there are some settings remaining from previous boot/configuration?
Bug#950310: re: nomacs ftbfs with libexiv2-27
ok, it turns out that only one extra line was to change in the
imagestore headers and code - so i will upload soon
--- nomacs-3.12.0+dfsg.orig/src/DkCore/DkImageStorage.cpp
+++ nomacs-3.12.0+dfsg/src/DkCore/DkImageStorage.cpp
@@ -1424,7 +1424,7 @@ void DkImage::mapGammaTable(cv::Mat& img
qDebug() << "gamma computation takes: " << dt;
}
-void DkImage::logPolar(const cv::Mat& src, cv::Mat& dst, CvPoint2D32f
center, double scaleLog, double angle, double scale) {
+void DkImage::logPolar(const cv::Mat& src, cv::Mat& dst, cv::Point2d
center, double scaleLog, double angle, double scale) {
cv::Mat mapx, mapy;
--- nomacs-3.12.0+dfsg.orig/src/DkCore/DkImageStorage.h
+++ nomacs-3.12.0+dfsg/src/DkCore/DkImageStorage.h
@@ -95,7 +95,7 @@ public:
static void mapGammaTable(cv::Mat& img, const QVector& gammaTable);
static void gammaToLinear(cv::Mat& img);
static void linearToGamma(cv::Mat& img);
- static void logPolar(const cv::Mat& src, cv::Mat& dst,
CvPoint2D32f center, double scaleLog, double angle, double scale = 1.0);
+ static void logPolar(const cv::Mat& src, cv::Mat& dst,
cv::Point2d center, double scaleLog, double angle, double scale = 1.0);
static void tinyPlanet(QImage& img, double scaleLog, double
angle, QSize s, bool invert = false);
#endif
Bug#948917: FTBFS: No rule to make target '/usr/lib/x86_64-linux-gnu/libglib-2.0.so'
Nice, without changing a line of code screengrab now need libglib2.0-dev as build dependency.
Bug#950310: re: nomacs ftbfs with libexiv2-27
https://github.com/nomacs/nomacs/issues/429
BTW - The "solution" you suggest don't work, i'm really not willing to
waste my time and re-invent the wheel for things that are already fixed
upstream.
With your "solution" applied - NO! Please, no - even if that means that
nomacs will disappear from testing.
Cheers Alf
In file included from
/home/agaida/work/code/pkg-main/nomacs/nomacs/src/DkCore/DkBasicLoader.cpp:568:
/home/agaida/work/code/pkg-main/nomacs/nomacs/3rdparty/drif/drif_image.h:
In function 'uint8_t* nmc::drifLoadImg(const char*, uint32_t*,
uint32_t*, uint32_t*)':
/home/agaida/work/code/pkg-main/nomacs/nomacs/3rdparty/drif/drif_image.h:171:10:
warning: ignoring return value of 'size_t fread(void*, size_t, size_t,
FILE*)', declared with attribute warn_unused_result [-Wunused-result]
171 | fread((void*)buffer, DRIF_FOOTER_SZ, 1, fp);
| ~^~
[ 42%] Building CXX object CMakeFiles/nomacsCore.dir/src/DkCore/DkMath.cpp.o
/usr/lib/ccache/c++ -DHAVE_EXIV2_HPP -DNDEBUG -DNOMACS_VERSION=\"3.12\"
-DQT5 -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB
-DQT_NO_DEBUG -DQT_NO_DEBUG_OUTPUT -DQT_PRINTSUPPORT_LIB -DQT_SVG_LIB
-DQT_WIDGETS_LIB -DWITH_LIBRAW -DWITH_LIBTIFF -DWITH_OPENCV
-DWITH_QUAZIP -DnomacsCore_EXPORTS
-I/home/agaida/work/code/pkg-main/nomacs/nomacs/obj-x86_64-linux-gnu/nomacsCore_autogen/include
-I/home/agaida/work/code/pkg-main/nomacs/nomacs/obj-x86_64-linux-gnu
-I/home/agaida/work/code/pkg-main/nomacs/nomacs/src
-I/home/agaida/work/code/pkg-main/nomacs/nomacs/src/DkCore
-I/home/agaida/work/code/pkg-main/nomacs/nomacs/src/DkGui
-I/usr/include/quazip5
-I/home/agaida/work/code/pkg-main/nomacs/nomacs/3rdparty/libqpsd
-I/home/agaida/work/code/pkg-main/nomacs/nomacs/3rdparty/drif -isystem
/usr/include/opencv4 -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem
/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem
/usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem
/usr/include/x86_64-linux-gnu/qt5/QtSvg -g -O2
-fdebug-prefix-map=/home/agaida/work/code/pkg-main/nomacs/nomacs=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -std=c++11 -Wno-unknown-pragmas -O2 -g -DNDEBUG
-fPIC -DDK_CORE_DLL_EXPORT -DNOMINMAX -fPIC -o
CMakeFiles/nomacsCore.dir/src/DkCore/DkMath.cpp.o -c
/home/agaida/work/code/pkg-main/nomacs/nomacs/src/DkCore/DkMath.cpp
[ 43%] Building CXX object
CMakeFiles/nomacsCore.dir/src/DkCore/DkMessageBox.cpp.o
/usr/lib/ccache/c++ -DHAVE_EXIV2_HPP -DNDEBUG -DNOMACS_VERSION=\"3.12\"
-DQT5 -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB
-DQT_NO_DEBUG -DQT_NO_DEBUG_OUTPUT -DQT_PRINTSUPPORT_LIB -DQT_SVG_LIB
-DQT_WIDGETS_LIB -DWITH_LIBRAW -DWITH_LIBTIFF -DWITH_OPENCV
-DWITH_QUAZIP -DnomacsCore_EXPORTS
-I/home/agaida/work/code/pkg-main/nomacs/nomacs/obj-x86_64-linux-gnu/nomacsCore_autogen/include
-I/home/agaida/work/code/pkg-main/nomacs/nomacs/obj-x86_64-linux-gnu
-I/home/agaida/work/code/pkg-main/nomacs/nomacs/src
-I/home/agaida/work/code/pkg-main/nomacs/nomacs/src/DkCore
-I/home/agaida/work/code/pkg-main/nomacs/nomacs/src/DkGui
-I/usr/include/quazip5
-I/home/agaida/work/code/pkg-main/nomacs/nomacs/3rdparty/libqpsd
-I/home/agaida/work/code/pkg-main/nomacs/nomacs/3rdparty/drif -isystem
/usr/include/opencv4 -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem
/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem
/usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem
/usr/include/x86_64-linux-gnu/qt5/QtSvg -g -O2
-fdebug-prefix-map=/home/agaida/work/code/pkg-main/nomacs/nomacs=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -std=c++11 -Wno-unknown-pragmas -O2 -g -DNDEBUG
-fPIC -DDK_CORE_DLL_EXPORT -DNOMINMAX -fPIC -o
CMakeFiles/nomacsCore.dir/src/DkCore/DkMessageBox.cpp.o -c
/home/agaida/work/code/pkg-main/nomacs/nomacs/src/DkCore/DkMessageBox.cpp
/home/agaida/work/code/pkg-main/nomacs/nomacs/src/DkCore/DkImageStorage.cpp:
In static member function 'static void nmc::DkImage::tinyPlanet(QImage&,
double, double, QSize, bool)':
/home/agaida/work/code/pkg-main/nomacs/nomacs/src/DkCore/DkImageStorage.cpp:1508:27:
error: cannot convert 'cv::Point2d' {aka 'cv::Point_'} to
'CvPoint2D32f'
1508 | logPolar(mImg, mImg, cv::Point2d(mI
Bug#931528: workaround: lightdm does not start and display stays off after resume from DPMS
Package: xserver-xorg Version: 1:7.7+19 Followup-For: Bug #931528 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? As this bug exists since upgrade from Stretch to Buster here just a few hints: Display stays off when resuming from DPMS monitor off. Mouse events don't tigger resume. Only way to get X back is switcheing console (VT) by Ctrl+Alt+F1/F7. * What exactly did you do (or not do) that was effective (or ineffective)? Several hints as described also by other users in bug #929834 improve the situation, like using kernel 5.3 xset -s off deactivating start of light-locker etc. finally I observed the following: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929834#161. Now I discovered this posting from Dai_trying: http://forums.debian.net/viewtopic.php?f=10=142383#p700796 and generated a /etc/X11/xorg.conf as described service lightdm stop X -configure cp /root/xorg.conf.new /etc/X11/xorg.conf And that really works without any glitches for over a week so far. Additionally it also solved another bug which I reported on 19. March 2019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893559 It caused solaar (tool to manage Logitech Unifying Receiver) failing to start in xfce4 when set up for automatic start in session. Now it starts reliable iconised in the xfce4-panel. So, my guess is that this nasty bug is actually not caused by light-locker, but instead by xorg-server which either looses the mouse or fails to (re)start with correct configuration. With said xorg.conf all this is gone. * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) Xorg X server configuration file status: -rw-r--r-- 1 root root 3306 Jan 2 17:06 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" EndSection Section "Files" ModulePath "/usr/lib/xorg/modules" FontPath "/usr/share/fonts/X11/misc" FontPath "/usr/share/fonts/X11/cyrillic" FontPath "/usr/share/fonts/X11/100dpi/:unscaled" FontPath "/usr/share/fonts/X11/75dpi/:unscaled" FontPath "/usr/share/fonts/X11/Type1" FontPath "/usr/share/fonts/X11/100dpi" FontPath "/usr/share/fonts/X11/75dpi" FontPath "built-ins" EndSection Section "Module" Load "glx" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName"Monitor Model" EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz", ### : "%" ### [arg]: arg optional #Option "Accel" # [] #Option "AccelMethod" # #Option "Backlight" # #Option "CustomEDID"# #Option "DRI" # #Option "Present" # [] #Option "ColorKey" # #Option "VideoKey" # #Option "Tiling"# [] #Option "LinearFramebuffer" # [] #Option "HWRotation"# [] #Option "VSync" # [] #Option "PageFlip" # [] #Option "SwapbuffersWait" # [] #Option "TripleBuffer" # [] #Option "XvPreferOverlay" # [] #Option "HotPlug" # [] #Option "ReprobeOutputs"# [] #Option "XvMC" # [] #Option "ZaphodHeads" # #Option "VirtualHeads" # #Option "TearFree" # [] #Option "PerCrtcPixmaps"# [] #Option "FallbackDebug" # [] #Option "DebugFlushBatches"
Bug#929834: Found a workaround which also solves other oddities
I did try the different workarounds in Buster like "xset s off", disabling light-locker so it wouldn't start, tried kernel 5.3. All these improved the situations with "black screen", but finally still some situations where the monitor should awake from DPMS state remained and I had to switch virtual console (Ctrl+Alf+F1/F7) randomly every few days. Now I discovered this posting from Dai_trying: http://forums.debian.net/viewtopic.php?f=10=142383#p700796 and generated a /etc/X11/xorg.conf as described service lightdm stop X -configure cp /root/xorg.conf.new /etc/X11/xorg.conf And that really works without any glitches for over a week so far. Additionally it also solved another bug which I reported on 19. March 2019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893559 It caused solaar (tool to manage Logitech Unifying Receiver) failing to start in xfce4 when set up for automatic start in session. Now it starts reliable iconised in the xfce4-panel. So, my guess is that this nasty bug is actually caused not caused by light-locker, but instead by xorg-server which either looses the mouse or fails to (re)start with correct configuration. With said xorg.conf all this is gone.
Bug#945595: New mpv in sid breaks smplayer
Package: smplayer Version: 19.10.2~ds0-0.siduction Severity: grave Hi, new mpv 0.30* don't play well with smplayer in sid - new 19.10.* will solve that problem. No action needed right now, will work on it. Cheers Alf -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.11-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages smplayer depends on: ii libc6 2.29-3 ii libgcc1 1:9.2.1-20 ii libqt5core5a5.12.5+dfsg-2 ii libqt5dbus5 5.12.5+dfsg-2 ii libqt5gui5 5.12.5+dfsg-2 ii libqt5network5 5.12.5+dfsg-2 ii libqt5script5 5.12.5+dfsg-2 ii libqt5widgets5 5.12.5+dfsg-2 ii libqt5xml5 5.12.5+dfsg-2 ii libstdc++6 9.2.1-20 ii libx11-62:1.6.8-1 ii mplayer 2:1.3.0-8+b5 ii mpv 0.30.0-1 ii zlib1g 1:1.2.11.dfsg-1+b1 Versions of packages smplayer recommends: ii smplayer-l10n19.10.2~ds0-0.siduction ii smplayer-themes 1:18.6.0-1 smplayer suggests no packages. -- no debconf information
Bug#941741: closed by Alf Gaida (Re: libfm-qt6: Upstream fix for sorting issues)
On Sun, 10 Nov 2019 13:09:47 +1000 Reuben wrote: > Is there a reason why this was not included in 0.14.1-12 ? Sure there is a reason: It will be in sid with the upcoming release - it is not security related, there is no reason to add the patch. git says that there was over hundred commits upstream after the last release (107-g0954fc8) - so a new release is near and we will not grab single commits from upstream. Cheers Alf
Bug#924934: connman: add a connmant-tests package
Hi Ritesh, finally i was able and brave enough to finish the new connman packaging. It's not only about the connman-tests activation, it's also about iptables and nftables support. After using it some month with latest upstream i think it is ready for debian. So it would be nice if you could review and sponsor it when ready. Packaging is here: https://salsa.debian.org/debian/connman/tree/debian/experimental <https://salsa.debian.org/debian/connman/tree/debian/experimental> Cheers Alf PS: That's the fine thing about being DM - one need a review and a sponspr if one think new packages are needed - infrastructure things should not be uploaded without.
Bug#929834: With kernel linux-image-5.3.0-1-amd64 it seems to be fixed
Hi Yves-Alexis, I tested in Buster with kernel linux-image-5.3.0-1-amd64 from unstable and "modesetting" DDX: it appears to be fixed. Hardware is Intel Iyv-Bridge CPU with HD4000 GPU. The workarounds like using "intel" driver or "xset s off" are no longer required - great since the intel driver causes other problems. Would be great if that fix could be applied to the standard Buster kernel 4.19.0, so users will not have to use buster-backports repo.
Bug#942883: closed by Alf Gaida (Re: libqt5xdgiconloader3: Dependency upon qtbase-abi-5-11-3 prevents installation)
On Tue, 22 Oct 2019 13:58:13 -0700 Felicia P wrote: > Thank you for the transition information Hi, when running sid the transition tracker is the best friend one can have. Second best friend is apt - i might sound old fashioned, but GUI tools don't give so much hints about not wanted package removals or reasons for not installing certain packages - so in case apt want to remove x packages - just hit and find out the reason - on my work horse currently 106 packages are to be removed :D - the key word is patience. And while waiting one can use the time to gather some additional knowledge. (I learned it the very hard way years ago :P) Cheers Alf
Bug#942741: ITP: lxqt-organizer -- LXQt Pim, right now only an basic organizer
Package: wnpp Severity: wishlist Owner: Alf Gaida * Package name: lxqt-organizer Version : 0.1.0 Upstream Author : crispinalan * URL : https://github.com/lxqt/lxqt-organizer * License : LGPL Programming Lang: C++ Description : LXQt Pim, right now only an basic organizer The LXQt Team will maintain the package
Bug#942449: Found a solution/workaround
To remove those dead drive icons I just edited /etc/fstab and appended "x-gvfs-hide" to the mount options of those partititions like this: UUID=ea5ad8...de2 /media/sda1 ext4 noatime,errors=remount-ro,noauto,x-gvfs-hide 0 0 Immediately the icons disappear , even without reboot. So, it's just ea configuration error which reports partititions marked "nouser" as removable. Whether it is xfdesktop4 or even a bug in gvfs I don't know.
Bug#941333:
On Sun, 29 Sep 2019 00:03:57 -0500 Clinton H <49studeba...@gmail.com> wrote: > The new user might assume their wifi device is not supported. The new > user might not realize that their device is supported, but their > manual wifi switch is set to OFF. The chance is higher that there is no firmware for their hardware installed. Not all new linux users are idiots, ymmv. So it might not be wise to treat them like they are. The normal reaction will be: Check if wifi is turned on, second (only for technical interested users) check the installed firmware and swear if there is no firmware. And that it was. Most likely now they load an image that works with their hardware out of the box - chances are high that this next image is not debian and never ever will be again. Cheers Alf
Bug#942528: Some files in libkpmcore8 are missed - rendering Calamares unusable.
https://salsa.debian.org/qt-kde-team/extras/kpmcore/merge_requests/1 Should solve it. Cheers Alf
Bug#942528: Some files in libkpmcore8 are missed - rendering Calamares unusable.
Package: libkpmcore8 Version: 4.0.1-1.1 Severity: grave Will create some MRs and link them here Cheers Alf -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.5-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libkpmcore8 depends on: ii libblkid1 2.34-0.1 ii libc6 2.29-2 ii libgcc1 1:9.2.1-9 ii libkf5authcore5 5.62.0-1 ii libkf5coreaddons5 5.62.0-1 ii libkf5i18n5 5.62.0-1 ii libkf5widgetsaddons5 5.62.0-1 ii libqca-qt5-2 2.2.1-2 ii libqca-qt5-2-plugins 2.2.1-2 ii libqt5core5a 5.11.3+dfsg1-4 ii libqt5dbus5 5.11.3+dfsg1-4 ii libqt5gui55.11.3+dfsg1-4 ii libqt5widgets55.11.3+dfsg1-4 ii libstdc++69.2.1-9 libkpmcore8 recommends no packages. libkpmcore8 suggests no packages. -- no debconf information
Bug#942522: Calamares refuse to work with kpmcore 4.0.1
Package: calamares Severity: grave Hi, calamares stay forever in the Welcome screen with current kpmcore 4.0.1 in sid. Reason migt be some missed files in libkpmcore8. Will open some bugs and merge requests in kpmcore. Cheers Alf -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.5-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages calamares depends on: ii btrfs-progs5.2.1-1 pn calamares-branding ii kio5.62.1-2 ii kpackagetool5 5.62.0-1 ii libatasmart4 0.19-5 ii libblkid1 2.34-0.1 ii libboost-python1.67.0 1.67.0-13 ii libc6 2.29-2 ii libgcc11:9.2.1-9 ii libkf5auth55.62.0-1 ii libkf5codecs5 5.62.0-1 ii libkf5completion5 5.62.0-1 ii libkf5configcore5 5.62.0-1 ii libkf5configgui5 5.62.0-1 ii libkf5configwidgets5 5.62.0-1 ii libkf5coreaddons5 5.62.0-1 ii libkf5i18n55.62.0-1 ii libkf5jobwidgets5 5.62.0-1 ii libkf5kiocore5 5.62.1-2 ii libkf5kiowidgets5 5.62.1-2 ii libkf5package5 5.62.0-1 ii libkf5parts5 5.62.0-1 ii libkf5plasma5 5.62.0-1 ii libkf5service-bin 5.62.0-1 ii libkf5service5 5.62.0-1 ii libkf5sonnetui55.62.0-1 ii libkf5textwidgets5 5.62.0-1 ii libkf5widgetsaddons5 5.62.0-1 ii libkf5xmlgui5 5.62.0-1 pn libkpmcore7 ii libkpmcore84.0.1-1.1 ii libparted2 3.3-1 ii libpwquality1 1.4.1-3 ii libpython3.7 3.7.5-1 ii libqt5concurrent5 5.11.3+dfsg1-4 ii libqt5core5a 5.11.3+dfsg1-4 ii libqt5dbus55.11.3+dfsg1-4 ii libqt5gui5 5.11.3+dfsg1-4 ii libqt5network5 5.11.3+dfsg1-4 ii libqt5qml5 5.11.3-4 ii libqt5quick5 5.11.3-4 ii libqt5quickwidgets55.11.3-4 ii libqt5svg5 5.11.3-3 ii libqt5webkit5 5.212.0~alpha2-21 ii libqt5widgets5 5.11.3+dfsg1-4 ii libqt5xml5 5.11.3+dfsg1-4 ii libstdc++6 9.2.1-9 ii libyaml-cpp0.6 0.6.2-4 ii os-prober 1.77 ii squashfs-tools 1:4.4-1 ii sudo 1.8.27-1.1 Versions of packages calamares recommends: ii btrfs-progs 5.2.1-1 ii squashfs-tools 1:4.4-1 calamares suggests no packages.
Bug#942449: xfdesktop4: Icons for hidden disk partitions are shown as removable on the desktop
Package: xfdesktop4
Version: 4.12.4-2
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where
appropriate ***
* What led up to the situation?
Upgrading from Stretch to Buster made hidden drive icons of HD-partititions
appear on the desktop. It is impossible to hide them as before. This is
independant whether they are mountd or unmonted (when set to "noauto").
Those partititions are listed in fstab for manual mount by root only.
fstab entries are like this:
#/dev/sda1
UUID=ea5ad8...de2 /media/sda1 ext4 noatime,errors=remount-ro,noauto 0 0
* What exactly did you do (or not do) that was effective (or
ineffective)?
I have set up UDEV rules to hide those "drives" from users like this:
KERNEL=="sda1",ENV{UDISKS_IGNORE}="1"
According to freedesktop-org documentation the "HintIgnore" property
property should:
If TRUE, the device should be hidden from users.
Thunar beheaves correctly and does not show those drives.
* What was the outcome of this action?
All worked fine as it should in previous Debian releases including
Stretch, but since Buster I cannot hide the drives anymore.
Clicking on them just tells me:
"could not be mounted, operation permitted for root only."
* What outcome did you expect instead?
Respecting the UDEV-rules and not show "dead" icons on the desktop,
where normal users do not have access to.
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 10.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8),
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages xfdesktop4 depends on:
ii exo-utils0.12.4-1
ii libc62.28-10
ii libcairo21.16.0-4
ii libdbus-1-3 1.12.16-1
ii libdbus-glib-1-2 0.110-4
ii libexo-1-0 0.12.4-1
ii libgarcon-1-00.6.2-1
ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii libglib2.0-0 2.58.3-2+deb10u1
ii libgtk2.0-0 2.24.32-3
ii libnotify4 0.7.7-4
ii libpango-1.0-0 1.42.4-7~deb10u1
ii libpangocairo-1.0-0 1.42.4-7~deb10u1
ii libwnck222.30.7-6
ii libx11-6 2:1.6.7-1
ii libxfce4ui-1-0 4.12.1-3
ii libxfce4util74.12.1-3
ii libxfconf-0-24.12.1-1
ii xfdesktop4-data 4.12.4-2
Versions of packages xfdesktop4 recommends:
ii dbus-user-session [default-dbus-session-bus] 1.12.16-1
ii dbus-x11 [dbus-session-bus] 1.12.16-1
ii librsvg2-common 2.44.10-2.1
ii tumbler 0.2.3-1
ii xdg-user-dirs 0.17-2
Versions of packages xfdesktop4 suggests:
pn menu
-- no debconf information
Bug#912993: It's a configuration issue, in fact an old bug has been fixed
I was hit by the same issue as well, getting cryptic suffixes appended the the filename. I carefully went through the configuration file and found: > ### > # # > # Filename Settings # > # # > ### ... > ### Key: TitlePref (config, ppd, lpoptions) ## where to look first > for a title when creating the output filename ## (title in PS file > or title on commandline): ## 0: prefer title from %Title statement > in the PS file ## 1: prefer title passed via commandline ### > Default: 0 > > TitlePref 0 which means that the filename is derived preferable from the title statement in the PS file. However the old beheaviour was to derive the output filename from commandline = input filename, strip the suffix and append "pdf" instead. So, I set that Option to "1" > TitlePref 1 And now my PDF-printer works as it used to since years. I double checked with the configuration file in Stretch, ist is precisely the same as it shipped with Buster with regard to this option (default = 0), so actually in Stretch it was not performinmg as documentatoin says - thus buggy.
Bug#942157: replace the display-manager alternatives with sddm | x-display-manager
Package: lxqt Severity: normal as the title says - we don't care about the used display-manager, but default to sddm -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.2-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lxqt depends on: ii featherpad 0.11.1-2 ii kwin-x11 [x-window-manager]4:5.14.5-1 ii lightdm1.26.0-6 ii lximage-qt 0.14.2~55-g8cc1a6f-1 ii lxqt-about 0.14.2~35-g7be3d03-1 ii lxqt-admin 0.14.2~18-g43650c9-1 ii lxqt-branding-debian [lxqt-branding] 0.14.0.3 pn lxqt-core ii lxqt-openssh-askpass 0.14.2~9-g8cb5987-1 ii lxqt-powermanagement 0.14.2~33-gf4d5ab4-1 ii lxqt-sudo 0.14.2~33-gcc12337-1 ii openbox [x-window-manager] 3.6.1-8 ii pavucontrol-qt 0.14.2~21-g82110d6-1 ii pekwm [x-window-manager] 0.1.17-3+b1 ii qlipper1:5.1.3~2-gb2b3589-1 ii qps2.0.0-1 ii qterminal 0.14.2~62-g96fa4be-1 ii qttranslations5-l10n 5.11.3-2 ii sddm-theme-debian-elarun [sddm-theme] 0.18.0-1 ii sddm-theme-maui [sddm-theme] 0.18.0-1 ii xarchiver 1:0.5.4.14-1 ii xfwm4 [x-window-manager] 4.14.0-2 Versions of packages lxqt recommends: ii audacious 3.10.1-1 ii brave-browser [www-browser] 0.63.48 ii claws-mail3.17.4-1+b1 ii cmst 2019.04.192019.01.13-1-g0ab099e-1 ii dillo [www-browser] 3.0.5-6 ii falkon [www-browser] 3.0.0-3 ii feathernotes 0.4.7~86-g5d5cc93-1 ii firefox [www-browser] 69.0.2-1 ii google-chrome-unstable [www-browser] 79.0.3928.4-1 ii gucharmap 1:12.0.1-2 ii hexchat 2.14.2-5+b1 ii links [www-browser] 2.20.2-1 ii lynx [www-browser]2.9.0dev.4-1 ii meteo-qt 1.3.1~2-gb454cf8-1 ii midori [www-browser] 7.0-2+b1 ii mutt 1.10.1-2.1+b1 ii opera-stable [www-browser]64.0.3417.47 ii preload 0.6.4-5+b1 ii qpdfview 0.4.18-1 ii screengrab2.0.0~11-g8c798d2-1 ii smplayer 19.5.0~ds0-1 ii smtube19.6.0-1 ii weechat 2.6-1 Versions of packages lxqt suggests: pn calibre ii compton-conf 0.14.2~35-ga50ce9f-1 pn juffed ii nomacs 3.12.1~99-gadf70aaa-1 ii obconf-qt 0.14.2~25-gcc46f29-1 ii qt5-style-kvantum 0.11.3~61-g3b21348-1 pn qtpass pn shutter pn vokoscreen
Bug#939382: fswatch: bad symbols file on !amd64
On Wed, 4 Sep 2019 11:42:01 +0200 Gianfranco Costamagna wrote: > I don't think exporting such c++ symbols is a good idea, specially because they change between architectures, > and with different gcc optimization levels. I think it is a good idea - or the best idea right now. Tbh - i don't care much about different optimization levels (i know what you mean and i know the small derivative that uses O3 :P) - i don't care about architecture dependend symbols. Situation is not that nice, because the most of the differences was introduced by different compilers in some architectures. And yes, upstream should hide not needed symbols - but that's not my area of expertise - if any derivative think that these symbols are of no use - they can just delete the symbols file and be done with. So all i can do right now is to make some symbols optional. Cheers Alf
Bug#939796: ITP: lxqt-kcm-integration -- Integration package for several KDE control modules into LXQt
Package: wnpp Severity: wishlist Owner: Alf Gaida * Package name: lxqt-kcm-integration Version : 0.0.1 Upstream Author : Alf Gaida * URL : https://github.com/lxqt/lxqt-kcm-integration * License : (LGPL2+) Programming Lang: (desktop files) Description : Integration package for several KDE control modules into LXQt Right now the set of controls include: * KCM KWin settings * KCM Appearance * KCM Bluetooth * KCM Systeminfo The package will ease the pain when $user descide to use kwin with LXQt. The LXQt packaging team will maintain the package.
Bug#939651: meteo-qt/buster crashes immediately because of changed openweathermap data structure
Description: Fixes crash after changes of the received data (xml structure)
* backported from current upstream
* some minor string changes
* reflect changed openweathermap datastructure
* fix crash when wind direction is not available
* shows UV when available
* handle download errors and missing values
* fix logging handling
* fix crash when 6 days forcast is not available
* fix crash if applying settings and start minimized
* catch unhandled exceptions and write them into log file
* fix crash when UV index has two decimals
Author: Alf Gaida
---
Bug-Debian: https://bugs.debian.org/939651
Forwarded: not-needed
Last-Update: 2019-09-07
--- meteo-qt-1.0.0.orig/CHANGELOG
+++ meteo-qt-1.0.0/CHANGELOG
@@ -1,3 +1,11 @@
+1.1
+- Option to show the window at start-up
+- Fixes for crashes
+- Show wind info when Bft unit option is unchecked
+- Use unicode arrows for hPa and T° trend
+- Wrap weather information of the day on panel
+- Update translations [German, Slovak, Czech]
+
1.0.0
- Automatic detection of the geolocation
- Reenable UV Ozone in weather information
--- meteo-qt-1.0.0.orig/meteo_qt/about_dlg.py
+++ meteo-qt-1.0.0/meteo_qt/about_dlg.py
@@ -102,7 +102,8 @@ class AboutDialog(QDialog):
'',
'werthad '
'wert...@gmail.com'
-' [hu] Hungarian translation', ''
+' [hu] Hungarian translation',
+''
)
+ QCoreApplication.translate(
'',
@@ -129,27 +130,44 @@ class AboutDialog(QDialog):
'rw4...@yandex.ru'
'Alexey Zakaldaev '
'nelex...@gmail.com'
-'Liliya Panova [ru] Russian translation', ''
+'Liliya Panova [ru] Russian translation',
+''
+)
++ QCoreApplication.translate(
+'',
+'jose1711 '
+''
+'jose1...@gmail.com'
+' [sk] Slovak translation, Project',
+''
)
+ QCoreApplication.translate(
'',
'Atilla Öntaş '
''
'tarakbu...@gmail.com'
-' [tr] Turkish translation', ''
+' [tr] Turkish translation',
+''
)
+ QCoreApplication.translate(
'',
'Yuri Chornoivan '
'yurc...@ukr.net'
-' [uk] Ukrainian translation', ''
+' [uk] Ukrainian translation',
+''
)
+ QCoreApplication.translate(
'',
'You-Cheng Hsieh '
''
'yochenhs...@gmail.com'
-' [zh_TW] Chinese (Taiwan) translation', ''
+' [zh_TW] Chinese (Taiwan) translation',
+''
+)
++ QCoreApplication.translate(
+'',
+'pmav99 Project',
+''
)
-+ QCoreApplication.translate('', 'pmav99 Project', ''))
+)
return contributors
--- meteo-qt-1.0.0.orig/meteo_qt/citylistdlg.py
+++ meteo-qt-1.0.0/meteo_qt/citylistdlg.py
@@ -127,7 +127,7 @@ class CityListDlg(QDialog):
QCoreApplication.translate(
'Message when trying to remove the'
'last and unique city in the list',
-'This is the default city !',
+'This is the default city!',
'Cities list dialogue'
)
)
--- meteo-qt-1.0.0.orig/meteo_qt/meteo_qt.py
+++ meteo-qt-1.0.0/meteo_qt/meteo_qt.py
@@ -17,6 +17,9 @@ from lxml import etree
import json
import time
import datetime
+import traceback
+from io import StringIO
+import gc
from PyQt5.QtCore import (
PYQT_VERSION_STR, QT_VERSION_STR, QCoreApplication, QByteArray,
@@ -143,17 +146,6 @@ class SystemTrayIcon(QMainWindow):
# The traycolor has to be initialized here for the case when we cannot
# reach the tray method (case: set the color at first time usage)
self.traycolor = ''
-self.refresh()
-
-def overviewcity(self):
-temp_trend = ''
-if self.temp_trend == " ↗":
-temp_trend = " "
-elif self.temp_trend == " ↘":
-temp_trend = ""
-
-self.overviewcitydlg = QDialog()
-self.setCentralWidget(self.overviewcitydlg)
self.days_dico = {'0': self.tr('Mon'),
'1': self.tr('Tue'),
'2': self.tr('Wed'),
@@ -169,14 +161,21 @@ class SystemTrayIcon(QMainWindow):
self.hpa_indications = self.cond.pressure
self.uv_risk = self.cond.uv_risk
self.uv_recommend = self.cond.uv_recommend
+
+self.refresh()
+
+def overviewcity(self):
Bug#939651: meteo-qt/buster crashes immediately because of changed openweathermap data structure
Package: meteo-qt Version: 1.0.0-1 Severity: grave Tags: patch Hi, there are a few possible ways to solve this: * new version in buster * a wholesale patch (just tested, apply fine, build and run fine) * a stripped down patch who leaves typos and such things out Tbh i would prefer the wholesale patch without changing the version. meteo-qt is a typical leave package - nothing depend on it, so a wholesale patch should not introduce any problem for other packages - and fixes some crashes beside only changing the read of the new data structure. Cheers Alf -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.11-towo.2-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages meteo-qt depends on: ii python33.7.3-1 ii python3-lxml 4.4.1-1 ii python3-pyqt5 5.12.3+dfsg-2 ii python3-sip4.19.18+dfsg-1 Versions of packages meteo-qt recommends: ii meteo-qt-l10n 1.0.0-1 meteo-qt suggests no packages. -- debconf-show failed
Bug#936016: meteo-qt crashes immediately
my bad, my first answer was wrong - should talk with the author cheers Alf
Bug#936016: meteo-qt crashes immediately
Nice finding, unfortunately you are right: >From bfe9ae4d25b914d5c2622042303ba09fa8060e80 Mon Sep 17 00:00:00 2001 From: Dimitrios Glentadakis Date: Mon, 6 May 2019 19:34:58 +0200 Subject: [PATCH] Fix crash when 6 days forceast is not available --- meteo_qt/meteo_qt.py | 4 1 file changed, 4 insertions(+) diff --git a/meteo_qt/meteo_qt.py b/meteo_qt/meteo_qt.py index f6fca87..9774616 100644 --- a/meteo_qt/meteo_qt.py +++ b/meteo_qt/meteo_qt.py @@ -1861,6 +1861,10 @@ def run(self): 'Fetching url for 6 days :' + self.forecast6_url + self.id_ + self.suffix + '=7' ) +reqforecast6 = ( +self.forecast6_url + self.id_ ++ self.suffix + '=7' +) try: reqforecast6 = urllib.request.urlopen( self.forecast6_url + self.id_ Applying this patch to 1.0.0 fixes the problem for me - next question is: How to get this to stable, testing and sid have already 1.3.
Bug#930334: libfm-qt6: archivers.list adjustment (xarchiver compress)
On Mon, 10 Jun 2019 18:05:18 + "Amy Kos" wrote: > Package: libfm-qt6 > Version: 0.14.1-9 > Severity: wishlist > > > Hi, > > > please change line 16 from > > create=xarchiver --add-to %F > > to > > create=xarchiver --compress %F > > in > > /usr/share/libfm-qt/archivers.list > > For further details please see upstream commit: > https://github.com/ib/xarchiver/commit/d0575bcd1321dd0d7b47c242bd355e69067752c6 > > > Thanks, > Amy > > Why?
Bug#925687: fswatch: ftbfs with GCC-9
hahaha - good joke: The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release.
Bug#933189: Split out the backlight helper?
Package: liblxqt0 Version: 0.14.2~20-g2b80534-1 Severity: normal No further text needed -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.1.19-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages liblxqt0 depends on: ii desktop-file-utils 0.23-4 ii libc62.28-10 ii libkf5windowsystem5 5.54.0-1 ii libqt5core5a 5.11.3+dfsg1-2 ii libqt5dbus5 5.11.3+dfsg1-2 ii libqt5gui5 5.11.3+dfsg1-2 ii libqt5widgets5 5.11.3+dfsg1-2 ii libqt5x11extras5 5.11.3-2 ii libqt5xdg3 3.4.0~18-gf30ee3a-1 ii libstdc++6 9.1.0-10 ii libx11-6 2:1.6.7-1 ii libxss1 1:1.2.3-1 ii shared-mime-info 1.10-1 Versions of packages liblxqt0 recommends: ii liblxqt-l10n 0.14.2~20-g2b80534-1 liblxqt0 suggests no packages. -- no debconf information
Bug#933150: evolution crashes on loading external contents
Package: evolution Version: 3.32.2-1 Severity: grave Same bug for evolution/unstable when loading ext content in several html mails - if you cant reproduce i could forward such a mail. Thread 83 "pool-evolution" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffcef2b700 (LWP 1891)] __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:132 132 ../sysdeps/x86_64/multiarch/memcpy-ssse3.S: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 0x743e1a30 in __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:132 #1 0x772c358a in g_memdup () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x73764d0b in soup_buffer_new () at /lib/x86_64-linux-gnu/libsoup-2.4.so.1 #3 0x73764d73 in soup_buffer_copy () at /lib/x86_64-linux-gnu/libsoup-2.4.so.1 #4 0x73765004 in soup_message_body_append_buffer () at /lib/x86_64-linux-gnu/libsoup-2.4.so.1 #5 0x73767da1 in () at /lib/x86_64-linux-gnu/libsoup-2.4.so.1 #6 0x737683d4 in () at /lib/x86_64-linux-gnu/libsoup-2.4.so.1 #7 0x73768e27 in () at /lib/x86_64-linux-gnu/libsoup-2.4.so.1 #8 0x73765915 in () at /lib/x86_64-linux-gnu/libsoup-2.4.so.1 #9 0x73778c4c in () at /lib/x86_64-linux-gnu/libsoup-2.4.so.1 #10 0x7377911e in () at /lib/x86_64-linux-gnu/libsoup-2.4.so.1 #11 0x7fffe68d687d in () at /usr/lib/evolution/libevolution-mail.so.0 #12 0x74565a75 in e_content_request_process_sync () at /usr/lib/evolution/libevolution-util.so.0 #13 0x74565cc2 in () at /usr/lib/evolution/libevolution-util.so.0 #14 0x745dd789 in () at /usr/lib/evolution/libevolution-util.so.0 #15 0x772cd403 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x772cccfd in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x74472fa3 in start_thread (arg=) at pthread_create.c:486 #18 0x743a14cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 (gdb) continue Continuing. [1] + 6645 suspended (tty output) gdb evolution Cheers Alf -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.1.19-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages evolution depends on: ii dbus 1.13.12-1 ii evolution-common 3.32.2-1 ii evolution-data-server 3.32.2-2 ii libc6 2.28-10 ii libcamel-1.2-623.32.2-2 ii libclutter-gtk-1.0-0 1.8.4-4 ii libecal-1.2-19 3.32.2-2 ii libedataserver-1.2-24 3.32.2-2 ii libevolution 3.32.2-1 ii libglib2.0-0 2.61.1-2 ii libgtk-3-0 3.24.10-1 ii libical3 3.0.5-1 ii libnotify4 0.7.7-4 ii libsoup2.4-1 2.67.3-1 ii libwebkit2gtk-4.0-37 2.24.3-1 ii libxml22.9.8+dfsg-1+b1 ii psmisc 23.2-1 Versions of packages evolution recommends: ii evolution-plugin-bogofilter 3.32.2-1 ii evolution-plugin-pstimport 3.32.2-1 ii evolution-plugins3.32.2-1 ii yelp 3.31.90-1 Versions of packages evolution suggests: pn evolution-ews pn evolution-plugins-experimental ii gnupg 2.2.17-3 pn network-manager -- no debconf information
Bug#932578: Cinnamon Settings fail to start
Package: cinnamon Version: 3.8.8-1 Severity: grave Dear Maintainer, after dist-upgrading a current sid system cinnamon-settings fail to start. If started from terminal the following backtrace comes up: /usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py:220: DeprecationWarning: Gtk.Widget.set_margin_right is deprecated self.stack_switcher.set_margin_right(n) /usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py:233: DeprecationWarning: Gtk.Window.set_has_resize_grip is deprecated self.window.set_has_resize_grip(False) Traceback (most recent call last): File "/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py", line 608, in window = MainWindow() File "/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py", line 244, in __init__ for module in modules: File "/usr/share/cinnamon/cinnamon-settings/modules/cs_backgrounds.py", line 5, in import imtools File "/usr/share/cinnamon/cinnamon-settings/bin/imtools.py", line 623, in if Image.VERSION == '1.1.7': AttributeError: module 'PIL.Image' has no attribute 'VERSION' Reason is the uncoordinated upload of pillow in ver. 6.1.0-1. Downgrading python3-pil "solve" the problem for now. Cheers Alf -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.1.18-towo.1-siduction-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages cinnamon depends on: ii cinnamon-common 3.8.8-1 ii cinnamon-control-center 3.8.1-1 ii cinnamon-desktop-data3.8.1-2 ii cinnamon-screensaver 3.8.2-1 ii cinnamon-session 3.8.2-1 ii cinnamon-settings-daemon 3.8.4-2 ii cjs 3.8.0-5 ii cups-pk-helper 0.2.6-1+b1 ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii gir1.2-accountsservice-1.0 0.6.45-2 ii gir1.2-caribou-1.0 0.4.21-7 ii gir1.2-clutter-1.0 1.26.2+dfsg-10 ii gir1.2-cmenu-3.0 3.8.2-1 ii gir1.2-cogl-1.0 1.22.2-6 ii gir1.2-cvc-1.0 3.8.1-2 ii gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1 ii gir1.2-gkbd-3.0 3.26.1-1 ii gir1.2-glib-2.0 1.58.3-2 ii gir1.2-gnomedesktop-3.0 3.30.2.1-2 ii gir1.2-gtk-3.0 3.24.10-1 ii gir1.2-gtkclutter-1.01.8.4-4 ii gir1.2-keybinder-3.0 0.3.2-1 ii gir1.2-meta-muffin-0.0 3.8.2-1 ii gir1.2-nm-1.01.18.0-3 ii gir1.2-nma-1.0 1.8.22-2 ii gir1.2-notify-0.70.7.7-4 ii gir1.2-pango-1.0 1.42.4-6 ii gir1.2-polkit-1.00.105-25 ii gir1.2-soup-2.4 2.64.2-2 ii gir1.2-upowerglib-1.00.99.10-1 ii gir1.2-xapp-1.0 1.2.2-1 ii gkbd-capplet 3.26.1-1 ii gnome-backgrounds3.30.0-1 ii gnome-themes-extra 3.28-1 ii gsettings-desktop-schemas3.28.1-1 ii iso-flags-png-320x2401.0.2-1 ii libatk-bridge2.0-0 2.30.0-5 ii libatk1.0-0 2.30.0-2 ii libc62.28-10 ii libcairo21.16.0-4 ii libcinnamon-desktop4 3.8.1-2 ii libcinnamon-menu-3-0 3.8.2-1 ii libcjs0 3.8.0-5 ii libclutter-1.0-0 1.26.2+dfsg-10 ii libcogl-pango20 1.22.2-6 ii libcogl-path20 1.22.2-6 ii libcogl201.22.2-6 ii libcroco30.6.12-3 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libgirepository-1.0-11.58.3-2 ii libgl1 1.1.0-1 ii libglib2.0-0 2.60.5-1 ii libglib2.0-bin 2.60.5-1 ii libgstreamer1.0-01.16.0-2 ii libgtk-3-0 3.24.10-1 ii libmuffin0 3.8.2-1 ii libpango-1.0-0
Bug#931794: fwupd doesn't work because of latest logitech firmware
Version 2.9.1 from unstable fixes the bug, updating Logitech firmware for Unifying Receiver worked flawlessly - thanks! $ fwupdmgr get-updates Firmware-Aktualisierungen für Unifying Receiver verfügbar: Device ID: 2e9da6ef470824f72c5e7f16cc039da920f7b917 GUID:9d131a0c-a606-580f-8eda-80587250b8d6 GUID:279ed287-3607-549e-bacc-f873bb9838c4 Kennung: com.logitech.Unifying.RQR12.firmware Version aktualisieren: RQR12.08_B0030 Aktualisierungsname: Unifying Receiver Device Update Update Aktualisierungszusammenfassung:Firmware for the Logitech Unifying receiver Update Remote ID:lvfs Update Duration: 7 seconds Prüfsumme aktualisieren:SHA1(8dabc1e0fdd536c13d1e94c637d300f3541d3bf1) Ort aktualisieren: https://fwupd.org/downloads/690feedb8fe9cb05d1eaf80f903d66381eec7200-Logitech-Unifying-RQR12.08_B0030.cab Beschreibung aktualisieren:This release addresses an encrypted keystroke injection issue known as Bastille security issue #13. The vulnerability is complex to replicate and would require a hacker to be physically close to a target. • Wireless Mouse M335 • Zone Touch Mouse T400 • Wireless Mouse M545 • Wireless Mouse M560 • Touch Mouse M600 • Touch Mouse T620 • Wireless Rechargeable Touchpad T650 Kennung: com.logitech.Unifying.RQR12.firmware Version aktualisieren: RQR12.07_B0029 Aktualisierungsname: Unifying Receiver Device Update Update Aktualisierungszusammenfassung:Firmware for the Logitech Unifying receiver Update Remote ID:lvfs Update Duration: 7 seconds Prüfsumme aktualisieren:SHA1(d0d33e760ab6eeed6f11b9f9bd7e83820b29e970) Ort aktualisieren: https://fwupd.org/downloads/938fec082652c603a1cdafde7cd25d76baadc70d-Logitech-Unifying-RQR12.07_B0029.cab Beschreibung aktualisieren:This release addresses an unencrypted keystroke injection issue known as Bastille security issue #11. The vulnerability is complex to replicate and would require a hacker to be physically close to a target. $ fwupdmgr update Downloading RQR12.08_B0030 for Unifying Receiver... Firmware wird abgerufen https://fwupd.org/downloads/690feedb8fe9cb05d1eaf80f903d66381eec7200-Logitech-Unifying-RQR12.08_B0030.cab Herunterladen … [***] Entpacken … [***] Authentifizierung … [***] Unifying Receiver wird aktualisiert … Bereit … [***] Unifying Receiver wird aktualisiert …]
Bug#931794: fwupd doesn't work because of latest logitech firmware
I am hit by the same error when trying to update my Logitech Unifying Receiver (current Firmware RQR12.03_B0025). This Update is higly recommended to fix some recent vulnerabilitis in the Firmware, see https://www.heise.de/ct/artikel/Logitech-keyboards-and-mice-vulnerable-to-extensive-cyber-attacks-4464533.html. Therefore this bug should be tagged "securuty".
Bug#931875: gnome-shell-extension-dashtodock has broken dependencies
Package: gnome-shell-extension-dashtodock Severity: grave gnome-shell-extension-dashtodock : Depends: gnome-shell (>= 3.32) but 3.30.2-9 is to be installed -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.1.17-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-shell-extension-dashtodock depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 pn gir1.2-clutter-1.0 pn gnome-shell gnome-shell-extension-dashtodock recommends no packages. gnome-shell-extension-dashtodock suggests no packages.
Bug#931874: not installable, broken dependencies
Package: gnome-shell-extension-appindicator Severity: grave gnome-shell-extension-appindicator : Depends: gnome-shell (>= 3.31) but 3.30.2-9 is to be installed -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.1.17-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-shell-extension-appindicator depends on: pn gnome-shell gnome-shell-extension-appindicator recommends no packages. gnome-shell-extension-appindicator suggests no packages.
Bug#931252: lximage-qt: should have a manpage
If you want a manpage - just write one. We will be happy to merge it upstream. There will not be a manpage stub for debian. Re: Mandatory - of course i could use a tool to convert the help into a manpage, but: Really, no! Never ever. Never. Really. It will be more likely that the hell will freeze over. Cheers Alf
Bug#931236: connman: Sysv init script should do a noop if connman is not installed
test -x $DAEMON || exit 0 meh - why not, will not hurt. More verbose, normally i wouldn't care but it seems to be common in sysv. Cheers Alf
Bug#931236: connman: Sysv init script should do a noop if connman is not installed
I'm biased - if one remove connman and leave the configurations in place for a reason the system should be verbose about. If one want to really get rid of connman one should purge it - solved, no changes needed. Cheers Alf
Bug#929834: Buster/XFCE unlock screen is blank
Am 22.06.19 um 23:34 schrieb John Franklin: > > I've been suffering from this bug in a clean Buster system, too. A > solution noted in another bug tracker is to explicitly tell X.org to > use the intel driver. Apparently, it uses the fbdev driver by default. > (Sorry, I don't have a reference to other bug handy.) > > Per a suggestion in the other bug, I added the following config about a > week ago and haven't seen the problem since. > > $ cat /etc/X11/xorg.conf.d/20-intel.conf > Section "Device" > Identifier "Intel Graphics" > Driver "intel" > EndSection > > jf > Great John, I can confirm that it fixes the bug here too. My hardware: Ivy-Bridge i5 with Intel HD4000 graphics. Thanks, Alf
Bug#930632: unblock: libfm-qt/0.14.1-9
Hi Paul, hard to answer. Imho you miss nothing, but: * there was this long thread about the sense or non-sense of creating symbols for c++ libs. I'm in favour of doing so, but i also see the arguments from the other side. To be honest: I'm not that into symbols too, even after four or five years - but they are great to detect changes that imply a abi or api bump. I would consider the additional symbols harmless - if a application is not compiled against the changed lib, nothing changes - both symbols are used only internal but are exposed - so the functionality could be used in applications that use the library. I'm not sure if both symbols should be exposed, but i would leave that to upstream. I'm a big fan of not expose things - some of the LXQt main developers think otherwise. So i have to dive into this within the upcoming release cycle. The only thing for buster is: It will do no harm. The version is right: It will be the version that is available for the lifetime of buster. so 0.14.1~ is right when one consider possible backports. 1-9~ will trigger rightfully a lintian warning about the version - it doesn't really matter when the symbols are introduced, the only thing that matters is that the lib in the wild really contains these symbols. Cheers Alf
Bug#930632: unblock: libfm-qt/0.14.1-9
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libfm-qt Latest version fixes #926803, missed file monitoring on remote file systems. Without the fix remote filesystems are nearly unusable. Diff: diff --git a/debian/changelog b/debian/changelog index 9bc9b25..54ef4eb 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +libfm-qt (0.14.1-9) unstable; urgency=medium + + * Added upstream patch workaround-missed-file-monitoring.patch +(Closes: #926803) + * Added two new symbols - internal use only + + -- Alf Gaida Sat, 08 Jun 2019 16:39:11 +0200 + libfm-qt (0.14.1-8) unstable; urgency=medium * Removed the wrongly introduced build dependency on lxqt-qtplugin diff --git a/debian/libfm-qt6.symbols b/debian/libfm-qt6.symbols index d06f805..158bd23 100644 --- a/debian/libfm-qt6.symbols +++ b/debian/libfm-qt6.symbols @@ -531,12 +531,14 @@ libfm-qt.so.6 libfm-qt6 #MINVER# (c++)"Fm::Folder::filesAdded(Fm::FileInfoList&)@Base" 0.12.0 (c++)"Fm::Folder::filesChanged(std::vector, std::shared_ptr >, std::allocator, std::shared_ptr > > >&)@Base" 0.12.0 (c++)"Fm::Folder::filesRemoved(Fm::FileInfoList&)@Base" 0.12.0 + (c++)"Fm::Folder::findByPath(Fm::FilePath const&)@Base" 0.14.1~ (c++)"Fm::Folder::finishLoading()@Base" 0.12.0 (c++)"Fm::Folder::fromPath(Fm::FilePath const&)@Base" 0.12.0 (c++|arch= !armel !armhf !i386 !mips !mipsel !hppa !hurd-i386 !kfreebsd-i386 !m68k !powerpc !powerpcspe !sh4 !x32 )"Fm::Folder::getFilesystemInfo(unsigned long*, unsigned long*) const@Base" 0.12.0 (c++|arch= !amd64 !arm64 !mips64el !ppc64el !s390x !alpha !ia64 !kfreebsd-amd64 !ppc64 !riscv64 !sparc64 )"Fm::Folder::getFilesystemInfo(unsigned long long*, unsigned long long*) const@Base" 0.12.0 (c++)"Fm::Folder::hadCutFilesUnset()@Base" 0.12.0 (c++)"Fm::Folder::hasCutFiles()@Base" 0.12.0 + (c++)"Fm::Folder::hasFileMonitor() const@Base" 0.14.1~ (c++)"Fm::Folder::info() const@Base" 0.12.0 (c++)"Fm::Folder::isEmpty() const@Base" 0.12.0 (c++)"Fm::Folder::isIncremental() const@Base" 0.12.0 diff --git a/debian/patches/series b/debian/patches/series index 1a4dd71..031051b 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -2,3 +2,4 @@ fix-smb-recursive-copy.patch fix-license-headers.patch dont-ignore-crea-del-sequences.patch workaround-glib-recursive-moving-error.patch +workaround-missed-file-monitoring.patch diff --git a/debian/patches/workaround-missed-file-monitoring.patch b/debian/patches/workaround-missed-file-monitoring.patch new file mode 100644 index 000..5be3811 --- /dev/null +++ b/debian/patches/workaround-missed-file-monitoring.patch @@ -0,0 +1,143 @@ +Description: Realod folder after transfer job if it lacks file monitoring + Closes https://github.com/lxqt/pcmanfm-qt/issues/933 and closes + https://github.com/lxqt/libfm-qt/issues/280. After a file transfer job is + finished inside a directory, if it is the path of an open folder that lacks + file monitoring, this patch reloads its corresponding folder. In this way, the + lack of file monitoring is partially compensated for. + Please note that this doesn't work with `search://` because the files inside + `search://` don't belong to it. By covering file creation, renaming, moving + from one shared folder to another and deleting after trying to move into Trash. + +Last-Upd
Bug#929041: unblock: pcmanfm-qt/0.14.1-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package pcmanfm-qt
Starting pcmanfm-qt as root session need a running dbus user-session
Bug was: pcmanfm-qt does not start as root on Debian live (Closes: #928818)
diff --git a/config/pcmanfm-qt/lxqt/settings.conf.in
b/config/pcmanfm-qt/lxqt/settings.conf.in
index b7ef002..68dc7b1 100644
--- a/config/pcmanfm-qt/lxqt/settings.conf.in
+++ b/config/pcmanfm-qt/lxqt/settings.conf.in
@@ -1,6 +1,6 @@
[System]
IconThemeName=elementary
-SuCommand=lxqt-sudo %s
+SuCommand=lxsudo dbus-run-session -- %s
TerminalCommand=
Archiver=file-roller
SIUnit=false
diff --git a/debian/changelog b/debian/changelog
index 9347ae6..97ef5b0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,18 @@
+pcmanfm-qt (0.14.1-3) unstable; urgency=medium
+
+ * Enhanched the fix and included pcmanfm/settings.cpp - the fallback
+settings.
+
+ -- Alf Gaida Sun, 12 May 2019 01:41:32 +0200
+
+pcmanfm-qt (0.14.1-2) unstable; urgency=medium
+
+ * Starting pcmanfm-qt as root session need a running dbus user-session
+Bug was: pcmanfm-qt does not start as root on Debian live (Closes: #928818)
+Thanks adrian15 for spotting this.
+
+ -- Alf Gaida Sat, 11 May 2019 20:38:43 +0200
+
pcmanfm-qt (0.14.1-1) unstable; urgency=medium
* Cherry-picking upstream release 0.14.1.
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..7552e93
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+use-dbus-run-session.patch
diff --git a/debian/patches/use-dbus-run-session.patch
b/debian/patches/use-dbus-run-session.patch
new file mode 100644
index 000..af4333d
--- /dev/null
+++ b/debian/patches/use-dbus-run-session.patch
@@ -0,0 +1,46 @@
+Description: pcmanfm-qt need a dbus user session to be started as root
+ Just using dbus-run-session to get one. This is the upstream solution.
+
+Author: Alf Gaida
+Last-Update: 2019-05-11
+
+--- pcmanfm-qt-0.14.1.orig/config/pcmanfm-qt/lxqt/settings.conf.in
pcmanfm-qt-0.14.1/config/pcmanfm-qt/lxqt/settings.conf.in
+@@ -1,6 +1,6 @@
+ [System]
+ IconThemeName=elementary
+-SuCommand=lxqt-sudo %s
++SuCommand=lxsudo dbus-run-session -- %s
+ TerminalCommand=
+ Archiver=file-roller
+ SIUnit=false
+--- pcmanfm-qt-0.14.1.orig/pcmanfm/preferences.ui
pcmanfm-qt-0.14.1/pcmanfm/preferences.ui
+@@ -704,11 +704,13 @@ only if there are more than one tab.
+
+
+- Examples: xterm -e %s for terminal or
gksu %s for switching user.
+-%s = the command line you want to execute with terminal or su.
++ Examples:brFor terminal: ixterm -e
%s/ibrFor switching user: ilxsudo %s/i or
ilxsudo dbus-run-session -- %s/ibri%s/i
is the command line you want to execute with terminal or su.br
Important: Please use lxsudo, sudo alone will wreck permissions of the settings
file.
+
+
+- Qt::PlainText
++ Qt::RichText
++
++
++ true
+
+
+
+--- pcmanfm-qt-0.14.1.orig/pcmanfm/settings.cpp
pcmanfm-qt-0.14.1/pcmanfm/settings.cpp
+@@ -189,7 +189,7 @@ bool Settings::loadFile(QString filePath
+ // the value from XSETTINGS instead of hard code a fallback value.
+ fallbackIconThemeName_ = "oxygen"; // fallback icon theme name
+ }
+-suCommand_ = settings.value("SuCommand", "lxqt-sudo %s").toString();
++suCommand_ = settings.value("SuCommand", "lxsudo dbus-run-session --
%s").toString();
+ setTerminal(settings.value("Terminal", "xterm").toString());
+ setArchiver(settings.value("Archiver", "file-roller").toString());
+ setSiUnit(settings.value("SIUnit", false).toBool());
diff --git a/pcmanfm/preferences.ui b/pcmanfm/preferences.ui
index c7a3c37..0e5b916 100644
--- a/pcmanfm/preferences.ui
+++ b/pcmanfm/preferences.ui
@@ -704,11 +704,13 @@ only if there are more than one tab.
- Examples: xterm -e %s for terminal or
gksu %s for switching user.
-%s = the command line you want to execute with terminal or su.
+ Examples:brFor terminal: ixterm -e
%s/ibrFor switching user: ilxsudo %s/i or
ilxsudo dbus-run-session -- %s/ibri%s/i
is the command line you want to execute with terminal or su.br
Important: Please use lxsudo, sudo alone will wreck permissions of the settings
file.
- Qt::PlainText
+ Qt::RichText
+
+
+ true
diff --git a/pcmanfm/settings.cpp b/pcmanfm/settings.cpp
index 88d4056..d486c7f 100644
--- a/pcmanfm/settings.cpp
+++ b/pcmanfm/settings.cpp
@@ -189,7 +189,7 @@ bool Settings::loa
Bug#929033: unblock: lxqt-session/0.14.1-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package lxqt-session
Fixes the memory leak described in the commit message. The leak can allocate
in rare cases nearly all available RAM and make the machine unusable, original
upstream bug was about games running in wine and was reproducible without
introducing wine and games.
(https://github.com/lxqt/lxqt-session/pull/256)
commit c1e17fdc6344b9108b5cde7d31c5ad1f12a114b6
Author: Alf Gaida
Date: Sat May 11 15:30:24 2019 +0200
Fixes memory leak in lxqt-session
lxqt-session allocates memory for process output never read (Closes:
#928804)
diff --git a/debian/changelog b/debian/changelog
index 23a2adf..c92df90 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+lxqt-session (0.14.1-2) unstable; urgency=medium
+
+ * Fixes memory leak in lxqt-session, lxqt-session allocates memory for
process
+output never read (Closes: #928804)
+
+ -- Alf Gaida Sat, 11 May 2019 15:30:08 +0200
+
lxqt-session (0.14.1-1) unstable; urgency=medium
* Cherry-picking new upstream version 0.14.1.
diff --git a/debian/patches/forward-process-output.patch
b/debian/patches/forward-process-output.patch
new file mode 100644
index 000..e8e2faf
--- /dev/null
+++ b/debian/patches/forward-process-output.patch
@@ -0,0 +1,20 @@
+Author: Luís Pereira
+Date: Thu May 9 21:14:08 2019 +0100
+
+Don't throw stderr/stdout to a black hole
+Implement the consensus solution achieved described in
https://github.com/lxqt/lxqt-session/pull/256.
+It was, actually, one the alternative proposed by
https://github.com/keturn.
+
+diff --git a/lxqt-session/src/lxqtmodman.cpp b/lxqt-session/src/lxqtmodman.cpp
+index 2beff61..d11ffc0 100644
+--- a/lxqt-session/src/lxqtmodman.cpp
b/lxqt-session/src/lxqtmodman.cpp
+@@ -467,6 +467,7 @@ LXQtModule::LXQtModule(const XdgDesktopFile& file,
QObject* parent) :
+ fileName(QFileInfo(file.fileName()).fileName()),
+ mIsTerminating(false)
+ {
++QProcess::setProcessChannelMode(QProcess::ForwardedChannels);
+ connect(this, SIGNAL(stateChanged(QProcess::ProcessState)),
SLOT(updateState(QProcess::ProcessState)));
+ }
+
+
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..05bd07f
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+forward-process-output.patch
unblock lxqt-session/0.14.1-2
-- System Information:
Debian Release: 10.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500,
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.1.2-towo.2-siduction-amd64 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Bug#928941: HOME and TERM are stripped by mistake
Package: lxqt-sudo Version: 0.14.1-1 Severity: critical Tags: patch Configurations are written into wrong directories etc - not funny, if a programm is called with lxsudo again the false written config will be read, if called with a right working (graphical) sudo not. Informations written into wrong directories might cause security breaches. -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.1.1-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages lxqt-sudo depends on: ii libc6 2.28-10 ii liblxqt00.14.2~12-ga398a7c-1 ii libqt5core5a5.11.3+dfsg1-1 ii libqt5gui5 5.11.3+dfsg1-1 ii libqt5widgets5 5.11.3+dfsg1-1 ii libstdc++6 8.3.0-7 Versions of packages lxqt-sudo recommends: ii lxqt-qtplugin 0.14.1~8-g02a9e71-1 ii lxqt-sudo-l10n 0.14.1-1 lxqt-sudo suggests no packages. -- no debconf information
Bug#928818: pcmanfm-qt does not start as root on Debian live
Thanks adrian15, very helpful. After testing and discussing it a bit upstream the leading bug in that case is https://github.com/lxqt/pcmanfm-qt/issues/958 Fixed in: https://github.com/lxqt/pcmanfm-qt/pull/960 Cheers Alf
Bug#928804: lxqt-session allocates memory for process output never read
Package: lxqt-session
Version: 0.14.2~15-g55a59f8-1
Severity: important
Tags: patch
The way is to forward output from these processes to lxqt-session stdout. This
is discussed in
https://github.com/lxqt/lxqt/issues/442 and
https://github.com/lxqt/lxqt-session/pull/256
Patch:
Author: Luís Pereira
Date: Thu May 9 21:14:08 2019 +0100
Don't throw stderr/stdout to a black hole
Implement the consensus solution achieved described in
https://github.com/lxqt/lxqt-session/pull/256.
It was, actually, one the alternative proposed by https://github.com/keturn.
diff --git a/lxqt-session/src/lxqtmodman.cpp b/lxqt-session/src/lxqtmodman.cpp
index 2beff61..d11ffc0 100644
--- a/lxqt-session/src/lxqtmodman.cpp
+++ b/lxqt-session/src/lxqtmodman.cpp
@@ -467,6 +467,7 @@ LXQtModule::LXQtModule(const XdgDesktopFile& file, QObject*
parent) :
fileName(QFileInfo(file.fileName()).fileName()),
mIsTerminating(false)
{
+QProcess::setProcessChannelMode(QProcess::ForwardedChannels);
connect(this, SIGNAL(stateChanged(QProcess::ProcessState)),
SLOT(updateState(QProcess::ProcessState)));
}
-- System Information:
Debian Release: 10.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.0.14-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages lxqt-session depends on:
ii libc6 2.28-10
ii libkf5windowsystem5 5.54.0-1
ii liblxqt00.14.2~12-ga398a7c-1
ii libqt5core5a5.11.3+dfsg1-1
ii libqt5dbus5 5.11.3+dfsg1-1
ii libqt5gui5 5.11.3+dfsg1-1
ii libqt5widgets5 5.11.3+dfsg1-1
ii libqt5x11extras55.11.3-2
ii libqt5xdg3 3.4.0~13-ga0c8e32-1
ii libstdc++6 8.3.0-7
ii libudev1241-3
ii libx11-62:1.6.7-1
ii lxqt-qtplugin 0.14.1~8-g02a9e71-1
ii lxqt-theme-debian [lxqt-theme] 0.14.0.3
ii lxqt-themes [lxqt-theme]0.14.0-1
ii x11-xkb-utils 7.7+4
Versions of packages lxqt-session recommends:
ii lxqt-config 0.14.2~49-ge265219-1
ii lxqt-notificationd0.14.2~17-ga5ee062-1
ii lxqt-policykit0.14.1-1
ii lxqt-powermanagement 0.14.2~14-ge9c8192-1
ii lxqt-session-l10n 0.14.2~15-g55a59f8-1
ii lxqt-sudo 0.14.2~9-g544b8d0-1
ii pcmanfm-qt0.14.2~21-g40e9db1-1
ii qlipper 1:5.1.2-1
ii qps 1.10.21~15-gdfd70d8-1
ii suckless-tools44-1
ii xscreensaver 5.42+dfsg1-1
lxqt-session suggests no packages.
-- no debconf information
Bug#928740: unblock: libqtxdg/3.3.1-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libqtxdg
Avoid freeze for DBusActivatable apps, this is mostly visable for the panel
at startup and applications started from menu, pcmanfm-qt application folder
or lxqt-runner. Without the patch the application in charge is frosen up to
25-30s.
>From 6a5d3c26c583613e5c861ab4fafbb418ce82a138 Mon Sep 17 00:00:00 2001
From: Alf Gaida
Date: Thu, 9 May 2019 17:57:24 +0200
Subject: [PATCH] Upstream patch: Avoid freeze for DBusActivatable apps
(Closes: #928721)
---
debian/changelog | 6 +
debian/patches/avoid-dbus-freeze.patch | 164 +
debian/patches/series | 1 +
3 files changed, 171 insertions(+)
create mode 100644 debian/patches/avoid-dbus-freeze.patch
create mode 100644 debian/patches/series
diff --git a/debian/changelog b/debian/changelog
index 86b2be2..41a9c2f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+libqtxdg (3.3.1-2) unstable; urgency=medium
+
+ * Upstream patch: Avoid freeze for DBusActivatable apps (Closes: #928721)
+
+ -- Alf Gaida Thu, 09 May 2019 17:57:01 +0200
+
libqtxdg (3.3.1-1) unstable; urgency=medium
* Cherry-picked new upstream-release 3.3.1.
diff --git a/debian/patches/avoid-dbus-freeze.patch
b/debian/patches/avoid-dbus-freeze.patch
new file mode 100644
index 000..e90e67b
--- /dev/null
+++ b/debian/patches/avoid-dbus-freeze.patch
@@ -0,0 +1,164 @@
+From bccc6c4030a601892847e9a1495142a1938d1a58 Mon Sep 17 00:00:00 2001
+From: Palo Kisa
+Date: Tue, 9 Apr 2019 12:36:11 +0200
+Subject: [PATCH] xdgdesktopfile: Avoid freeze for DBusActivatable apps
+
+For case when the DBusActivatable application is unresponsive the
+startDetached() can block for a long time (the Qt default 25s DBus
+timeout). Blocking can't be avoided while using QDBusInterface, because
+the object can block directly in its constructor.
+
+So we use the generated interface class and set the timeout for the DBus
+call to 1500ms (can be overridden env variable QTXDG_DBUSACTIVATE_TIMEOUT).
+
+See also: https://bugreports.qt.io/browse/QTBUG-75016
+---
+ src/qtxdg/CMakeLists.txt | 10 +
+ .../dbus/org.freedesktop.Application.xml | 25 +++
+ src/qtxdg/xdgdesktopfile.cpp | 43 ---
+ 3 files changed, 72 insertions(+), 6 deletions(-)
+ create mode 100644 src/qtxdg/dbus/org.freedesktop.Application.xml
+
+diff --git a/src/qtxdg/CMakeLists.txt b/src/qtxdg/CMakeLists.txt
+index f75b5a5..60ba48b 100644
+--- a/src/qtxdg/CMakeLists.txt
b/src/qtxdg/CMakeLists.txt
+@@ -1,3 +1,5 @@
++set(CMAKE_INCLUDE_CURRENT_DIR ON)
++
+ set(QTX_LIBRARIES Qt5::Widgets Qt5::Xml Qt5::DBus)
+
+ set(libqtxdg_PUBLIC_H_FILES
+@@ -50,10 +52,18 @@ set(libqtxdg_CPP_FILES
+ xdgmimetype.cpp
+ )
+
++QT5_ADD_DBUS_INTERFACE(DBUS_INTERFACE_SRCS
++dbus/org.freedesktop.Application.xml
++application_interface
++)
++
++set_property(SOURCE ${DBUS_INTERFACE_SRCS} PROPERTY SKIP_AUTOGEN ON)
++
+ add_library(${QTXDGX_LIBRARY_NAME} SHARED
+ ${libqtxdg_PUBLIC_H_FILES}
+ ${libqtxdg_PRIVATE_H_FILES}
+ ${libqtxdg_CPP_FILES}
++${DBUS_INTERFACE_SRCS}
+ )
+
+ target_link_libraries(${QTXDGX_LIBRARY_NAME}
+diff --git a/src/qtxdg/dbus/org.freedesktop.Application.xml
b/src/qtxdg/dbus/org.freedesktop.Application.xml
+new file mode 100644
+index 000..945ba9e
+--- /dev/null
b/src/qtxdg/dbus/org.freedesktop.Application.xml
+@@ -0,0 +1,25 @@
++http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd;>
++
++
++
++
++
++
++
++
++
++
++
++
++
++
++
++
++
++
++
++
++
+diff --git a/src/qtxdg/xdgdesktopfile.cpp b/src/qtxdg/xdgdesktopfile.cpp
+index c22d57d..5fa7604 100644
+--- a/src/qtxdg/xdgdesktopfile.cpp
b/src/qtxdg/xdgdesktopfile.cpp
+@@ -30,6 +30,7 @@
+ #include "xdgdesktopfile_p.h"
+ #include "xdgdirs.h"
+ #include "xdgicon.h"
++#include "application_interface.h"
+
+ #include
+ #include
+@@ -100,6 +101,27 @@ QString (QString& str);
+ QString (QString& str);
+ void loadMimeCacheDir(const QString& dirName, QHash > & cache);
+
++namespace
++{
++//! Simple helper for getting timeout for starting of DBus activatable
applications
++class DBusActivateTimeout
++{
++private:
++int mTimeoutMs;
++DBusActivateTimeout()
++{
++bool ok;
++mTimeoutMs = qgetenv("QTXDG_DBUSACTIVATE_TIMEOUT").toInt();
++if (!ok)
++mTimeoutMs = 1500;
++}
++static DBusActivateTimeout msInstance;
++public:
++static const DBusActivateTimeout & instance() { return msInstance; }
++operator int() cons
Bug#928721: Avoid freeze for DBusActivatable apps
Package: libqt5xdg3 Version: 3.4.0~13-ga0c8e32-1 Severity: important Tags: patch For case when the DBusActivatable application is unresponsive the startDetached() can block for a long time (the Qt default 25s DBus timeout). Blocking can't be avoided while using QDBusInterface, because the object can block directly in its contructor. So we use the generated interface class and set the timeout for the DBus call to 1500ms (can be overriden env variable QTXDG_DBUSACTIVATE_TIMEOUT). See also: https://bugreports.qt.io/browse/QTBUG-75016 -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.12-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libqt5xdg3 depends on: ii file 1:5.35-4 ii libc6 2.28-10 ii libfile-mimeinfo-perl 0.29-1 ii libglib2.0-bin 2.60.0-1.1 ii libqt5core5a 5.11.3+dfsg1-1 ii libqt5dbus55.11.3+dfsg1-1 ii libqt5gui5 5.11.3+dfsg1-1 ii libqt5widgets5 5.11.3+dfsg1-1 ii libqt5xdgiconloader3 3.4.0~13-ga0c8e32-1 ii libqt5xml5 5.11.3+dfsg1-1 ii libstdc++6 8.3.0-7 ii shared-mime-info 1.10-1 Versions of packages libqt5xdg3 recommends: ii qttranslations5-l10n 5.11.3-2 libqt5xdg3 suggests no packages. -- no debconf information
Bug#928524: lxqt-panel starts with a delay of approx. 30s when the statusnotifier plugin is enabled
Package: lxqt-panel Version: 0.14.1-1 Severity: important Dear Maintainer, lxqt-panel will be displayed at systemstart with a 30s delay - in this time lxqt-runner is also not usable. Reason is the statusnotifier plugin. Solution: adding a recommend to sni-qt, so old-fashioned applications can use the indicator system with their systray. Cheers Alf -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lxqt-panel depends on: ii libasound2 1.1.8-1 ii libc6 2.28-10 ii libdbusmenu-qt5-2 0.9.3+16.04.20160218-1 ii libkf5solid55.54.0-1 ii libkf5windowsystem5 5.54.0-1 ii liblxqt-globalkeys-ui0 0.14.1-1 ii liblxqt-globalkeys0 0.14.1-1 ii liblxqt00.14.1-1 ii libpulse0 12.2-4 ii libqt5core5a5.11.3+dfsg1-1 ii libqt5dbus5 5.11.3+dfsg1-1 ii libqt5gui5 5.11.3+dfsg1-1 ii libqt5widgets5 5.11.3+dfsg1-1 ii libqt5x11extras55.11.3-2 ii libqt5xdg3 3.3.1-1 ii libqt5xml5 5.11.3+dfsg1-1 ii libsensors5 1:3.5.0-3 ii libstatgrab10 0.91-1+b2 ii libstdc++6 8.3.0-6 ii libsysstat-qt5-00.4.2-1 ii libx11-62:1.6.7-1 ii libxcb-xkb1 1.13.1-2 ii libxcb1 1.13.1-2 ii libxcomposite1 1:0.4.4-2 ii libxdamage1 1:1.1.4-3+b3 ii libxkbcommon-x11-0 0.8.2-1 ii libxkbcommon0 0.8.2-1 ii libxrender1 1:0.9.10-1 ii lxmenu-data 0.1.5-2 ii lxqt-policykit 0.14.1-1 Versions of packages lxqt-panel recommends: ii lxqt-about 0.14.1-1 ii lxqt-config 0.14.1-2 ii lxqt-notificationd 0.14.1-1 ii lxqt-panel-l10n 0.14.1-1 ii lxqt-qtplugin 0.14.0-3 ii lxqt-runner 0.14.1-1 ii lxqt-session0.14.1-1 ii pavucontrol-qt 0.14.1-1 ii qlipper 1:5.1.2-1 Versions of packages lxqt-panel suggests: ii lxqt 29 ii lxqt-core 29 -- no debconf information
Bug#928438: unblock: libfm-qt/0.14.1-8
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libfm-qt
Problem: Recursive moving of folders is prohibited in some cases
New version fixes #927708 which renders pcmanfm-qt nearly unusable for basic
tasks in file management.
Solution was to port back the upstream fix.
diff --git a/debian/changelog b/debian/changelog
index e5012f5..9bc9b25 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+libfm-qt (0.14.1-8) unstable; urgency=medium
+
+ * Removed the wrongly introduced build dependency on lxqt-qtplugin
+
+ -- Alf Gaida Sat, 27 Apr 2019 18:40:25 +0200
+
+libfm-qt (0.14.1-7) unstable; urgency=medium
+
+ * Workaround for GLib's recursive moving error (Closes: #927708)
+
+ -- Alf Gaida Sat, 27 Apr 2019 10:50:16 +0200
+
libfm-qt (0.14.1-6) unstable; urgency=medium
* Fixed ignored creation-deletion sequences (Closes: #927707)
diff --git a/debian/patches/series b/debian/patches/series
index 3a2195c..1a4dd71 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
fix-smb-recursive-copy.patch
fix-license-headers.patch
dont-ignore-crea-del-sequences.patch
+workaround-glib-recursive-moving-error.patch
diff --git a/debian/patches/workaround-glib-recursive-moving-error.patch
b/debian/patches/workaround-glib-recursive-moving-error.patch
new file mode 100644
index 000..838ff29
--- /dev/null
+++ b/debian/patches/workaround-glib-recursive-moving-error.patch
@@ -0,0 +1,33 @@
+From 476dded99de11a57c64103b4610f0de3dbdbc769 Mon Sep 17 00:00:00 2001
+From: Tsu Jan
+Date: Mon, 22 Apr 2019 00:07:07 +0430
+Subject: [PATCH] Workaround for GLib's recursive moving error, e.g. with bound
+ mounts
+
+`g_file_move()` may not work recursively on the same filesystem, especially
+with bound mounts (to `/mnt`, for example) and give the
`G_IO_ERROR_WOULD_RECURSE`
+error. This patch ignores the error and tries our
`FileTransferJob::copyFile()`.
+
+Closes https://github.com/lxqt/pcmanfm-qt/issues/943
+---
+ src/core/filetransferjob.cpp | 7 +++
+ 1 file changed, 7 insertions(+)
+
+diff --git a/src/core/filetransferjob.cpp b/src/core/filetransferjob.cpp
+index c3d5851..32f0f89 100644
+--- a/src/core/filetransferjob.cpp
b/src/core/filetransferjob.cpp
+@@ -83,6 +83,13 @@ bool FileTransferJob::moveFileSameFs(const FilePath&
srcPath, const GFileInfoPtr
+ // do the file operation
+ if(!g_file_move(srcPath.gfile().get(), destPath.gfile().get(),
GFileCopyFlags(flags), cancellable().get(),
+nullptr, this, )) {
++// Specially with mounts bound to /mnt, g_file_move() may give
the recursive error
++// and fail, in which case, we ignore the error and try copying
and deleting.
++if(err.code() == G_IO_ERROR_WOULD_RECURSE) {
++ if(auto parent = destPath.parent()) {
++ return copyFile(srcPath, srcInfo, parent,
destPath.baseName().get());
++ }
++}
+ retry = handleError(err, srcPath, srcInfo, destPath, flags);
+ }
+ else {
unblock libfm-qt/0.14.1-8
-- System Information:
Debian Release: 10.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.0.11-towo.2-siduction-amd64 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Bug#924934: connman: add a connmant-tests package
Hi Ritesh, no problem, will do so. Would you be so kind and review and sponsor it for NEW? Thanks, Alf
Bug#927984: unblock: lxqt-qtplugin/0.14.0-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package lxqt-qtplugin
lxqt-qtplugin try to load libfm-qt.so instead of libfm-qt.so.6.
(Closes: #927905)
>From 9f3a044c94b042d41e88d0b9aed9b2f043de8231 Mon Sep 17 00:00:00 2001
From: Alf Gaida
Date: Wed, 24 Apr 2019 23:05:32 +0200
Subject: [PATCH] Try to load the versioned libfm-qt.so.6 instead of
libfm-qt.so
(Closes: #927905)
---
debian/changelog | 7 +++
debian/patches/load-versioned-libfm-qt.patch | 20
debian/patches/series| 1 +
3 files changed, 28 insertions(+)
create mode 100644 debian/patches/load-versioned-libfm-qt.patch
create mode 100644 debian/patches/series
diff --git a/debian/changelog b/debian/changelog
index d59d042..0282597 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+lxqt-qtplugin (0.14.0-3) unstable; urgency=medium
+
+ * Try to load the versioned libfm-qt.so.6 instead of libfm-qt.so
+(Closes: #927905)
+
+ -- Alf Gaida Wed, 24 Apr 2019 23:05:04 +0200
+
lxqt-qtplugin (0.14.0-2) unstable; urgency=medium
* Added missed direct dependency libqt5xdgiconloader-dev, the new
diff --git a/debian/patches/load-versioned-libfm-qt.patch
b/debian/patches/load-versioned-libfm-qt.patch
new file mode 100644
index 000..c83378d
--- /dev/null
+++ b/debian/patches/load-versioned-libfm-qt.patch
@@ -0,0 +1,20 @@
+Description: Load the versioned library
+ Loading libfm-qt.so would not be wise, it would introduce a dependency
+ to libfm-qt-dev. So hard patching to libfm-qt.so.6 will be fine for
+ Buster - we will find a better solution upstream for the next release.
+Author: Alf Gaida
+
+---
+Bug-Debian: https://bugs.debian.org/927905
+
+--- lxqt-qtplugin-0.14.0.orig/src/lxqtplatformtheme.cpp
lxqt-qtplugin-0.14.0/src/lxqtplatformtheme.cpp
+@@ -239,7 +239,7 @@ QPlatformDialogHelper *LXQtPlatformTheme
+ // The createFileDialogHelper() method is dynamically loaded from
libfm-qt on demand
+ if(createFileDialogHelper == nullptr) {
+ // try to dynamically load libfm-qt.so
+-QLibrary libfmQtLibrary{QLatin1String("libfm-qt")};
++QLibrary libfmQtLibrary{QLatin1String("libfm-qt.so.6")};
+ libfmQtLibrary.load();
+ if(!libfmQtLibrary.isLoaded()) {
+ return nullptr;
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..231d243
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+load-versioned-libfm-qt.patch
--
2.20.1
unblock lxqt-qtplugin/0.14.0-3
-- System Information:
Debian Release: 10.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.0.9-towo.4-siduction-amd64 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Bug#927905: lxqt-qtplugin try to load the wrong version of libfm-qt
Package: lxqt-qtplugin
Version: 0.14.1~1-gc122cbd-1
Severity: important
Tags: patch
Dear Maintainer,
lxqt-qtplugin try to load libfm-qt.so which is strictly a dev symlink - the
right choice would be libfm-qt.so.6.
This brings up the poor Qt file dialog instead of the LXQt one when opening a
file.
For Buster a sufficient solution would be hard wiring the needed so-version.
--- lxqt-qtplugin-0.14.0.orig/src/lxqtplatformtheme.cpp
+++ lxqt-qtplugin-0.14.0/src/lxqtplatformtheme.cpp
@@ -239,7 +239,7 @@ QPlatformDialogHelper *LXQtPlatformTheme
// The createFileDialogHelper() method is dynamically loaded from
libfm-qt on demand
if(createFileDialogHelper == nullptr) {
// try to dynamically load libfm-qt.so
-QLibrary libfmQtLibrary{QLatin1String("libfm-qt")};
+QLibrary libfmQtLibrary{QLatin1String("libfm-qt.so.6")};
libfmQtLibrary.load();
if(!libfmQtLibrary.isLoaded()) {
return nullptr;
Thanks to @wxl (Lubuntu Team) for spotting this.
Cheers Alf
System Information:
Debian Release: 10.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.0.9-towo.4-siduction-amd64 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages lxqt-qtplugin depends on:
ii libc6 2.28-8
ii libdbusmenu-qt5-2 0.9.3+16.04.20160218-1
ii libqt5core5a [qtbase-abi-5-11-3] 5.11.3+dfsg1-1
ii libqt5dbus5 5.11.3+dfsg1-1
ii libqt5gui55.11.3+dfsg1-1
ii libqt5widgets55.11.3+dfsg1-1
ii libqt5xdgiconloader3 3.4.0~11-g91100ee-1
ii libstdc++68.3.0-6
Versions of packages lxqt-qtplugin recommends:
ii libfm-qt6 0.14.2~36-g06d8d31-2
ii lxqt-config 0.14.2~42-g0f43068-1
ii lxqt-session 0.14.2~12-g292c281-1
Versions of packages lxqt-qtplugin suggests:
pn lxqt | lxqt-core
-- no debconf information
Bug#927754: unblock: libfm-qt/0.14.1-6
diff --git a/debian/changelog b/debian/changelog
index 2124e86..e5012f5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+libfm-qt (0.14.1-6) unstable; urgency=medium
+
+ * Fixed ignored creation-deletion sequences (Closes: #927707)
+
+ -- Alf Gaida Sun, 21 Apr 2019 20:50:23 +0200
+
libfm-qt (0.14.1-5) unstable; urgency=medium
* Fixed license for vfs-search.c and vfs-menu.c - was forgotten upstream.
diff --git a/debian/patches/dont-ignore-crea-del-sequences.patch b/debian/patches/dont-ignore-crea-del-sequences.patch
new file mode 100644
index 000..677695c
--- /dev/null
+++ b/debian/patches/dont-ignore-crea-del-sequences.patch
@@ -0,0 +1,115 @@
+From 7e79e591eb536603da92ee537bf949490b1259fc Mon Sep 17 00:00:00 2001
+From: Tsu Jan
+Date: Sun, 21 Apr 2019 14:11:14 +0430
+Subject: [PATCH] Don't ignore creation-deletion sequences
+
+Fixes https://github.com/lxqt/pcmanfm-qt/issues/944
+
+Previously, if a file was in addition queue and then it came into the deletion
+queue, its addition and deletion were both ignored. That was wrong and could
+result in showing nonexistent files because addition can also happen in
+directory list job before being processed by file info job.
+
+Also process accumulated changes only after finishing the current info job and
+don't clear all deletion paths after processing them (because, logically, only
+those paths that can be deleted should be removed).
+---
+ src/core/folder.cpp | 60 +++--
+ 1 file changed, 31 insertions(+), 29 deletions(-)
+
+diff --git a/src/core/folder.cpp b/src/core/folder.cpp
+index 6c2b27d..2385a8b 100644
+--- a/src/core/folder.cpp
b/src/core/folder.cpp
+@@ -228,16 +228,6 @@ void Folder::onFileInfoFinished() {
+ return;
+ }
+
+-// process the changes accumulated during this info job
+-if(filesystem_info_pending // means a pending change; see "onFileSystemInfoFinished()"
+- || !paths_to_update.empty() || !paths_to_add.empty() || !paths_to_del.empty()) {
+-QTimer::singleShot(0, this, ::processPendingChanges);
+-}
+-// there's no pending change at the moment; let the next one be processed
+-else {
+-has_idle_update_handler = false;
+-}
+-
+ FileInfoList files_to_add;
+ FileInfoList files_to_delete;
+ std::vector files_to_update;
+@@ -271,6 +261,16 @@ void Folder::onFileInfoFinished() {
+ Q_EMIT filesChanged(files_to_update);
+ }
+ Q_EMIT contentChanged();
++
++// process the changes accumulated during this info job
++if(filesystem_info_pending // means a pending change; see "onFileSystemInfoFinished()"
++ || !paths_to_update.empty() || !paths_to_add.empty() || !paths_to_del.empty()) {
++QTimer::singleShot(0, this, ::processPendingChanges);
++}
++// there's no pending change at the moment; let the next one be processed
++else {
++has_idle_update_handler = false;
++}
+ }
+
+ void Folder::processPendingChanges() {
+@@ -314,21 +314,24 @@ void Folder::processPendingChanges() {
+ }
+
+ // process deletion
+-if(!paths_to_del.empty()) {
+-FileInfoList deleted_files;
+-for(const auto : paths_to_del) {
+-auto name = path.baseName();
+-auto it = files_.find(name.get());
+-if(it != files_.end()) {
+-deleted_files.push_back(it->second);
+-files_.erase(it);
+-}
++FileInfoList deleted_files;
++auto path_it = paths_to_del.begin();
++while(path_it != paths_to_del.end()) {
++const auto& path = *path_it;
++auto name = path.baseName();
++auto it = files_.find(name.get());
++if(it != files_.end()) {
++deleted_files.push_back(it->second);
++files_.erase(it);
++path_it = paths_to_del.erase(path_it);
+ }
+-if(!deleted_files.empty()) {
+-Q_EMIT filesRemoved(deleted_files);
+-Q_EMIT contentChanged();
++else {
++++path_it;
+ }
+-paths_to_del.clear();
++}
++if(!deleted_files.empty()) {
++Q_EMIT filesRemoved(deleted_files);
++Q_EMIT contentChanged();
+ }
+
+ if(pending_change_notify) {
+@@ -404,13 +407,12 @@ void Folder::eventFileDeleted(const FilePath& path) {
+ bool deleted = true;
+ // qDebug() << "delete " << path.baseName().get();
+ // G_LOCK(lists);
+-if(std::find(paths_to_add.cbegin(), paths_to_add.cend(), path) != paths_to_add.cend()) {
+-// if the file was going to be added, just remove it from the addition queue
+-paths_to_add.erase(std::remove(paths_to_add.begin(), paths_to_add.end(), path), paths_to_add.cend());
+-}
+-else if(std::find(paths_to_del.cbegin(), paths_to_del.cend(), path) == paths_to_del.cend()) {
++/* WARNING: If the file is in the addition queue, we shoul
Bug#927754: unblock: libfm-qt/0.14.1-6
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package libfm-qt In some rare cases libfm-qt ignore creation/deletion squences resulting in displaying non-existing files. (#927707) This version fixes this. (include/attach the debdiff against the package in testing) unblock libfm-qt/0.14.1-6 -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.7-towo.4-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#927708: Recursive moving of folders is prohibited in some cases
Package: libfm-qt6 Version: 0.14.2~36-g06d8d31-2 Severity: important Tags: patch Introduced by new glib, should be worked around - no need to do anything here, it's an upstream thing. Cheers Alf -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.7-towo.4-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libfm-qt6 depends on: ii libc6 2.28-8 ii libexif12 0.6.21-5.1 ii libglib2.0-0 2.60.0-1.1 ii libglib2.0-bin2.60.0-1.1 ii libmenu-cache31.1.1~2-g583c190-1 ii libqt5core5a [qtbase-abi-5-11-3] 5.11.3+dfsg1-1 ii libqt5gui55.11.3+dfsg1-1 ii libqt5widgets55.11.3+dfsg1-1 ii libqt5x11extras5 5.11.3-2 ii libstdc++68.3.0-6 ii libxcb1 1.13.1-2 ii shared-mime-info 1.10-1 Versions of packages libfm-qt6 recommends: ii libfm-qt-l10n 0.14.2~36-g06d8d31-2 libfm-qt6 suggests no packages. -- no debconf information
Bug#927707: libfm-qt ignores creation-deletion sequences
Package: libfm-qt6
Version: 0.14.2~36-g06d8d31-2
Severity: important
Tags: patch
Dear Maintainer,
in some rare cases libfm-qt ignore creation/deletion sequences resulting in
displaying non-existing files.
Upstream-Bug: https://github.com/lxqt/pcmanfm-qt/issues/944
Upstream-Fix: https://github.com/lxqt/libfm-qt/pull/408
Thanks to Walter Lapchynski (w...@polka.bike) for spotting this.
Cheers Alf
Patch:
>From 7e79e591eb536603da92ee537bf949490b1259fc Mon Sep 17 00:00:00 2001
From: Tsu Jan
Date: Sun, 21 Apr 2019 14:11:14 +0430
Subject: [PATCH] Don't ignore creation-deletion sequences
Fixes https://github.com/lxqt/pcmanfm-qt/issues/944
Previously, if a file was in addition queue and then it came into the deletion
queue, its addition and deletion were both ignored. That was wrong and could
result in showing nonexistent files because addition can also happen in
directory list job before being processed by file info job.
Also process accumulated changes only after finishing the current info job and
don't clear all deletion paths after processing them (because, logically, only
those paths that can be deleted should be removed).
---
src/core/folder.cpp | 60 +++--
1 file changed, 31 insertions(+), 29 deletions(-)
diff --git a/src/core/folder.cpp b/src/core/folder.cpp
index 6c2b27d..2385a8b 100644
--- a/src/core/folder.cpp
+++ b/src/core/folder.cpp
@@ -228,16 +228,6 @@ void Folder::onFileInfoFinished() {
return;
}
-// process the changes accumulated during this info job
-if(filesystem_info_pending // means a pending change; see
"onFileSystemInfoFinished()"
- || !paths_to_update.empty() || !paths_to_add.empty() ||
!paths_to_del.empty()) {
-QTimer::singleShot(0, this, ::processPendingChanges);
-}
-// there's no pending change at the moment; let the next one be processed
-else {
-has_idle_update_handler = false;
-}
-
FileInfoList files_to_add;
FileInfoList files_to_delete;
std::vector files_to_update;
@@ -271,6 +261,16 @@ void Folder::onFileInfoFinished() {
Q_EMIT filesChanged(files_to_update);
}
Q_EMIT contentChanged();
+
+// process the changes accumulated during this info job
+if(filesystem_info_pending // means a pending change; see
"onFileSystemInfoFinished()"
+ || !paths_to_update.empty() || !paths_to_add.empty() ||
!paths_to_del.empty()) {
+QTimer::singleShot(0, this, ::processPendingChanges);
+}
+// there's no pending change at the moment; let the next one be processed
+else {
+has_idle_update_handler = false;
+}
}
void Folder::processPendingChanges() {
@@ -314,21 +314,24 @@ void Folder::processPendingChanges() {
}
// process deletion
-if(!paths_to_del.empty()) {
-FileInfoList deleted_files;
-for(const auto : paths_to_del) {
-auto name = path.baseName();
-auto it = files_.find(name.get());
-if(it != files_.end()) {
-deleted_files.push_back(it->second);
-files_.erase(it);
-}
+FileInfoList deleted_files;
+auto path_it = paths_to_del.begin();
+while(path_it != paths_to_del.end()) {
+const auto& path = *path_it;
+auto name = path.baseName();
+auto it = files_.find(name.get());
+if(it != files_.end()) {
+deleted_files.push_back(it->second);
+files_.erase(it);
+path_it = paths_to_del.erase(path_it);
}
-if(!deleted_files.empty()) {
-Q_EMIT filesRemoved(deleted_files);
-Q_EMIT contentChanged();
+else {
+++path_it;
}
-paths_to_del.clear();
+}
+if(!deleted_files.empty()) {
+Q_EMIT filesRemoved(deleted_files);
+Q_EMIT contentChanged();
}
if(pending_change_notify) {
@@ -404,13 +407,12 @@ void Folder::eventFileDeleted(const FilePath& path) {
bool deleted = true;
// qDebug() << "delete " << path.baseName().get();
// G_LOCK(lists);
-if(std::find(paths_to_add.cbegin(), paths_to_add.cend(), path) !=
paths_to_add.cend()) {
-// if the file was going to be added, just remove it from the addition
queue
-paths_to_add.erase(std::remove(paths_to_add.begin(),
paths_to_add.end(), path), paths_to_add.cend());
-}
-else if(std::find(paths_to_del.cbegin(), paths_to_del.cend(), path) ==
paths_to_del.cend()) {
+/* WARNING: If the file is in the addition queue, we shouldn not remove it
from that queue
+ and ignore its deletion because it may have been added by the directory
list job, in
+ which case, ignoring an addition-deletion sequence would result in a
nonexistent file. */
+if(std::find(paths_to_del.cbegin(), paths_to_del.cend(), path) ==
paths_to_del.cend()) {
paths_to_del.push_back(path);
Bug#926513: unblock: fswatch/1.14.0+repack-7
Control: tags -1 - moreinfo
Bug#927380: unblock: libfm-qt/0.14.1-5
diff --git a/debian/changelog b/debian/changelog index 76ab27e..2124e86 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +libfm-qt (0.14.1-5) unstable; urgency=medium + + * Fixed license for vfs-search.c and vfs-menu.c - was forgotten upstream. + * Fixed d/copyright that way. + + -- Alf Gaida Thu, 18 Apr 2019 20:52:30 +0200 + libfm-qt (0.14.1-4) unstable; urgency=medium * Fix recursive copy to smb shares (and possible other remote filesystems) @@ -7,13 +14,13 @@ libfm-qt (0.14.1-4) unstable; urgency=medium libfm-qt (0.14.1-3) unstable; urgency=medium - * Fixed the remaining symbols + * Fixed the remaining symbols -- Alf Gaida Fri, 01 Mar 2019 01:34:43 +0100 libfm-qt (0.14.1-2) unstable; urgency=medium - * Fixed new and optional symbols + * Fixed new and optional symbols -- Alf Gaida Tue, 26 Feb 2019 22:07:40 +0100 diff --git a/debian/copyright b/debian/copyright index f040a2c..f7f9d49 100644 --- a/debian/copyright +++ b/debian/copyright @@ -5,20 +5,10 @@ Source: https://github.com/lxqt/libfm-qt Files: * Copyright: 2013-2019 LXQt team 2013-2019 Hong Jen Yee (PCMan) - 2012-2013 Andriy Grytsenko (LStranger) + 2012-2014 Andriy Grytsenko (LStranger) 2014 Kuzma Shapran License: LGPL-2.1+ -Files: src/core/vfs/vfs-search.c -Copyright: 2012-2014 Andriy Grytsenko (LStranger) -License: GPL-2.0+ - -Files:src/core/vfs/vfs-menu.c -Copyright: 2012 Hong Jen Yee (PCMan) - 2010 Shae Smittle -License: GPL-2.0+ - - Files: cmake/fm-qt-config.cmake.in Copyright: 2015 LuÃs Pereira License: BSD-3-Clause @@ -70,19 +60,3 @@ License: LGPL-2.1+ Public License version 2.1 can be found in "/usr/share/common-licenses/LGPL-2.1". -License: GPL-2.0+ - This package is free software; you can redistribute it and/or modify - it under the terms of the GNU General Public License as published by - the Free Software Foundation; either version 2 of the License, or - (at your option) any later version. - . - This package is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU General Public License for more details. - . - You should have received a copy of the GNU General Public License - along with this program. If not, see <https://www.gnu.org/licenses/> - . - On Debian systems, the complete text of the GNU General - Public License version 2 can be found in "/usr/share/common-licenses/GPL-2". diff --git a/debian/patches/fix-license-headers.patch b/debian/patches/fix-license-headers.patch new file mode 100644 index 000..f7e6045 --- /dev/null +++ b/debian/patches/fix-license-headers.patch @@ -0,0 +1,97 @@ +From 3d23ec7f0857cbc1ae8e42bdd27ab179a7e8344f Mon Sep 17 00:00:00 2001 +From: "Hong Jen Yee (PCMan)" +Date: Fri, 19 Apr 2019 01:19:08 +0800 +Subject: [PATCH] Fix the license header of code we took from libfm (they + should use LGPL2 instead of GPL2). - src/core/vfs/vfs-menu.c - + src/core/vfs/vfs-search.c These files are taken from libfm which has been + relicensed to LGPL 2 on 2014-09-05 by Andrey N. Gritsenko after consulting + other contributors. + +--- + src/core/vfs/vfs-menu.c | 21 ++--- + src/core/vfs/vfs-search.c | 37 + + 2 files changed, 27 insertions(+), 31 deletions(-) + +diff --git a/src/core/vfs/vfs-menu.c b/src/core/vfs/vfs-menu.c +index c541159..069b1bc 100644 +--- a/src/core/vfs/vfs-menu.c b/src/core/vfs/vfs-menu.c +@@ -4,20 +4,19 @@ + * + * Copyright 2012-2014 Andriy Grytsenko (LStranger) + * +- * This program is free software; you can redistribute it and/or modify +- * it under the terms of the GNU General Public License as published by +- * the Free Software Foundation; either version 2 of the License, or +- * (at your option) any later version. ++ * This library is free software; you can redistribute it and/or ++ * modify it under the terms of the GNU Lesser General Public ++ * License as published by the Free Software Foundation; either ++ * version 2.1 of the License, or (at your option) any later version. + * +- * This program is distributed in the hope that it will be useful, ++ * This library is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of +- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +- * GNU General Public License for more details. ++ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU ++ * Lesser General Public License for more details. + * +- * You should have received a copy of the GNU General Public License +- * along with this program; if not, write to the Free Software +- * Foundation, Inc., 51 Franklin Street, Fifth Floor,
Bug#927380: unblock: libfm-qt/0.14.1-5
Package: release.debian.org Severity: normal Owner: nthyk...@debian.org User: release.debian@packages.debian.org Usertags: unblock Please unblock package libfm-qt two files was released with the wrong license upstream, now fixed (include/attach the debdiff against the package in testing) unblock libfm-qt/0.14.1-5 -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.7-towo.4-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#921266: linphone: Segfault and crash with "error 4 in libc-2.28.so" on password entry
Am 13.04.19 um 14:30 schrieb Bernhard Übelacker: > Hello Alf, > > Am 12.04.19 um 22:10 schrieb Alf: >> I am prepared to test your patch as soon as I get a binary of the >> patched lib. > > please find attached some commands to build the package > with the patches in question by yourself. > Hello Bernhard, !! Success !! It works as expected - no more crashes, dialing out and accepting incoming calls, all works fine. I think, the problem was that Telekon/t-online does not supply a nonce after initial registering. At the beginning a nonce is sent once or twice to stay compatible with the old procedure (before transition to BNG). I found some figures indicating that some 15% of Users are still not converted, while 85% are on "BNG", which uses authentication by hardware (the port on the DSLAM). Here part of the debug output as logged by linphone with your patches, see the line with >>> "error: ... [nonce]not found.. <<<< which I suppose caused to the crash. message: 2019-04-14 19:01:54:880 channel [0x55e37bc52800]: keep alive sent to [UDP://tel.t-online.de:5060] message: 2019-04-14 19:02:04:909 channel [0x55e37bc52800]: keep alive sent to [UDP://tel.t-online.de:5060] message: 2019-04-14 19:02:08:614 linphone_core_find_auth_info(): returning auth info username=061234567818, realm=tel.t-online.de message: 2019-04-14 19:02:08:614 Auth info found for [061234567818] realm [tel.t-online.de] error: 2019-04-14 19:02:08:614 parameter [nonce]not found for header [authorization] message: 2019-04-14 19:02:08:614 Transaction [0x55e37bb11cb0] deleted message: 2019-04-14 19:02:08:615 Changing [client] [REGISTER] transaction [0x55e37bd3ec00], from state [INIT] to [TRYING] message: 2019-04-14 19:02:08:615 channel [0x55e37bc52800]: message sent to [UDP://tel.t-online.de:5060], size: [571] bytes REGISTER sip:tel.t-online.de SIP/2.0 Via: SIP/2.0/UDP 192.168.33.12:5060;branch=z9hG4bK.GfqS~Yviw;rport From: ;tag=PdBaldvNc To: sip:061234567...@tel.t-online.de CSeq: 22 REGISTER Call-ID: kNvTHMUU1E Max-Forwards: 70 Supported: replaces, outbound . If you need more information, please let me know, I can generate a debug log over a longer time period including incoming and outgoing calls. Again myany thanks for your great help and patience. Kind regards, Alf
Bug#921266: linphone: Segfault and crash with "error 4 in libc-2.28.so" on password entry
Am 13.04.19 um 14:30 schrieb Bernhard Übelacker: > Hello Alf, > > If you do not want to build yourself, I can send you the files > by mail (2.7MB). > > Kind regards, > Bernhard > Please be so kind and send me the binaries by mail to the reply address of this mail. I'll immediately test and report the results. Many thanks in advance, Alf
Bug#921266: linphone: Segfault and crash with "error 4 in libc-2.28.so" on password entry
Am 10.04.19 um 19:43 schrieb Bernhard Übelacker:
> Control: reassign 921266 libbellesip0 1.6.3-4
> Control: affects 921266 linphone
> Control: tags 921266 + upstream patch
> (gdb) list provider.c:1032,1050
> 1032
> 1033static void
> authorization_context_fill_from_auth(authorization_context_t*
> auth_context,belle_sip_header_www_authenticate_t*
> authenticate,belle_sip_uri_t *from_uri) {
> 1034
> authorization_context_set_realm(auth_context,belle_sip_header_www_authenticate_get_realm(authenticate));
> 1035 >>>>>>>>> if (auth_context->nonce &&
> strcmp(belle_sip_header_www_authenticate_get_nonce(authenticate),auth_context->nonce)!=0)
> {
> 1036/*new nonce, resetting nounce_count*/
> 1037auth_context->nonce_count=0;
> 1038}
>
Thanks for your help Bernhard!
I am prepared to test your patch as soon as I get a binary of the
patched lib.
I just got aware of another detail regarding Telekom/t-online:
Some time ago (1 - 2 years) the internet access has been switched to so
called "BNG" (broadband network gateway). With that the authentication
no longer needs a password, it is tied to "the pair of wires" = the
physical port on the DSL access multiplexer.
So a password is actually obsolete, every string or even none as a
password does allow registration. The only parameter needed is the phone
number which should be registered (I got 4). I tested with twinkle (in
Buster and Stretch) and linphone 3.6.1 in Stretch.
Kind regards,
Alf
Bug#926803: libfm-qt will not react to file changes in filesystems with no monitoring
Package: libfm-qt6 Version: 0.14.2~16-g2fc359a-2 Severity: important Tags: upstream This is esp. painful for smb and similar - not refreshing remote file systems after file operations in pcmanfm-qt and other dependend applications make a normal workflow impossible. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.7-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libfm-qt6 depends on: ii libc6 2.28-8 ii libexif12 0.6.21-5.1 ii libglib2.0-0 2.58.3-1 ii libglib2.0-bin2.58.3-1 ii libmenu-cache31.1.1~2-g583c190-1 ii libqt5core5a [qtbase-abi-5-11-3] 5.11.3+dfsg1-1 ii libqt5gui55.11.3+dfsg1-1 ii libqt5widgets55.11.3+dfsg1-1 ii libqt5x11extras5 5.11.3-2 ii libstdc++68.3.0-6 ii libxcb1 1.13.1-2 ii shared-mime-info 1.10-1 Versions of packages libfm-qt6 recommends: ii libfm-qt-l10n 0.14.2~16-g2fc359a-2 libfm-qt6 suggests no packages. -- no debconf information
Bug#921266: linphone: Segfault and crash with "error 4 in libc-2.28.so" on password entry
Am 09.04.19 um 23:27 schrieb Bernhard Übelacker: > Hello Alf, > thanks for the fast response. > You can query to which package a shared object belongs by: > > dpkg -S /usr/lib/x86_64-linux-gnu/libbellesip.so.0 > > That should show 'libbellesip0' I guess. > > So, if package libbellesip0-dbgsym gets installed, another > retry should have all needed debug information to show > for each line of the backtrace debug information. Wqas too late yesterday night, but here the result is coming in gdb_linphone_2019-04-10_11-07-23.log Hope this helps you to locate the root cause. Many thanks for the lesson how to collect the necessary information! Best regards, Alf Script started on 2019-04-10 11:07:23+02:00 [TERM="xterm-256color" TTY="/dev/pts/0" COLUMNS="165" LINES="28"] Reading symbols from linphonec...Reading symbols from /usr/lib/debug/.build-id/a6/e413996c0caf2689202302196ba19a26ce481f.debug...done. done. Starting program: /usr/bin/linphonec -d 5 -l linphone-debug [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe81ea700 (LWP 2922)] Ready Warning: video is disabled in linphonec, use -V or -C or -D to enable. [New Thread 0x7fffe79e9700 (LWP 2923)] linphonec> Refreshing on sip:061234567...@tel.t-online.de... linphonec> Registration on sip:tel.t-online.de failed: Unauthorized 11030230348 linphonec> Password for 061234567818 on tel.t-online.de: [top secret] Refreshing on sip:061234567...@tel.t-online.de... linphonec> Thread 1 "linphonec" received signal SIGSEGV, Segmentation fault. __strcmp_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:31 31 ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S: Datei oder Verzeichnis nicht gefunden. #0 __strcmp_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:31 #1 0x77a52782 in authorization_context_fill_from_auth (auth_context=auth_context@entry=0x55747df0, authenticate=authenticate@entry=0x55738e20, from_uri=from_uri@entry=0x55761e10) at ./src/provider.c:1035 #2 0x77a528aa in belle_sip_provider_update_or_create_auth_context (p=0x55739020, call_id=0x5574b280, authenticate=0x55738e20, from_uri=0x55761e10, realm=) at ./src/provider.c:1109 #3 0x77a53da7 in belle_sip_provider_dispatch_response (msg=0x557e8140, p=0x55739020) at ./src/provider.c:235 #4 belle_sip_provider_dispatch_message (prov=0x55739020, msg=0x557e8140) at ./src/provider.c:290 #5 0x77a34b9d in notify_incoming_messages (obj=0x5578fdd0) at ./src/channel.c:526 #6 belle_sip_channel_process_stream (obj=0x5578fdd0, eos=) at ./src/channel.c:632 #7 0x77a36a57 in belle_sip_channel_process_read_data (obj=0x5578fdd0) at ./src/channel.c:670 #8 belle_sip_channel_process_data (obj=obj@entry=0x5578fdd0, revents=revents@entry=1) at ./src/channel.c:695 #9 0x77a5c0de in on_udp_data (lp=0x55738530, events=1) at ./src/transports/udp_listeningpoint.c:195 #10 0x77a2a860 in belle_sip_main_loop_iterate (ml=0x557395c0) at ./src/belle_sip_loop.c:559 #11 belle_sip_main_loop_run (ml=0x557395c0) at ./src/belle_sip_loop.c:614 #12 0x77a2ab6c in belle_sip_main_loop_sleep (ml=0x557395c0, milliseconds=) at ./src/belle_sip_loop.c:626 #13 0x77a57df9 in belle_sip_stack_sleep (stack=, milliseconds=) at ./src/sipstack.c:221 #14 0x555b1cc2 in sal_iterate (sal=) at ./coreapi/bellesip_sal/sal_impl.c:838 #15 0x555eabc6 in linphone_core_iterate (lc=0x55693480) at ./coreapi/linphonecore.c:3194 #16 0x555a83db in linphonec_idle_call () at ./console/linphonec.c:1023 #17 0x555a858d in linphonec_readline (prompt=) at ./console/linphonec.c:543 #18 0x555a6dd8 in linphonec_main_loop (opm=) at /usr/include/x86_64-linux-gnu/bits/stdio2.h:64 #19 main (argc=, argv=) at ./console/linphonec.c:652 #0 __strcmp_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:31 No locals. #1 0x77a52782 in authorization_context_fill_from_auth (auth_context=auth_context@entry=0x55747df0, authenticate=authenticate@entry=0x55738e20, from_uri=from_uri@entry=0x55761e10) at ./src/provider.c:1035 No locals. #2 0x77a528aa in belle_sip_provider_update_or_create_auth_context (p=0x55739020, call_id=0x5574b280, authenticate=0x55738e20, from_uri=0x55761e10, realm=) at ./src/provider.c:1109 auth_context_lst = 0x5575ee40 auth_context = 0x55747df0 #3 0x77a53da7 in belle_sip_provider_dispatch_response (msg=0x557e8140, p=0x55739020) at ./src/provider.c:235 authorization = www_authenticate = 0x55738e20 authentication_info = 0x557d91e0 authorization_lst = 0x557d2670 from = req = call_id
Bug#921266: linphone: Segfault and crash with "error 4 in libc-2.28.so" on password entry
Am 09.04.19 um 21:51 schrieb Bernhard Übelacker: ... And here with the 3 debug packages for linphone installed, Alf Script started on 2019-04-09 23:13:10+02:00 [TERM="xterm-256color" TTY="/dev/pts/0" COLUMNS="119" LINES="28"] Reading symbols from linphonec...Reading symbols from /usr/lib/debug/.build-id/a6/e413996c0caf2689202302196ba19a26ce481f.debug...done. done. Starting program: /usr/bin/linphonec -d 5 -l linphone-debug [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe81ea700 (LWP 3303)] Ready Warning: video is disabled in linphonec, use -V or -C or -D to enable. [New Thread 0x7fffe79e9700 (LWP 3305)] linphonec> Refreshing on sip:061234567...@tel.t-online.de... linphonec> Registration on sip:tel.t-online.de failed: Unauthorized 11030230348 linphonec> Password for 061234567818 on tel.t-online.de: [top secret] Refreshing on sip:061234567...@tel.t-online.de... linphonec> Thread 1 "linphonec" received signal SIGSEGV, Segmentation fault. __strcmp_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:31 31 ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S: Datei oder Verzeichnis nicht gefunden. #0 __strcmp_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:31 #1 0x77a52782 in ?? () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 #2 0x77a528aa in ?? () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 #3 0x77a53da7 in belle_sip_provider_dispatch_message () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 #4 0x77a34b9d in ?? () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 #5 0x77a36a57 in belle_sip_channel_process_data () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 #6 0x77a5c0de in ?? () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 #7 0x77a2a860 in belle_sip_main_loop_run () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 #8 0x77a2ab6c in belle_sip_main_loop_sleep () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 #9 0x555b1cc2 in sal_iterate (sal=) at ./coreapi/bellesip_sal/sal_impl.c:838 #10 0x555eabc6 in linphone_core_iterate (lc=0x55693480) at ./coreapi/linphonecore.c:3194 #11 0x555a83db in linphonec_idle_call () at ./console/linphonec.c:1023 #12 0x555a858d in linphonec_readline (prompt=) at ./console/linphonec.c:543 #13 0x555a6dd8 in linphonec_main_loop (opm=) at /usr/include/x86_64-linux-gnu/bits/stdio2.h:64 #14 main (argc=, argv=) at ./console/linphonec.c:652 #0 __strcmp_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:31 No locals. #1 0x77a52782 in ?? () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 No symbol table info available. #2 0x77a528aa in ?? () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 No symbol table info available. #3 0x77a53da7 in belle_sip_provider_dispatch_message () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 No symbol table info available. #4 0x77a34b9d in ?? () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 No symbol table info available. #5 0x77a36a57 in belle_sip_channel_process_data () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 No symbol table info available. #6 0x77a5c0de in ?? () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 No symbol table info available. #7 0x77a2a860 in belle_sip_main_loop_run () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 No symbol table info available. #8 0x77a2ab6c in belle_sip_main_loop_sleep () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 No symbol table info available. #9 0x555b1cc2 in sal_iterate (sal=) at ./coreapi/bellesip_sal/sal_impl.c:838 No locals. #10 0x555eabc6 in linphone_core_iterate (lc=0x55693480) at ./coreapi/linphonecore.c:3194 calls = call = curtime_ms = elapsed = current_real_time = 1554844401 diff_time = one_second_elapsed = 0 '\000' remote_provisioning_uri = #11 0x555a83db in linphonec_idle_call () at ./console/linphonec.c:1023 opm = 0x55693480 #12 0x555a858d in linphonec_readline (prompt=) at ./console/linphonec.c:543 prompt_reader_started = 1 '\001' pipe_reader_started = 0 '\000' #13 0x555a6dd8 in linphonec_main_loop (opm=) at /usr/include/x86_64-linux-gnu/bits/stdio2.h:64 input = input = iptr = input_len = #14 main (argc=, argv=) at ./console/linphonec.c:652 No locals. Detaching from program: /usr/bin/linphonec, process 3299 [Inferior 1 (process 3299) detached] Script done on 2019-04-09 23:13:21+02:00 [COMMAND_EXIT_CODE="0"]
Bug#921266: linphone: Segfault and crash with "error 4 in libc-2.28.so" on password entry
Am 09.04.19 um 21:51 schrieb Bernhard Übelacker: > Hello Alf, > maybe we can get more context of this crash > by doing one of the following: > > - Install gdb and run linphone like this: > > script -c "gdb -q -ex 'set width 0' -ex 'set pagination off' -ex 'run' > -ex 'bt' -ex 'bt full' -ex 'detach' -ex 'quit' --args linphonec -d 5 -l > linphone-debug" -a gdb_linphone_$(date +%Y-%m-%d_%H-%M-%S).log > > The created file might contain a backtrace, that > could help here. > > - Install a core dump collector like > > - systemd-coredump: should output a backtrace > without debug symbol information right into > the journal. > > Alternatively one could list the crashes happend > since this boot by: > >coredumpctl list > > And attach get a backtrace from gdb from this by: > >coredumpctl gdb > bt > bt full > quit > > - corekeeper: should also collect core dumps which > could be inspected by: > > gdb -q $(which linphonec) --core /var/crash/user/coredump >bt >bt full >quit > > All the ways might be improved by installing > the debug information packages described in [1], > e.g. linphone-nogtk-dbgsym. > Adding these packages for the shared libraries, > shown in the backtrace, helps further. > > Kind regards, > Bernhard > > [1] > https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols > Hi Bernhard, I performed the first proposal and got some 4kb of output. I did not find any debug symbols for linphone yet in the standard repositories, so there ar some complaints. I did alter the phone number (2 places) and of course substituted my paaswrd. I do attach the output here, please advise whether I should try your other proposals and/or install required debug symbols. Kind regards, Alf Script started on 2019-04-09 22:35:58+02:00 [TERM="xterm-256color" TTY="/dev/pts/0" COLUMNS="184" LINES="20"] Reading symbols from linphonec...(no debugging symbols found)...done. Starting program: /usr/bin/linphonec -d 5 -l linphone-debug [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe81ea700 (LWP 2000)] Ready Warning: video is disabled in linphonec, use -V or -C or -D to enable. [New Thread 0x7fffe79e9700 (LWP 2001)] linphonec> Refreshing on sip:061234567...@tel.t-online.de... linphonec> Registration on sip:tel.t-online.de failed: Unauthorized 11030230348 linphonec> Password for 061234567818 on tel.t-online.de: [top secret] Refreshing on sip:061234567...@tel.t-online.de... linphonec> Thread 1 "linphonec" received signal SIGSEGV, Segmentation fault. __strcmp_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:31 31 ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S: Datei oder Verzeichnis nicht gefunden. #0 __strcmp_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:31 #1 0x77a52782 in ?? () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 #2 0x77a528aa in ?? () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 #3 0x77a53da7 in belle_sip_provider_dispatch_message () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 #4 0x77a34b9d in ?? () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 #5 0x77a36a57 in belle_sip_channel_process_data () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 #6 0x77a5c0de in ?? () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 #7 0x77a2a860 in belle_sip_main_loop_run () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 #8 0x77a2ab6c in belle_sip_main_loop_sleep () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 #9 0x555b1cc2 in sal_iterate () #10 0x555eabc6 in linphone_core_iterate () #11 0x555a83db in ?? () #12 0x555a858d in linphonec_readline () #13 0x555a6dd8 in main () #0 __strcmp_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:31 No locals. #1 0x77a52782 in ?? () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 No symbol table info available. #2 0x77a528aa in ?? () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 No symbol table info available. #3 0x77a53da7 in belle_sip_provider_dispatch_message () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 No symbol table info available. #4 0x77a34b9d in ?? () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 No symbol table info available. #5 0x77a36a57 in belle_sip_channel_process_data () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 No symbol table info available. #6 0x77a5c0de in ?? () from /usr/lib/x86_64-linux-gnu/libbellesip.so.0 No symbol table info available.
Bug#921266: The segfault Is defintely not caused by t-online, but linpone
Am 09.04.19 um 16:20 schrieb Jonas Smedegaard: > Quoting Alf (2019-04-08 22:08:27) >> I have done further tests and finally given up to get linphone working >> as a SIP client here - the segfault on password enty is absolutely >> reproducible. >> >> To solve this issue I have tried "twinkle" (another SIP client from >> Buster-repo and that was set up within a few minutes. >> Just entered the SIP and STUN servers and my credentials for my >> t-online account - and all works as expected. >> >> This definitely confirms that it is not related to t-online, nor to >> some missconfiguration of my system. >> >> Moreover such a segfault is caused by severe bugs in the application >> itself. Again the syslog message: >> >> tux kernel: [ 4866.131680] linphone[6107]: segfault at 0 ip >> 003153a8f37a sp 7ffe572604c8 error 4 in >> libc-2.24.so[3153a0+194000] >> Mar 3 18:17:33 tux kernel: [ 4866.131690] Code: 89 e6 5b 4c 89 ef 5d 41 >> 5c 41 5d e9 e0 49 ff ff 89 f8 31 d2 66 0f ef ff 09 f0 25 ff 0f 00 00 3d >> c0 0f 00 00 0f 8f 78 02 00 00 0f 6f 0f f3 0f 6f 06 66 0f 74 c1 66 >> 0f da c1 66 0f ef c9 66 0f >> >> of which the tail is always the same: >> - >> ... 89 f8 31 d2 66 0f ef ff 09 f0 25 ff 0f 00 00 3d c0 0f 00 00 0f 8f 78 >> 02 00 00 0f 6f 0f f3 0f 6f 06 66 0f 74 c1 66 0f da c1 66 0f ef c9 66 0f >> >> There is also no means to gather more info about the crash in libc6 >> besides the syslog entry. Linphone's debug output. >> Even at highest level does not disclose anything valuable for me. >> >> So linphone 3.12 from Buster is buggy and absolutely unusable for me, >> severity should be set back to 'serious' to reflect that. > > Above crash involves libc-2.24 which is not Buster, so it seems you test > in some mixture of stable and testing system. > > Probably helpful to know which official Debian package repository you > primarily use, and which packages deviate from that - in any way, > including held packages and packages from deb-multimedia.org. > > Please also mention code included by other means than official Debian > packages - e.g. self-compiled kernel, flatpak... > > > - Jonas > Sorry, don't know how that happened - shame on me. Of course Buster has: ii libc6:amd642.28-8 amd64GNU C Library: Shared libraries Here the segfault message generated a few minutes ago in Buster. You can see, also here the tail is identical Apr 9 17:54:37 tux kernel: [ 203.438238] linphonec[1581]: segfault at 0 ip 7fd44a1ecc7a sp 7ffcb9a79018 error 4 in libc-2.28.so[7fd44a17e000+148000] Apr 9 17:54:37 tux kernel: [ 203.438248] Code: 0f b6 0e 0f b6 07 29 c8 c3 0f 1f 80 00 00 00 00 89 f8 31 d2 66 0f ef ff 09 f0 25 ff 0f 00 00 3d c0 0f 00 00 0f 8f 78 02 00 00 0f 6f 0f f3 0f 6f 06 66 0f 74 c1 66 0f da c1 66 0f ef c9 66 0f
Bug#921266: The segfault Is defintely not caused by t-online, but linpone
Am 09.04.19 um 14:54 schrieb W. Martin Borgert: > Quoting Alf : >> This definitely confirms that it is not related to t-online, nor to some >> missconfiguration of my system. > > Still, it would be interesting what leads to that behaviour. > I use Linphone as my one and only telephone and it works fine > for me on both a stretch and a buster system, both amd64. No > crashes at all. I use different providers, however. > I found (hopefully) an explanation how authentication at t-online should work. See this URL: https://andrewjprokop.wordpress.com/2015/01/27/understanding-sip-authentication/ If you have a look at my debug output some posts above you see that for registration the client contacts the server. The server responds with: SIP/2.0 401 Unauthorized 11030230348 and next it sends the nonce WWW-Authenticate: Digest realm="tel.t-online.de",nonce="415F6A393573AB5CED81AB3F",stale=true,algorithm=MD5,qop="auth" and so on until registration is complete This cycle is run twice with linphone 3.6.1 until registration is complete. It can be seen in the debug output id you search for the string "Authentication-Info: qop=auth" Linphone 3.12.0 only runs this cycle once and then crashing at following output: Authentication-Info: qop=auth,rspauth="3f09707f2c9d40af03c39831078ffc75",cnonce="zJy0v3v2zDA0WMNm",nc=0001 2019-04-08 18:13:30:008 ortp-message-channel [0x55623f893e60] [722] bytes parsed 2019-04-08 18:13:30:008 ortp-message-Found transaction matching response. 2019-04-08 18:13:30:008 ortp-message-Updating auth context for ream [tel.t-online.de] next nonce is going to be [(null)] crash! It for sure has nothing to do with the GUI, all debug output was collected using CLI vith option "-d 5". One final thought: Ubuntu/Canonical has choosen linphone 3.6.1 for the upcoming release 1904 (Disco Dingo) instead of 3.12 - maybe they have a reason for that decision, expecially as they genally aim for latest available version?
Bug#926683: unblock: libfm-qt/0.14.1-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libfm-qt
New version fixes grave bug #926626 libfm-qt6: Cannot copy dirs over smb
Solution: Added upstream patch
>From 6cb5f38d2c1261b782b16da45bb323b069db94fe Mon Sep 17 00:00:00 2001
From: Tsu Jan
Date: Mon, 8 Apr 2019 07:13:09 +0430
Subject: [PATCH] Fixed SMB recursive copy
Fixes https://github.com/lxqt/libfm-qt/issues/385 by trying to set dir
permissions only once and ignoring possible errors (that happen with SMB and,
maybe, other protocols).
---
src/core/filetransferjob.cpp | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/src/core/filetransferjob.cpp b/src/core/filetransferjob.cpp
index 4039c58..6b44576 100644
--- a/src/core/filetransferjob.cpp
+++ b/src/core/filetransferjob.cpp
@@ -279,16 +279,17 @@ bool FileTransferJob::makeDir(const FilePath& srcPath,
GFileInfoPtr srcInfo, Fil
mode,
G_FILE_QUERY_INFO_NOFOLLOW_SYMLINKS,
cancellable().get(),
);
if(!chmod_done) {
-ErrorAction act = emitError(err, ErrorSeverity::MODERATE);
+/* NOTE: Some filesystems may not support this. So, ignore
errors for now. */
+break;
+/*ErrorAction act = emitError(err,
ErrorSeverity::MODERATE);
if(act != ErrorAction::RETRY) {
break;
-}
-/* FIXME: some filesystems may not support this. */
+}*/
}
} while(!chmod_done && !isCancelled());
}
}
-return mkdir_done && chmod_done;
+return mkdir_done/* && chmod_done*/;
}
bool FileTransferJob::handleError(GErrorPtr , const FilePath ,
const GFileInfoPtr , FilePath , int& flags) {
Thanks Alf
unblock libfm-qt/0.14.1-4
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.0.7-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Bug#921266: The segfault Is defintely not caused by t-online, but linpone
I have done further tests and finally given up to get linphone working as a SIP client here - the segfault on password enty is absolutely reproducible. To solve this issue I have tried "twinkle" (another SIP client from Buster-repo and that was set up within a few minutes. Just entered the SIP and STUN servers and my credentials for my t-online account - and all works as expected. This definitely confirms that it is not related to t-online, nor to some missconfiguration of my system. Moreover such a segfault is caused by severe bugs in the application itself. Again the syslog message: tux kernel: [ 4866.131680] linphone[6107]: segfault at 0 ip 003153a8f37a sp 7ffe572604c8 error 4 in libc-2.24.so[3153a0+194000] Mar 3 18:17:33 tux kernel: [ 4866.131690] Code: 89 e6 5b 4c 89 ef 5d 41 5c 41 5d e9 e0 49 ff ff 89 f8 31 d2 66 0f ef ff 09 f0 25 ff 0f 00 00 3d c0 0f 00 00 0f 8f 78 02 00 00 0f 6f 0f f3 0f 6f 06 66 0f 74 c1 66 0f da c1 66 0f ef c9 66 0f of which the tail is always the same: - ... 89 f8 31 d2 66 0f ef ff 09 f0 25 ff 0f 00 00 3d c0 0f 00 00 0f 8f 78 02 00 00 0f 6f 0f f3 0f 6f 06 66 0f 74 c1 66 0f da c1 66 0f ef c9 66 0f There is also no means to gather more info about the crash in libc6 besides the syslog entry. Linphone's debug output. Even at highest level does not disclose anything valuable for me. So linphone 3.12 from Buster is buggy and absolutely unusable for me, severity should be set back to 'serious' to reflect that.
Bug#926513: unblock: fswatch/1.14.0+repack-7
Diff for unblocking diff -uar diff/fswatch-1.14.0+repack/debian/changelog fswatch/debian/changelog --- diff/fswatch-1.14.0+repack/debian/changelog 2018-12-29 12:44:58.0 +0100 +++ fswatch/debian/changelog 2019-04-06 13:13:34.950903659 +0200 @@ -1,3 +1,38 @@ +fswatch (1.14.0+repack-7) unstable; urgency=medium + + * Fixed the last remaning symbols for armel, powerpcspe and riscv64 + * Cleaned up the Files-Excluded entries (Closes: #910330) + * Bumped year in debian/copyright + + -- Alf Gaida Sat, 06 Apr 2019 13:13:27 +0200 + +fswatch (1.14.0+repack-6) unstable; urgency=medium + + * Added last missed symbol + + -- Alf Gaida Fri, 05 Apr 2019 23:39:43 +0200 + +fswatch (1.14.0+repack-5) unstable; urgency=medium + + * Fixed some symbols, compiler changes are fun. + + -- Alf Gaida Thu, 04 Apr 2019 21:30:19 +0200 + +fswatch (1.14.0+repack-4) unstable; urgency=medium + + * Fixed the remaining symbols + * Bumped Standards to 4.3.0, no changes needed + * Switched to debhelper-compat (= 12) + * Removed debian/compat + + -- Alf Gaida Sun, 03 Mar 2019 22:08:40 +0100 + +fswatch (1.14.0+repack-3) unstable; urgency=medium + + * next round of mangling symbols + + -- Alf Gaida Sat, 23 Feb 2019 12:41:09 +0100 + fswatch (1.14.0+repack-2) unstable; urgency=medium * Fixed missed optional symbols. Nur in diff/fswatch-1.14.0+repack/debian: compat. diff -uar diff/fswatch-1.14.0+repack/debian/control fswatch/debian/control --- diff/fswatch-1.14.0+repack/debian/control 2018-12-28 21:25:15.0 +0100 +++ fswatch/debian/control 2019-03-03 22:07:52.199170099 +0100 @@ -2,12 +2,12 @@ Maintainer: Alf Gaida Section: misc Priority: optional -Build-Depends: debhelper (>= 11~), +Build-Depends: debhelper-compat (= 12), doxygen, libtool, linux-libc-dev, texinfo -Standards-Version: 4.2.1 +Standards-Version: 4.3.0 Vcs-Browser: https://salsa.debian.org/debian/fswatch Vcs-Git: https://salsa.debian.org/debian/fswatch.git Homepage: http://emcrisostomo.github.io/fswatch diff -uar diff/fswatch-1.14.0+repack/debian/copyright fswatch/debian/copyright --- diff/fswatch-1.14.0+repack/debian/copyright 2018-12-28 21:27:56.0 +0100 +++ fswatch/debian/copyright 2019-04-06 13:12:25.350153383 +0200 @@ -104,7 +104,7 @@ License: FSFAP Files: debian/* -Copyright: 2016-2018 Alf Gaida +Copyright: 2016-2019 Alf Gaida License: GPL-3+ License: FSFAP Nur in fswatch/debian: files. Nur in fswatch/debian: .gitignore. diff -uar diff/fswatch-1.14.0+repack/debian/libfswatch11.symbols fswatch/debian/libfswatch11.symbols --- diff/fswatch-1.14.0+repack/debian/libfswatch11.symbols 2018-12-29 12:43:26.0 +0100 +++ fswatch/debian/libfswatch11.symbols 2019-04-06 13:05:04.459790841 +0200 @@ -144,14 +144,14 @@ (optional|c++|arch= !armel !armhf !i386 !mips !mipsel !hppa !m68k !powerpc !powerpcspe !sh4 !x32 )"std::_Hashtable, std::__detail::_Identity, std::equal_to, std::hash, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_erase(unsigned long, std::__detail::_Hash_node_base*, std::__detail::_Hash_node*)@Base" 1.9.3 (optional|c++|arch= armel armhf i386 mips mipsel hppa m68k powerpc powerpcspe sh4 x32 )"std::_Hashtable, std::__detail::_Identity, std::equal_to, std::hash, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_erase(unsigned int, std::__detail::_Hash_node_base*, std::__detail::_Hash_node*)@Base" 1.9.3 (optional|c++|arch= !armel !armhf !i386 !mips !mipsel !hppa !ia64 !m68k !powerpc !powerpcspe !sh4 !x32 )"std::_Hashtable, std::__detail::_Identity, std::equal_to, std::hash, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_insert_unique_node(unsigned long, unsigned long, std::__detail::_Hash_node*, unsigned long)@Base" 1.12.0 - (optional|c++|arch= armel armhf i386 mips mipsel hppa m68k powerpc sh4 x32 )"std::_Hashtable, std::__detail::_Identity, std::equal_to, std::hash, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_insert_unique_node(unsigned int, unsigned int, std::__detail::_Hash_node*, unsigned int)@Base" 1.12.0 + (optional|c++|arch= armel armhf i386 mips mipsel hppa m68k powerpc powerpcspe sh4 x32 )"std::_Hashtable, std::__detail::_Identity, std::equal_to, std::hash, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_insert_unique_node(unsigned int, unsigned int, std::__detail::_Hash_node*, unsigned int)@Base" 1.12.0 (optional|c++|arch= !armel !armhf !i386 !mips !mipsel !hppa !
Bug#926513: unblock: fswatch/1.14.0+repack-7
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package fswatch Reason: Symbols reworked after compiler change. Additional bumped Standards and switched to debhelper-compat. unblock fswatch/1.14.0+repack-7 -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.6-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#925364: unblock: featherpad/0.9.4-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package featherpad The new version fixes three bugs: * #925361 - Don't toggle the insert mode with modifier * #925362 - Save button is disabled when it shouldn't * #923687 - Add qttranslations5-l10n as recommend unfortunately i was to fast with fixing #923687 (not thought about freeze start and let the faulty package migrate before uploading) so 0.9.4 did not migrate to testing in time. It would be really nice to have 0.9.4 in buster - beside the mentiond changes there are some translation updates. If not possible it have to split out the fixes for 925361 and 925362 and patch 0.9.3. It would be nice if i can save that time. featherpad is not a dependency for everything, but the considered main editor in LXQt. Cheers Alf unblock featherpad/0.9.4-2 -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.3-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#925362: Save button is disabled when it shouldn't
Package: featherpad Version: 0.9.4-2 Severity: important Reported upstream: https://github.com/tsujan/FeatherPad/issues/251 At least important, if not serious - most of the day i really want to save my changes to a file. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.3-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages featherpad depends on: ii libc62.28-8 ii libgcc1 1:8.3.0-3 ii libqt5core5a 5.11.3+dfsg1-1 ii libqt5gui5 5.11.3+dfsg1-1 ii libqt5network5 5.11.3+dfsg1-1 ii libqt5printsupport5 5.11.3+dfsg1-1 ii libqt5svg5 5.11.3-2 ii libqt5widgets5 5.11.3+dfsg1-1 ii libqt5x11extras5 5.11.3-2 ii libstdc++6 8.3.0-3 ii libx11-6 2:1.6.7-1 Versions of packages featherpad recommends: ii libglib2.0-bin2.58.3-1 ii qttranslations5-l10n 5.11.3-2 featherpad suggests no packages. -- no debconf information
Bug#925361: Don't toggle the insert mode with modifier
Package: featherpad Version: 0.9.4-2 Severity: important Bug reported upstream: https://github.com/tsujan/FeatherPad/issues/247 Can and will break workflows without sane reason, fixed upstream. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.0.3-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages featherpad depends on: ii libc62.28-8 ii libgcc1 1:8.3.0-3 ii libqt5core5a 5.11.3+dfsg1-1 ii libqt5gui5 5.11.3+dfsg1-1 ii libqt5network5 5.11.3+dfsg1-1 ii libqt5printsupport5 5.11.3+dfsg1-1 ii libqt5svg5 5.11.3-2 ii libqt5widgets5 5.11.3+dfsg1-1 ii libqt5x11extras5 5.11.3-2 ii libstdc++6 8.3.0-3 ii libx11-6 2:1.6.7-1 Versions of packages featherpad recommends: ii libglib2.0-bin2.58.3-1 ii qttranslations5-l10n 5.11.3-2 featherpad suggests no packages. -- no debconf information
Bug#925352: unblock: lxqt-config/0.14.1-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package lxqt-config
there was a regression with keyboard layout shortcut handling that make using
different keyboard layouts/models hard for people who need this functionality.
Source diff:
diff --git a/debian/changelog b/debian/changelog
index 712d526..eec2f8b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+lxqt-config (0.14.1-2) unstable; urgency=medium
+
+ * Fixed keyboard layout switch shortcut (Closes: #925346)
+
+ -- Alf Gaida Sat, 23 Mar 2019 15:40:43 +0100
+
lxqt-config (0.14.1-1) unstable; urgency=medium
* Cherry-picking new upstream version 0.14.1.
diff --git a/debian/patches/fix-keybord-layout-shortcut.patch
b/debian/patches/fix-keybord-layout-shortcut.patch
new file mode 100644
index 000..d94ce4c
--- /dev/null
+++ b/debian/patches/fix-keybord-layout-shortcut.patch
@@ -0,0 +1,32 @@
+From dfe9a2b27aab40262b9186672fad480a406d5c4a Mon Sep 17 00:00:00 2001
+From: Tsu Jan
+Date: Fri, 22 Mar 2019 19:55:32 +0430
+Subject: [PATCH] Fixed changing keyboard layout switch shortcut and model
+
+Fixes https://github.com/lxqt/lxqt-config/issues/445
+---
+ lxqt-config-input/keyboardlayoutconfig.cpp | 10 --
+ 1 file changed, 8 insertions(+), 2 deletions(-)
+
+diff --git a/lxqt-config-input/keyboardlayoutconfig.cpp
b/lxqt-config-input/keyboardlayoutconfig.cpp
+index f5a7f24..bc6c369 100644
+--- a/lxqt-config-input/keyboardlayoutconfig.cpp
b/lxqt-config-input/keyboardlayoutconfig.cpp
+@@ -40,8 +40,14 @@ KeyboardLayoutConfig::KeyboardLayoutConfig(LXQt::Settings*
_settings, QWidget* p
+ connect(ui.removeLayout, ::clicked, this,
::onRemoveLayout);
+ connect(ui.moveUp, ::clicked, this,
::onMoveUp);
+ connect(ui.moveDown, ::clicked, this,
::onMoveDown);
+- connect(ui.keyboardModel, QOverload::of(::activated), this,
::settingsChanged);
+- connect(ui.switchKey, QOverload::of(::activated), this,
::settingsChanged);
++ connect(ui.keyboardModel, QOverload::of(::activated),
[this](int /*index*/) {
++applyConfig_ = true;
++Q_EMIT settingsChanged();
++ });
++ connect(ui.switchKey, QOverload::of(::activated), [this](int
/*index*/) {
++applyConfig_ = true;
++Q_EMIT settingsChanged();
++ });
+ }
+
+ KeyboardLayoutConfig::~KeyboardLayoutConfig() {
+
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..006086d
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+fix-keybord-layout-shortcut.patch
unblock lxqt-config/0.14.1-2
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.0.3-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
