Bug#1071377: chkrootkit: File name including a quote mark throws script off

[Shai Berger]

Package: chkrootkit
Version: 0.58b-1+b3
Severity: normal

Dear Maintainer,

In Hebrew, the double quote mark can sometimes be used
to mark an acronym. In this role, it can make its way
into file names.

This morning, when chkrootkit made its daily run, I had
in /tmp a file named: 'חברת חשמל לישראל בע"מ - חשבון דו חודשי.pdf'
(the single quote marks on the edges are not part of the name, but
the double quote mark in the middle is)

This caused this output from the script:

"""
Searching for suspect PHP files...  /usr/bin/head: 
cannot open '/tmp/חברת חשמל לישראל בעמ' for reading: No such file or directory
/usr/bin/head: cannot open 'חשבון' for reading: No such file or directory
/usr/bin/head: cannot open 'דו' for reading: No such file or directory
/usr/bin/head: cannot open 'חודשי.pdf 2>/dev/null | /usr/bin/grep -q ^#!.*php 
&& echo /tmp/חברת' for reading: No such file or directory
/usr/bin/head: cannot open 'חשמל' for reading: No such file or directory
/usr/bin/head: cannot open 'לישראל' for reading: No such file or directory
/usr/bin/head: cannot open 'בעמ - חשבון דו חודשי.pdf' for reading: No such file 
or directory
WARNING

WARNING: The following suspicious PHP files were found:
==> standard input <==  
"""

Thanks,
Shai.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_IL.UTF-8, LC_CTYPE=en_IL.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chkrootkit depends on:
ii  libc6  2.38-10

Versions of packages chkrootkit recommends:
ii  anacron2.3-40
ii  binutils   2.42-4
ii  cron [cron-daemon] 3.0pl1-189
ii  exim4-daemon-light [mail-transport-agent]  4.97-8
ii  iproute2   6.8.0-1
ii  mailutils [mailx]  1:3.17-1.1+b2
ii  procps 2:4.0.4-4
ii  systemd-sysv   255.5-1

chkrootkit suggests no packages.

-- Configuration Files:
/etc/chkrootkit/chkrootkit.ignore changed:
/usr/lib/ruby/vendor_ruby/rubygems/tsort/.document
/usr/lib/ruby/vendor_ruby/rubygems/optparse/.document
/usr/lib/ruby/vendor_ruby/rubygems/ssl_certs/.document
/usr/lib/ruby/gems/3.1.0/gems/typeprof-0.21.2/vscode/.vscode
/usr/lib/ruby/gems/3.1.0/gems/typeprof-0.21.2/vscode/.gitignore
/usr/lib/ruby/gems/3.1.0/gems/typeprof-0.21.2/vscode/.vscodeignore
/usr/lib/jvm/.java-1.17.0-openjdk-amd64.jinfo
/usr/lib/libreoffice/share/.registry
/usr/lib/python3/dist-packages/matplotlib/backends/web_backend/.eslintrc.js
/usr/lib/python3/dist-packages/matplotlib/backends/web_backend/.prettierignore
/usr/lib/python3/dist-packages/matplotlib/backends/web_backend/.prettierrc
/usr/lib/python3/dist-packages/matplotlib/tests/tinypages/.gitignore
/usr/lib/python3/dist-packages/matplotlib/tests/tinypages/_static/.gitignore
/usr/lib/python3/dist-packages/matplotlib/tests/baseline_images/.keep
/usr/lib/python3/dist-packages/numpy/f2py/tests/src/assumed_shape/.f2py_f2cmap
/usr/lib/python3/dist-packages/numpy/f2py/tests/src/f2cmap/.f2py_f2cmap
/usr/lib/python3/dist-packages/numpy/core/include/numpy/.doxyfile


-- no debconf information

Bug#1050656: libqt5gui5: This was local to my system only

[Shai Berger]

Package: libqt5gui5
Followup-For: Bug #1050656

Dear Maintainer,

Looking again at some tracebacks and coredumps, I realized the
problem was really with libjpeg62-turbo -- but that didn't make
sense to me, as that library hasn't changed in a long time.

Except, apparently, on my system, it has.

Reinstalling it solved the problem.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-4-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_IL.UTF-8, LC_CTYPE=en_IL.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libqt5gui5 depends on:
ii  fontconfig 2.14.2-6
ii  libc6  2.37-12
ii  libdrm22.4.117-1
ii  libegl11.7.0-1
ii  libfontconfig1 2.14.2-6
ii  libfreetype6   2.13.2+dfsg-1
ii  libgbm123.2.1-1
ii  libgcc-s1  13.2.0-5
ii  libgl1 1.7.0-1
ii  libglib2.0-0   2.78.1-2
ii  libharfbuzz0b  8.0.1-1
ii  libice62:1.0.10-1
ii  libinput10 1.23.0-2
ii  libjpeg62-turbo1:2.1.5-2
ii  libmd4c0   0.4.8-1
ii  libmtdev1  1.1.6-1
ii  libpng16-161.6.40-2
ii  libqt5core5a [qtbase-abi-5-15-10]  5.15.10+dfsg-4
ii  libqt5dbus55.15.10+dfsg-4
ii  libqt5network5 5.15.10+dfsg-4
ii  libsm6 2:1.2.3-1
ii  libstdc++6 13.2.0-5
ii  libudev1   254.5-1
ii  libx11-6   2:1.8.7-1
ii  libx11-xcb12:1.8.7-1
ii  libxcb-glx01.15-1
ii  libxcb-icccm4  0.4.1-1.1
ii  libxcb-image0  0.4.0-2
ii  libxcb-keysyms10.4.0-1+b2
ii  libxcb-randr0  1.15-1
ii  libxcb-render-util00.3.9-1+b1
ii  libxcb-render0 1.15-1
ii  libxcb-shape0  1.15-1
ii  libxcb-shm01.15-1
ii  libxcb-sync1   1.15-1
ii  libxcb-xfixes0 1.15-1
ii  libxcb-xinerama0   1.15-1
ii  libxcb-xinput0 1.15-1
ii  libxcb-xkb11.15-1
ii  libxcb11.15-1
ii  libxkbcommon-x11-0 1.6.0-1
ii  libxkbcommon0  1.6.0-1
ii  libxrender11:0.9.10-1.1
ii  zlib1g 1:1.2.13.dfsg-3

Versions of packages libqt5gui5 recommends:
ii  libqt5svg5 5.15.10-2
ii  qt5-gtk-platformtheme  5.15.10+dfsg-4
ii  qtwayland5 5.15.10-2

Versions of packages libqt5gui5 suggests:
pn  qgnomeplatform-qt5 
ii  qt5-image-formats-plugins  5.15.10-2

-- no debconf information

Bug#1050656: telegram-desktop: Problem is actually in Qt

[Shai Berger]

Package: telegram-desktop
Version: 4.10.3+ds-1+b1
Followup-For: Bug #1050656
Control: reassign -1 libqt5gui5 5.15.10+dfsg-4
Control: retitle -1 Bus error when trying to write jpeg images images

Dear Maintainer,

I've run into similar crashes with similar tracebacks in
KDE applications not related to Telegram, whenever one
tries to write a JPEG image to disk. Therefore, I don't
believe the issue to be with Telegram.

The problem was detected in testing, with
libqt5gui5=5.15.10+dfsg-3 and probably previous
versions; I installed the latest in unstable to see
if it fixes it. It doesn't.

-- Package-specific info:

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_IL.UTF-8, LC_CTYPE=en_IL.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages telegram-desktop depends on:
ii  libabsl20220623  20220623.1-3
ii  libavcodec-extra60 [libavcodec60]7:6.0-7+b1
ii  libavfilter-extra9 [libavfilter9]7:6.0-7+b1
ii  libavformat-extra60 [libavformat60]  7:6.0-7+b1
ii  libavutil58  7:6.0-7+b1
ii  libc62.37-12
ii  libgcc-s113.2.0-5
ii  libglib2.0-0 2.78.0-2
ii  libglibmm-2.68-1 2.78.0-1
ii  libhunspell-1.7-01.7.2+really1.7.2-10
ii  libjpeg62-turbo  1:2.1.5-2
ii  libkf5coreaddons55.107.0-1
ii  liblz4-1 1.9.4-1
ii  libminizip1  1:1.2.13.dfsg-3
ii  libopenal1   1:1.23.1-4
ii  libopus0 1.4-1
ii  libqrcodegencpp1 1.8.0-1.2
ii  libqt5core5a [qtbase-abi-5-15-10]5.15.10+dfsg-3
ii  libqt5gui5   5.15.10+dfsg-4
ii  libqt5network5   5.15.10+dfsg-3
ii  libqt5qml5   5.15.10+dfsg-2
ii  libqt5quick5 5.15.10+dfsg-2
ii  libqt5quickwidgets5  5.15.10+dfsg-2
ii  libqt5svg5   5.15.10-2
ii  libqt5waylandcompositor5 5.15.10-2
ii  libqt5widgets5   5.15.10+dfsg-3
ii  librlottie0-10.1+dfsg-4
ii  libsigc++-3.0-0  3.4.0-7
ii  libsrtp2-1   2.5.0-3
ii  libssl3  3.0.11-1
ii  libstdc++6   13.2.0-5
ii  libswresample4   7:6.0-7+b1
ii  libswscale7  7:6.0-7+b1
ii  libvpx8  1.13.1-2
ii  libx11-6 2:1.8.7-1
ii  libxcb-keysyms1  0.4.0-1+b2
ii  libxcb-record0   1.15-1
ii  libxcb-screensaver0  1.15-1
ii  libxcb1  1.15-1
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.6-1
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxrandr2   2:1.5.2-2+b1
ii  libxtst6 2:1.2.3-1.1
ii  libxxhash0   0.8.2-2
ii  libyuv0  0.0~git20230907.cbfb661-1
ii  qt5-image-formats-plugins5.15.10-2
ii  zlib1g   1:1.2.13.dfsg-3

Versions of packages telegram-desktop recommends:
ii  fonts-open-sans   1.11-2
ii  libwebkit2gtk-4.0-37  2.42.1-2+b1
ii  libwebkit2gtk-4.1-0   2.42.1-2+b1

telegram-desktop suggests no packages.

Versions of packages telegram-desktop is related to:
ii  xdg-desktop-portal   1.18.0-1
ii  xdg-desktop-portal-gtk [xdg-desktop-portal-backend]  1.14.1-1
ii  xdg-desktop-portal-kde [xdg-desktop-portal-backend]  5.27.8-1

-- no debconf information
[2023.10.29 17:56:46] Launched version: 4010003, install beta: [FALSE], alpha: 
0, debug mode: [FALSE]
[2023.10.29 17:56:46] Executable dir: /usr/bin/, name: telegram-desktop
[2023.10.29 17:56:46] Initial working dir: /home/shai/
[2023.10.29 17:56:46] Working dir: /home/shai/.local/share/TelegramDesktop/
[2023.10.29 17:56:46] Command line: /usr/bin/telegram-desktop --
[2023.10.29 17:56:46] Executable path before check: /usr/bin/telegram-desktop
[2023.10.29 17:56:46] Logs started
[2023.10.29 17:56:46] Launcher filename: org.telegram.desktop.desktop
[2023.10.29 17:56:46] We use allocator from /lib/x86_64-linux-gnu/libc.so.6
[2023.10.29 17:56:46] Connecting local socket to 
/tmp/735a4fdec5600e9bc6df96b79a9689ee-{87A94AB0-E370-4cde-98D3-ACC110C5967D}...
[2023.10.29 17:56:46] Socket connect error 0, starting server and app...
[2023.10.29 17:56:46] Moved logging from 

Bug#1050656: telegram-desktop: Bus Error whenever a channel has a video

[Shai Berger]

Package: telegram-desktop
Version: 4.9.7+ds-1
Followup-For: Bug #1050656

Dear Maintainer,

I suspected this bug was caused by having on my system some mixed
versions (I have some packages from unstable).

So I checked for any relevant packages which are not from testing:

$ aptitude versions --group-by=none ~Rtelegram-desktop | grep ^i | grep -v 
testing

I found packages which needed updating, and packages which needed
removing, but after all of that -- the output of the above command
is now empty -- and a reboot, the problem remains.

-- Package-specific info:

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_IL.UTF-8, LC_CTYPE=en_IL.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages telegram-desktop depends on:
ii  libabsl20220623  20220623.1-3
ii  libavcodec-extra60 [libavcodec60]7:6.0-7
ii  libavfilter-extra9 [libavfilter9]7:6.0-7
ii  libavformat-extra60 [libavformat60]  7:6.0-7
ii  libavutil58  7:6.0-7
ii  libc62.37-12
ii  libgcc-s113.2.0-4
ii  libglib2.0-0 2.78.0-2
ii  libglibmm-2.68-1 2.78.0-1
ii  libhunspell-1.7-01.7.2+really1.7.2-10
ii  libjpeg62-turbo  1:2.1.5-2
ii  libkf5coreaddons55.107.0-1
ii  liblz4-1 1.9.4-1
ii  libminizip1  1:1.2.13.dfsg-3
ii  libopenal1   1:1.23.1-4
ii  libopus0 1.4-1
ii  libqrcodegencpp1 1.8.0-1.2
ii  libqt5core5a [qtbase-abi-5-15-10]5.15.10+dfsg-3
ii  libqt5gui5   5.15.10+dfsg-3
ii  libqt5network5   5.15.10+dfsg-3
ii  libqt5svg5   5.15.10-2
ii  libqt5widgets5   5.15.10+dfsg-3
ii  librlottie0-10.1+dfsg-4
ii  libsigc++-3.0-0  3.4.0-7
ii  libsrtp2-1   2.5.0-3
ii  libssl3  3.0.11-1
ii  libstdc++6   13.2.0-4
ii  libswresample4   7:6.0-7
ii  libswscale7  7:6.0-7
ii  libvpx7  1.12.0-1.2
ii  libx11-6 2:1.8.6-1
ii  libxcb-keysyms1  0.4.0-1+b2
ii  libxcb-record0   1.15-1
ii  libxcb-screensaver0  1.15-1
ii  libxcb1  1.15-1
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.6-1
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxrandr2   2:1.5.2-2+b1
ii  libxtst6 2:1.2.3-1.1
ii  libxxhash0   0.8.2-2
ii  libyuv0  0.0~git20230907.cbfb661-1
ii  qt5-image-formats-plugins5.15.10-2
ii  zlib1g   1:1.2.13.dfsg-3

Versions of packages telegram-desktop recommends:
ii  fonts-open-sans   1.11-2
ii  libwebkit2gtk-4.0-37  2.42.1-1
ii  libwebkit2gtk-4.1-0   2.42.1-1

telegram-desktop suggests no packages.

Versions of packages telegram-desktop is related to:
ii  xdg-desktop-portal   1.18.0-1
ii  xdg-desktop-portal-gtk [xdg-desktop-portal-backend]  1.14.1-1
ii  xdg-desktop-portal-kde [xdg-desktop-portal-backend]  5.27.8-1

-- no debconf information
[2023.10.10 09:50:50] Launched version: 4009007, install beta: [FALSE], alpha: 
0, debug mode: [FALSE]
[2023.10.10 09:50:50] Executable dir: /usr/bin/, name: telegram-desktop
[2023.10.10 09:50:50] Initial working dir: /home/shai/
[2023.10.10 09:50:50] Working dir: /home/shai/.local/share/TelegramDesktop/
[2023.10.10 09:50:50] Command line: /usr/bin/telegram-desktop --
[2023.10.10 09:50:50] Executable path before check: /usr/bin/telegram-desktop
[2023.10.10 09:50:50] Logs started
[2023.10.10 09:50:50] Launcher filename: org.telegram.desktop.desktop
[2023.10.10 09:50:50] We use allocator from /lib/x86_64-linux-gnu/libc.so.6
[2023.10.10 09:50:50] Connecting local socket to 
/tmp/735a4fdec5600e9bc6df96b79a9689ee-{87A94AB0-E370-4cde-98D3-ACC110C5967D}...
[2023.10.10 09:50:50] Socket connect error 0, starting server and app...
[2023.10.10 09:50:50] Moved logging from 
'/home/shai/.local/share/TelegramDesktop/log_start0.txt' to 
'/home/shai/.local/share/TelegramDesktop/log.txt'!
[2023.10.10 09:50:50] Global devicePixelRatio: 1
[2023.10.10 09:50:50] QT_AUTO_SCREEN_SCALE_FACTOR: 0
[2023.10.10 09:50:50] QT_DPI_ADJUSTMENT_POLICY: AdjustDpi
[2023.10.10 

Bug#1029710: emacs-gtk: Default font odd after disabling rashi

[Shai Berger]

Package: emacs-gtk
Version: 1:29.1+1-5
Followup-For: Bug #1029710

Dear Maintainer,

After disabling the Rashi font as noted above, for some time,
the Hebrew font was sensible. But recently it changed again,
this time to Dorian.

By invoking the menu option:
"Options->Multilingual Environment->Show all multilingual settings"
I was able to see the list of fonts for the Hebrew block:

(#x590 .. #x5FF)
-*-*-*-*-*-*-*-*-*-*-*-*-iso10646-1
[-PfEd-Dorian CLM-regular-normal-normal-*-15-*-*-*-*-0-iso10646-1]
[-PfEd-Simple CLM-regular-normal-normal-*-15-*-*-*-*-0-iso10646-1]
[-PfEd-DejaVu Sans-bold-normal-normal-*-15-*-*-*-*-0-iso10646-1]
[-PfEd-David CLM-bold-italic-normal-*-15-*-*-*-*-0-iso10646-1]
-*-*-*-*-*-*-*-*-*-*-*-*-iso8859-8

Dorian is a cursive, "fancy" font (in fact it comes from the package
culmus-fancy, not from the core culmus package). It is not as bas as
Rashi, but still unsuitable as a default font for text editing in Hebrew.

What controls the order of fonts?

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-4-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_IL.UTF-8, LC_CTYPE=en_IL.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages emacs-gtk depends on:
ii  emacs-bin-common 1:29.1+1-5
ii  emacs-common 1:29.1+1-5
ii  libacl1  2.3.1-3
ii  libasound2   1.2.9-2
ii  libc62.37-7
ii  libcairo21.16.0-7
ii  libdbus-1-3  1.14.10-1
ii  libfontconfig1   2.14.2-4
ii  libfreetype6 2.13.2+dfsg-1
ii  libgccjit0   13.2.0-2
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libgif7  5.2.1-2.5
ii  libglib2.0-0 2.77.2-1
ii  libgmp10 2:6.3.0+dfsg-2
ii  libgnutls30  3.8.1-4
ii  libgpm2  1.20.7-10+b1
ii  libgtk-3-0   3.24.38-4
ii  libharfbuzz0b8.0.1-1
ii  libice6  2:1.0.10-1
ii  libjansson4  2.14-2
ii  libjpeg62-turbo  1:2.1.5-2
ii  liblcms2-2   2.14-2
ii  libm17n-01.8.4-1
ii  libotf1  0.9.16-4
ii  libpango-1.0-0   1.51.0+ds-2
ii  libpng16-16  1.6.40-1
ii  librsvg2-2   2.54.7+dfsg-2
ii  libselinux1  3.5-1
ii  libsm6   2:1.2.3-1
ii  libsqlite3-0 3.42.0-1
ii  libsystemd0  254.1-2
ii  libtiff6 4.5.1+git230720-1
ii  libtinfo66.4+20230625-2
ii  libtree-sitter0  0.20.8-2
ii  libwebp7 1.2.4-0.2
ii  libwebpdemux21.2.4-0.2
ii  libx11-6 2:1.8.6-1
ii  libxcomposite1   1:0.4.5-1
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxi6   2:1.8-1+b1
ii  libxinerama1 2:1.1.4-3
ii  libxml2  2.9.14+dfsg-1.3
ii  libxrandr2   2:1.5.2-2+b1
ii  libxrender1  1:0.9.10-1.1
ii  zlib1g   1:1.2.13.dfsg-3

Versions of packages emacs-gtk recommends:
ii  fonts-noto-color-emoji  2.038-1

Versions of packages emacs-gtk suggests:
ii  emacs-common-non-dfsg  1:29.1+1-1

-- no debconf information

Bug#865975: docker.io changes iptables default FORWARD policy to DROP, breaks VM and others

[Shai Berger]

Package: docker.io
Followup-For: Bug #865975

Dear Maintainer,

I come here with a different use-case. I use Debian on a desktop, in a
room where the home wifi is weak. The desktop is connected by wire,
but also has a wireless network adapter, so I set up a hotspot for my
phone -- using tools from KDE (plasma-nm). I never touched the kernel
configuration or firewall rules, as (like Jonathan above) I never
needed to.

Recently I installed Docker in order to play with something, and it
took me quite a while to find out why, suddenly, when my phone
connects to the hotspot, it gets no access to the internet.

Docker's "solution" of only blocking forwarding if it set
ip_forwarding=1 itself is not helpful in my case -- the hotspot was
defined in my desktop, but the docker daemon starts at boot, typically
before I can log in.

When the access point is active, the following nft rules are set:

table ip nm-shared-wlan0 {
chain nat_postrouting {
type nat hook postrouting priority srcnat; policy accept;
ip saddr 10.42.0.0/24 ip daddr != 10.42.0.0/24 masquerade
}

chain filter_forward {
type filter hook forward priority filter; policy accept;
ip daddr 10.42.0.0/24 oifname "wlan0" ct state { established, 
related } accept
ip saddr 10.42.0.0/24 iifname "wlan0" accept
iifname "wlan0" oifname "wlan0" accept
iifname "wlan0" reject
oifname "wlan0" reject
}
}

This makes sense to me; when the UI opens up forwarding, it sets up
firewall rules to protect its own interfaces. Not everyone
else's. This is in the spirit of what Marvin suggested in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865975#53 -- and it
makes me disagree with the statement in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865975#91, that
Docker is "doing nothing wrong".

I should point also that in the original issue, the main motivation
behind seeing this as a security issue is to protect the containers
(see
e.g. https://github.com/moby/moby/issues/14041#issuecomment-113554682).

I realize that opening up forwarding can affect the security of a
system.  I think that Debian should ship a docker package which
doesn't do this (this seems to be controllable by configutation), but
instead, makes the proper changes to the system upon installation (and
lets the user know).

(the option to just error out from Docker if forwarding is not set up
was also mentioned on the ticket).

Also, since I'm not convinced by the argument in message #91, and
since I've had docker break unrelated functionality, I also disagree
with the downgrade in message #98. This behavior, as has not been
contested, "makes unrelated software on the system break". I agree
that before the behavior's introduction, it "introduce[d] a security
hole on systems where you install[ed] the package", which is also
critical, but that should not make it acceptable to break unrelated
software.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-4-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_IL.UTF-8, LC_CTYPE=en_IL.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages docker.io depends on:
ii  adduser3.137
pn  containerd 
ii  init-system-helpers1.65.2
ii  iptables   1.8.9-2
ii  libc6  2.37-7
ii  libdevmapper1.02.1 2:1.02.185-2
ii  libsystemd0254.1-2
ii  lsb-base   11.6
pn  runc   
ii  sysvinit-utils [lsb-base]  3.07-1
pn  tini   

Versions of packages docker.io recommends:
ii  apparmor 3.0.12-1
ii  ca-certificates  20230311
pn  cgroupfs-mount   
ii  git  1:2.40.1-1
ii  needrestart  3.6-5
ii  xz-utils 5.4.4-0.1

Versions of packages docker.io suggests:
pn  aufs-tools 
pn  btrfs-progs
pn  debootstrap
pn  docker-doc 
ii  e2fsprogs  1.47.0-2
pn  rinse  
pn  rootlesskit
pn  xfsprogs   
pn  zfs-fuse | zfsutils-linux  

Bug#1050656: telegram-desktop: Bus Error whenever a channel has a video

[Shai Berger]

Package: telegram-desktop
Version: 4.8.1+ds-2+b2
Severity: important

Dear Maintainer,

Since the last update of telegram-desktop, every time I get to a video
in a channel or group, the program crashes.

I have run the program under gdb, and am attaching the traceback.
I hope it is useful.

-- Package-specific info:

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_IL.UTF-8, LC_CTYPE=en_IL.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages telegram-desktop depends on:
ii  libabsl20220623  20220623.1-3
ii  libavcodec-extra60 [libavcodec60]7:6.0-5
ii  libavfilter-extra9 [libavfilter9]7:6.0-5
ii  libavformat-extra60 [libavformat60]  7:6.0-5
ii  libavutil58  7:6.0-5
ii  libc62.37-7
ii  libgcc-s113.2.0-2
ii  libglib2.0-0 2.77.2-1
ii  libglibmm-2.68-1 2.77.0-1
ii  libhunspell-1.7-01.7.2+really1.7.2-10
ii  libjpeg62-turbo  1:2.1.5-2
ii  libkf5coreaddons55.107.0-1
ii  liblz4-1 1.9.4-1
ii  libminizip1  1:1.2.13.dfsg-3
ii  libopenal1   1:1.23.1-3
ii  libopus0 1.4-1
ii  libqrcodegencpp1 1.8.0-1.1
ii  libqt5core5a [qtbase-abi-5-15-10]5.15.10+dfsg-3
ii  libqt5gui5   5.15.10+dfsg-3
ii  libqt5network5   5.15.10+dfsg-3
ii  libqt5qml5   5.15.10+dfsg-2
ii  libqt5quickwidgets5  5.15.10+dfsg-2
ii  libqt5svg5   5.15.10-2
ii  libqt5waylandcompositor5 5.15.10-2
ii  libqt5widgets5   5.15.10+dfsg-3
ii  librlottie0-10.1+dfsg-4
ii  libsigc++-3.0-0  3.4.0-7
ii  libsrtp2-1   2.5.0-3
ii  libssl3  3.0.10-1
ii  libstdc++6   13.2.0-2
ii  libswresample4   7:6.0-5
ii  libswscale7  7:6.0-5
ii  libvpx7  1.12.0-1
ii  libwayland-client0   1.22.0-2
ii  libx11-6 2:1.8.6-1
ii  libxcb-keysyms1  0.4.0-1+b2
ii  libxcb-record0   1.15-1
ii  libxcb-screensaver0  1.15-1
ii  libxcb1  1.15-1
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.6-1
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxrandr2   2:1.5.2-2+b1
ii  libxtst6 2:1.2.3-1.1
ii  libxxhash0   0.8.1-1
ii  libyuv0  0.0~git20230616.a366ad7-1
ii  qt5-image-formats-plugins5.15.10-2
ii  zlib1g   1:1.2.13.dfsg-3

Versions of packages telegram-desktop recommends:
ii  fonts-open-sans   1.11-2
ii  libwebkit2gtk-4.0-37  2.40.5-1
ii  libwebkit2gtk-4.1-0   2.40.5-1

telegram-desktop suggests no packages.

Versions of packages telegram-desktop is related to:
ii  xdg-desktop-portal   1.16.0-3
ii  xdg-desktop-portal-gtk [xdg-desktop-portal-backend]  1.14.1-1
ii  xdg-desktop-portal-kde [xdg-desktop-portal-backend]  5.27.7-1

-- no debconf information
[2023.08.27 14:12:03] Launched version: 4008001, install beta: [FALSE], alpha: 
0, debug mode: [FALSE]
[2023.08.27 14:12:03] Executable dir: /usr/bin/, name: telegram-desktop
[2023.08.27 14:12:03] Initial working dir: /home/shai/Documents/
[2023.08.27 14:12:03] Working dir: /home/shai/.local/share/TelegramDesktop/
[2023.08.27 14:12:03] Command line: /usr/bin/telegram-desktop
[2023.08.27 14:12:03] Executable path before check: /usr/bin/telegram-desktop
[2023.08.27 14:12:03] Logs started
[2023.08.27 14:12:03] Launcher filename: org.telegram.desktop.desktop
[2023.08.27 14:12:03] We use allocator from /lib/x86_64-linux-gnu/libc.so.6
[2023.08.27 14:12:06] Connecting local socket to 
/tmp/735a4fdec5600e9bc6df96b79a9689ee-{87A94AB0-E370-4cde-98D3-ACC110C5967D}...
[2023.08.27 14:12:06] Socket connect error 0, starting server and app...
[2023.08.27 14:12:06] Moved logging from 
'/home/shai/.local/share/TelegramDesktop/log_start0.txt' to 
'/home/shai/.local/share/TelegramDesktop/log.txt'!
[2023.08.27 14:12:06] Global devicePixelRatio: 1
[2023.08.27 14:12:06] QT_AUTO_SCREEN_SCALE_FACTOR: 0
[2023.08.27 14:12:06] QT_DPI_ADJUSTMENT_POLICY: AdjustDpi
[2023.08.27 14:12:06] Primary screen DPI: 96.1263, 

Bug#1042404: redis-server postinst script gets stuck when disk is low

[Shai Berger]

Hi Chris,

On Fri, 28 Jul 2023 10:17:49 +0100
"Chris Lamb"  wrote:

> 
> Hm. Do you know what part of the postinst script is sticking? You may
> be able to find out by looking at your process table eg. via top or
> htop.
> 
> (My initial guess is that redis process itself gets wedged when it has
> no diskspace, and then—even after freeing some space—the postinst is
> waiting for it to restart?)
> 

I think I saw something like that, indeed, one of my probes into the
system showed that a "systemctl stop redis" or something very similar
was still running.

This seems quite odd to me -- I thought Redis, at least in its default
configuration (which is what I use), was an in-memory database. Why
would it get stuck over low disk space? And, if it does get stuck --
why wouldn't we just kill it? And how come the postinst script is
SIGINT-resistant?

Bug#1042404: redis-server postinst script gets stuck when disk is low

[Shai Berger]

Package: redis-server
Version: 5:7.0.11-1
Severity: normal

Dear Maintainer,

My system was set up years ago, with a root partition that
is not really big enough anymore. Repeatedly, when I run
updates, I get in trouble because space on the root partition
runs out.

However, with most packages, this just means that setup fails,
and after I make some room, a "dpkg --configure -a" sets things
straight.

redis-server, not so. The script gets stuck, not erroring out and
not finishing. Even after it is killed and room becomes available,
it's still a hard fight to get it to complete; sometimes an
uninstall+install is enough, today, not even that seems to work.

BTW, when I say "killed", I do mean killed: Ctrl-C does nothing to
the dpkg or aptitude process. It needs to be stopped with ctrl-Z,
and then killed.

-- System Information:
Debian Release: trixie/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'oldstable-updates'), (500, 
'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages redis-server depends on:
ii  init-system-helpers1.65.2
ii  lsb-base   11.6
ii  redis-tools5:7.0.11-1
ii  sysvinit-utils [lsb-base]  3.07-1

redis-server recommends no packages.

redis-server suggests no packages.

-- Configuration Files:
/etc/redis/redis.conf [Errno 13] Permission denied: '/etc/redis/redis.conf'

-- no debconf information

Bug#1041773: wpasupplicant: probably wrong "handshake" for hotspot with WPA2-Personal

[Shai Berger]

Package: wpasupplicant
Version: 2:2.10-12
Severity: normal

Dear Maintainer,

I have been using wpasupplucant with NetworkManager under KDE for
several years, in order to make an access point in my study (where
the home wifi signal is too weak). I've been using a Samsung S9
phone, and all was well.

Lately, I bought a newer phone -- a Samsung S20 -- and with that
phone, I could not connect to the access point. I searched high and low,
until I found this
https://www.reddit.com/r/kde/comments/soqzo4/unable_to_connect_to_hotspot_made_with/
with the recommendation to use iwd instead of wpasupplicant.

And just like for that responder, iwd "just worked".

In addition to the S20 refusing to connect, I also have a laptop
running Ubuntu 20.04. When that laptop was scanning the relevant
network (with wpasupplicant), the access point showed up with
"unknown encryption scheme". With iwd, it says "WPA2-PSK".
(just to make perfectly clear: the computer where the backend
was switched is a Debian desktop. The laptop uses whatever is
default in Ubuntu, and nothing in it was changed).

BTW the Reddit page leads to a KDE bug
https://bugs.kde.org/show_bug.cgi?id=449265
but my guess would be that the bug is not in KDE, but
somewhere between wpasupplicant and NetworkManager.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_IL.UTF-8, LC_CTYPE=en_IL.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wpasupplicant depends on:
ii  adduser3.137
ii  libc6  2.37-6
ii  libdbus-1-31.14.8-2
ii  libnl-3-2003.7.0-0.2+b1
ii  libnl-genl-3-200   3.7.0-0.2+b1
ii  libnl-route-3-200  3.7.0-0.2+b1
ii  libpcsclite1   2.0.0-1
ii  libreadline8   8.2-1.3
ii  libssl33.0.9-1

wpasupplicant recommends no packages.

Versions of packages wpasupplicant suggests:
pn  libengine-pkcs11-openssl  
pn  wpagui

-- no debconf information

Bug#1033681: ffmpeg: All executables fail to start with "Bus Error"

[Shai Berger]

Package: ffmpeg
Version: 7:5.1.2-3
Severity: important

Dear Maintainer,

I have not used ffmpeg in a while, so I cannot say how new this is,
but, as the title says, today, if I try to run ffmpgeg, ffprobe or
ffplay, even with just the '-version' flag, I get the same response:

$ ffmpeg -version
Bus error

This happens only on this one system. I have another system which
is also a Debian Testing, and there things do work.

I have tried to debug this, but to no avail:

$ gdb /usr/bin/ffmpeg 
GNU gdb (Debian 13.1-2) 13.1
Copyright (C) 2023 Free Software Foundation, Inc.
[...]
This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
Reading symbols from 
/home/shai/.cache/debuginfod_client/7215fbfbcdbd6cfa01fc6d11f68e6cd32e232637/debuginfo...

 
(gdb) r -version

   
Starting program: /usr/bin/ffmpeg -version
Downloading separate debug info for /lib64/ld-linux-x86-64.so.2
Downloading separate debug info for system-supplied DSO at 0x77fc9000   

   


   
Program received signal SIGBUS, Bus error.
0x77fd93c8 in ?? () from /lib64/ld-linux-x86-64.so.2
(gdb) where
#0  0x77fd93c8 in ?? () from /lib64/ld-linux-x86-64.so.2
#1  0x77fe8c09 in ?? () from /lib64/ld-linux-x86-64.so.2
#2  0x77fe519f in ?? () from /lib64/ld-linux-x86-64.so.2
#3  0x77fe6b1c in ?? () from /lib64/ld-linux-x86-64.so.2
#4  0x77fe59c8 in ?? () from /lib64/ld-linux-x86-64.so.2
#5  0x0002 in ?? ()
#6  0x7fffe16d in ?? ()
#7  0x7fffe17d in ?? ()
#8  0x in ?? ()
(gdb) 


I've also tried running the same with a user which never used
ffmpeg before, to account for some settings if relevant. Same.

I am at a loss on how to debug this further.

Thanks in advance for your attention and help,

   Shai.
   

-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-6-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_IL.UTF-8, LC_CTYPE=en_IL.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ffmpeg depends on:
ii  libavcodec597:5.1.2-3
ii  libavdevice59   7:5.1.2-3
ii  libavfilter87:5.1.2-3
ii  libavformat59   7:5.1.2-3
ii  libavutil57 7:5.1.2-3
ii  libc6   2.36-8
ii  libpostproc56   7:5.1.2-3
ii  libsdl2-2.0-0   2.26.4+dfsg-1
ii  libswresample4  7:5.1.2-3
ii  libswscale6 7:5.1.2-3

ffmpeg recommends no packages.

Versions of packages ffmpeg suggests:
pn  ffmpeg-doc  

-- no debconf information

Bug#1029710: Confirmation

[Shai Berger]

Dear Maintainer,

It's not just Tzafrir...

As a workaround, I added this in my .emacs:

(add-to-list 'face-ignored-fonts "Noto Rashi Hebrew")

Thanks,
Shai.

Bug#1003108: python3-poetry: Still an issue

[Shai Berger]

Package: python3-poetry
Version: 1.1.14+dfsg-1
Followup-For: Bug #1003108

Dear Maintainer,

Just installed poetry, ran into the missing cachecontrol,
installed cachecontrol manually, all seems fine.

The default for poetry in Debian, though, is just not to work,
as long as this is not handled.

-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-poetry depends on:
ii  python3 3.10.5-3
ii  python3-cachecontrol0.12.12-2
ii  python3-cachy   0.3.0-4
ii  python3-cleo0.8.1-4
ii  python3-clikit  0.6.2-3
ii  python3-html5lib1.1-3
ii  python3-importlib-metadata  4.12.0-1
ii  python3-lockfile1:0.12.2-2.2
ii  python3-packaging   21.3-1.1
ii  python3-pexpect 4.8.0-3
ii  python3-pkginfo 1.8.2-1
ii  python3-poetry-core 1.0.8-2
ii  python3-requests2.27.1+dfsg-1
ii  python3-requests-toolbelt   0.9.1-2
ii  python3-shellingham 1.5.0-1
ii  python3-tomlkit 0.11.6-1
ii  python3-virtualenv  20.16.6+ds-1

python3-poetry recommends no packages.

python3-poetry suggests no packages.

-- no debconf information

Bug#967010: apache2: Did not reporoduce

[Shai Berger]

Hi,

On Tue, 08 Nov 2022 18:05:23 +0100
"Yadd"  wrote:

> 
> Hi, it's a Buster-only bug, not a Bullseye's one
> 

It was flagged by apt-listbugs on my bookworm/sid system.

Bug#967010: apache2: Did not reporoduce

[Shai Berger]

Package: apache2
Followup-For: Bug #967010

Dear Maintainer,

I just installed Apache2 and did not encounter the problem
as reported in this bug.

It is an old bug, and for some reason full of spam.

Please close and/or delete it.

Thanks.

-- Package-specific info:

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_IL.UTF-8, LC_CTYPE=en_IL.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apache2 depends on:
ii  apache2-bin2.4.54-3
ii  apache2-data   2.4.54-3
ii  apache2-utils  2.4.54-3
ii  init-system-helpers1.65.2
ii  lsb-base   11.4
ii  mime-support   3.66
ii  perl   5.36.0-4
ii  procps 2:3.3.17-7.1
ii  sysvinit-utils [lsb-base]  3.05-6

Versions of packages apache2 recommends:
ii  ssl-cert  1.1.2

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  chromium [www-browser]   107.0.5304.87-1
ii  dillo [www-browser]  3.0.5-7+b1
ii  firefox-esr [www-browser]102.4.0esr-1
ii  konqueror [www-browser]  4:21.12.3-1
ii  lynx [www-browser]   2.9.0dev.10-1+b1

Versions of packages apache2-bin depends on:
ii  libapr1  1.7.0-8
ii  libaprutil1  1.6.1-5+b2
ii  libaprutil1-dbd-sqlite3  1.6.1-5+b2
ii  libaprutil1-ldap 1.6.1-5+b2
ii  libbrotli1   1.0.9-2+b4
ii  libc62.35-4
ii  libcrypt11:4.4.28-2
ii  libcurl4 7.85.0-1
ii  libjansson4  2.14-2
ii  libldap-2.5-02.5.13+dfsg-2+b1
ii  liblua5.3-0  5.3.6-1+b1
ii  libnghttp2-141.50.0-1+b1
ii  libpcre2-8-0 10.40-2
ii  libssl3  3.0.7-1
ii  libxml2  2.9.14+dfsg-1+b1
ii  perl 5.36.0-4
ii  zlib1g   1:1.2.11.dfsg-4.1

Versions of packages apache2-bin suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  chromium [www-browser]   107.0.5304.87-1
ii  dillo [www-browser]  3.0.5-7+b1
ii  firefox-esr [www-browser]102.4.0esr-1
ii  konqueror [www-browser]  4:21.12.3-1
ii  lynx [www-browser]   2.9.0dev.10-1+b1

Versions of packages apache2 is related to:
ii  apache2  2.4.54-3
ii  apache2-bin  2.4.54-3

-- no debconf information

Bug#994928: kde-style-qtcurve-qt5 should Provide: kde-style-qtcurve

[Shai Berger]

Package: kde-style-qtcurve-qt5
Version: 1.9-7+b3
Followup-For: Bug #994928

Dear Maintainer,

Just found the same. Still a problem.

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.19.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kde-style-qtcurve-qt5 depends on:
ii  kio   5.98.0-1
ii  libc6 2.34-8
ii  libkf5archive55.98.0-1
ii  libkf5completion5 5.98.0-1
ii  libkf5configcore5 5.98.0-1
ii  libkf5configwidgets5  5.98.0-1
ii  libkf5coreaddons5 5.98.0-1
ii  libkf5guiaddons5  5.98.0-1
ii  libkf5i18n5   5.98.0-1
ii  libkf5iconthemes5 5.98.0-2
ii  libkf5kdelibs4support55.98.0-1
ii  libkf5kiowidgets5 5.98.0-1
ii  libkf5style5  5.98.0-1
ii  libkf5widgetsaddons5  5.98.0-1
ii  libkf5windowsystem5   5.98.0-1
ii  libkf5xmlgui5 5.98.0-1
ii  libqt5core5a [qtbase-abi-5-15-4]  5.15.4+dfsg-5
ii  libqt5dbus5   5.15.4+dfsg-5
ii  libqt5gui55.15.4+dfsg-5
ii  libqt5printsupport5   5.15.4+dfsg-5
ii  libqt5svg55.15.4-2
ii  libqt5widgets55.15.4+dfsg-5
ii  libqt5x11extras5  5.15.4-2
ii  libqtcurve-utils2 1.9-7+b3
ii  libstdc++612.2.0-3

kde-style-qtcurve-qt5 recommends no packages.

Versions of packages kde-style-qtcurve-qt5 suggests:
pn  gtk2-engines-qtcurve  

-- no debconf information

Bug#1007259: closed by Debian FTP Masters (reply to Ricardo Mones ) (Bug#1007259: fixed in claws-mail 4.0.0-3)

[Shai Berger]

Yay! Thanks a bunch!

Bug#1007259: claws-mail-extra-plugins: Please re-package Fancy plugin

[Shai Berger]

Package: claws-mail-extra-plugins
Version: 4.0.0-2
Severity: wishlist

Dear Maintainer,

With claws-mail 3.X, based on Gtk2, the fancy plugin needed
an abandoned branch of libwebkitgtk, and basically required
the package libwebkitgtk-1.0.0 which had been removed from
Debian. But now that 4.0.0 is based on Gtk3, Fancy can be built
against libwebkit2gtk-4.0-37 which is very much alive.

Can we bring claws-mail-fancy-plugin back?

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.16.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_IL.UTF-8, LC_CTYPE=en_IL.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages claws-mail-extra-plugins depends on:
ii  claws-mail-acpi-notifier 4.0.0-2+b1
ii  claws-mail-address-keeper4.0.0-2+b1
ii  claws-mail-archiver-plugin   4.0.0-2+b1
ii  claws-mail-attach-remover4.0.0-2+b1
ii  claws-mail-attach-warner 4.0.0-2+b1
ii  claws-mail-bsfilter-plugin   4.0.0-2+b1
ii  claws-mail-clamd-plugin  4.0.0-2+b1
ii  claws-mail-dillo-viewer  4.0.0-2+b1
ii  claws-mail-feeds-reader  4.0.0-2+b1
ii  claws-mail-fetchinfo-plugin  4.0.0-2+b1
ii  claws-mail-gdata-plugin  4.0.0-2+b1
ii  claws-mail-libravatar4.0.0-2+b1
ii  claws-mail-litehtml-viewer   4.0.0-2+b1
ii  claws-mail-mailmbox-plugin   4.0.0-2+b1
ii  claws-mail-managesieve   4.0.0-2+b1
ii  claws-mail-multi-notifier4.0.0-2+b1
ii  claws-mail-newmail-plugin4.0.0-2+b1
ii  claws-mail-pdf-viewer4.0.0-2+b1
ii  claws-mail-perl-filter   4.0.0-2+b1
ii  claws-mail-spam-report   4.0.0-2+b1
ii  claws-mail-tnef-parser   4.0.0-2+b1
ii  claws-mail-vcalendar-plugin  4.0.0-2+b1

claws-mail-extra-plugins recommends no packages.

claws-mail-extra-plugins suggests no packages.

-- no debconf information

Bug#943671: claws-mail 4.0.0 is based on GTK3

[Shai Berger]

Package: claws-mail
Followup-For: Bug #943671

Dear Maintainer,

With claws-mail 4.0.0 based on GTK3 in testing, I believe this bug can be 
closed.

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.16.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_IL.UTF-8, LC_CTYPE=en_IL.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages claws-mail depends on:
ii  libc62.33-7
ii  libcairo21.16.0-5
ii  libcompfaceg11:1.5.2-5.1
ii  libdbus-glib-1-2 0.112-2
ii  libenchant-2-2   2.3.2-1
ii  libetpan20   1.9.4-3
ii  libgdk-pixbuf-2.0-0  2.42.6+dfsg-2
ii  libglib2.0-0 2.70.4-1
ii  libgnutls30  3.7.3-4+b1
ii  libgtk-3-0   3.24.33-1
ii  libice6  2:1.0.10-1
ii  libldap-2.4-22.4.59+dfsg-1+b1
ii  libnettle8   3.7.3-1
ii  libpango-1.0-0   1.50.4+ds-1
ii  libpangocairo-1.0-0  1.50.4+ds-1
ii  librsvg2-2   2.52.5+dfsg-3+b1
ii  libsm6   2:1.2.3-1
ii  xdg-utils1.1.3-4.1

Versions of packages claws-mail recommends:
ii  aspell-en [aspell-dictionary]  2018.04.16-0-1
ii  claws-mail-i18n4.0.0-2
ii  xfonts-100dpi  1:1.0.4+nmu1.1
ii  xfonts-75dpi   1:1.0.4+nmu1.1

Versions of packages claws-mail suggests:
ii  chromium [www-browser] 98.0.4758.102-1
ii  claws-mail-doc 4.0.0-2
pn  claws-mail-tools   
ii  dillo [www-browser]3.0.5-7
ii  firefox-esr [www-browser]  91.7.0esr-1
ii  gedit  41.0-3
ii  konqueror [www-browser]4:21.12.3-1
ii  kwrite 4:21.12.3-1
ii  lynx [www-browser] 2.9.0dev.10-1
ii  mousepad   0.5.8-1+b1

-- no debconf information

Bug#1001947: firefox-esr: Update from Firefox 78 to 91 reset browser.ctrlTab.sortByRecentlyUsed

[Shai Berger]

On Mon, 20 Dec 2021 05:36:42 +0900
Mike Hommey  wrote:

> 
> Filed upstream as https://bugzilla.mozilla.org/show_bug.cgi?id=1746804
> but at this point, this is probably unfixable... 
> 

Thanks. My apologies for thinking this was more likely to be a
packaging bug than an upstream one; though, by the description, one
needs to be more knowledgable than me to figure out what the problem
was...

Given the above, I won't object to the bug being closed and marked
wontfix, if you find that more useful.

> Note the pref is in Settings, under General > Tabs.
> 

Thanks, that helps! I have several Firefox profiles, some are still not
fixed.

Cheers,
Shai.

Bug#1001947: firefox-esr: Update from Firefox 78 to 91 reset browser.ctrlTab.sortByRecentlyUsed

[Shai Berger]

Package: firefox-esr
Version: 91.4.0esr-1
Severity: normal

Dear Maintainer,

I have been using Firefox for years; an important part
of the experience is having ctrl-tab go through tabs in
the order of recent use, rather than cycling through them
from left to right. This is not the default, but enabled
by an about:config flag named 'browser.ctrlTab.sortByRecentlyUsed'

Following the very welcome upgrade from 78 to 91, I
found that the browser reverted this flag to its default,
and I had to set it on again manually (after finding again
what it was named...)

Thanks for all your great efforts,

Shai.


-- Package-specific info:

-- Extensions information
Name: Amazon.com
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Bing
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Dark theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled

Name: DoH Roll-Out
Location: /usr/lib/firefox-esr/browser/features/doh-roll...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: DuckDuckGo
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Firebug
Location: ${PROFILE_EXTENSIONS}/fire...@software.joehewitt.com.xpi
Status: app-disabled

Name: Firefox Alpenglow theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled

Name: Firefox Screenshots
Location: /usr/lib/firefox-esr/browser/features/screensh...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: Form Autofill
Location: /usr/lib/firefox-esr/browser/features/formautof...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: Google
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Greasemonkey
Location: ${PROFILE_EXTENSIONS}/{e4a8a97b-f2ed-450b-b12d-ee082ba24781}.xpi
Status: enabled

Name: Hebrew (IL) Language Pack locale
Location: 
/usr/lib/firefox-esr/browser/extensions/langpack...@firefox-esr.mozilla.org.xpi
Package: firefox-esr-l10n-he
Status: enabled

Name: Light theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled

Name: Picture-In-Picture
Location: /usr/lib/firefox-esr/browser/features/pictureinpict...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: Proxy Failover
Location: /usr/lib/firefox-esr/browser/features/proxy-failo...@mozilla.com.xpi
Package: firefox-esr
Status: enabled

Name: System theme theme
Location: /usr/lib/firefox-esr/omni.ja
Package: firefox-esr
Status: enabled

Name: Web Compatibility Interventions
Location: /usr/lib/firefox-esr/browser/features/webcom...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: WebCompat Reporter
Location: 
/usr/lib/firefox-esr/browser/features/webcompat-repor...@mozilla.org.xpi
Package: firefox-esr
Status: user-disabled

Name: Wikipedia (en)
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled


-- Addons package information
ii  firefox-esr 91.4.0esr-1  amd64Mozilla Firefox web browser - 
Extended Support Release (ESR)
ii  firefox-esr-l10n-he 91.4.0esr-1  all  Hebrew language package for 
Firefox ESR

-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages firefox-esr depends on:
ii  debianutils  4.11.2
ii  fontconfig   2.13.1-4.2
ii  libatk1.0-0  2.36.0-3
ii  libc62.33-1
ii  libcairo-gobject21.16.0-5
ii  libcairo21.16.0-5
ii  libdbus-1-3  1.12.20-3
ii  libdbus-glib-1-2 0.112-2
ii  libevent-2.1-7   2.1.12-stable-1
ii  libffi8  3.4.2-3
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.11.0+dfsg-1
ii  libgcc-s111.2.0-12
ii  libgdk-pixbuf-2.0-0  2.42.6+dfsg-2
ii  libglib2.0-0 2.70.2-1
ii  libgtk-3-0   3.24.30-4
ii  libnspr4 2:4.32-3
ii  libnss3  2:3.73-1
ii  libpango-1.0-0   1.48.10+ds1-1
ii  libstdc++6   11.2.0-12
ii  libvpx7  1.11.0-2
ii  libx11-6 2:1.7.2-2+b1
ii  libx11-xcb1  2:1.7.2-2+b1
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.4-1
ii  libxfixes3   1:5.0.3-2
ii  libxrender1  1:0.9.10-1
ii  procps   2:3.3.17-5
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages firefox-esr recommends:
ii  libavcodec57  7:3.4.3-1
ii  libavcodec58  7:4.4.1-2+b1

Versions of packages firefox-esr 

Bug#999339: plasma-workspace: Maximized windows do not move to primary display when connected

[Shai Berger]

Hi Norbert, thanks for your very prompt reply, and my apologies for
failing to reply in kind.

On Wed, 10 Nov 2021 15:41:25 +0900
Norbert Preining  wrote:

> 
> Can you please test 5.23.3 which I have uploaded just today. It has
> several fixes included concerning exactly this problem, as far as I
> read it.
> 

I use "testing", and AFAICT 5.23.3 hasn't yet migrated there.

I added sid to the sources-list, and upgraded kde-plasma-desktop, which
did the following:

[UPGRADE] kde-plasma-desktop:amd64 5:114 -> 5:115
[UPGRADE] kwin-common:amd64 4:5.23.2-1 -> 4:5.23.3-1
[UPGRADE] kwin-data:amd64 4:5.23.2-1 -> 4:5.23.3-1
[UPGRADE] kwin-x11:amd64 4:5.23.2-1 -> 4:5.23.3-1
[UPGRADE] libcolorcorrect5:amd64 4:5.23.2-1 -> 4:5.23.3-1
[UPGRADE] libkfontinst5:amd64 4:5.23.2-1 -> 4:5.23.3-1
[UPGRADE] libkfontinstui5:amd64 4:5.23.2-1 -> 4:5.23.3-1
[UPGRADE] libkwin4-effect-builtins1:amd64 4:5.23.2-1 -> 4:5.23.3-1
[UPGRADE] libkwineffects13:amd64 4:5.23.2-1 -> 4:5.23.3-1
[UPGRADE] libkwinglutils13:amd64 4:5.23.2-1 -> 4:5.23.3-1
[UPGRADE] libkwinxrenderutils13:amd64 4:5.23.2-1 -> 4:5.23.3-1
[UPGRADE] libkworkspace5-5:amd64 4:5.23.2-1 -> 4:5.23.3-1
[UPGRADE] libnotificationmanager1:amd64 4:5.23.2-1 -> 4:5.23.3-1
[UPGRADE] libplasma-geolocation-interface5:amd64 4:5.23.2-1 -> 4:5.23.3-1
[UPGRADE] libtaskmanager6abi1:amd64 4:5.23.2-1 -> 4:5.23.3-1
[UPGRADE] libweather-ion7:amd64 4:5.23.2-1 -> 4:5.23.3-1
[UPGRADE] plasma-desktop:amd64 4:5.23.2.1-1 -> 4:5.23.3-1
[UPGRADE] plasma-desktop-data:amd64 4:5.23.2.1-1 -> 4:5.23.3-1
[UPGRADE] plasma-workspace:amd64 4:5.23.2-1 -> 4:5.23.3-1
[UPGRADE] plasma-workspace-data:amd64 4:5.23.2-1 -> 4:5.23.3-1

With these in place, the problem did not improve.

Thanks,
Shai.

Bug#999339: plasma-workspace: Maximized windows do not move to primary display when connected

[Shai Berger]

Package: plasma-workspace
Version: 4:5.23.2-1
Severity: normal

Dear Maintainer,

I use a laptop in different locations, with external screens.
Since the external screens are larger, I usually set them as 
the primary display, and use most of my applications there.

Until (and including) 5.21, when I had windows on the external
screen, disconnected it and reconnected an external screen, the
windows would hop back to the external (primary) display.

Since 5.23, I've noted that this doesn't quite work. With the
current version I've noticed further that it's the maximized
windows, specifically, which stay on the laptop screen (which,
when an external is connected, is the secondary display); 
normal-sized windows behave as expected.

-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.14.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-workspace depends on:
ii  dbus-user-session [default-dbus-session-bus]1.12.20-3
ii  drkonqi 5.23.2-1
ii  frameworkintegration5.86.0-1
ii  gdb-minimal [gdb]   10.1-2
ii  init-system-helpers 1.60
ii  iso-codes   4.7.0-1
ii  kactivitymanagerd   5.23.2-1
ii  kded5   5.86.0-1
ii  kinit   5.86.0-1
ii  kio 5.86.0-1
ii  kpackagetool5   5.86.0-1
ii  kwin-common 4:5.23.2-1
ii  libappstreamqt2 0.14.6-1
ii  libc6   2.32-4
ii  libcolorcorrect54:5.23.2-1
ii  libegl1 1.3.4-2+b1
ii  libfontconfig1  2.13.1-4.2
ii  libfreetype62.11.0+dfsg-1
ii  libgcc-s1   11.2.0-10
ii  libgl1  1.3.4-2+b1
ii  libgps283.22-4
ii  libice6 2:1.0.10-1
ii  libkf5activities5   5.86.0-1
ii  libkf5activitiesstats1  5.86.0-1
ii  libkf5archive5  5.86.0-1
ii  libkf5authcore5 5.86.0-1
ii  libkf5baloo55.86.0-1
ii  libkf5bookmarks55.86.0-1
ii  libkf5calendarevents5   5.86.0-1
ii  libkf5completion5   5.86.0-1
ii  libkf5config-bin5.86.0-1
ii  libkf5configcore5   5.86.0-1
ii  libkf5configgui55.86.0-1
ii  libkf5configwidgets55.86.0-1
ii  libkf5coreaddons5   5.86.0-1
ii  libkf5crash55.86.0-1
ii  libkf5dbusaddons5   5.86.0-1
ii  libkf5declarative5  5.86.0-1
ii  libkf5globalaccel-bin   5.86.0-1
ii  libkf5globalaccel5  5.86.0-1
ii  libkf5guiaddons55.86.0-1
ii  libkf5holidays5 1:5.86.0-1
ii  libkf5i18n5 5.86.0-1
ii  libkf5iconthemes5   5.86.0-1
ii  libkf5idletime5 5.86.0-1
ii  libkf5itemmodels5   5.86.0-1
ii  libkf5jobwidgets5   5.86.0-1
ii  libkf5kcmutils5 5.86.0-1
ii  libkf5kiocore5  5.86.0-1
ii  libkf5kiofilewidgets5   5.86.0-1
ii  libkf5kiogui5   5.86.0-1
ii  libkf5kiowidgets5   5.86.0-1
ii  libkf5networkmanagerqt6 5.86.0-1
ii  libkf5newstuff5 5.86.0-3
ii  libkf5newstuffcore5 5.86.0-3
ii  libkf5notifications55.86.0-1
ii  libkf5notifyconfig5 5.86.0-1
ii  libkf5package5

Bug#985647: telegram-desktop: Actively works against KDE Window rules

[Shai Berger]

Hi Nicholas,

On Sun, 21 Mar 2021 16:38:20 +0300
Nicholas Guriev  wrote:

> If you prefer to see KDE's titlebar on Telegram Desktop, set the
> System window frame checkbox in advanced settings inside the app.
> 

Thanks for the tip. In case anyone else sees this -- initially, when
you set the checkbox, Telegram's own titlebar disappears and the KDE one
does not appear, leaving the window with no titlebar at all. Only after
closing and reopening the window (e.g. by clicking the Telegram tray
icon), the KDE titlebar shows up.

I should note that even with this, the rule
Virtual Desktop: Apply Initially / All Desktops
Does not achieve anything. And it used to. 

Bug#985647: telegram-desktop: Actively works against KDE Window rules

[Shai Berger]

Package: telegram-desktop
Version: 2.6.1+ds-1
Severity: normal

Dear Maintainer,

Not sure how long this has been going on -- I normally have two virtual
desktops, and I like to have telegram-desktop present on both of them.

So I've set up KDE window rules to make it so. And they worked fine.

Recently I've noticed that Telegram was only on one desktop. I looked
for the titlebar in order to pin it, and then realized there's no
titlebar.

So I set a Window Rule to "Apply Initially" that the titlebar be present,
in addition to the initially-applied "Virtual Desktop: All Desktops".

Open opening Telegram, it just ignored these.

I could change them to "Force", I guess...


-- Package-specific info:

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-4-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 telegram-desktop depends on:
ii  libavcodec58  7:4.3.2-0+deb11u1
ii  libavformat58 7:4.3.2-0+deb11u1
ii  libavutil56   7:4.3.2-0+deb11u1
ii  libc6 2.31-9
ii  libdbusmenu-qt5-2 0.9.3+16.04.20160218-2+b1
ii  libgcc-s1 10.2.1-6
ii  libgdk-pixbuf-2.0-0   2.42.2+dfsg-1
ii  libglib2.0-0  2.66.7-2
ii  libgtk-3-03.24.24-3
ii  libhunspell-1.7-0 1.7.0-3
ii  libjpeg62-turbo   1:2.0.6-4
ii  libkf5waylandclient5  4:5.78.0-2
ii  liblz4-1  1.9.3-1
ii  liblzma5  5.2.5-1.0
ii  libminizip1   1.1-8+b1
ii  libopenal11:1.19.1-2
ii  libopus0  1.3.1-0.1
ii  libqrcodegencpp1  1.6.0-1
ii  libqt5core5a [qtbase-abi-5-15-2]  5.15.2+dfsg-5
ii  libqt5dbus5   5.15.2+dfsg-5
ii  libqt5gui55.15.2+dfsg-5
ii  libqt5network55.15.2+dfsg-5
ii  libqt5waylandclient5 [qtwayland-client-abi-5-15-  5.15.2-2
ii  libqt5widgets55.15.2+dfsg-5
ii  librlottie0-1 0.1+dfsg-1
ii  libssl1.1 1.1.1j-1
ii  libstdc++610.2.1-6
ii  libswresample37:4.3.2-0+deb11u1
ii  libswscale5   7:4.3.2-0+deb11u1
ii  libx11-6  2:1.7.0-2
ii  libxcb-keysyms1   0.4.0-1+b2
ii  libxcb-record01.14-3
ii  libxcb-screensaver0   1.14-3
ii  libxcb1   1.14-3
ii  libxxhash00.8.0-2
ii  qt5-image-formats-plugins 5.15.2-2
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages telegram-desktop recommends:
ii  fonts-open-sans  1.11-1.1

telegram-desktop suggests no packages.

-- no debconf information
[2021.03.14 08:56:06] Launched version: 2006001, install beta: [FALSE], alpha: 
0, debug mode: [FALSE]
[2021.03.14 08:56:06] Executable dir: /usr/bin/, name: telegram-desktop
[2021.03.14 08:56:06] Initial working dir: /home/shai/
[2021.03.14 08:56:06] Working dir: /home/shai/.local/share/TelegramDesktop/
[2021.03.14 08:56:06] Command line: /usr/bin/telegram-desktop --
[2021.03.14 08:56:05] Executable path before check: /usr/bin/telegram-desktop
[2021.03.14 08:56:06] Logs started
[2021.03.14 08:56:06] Launcher filename: telegramdesktop.desktop
[2021.03.14 08:56:06] Connecting local socket to 
/run/user/1000/735a4fdec5600e9bc6df96b79a9689ee-{87A94AB0-E370-4cde-98D3-ACC110C5967D}...
[2021.03.14 08:56:06] This is the only instance of Telegram, starting server 
and app...
[2021.03.14 08:56:06] Moved logging from 
'/home/shai/.local/share/TelegramDesktop/log_start0.txt' to 
'/home/shai/.local/share/TelegramDesktop/log.txt'!
[2021.03.14 08:56:06] Primary screen DPI: 96.1263
[2021.03.14 08:56:07] App Info: reading settings...
[2021.03.14 08:56:07] App Info: reading encrypted settings...
[2021.03.14 08:56:08] Lang Info: Loaded cached, keys: 3079
[2021.03.14 08:56:12] OpenAL Logging Level: (not set)
[2021.03.14 08:56:14] 

Bug#979819: python3-distutils version 3.9.x breaks python3.8-stdlib with no version limit

[Shai Berger]

Thanks again.

Bug#979819: python3-distutils version 3.9.x breaks python3.8-stdlib with no version limit

[Shai Berger]

On Tue, 26 Jan 2021 12:46:39 +0100
Matthias Klose  wrote:

> On 1/11/21 5:34 PM, Shai Berger wrote:
> > Package: python3-distutils
> > Version: 3.9.1-2
> > Severity: normal
> > 
> > 
> > While this packages lists, among other things,
> > Breaks: ..., libpython3.8-stdlib (< 3.8.0~b2-5)
> > 
> > In fact, [it breaks all versions of] libpython3.8-stdlib.
> > 
> > I see two, non-exclusionary paths to solve this:
> > - Just mark the breakage correctly
> 
> Closing this issue as won't fix.

Please just fix the Breaks info. Mark libpython3.8-stdlib as
uncoditionally broken by current versions of python3-distutils.

Further,

> 
> The python3-tk, python3-gdbm and python3-distutils packages are real
> packages, not virtual packages, which support both the old 3.8 and
> the new 3.9 Python versions during the time Debian is doing the
> transition to a new Python3 version. After the transition we remove
> 3.8, so we only build those using 3.9.
> 

In my suggestion:

> > - Provide real, rather than virtual, python3.x-distutils packages  

I wasn't referring to python3-distutils, but to python3.8-distutils or
python3.9-distutils, which are virtual (provided by python3-distutils).
I fully understand and support a decision not to make them real
packages; I appreciate that this would be more work for busy volunteer
maintainers, for a less-than-mainstream use-case.

Thanks for all your efforts,
Shai.

Bug#979819: python3-distutils version 3.9.x breaks python3.8-stdlib with no version limit

[Shai Berger]

Package: python3-distutils
Version: 3.9.1-2
Severity: normal

Dear Maintainer,

For years I've known that installing a newer version of Python
on my Debian system breaks existing virtualenvs set up for the
old Python version. Today I investigated a little and found out
why:

While this packages lists, among other things,
Breaks: ..., libpython3.8-stdlib (< 3.8.0~b2-5)

In fact, installing it at this version removes most files from
/usr/lib/python3.8/distutils/ and thereby breaks any use of 
distutils or setuptools under python 3.8, and that most certainly
includes libpython3.8-stdlib=3.8.7-1 which I currently have
installed, as well as, I believe, any other version of libpython3.8-stdlib.

I see two, non-exclusionary paths to solve this:
- Just mark the breakage correctly
- Provide real, rather than virtual, python3.x-distutils packages

Thanks,
Shai.

-- System Information:
Debian Release: bullseye/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-distutils depends on:
ii  python3  3.9.1-1
ii  python3-lib2to3  3.9.1-2

python3-distutils recommends no packages.

python3-distutils suggests no packages.

-- no debconf information

Bug#979177: cups-filters-core-drivers: Adding a printer impossible because "driverless" is too slow

[Shai Berger]

Package: cups-filters-core-drivers
Version: 1.28.6-1
Severity: normal

Dear Maintainer,

I've seen some misbehavior from my printer, and tried to remove and add it
back again. This failed, with the symptoms described in
https://unix.stackexchange.com/questions/276736/cups-adding-printer-fails-with-unable-to-get-list-of-printer-drivers-success
that is, no matter what interface I use -- KDE, Gnome or the web
via localhost:631 -- I get the same error when trying to find
drivers for the printer:

Unable to get list of printer drivers:
Success

Following the advice on that page, I tried to see if removal of
one of the files in /usr/lib/cups/driver can help me get faster
results, and I found that the guilty script was
/usr/lib/cups/driver/driverless

I then tried to run this script in isolation, and got:

$ time /usr/lib/cups/driver/disabl/driverless list
DEBUG: Started ippfind (PID 19070)
Failed to get info about driverless support.
"driverless:ipp://HP%20OfficeJet%206950%20%5B00A23E%5D%20(USB)._ipp._tcp.local/"
 en "HP" "HP OfficeJet 6950, driverless - cannot check driverless status, 
cups-filters 1.28.6" "MFG:HP;MDL:OfficeJet 
6950;CMD:PCLM,PCL,PWGRaster,AppleRaster,JPEG,URF,PWG;"
"driverless-fax:ipp://HP%20OfficeJet%206950%20%5B00A23E%5D%20(USB)._ipp._tcp.local/"
 en "HP" "HP OfficeJet 6950, Fax, driverless - cannot check driverless status, 
cups-filters 1.28.6" "MFG:HP;MDL:OfficeJet 
6950;CMD:PCLM,PCL,PWGRaster,AppleRaster,JPEG,URF,PWG;"
DEBUG: ippfind (PID 19070) exited with no errors.

real3m1.817s
user0m0.005s
sys 0m0.015s

Noticing my specific printer named in the output -- could it be
that the script tries to communicate with it, but fails to do it
in a robust way?

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_IL.UTF-8, LC_CTYPE=en_IL.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cups-filters-core-drivers depends on:
ii  bc 1.07.1-2+b2
ii  cups-ipp-utils 2.3.3op1-3
ii  libc6  2.31-6
ii  libcups2   2.3.3op1-3
ii  libcupsfilters11.28.6-1
ii  libgcc-s1  10.2.1-3
ii  liblcms2-2 2.9-4+b1
ii  libpoppler-cpp0v5  20.09.0-3
ii  libqpdf28  10.0.4-1
ii  libstdc++6 10.2.1-3
ii  poppler-utils  20.09.0-3
ii  zlib1g 1:1.2.11.dfsg-2

cups-filters-core-drivers recommends no packages.

cups-filters-core-drivers suggests no packages.

-- no debconf information

Bug#946976: plasma-desktop: Processes stay alive after logoff

[Shai Berger]

Package: plasma-desktop
Version: 4:5.14.5.1-4
Severity: normal

Dear Maintainer,

I have discovered that users on this system who log off their plasma
sessions, leave running processes behind them. These are usually
non-KDE processes.

As an example, some processes left from a user session (all belong
to the said user, all date from their last session, user has no
crontab; some details deleted for privacy reasons)

/lib/systemd/systemd --user
(sd-pam)
/usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile 
--systemd-activation --syslog-only
/usr/lib/dconf/dconf-service
/usr/lib/at-spi2-core/at-spi-bus-launcher --launch-immediately
/usr/libexec/geoclue-2.0/demos/agent
/usr/bin/dbus-daemon 
--config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork 
--print-address 3
/usr/bin/zeitgeist-datahub
/usr/bin/python3 /usr/bin/hp-systray -x
/usr/bin/python3 /usr/bin/hp-systray -x
/usr/lib/tracker/tracker-miner-apps
/usr/lib/tracker/tracker-miner-fs
/usr/lib/gvfs/gvfsd
/usr/lib/gvfs/gvfsd-fuse /run/user/1005/gvfs -f
/usr/lib/tracker/tracker-store
/usr/lib/gvfs/gvfs-udisks2-volume-monitor
/usr/lib/gvfs/gvfs-mtp-volume-monitor
/usr/lib/gvfs/gvfs-goa-volume-monitor
/usr/lib/gnome-online-accounts/goa-daemon
/usr/bin/zeitgeist-daemon
/usr/lib/zeitgeist/zeitgeist-fts
/usr/lib/gnome-online-accounts/goa-identity-service
/usr/lib/gvfs/gvfs-afc-volume-monitor
/usr/lib/gvfs/gvfs-gphoto2-volume-monitor
/usr/lib/bluetooth/obexd

User's session is Plasma. Cinnamon and XFCE are also installed
on the system, but seldom used.

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'unstable'), (800, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IL.UTF-8, LC_CTYPE=en_IL.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-desktop depends on:
ii  breeze   4:5.14.5-2+b1
ii  kactivitymanagerd5.14.5-1+b1
ii  kde-cli-tools4:5.14.5-2+b1
ii  kded55.62.0-1+b1
ii  kio  5.62.1-2+b1
ii  kpackagetool55.62.0-1
ii  libappstreamqt2  0.12.9-1
ii  libc62.29-3
ii  libfontconfig1   2.13.1-2+b1
ii  libfreetype6 2.10.1-2
ii  libgcc1  1:9.2.1-21
ii  libkf5activities55.62.0-1+b1
ii  libkf5activitiesstats1   5.62.0-1
ii  libkf5archive5   5.62.0-1
ii  libkf5authcore5  5.62.0-1+b1
ii  libkf5baloo5 5.62.0-2+b1
ii  libkf5codecs55.62.0-1
ii  libkf5completion55.62.0-1+b1
ii  libkf5configcore55.62.0-1+b1
ii  libkf5configgui5 5.62.0-1+b1
ii  libkf5configwidgets5 5.62.0-1+b1
ii  libkf5coreaddons55.62.0-1
ii  libkf5dbusaddons55.62.0-1
ii  libkf5declarative5   5.62.0-1+b1
ii  libkf5emoticons-bin  5.62.0-1+b1
ii  libkf5emoticons5 5.62.0-1+b1
ii  libkf5globalaccel-bin5.62.0-1+b1
ii  libkf5globalaccel5   5.62.0-1+b1
ii  libkf5guiaddons5 5.62.0-2
ii  libkf5i18n5  5.62.0-1
ii  libkf5iconthemes55.62.0-1+b1
ii  libkf5itemmodels55.62.0-1
ii  libkf5itemviews5 5.62.0-1+b1
ii  libkf5jobwidgets55.62.0-1+b1
ii  libkf5kcmutils5  5.62.0-1+b1
ii  libkf5kdelibs4support5   5.62.0-2
ii  libkf5kiocore5   5.62.1-2+b1
ii  libkf5kiofilewidgets55.62.1-2+b1
ii  libkf5kiowidgets55.62.1-2+b1
ii  libkf5newstuff5  5.62.0-1+b1
ii  libkf5notifications5 5.62.0-1+b1
ii  libkf5notifyconfig5  5.62.0-1+b1
ii  libkf5package5   5.62.0-1
ii  libkf5parts5 5.62.0-1+b1
ii  libkf5people55.62.0-1+b1
ii  libkf5peoplewidgets5 5.62.0-1+b1
ii  libkf5plasma55.62.0-1+b1
ii  libkf5plasmaquick5   5.62.0-1+b1
ii  libkf5quickaddons5   5.62.0-1+b1
ii  libkf5runner55.62.0-1+b1
ii  libkf5service-bin5.62.0-1
ii  libkf5service5   5.62.0-1
ii  libkf5solid5

Bug#927478: rust-doc: font-awesome not picked up by Firefox

[Shai Berger]

Package: rust-doc
Version: 1.32.0+dfsg1-3
Severity: minor

Dear Maintainer,

I like to browse the rust book using my locally installed
copy of the Rust documentation. Also, I use Firefox.

I've noticed for a long time that some icons in the book
web pages, like the "previous" and "next" buttons, are not
displayed as proper characters, and instead are showing just
a hexadecimal character code.

Today I checked and found:
- These symbols are created by use of Font Awesome
- Chromium, unlike Firefox, does show the correct symbols
- Firefox does show the symbols in the online version
  of the book

So I think that the problem is that the packaging somehow
prevents Firefox from picking up the correct fonts.

Thanks,
Shai.



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IL.UTF-8, LC_CTYPE=en_IL.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages rust-doc depends on:
ii  fonts-font-awesome  5.0.10+really4.7.0~dfsg-1
ii  fonts-open-sans 1.11-1
ii  libjs-highlight.js  9.12.0+dfsg1-4
ii  libjs-jquery3.3.1~dfsg-1
ii  libjs-mathjax   2.7.4+dfsg-1

Versions of packages rust-doc recommends:
ii  cargo-doc  0.33.0-1

rust-doc suggests no packages.

-- no debconf information

Bug#916747: kdesudo: Windows open through kdesudo do not support multiple keyboard layouts

[Shai Berger]

Package: kdesudo
Version: 3.4.2.4-2+b1
Severity: normal
Tags: l10n

Dear Maintainer,

I use multiple system users for my work on different projects,
and I use kdesudo in order to open a terminal (and from it,
other apps) for my separate users, within my "main" user's
desktop.

I also use multiple keyboard layouts -- us and il.

But the windows opened via kdesudo do not seem to be aware of this.
Whenever I enter one of these windows, I am "stuck" in the us
layout, and cannot switch layouts; neither via the switch-layout
shortcut, nor by clicking the system-tray icon.

This may be related to input methods -- I know very little of these,
and am not using anything non-default, at least not intentionally.

-- System Information:
Debian Release: buster/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kdesudo depends on:
ii  debconf [debconf-2.0]  1.5.69
ii  kde-runtime4:17.08.3-2
ii  libc6  2.28-2
ii  libgcc11:8.2.0-12
ii  libkdecore54:4.14.38-3
ii  libkdeui5  4:4.14.38-3
ii  libqt4-dbus4:4.8.7+dfsg-17
ii  libqt4-svg 4:4.8.7+dfsg-17
ii  libqtcore4 4:4.8.7+dfsg-17
ii  libqtgui4  4:4.8.7+dfsg-17
ii  libstdc++6 8.2.0-12
ii  sudo   1.8.26-2

kdesudo recommends no packages.

kdesudo suggests no packages.

-- debconf information:
  kdesudo/kdesu: false

Bug#910853: closed by Sebastiaan Couwenberg (Re: Bug#910853: qgis: Crashes on attempt to use Python console)

[Shai Berger]

Tried again on a cleaner system, and indeed, cannot reproduce.

Thanks, and sorry for the noise.

Bug#910853: qgis: Crashes on attempt to use Python console

[Shai Berger]

Package: qgis
Version: 2.18.24+dfsg-1
Severity: normal

Dear Maintainer,

Open qgis. Click the python console symbol. In the console which
opens, start typing -- I tried to type "help(iface)" as the 
console recommends, and the program crashed before I could
finish.

-- System Information:
Debian Release: buster/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qgis depends on:
ii  libc6   2.27-6
ii  libexpat1   2.2.6-1
ii  libgcc1 1:8.2.0-7
ii  libgdal20 [gdal-abi-2-3-0]  2.3.2+dfsg-1
ii  libgeos-c1v53.7.0-1
ii  libgsl232.5+dfsg-5
ii  libgslcblas02.5+dfsg-5
ii  libpq5  10.5-1
ii  libproj13   5.2.0-1
ii  libqca2 2.1.3-2
ii  libqgis-analysis2.18.24 2.18.24+dfsg-1
ii  libqgis-app2.18.24  2.18.24+dfsg-1
ii  libqgis-core2.18.24 2.18.24+dfsg-1
ii  libqgis-gui2.18.24  2.18.24+dfsg-1
ii  libqgis-networkanalysis2.18.24  2.18.24+dfsg-1
ii  libqscintilla2-qt4-13   2.10.4+dfsg-1+b1
ii  libqt4-network  4:4.8.7+dfsg-17
ii  libqt4-sql  4:4.8.7+dfsg-17
ii  libqt4-svg  4:4.8.7+dfsg-17
ii  libqt4-xml  4:4.8.7+dfsg-17
ii  libqtcore4  4:4.8.7+dfsg-17
ii  libqtgui4   4:4.8.7+dfsg-17
ii  libqwt6abi1 6.1.3-1
ii  libspatialindex4v5  1.8.5-7
ii  libspatialite7  4.3.0a-5+b2
ii  libsqlite3-03.25.2-1
ii  libstdc++6  8.2.0-7
ii  python-qgis 2.18.24+dfsg-1
ii  qgis-common 2.18.24+dfsg-1
ii  qgis-providers  2.18.24+dfsg-1

Versions of packages qgis recommends:
ii  qgis-plugin-grass2.18.24+dfsg-1
ii  qgis-provider-grass  2.18.24+dfsg-1

Versions of packages qgis suggests:
pn  gpsbabel  

-- no debconf information

Bug#905627: firefox: After update, tabs from previous session fail to load on selection

[Shai Berger]

Package: firefox
Version: 62.0~b10-1
Severity: normal

Dear Maintainer,

Basically, I ran into the same issue as described in 
https://support.mozilla.org/en-US/questions/1155656
and the workaround described there solved my problem.

I don't think it's relevant, but just in case: I have only
ran Firefox 62 under a user different than the owner of the
X session.

The setting "tabs.remote.autostart.2" mentioned there appears
already in firefox-esr (52), and seems to be set to true by
user, but I have never touched it on purpose, so this may (or
may not) be a packaging issue.

-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: buster/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages firefox depends on:
ii  debianutils   4.8.6
ii  fontconfig2.13.0-5
ii  libatk1.0-0   2.28.1-1
ii  libc6 2.27-5
ii  libcairo-gobject2 1.15.10-3
ii  libcairo2 1.15.10-3
ii  libdbus-1-3   1.12.10-1
ii  libdbus-glib-1-2  0.110-2
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-8
ii  libfontconfig12.13.0-5
ii  libfreetype6  2.8.1-2
ii  libgcc1   1:8.2.0-1
ii  libgdk-pixbuf2.0-02.36.12-1
ii  libglib2.0-0  2.56.1-2
ii  libgtk-3-03.22.30-2
ii  libjsoncpp1   1.7.4-3
ii  libnspr4  2:4.19-3
ii  libnss3   2:3.38-1
ii  libpango-1.0-01.42.1-2
ii  libsqlite3-0  3.24.0-1
ii  libstartup-notification0  0.12-5
ii  libstdc++68.2.0-1
ii  libvpx5   1.7.0-3
ii  libx11-6  2:1.6.5-1
ii  libx11-xcb1   2:1.6.5-1
ii  libxcb-shm0   1.13-2
ii  libxcb1   1.13-2
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.15-2
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages firefox recommends:
ii  libavcodec57  7:3.4.3-1
ii  libavcodec58  7:4.0.2-1

Versions of packages firefox suggests:
ii  fonts-lmodern  2.004.5-3
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-6
ii  libgssapi-krb5-2   1.16-2
ii  libgtk2.0-02.24.32-2

-- no debconf information

Bug#902932: cinnamon: System-tray language switcher cannot be used via mouse

[Shai Berger]

Package: cinnamon
Version: 3.6.7-8
Severity: normal
Tags: l10n

Dear Maintainer,

I use two languages -- English and Hebrew, and so I use two keyboard layouts.
I usually switch between them using a keyboard shortcut, and that mostly works.
But I've found that the language can only be switched when the focus is in a
window where one may edit text. This means that if I click a window decoration,
language cannot be switched with the shortcut; it also means that choosing a
language with the mouse, using the pop-up that springs when the icon from the
system try is clicked, never works.

On a more minor tone -- I sometimes run apps as a different user; when these
have focues, the layout switcher apparently fails to realize that it is in
"editable space", and again, language cannot be switched.

In case this matters, the apps in question include Konsole and Firefox, and
I start-as-other-user with kdesudo (yes, I'm a relatively recent convert from
KDE).

Thanks,
Shai.

-- System Information:
Debian Release: buster/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cinnamon depends on:
ii  cinnamon-common  3.6.7-8
ii  cinnamon-control-center  3.6.5-2
ii  cinnamon-desktop-data3.6.2-2
ii  cinnamon-screensaver 3.6.1-2
ii  cinnamon-session 3.6.1-1
ii  cinnamon-settings-daemon 3.6.2-1
ii  cjs  3.2.0-3
ii  cups-pk-helper   0.2.6-1+b1
ii  dconf-gsettings-backend [gsettings-backend]  0.28.0-2
ii  gir1.2-accountsservice-1.0   0.6.45-1
ii  gir1.2-caribou-1.0   0.4.21-5
ii  gir1.2-clutter-1.0   1.26.2+dfsg-4
ii  gir1.2-cmenu-3.0 3.6.0-1
ii  gir1.2-cogl-1.0  1.22.2-3
ii  gir1.2-cvc-1.0   3.6.2-2
ii  gir1.2-gdkpixbuf-2.0 2.36.11-2
ii  gir1.2-gkbd-3.0  3.26.0-3
ii  gir1.2-glib-2.0  1.56.1-1
ii  gir1.2-gnomedesktop-3.0  3.28.2-1
ii  gir1.2-gtk-3.0   3.22.30-2
ii  gir1.2-gtkclutter-1.01.8.4-3
ii  gir1.2-keybinder-3.0 0.3.2-1
ii  gir1.2-meta-muffin-0.0   3.6.0-1
ii  gir1.2-nm-1.01.10.8-1
ii  gir1.2-nma-1.0   1.8.12-2
ii  gir1.2-notify-0.70.7.7-3
ii  gir1.2-pango-1.0 1.42.1-2
ii  gir1.2-polkit-1.00.105-20
ii  gir1.2-soup-2.4  2.62.1-1
ii  gir1.2-upowerglib-1.00.99.8-1
ii  gir1.2-xapp-1.0  1.0.4-2
ii  gkbd-capplet 3.26.0-3
ii  gnome-backgrounds3.28.0-1
ii  gnome-themes-extra   3.28-1
ii  gnome-themes-standard3.28-1
ii  gsettings-desktop-schemas3.28.0-1
ii  iso-flags-png-320x2401.0.2-1
ii  libatk-bridge2.0-0   2.26.2-1
ii  libatk1.0-0  2.28.1-1
ii  libc62.27-3
ii  libcairo21.15.10-3
ii  libcinnamon-menu-3-0 3.6.0-1
ii  libcjs0  3.2.0-3
ii  libclutter-1.0-0 1.26.2+dfsg-4
ii  libcogl-pango20  1.22.2-3
ii  libcogl-path20   1.22.2-3
ii  libcogl201.22.2-3
ii  libcroco30.6.12-2
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libgirepository-1.0-11.56.1-1
ii  libgl1   1.0.0+git20180308-3
ii  libglib2.0-0 2.56.1-2
ii  libglib2.0-bin   2.56.1-2
ii  libgstreamer1.0-01.14.1-1
ii  libgtk-3-0   3.22.30-2
ii  libmuffin0   3.6.0-1
ii  libpango-1.0-0   1.42.1-2
ii  libpangocairo-1.0-0  1.42.1-2
ii  libstartup-notification0 0.12-5
ii  libx11-6 2:1.6.5-1
ii  libxfixes3   1:5.0.3-1

Bug#888831: Is there really a bug in Firefox here?

[Shai Berger]

I'm using testing (Buster), I've had Firefox pinned for some time
because of this bug, and today I found it was for no good reason --
libnss3 is at 2:3.36.1-1, and Firefox has no problem accessing websites
using HTTPS.

As the OP said, there seems to have been a problem only with a specific
version of libbss3.

The dependency in firefox-esr is not set to this specific version, so
the package does work with newer (and some older) versions of libnss3;
the only thing the firefox-esr maintainers could possibly do is add a
(!= 2:3.33-1) to the dependencies, and since 2:3.33-1 is not the
current version on any of the Debian releases and architectures (and
seems like never will be), it seems like holding a bug against
firefox-esr, with severity "grave", is a bit of an overkill.

Thanks,
Shai.

Bug#887697: akregator: back up feed list when it's good

[Shai Berger]

Package: akregator
Version: 4:17.08.3-1
Severity: wishlist

Dear Maintainer,

I had a power outage. Later, when I started Akregator, I was greeted with a
message telling me that the feed list is corrupted, and a backup has been
made.

So I looked at the data folder, and saw:

~/.local/share/akregator/data$ ls -l
total 20
-rw-r--r-- 1 shai shai 2229 Jan 19 08:16 feeds.opml
-rw-r--r-- 1 shai shai1 Jan 19 08:13 feeds.opml~
-rw-r--r-- 1 shai shai0 Aug  6  2016 feeds.opml-backup.1430053506
-rw-r--r-- 1 shai shai1 Jan 19 08:11 feeds.opml-backup.1516342263
-rw-r--r-- 1 shai shai 3690 Aug  6  2016 feeds.opml.default-debian-kde
-rw--- 1 shai shai0 Aug  6  2016 feeds.opmlhD1662.new
-rw-r--r-- 1 shai shai   65 Aug  6  2016 tagset.xml

So, it appears that akregator tries to back up feeds.opml, but for
some reason only does it when the file is known to be bad. Thus,
I have a backup of a 1-byte version of the file.

I'll go see if I have a real backup somewhere.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IL.UTF-8, LC_CTYPE=en_IL.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages akregator depends on:
ii  kinit5.37.0-2
ii  kio  5.37.0-2
ii  libc62.26-2
ii  libgcc1  1:7.2.0-19
ii  libkf5codecs55.37.0-2
ii  libkf5completion55.37.0-2
ii  libkf5configcore55.37.0-2
ii  libkf5configgui5 5.37.0-2
ii  libkf5configwidgets5 5.37.0-2
ii  libkf5coreaddons55.37.0-3
ii  libkf5crash5 5.37.0-2
ii  libkf5grantleetheme-plugins  17.08.3-1
ii  libkf5grantleetheme5 17.08.3-1
ii  libkf5i18n5  5.37.0-2
ii  libkf5iconthemes55.37.0-2
ii  libkf5jobwidgets55.37.0-2
ii  libkf5kcmutils5  5.37.0-2
ii  libkf5kiocore5   5.37.0-2
ii  libkf5kiogui55.37.0-2
ii  libkf5kiowidgets55.37.0-2
ii  libkf5kontactinterface5  17.08.3-1
ii  libkf5libkdepim-plugins  4:17.08.3-1
ii  libkf5libkdepim5 4:17.08.3-1
ii  libkf5messageviewer5 4:17.08.3-1
ii  libkf5mimetreeparser54:17.08.3-1
ii  libkf5notifications5 5.37.0-2
ii  libkf5notifyconfig5  5.37.0-2
ii  libkf5parts5 5.37.0-2
ii  libkf5pimcommon-plugins  4:17.08.3-1
ii  libkf5pimcommon5 4:17.08.3-1
ii  libkf5pimtextedit5   17.08.3-1
ii  libkf5service-bin5.37.0-2
ii  libkf5service5   5.37.0-2
ii  libkf5syndication5   17.08.3-1
ii  libkf5textwidgets5   5.37.0-2
ii  libkf5webengineviewer5   4:17.08.3-1
ii  libkf5widgetsaddons5 5.37.0-2
ii  libkf5xmlgui55.37.0-2
ii  libqt5core5a 5.9.2+dfsg-6
ii  libqt5dbus5  5.9.2+dfsg-6
ii  libqt5gui5   5.9.2+dfsg-6
ii  libqt5network5   5.9.2+dfsg-6
ii  libqt5printsupport5  5.9.2+dfsg-6
ii  libqt5webenginewidgets5  5.9.2+dfsg-2
ii  libqt5widgets5   5.9.2+dfsg-6
ii  libqt5xml5   5.9.2+dfsg-6
ii  libstdc++6   7.2.0-19

akregator recommends no packages.

akregator suggests no packages.

-- no debconf information

Bug#683662: lightdm does not remember which session was selected

[Shai Berger]

Package: lightdm
Version: 1.18.3-1
Followup-For: Bug #683662

Dear Maintainer,

What Adrian said. 

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IL.UTF-8, LC_CTYPE=en_IL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lightdm depends on:
ii  adduser3.115
ii  dbus   1.10.14-1
ii  debconf [debconf-2.0]  1.5.59
ii  libaudit1  1:2.6.7-1
ii  libc6  2.24-8
ii  libgcrypt201.7.5-2
ii  libglib2.0-0   2.50.2-2
ii  libpam-systemd 232-8
ii  libpam0g   1.1.8-3.5
ii  libxcb11.12-1
ii  libxdmcp6  1:1.1.2-1.1
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.2-1

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+18

Versions of packages lightdm suggests:
ii  accountsservice  0.6.43-1
ii  upower   0.99.4-4
pn  xserver-xephyr   

-- debconf information:
  lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm

Bug#851693: xfce4-clipman: xfce4-popup-clipman doesn't open with a hotkey

[Shai Berger]

Package: xfce4-clipman
Version: 2:1.4.1-1
Severity: normal

Dear Maintainer,

xfce4-popup-clipman doesn't open with a hotkey.
I have a shortcut assigned in keyboard settings.
When i run xfce4-popup-clipman from the terminal or via the app finder,
it opens as expected, but not with my hotkey.

This has been reported upstream, https://bugzilla.xfce.org/show_bug.cgi?id=12868
but I think the issue is really downstream as explained in
Comment 6 (https://bugzilla.xfce.org/show_bug.cgi?id=12868#c6)

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xfce4-clipman depends on:
ii  libc6   2.24-8
ii  libgdk-pixbuf2.0-0  2.36.2-1
ii  libglib2.0-02.50.2-2
ii  libgtk-3-0  3.22.5-1
ii  libqrencode33.4.4-1+b1
ii  libx11-62:1.6.4-2
ii  libxfce4ui-2-0  4.12.1-2
ii  libxfce4util7   4.12.1-3
ii  libxfconf-0-2   4.12.1-1
ii  libxtst62:1.2.3-1

xfce4-clipman recommends no packages.

xfce4-clipman suggests no packages.

-- no debconf information

Bug#767354: hplip: looks like a permissions issue

[Shai Berger]

Package: hplip
Version: 3.16.11+repack0-1
Followup-For: Bug #767354

Dear Maintainer,

I saw exactly the same error as the original poster. I was
able to resolve it by

 $ sudo chgrp lp ~/.hplip
 $ chmod g+w ~/.hplip

The issue turns out to have been reported upstream:
https://bugs.launchpad.net/hplip/+bug/702934

and I added a slightly more detailed description there.

(I added the hp-check output in hopes that it could be
useful, but as you probably know, a lot of its error messages
are suspicious)

Thanks for your good work,
   Shai.

-- Package-specific info:
Saving output in log file: /home/shai/.hplip/hp-check.log

HP Linux Imaging and Printing System (ver. 3.16.11)
Dependency/Version Check Utility ver. 15.1

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Note: hp-check can be run in three modes:
1. Compile-time check mode (-c or --compile): Use this mode before compiling 
the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper 
 
dependencies are installed to successfully compile HPLIP.   
  
2. Run-time check mode (-r or --run): Use this mode to determine if a distro 
supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball 
has
the proper dependencies installed to successfully run.  
  
3. Both compile- and run-time check mode (-b or --both) (Default): This mode 
will check both of the above cases (both compile- and run-time dependencies).   
 

Check types:
  
a. EXTERNALDEP - External Dependencies  
  
b. GENERALDEP - General Dependencies (required both at compile and run time)
  
c. COMPILEDEP - Compile time Dependencies   
  
d. [All are run-time checks]
  
PYEXT SCANCONF QUEUES PERMISSION
  

Status Types:
OK
MISSING   - Missing Dependency or Permission or Plug-in
INCOMPAT  - Incompatible dependency-version or Plugin-version

warning: 2-stretch/sid version is not supported. Using 2-8.6 versions 
dependencies to verify and install...

---
| SYSTEM INFO |
---

 Kernel: 4.8.0-2-amd64 #1 SMP Debian 4.8.11-1 (2016-12-02) GNU/Linux
 Host: deblack
 Proc: 4.8.0-2-amd64 #1 SMP Debian 4.8.11-1 (2016-12-02) GNU/Linux
 Distribution: 2 stretch/sid
 Bitness: 64 bit


---
| HPLIP CONFIGURATION |
---

HPLIP-Version: HPLIP 3.16.11
HPLIP-Home: /usr/share/hplip
warning: HPLIP-Installation: Auto installation is not supported for 2 distro  
stretch/sid version 

Current contents of '/etc/hp/hplip.conf' file:
# hplip.conf.  Generated from hplip.conf.in by configure.

[hplip]
version=3.16.11

[dirs]
home=/usr/share/hplip
run=/var/run
ppd=/usr/share/ppd/hplip/HP
ppdbase=/usr/share/ppd/hplip
doc=/usr/share/doc/hplip
html=/usr/share/doc/hplip-doc
icon=no
cupsbackend=/usr/lib/cups/backend
cupsfilter=/usr/lib/cups/filter
drv=/usr/share/cups/drv
bin=/usr/bin
apparmor=/etc/apparmor.d
# Following values are determined at configure time and cannot be changed.
[configure]
network-build=yes
libusb01-build=no
pp-build=yes
gui-build=yes
scanner-build=yes
fax-build=yes
dbus-build=yes
cups11-build=no
doc-build=yes
shadow-build=no
hpijs-install=yes
foomatic-drv-install=yes
foomatic-ppd-install=yes
foomatic-rip-hplip-install=no
hpcups-install=yes
cups-drv-install=yes
cups-ppd-install=no
internal-tag=3.16.11
restricted-build=no
ui-toolkit=qt5
qt3=no
qt4=no
qt5=yes
policy-kit=yes
lite-build=no
udev_sysfs_rules=no
hpcups-only-build=no
hpijs-only-build=no
apparmor_build=no


Current contents of '/var/lib/hp/hplip.state' file:
Plugins are not installed. Could not access file: No such file or directory

Current contents of '~/.hplip/hplip.conf' file:
[commands]
scan = /usr/bin/simple-scan %SANE_URI%

[fax]
email_address = 
voice_phone = 

[installation]
date_time = 01/06/17 00:49:37
version = 3.16.11

[last_used]
device_uri = "hpfax:/net/OfficeJet_6950?ip=192.168.11.25"
printer_name = OfficeJet_6950_fax
working_dir = .

[polling]
device_list = 

Bug#830523: xserver-xorg-input-libinput: segfaults upon plugging back a USB keyboard when session is inactive

[Shai Berger]

forwarded 830523 https://bugs.freedesktop.org/show_bug.cgi?id=97117
retitle 830523
tags 830523 + upstream fixed-upstream
thanks

It seems this bug has been  reported and even recently fixed upstream. The 
Freedesktop.org bug title is about bluetooth, but it appears to share the 
underlying cause with our USB case, and later comments include a scenario 
exactly repeating the one described here.

Bug#830523: Easy workaround found

[Shai Berger]

Hello,

I was able to find an easy workaround for this problem:

0) Make sure xserver-xorg-input-evdev (or some other input driver to handle 
the keyboard and mouse) is installed. If your system is not brand-new, they 
are probably installed anyway

1) Disable the configuration that causes libinput to be used:

sudo mv /usr/share/X11/xorg.conf.d/40-libinput.conf{,.disabled}

2) Restart X

Maintainers: Do you know if this has been reported upstream? Conversely, do 
you know of a reason to suspect that this is a Debian-only problem?

Thanks for your good work,

Shai.

Bug#830523: I was apparently wrong...

[Shai Berger]

After checking a little more, it looks like it does happen every time the USB 
device is reconnected.

Further, there is no need for two X servers to be running -- one is enough, 
provided that it is made not active. That is, to reproduce:

0. Make sure your keyboard/mouse are connected via USB
1. Open a normal X session, log in
2. Go to a console tty (depending on your setup, you can probably do this by 
pressing ctrl+alt+F2)
3. Diconnect and reconnect your keyboard/mouse

Expected Results: Nothing special happens
Actual Results: X session segfaults

HTH,
Shai.

Bug#830517: lightdm: Cannot start sessions after first, requires lighdm restart

[Shai Berger]

Package: lightdm
Version: 1.18.2-1
Severity: normal

Dear Maintainer,

I am encountering difficulties with starting any session beyond the first.
Whether I try to start a second session while the first is still active (that
is, to switch to another user) or after the first user logged out, I get an
error message about DBus not being accessible, and the the (new) session is
ended before anything starts.

If I restart lightdm (from a text console, tty1) then I can log in again, but
again, only once.

FWIW, I'm a KDE/Plasma user; I've had similar and worse issues with sddm, so
the problem may actually be in some other component (systemd?), however, I
currently experience it as a lightdm issue and I don't really know how to
debug it further; I don't see anything which seems related in system logs.

Thanks,
Shai.


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lightdm depends on:
ii  adduser3.115
ii  dbus   1.10.8-1
ii  debconf [debconf-2.0]  1.5.59
ii  libaudit1  1:2.6.1-1
ii  libc6  2.23-1
ii  libgcrypt201.7.1-2
ii  libglib2.0-0   2.48.1-1
ii  libpam-systemd 230-5
ii  libpam0g   1.1.8-3.3
ii  libxcb11.11.1-1
ii  libxdmcp6  1:1.1.2-1.1
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.1-2

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+15

Versions of packages lightdm suggests:
ii  accountsservice  0.6.40-3
ii  upower   0.99.4-3

-- debconf information:
* shared/default-x-display-manager: lightdm
  lightdm/daemon_name: /usr/sbin/lightdm

Bug#828923: kde-l10n-he: current version incompatible with old kdenlive-data

[Shai Berger]

Package: kde-l10n-he
Version: 4:16.04.2-2
Severity: important
Tags: l10n

Dear Maintainer,

I am now upgrading a system after a very long time. During the installation, I 
ran
into this error:

Unpacking kde-l10n-he (4:16.04.2-2) over (4:4.14.0-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/kde-l10n-he_4%3a16.04.2-2_all.deb (--unpack):
 trying to overwrite '/usr/share/locale/he/LC_MESSAGES/kdenlive.mo', which is 
also in package kdenlive-data 0.9.10-2

I am guessing that this means the incompatibility between kde-l10n-he 
4:16.04.2-2 and
kdenlive-data 0.9.10-2 is not recorded, or else apt would have found the 
correct order
for doing things (it needed to upgrade kdenlive anyway).

While this is in itself a minor issue, the only way I found to overcome it was 
to remove
kdenlive using dpkg; so, it essentially breaks the upgrade tools. Hence I 
marked it important.
If this is wrong, accept my apologies.

Thanks,
Shai.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kde-l10n-he depends on:
iu  libkdecore5  4:4.14.21-1
iu  libkf5i18n5  5.23.0-1

kde-l10n-he recommends no packages.

Versions of packages kde-l10n-he suggests:
ii  kde-standard  5:84

-- no debconf information

Bug#731318: aptitude: keeps switching a package between architectures on safe-upgrade

[Shai Berger]

Hi Manuel,

On Tuesday 08 March 2016 00:52:36 Manuel A. Fernandez Montecelo wrote:
> 
> Did you keep observing this problem in recent years/releases?
> 

I'm not sure when was the last time I saw the problem; anyway, since the last 
major ABI transitions (gcc 5 together with KDE5, IIRC) I have not updated the 
system regularly and so I cannot comment.

Thanks,
Shai.

Bug#784062: openshot: Trying to import image sequence from new location segfaults

[Shai Berger]

Package: openshot
Version: 1.4.3-1.1
Severity: normal

Dear Maintainer,

1) Start openshot
2) Click File - Import image sequence
3) In the Image Folder: selection, select Other...

Expected result: A file selection dialog opens

Actual result: Program crashes. When started from the command line, the 
following exception is reported:

/usr/lib/pymodules/python2.7/openshot/windows/SimpleGtkBuilderApp.py:49: 
GtkWarning: gtk_tree_model_filter_get_value: assertion 'GTK_TREE_MODEL_FILTER 
(model)-priv-stamp == iter-stamp' failed
  gtk.main()
  /usr/lib/pymodules/python2.7/openshot/windows/SimpleGtkBuilderApp.py:49: 
Warning: /build/glib2.0-etimD8/glib2.0-2.44.0/./gobject/gtype.c:4268: type id 
'0' is invalid
gtk.main()
/usr/lib/pymodules/python2.7/openshot/windows/SimpleGtkBuilderApp.py:49: 
Warning: can't peek value table for type 'invalid' which is not currently 
referenced
  gtk.main()
  Segmentation fault
  

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openshot depends on:
ii  fontconfig   2.11.0-6.3
ii  gtk2-engines-pixbuf  2.24.25-3
ii  librsvg2-common  2.40.5-1
ii  melt 0.9.6-1
ii  python   2.7.9-1
ii  python-gtk2  2.24.0-4
ii  python-httplib2  0.9+dfsg-2
ii  python-imaging   2.6.1-2
ii  python-mlt   0.9.6-1
ii  python-pygoocanvas   0.14.1-1+b3
ii  python-support   1.0.15
ii  python-xdg   0.25-4

Versions of packages openshot recommends:
ii  frei0r-plugins  1.4-3
ii  openshot-doc1.4.3-1.1

Versions of packages openshot suggests:
ii  blender   2.74+dfsg0-2
ii  inkscape  0.91-4

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#777198: command-not-found: refers to wrong package for docker

[Shai Berger]

Package: command-not-found
Version: 0.2.38-1
Severity: normal

Dear Maintainer,

When I tried to run docker, I got this output:

$ docker pull doesnt/matter
The program 'docker' is currently not installed.  To run 'docker' please ask 
your administrator to install the package 'docker'
docker: command not found

The package 'docker' provides the command 'wmdocker', a panel applet for KDE
and GNOME.

The package with the 'docker' command is 'docker.io'.

Thanks.

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages command-not-found depends on:
ii  apt-file2.5.4
ii  lsb-release 4.1+Debian13+nmu1
ii  python  2.7.8-2
ii  python-gdbm 2.7.8-2+b1
ii  python-support  1.0.15

command-not-found recommends no packages.

command-not-found suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#735261: mutiple upstream bugs

[Shai Berger]

On Monday 19 January 2015 00:54:41 Michael Gilbert wrote:
 On Sun, Jan 18, 2015 at 5:44 PM, Shai Berger wrote:
  I am asking about serious vs. non-serious because those are the terms
  used by reportbug (non-serious data loss is a reason to mark a bug
  grave).
 
 Both grave and critical refer to actual data loss.  Using the term
 serious isn't particularly useful since that falls outside those two
 categories anyway.
 

Again, you're being tautological, repeating your terms rather than defining 
them.

 
 The description of the important may help correct the ongoing
 misperception: https://www.debian.org/Bugs/Developer#severities
 

In my book, a major effect on the usability of a package means I can't do 
what I want (easily enough). The case here -- I told the program something 
and it forgot it -- is data loss.

Your answers above indicate that easy recreatability does not make something 
not data loss; and yet this case is not data loss because it is just easily 
recreatable bits. The only interpretation I find consistent with that is 
single bits are not data -- which makes no sense to me.

Thanks for your patience,
Shai.
 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#735261: mutiple upstream bugs

[Shai Berger]

On Sunday 18 January 2015 23:51:01 Michael Gilbert wrote:
 On Sun, Jan 18, 2015 at 4:14 PM, Shai Berger s...@platonix.com wrote:
  Those easily recreatable bits represent a significant part of my mail
  workflow. Almost any data can be recreated by repeating the work that
  created it. Your claims essentially come down to workflows based on
  'read status' are invalid or unimportant. Well, they're damned
  important to me.
 
 Then you're either choosing the wrong mail client or not doing enough
 to help upstream scratch that itch.
 

Certainly; but that's hardly what we're discussing here.

  I suspect that this discussion is going nowhere, but I still would like
  you to answer one more question: Can you describe the difference between
  serious and non-serious data loss?
 
 The difference is actual vs. perceived data loss.
 

I am asking about serious vs. non-serious because those are the terms used 
by reportbug (non-serious data loss is a reason to mark a bug grave).

Calling data-loss which you find unimportant perceived, not  actual isn't 
helpful at all. You're playing with terms rather than making points.

Shai.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#735261: mutiple upstream bugs

[Shai Berger]

On Sunday 18 January 2015 21:46:52 Michael Gilbert wrote:
 On Fri, Jan 16, 2015 at 8:07 AM, Shai Berger wrote:
  On Friday 16 January 2015 01:45:53 Michael Gilbert wrote:
   However, the problem reported here is not a usability problem. If a
   mail client losing record of which mails have been read and which
   haven't isn't non-serious data loss, I can't tell what is.
  
  Actual data loss.
  
  So, the bits marking messages as read or unread are not data? What,
  pray tell, are they?
 
 Easily recreatable bit flags.
 

So data isn't lost if it is easily recreatable? Really?

By that argument, there really shouldn't be any data loss bugs, because all 
data should be easily restorable from backup.

Those easily recreatable bits represent a significant part of my mail 
workflow. Almost any data can be recreated by repeating the work that created 
it. Your claims essentially come down to workflows based on 'read status' are 
invalid or unimportant. Well, they're damned important to me.

I suspect that this discussion is going nowhere, but I still would like you to 
answer one more question: Can you describe the difference between serious and 
non-serious data loss?

Thanks,
Shai.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#735261: mutiple upstream bugs

[Shai Berger]

On Friday 16 January 2015 01:45:53 Michael Gilbert wrote:
  However, the problem reported here is not a usability problem. If a mail
  client losing record of which mails have been read and which haven't
  isn't non-serious data loss, I can't tell what is.
 
 Actual data loss.
 

So, the bits marking messages as read or unread are not data? What, pray 
tell, are they?


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#735261: mutiple upstream bugs

[Shai Berger]

Hi Michael,

On Wednesday 14 January 2015 04:45:16 Michael Gilbert wrote:
 
 This is a usability problem, so it doesn't really qualify as release
 critical.

Debian developers get to call the severity of bugs in general, and the 
criticality for a specific release in particular.

However, the problem reported here is not a usability problem. If a mail 
client losing record of which mails have been read and which haven't isn't 
non-serious data loss, I can't tell what is.

Respectfully,

Shai.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#727800: kmail: KMail goes bonkers following Qt update

[Shai Berger]

So, I've tried again, this time restarting Akonadi when the migration script 
said it was done. I tried two variations:

1) akonadictl restart before pressing ok on the window showing the kmail 
resource migration. Surprisingly, this did not cause KMail to shut down. It 
also didn't really work -- I ended up with two KMail Folders collections, 
repeated item belongs to two top-level collections error messages, and other 
misbehaviors. The two KMail Folders collections contained, each, all my 
folders, but it seemed the folders didn't quite work in any of them; I think 
inbox looked like it had the right contents in one, but I couldn't get 
contents in any other. Maybe I just didn't wait enough (see below).

2) When the migration script says it's done, press ok, close KMail, and then 
restart Akonadi. This worked -- in the sense that I got a single KMail 
Folders collection with all my folders. However, it postponed the action of 
actual migration -- when I tried to access the folders, only then KMail did 
the actual loading and syncing or whatever takes so long. Opening a folder 
with ~22000 mails took well over 5 minutes, and during these minutes, no other 
mail could be retrieved (even from the inbox which had already been synced 
before).

Still, no filters were migrated. None whatsoever. I have ~30 of them.

I am writing this message from the upgraded user -- as a test to see if the 
other bug I'm  experiencing (sending requires akonadi restart) is specific to 
my regular user. I encountered another issue -- although my Identity has 
sign messages automatically set to False, when I started writing the sign 
message option was on. Perhaps it was on in the last message I sent before 
doing the backup from which this user is restored, I'm not sure. Either way, 
it was surprising.

Hope this helps,
Shai.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#727800: kmail: KMail goes bonkers following Qt update

[Shai Berger]

On Sunday 14 December 2014 21:35:45 Diane Trout wrote:
 The migration bug is the one kmail bug I've been able to reproduce
 repeteadly.
 
 I have a work-around patch that basically does
 
 akonadictl restart
 
 when the migrator says Migration Done

Oh, I haven't followed that advice. I'll try again, hopefully this week.

 
 I haven't figured out how to reproduce the other kmail bugs.
 
 And yes, one of KDE's design choices is that everything is integrated, so
 not shipping kmail2 would be very difficult if not impossible.
 
 You might also want to check out the current versions of evolution or
 thunderbird. Both are also quite decent mail clients.
 

This is becoming increasingly off-topic, I'll respond on the mailing list.

Thanks,
Shai.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#727800: kmail: KMail goes bonkers following Qt update

[Shai Berger]

Finally got to it.

The upgrade was not smooth at all; the update script ended quickly enough, but 
the real upgrade only happened when I opened KMail. I had the same experience 
as last time -- KMail shows blank folders, nothing seems to be going on, 
except if you look for it. At some point KMail's little operation in 
progress bar (bottom right progress bar when doing something) lit up with 0%. 
I tried to click the up-arrow next to it, to see what KMail was doing. After 
that, looking from another X session, I saw mysqld, akonadiserver and kwin(!) 
all taking 100% CPU (I have four cores). Pretty soon after that, kwin managed 
to make the X server completely unresponsive -- not even Ctrl-Alt-Fn to go to 
another session. This happened twice, so I'm calling it reproducible. Perhaps 
it should just be reported elsewhere -- I suspect a grave bug in the upgrade.

It seems like the mails themselves made it through the upgrade; I haven't yet 
verified the filters and identities. The computer that runs Sid serves the 
whole 
family, and I had to reboot it to restore it to functional after running the 
imported user.

A little off-topic, w.r.t. a comment Lisandro made earlier -- I understand that 
not shipping Akonadi is not an option. Would you say the same about KMail2?

Thanks,
Shai.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#772612: kmail: Sent message opened for editing by default and can be removed from sent by saving

[Shai Berger]

Well. Logoff, logon, and inbox is back to normal behavior (double-clicking the 
message in the list opens it for reading, not editing). Sent-mail is still 
exactly as described.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#772612: not reproducable

[Shai Berger]

Hi,

On Sat, 13 Dec 2014 12:37:23 +0100 Sandro =?ISO-8859-1?Q?Knau=DF?= 
b...@sandroknauss.de wrote:
 I would suggest you test with a clean user and/or check all identities. It 
 sounds like one identity uses the sent folder as outbox.
 

There is no UI way to set the outbox for an identity; one may only choose the 
sent-mail folder, the drafts folder and the templates folder. I couldn't find 
the identities in kmail2rc, so I don't even know how to do it with non-UI.

Nevertheless, I checked those folders on all identities, and there was one 
anomaly (probably a remainder from the problem reported in [1]) -- one 
identity (which I haven't used for sending in years) had its sent-folder set 
to a sub-folder of inbox. I set it straight, and things seem to be normal now.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727800#10

Thanks,
Shai.

PS: This still makes me very uncomfortable: If KMail2's config can be easily 
broken in ways that lead to data loss -- and by easily I mean without user 
intervention -- is there a way to run a health check?

I don't feel it is right to close this bug without understanding what happened 
and how it can be prevented, so I'm not closing it myself; but I won't object 
if you guys decide to close it.

Shai.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#772612: kmail: Sent message opened for editing by default and can be removed from sent by saving

[Shai Berger]

Hi,

On Tuesday 09 December 2014 11:12:42 Diane Trout wrote:
 Hello,
 
 I tried to duplicate this with 4.14.1.
 
 I had to hit T in order to actually edit the message, and then if I make a
 change and save it, the save button says Save to Draft, for me the
 modified message moved to the Drafts folder.
 
 By any chance is the modified message now in the draft folder for you?

Yes, it is. I might have considered it not-really-data-loss, if the behavior 
had only been specifically triggered by editing the message. But:

A) I definitely (just checked again) didn't need to press T (which is labeled 
in the menu as Edit message). On the other hand, double-click behaves as T 
for me in other folders as well. Is there a setting I messed up? I couldn't 
find anything looking relevant.

B) I expect behavior in sent-messages to be the same as, say, inbox, where the 
message, even if selected for editing, is not changed or removed, but a new 
copy of it is created and edited.

The message moving to the draft folder is already losing its sent status and 
sent date/time, and is highly likely to lose the message itself as well (if 
the user did not expect or notice that the draft takes the place of the old 
sent message).

Thanks,
Shai.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#772612: kmail: Sent message opened for editing by default and can be removed from sent by saving

[Shai Berger]

Package: kmail
Version: 4:4.14.2-2
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

Double-click a message in any folder; unlike in kmail1, the message
opens as editable (in kmail1 this was only true for Outbox).

However, if the message is opened from the sent-mail folder, then --
just like with outbox -- it is also removed from the list. When you
close the message, as with any editable, you are offered to discard
the changes or save as draft. If you discard, all is well; but if
you save as draft, it is removed permanently from the sent folder,
losing the data that the message was sent.


-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kmail depends on:
ii  kde-runtime   4:4.14.2-1
ii  kdepim-runtime4:4.14.2-2
ii  kdepimlibs-kio-plugins4:4.14.2-2
ii  libakonadi-calendar4  4:4.14.2-2
ii  libakonadi-contact4   4:4.14.2-2
ii  libakonadi-kde4   4:4.14.2-2
ii  libakonadi-kmime4 4:4.14.2-2
ii  libakonadiprotocolinternals1  1.13.0-2
ii  libc6 2.19-13
ii  libcalendarsupport4   4:4.14.2-2
ii  libfollowupreminder4  4:4.14.2-2
ii  libgcc1   1:4.9.2-5
ii  libgpgme++2   4:4.14.2-2
ii  libgrantlee-core0 0.4.0-2
ii  libincidenceeditorsng44:4.14.2-2
ii  libkabc4  4:4.14.2-2
ii  libkalarmcal2 4:4.14.2-2
ii  libkcalcore4  4:4.14.2-2
ii  libkcalutils4 4:4.14.2-2
ii  libkcmutils4  4:4.14.2-4
ii  libkdecore5   4:4.14.2-4
ii  libkdepim44:4.14.2-2
ii  libkdeui5 4:4.14.2-4
ii  libkio5   4:4.14.2-4
ii  libkleo4  4:4.14.2-2
ii  libkmanagesieve4  4:4.14.2-2
ii  libkmime4 4:4.14.2-2
ii  libknewstuff3-4   4:4.14.2-4
ii  libknotifyconfig4 4:4.14.2-4
ii  libkontactinterface4a 4:4.14.2-2
ii  libkparts44:4.14.2-4
ii  libkpgp4  4:4.14.2-2
ii  libkpimidentities44:4.14.2-2
ii  libkpimtextedit4  4:4.14.2-2
ii  libkpimutils4 4:4.14.2-2
ii  libkprintutils4   4:4.14.2-4
ii  libksieveui4  4:4.14.2-2
ii  libktnef4 4:4.14.2-2
ii  libmailcommon44:4.14.2-2
ii  libmailimporter4  4:4.14.2-2
ii  libmailtransport4 4:4.14.2-2
ii  libmessagecomposer4   4:4.14.2-2
ii  libmessagecore4   4:4.14.2-2
ii  libmessagelist4   4:4.14.2-2
ii  libmessageviewer4 4:4.14.2-2
ii  libpimcommon4 4:4.14.2-2
ii  libqt4-dbus   4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtwebkit4  2.3.4.dfsg-3
ii  libsendlater4 4:4.14.2-2
ii  libsolid4 4:4.14.2-4
ii  libstdc++64.9.2-5
ii  libtemplateparser44:4.14.2-2
ii  perl  5.20.1-3

Versions of packages kmail recommends:
ii  gnupg-agent   2.0.26-3
ii  gnupg22.0.26-3
ii  pinentry-gtk2 [pinentry-x11]  0.8.3-2

Versions of packages kmail suggests:
ii  bogofilter 1.2.4+dfsg1-3
pn  clamav | f-prot-installer  none
ii  kaddressbook   4:4.14.2-2
pn  kleopatra  none
ii  procmail   3.22-23
ii  spambayes  1.1b1-1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#760707: Workaround: Restart Akonadi

[Shai Berger]

Package: kmail
Version: 4:4.14.2-2
Followup-For: Bug #760707

Dear Maintainer,

I have recently experienced the send side of the above report,
repeatedly. This may be related to the fact that I tend to leave
my KDE session open for days -- I think that crossing midnight
triggers tris, but I may be wrong about it.

Anyway, repeatedly, kmail quietly puts mails in outbox instead
of sending them, and as described, send queued messages does nothing.
When this happens, restarting kmail alone does not help, but
after restarting Akonadi, when kmail starts again, it does send
from the outbox.

(so this may actually be an Akonadi, rather than KMail, problem,
although I wasn't aware Akonadi is involved in sending mails too).

Thanks,
Shai.
-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kmail depends on:
ii  kde-runtime   4:4.14.2-1
ii  kdepim-runtime4:4.14.2-2
ii  kdepimlibs-kio-plugins4:4.14.2-2
ii  libakonadi-calendar4  4:4.14.2-2
ii  libakonadi-contact4   4:4.14.2-2
ii  libakonadi-kde4   4:4.14.2-2
ii  libakonadi-kmime4 4:4.14.2-2
ii  libakonadiprotocolinternals1  1.13.0-2
ii  libc6 2.19-13
ii  libcalendarsupport4   4:4.14.2-2
ii  libfollowupreminder4  4:4.14.2-2
ii  libgcc1   1:4.9.2-4
ii  libgpgme++2   4:4.14.2-2
ii  libgrantlee-core0 0.4.0-2
ii  libincidenceeditorsng44:4.14.2-2
ii  libkabc4  4:4.14.2-2
ii  libkalarmcal2 4:4.14.2-2
ii  libkcalcore4  4:4.14.2-2
ii  libkcalutils4 4:4.14.2-2
ii  libkcmutils4  4:4.14.2-3
ii  libkdecore5   4:4.14.2-3
ii  libkdepim44:4.14.2-2
ii  libkdeui5 4:4.14.2-3
ii  libkio5   4:4.14.2-3
ii  libkleo4  4:4.14.2-2
ii  libkmanagesieve4  4:4.14.2-2
ii  libkmime4 4:4.14.2-2
ii  libknewstuff3-4   4:4.14.2-3
ii  libknotifyconfig4 4:4.14.2-3
ii  libkontactinterface4a 4:4.14.2-2
ii  libkparts44:4.14.2-3
ii  libkpgp4  4:4.14.2-2
ii  libkpimidentities44:4.14.2-2
ii  libkpimtextedit4  4:4.14.2-2
ii  libkpimutils4 4:4.14.2-2
ii  libkprintutils4   4:4.14.2-3
ii  libksieveui4  4:4.14.2-2
ii  libktnef4 4:4.14.2-2
ii  libmailcommon44:4.14.2-2
ii  libmailimporter4  4:4.14.2-2
ii  libmailtransport4 4:4.14.2-2
ii  libmessagecomposer4   4:4.14.2-2
ii  libmessagecore4   4:4.14.2-2
ii  libmessagelist4   4:4.14.2-2
ii  libmessageviewer4 4:4.14.2-2
ii  libpimcommon4 4:4.14.2-2
ii  libqt4-dbus   4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtwebkit4  2.3.4.dfsg-3
ii  libsendlater4 4:4.14.2-2
ii  libsolid4 4:4.14.2-3
ii  libstdc++64.9.2-4
ii  libtemplateparser44:4.14.2-2
ii  perl  5.20.1-3

Versions of packages kmail recommends:
ii  gnupg-agent   2.0.26-3
ii  gnupg22.0.26-3
ii  pinentry-gtk2 [pinentry-x11]  0.8.3-2

Versions of packages kmail suggests:
ii  bogofilter 1.2.4+dfsg1-3
pn  clamav | f-prot-installer  none
ii  kaddressbook   4:4.14.2-2
pn  kleopatra  none
ii  procmail   3.22-22
ii  spambayes  1.1b1-1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#727800: kmail: KMail goes bonkers following Qt update

[Shai Berger]

Hi, 

On Wednesday 26 November 2014 15:21:15 you wrote:
 
 Hi! As Sandro pointed out, this seems fixed in newer versions. Can you
 please test if this is still an issue for you?
 

I have no means to reconstruct the update as it was. I am using two systems: 
One of them is a sid which I keep updating. Upgrades ever since that woefull 
upgrade have been smooth as far as I can tell, although I haven't been 
watching closely -- ever since kmail2 came into sid, mail there has not been 
really reliable, so if I suddenly have a couple hundred more unread mails, I 
don't think I'd notice. The filters haven't been broken again, as far as I can 
remember.

The other system is mostly testing, but since I use kmail for all my critical 
mail, and kmail2 has not been production-ready (at least before 4.14, though I 
find it hard to trust even now) I have pinned kmail there; I am writing this 
message from kmail 1.13.7 on kde 4.14.2. 

I can try to copy the user from testing to sid and see how the upgrade goes, 
although this would be a lengthy process; would that be helpful?

On a side note -- I see that mails sent to the bug are no longer sent to the 
submitter automatically (except when sent to -submitter specifically); is 
this on purpose? It is a bit of a problem. Feel free to include my address 
explicitly in replies.

Thanks,
Shai.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#735261: kmail2 randomly marks read messages as unread

[Shai Berger]

On Saturday 01 November 2014 00:34:56 Scott Kitterman wrote:
  
  KMail randomly marks single messages as unread. This makes my
  normal workflow, where I leave messages unread for later, deeper
  consideration, tedious and bordering on impossible.
  
  KMail also randomly creates new duplicates of old messages, which
  are (of course) also marked unread.
 
 Is this still an issue with the current kmail (4.14) or akonadi (1.13)?
 

The issue went on-and-off over a lot of time, and in the end I've given up on 
trusting kmail2 with my read/unread marks; so it was hard to me to answer 
immediately.

That said, in the last week there seem to be no spurious duplicates or unread 
markings.

Thanks,
Shai.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#764705: postgresql-9.4: ERROR: The database format changed between beta 2 and 3. Please dump, but how?

[Shai Berger]

Package: postgresql-9.4
Followup-For: Bug #764705

Dear Maintainer,

I, like a previous poster, have this:

postgres@deblack:~$ pg_lsclusters
Ver Cluster Port Status OwnerData directory   Log file
9.3 main5432 online postgres /var/lib/postgresql/9.3/main 
/var/log/postgresql/postgresql-9.3-main.log
9.4 main5433 online postgres /var/lib/postgresql/9.4/main 
/var/log/postgresql/postgresql-9.4-main.log

which means I have both 9.3 and 9.4 installed. Thus, I was a little
worried about the command 

$ zcat 9.4-main.dump.gz | psql -q

in the instructions -- there was no mention of 9.4 in the dump file,
and by default, psql connects to the 9.3 server; thus, I think that
if I had run the command as given, it would have applied to the 9.3
cluster and not the 9.4 one.

I ran it instead as 

$ zcat 9.4-main.dump.gz | psql -p5433

(9.3 runs on 5432, 9.4 on 5433). If I'm wrong, I'd love to be told
about it; otherwise, I suspect the instructions should be modified.

Thanks,
Shai.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages postgresql-9.4 depends on:
ii  libc6  2.19-11
ii  libgssapi-krb5-2   1.12.1+dfsg-10
ii  libldap-2.4-2  2.4.39-1.1+b1
ii  libpam0g   1.1.8-3.1
ii  libpq5 9.4~beta3-2
ii  libssl1.0.01.0.1j-1
ii  libxml22.9.1+dfsg1-4
ii  locales2.19-11
ii  postgresql-client-9.4  9.4~beta3-2
ii  postgresql-common  162
ii  ssl-cert   1.0.35
ii  tzdata 2014h-2

postgresql-9.4 recommends no packages.

Versions of packages postgresql-9.4 suggests:
pn  locales-all none
pn  oidentd | ident-server  none

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#761252: Fixed upstream

[Shai Berger]

reopen 761252
thanks

I hadn't realized that having a Done entry means the bug is closed.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#761252: Fixed upstream

[Shai Berger]

tag 761252 fixed-upstream
thanks

Hi,

The upstream bug has now been fixed. Is there anything I can do to help get the 
fix into Sid? For me, this problem has turned kmail in sid from barely-usable 
to completely-useless.

Thanks,
Shai.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#761252: kmail: Some details please -- same problem encountered

[Shai Berger]

Package: kmail
Version: 4:4.14.0-1
Followup-For: Bug #761252

I wonder what the original reporter meant by problem is elsewhere,
and whether an upstream bug was filed; I couldn't find one.

Anyway, as far as I can see, the problem is live and well: Filter
processing fails to read the List-Id header. I see messages with
list-ids, and the Filter Log Viewer shows the relevant rule not
matched because the List-Id header is (falsely) empty.

I also see the From header reported as empty by the filters,
but the X-Spambayes-Classification header -- added by another
filter -- is read correctly.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kmail depends on:
ii  kde-runtime   4:4.14.0-2
ii  kdepim-runtime4:4.14.0-1
ii  kdepimlibs-kio-plugins4:4.14.0-1
ii  libakonadi-calendar4  4:4.14.0-1
ii  libakonadi-contact4   4:4.14.0-1
ii  libakonadi-kde4   4:4.14.0-1
ii  libakonadi-kmime4 4:4.14.0-1
ii  libakonadiprotocolinternals1  1.13.0-1
ii  libc6 2.19-11
ii  libcalendarsupport4   4:4.14.0-1
ii  libfollowupreminder4  4:4.14.0-1
ii  libgcc1   1:4.9.1-14
ii  libgpgme++2   4:4.14.0-1
ii  libgrantlee-core0 0.4.0-2
ii  libincidenceeditorsng44:4.14.0-1
ii  libkabc4  4:4.14.0-1
ii  libkalarmcal2 4:4.14.0-1
ii  libkcalcore4  4:4.14.0-1
ii  libkcalutils4 4:4.14.0-1
ii  libkcmutils4  4:4.14.0-1
ii  libkdecore5   4:4.14.0-1
ii  libkdepim44:4.14.0-1
ii  libkdeui5 4:4.14.0-1
ii  libkio5   4:4.14.0-1
ii  libkleo4  4:4.14.0-1
ii  libkmanagesieve4  4:4.14.0-1
ii  libkmime4 4:4.14.0-1
ii  libknewstuff3-4   4:4.14.0-1
ii  libknotifyconfig4 4:4.14.0-1
ii  libkontactinterface4a 4:4.14.0-1
ii  libkparts44:4.14.0-1
ii  libkpgp4  4:4.14.0-1
ii  libkpimidentities44:4.14.0-1
ii  libkpimtextedit4  4:4.14.0-1
ii  libkpimutils4 4:4.14.0-1
ii  libkprintutils4   4:4.14.0-1
ii  libksieveui4  4:4.14.0-1
ii  libktnef4 4:4.14.0-1
ii  libmailcommon44:4.14.0-1
ii  libmailimporter4  4:4.14.0-1
ii  libmailtransport4 4:4.14.0-1
ii  libmessagecomposer4   4:4.14.0-1
ii  libmessagecore4   4:4.14.0-1
ii  libmessagelist4   4:4.14.0-1
ii  libmessageviewer4 4:4.14.0-1
ii  libpimcommon4 4:4.14.0-1
ii  libqt4-dbus   4:4.8.6+git64-g5dc8b2b+dfsg-2
ii  libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-2
ii  libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2
ii  libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2
ii  libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2
ii  libqtwebkit4  2.3.2.dfsg-4
ii  libsendlater4 4:4.14.0-1
ii  libsolid4 4:4.14.0-1
ii  libstdc++64.9.1-14
ii  libtemplateparser44:4.14.0-1
ii  perl  5.20.0-6

Versions of packages kmail recommends:
ii  gnupg-agent   2.0.26-2
ii  gnupg22.0.26-2
ii  pinentry-gtk2 [pinentry-x11]  0.8.3-2

Versions of packages kmail suggests:
ii  bogofilter 1.2.4+dfsg1-3
pn  clamav | f-prot-installer  none
ii  kaddressbook   4:4.14.0-1
pn  kleopatra  none
ii  procmail   3.22-22
ii  spambayes  1.1b1-1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#576386: #576386 - nautilus: with --no-desktop and exit_with_last_window==false, a quit menu option is needed

[Shai Berger]

Hi Pedro,
The context in which this came up was that nautilus was started as an 
application and then started to manage the desktop. In the setting which you 
describe, nautilus is explicitly used to manage the desktop; I don't see much 
value in a quit option in this use-case.

Thanks,
Shai.

On 9 באוגוסט 2014 15:54:58 CEST, Pedro Beja altha...@gmail.com wrote:
Control: found -1 3.12.2-1
Control: severity -1 wishlist
kthxbye

Hey Shai,

Well if we enable icons on desktop using gnome-tweak-tool under desktop
tab, a process nautilus -n is always running even if we close the last
window. It makes sense since it's nautilus managing the background.
Otherwise it completely closes the nautilus process when last window is
closed.

I am marking this as found on 3.12.2-1 and wishlist also to have a quit
button (if possible, I have my doubts).

thanks
regards
althaser

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Bug#570314: #570314 - nautilus: --no-desktop should imply exit_with_last_window and !media_automount_open

[Shai Berger]

Hi again,

If you are using nautilus to manage the desktop, then you don't have 
--no-desktop (or whatever that option is called today). This use is irrelevant 
to the bug.

The two bugs asked for seperate (though related) features, but it seems both of 
them can be closed now.

Thanks, Shai.

On 9 באוגוסט 2014 15:58:50 CEST, Pedro Beja altha...@gmail.com wrote:
Control: found -1 3.12.2-1
Control: severity -1 wishlist
kthxbye

Hey Shai,

Well if we enable icons on desktop using gnome-tweak-tool under desktop
tab, a process nautilus -n is always running even if we close the last
window. It makes sense since it's nautilus managing the background.
Otherwise it completely closes the nautilus process when last window is
closed.

I am marking this as found on 3.12.2-1 and wishlist also to have a quit
button (if possible, I have my doubts).

Shouldn't we merge #570314 and #576386 ?

thanks
regards
althaser

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Bug#576386: #576386 - nautilus: with --no-desktop and exit_with_last_window==false, a quit menu option is needed

[Shai Berger]

Hi Pedro,

On Saturday 09 August 2014 03:02:22 Pedro Beja wrote:
 
 this is an old bug.
 
 Could you please still reproduce this issue with newer nautilus version
 like 3.4.2-1+build1 or 3.12.2-1 ?
 

See the bug[1] this was spun off from -- according to my tests with 3.4.2-2, a 
quit menu option is no longer needed because nautilus always seems to exit 
with its last window. As I noted there, I am neither a regular user of 
Nautilus nor of Gnome, so I may not be aware of all configuration options; if 
there still is a configuration where Nautilus stays alive with no windows, then 
in that configuration, a quit menu option is still needed.

Thanks,
Shai.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570314


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#576384: #576384 - nautilus: --no-desktop and media_automount_open==false should imply no automount

[Shai Berger]

Hi there,

On Friday 18 July 2014 17:39:24 you wrote:
 Hey Shai,
 
 this is an old bug.
 
 Could you please still reproduce this issue with newer nautilus version
 like 3.4.2-1+build1 or 3.8.2-3 ?
 

I tried to reproduce:
Version: 3.4.2-2

It seems that even with media_automount and media_automount_open set to true, 
and without the --no-desktop flag, a nautilus opened within a KDE session does 
not automount media anymore. If this is indeed the case, then the bug is moot.

Hope this helps,
Shai.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#570314: #570314 - nautilus: --no-desktop should imply exit_with_last_window and !media_automount_open

[Shai Berger]

Hi,

On Friday 18 July 2014 17:12:42 Pedro Beja wrote:
 
 this is an old bug.
 
 Could you please still reproduce this issue with newer nautilus version
 like 3.4.2-1+build1 or 3.8.2-3 ?
 
With 3.4.2-2, I found nautilus to exit with closure of its last window, with 
or without --no-desktop, and whether exit_with_last_window was set or not.

For my use case, that is good enough. If there is still a configuration where 
nautilus stays alive when its last window is gone, the bug may still be valid.

HTH,
Shai.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#752467: python-virtualenv: what mike said

[Shai Berger]

Package: python-virtualenv
Version: 1.11.6-2
Followup-For: Bug #752467

Dear Maintainer,

The virtualenv package now exists in testing. However, As Mike Hommey
pointed out, nothing installs it by default on a system which used to
get the virtualenv command from python-virtualenv.

Installing virtualenv, indeed, makes the problem go away.

There is a weird pattern of dependencies, though:
  python-virtualenv recommends virtualenv
  virtualenv depends on python3-virtualenv

The package descriptions do seem to make sense:

virtualenv
This is the command line script and manpage.
python-virtualenv
This is the Python 2 version of the library.
python3-virtualenv
This is the Python 3 version of the library.

It seems like the dependencies are confused.

Thanks,
Shai.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-virtualenv depends on:
ii  python 2.7.6-2
ii  python-pip-whl 1.5.6-2
ii  python-pkg-resources   5.4.1-1
ii  python-setuptools-whl  5.4.1-1

Versions of packages python-virtualenv recommends:
ii  virtualenv  1.11.6-2

python-virtualenv suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#752467: python-virtualenv: no command virtualenv

[Shai Berger]

Package: python-virtualenv
Version: 1.11.6-2
Severity: important

Dear Maintainer,

The package is installed, but the command is not found.

$ virtualenv
The program 'virtualenv' is currently not installed.  To run 'virtualenv' 
please ask your administrator to install the package 'python-virtualenv'
virtualenv: command not found
$ aptitude search python-virtualenv
i   python-virtualenv  - Python virtual environment creator  

Further, indeed:
$ dpkg -L python-virtualenv
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/python-virtualenv
/usr/share/doc/python-virtualenv/changelog.Debian.gz
/usr/share/doc/python-virtualenv/copyright
/usr/share/doc/python-virtualenv/index.rst
/usr/share/doc/python-virtualenv/changelog.gz
/usr/share/doc/python-virtualenv/AUTHORS.txt
/usr/lib
/usr/lib/python2.7
/usr/lib/python2.7/dist-packages
/usr/lib/python2.7/dist-packages/virtualenv-1.11.6.egg-info
/usr/lib/python2.7/dist-packages/virtualenv-1.11.6.egg-info/entry_points.txt
/usr/lib/python2.7/dist-packages/virtualenv-1.11.6.egg-info/PKG-INFO
/usr/lib/python2.7/dist-packages/virtualenv-1.11.6.egg-info/dependency_links.txt
/usr/lib/python2.7/dist-packages/virtualenv-1.11.6.egg-info/not-zip-safe
/usr/lib/python2.7/dist-packages/virtualenv-1.11.6.egg-info/top_level.txt
/usr/lib/python2.7/dist-packages/virtualenv.py

I don't see anything here which would be a virtualenv command.

Thanks,
Shai.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-virtualenv depends on:
ii  python 2.7.6-2
ii  python-pip-whl 1.5.6-2
ii  python-pkg-resources   4.0.1-1
ii  python-setuptools-whl  4.0.1-1

Versions of packages python-virtualenv recommends:
pn  virtualenv  none

python-virtualenv suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#752467: python-virtualenv: unstable is ok

[Shai Berger]

Package: python-virtualenv
Followup-For: Bug #752467

Dear Maintainer,

I just realized that, in unstable, the missing command is provided by
a separate package named virtualenv. However, it seems that this
package does not (yet?) exist in testing.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-virtualenv depends on:
ii  python 2.7.6-2
ii  python-pip-whl 1.5.6-2
ii  python-pkg-resources   4.0.1-1
ii  python-setuptools-whl  4.0.1-1

Versions of packages python-virtualenv recommends:
ii  virtualenv  1.11.6-2

python-virtualenv suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#752183: kdm: no login prompt

[Shai Berger]

Package: kdm
Version: 4:4.11.9-1
Severity: important

Dear Maintainer,

After an upgrade, everything seemed fine, but after an unorderly
reboot, kdm no longer shows a login prompt.

kdm.log says:

klauncher(3169) kdemain: No DBUS session-bus found. Check if you have started 
the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(3161)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() 
D-Bus call failed:  Not connected to D-Bus server 

kdmgreet(3161)/kdecore (K*TimeZone*): No time zone information obtained from 
ktimezoned 

So, it seems like the grave #743649 or #746589 might be related, but 
those bugs report failure when logging in -- and I am blocked before
that stage. #743649 implicates a connection to systemd -- I've tried
with both systemd-sysv and sysvinit-core, and there is no difference.

I've also tried to follow the diagnostic steps from #726368 (which
appears to be a dupe of #743649), but:

* dbus is running

message+   647  0.0  0.0  42484  2700 ?Ss   18:21   0:00 
/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile 
--systemd-activation

* lsof also shows it is listening on /var/run/dbus/system_bus_socket

* .xsession-errors is irrelevant (no user-specific login)

I'm attaching the X log; there doesn't seem to be any relevant
problem there, and further, starting a session with

startx startkde -- :1

works fine (with either sysvinit or systemd).

Thanks,
Shai.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kdm depends on:
ii  adduser   3.113+nmu3
ii  consolekit0.4.6-5
ii  debconf [debconf-2.0] 1.5.53
ii  kde-runtime   4:4.13.1-1
ii  kde-wallpapers-default4:4.12.4-1
ii  kde-workspace-kgreet-plugins  4:4.11.9-1
ii  libc6 2.19-3
ii  libck-connector0  0.4.6-5
ii  libdbus-1-3   1.8.4-1
ii  libkdecore5   4:4.13.1-1
ii  libkdeui5 4:4.13.1-1
ii  libkio5   4:4.13.1-1
ii  libknewstuff3-4   4:4.13.1-1
ii  libkworkspace4abi24:4.11.9-1
ii  libpam0g  1.1.8-3
ii  libqimageblitz4   1:0.0.6-4
ii  libqt4-svg4:4.8.6+dfsg-2
ii  libqt4-xml4:4.8.6+dfsg-2
ii  libqtcore44:4.8.6+dfsg-2
ii  libqtgui4 4:4.8.6+dfsg-2
ii  libstdc++64.9.0-7
ii  libx11-6  2:1.6.2-2
ii  libxau6   1:1.0.8-1
ii  libxdmcp6 1:1.1.1-1
ii  libxtst6  2:1.2.2-1
ii  lsb-base  4.1+Debian13

Versions of packages kdm recommends:
ii  cinnamon [x-window-manager] 1.7.4-2.2
ii  gnome-session [x-session-manager]   3.4.2.1-4
ii  gnome-session-fallback [x-session-manager]  3.4.2.1-4
ii  gnome-terminal [x-terminal-emulator]3.12.2-3
ii  kde-window-manager [x-window-manager]   4:4.11.9-1
ii  kde-workspace   4:4.11.9-1
ii  konsole [x-terminal-emulator]   4:4.13.1-1
ii  logrotate   3.8.7-1
ii  metacity [x-window-manager] 1:2.34.13-1
ii  mlterm [x-terminal-emulator]3.3.6-1
ii  xserver-xephyr [xserver]2:1.15.1-1
ii  xserver-xorg [xserver]  1:7.7+7
ii  xterm [x-terminal-emulator] 307-1

Versions of packages kdm suggests:
ii  kde-wallpapers  4:4.12.4-1
ii  kdepasswd   4:4.12.4-1

-- Configuration Files:
/etc/kde4/kdm/README changed:
This automatically generated configuration consists of the following files:
- /etc/kde4/kdm/kdmrc
- /etc/kde4/kdm/Xaccess
- /etc/kde4/kdm/Xwilling
- /etc/kde4/kdm/Xsetup
- /etc/kde4/kdm/Xstartup
- /etc/kde4/kdm/Xreset
- /etc/kde4/kdm/Xsession
- /etc/kde4/kdm/backgroundrc
This config was derived from existing files. As the used algorithms are
pretty dumb, it may be broken.
Information from these files was extracted:
- /etc/kde4/kdm/kdmrc
These files were directly incorporated:
- /etc/kde4/kdm/Xaccess
- /etc/kde4/kdm/Xwilling
- /etc/kde4/kdm/Xsetup
- /etc/kde4/kdm/Xstartup
- /etc/kde4/kdm/Xreset
- /etc/kde4/kdm/Xsession
- /etc/kde4/kdm/backgroundrc
Old files that would have been overwritten were renamed to oldname.bak.
Try 'genkdmconf --help' if you want to generate another configuration.
You may delete this README.

/etc/kde4/kdm/kdmrc changed:
[General]
ConfigVersion=2.4
StaticServers=:0
ReserveServers=:1,:2,:3
ServerVTs=-7
ConsoleTTYs=tty1,tty2,tty3,tty4,tty5,tty6
PidFile=/var/run/kdm.pid
GreeterUID=kdm
[Xdmcp]
Enable=false
Xaccess=/etc/kde4/kdm/Xaccess

Bug#530820: Title change

[Shai Berger]

retitle 530820 Upgrade xkeyboard-config to version 2.11
thanks

Hi,

A local mail discussion made me realize that a retitle may be in order.

I don't intend to push too hard, will help any way I can.

Thanks,
Shai.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#530820: xkeyboard-config 2.11 includes the fix for this bug

[Shai Berger]

Hi,

xkeyboard-config 2.11, released last week, includes an implementation of the 
new version of the Israeli standard SI1452 -- which solves this bug.

Thanks,
Shai.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#735261: kmail2 randomly marks read messages as unread

[Shai Berger]

Package: kmail
Version: 4:4.11.3-1
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

KMail randomly marks single messages as unread. This makes my
normal workflow, where I leave messages unread for later, deeper
consideration, tedious and bordering on impossible.

KMail also randomly creates new duplicates of old messages, which
are (of course) also marked unread.

After an safe-update which included Akonadi, I found duplicates
for 400 such messages.

Losing read status is data loss.



-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kmail depends on:
ii  kde-runtime   4:4.11.3-1
ii  kdepim-runtime4:4.11.3-1
ii  kdepimlibs-kio-plugins4:4.11.3-2
ii  libakonadi-calendar4  4:4.11.3-2
ii  libakonadi-contact4   4:4.11.3-2
ii  libakonadi-kde4   4:4.11.3-2
ii  libakonadi-kmime4 4:4.11.3-2
ii  libakonadiprotocolinternals1  1.11.0-1
ii  libc6 2.17-97
ii  libcalendarsupport4   4:4.11.3-1
ii  libgcc1   1:4.8.2-13
ii  libgpgme++2   4:4.11.3-2
ii  libgrantlee-core0 0.3.0-5
ii  libincidenceeditorsng44:4.11.3-1
ii  libkabc4  4:4.11.3-2
ii  libkalarmcal2 4:4.11.3-2
ii  libkcalcore4  4:4.11.3-2
ii  libkcalutils4 4:4.11.3-2
ii  libkcmutils4  4:4.11.3-2
ii  libkdecore5   4:4.11.3-2
ii  libkdepim44:4.11.3-1
ii  libkdeui5 4:4.11.3-2
ii  libkio5   4:4.11.3-2
ii  libkleo4  4:4.11.3-1
ii  libkmime4 4:4.11.3-2
ii  libknewstuff3-4   4:4.11.3-2
ii  libknotifyconfig4 4:4.11.3-2
ii  libkontactinterface4  4:4.11.3-2
ii  libkparts44:4.11.3-2
ii  libkpgp4  4:4.11.3-1
ii  libkpimidentities44:4.11.3-2
ii  libkpimtextedit4  4:4.11.3-2
ii  libkpimutils4 4:4.11.3-2
ii  libkprintutils4   4:4.11.3-2
ii  libksieveui4  4:4.11.3-1
ii  libktnef4 4:4.11.3-2
ii  libmailcommon44:4.11.3-1
ii  libmailimporter4  4:4.11.3-1
ii  libmailtransport4 4:4.11.3-2
ii  libmessagecomposer4   4:4.11.3-1
ii  libmessagecore4   4:4.11.3-1
ii  libmessagelist4   4:4.11.3-1
ii  libmessageviewer4 4:4.11.3-1
ii  libnepomukcore4   4:4.11.3-2
ii  libpimcommon4 4:4.11.3-1
ii  libqt4-dbus   4:4.8.5+git209-g718fae5+dfsg-1
ii  libqt4-network4:4.8.5+git209-g718fae5+dfsg-1
ii  libqt4-xml4:4.8.5+git209-g718fae5+dfsg-1
ii  libqtcore44:4.8.5+git209-g718fae5+dfsg-1
ii  libqtgui4 4:4.8.5+git209-g718fae5+dfsg-1
ii  libqtwebkit4  2.2.1-7
ii  libsendlater4 4:4.11.3-1
ii  libsolid4 4:4.11.3-2
ii  libsoprano4   2.9.4+dfsg-1
ii  libstdc++64.8.2-13
ii  libtemplateparser44:4.11.3-1
ii  perl  5.14.2-21

Versions of packages kmail recommends:
ii  gnupg-agent   2.0.22-3
ii  gnupg22.0.22-3
ii  pinentry-gtk2 [pinentry-x11]  0.8.3-1

Versions of packages kmail suggests:
ii  bogofilter 1.2.4+dfsg1-2
pn  clamav | f-prot-installer  none
ii  kaddressbook   4:4.11.3-1
pn  kleopatra  none
ii  procmail   3.22-21
ii  spambayes  1.1a6-1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#734386: /usr/bin/scp: Hosts from .ssh/config recognized on source or target but not both

[Shai Berger]

Package: openssh-client
Version: 1:6.4p1-2
Severity: normal
File: /usr/bin/scp

Dear Maintainer,

In ~/.ssh/config you can define a list of host names, each mapped
to a real host and including options (such as user name, key file,
etc.). Such hosts can be used by scp as source or target hosts, but
trying to use them at both ends is likely to lead to host not found
errors, because scp essentially tries to resolve the second host
from the first host rather than the user's machine.

This is inconsistent and surprising.

#222992 (closed wontfix upstream) is probably related, but the
reasons for the closing do not apply here AFAICT.

Thanks,
Shai.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages openssh-client depends on:
ii  adduser   3.113+nmu3
ii  dpkg  1.17.5
ii  libc6 2.17-97
ii  libedit2  3.1-20130712-2
ii  libgssapi-krb5-2  1.11.3+dfsg-3+nmu1
ii  libselinux1   2.2.1-1
ii  libssl1.0.0   1.0.1e-6
ii  passwd1:4.1.5.1-1
ii  zlib1g1:1.2.8.dfsg-1

Versions of packages openssh-client recommends:
ii  xauth  1:1.0.7-1

Versions of packages openssh-client suggests:
pn  keychain none
pn  libpam-ssh   none
pn  monkeysphere none
ii  openssh-blacklist0.4.1+nmu1
ii  openssh-blacklist-extra  0.4.1+nmu1
pn  ssh-askpass  none

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#731318: aptitude: keeps switching a package between architectures on safe-upgrade

[Shai Berger]

Package: aptitude
Version: 0.6.8.2-1.2
Severity: normal

Dear Maintainer,

My system is mostly x86-64; some time ago I had to install Skype,
and for that, several :i386 packages got installed. The packages
in the system are managed almost exclusively by aptitude. I upgrade
manually, almost daily, by running

sudo aptitude update  sudo aptitude safe-upgrade 

Recently, I noticed that with every safe-upgrade, I have udisks
removed and udisks:i386 installed, or vice versa. Every single
time, this package is toggled between the architectures.

It doesn't really seems to hurt anything, but is a little annoying
and seems redundant.

-- Package-specific info:
Terminal: xterm
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.6.8.2 compiled at Aug 25 2013 12:37:10
Compiler: g++ 4.8.1
Compiled against:
  apt version 4.12.0
  NCurses version 5.9
  libsigc++ version: 2.2.10
  Ept support enabled.
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 5.9.20130608
  cwidget version: 0.5.16
  Apt version: 4.12.0

aptitude linkage:
linux-vdso.so.1 (0x711c2000)
libapt-pkg.so.4.12 = /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 
(0x7f480c6d5000)
libncursesw.so.5 = /lib/x86_64-linux-gnu/libncursesw.so.5 
(0x7f480c4a5000)
libtinfo.so.5 = /lib/x86_64-linux-gnu/libtinfo.so.5 
(0x7f480c27b000)
libsigc-2.0.so.0 = /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f480c076000)
libcwidget.so.3 = /usr/lib/libcwidget.so.3 (0x7f480bd6f000)
libept.so.1.aptpkg4.12 = 
/usr/lib/x86_64-linux-gnu/libept.so.1.aptpkg4.12 (0x7f480bb12000)
libxapian.so.22 = /usr/lib/libxapian.so.22 (0x7f480b72f000)
libz.so.1 = /lib/x86_64-linux-gnu/libz.so.1 (0x7f480b517000)
libsqlite3.so.0 = /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f480b25e000)
libboost_iostreams.so.1.54.0 = /usr/lib/libboost_iostreams.so.1.54.0 
(0x7f480b044000)
libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f480ae28000)
libstdc++.so.6 = /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f480ab24000)
libm.so.6 = /lib/x86_64-linux-gnu/libm.so.6 (0x7f480a826000)
libgcc_s.so.1 = /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f480a61)
libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f480a263000)
libutil.so.1 = /lib/x86_64-linux-gnu/libutil.so.1 (0x7f480a06)
libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7f4809e5c000)
libbz2.so.1.0 = /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f4809c4b000)
libuuid.so.1 = /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f4809c45000)
librt.so.1 = /lib/x86_64-linux-gnu/librt.so.1 (0x7f4809a3c000)
/lib64/ld-linux-x86-64.so.2 (0x7f480d05a000)

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages aptitude depends on:
ii  aptitude-common   0.6.8.2-1.2
ii  libapt-pkg4.120.9.12.1
ii  libboost-iostreams1.54.0  1.54.0-3
ii  libc6 2.17-93
ii  libcwidget3   0.5.16-3.5
ii  libept1.4.12  1.0.12
ii  libgcc1   1:4.8.2-1
ii  libncursesw5  5.9+20130608-1
ii  libsigc++-2.0-0c2a2.2.10-0.2
ii  libsqlite3-0  3.8.1-1
ii  libstdc++64.8.2-1
ii  libtinfo5 5.9+20130608-1
ii  libxapian22   1.2.15-2
ii  zlib1g1:1.2.8.dfsg-1

Versions of packages aptitude recommends:
ii  apt-xapian-index0.46
ii  aptitude-doc-en [aptitude-doc]  0.6.8.2-1.2
ii  libparse-debianchangelog-perl   1.2.0-1
ii  sensible-utils  0.0.9

Versions of packages aptitude suggests:
pn  debtags  none
ii  tasksel  3.18

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#731134: amarok: Amarok eats up all memory when playing from Magnatune

[Shai Berger]

Package: amarok
Version: 2.7.1-1
Severity: normal

Dear Maintainer,

Using Amarok, I tried to listen to Beth Quist's album,
Lucidity, from MagnaTune. When I first added the album
to my playlist, Amarok started playing from the 3rd song.
I moved to the first song. During the second song, I 
noticed my whole system slowing down. Upon check, I saw 
Amarok taking upwards of 80% of my system's 8G memory, with 
a virtual size over 11G. I was able to quit it, and start 
it again, playing only from my local collection; in these
conditions, things seem normal (Amarok taking 1.7% of
system memory, RES 137m, VIRT 5148m).

I have another system running Debian Sid, I will try to
reproduce there later tonight.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages amarok depends on:
ii  amarok-common 2.7.1-1
ii  amarok-utils  2.7.1-1
ii  kde-runtime   4:4.8.4-2+b1
ii  libaio1   0.3.109-4
ii  libavcodec53  6:0.8.7-1
ii  libavformat53 6:0.8.7-1
ii  libavutil51   6:0.8.7-1
ii  libc6 2.17-93
ii  libcurl3-gnutls   7.33.0-1
ii  libgcc1   1:4.8.2-1
ii  libgcrypt11   1.5.3-2
ii  libgdk-pixbuf2.0-02.28.2-1
ii  libglib2.0-0  2.36.4-1
ii  libgpod4-nogtk0.8.3-1.1
ii  libkcmutils4  4:4.11.3-2
ii  libkdecore5   4:4.11.3-2
ii  libkdeui5 4:4.11.3-2
ii  libkdewebkit5 4:4.11.3-2
ii  libkdnssd44:4.11.3-2
ii  libkfile4 4:4.11.3-2
ii  libkio5   4:4.11.3-2
ii  libknewstuff3-4   4:4.11.3-2
ii  liblastfm11.0.8-2
ii  libloudmouth1-0   1.4.3-10
ii  libmtp9   1.1.6-20-g1b9f164-1
ii  libmysqlclient18  5.5.33+dfsg-1
ii  libofa0   0.9.3-5
ii  libphonon44:4.7.0.0-2
ii  libplasma34:4.11.3-2
ii  libqjson0 0.8.1-3
ii  libqt4-dbus   4:4.8.5+git121-g2a9ea11+dfsg1-2
ii  libqt4-network4:4.8.5+git121-g2a9ea11+dfsg1-2
ii  libqt4-script 4:4.8.5+git121-g2a9ea11+dfsg1-2
ii  libqt4-sql4:4.8.5+git121-g2a9ea11+dfsg1-2
ii  libqt4-svg4:4.8.5+git121-g2a9ea11+dfsg1-2
ii  libqt4-xml4:4.8.5+git121-g2a9ea11+dfsg1-2
ii  libqtcore44:4.8.5+git121-g2a9ea11+dfsg1-2
ii  libqtgui4 4:4.8.5+git121-g2a9ea11+dfsg1-2
ii  libqtscript4-core 0.2.0-1
ii  libqtscript4-gui  0.2.0-1
ii  libqtscript4-network  0.2.0-1
ii  libqtscript4-sql  0.2.0-1
ii  libqtscript4-uitools  0.2.0-1
ii  libqtscript4-xml  0.2.0-1
ii  libqtwebkit4  2.2.1-7
ii  libsolid4 4:4.11.3-2
ii  libstdc++64.8.2-1
ii  libtag-extras11.0.1-3
ii  libtag1c2a1.9.1-2
ii  libthreadweaver4  4:4.11.3-2
ii  libx11-6  2:1.6.2-1
ii  libxml2   2.9.1+dfsg1-3
ii  phonon4:4.7.0.0-2
ii  zlib1g1:1.2.8.dfsg-1

Versions of packages amarok recommends:
pn  clamz  none
pn  kdemultimedia-kio-plugins  none

Versions of packages amarok suggests:
pn  amarok-doc none
ii  libqt4-sql-mysql   4:4.8.5+git121-g2a9ea11+dfsg1-2
pn  libqt4-sql-psqlnone
ii  libqt4-sql-sqlite  4:4.8.5+git121-g2a9ea11+dfsg1-2
pn  moodbarnone

Versions of packages amarok-common depends on:
ii  perl  5.18.1-4

amarok-common recommends no packages.

Versions of packages amarok is related to:
ii  phonon-backend-vlc [phonon-backend]  0.7.0-1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#530820: Upstream bug and patch

[Shai Berger]

forwarded 530820 https://bugs.freedesktop.org/show_bug.cgi?id=70887
thanks

Hi,

I haven't submitted the bug upstream myself -- someone else
beat me to it; but I did send them the suggested fix.

The fix is not a new variant -- what I wanted to achieve with the
variant is now incorporated into the new Israeli Standard 1542,
so the patch incorporates it into the basic variant.

Thanks for your patience,

Shai.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#729206: kde-plasma-desktop: Screen locker does not allow opening a new session until opened otherwise

[Shai Berger]

Package: kde-plasma-desktop
Followup-For: Bug #729206

Indeed, after an additional update the problem went away.

Thanks,
Shai.


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.11-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kde-plasma-desktop depends on:
ii  kde-baseapps4:4.11.3-1
ii  kde-runtime 4:4.11.3-1
ii  kde-workspace   4:4.10.5-3
ii  plasma-desktop  4:4.10.5-3
ii  udisks2 2.1.1-1
ii  upower  0.9.23-2+b1

Versions of packages kde-plasma-desktop recommends:
ii  kdm   4:4.10.5-3
ii  xserver-xorg  1:7.7+4

Versions of packages kde-plasma-desktop suggests:
ii  kde-l10n-he [kde-l10n]  4:4.10.5-2

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#729206: kde-plasma-desktop: Screen locker does not allow opening a new session until opened otherwise

[Shai Berger]

Package: kde-plasma-desktop
Version: 5:82
Severity: normal

Dear Maintainer,

I just upgraded my system and got a substantial part of kde-sc 4.11.
Following the upgrade, I opened a session, then locked it; the lock
screen showed a password prompt with the unlock button, but the
switch users button that is usually there was missing. Only after
I unlocked, and used the switch users action from the menu 
(I use Lancelot) to open a second session, the button became available
on the locked screen as well.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.11-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kde-plasma-desktop depends on:
ii  kde-baseapps4:4.11.3-1
ii  kde-runtime 4:4.11.3-1
ii  kde-workspace   4:4.10.5-3
ii  plasma-desktop  4:4.10.5-3
ii  udisks2 2.1.1-1
ii  upower  0.9.23-2+b1

Versions of packages kde-plasma-desktop recommends:
ii  kdm   4:4.10.5-3
ii  xserver-xorg  1:7.7+4

Versions of packages kde-plasma-desktop suggests:
ii  kde-l10n-he [kde-l10n]  4:4.10.5-2

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#727800: kmail: Also identity folders got mixed up

[Shai Berger]

Package: kmail
Version: 4:4.10.5-2
Followup-For: Bug #727800

Dear Maintainer,

Extra data point from original reporter: I just realized that,
in addition to everything in my initial report, the folders
defined for my identities got mixed up. Thus, sent messages
were saved into a sub-folder of the inbox, where I hadn't 
suspected I should look for them, and drafts were saved into 
the sent folder.

(I use the standard folders, but I have defined two subfolders
for inbox and one for sent-mail).

Thanks,
Shai.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#723105: nepomuk-core-runtime: Nepomuk sends virtuoso to 100% CPU after marking KMail folder read

[Shai Berger]

Package: nepomuk-core-runtime
Version: 4:4.10.5-1+b1
Followup-For: Bug #723105

Dear Maintainer,

Just happened again. This time, I had picked ~3600 messages from
the inbox and marked them read, so, not a full folder.

(the reason I had 4000 unread messages in my inbox is a separate bug).

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.11-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nepomuk-core-runtime depends on:
ii  libavcodec-extra-54  6:9.10-1
ii  libavformat546:9.10-1
ii  libavutil52  6:9.10-1
ii  libc62.17-93
ii  libexiv2-12  0.23-1
ii  libgcc1  1:4.8.2-1
ii  libkdecore5  4:4.10.5-1+b1
ii  libkdeui54:4.10.5-1+b1
ii  libkidletime44:4.10.5-1+b1
ii  libkio5  4:4.10.5-1+b1
ii  libnepomukcore4  4:4.10.5-1+b1
ii  libpoppler-qt4-3 0.18.4-8
ii  libqt4-dbus  4:4.8.5+git121-g2a9ea11+dfsg1-2
ii  libqtcore4   4:4.8.5+git121-g2a9ea11+dfsg1-2
ii  libqtgui44:4.8.5+git121-g2a9ea11+dfsg1-2
ii  libsolid44:4.10.5-1+b1
ii  libsoprano4  2.9.2+dfsg.1-4
ii  libstdc++6   4.8.2-1
ii  libtag1c2a   1.8-2

nepomuk-core-runtime recommends no packages.

nepomuk-core-runtime suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#727800: kmail: KMail goes bonkers following Qt update

[Shai Berger]

Package: kmail
Version: 4:4.10.5-2
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

Today, following a safe-upgrade which updated the Qt4 libraries,
I found the whole KMail/Akonadi system quite broken.

I should note that, after the upgrade, I rebooted the system, as
it included updates to the kernel.

At first, things seemed normal, except filters weren't working.

I closed KMail, and tried to re-open it. It wouldn't start,
saying it Failed to fetch resource collection.

Now, I am not sure exactly when I restarted what. At some point,
akonadiconsole wouldn't start with the same complaint. Later,
it opened, but KMail still refused to run. Reports on the web
suggested the problem was a misconfigured mail folder, but
the mail folder was configured correctly.

I noticed that the Akonadi self-test was reporting an error in
the mysql server startup -- missing tables. After consulting the
web, I decided to try to recreate the database with 

mysql_install_db --datadir=$HOME/.local/share/akonadi/db_data/ --user=shai 
--force

This seems to have worked -- after a few more false starts,
logoff-logon cycles, akonadi restart, and KMail failures,
something finally clicked into place and KMail started. 

At first it seemed like it had forgotten all my mail. But
something was synchronizing, so I let it go. When it was
done (didn't follow closely, but ~20 minutes later) it had
restored my mails -- sort of.

It managed to forget the read status of ~3 months of mails,
so I suddenly had more than 4000 unread mails in my inbox.
The 3 months weren't the last ones, but mid April to mid July;
I suspect these were the first 3 months of KMail2 on this system.

And then I noted the filters were still not working. I have ~20 
filters, most of them just send messages to different folders. When I
looked at the filter configuration, I realized all the filter target
folders were wrong. It wasn't too hard to resotre them, but
it had to be done manually.

So -- 

A) There was real (though minor) data loss -- the read status,
and the filters configurations;
B) There was what looked like data loss -- at first, seeing the
empty mail folders was scary; it is very easy to panic and kill
the program at that stage, which is likely to cause more serious
data loss.

References:

https://bbs.archlinux.org/viewtopic.php?pid=695037 for the tables
https://bugs.kde.org/show_bug.cgi?id=259355 for the startup fail
(comment 10 there seems to be suggested often as a workaround; as
noted above, was not relevant for my case. I believe the problem 
I encountered is similar in effects, but different in cause).

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.11-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kmail depends on:
ii  kde-runtime   4:4.10.5-1
ii  kdepim-runtime4:4.10.5-2
ii  kdepimlibs-kio-plugins4:4.10.5-1
ii  libakonadi-contact4   4:4.10.5-1
ii  libakonadi-kde4   4:4.10.5-1
ii  libakonadi-kmime4 4:4.10.5-1
ii  libakonadiprotocolinternals1  1.9.2-2+b1
ii  libc6 2.17-93
ii  libcalendarsupport4   4:4.10.5-2
ii  libgcc1   1:4.8.2-1
ii  libgpgme++2   4:4.10.5-1
ii  libincidenceeditorsng44:4.10.5-2
ii  libkabc4  4:4.10.5-1
ii  libkcalcore4  4:4.10.5-1
ii  libkcalutils4 4:4.10.5-1
ii  libkcmutils4  4:4.10.5-1+b1
ii  libkdecore5   4:4.10.5-1+b1
ii  libkdepim44:4.10.5-2
ii  libkdeui5 4:4.10.5-1+b1
ii  libkio5   4:4.10.5-1+b1
ii  libkleo4  4:4.10.5-2
ii  libkmime4 4:4.10.5-1
ii  libknotifyconfig4 4:4.10.5-1+b1
ii  libkontactinterface4  4:4.10.5-1
ii  libkparts44:4.10.5-1+b1
ii  libkpgp4  4:4.10.5-2
ii  libkpimidentities44:4.10.5-1
ii  libkpimtextedit4  4:4.10.5-1
ii  libkpimutils4 4:4.10.5-1
ii  libkprintutils4   4:4.10.5-1+b1
ii  libksieveui4  4:4.10.5-2
ii  libktnef4 4:4.10.5-1
ii  libmailcommon44:4.10.5-2
ii  libmailimporter4  4:4.10.5-2
ii  libmailtransport4 4:4.10.5-1
ii  libmessagecomposer4   4:4.10.5-2
ii  libmessagecore4   4:4.10.5-2
ii  libmessagelist4   4:4.10.5-2
ii  libmessageviewer4 4:4.10.5-2
ii  libnepomukcore4   4:4.10.5-1+b1
ii  libpimcommon4 4:4.10.5-2
ii  libqt4-dbus   4:4.8.5+git121-g2a9ea11+dfsg1-2
ii  libqt4-network4:4.8.5+git121-g2a9ea11+dfsg1-2
ii  libqt4-xml   

Bug#723105: nepomuk-core-runtime: Nepomuk sends virtuoso to 100% CPU after marking KMail folder read

[Shai Berger]

Package: nepomuk-core-runtime
Version: 4:4.10.5-1+b1
Severity: normal

Dear Maintainer,

Just what the summary says. In KMail, I right-clicked the Junk folder
(37400 messages, 500M, about 8000 were unread) and selected mark folder
as read. This seems to have worked, but since that moment, and for more
than an hour, the system was constantly at 100% CPU, where every bit of
free CPU is taken by the Nepomuk server's Virtuoso process.

I killed -HUP the virtuoso, it restarted and went back to 100% CPU.

I killed -HUP the nepomukserver, and the CPU came back down to normal.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nepomuk-core-runtime depends on:
ii  libavcodec-extra-54  6:9.8-2+b1
ii  libavformat546:9.8-2+b1
ii  libavutil52  6:9.8-2+b1
ii  libc62.17-92+b1
ii  libexiv2-12  0.23-1
ii  libgcc1  1:4.8.1-10
ii  libkdecore5  4:4.10.5-1+b1
ii  libkdeui54:4.10.5-1+b1
ii  libkidletime44:4.10.5-1+b1
ii  libkio5  4:4.10.5-1+b1
ii  libnepomukcore4  4:4.10.5-1+b1
ii  libpoppler-qt4-3 0.18.4-8
ii  libqt4-dbus  4:4.8.5+git121-g2a9ea11+dfsg-1
ii  libqtcore4   4:4.8.5+git121-g2a9ea11+dfsg-1
ii  libqtgui44:4.8.5+git121-g2a9ea11+dfsg-1
ii  libsolid44:4.10.5-1+b1
ii  libsoprano4  2.9.2+dfsg.1-4
ii  libstdc++6   4.8.1-10
ii  libtag1c2a   1.8-2

nepomuk-core-runtime recommends no packages.

nepomuk-core-runtime suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#721312: Upgrading libclutter-1.0-0 seems to have fixed this

[Shai Berger]

Hi,

Upgrading libclutter-1.0-0 seems to have fixed this problem.

Now at 1.14.4-3, and evolution starts.

(so whoever closes this can also reassign it to libclutter while at it).

Thanks,
Shai.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#721312: evolution will not start

[Shai Berger]

Package: evolution
Version: 3.4.4-4+b1
Severity: important

Dear Maintainer,

Starting evolution has ceased to work after recent updates.

The problem seems to be related to clutter, but I am not
a gnome user, so I cannot be sure.

I usually use evolution under KDE, and there, I get this:

$ evolution --clutter-debug=all
Clutter-Message: [  2549001632]:[BACKEND]:./x11/clutter-backend-x11.c:1303: 
ARGB visuals are enabled
Clutter-Message: [  2549001703]:[BACKEND]:./x11/clutter-backend-x11.c:394: 
Getting the X screen
Clutter-Message: [  2549001765]:[BACKEND]:./clutter-settings.c:201: New 
resolution: 93.00
Clutter-Message: [  2549001889]:[BACKEND]:./clutter-backend.c:241: Units 
per em: 18.02
Clutter-Message: [  2549002485]:[BACKEND]:./x11/clutter-backend-x11.c:463: 
X Display ':0'[0x7f1963b604c0] opened (screen:0, root:608, dpi:93.00)
Clutter-Message: [  2549002524]:[MISC]:./clutter-feature.c:92: checking 
features
Clutter-Message: [  2549002574]:[MISC]:./clutter-feature.c:96: allocating 
features data
Clutter-Message: [  2549002596]:[BACKEND]:./clutter-backend.c:271: Creating 
Cogl renderer
Clutter-Message: [  2549002615]:[BACKEND]:./x11/clutter-backend-x11.c:706: 
Creating a new Xlib renderer
Clutter-Message: [  2549002697]:[BACKEND]:./clutter-backend.c:288: 
Connecting the renderer
Failed to connected to any renderer: 

Gnome-shell based sessions (gnome, cinnamon) also don't work
for me (which strengthens suspicion of a clutter problem). 
When I start evolution under Gnome Classic I get:

$ evolution --clutter-debug=all
Clutter-Message: [  1409239081]:[BACKEND]:./x11/clutter-backend-x11.c:1303: 
ARGB visuals are enabled
Clutter-Message: [  1409239191]:[BACKEND]:./x11/clutter-backend-x11.c:394: 
Getting the X screen
Clutter-Message: [  1409239241]:[BACKEND]:./clutter-settings.c:201: New 
resolution: 93.00
Clutter-Message: [  1409239313]:[BACKEND]:./clutter-backend.c:241: Units 
per em: 18.02
Clutter-Message: [  1409239654]:[BACKEND]:./x11/clutter-backend-x11.c:207: 
Mapping XSETTING 'Gtk/FontName' to 'ClutterSettings:font-name'
Clutter-Message: [  1409239677]:[BACKEND]:./clutter-settings.c:192: New 
font-name: Cantarell 11
Clutter-Message: [  1409239700]:[BACKEND]:./clutter-backend.c:252: Units 
per em: 16.52
Clutter-Message: [  1409239741]:[BACKEND]:./x11/clutter-backend-x11.c:207: 
Mapping XSETTING 'Net/DndDragThreshold' to 'ClutterSettings:dnd-drag-threshold'
Clutter-Message: [  1409239761]:[BACKEND]:./x11/clutter-backend-x11.c:207: 
Mapping XSETTING 'Net/DoubleClickTime' to 'ClutterSettings:double-click-time'
Clutter-Message: [  1409239787]:[BACKEND]:./x11/clutter-backend-x11.c:207: 
Mapping XSETTING 'Xft/Antialias' to 'ClutterSettings:font-antialias'
Clutter-Message: [  1409239816]:[BACKEND]:./clutter-settings.c:183: New 
font options:
 - font-name:  Cantarell 11
 - antialias:  1
 - hinting:-1
 - hint-style: null
 - rgba:   null
 - dpi:93.00
Clutter-Message: [  1409239845]:[BACKEND]:./clutter-backend.c:252: Units 
per em: 16.52
Clutter-Message: [  1409239868]:[BACKEND]:./x11/clutter-backend-x11.c:207: 
Mapping XSETTING 'Xft/DPI' to 'ClutterSettings:font-dpi'
Clutter-Message: [  1409239884]:[BACKEND]:./clutter-settings.c:201: New 
resolution: 96.00
Clutter-Message: [  1409239905]:[BACKEND]:./clutter-backend.c:241: Units 
per em: 17.60
Clutter-Message: [  1409239924]:[BACKEND]:./x11/clutter-backend-x11.c:207: 
Mapping XSETTING 'Xft/HintStyle' to 'ClutterSettings:font-hint-style'
Clutter-Message: [  1409239940]:[BACKEND]:./clutter-settings.c:183: New 
font options:
 - font-name:  Cantarell 11
 - antialias:  1
 - hinting:-1
 - hint-style: hintmedium
 - rgba:   null
 - dpi:96.00
Clutter-Message: [  1409239963]:[BACKEND]:./clutter-backend.c:252: Units 
per em: 17.60
Clutter-Message: [  1409239982]:[BACKEND]:./x11/clutter-backend-x11.c:207: 
Mapping XSETTING 'Xft/Hinting' to 'ClutterSettings:font-hinting'
Clutter-Message: [  1409239997]:[BACKEND]:./clutter-settings.c:183: New 
font options:
 - font-name:  Cantarell 11
 - antialias:  1
 - hinting:1
 - hint-style: hintmedium
 - rgba:   null
 - dpi:96.00
Clutter-Message: [  1409240034]:[BACKEND]:./clutter-backend.c:252: Units 
per em: 17.60
Clutter-Message: [  1409240053]:[BACKEND]:./x11/clutter-backend-x11.c:207: 
Mapping XSETTING 'Xft/RGBA' to 'ClutterSettings:font-subpixel-order'
Clutter-Message: [  1409240070]:[BACKEND]:./clutter-settings.c:183: New 
font options:
 - font-name:  Cantarell 11
 - antialias:  1
 - hinting:1
 - hint-style: hintmedium
 - rgba:   none
 - dpi:96.00
Clutter-Message: [  1409240093]:[BACKEND]:./clutter-backend.c:252: Units 
per em: 17.60
Clutter-Message: [  1409240160]:[BACKEND]:./x11/clutter-backend-x11.c:463: 
X Display ':1'[0x7f71c5bc3100] opened (screen:0, root:608, dpi:96.00)
Clutter-Message: [  

Bug#717618: kmail: Resource KMail Folders is broken. This resource is now online

[Shai Berger]

Package: kmail
Followup-For: Bug #717618

Possibly related: Bug #717101, where the same message is displayed;
there, it is always related to problems accessing specific messages.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.10-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kmail depends on:
ii  kde-runtime   4:4.10.5-1
ii  kdepim-runtime4:4.10.5-1
ii  kdepimlibs-kio-plugins4:4.10.5-1
ii  libakonadi-contact4   4:4.10.5-1
ii  libakonadi-kde4   4:4.10.5-1
ii  libakonadi-kmime4 4:4.10.5-1
ii  libakonadiprotocolinternals1  1.9.2-2
ii  libc6 2.17-92
ii  libcalendarsupport4   4:4.10.5-1
ii  libgcc1   1:4.8.1-8
ii  libgpgme++2   4:4.10.5-1
ii  libincidenceeditorsng44:4.10.5-1
ii  libkabc4  4:4.10.5-1
ii  libkcalcore4  4:4.10.5-1
ii  libkcalutils4 4:4.10.5-1
ii  libkcmutils4  4:4.10.5-1
ii  libkdecore5   4:4.10.5-1
ii  libkdepim44:4.10.5-1
ii  libkdeui5 4:4.10.5-1
ii  libkio5   4:4.10.5-1
ii  libkleo4  4:4.10.5-1
ii  libkmime4 4:4.10.5-1
ii  libknotifyconfig4 4:4.10.5-1
ii  libkontactinterface4  4:4.10.5-1
ii  libkparts44:4.10.5-1
ii  libkpgp4  4:4.10.5-1
ii  libkpimidentities44:4.10.5-1
ii  libkpimtextedit4  4:4.10.5-1
ii  libkpimutils4 4:4.10.5-1
ii  libkprintutils4   4:4.10.5-1
ii  libksieveui4  4:4.10.5-1
ii  libktnef4 4:4.10.5-1
ii  libmailcommon44:4.10.5-1
ii  libmailimporter4  4:4.10.5-1
ii  libmailtransport4 4:4.10.5-1
ii  libmessagecomposer4   4:4.10.5-1
ii  libmessagecore4   4:4.10.5-1
ii  libmessagelist4   4:4.10.5-1
ii  libmessageviewer4 4:4.10.5-1
ii  libnepomukcore4   4:4.10.5-1
ii  libpimcommon4 4:4.10.5-1
ii  libqt4-dbus   4:4.8.5+dfsg-2
ii  libqt4-network4:4.8.5+dfsg-2
ii  libqt4-xml4:4.8.5+dfsg-2
ii  libqtcore44:4.8.5+dfsg-2
ii  libqtgui4 4:4.8.5+dfsg-2
ii  libqtwebkit4  2.2.1-6
ii  libsolid4 4:4.10.5-1
ii  libsoprano4   2.9.2+dfsg.1-1
ii  libstdc++64.8.1-8
ii  libtemplateparser44:4.10.5-1
ii  perl  5.14.2-21

Versions of packages kmail recommends:
ii  gnupg-agent   2.0.20-1
ii  gnupg22.0.20-1
ii  pinentry-gtk2 [pinentry-x11]  0.8.1-1

Versions of packages kmail suggests:
ii  bogofilter 1.2.2+dfsg1-3
pn  clamav | f-prot-installer  none
ii  kaddressbook   4:4.10.5-1
pn  kleopatra  none
ii  procmail   3.22-20
ii  spambayes  1.1a6-1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#718616: kmail: aborts on session startup

[Shai Berger]

Package: kmail
Version: 4:4.10.5-1
Severity: minor

Dear Maintainer,
I use kmail always, so it is usually open when I close a session.
Then, when I log in again, I expect the whole session to re-open.
This has always worked well.

Since kmail2, however, kmail aborts on session startup with a message
that it timed out getting a lock and now needs to close; I re-open it
manually once the rest of the busy session startup ends, and all is
well.

FWIW, the other programs I have starting with the session (all by way
of the last session being saved, no specific startup setting) are
three Konsole instances, Iceweasel and Akregator.

Thanks for your good work,

Shai.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.10-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kmail depends on:
ii  kde-runtime   4:4.10.5-1
ii  kdepim-runtime4:4.10.5-1
ii  kdepimlibs-kio-plugins4:4.10.5-1
ii  libakonadi-contact4   4:4.10.5-1
ii  libakonadi-kde4   4:4.10.5-1
ii  libakonadi-kmime4 4:4.10.5-1
ii  libakonadiprotocolinternals1  1.9.2-2
ii  libc6 2.17-92
ii  libcalendarsupport4   4:4.10.5-1
ii  libgcc1   1:4.8.1-8
ii  libgpgme++2   4:4.10.5-1
ii  libincidenceeditorsng44:4.10.5-1
ii  libkabc4  4:4.10.5-1
ii  libkcalcore4  4:4.10.5-1
ii  libkcalutils4 4:4.10.5-1
ii  libkcmutils4  4:4.10.5-1
ii  libkdecore5   4:4.10.5-1
ii  libkdepim44:4.10.5-1
ii  libkdeui5 4:4.10.5-1
ii  libkio5   4:4.10.5-1
ii  libkleo4  4:4.10.5-1
ii  libkmime4 4:4.10.5-1
ii  libknotifyconfig4 4:4.10.5-1
ii  libkontactinterface4  4:4.10.5-1
ii  libkparts44:4.10.5-1
ii  libkpgp4  4:4.10.5-1
ii  libkpimidentities44:4.10.5-1
ii  libkpimtextedit4  4:4.10.5-1
ii  libkpimutils4 4:4.10.5-1
ii  libkprintutils4   4:4.10.5-1
ii  libksieveui4  4:4.10.5-1
ii  libktnef4 4:4.10.5-1
ii  libmailcommon44:4.10.5-1
ii  libmailimporter4  4:4.10.5-1
ii  libmailtransport4 4:4.10.5-1
ii  libmessagecomposer4   4:4.10.5-1
ii  libmessagecore4   4:4.10.5-1
ii  libmessagelist4   4:4.10.5-1
ii  libmessageviewer4 4:4.10.5-1
ii  libnepomukcore4   4:4.10.5-1
ii  libpimcommon4 4:4.10.5-1
ii  libqt4-dbus   4:4.8.5+dfsg-2
ii  libqt4-network4:4.8.5+dfsg-2
ii  libqt4-xml4:4.8.5+dfsg-2
ii  libqtcore44:4.8.5+dfsg-2
ii  libqtgui4 4:4.8.5+dfsg-2
ii  libqtwebkit4  2.2.1-6
ii  libsolid4 4:4.10.5-1
ii  libsoprano4   2.9.2+dfsg.1-1
ii  libstdc++64.8.1-8
ii  libtemplateparser44:4.10.5-1
ii  perl  5.14.2-21

Versions of packages kmail recommends:
ii  gnupg-agent   2.0.20-1
ii  gnupg22.0.20-1
ii  pinentry-gtk2 [pinentry-x11]  0.8.1-1

Versions of packages kmail suggests:
ii  bogofilter 1.2.2+dfsg1-3
pn  clamav | f-prot-installer  none
ii  kaddressbook   4:4.10.5-1
pn  kleopatra  none
ii  procmail   3.22-20
ii  spambayes  1.1a6-1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#718214: akonadi: caused kmail to fail storing downloaded mails

[Shai Berger]

Package: akonadi-server
Version: 1.9.2-2
Severity: important
File: akonadi

Dear Maintainer,

I usually leave my session open for several days, including kdepim
applications. Yesterday, by chance, I did restart. Today when
I got to the computer, around 22:00, I found that it had stopped
downloading mail a little after 15:00, and there was a pile of messages
in the notifier:

   [pop3 account] Unable to store downloaded mails. Append failed

I looked it up and found https://bugs.kde.org/show_bug.cgi?id=273445 but
it seems to have been long fixed.

However this does seem to be related -- I followed the advice and
ran akonadictl restart and that seems to have helped. I started
by trying to follow the other advice there and remove the 

   ExternalPayload=false

line from akonadiserverrc -- except I thought I could comment it
out with a # sign. That didn't work -- when I opened it up, I
saw that the sign was url-encoded (?) to %23, but then I restored
the line and restarted akonadi again and things seem to have settled
down.

The output from the restart was made, essentially, of some error 
messages and hundreds of repetitions of the line

akonadi_nepomuk_feeder(32526) ItemQueue::fetchJobResult: Not all items were 
fetched:  0 100

Output (excluding fontconfig errors):

Connecting to deprecated signal 
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
search paths:  (/usr/lib/x86_64-linux-gnu/qt4/bin, /home/shai/bin, 
/usr/local/bin, /usr/bin, /bin, /usr/local/games, /usr/games, 
/usr/sbin, /usr/local/sbin, /usr/local/libexec, /usr/libexec, 
/opt/mysql/libexec, /opt/local/lib/mysql5/bin, /opt/mysql/sbin) 
akonadi.collectionattributetable   OK
akonadi.collectionmimetyperelation OK
akonadi.collectionpimitemrelation  OK
akonadi.collectiontableOK
akonadi.flagtable  OK
akonadi.mimetypetable  OK
akonadi.parttable  OK
akonadi.pimitemflagrelationOK
akonadi.pimitemtable   OK
akonadi.resourcetable  OK
akonadi.schemaversiontable OK
Connecting to deprecated signal 
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
search paths:  (/usr/lib/x86_64-linux-gnu/qt4/bin, /home/shai/bin, 
/usr/local/bin, /usr/bin, /bin, /usr/local/games, /usr/games) 
search paths:  (/home/shai/.kde/lib/kde4/plugins/, /usr/lib/kde4/plugins/, 
/usr/lib/x86_64-linux-gnu/qt4/plugins, /usr/lib/qt4/plugins, /usr/bin, 
/usr/lib/kde4/plugins, /home/shai/.kde/lib/kde4/, /usr/lib/kde4/) 
search paths:  (/home/shai/.kde/lib/kde4/plugins/, /usr/lib/kde4/plugins/, 
/usr/lib/x86_64-linux-gnu/qt4/plugins, /usr/lib/qt4/plugins, /usr/bin, 
/usr/lib/kde4/plugins, /home/shai/.kde/lib/kde4/, /usr/lib/kde4/) 
search paths:  (/home/shai/.kde/lib/kde4/plugins/, /usr/lib/kde4/plugins/, 
/usr/lib/x86_64-linux-gnu/qt4/plugins, /usr/lib/qt4/plugins, /usr/bin, 
/usr/lib/kde4/plugins, /home/shai/.kde/lib/kde4/, /usr/lib/kde4/) 
search paths:  (/home/shai/.kde/lib/kde4/plugins/, /usr/lib/kde4/plugins/, 
/usr/lib/x86_64-linux-gnu/qt4/plugins, /usr/lib/qt4/plugins, /usr/bin, 
/usr/lib/kde4/plugins, /home/shai/.kde/lib/kde4/, /usr/lib/kde4/) 
search paths:  (/home/shai/.kde/lib/kde4/plugins/, /usr/lib/kde4/plugins/, 
/usr/lib/x86_64-linux-gnu/qt4/plugins, /usr/lib/qt4/plugins, /usr/bin, 
/usr/lib/kde4/plugins, /home/shai/.kde/lib/kde4/, /usr/lib/kde4/) 
search paths:  (/home/shai/.kde/lib/kde4/plugins/, /usr/lib/kde4/plugins/, 
/usr/lib/x86_64-linux-gnu/qt4/plugins, /usr/lib/qt4/plugins, /usr/bin, 
/usr/lib/kde4/plugins, /home/shai/.kde/lib/kde4/, /usr/lib/kde4/) 
akonadi_nepomuk_feeder(32526) FeederPluginloader::feederPluginsForMimeType: No 
feeder for type  text/calendar  found 
akonadi_kcal_resource_3(32521): Cannot open  /usr/share/zoneinfo/Israel 
Standard Time 

akonadi_kcal_resource_3(32521): Cannot open  /usr/share/zoneinfo/Israel 
Standard Time 

akonadi_maildispatcher_agent(32522) OutboxQueue::Private::addIfComplete: Item 
143222 does not have the required attribute Address. 
akonadi_mixedmaildir_resource_0(32525)/akonadiresource (maildir): Failed to 
read item 1359646900.3940.Bi7Tl:2,S in Maildir /home/shai/Mail/trash 
akonadi_mixedmaildir_resource_0(32525)/akonadiresource (maildir) 
RetrieveItemsJob::Private::fetchNewResult: Store fetch for new item 
1359646900.3940.Bi7Tl:2,S in collection 63 , trash did not return the 
expected item. error= 102 , Error while reading mails from folder trash 
akonadi_nepomuk_feeder(32526) FeederPluginloader::feederPluginsForMimeType: No 
feeder for type  inode/directory  found 
akonadi_nepomuk_feeder(32526) ItemQueue::fetchJobResult: Not all items were 
fetched:  0 6 
akonadi_nepomuk_feeder(32526) ItemQueue::fetchJobResult: Not all items were 
fetched:  0 100 
akonadi_nepomuk_feeder(32526) ItemQueue::fetchJobResult: Not all 

Bug#718214: upstream ref

[Shai Berger]

forwarded 718214 https://bugs.kde.org/show_bug.cgi?id=322923
thanks

bug also reported upstream as https://bugs.kde.org/show_bug.cgi?id=322923


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#717110: link to upstream ticket

[Shai Berger]

forwareded 717110 https://bugs.kde.org/show_bug.cgi?id=259813
thanks

My KDE ticket turned out to be a dupe, linking to the correct ticket.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#717101: kmail: random failures to read messages

[Shai Berger]

Package: kmail
Version: 4:4.10.5-1
Severity: important
Tags: upstream

Dear Maintainer,

Having used the new kmail2 for a couple of days, I keep
running into this: On certain messages, when I try to
select the message to have it previewed, I get (for each
such message) 6 notifications: 3 pairs of KMail Folders:
Error while reading mails from folder and KMail: Resource
KMail Folders is broken. This resource is now online. When
this happens, the message is not accessible -- I get its
line in the message list selected, but the preview still
shows the previously selected mail.

It appears to be possible to read the message by going to
another folder and then return to the folder where the
problem was encountered.

I think this is https://bugs.kde.org/show_bug.cgi?id=310899
though I cannot be sure, of course. 

Thanks,
Shai.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kmail depends on:
ii  kde-runtime   4:4.10.5-1
ii  kdepim-runtime4:4.10.5-1
ii  kdepimlibs-kio-plugins4:4.10.5-1
ii  libakonadi-contact4   4:4.10.5-1
ii  libakonadi-kde4   4:4.10.5-1
ii  libakonadi-kmime4 4:4.10.5-1
ii  libakonadiprotocolinternals1  1.9.2-2
ii  libc6 2.17-7
ii  libcalendarsupport4   4:4.10.5-1
ii  libgcc1   1:4.8.1-6
ii  libgpgme++2   4:4.10.5-1
ii  libincidenceeditorsng44:4.10.5-1
ii  libkabc4  4:4.10.5-1
ii  libkcalcore4  4:4.10.5-1
ii  libkcalutils4 4:4.10.5-1
ii  libkcmutils4  4:4.10.5-1
ii  libkdecore5   4:4.10.5-1
ii  libkdepim44:4.10.5-1
ii  libkdeui5 4:4.10.5-1
ii  libkio5   4:4.10.5-1
ii  libkleo4  4:4.10.5-1
ii  libkmime4 4:4.10.5-1
ii  libknotifyconfig4 4:4.10.5-1
ii  libkontactinterface4  4:4.10.5-1
ii  libkparts44:4.10.5-1
ii  libkpgp4  4:4.10.5-1
ii  libkpimidentities44:4.10.5-1
ii  libkpimtextedit4  4:4.10.5-1
ii  libkpimutils4 4:4.10.5-1
ii  libkprintutils4   4:4.10.5-1
ii  libksieveui4  4:4.10.5-1
ii  libktnef4 4:4.10.5-1
ii  libmailcommon44:4.10.5-1
ii  libmailimporter4  4:4.10.5-1
ii  libmailtransport4 4:4.10.5-1
ii  libmessagecomposer4   4:4.10.5-1
ii  libmessagecore4   4:4.10.5-1
ii  libmessagelist4   4:4.10.5-1
ii  libmessageviewer4 4:4.10.5-1
ii  libnepomukcore4   4:4.10.5-1
ii  libpimcommon4 4:4.10.5-1
ii  libqt4-dbus   4:4.8.5+dfsg-2
ii  libqt4-network4:4.8.5+dfsg-2
ii  libqt4-xml4:4.8.5+dfsg-2
ii  libqtcore44:4.8.5+dfsg-2
ii  libqtgui4 4:4.8.5+dfsg-2
ii  libqtwebkit4  2.2.1-6
ii  libsolid4 4:4.10.5-1
ii  libsoprano4   2.9.2+dfsg.1-1
ii  libstdc++64.8.1-6
ii  libtemplateparser44:4.10.5-1
ii  perl  5.14.2-21

Versions of packages kmail recommends:
ii  gnupg-agent   2.0.20-1
ii  gnupg22.0.20-1
ii  pinentry-gtk2 [pinentry-x11]  0.8.1-1

Versions of packages kmail suggests:
ii  bogofilter 1.2.2+dfsg1-3
pn  clamav | f-prot-installer  none
ii  kaddressbook   4:4.10.5-1
pn  kleopatra  none
ii  procmail   3.22-20
ii  spambayes  1.1a6-1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#717110: kmail: status filter unread unusable

[Shai Berger]

Package: kmail
Version: 4:4.10.5-1
Severity: normal
Tags: upstream

Dear Maintainer,

When the status filter on the message list is set to Unread, every message
whose status changes to read is immediately removed from the list (except
when messages are threaded and the message has an unread child). This may
seem to make sense, but is in fact surprising and unwelcome; the fact that a
message I am looking at is already gone from the list, and if I press
right-arrow (next message) then left arrow (prev message) I won't get back
to it, is a real hindrance.

This is a regression from KMail 1.

https://bugs.kde.org/show_bug.cgi?id=322455 (filed by me, same description
and more details).

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kmail depends on:
ii  kde-runtime   4:4.10.5-1
ii  kdepim-runtime4:4.10.5-1
ii  kdepimlibs-kio-plugins4:4.10.5-1
ii  libakonadi-contact4   4:4.10.5-1
ii  libakonadi-kde4   4:4.10.5-1
ii  libakonadi-kmime4 4:4.10.5-1
ii  libakonadiprotocolinternals1  1.9.2-2
ii  libc6 2.17-7
ii  libcalendarsupport4   4:4.10.5-1
ii  libgcc1   1:4.8.1-6
ii  libgpgme++2   4:4.10.5-1
ii  libincidenceeditorsng44:4.10.5-1
ii  libkabc4  4:4.10.5-1
ii  libkcalcore4  4:4.10.5-1
ii  libkcalutils4 4:4.10.5-1
ii  libkcmutils4  4:4.10.5-1
ii  libkdecore5   4:4.10.5-1
ii  libkdepim44:4.10.5-1
ii  libkdeui5 4:4.10.5-1
ii  libkio5   4:4.10.5-1
ii  libkleo4  4:4.10.5-1
ii  libkmime4 4:4.10.5-1
ii  libknotifyconfig4 4:4.10.5-1
ii  libkontactinterface4  4:4.10.5-1
ii  libkparts44:4.10.5-1
ii  libkpgp4  4:4.10.5-1
ii  libkpimidentities44:4.10.5-1
ii  libkpimtextedit4  4:4.10.5-1
ii  libkpimutils4 4:4.10.5-1
ii  libkprintutils4   4:4.10.5-1
ii  libksieveui4  4:4.10.5-1
ii  libktnef4 4:4.10.5-1
ii  libmailcommon44:4.10.5-1
ii  libmailimporter4  4:4.10.5-1
ii  libmailtransport4 4:4.10.5-1
ii  libmessagecomposer4   4:4.10.5-1
ii  libmessagecore4   4:4.10.5-1
ii  libmessagelist4   4:4.10.5-1
ii  libmessageviewer4 4:4.10.5-1
ii  libnepomukcore4   4:4.10.5-1
ii  libpimcommon4 4:4.10.5-1
ii  libqt4-dbus   4:4.8.5+dfsg-2
ii  libqt4-network4:4.8.5+dfsg-2
ii  libqt4-xml4:4.8.5+dfsg-2
ii  libqtcore44:4.8.5+dfsg-2
ii  libqtgui4 4:4.8.5+dfsg-2
ii  libqtwebkit4  2.2.1-6
ii  libsolid4 4:4.10.5-1
ii  libsoprano4   2.9.2+dfsg.1-1
ii  libstdc++64.8.1-6
ii  libtemplateparser44:4.10.5-1
ii  perl  5.14.2-21

Versions of packages kmail recommends:
ii  gnupg-agent   2.0.20-1
ii  gnupg22.0.20-1
ii  pinentry-gtk2 [pinentry-x11]  0.8.1-1

Versions of packages kmail suggests:
ii  bogofilter 1.2.2+dfsg1-3
pn  clamav | f-prot-installer  none
ii  kaddressbook   4:4.10.5-1
pn  kleopatra  none
ii  procmail   3.22-20
ii  spambayes  1.1a6-1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#717111: kmail: when writing mail, subject line not right-aligned when RTL

[Shai Berger]

Package: kmail
Version: 4:4.10.5-1
Severity: minor
Tags: upstream l10n

Dear Maintainer,

When writing an RTL subject line in a new message, the subject line
control stays left-aligned -- but it should be right-aligned; text in
the message body does get the correct alignment automatically. 

Surprisingly, if the composer window is resized, the subject is then
aligned correctly; but it should align correctly already when the
subject is typed in.

Note that directionality is set correctly automatically; the problem
is only with alignment.

I reported this upstream as https://bugs.kde.org/show_bug.cgi?id=322459

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kmail depends on:
ii  kde-runtime   4:4.10.5-1
ii  kdepim-runtime4:4.10.5-1
ii  kdepimlibs-kio-plugins4:4.10.5-1
ii  libakonadi-contact4   4:4.10.5-1
ii  libakonadi-kde4   4:4.10.5-1
ii  libakonadi-kmime4 4:4.10.5-1
ii  libakonadiprotocolinternals1  1.9.2-2
ii  libc6 2.17-7
ii  libcalendarsupport4   4:4.10.5-1
ii  libgcc1   1:4.8.1-6
ii  libgpgme++2   4:4.10.5-1
ii  libincidenceeditorsng44:4.10.5-1
ii  libkabc4  4:4.10.5-1
ii  libkcalcore4  4:4.10.5-1
ii  libkcalutils4 4:4.10.5-1
ii  libkcmutils4  4:4.10.5-1
ii  libkdecore5   4:4.10.5-1
ii  libkdepim44:4.10.5-1
ii  libkdeui5 4:4.10.5-1
ii  libkio5   4:4.10.5-1
ii  libkleo4  4:4.10.5-1
ii  libkmime4 4:4.10.5-1
ii  libknotifyconfig4 4:4.10.5-1
ii  libkontactinterface4  4:4.10.5-1
ii  libkparts44:4.10.5-1
ii  libkpgp4  4:4.10.5-1
ii  libkpimidentities44:4.10.5-1
ii  libkpimtextedit4  4:4.10.5-1
ii  libkpimutils4 4:4.10.5-1
ii  libkprintutils4   4:4.10.5-1
ii  libksieveui4  4:4.10.5-1
ii  libktnef4 4:4.10.5-1
ii  libmailcommon44:4.10.5-1
ii  libmailimporter4  4:4.10.5-1
ii  libmailtransport4 4:4.10.5-1
ii  libmessagecomposer4   4:4.10.5-1
ii  libmessagecore4   4:4.10.5-1
ii  libmessagelist4   4:4.10.5-1
ii  libmessageviewer4 4:4.10.5-1
ii  libnepomukcore4   4:4.10.5-1
ii  libpimcommon4 4:4.10.5-1
ii  libqt4-dbus   4:4.8.5+dfsg-2
ii  libqt4-network4:4.8.5+dfsg-2
ii  libqt4-xml4:4.8.5+dfsg-2
ii  libqtcore44:4.8.5+dfsg-2
ii  libqtgui4 4:4.8.5+dfsg-2
ii  libqtwebkit4  2.2.1-6
ii  libsolid4 4:4.10.5-1
ii  libsoprano4   2.9.2+dfsg.1-1
ii  libstdc++64.8.1-6
ii  libtemplateparser44:4.10.5-1
ii  perl  5.14.2-21

Versions of packages kmail recommends:
ii  gnupg-agent   2.0.20-1
ii  gnupg22.0.20-1
ii  pinentry-gtk2 [pinentry-x11]  0.8.1-1

Versions of packages kmail suggests:
ii  bogofilter 1.2.2+dfsg1-3
pn  clamav | f-prot-installer  none
ii  kaddressbook   4:4.10.5-1
pn  kleopatra  none
ii  procmail   3.22-20
ii  spambayes  1.1a6-1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org