Bug#1000977: lintian: bogus elf-error in debug symbols

[Boris Pek]

Hi, I have faced with this quite annoying lintian bug during maintaining of mypsi-plus package: W: psi-plus-dbgsym: elf-error In program headers: Unable to find program interpreter name [usr/lib/debug/.build-id/b5/1539a4fbf03c5878734f256250491fe6be4ad8.debug]W: psi-plus-webkit-dbgsym: elf-error In program headers: Unable to find program interpreter name [usr/lib/debug/.build-id/78/3dd60a2ae37188510a3550ca76e08ae24ee581.debug] The problem is aggravated by impossibility of hiding of this warning nor bypsi-plus*-dbgsym.lintian-overrides files, nor by changing of lintian config("Disable-Tags" option in /usr/share/lintian/profiles/*/main.profile) Hope this will be solved one day. Best regards,Boris 

Bug#990129: libqt5core5a: breaks work of some QtWebEngine based programs

[Boris Pek]

Hi Dmitry,

> Can you please test if the .deb file attached to this message fixes the bug
> for you?
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989744#37
>
> In that file I reverted changes to src/corelib/mimetypes/qmimeprovider.cpp
> from that commit. These changes were not related to the main purpose of that
> commit, so this way we can still have the original bug fixed.

I tested proposed package libqt5core5a_5.15.2+dfsg-7_amd64.deb and may
confirm what it solves my problem with maps in QtWebEngine.

Best regards,
Boris

Bug#990129: libqt5core5a: breaks work of some QtWebEngine based programs

[Boris Pek]

Package: libqt5core5a
Version: 5.15.2+dfsg-6
Severity: important
X-Debbugs-Cc: tehnic...@yandex.ru


Hi,

I use Debian 11 (Bullseye) on work PC to develop Qt based projects. All worked
fine until update of Qt packages last week: one of our QML based application
stopped showing maps without any errors in stdin/stdout.

Today I spent few hours to find the root of problem. QtWebEngine is used for
displaying maps and it is quite problematic itself, but I was surprised to find
what problem was caused by update in QtCore library:
libqt5core5a:amd64 (5.15.2+dfsg-5, 5.15.2+dfsg-6)

And if I understand correctly here is the problematic patch:
https://salsa.debian.org/qt-kde-team/qt/qtbase/-/commit/5eaeb73

Could you revert it please?

Best regards,
Boris


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

Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8),
LANGUAGE=ru:en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libqt5core5a depends on:
ii  libc6  2.31-12
ii  libdouble-conversion3  3.1.5-6.1
ii  libgcc-s1  10.2.1-6
ii  libglib2.0-0   2.66.8-1
ii  libicu67   67.1-6
ii  libpcre2-16-0  10.36-2
ii  libstdc++6 10.2.1-6
ii  libzstd1   1.4.8+dfsg-2.1
ii  shared-mime-info   2.0-1
ii  zlib1g 1:1.2.11.dfsg-2

Versions of packages libqt5core5a recommends:
ii  qttranslations5-l10n  5.15.2-2

Versions of packages libqt5core5a suggests:
ii  libthai0  0.1.28-3

Bug#988601: unblock: eiskaltdcpp/2.4.2-1

[Boris Pek]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: tehn...@debian.org

Please unblock package eiskaltdcpp

This was a bugfix release of program with small amount of changes.
The most important one:
* Fix search on ADC hubs. (It was accidentally broken in 2.4.1 release.)

Notes:
Hub is just server software in terms of Direct Connect (DC aka NMDC) and
Advanced Direct Connect (ADC) protocols. For example, in Debian we have uhub
program which is ADC hub (without support of old DC protocol).

[ Reason ]
Bugfix release + updated translations.

Package was uploaded at 2021-03-03 01:02:49 +0300, almost ten days before
Hard Freeze (2021-03-12), but did not migrate to testing and I forgot to
check its status...

[ Impact ]
> What is the impact for the user if the unblock isn't granted?

Users connected only to ADC hubs will not be able to search files. All other
features (public and private chats, file exchange, observing file list, etc.)
work fine.

[ Tests ]
> What automated or manual tests cover the affected code?

There are no automated tests for code, but this version of program has been
successfully checked by a lot of users (including me) during long time
(since 2021-03-03).

[ Risks ]
There are no known risks.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
* I am upstream developer of program as well.
* Important patch: https://github.com/eiskaltdcpp/eiskaltdcpp/commit/e1717a8e
* Full diff: https://github.com/eiskaltdcpp/eiskaltdcpp/compare/v2.4.1...v2.4.2

unblock eiskaltdcpp/2.4.2-1



__debdiff.changes.diff
Description: Binary data

Bug#983682: Freeze exception for psi-plugins/1.5-2

[Boris Pek]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
X-Debbugs-CC: tehn...@debian.org, pkg-xmpp-de...@lists.alioth.debian.org

Dear release team,

Please consider a release exception for new package psi-plugins [1].

 This package contains officially supported plugins for Psi:
 * Attention
 * Autoreply
 * Birthday Reminder
 * Chess
 * Cleaner
 * Client Switcher
 * Conference Logger
 * Content Downloader
 * Enum Messages
 * Extended Menu
 * Extended Options
 * Gomoku Game
 * History Keeper
 * Image
 * Image Preview
 * Jabber Disk
 * Juick
 * Message Filter
 * OpenPGP
 * Off-the-Record
 * PEP Change Notify
 * QIP X-Statuses
 * Screenshot
 * Stop Spam
 * Storage Notes
 * Translate
 * Video Status
 * Watcher
 .
 Psi is a cross-platform powerful XMPP client designed for experienced users.
 User interface of program is very flexible in customization. For example,
 there are "multi windows" and "all in one" modes, support of different
 iconsets and themes. Psi supports file sharing and audio/video calls. Security
 is also a major consideration, and Psi provides it for both client-to-server
 (TLS) and client-to-client (OpenPGP, OTR, OMEMO) via appropriate plugins.


While psi-plugins package is new in Debian, the project has long history [2],
these plugins are stable and well tested in other GNU/Linux distros and even
in Debian [3], upstream is active and responsive, Psi 1.x releases cycle
receives only bug fixes, backported from git master branch (where active
development of next Psi 2.0 release is done).

Yes, Psi program may still be used without these plugins, but I believe that
additional features provided by them will be highly demanded by Debian users.

[1] https://tracker.debian.org/pkg/psi-plugins
[2] https://github.com/psi-im/plugins/tags
[3] In fact psi-plus-plugins package [4] used the same code base approximately
between Psi+ 0.16.19  and 1.2.40 releases [5] (2012-2017). Just a reminder:
Psi+ is a development branch of Psi with rolling release development model.
Users who wants to receive new features and bug fixes very quickly may use
Psi+ on daily basis. Users who do not care about new trends and prefer
constancy may choose Psi as it uses classical development model and its
releases are very rare.
[4] https://packages.debian.org/sid/psi-plus-plugins
[5] https://salsa.debian.org/xmpp-team/psi-plus/-/blob/master/debian/changelog

Best regards,
Boris

Bug#983678: Freeze exception for ncdc/1.22.1-2

[Boris Pek]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception

Dear release team,

Please consider a release exception for my package ncdc [1].

While this package is new in Debian, the project has long history [2], program
is stable and well tested in other GNU/Linux distros [3], upstream is active
and responsive.

Once ncdc package migrates to Debian Bullseye I'll open a removal request for
package microdc2 [4]:
+ project is dead:
   * official website does not exist anymore
   * last release (0.15.6) was in 2006 [5]
   * last commit to git repo was 2013 [6]
   * git repository has been explicitly marked as archived
   * upstream developer is not responsive
+ package is unmaintained [7]

Now microdc2 package does not have known RC bugs and its removal is not urgent
yet, but besides dead upstream there are few additional reasons for this:
* program does not support modern ADC protocol while in Debian repository there
  is server software [8] only for this protocol
* program lucks a lot of features required by regular users (for example,
  connecting to multiple hubs at the same time, etc.)
* ncdc fills the same niche (command line DC client) and has a lot of features
  absent in microdc2

[1] https://tracker.debian.org/pkg/ncdc
[2] https://dev.yorhel.nl/ncdc/changes
[3] https://repology.org/project/ncdc/versions
[4] https://tracker.debian.org/pkg/microdc2
[5] https://github.com/jnwatts/microdc2#news
[6] https://github.com/jnwatts/microdc2/commits/master
[7] https://bugs.debian.org/980954
[8] https://wiki.debian.org/Direct_Connect

Best regards,
Boris

Bug#982897: ITP: ncdc -- file sharing program using Direct Connect protocols

[Boris Pek]

Package: wnpp
Severity: wishlist
Owner: Boris Pek 
X-Debbugs-Cc: tehn...@debian.org

* Package name: ncdc
  Version : 1.22.1
  Upstream Contact: Yoran Heling 
* URL : https://dev.yorhel.nl/ncdc
* License : MIT (Expat)
  Programming Lang: C, ncurses
  Description : file sharing program using Direct Connect protocols

Ncdc is a lightweight direct connect client with a friendly ncurses interface.
It is compatible with EiskaltDC++, DC++, AirDC++, FlylinkDC++ and other DC
clients. Ncdc also interoperates with all common DC hub software that uses the
Direct Connect and Advanced Direct Connect protocols.
.
Program is NOT designed for using as daemon, but it may be used in combination
with a separate terminal multiplexer (screen, tmux) or detach utility (dtach)
if user needs such feature.

Bug#887799: RFP: atomtopubsub -- parse Atom feeds and send them to XMPP PubSub nodes

[Boris Pek]

Original project looks dead, but there is an active fork:
https://github.com/edhelas/atomtopubsub/network
https://github.com/imattau/atomtopubsub

Bug#981803: ITP: psi-plugins -- official plugins for Psi

[Boris Pek]

Package: wnpp
Severity: wishlist
Owner: Boris Pek 
X-Debbugs-Cc: tehn...@debian.org

* Package name: psi-plugins
  Version : 1.5
  Upstream Contact: https://github.com/psi-im/plugins/issues
* URL : https://github.com/psi-im/plugins
* License : GPL-2+
  Programming Lang: C++, Qt
  Description : official plugins for Psi

This package will contain officially supported plugins for Psi:
* Attention
* Autoreply
* Birthday Reminder
* Chess
* Cleaner
* Client Switcher
* Conference Logger
* Content Downloader
* Enum Messages
* Extended Menu
* Extended Options
* Gomoku Game
* History Keeper
* Image
* Image Preview
* Jabber Disk
* Juick
* Message Filter
* OpenPGP
* Off-the-Record
* PEP Change Notify
* QIP X-Statuses
* Screenshot
* Stop Spam
* Storage Notes
* Translate
* Video Status
* Watcher

Psi is a cross-platform powerful XMPP client designed for experienced users.
User interface of program is very flexible in customization. For example,
there are "multi windows" and "all in one" modes, support of different
iconsets and themes. Psi supports file sharing and audio/video calls. Security
is also a major consideration, and Psi provides it for both client-to-server
(TLS) and client-to-client (OpenPGP, OTR, OMEMO) via appropriate plugins.

List of supported XEPs you may found at:
https://github.com/psi-im/psi/wiki/Supported-XEPs

Bug#981185: [Pkg-matrix-maintainers] Bug#981185: nheko: video call results in a segfault

[Boris Pek]

Hi,

> Justification: voip is a new feature, there are still other
> improvements worth an upgrade
>
> I got this crash using nheko built using an older gcc 10 *till we have
> gcc 10.3 is in the archive)
>
> You can use https://people.debian.org/~praveen/nheko/ to reproduce this
> error.
>
> User glandos shared this stacktrace in upstream nheko matrix room.
>
> Thread 1 "nheko" received signal SIGSEGV, Segmentation fault.
> ...
> #0 0x7fff9ef0dcb5 in ?? () from
> /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
> ...
> #8 0x7fff9f622b2c in ?? () from
> /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
> ...

Please write which DE do you use and kind of session (X11 vs Wayland).
This is important. See: https://bugs.debian.org/978107

Best wishes,
Boris

Bug#979470: ITP: eiskaltdcpp-web -- Simple Web UI for eiskaltdcpp-daemon

[Boris Pek]

Package: wnpp
Severity: wishlist
Owner: Boris Pek 
X-Debbugs-Cc: tehn...@debian.org

* Package name: eiskaltdcpp-web
  Version : 1.0.1
  Upstream Contact: Boris Pek 
* URL : https://github.com/eiskaltdcpp/eiskaltdcpp-web
* License : GPL-3+
  Programming Lang: JavaScript, HTML
  Description : EiskaltDC++ Web UI

Official Web User Interface for eiskaltdcpp-daemon. It is designed for using on
embedded devices (for example in NAS) in user home network.

Features:
* Searching of files and directories
* List of current/queued downloads
* Status of connected hubs and basic statistics

Deb packages:
https://github.com/eiskaltdcpp/eiskaltdcpp-web-devel-debian

Bug#978107: [Pkg-xmpp-devel] Bug#978107: Bug#978107: gajim: Crashes when video preview is turned off in settings dialog window

[Boris Pek]

Hi,

>> Too bad. Still no problem for me.

I cannot reproduce this problem in my system in KDE and Fluxbox too.

But I have much more packages installed into the system than basic system +
gajim* packages + recommendations. And unfortunately I do not have enough free
space for one more guest environment in VirtualBox for tests...

Martin, could you try to reproduce this bug in a clean environment?

> I can reproduce in a virtual machine without any camera running sid also on
> amd64. I used GNOME Boxes with QEMU on KVM, emulating a QXL video card.

Do you use GNOME Shell launched above Wayland or X11 in your main system?

If you use Wayland than could you test the X11 session please? It should not
take too much time...

Best wishes,
Boris

Bug#977172: buster-pu: package qxmpp/1.0.0-4+deb10u1

[Boris Pek]

>>  I would like to push a fix for potential SEGFAULT on connection error
>>  in qxmpp library. Proposed patch is well tested in Debian unstable
>>  since qxmpp/1.0.0-5.
>
> Please go ahead.

Uploaded.

Thanks

-- 
Boris

Bug#977172: buster-pu: package qxmpp/1.0.0-4+deb10u1

[Boris Pek]

> Proposed patch is well tested in Debian unstable since qxmpp/1.0.0-5.
>
> Debdiff is attached.

The patch itself changes just 3 lines of code.
Debdiff is a bit longer due to packaging stuff...

Best regards,
Boris

Bug#977172: buster-pu: package qxmpp/1.0.0-4+deb10u1

[Boris Pek]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu


Dear release team,

I would like to push a fix for potential SEGFAULT on connection error in qxmpp
library. Proposed patch is well tested in Debian unstable since qxmpp/1.0.0-5.

Debdiff is attached.

Please consider accepting this as a buster-pu.

Thanks,
Boris
diff -Nru qxmpp-1.0.0/debian/changelog qxmpp-1.0.0/debian/changelog
--- qxmpp-1.0.0/debian/changelog	2019-01-19 21:56:20.0 +0300
+++ qxmpp-1.0.0/debian/changelog	2020-12-12 04:33:07.0 +0300
@@ -1,3 +1,10 @@
+qxmpp (1.0.0-4+deb10u1) buster; urgency=medium
+
+  * Add patch fix-segfault-on-connection-error:
+fixes potential SEGFAULT on connection error.
+
+ -- Boris Pek   Sat, 12 Dec 2020 04:33:07 +0300
+
 qxmpp (1.0.0-4) unstable; urgency=medium
 
   * Update debian/control:
diff -Nru qxmpp-1.0.0/debian/patches/fix-segfault-on-connection-error.patch qxmpp-1.0.0/debian/patches/fix-segfault-on-connection-error.patch
--- qxmpp-1.0.0/debian/patches/fix-segfault-on-connection-error.patch	1970-01-01 03:00:00.0 +0300
+++ qxmpp-1.0.0/debian/patches/fix-segfault-on-connection-error.patch	2020-12-12 04:15:35.0 +0300
@@ -0,0 +1,31 @@
+Description: Fix potential SEGFAULT on connection error
+ `socketError()` calls `connectToNextDNSHost()` which might cause
+ `socketError()` synchronously (and recursively), thus not giving a
+ change for updating `nextSrvRecordIdx`.
+ .
+ Overall, this results in attempting to connect to the same DNS record
+ recursively, until the stack is exhausted, resulting in SEGFAULT.
+ .
+ One of the solutions (done in this commit) is to increment the record
+ index _before_ attempting to connect.
+Origin: upstream, https://github.com/qxmpp-project/qxmpp/commit/daa03c8e
+Last-Update: 2019-10-12
+
+
+--- a/src/client/QXmppOutgoingClient.cpp
 b/src/client/QXmppOutgoingClient.cpp
+@@ -165,11 +165,10 @@
+ 
+ void QXmppOutgoingClientPrivate::connectToNextDNSHost()
+ {
++auto curIdx = nextSrvRecordIdx++;
+ connectToHost(
+-dns.serviceRecords().at(nextSrvRecordIdx).target(),
+-dns.serviceRecords().at(nextSrvRecordIdx).port());
+-
+-nextSrvRecordIdx++;
++dns.serviceRecords().at(curIdx).target(),
++dns.serviceRecords().at(curIdx).port());
+ }
+ 
+ /// Constructs an outgoing client stream.
diff -Nru qxmpp-1.0.0/debian/patches/series qxmpp-1.0.0/debian/patches/series
--- qxmpp-1.0.0/debian/patches/series	2019-01-19 21:56:19.0 +0300
+++ qxmpp-1.0.0/debian/patches/series	2020-12-12 04:15:35.0 +0300
@@ -1 +1,2 @@
 bump-SONAME.patch
+fix-segfault-on-connection-error.patch

Bug#956678: xpra: package is uninstallable

[Boris Pek]

Package: xpra
Version: 3.0.8+dfsg1-1
Severity: serious

Hi,

Is Debian unstable system with all updates:

$ LC_ALL=C sudo apt install -V xpra
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 xpra : Depends: xserver-xorg-input-void but it is not installable
E: Unable to correct problems, you have held broken packages.

Let's check xserver-xorg-input-void package:
https://tracker.debian.org/pkg/xserver-xorg-input-void

It was removed from Debian:
https://bugs.debian.org/955603

Best regards,
Boris

Bug#875243: [yagf] Future Qt4 removal from Buster

[Boris Pek]

Hi everyone,

> Status update: Qt4 has now been droppped from testing, qt4 will be removed
> from unstable by end of February (along with the remaining rdeps (currently 
> 15)).

As I see yagf package is still in Debian repo.
And now I have enough free time for updating it...
So I am going to upload updated version ported to Qt5 today if no-one objects.

Best regards,
Boris

Bug#949638: tesseract: uses -march=native

[Boris Pek]

> For example, default compiler flags in Debian unstable now:
> $ dpkg-buildflags --get CXXFLAGS
> -g -O2 -fdebug-prefix-map=/home/boris=. -fstack-protector-strong -Wformat 
> -Werror=format-security
> $ dpkg-buildflags --get CFLAGS
> -g -O2 -fdebug-prefix-map=/home/boris=. -fstack-protector-strong -Wformat 
> -Werror=format-security
> $ dpkg-buildflags --get CPPFLAGS
> -Wdate-time -D_FORTIFY_SOURCE=2
> $ dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro

This is on amd64 of course.

Sorry for extra message.

-- 
Boris

Bug#949638: tesseract: uses -march=native

[Boris Pek]

Hi,

> I see the problem of builds which depend on an autobuilder which may be
> different for each build. What would be the best solution for
> distributions?

1) Special configuration option, which disables all CPU specific optimizations
   in compiler flags.

or

2) Special configuration option, which disables all additional compiler flags
   which tesseract developers tends to add. Only compiler flags from system
   environment will be used in this case.

For example, default compiler flags in Debian unstable now:
$ dpkg-buildflags --get CXXFLAGS
-g -O2 -fdebug-prefix-map=/home/boris=. -fstack-protector-strong -Wformat 
-Werror=format-security
$ dpkg-buildflags --get CFLAGS
-g -O2 -fdebug-prefix-map=/home/boris=. -fstack-protector-strong -Wformat 
-Werror=format-security
$ dpkg-buildflags --get CPPFLAGS
-Wdate-time -D_FORTIFY_SOURCE=2
$ dpkg-buildflags --get LDFLAGS
-Wl,-z,relro

But many (if not most of) packages are built with additional flags now, see:
https://wiki.debian.org/Hardening

> Suppress the code using a new configure option or some
> magic which detects that the build is for a Debian distribution?

This is never an option for Debian. Also do not forget about other GNU/Linux
and *BSD distributions...

Hope this helps.

Best regards,
Boris

Bug#942184: New stable version is available: 5.13.1

[Boris Pek]

Package: qtwebkit-opensource-src
Version: 5.212.0~alpha3-4
Severity: wishlist

Hi,

Please update QtWebkit to the latest stable version 5.13.1.
Tarballs are available here:
https://download.qt.io/snapshots/ci/qtwebkit/5.212/latest/src/submodules/

Best wishes,
Boris

Bug#875243: [yagf] Future Qt4 removal from Buster

[Boris Pek]

Hi,

> similar ping as for qpxtool, last upstream commits are from 2015. Are you
> planning to port it yourself or should it be removed?

Patch for yagf port to Qt5 already exists at least in Mageia GNU/Linux distro.

I may backport this patch to yagf 0.9.3.2 or update yagf package to latest
release 0.9.5 and prepare patches with fixes for some regressions in this
version of program. (I have not decided yet.)

Do you have any time schedule for Qt4 removal? At least preliminary.

Best wishes,
Boris

Bug#935485: [Pkg-kde-extras] Looking for help to adopt recently removed package, kcollectd

[Boris Pek]

Hi,

> I've been following a bit of a breadcrumb trail, and I hope I'm in the right
> place now. kcollectd, a tool for viewing log information, has recently been
> removed from unstable because it lacked a Qt 5 port [1]. I have ported that
> package and I've taken over the upstream (which has been dead for years) [2].
> I'm offering to maintain the Debian package, but I have received very little
> response to my ITA RFS bug [3]. Should I refile this as an ITP bug, since the
> package has, in fact, already been removed?

Yes, please sent ITP bug report against WNPP package, update changelog in your
package noticing closing of this bug and update the title of your RFS bug
report accordingly.

> I spoke with Scott Kitterman, who requested the removal, and he said
> knows of no other reason the package should be removed. The updated
> packaging fixes several outstanding bugs, and makes the Debian lintian
> report much cleaner (one is, I believe, a false positive, and the other
> is due to lack of package tests which aren't really relevant to this kind of
> UI software).
>
> Is anyone here willing to sponsor this package, offer any criticism of
> the package, or direct me to a place where I might get such help?

I would suggest to ask about sponsoring of your package in mailing list:
pkg-kde-talk (at) alioth-lists.debian.net

Unfortunately, I do not have enough spare time for sponsoring others packages
now and I have no idea about this specific package, so I cannot help directly.

Thanks for your contributions to Debian!

Best wishes,
Boris

Bug#875141: [qpxtool] Future Qt4 removal from Buster

[Boris Pek]

Hi,

> qpxtool seems dead upstream.

Yes, I know.

> Are you planning to port it to Qt5 yourself

Yes.

> or should it be removed from the archive?

I prefer to try port to Qt5 at first. If I will see that it requires too much
time I'll send "rm" request myself.

Best regards,
Boris

Bug#934895: psi-plus: otr plugin does not work with some clients

[Boris Pek]

control: reassign 934895 psi-plus-plugins
control: merge 747918 934895

Hi,

> as much as i tested this problem is somehow related to debian. other distros
> works well.

OTR plugin in Psi+ has few well known issues. And they are not Debian specific,
but reproducible on all supported systems.

Best regards,
Boris

Bug#927208: unblock: psi-plus/1.4.554-2

[Boris Pek]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal


Dear Release Team,

Please unblock package psi-plus.

I uploaded updated package March 21, but forgot to send unblock request.
Fixing this now.

Changes in updated package:
* Add patch disable-usage-of-system-proxies. (Closes: #874561)
* Add patch fix-autoscroll-in-chats.

debdiff is attached.

Thanks!


unblock psi-plus/1.4.554-2
diff -Nru psi-plus-1.4.554/debian/changelog psi-plus-1.4.554/debian/changelog
--- psi-plus-1.4.554/debian/changelog	2019-02-17 03:07:36.0 +0300
+++ psi-plus-1.4.554/debian/changelog	2019-03-21 00:41:20.0 +0300
@@ -1,3 +1,10 @@
+psi-plus (1.4.554-2) unstable; urgency=medium
+
+  * Add patch disable-usage-of-system-proxies. (Closes: #874561)
+  * Add patch fix-autoscroll-in-chats.
+
+ -- Boris Pek   Thu, 21 Mar 2019 00:41:20 +0300
+
 psi-plus (1.4.554-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru psi-plus-1.4.554/debian/patches/disable-usage-of-system-proxies.patch psi-plus-1.4.554/debian/patches/disable-usage-of-system-proxies.patch
--- psi-plus-1.4.554/debian/patches/disable-usage-of-system-proxies.patch	1970-01-01 03:00:00.0 +0300
+++ psi-plus-1.4.554/debian/patches/disable-usage-of-system-proxies.patch	2019-03-21 00:41:20.0 +0300
@@ -0,0 +1,29 @@
+Description: Disable usage of system proxies
+Last-Update: 2019-03-21
+Origin: upstream,
+ https://github.com/psi-im/psi/commit/911880f1,
+ https://github.com/psi-im/iris/commit/ce6f4e58
+Bug: https://github.com/psi-plus/main/issues/758
+Bug-Debian: https://bugs.debian.org/874561
+
+
+--- a/iris/src/irisnet/noncore/cutestuff/bsocket.cpp
 b/iris/src/irisnet/noncore/cutestuff/bsocket.cpp
+@@ -141,6 +141,7 @@
+ SockData sd;
+ sd.state = Created;
+ sd.sock = new QTcpSocket(this);
++sd.sock->setProxy(QNetworkProxy::NoProxy);
+ sd.sock->setReadBufferSize(READBUFSIZE);
+ sd.relay = new QTcpSocketSignalRelay(sd.sock, this);
+ sd.resolver = 0;
+--- a/src/psicon.cpp
 b/src/psicon.cpp
+@@ -482,6 +482,7 @@
+ }
+ 
+ // proxy
++QNetworkProxyFactory::setUseSystemConfiguration(false); // we have qca-based own implementation
+ ProxyManager *proxy = ProxyManager::instance();
+ proxy->init(>accountTree);
+ if (accountMigration) proxy->migrateItemList(d->optionsMigration.proxyMigration);
diff -Nru psi-plus-1.4.554/debian/patches/fix-autoscroll-in-chats.patch psi-plus-1.4.554/debian/patches/fix-autoscroll-in-chats.patch
--- psi-plus-1.4.554/debian/patches/fix-autoscroll-in-chats.patch	1970-01-01 03:00:00.0 +0300
+++ psi-plus-1.4.554/debian/patches/fix-autoscroll-in-chats.patch	2019-03-21 00:41:20.0 +0300
@@ -0,0 +1,31 @@
+Description: Fix autoscroll in chats
+Last-Update: 2019-03-21
+Origin: upstream, https://github.com/psi-im/psi/commit/5140f191
+Bug: https://github.com/psi-im/psi/issues/430
+
+
+diff --git a/src/chatview_te.cpp b/src/chatview_te.cpp
+index 0def3505..08ea6969 100644
+--- a/src/chatview_te.cpp
 b/src/chatview_te.cpp
+@@ -318,6 +318,8 @@ void ChatView::dispatchMessage(const MessageView )
+ switch (mv.type()) {
+ case MessageView::Message:
+ {
++int scrollPos = verticalScrollBar()->value();
++bool doScrollBottom = atBottom();
+ bool isReplace = !replaceId.isEmpty();
+ QTextCursor cursor = textCursor(), replaceCursor;
+ auto sel = PsiRichText::saveSelection(this, cursor);
+@@ -362,6 +364,11 @@ void ChatView::dispatchMessage(const MessageView )
+ cursor.movePosition(QTextCursor::End); // ensure everything else is inserted into the end
+ PsiRichText::restoreSelection(this, cursor, sel);
+ setTextCursor(cursor);
++if (doScrollBottom) {
++scrollToBottom();
++} else {
++verticalScrollBar()->setValue(scrollPos);
++}
+ break;
+ }
+ case MessageView::Subject:
diff -Nru psi-plus-1.4.554/debian/patches/series psi-plus-1.4.554/debian/patches/series
--- psi-plus-1.4.554/debian/patches/series	1970-01-01 03:00:00.0 +0300
+++ psi-plus-1.4.554/debian/patches/series	2019-03-21 00:41:20.0 +0300
@@ -0,0 +1,2 @@
+disable-usage-of-system-proxies.patch
+fix-autoscroll-in-chats.patch

Bug#876331: Displaced after start

[Boris Pek]

Hi,

> Since the update to new qt, after restart of psi, the window is always
> displaced by -1 for X and -10 for Y.
>
> This is really annoying and it is the only application where I see such
> a displacement.
>
> I use fvwm window manager. And while my border width of 1 gives the hint
> that the new psi seems to ignore that for placement in X direction, I
> see no reason or the displacement in Y direction.

This problem is solved in Qt 5.12.x. But unfortunately Debian Buster will
be released with Qt 5.11.3 and Psi+ developers do not want to prepare a
workaround for this problem for old versions of Qt. So most probably this
bug will be solved only in Debian Bullseye.

Best wishes,
Boris

Bug#901948: [libsignal-protocol-c] New version of library is available

[Boris Pek]

Hi,

> am I right in assuming that this issue is blocking the updating of
> newer dino-im releases after this commit?
> https://github.com/dino/dino/commit/7012023d5997287b1ed300e03a4c5b91eb6c9c39

I do not think so because it just a question of one simple patch in a package.

> An update of libsignal-protocol-c before the buster freeze would be
> highly appreciated.

I am working on this.

Best wishes,
Boris

Bug#918748: nmu: kadu_4.1-1.1

[Boris Pek]

control: reopen 918748 =


Hi,

> Then qxmpp ABI was broken and that needs a SONAME bump on qxmpp.

SONAME in qxmpp library is fixed now.
Please rebuild kadu with libqxmpp1.

Thanks,
Boris

Bug#919487: [libqxmpp0] Bump SONAME of library and add symbols file

[Boris Pek]

retitle 919487 Bump SONAME of the library
X-Debbugs-CC: jeremy.la...@m4x.org


Hi Jeremy,

After reading of all documentation about symbols files on Debian and Ubuntu
resources and after playing with libqxmpp0.symbols for qxmpp-0.9.3 and
qxmpp-1.0.0 I see that they are almost useless in our case, because they
are solving completely another task.

For checking of ABI compatibility between different versions of library
special tools like ABI Compliance Checker may be used. But while qxmpp
development does not follow any guideline similar to [1] using of such
tools will be useless as well.

So the current plan of actions is now related only with increasing of SONAME.
I am not going to add symbols file anymore.

Any comments?

[1] https://community.kde.org/Policies/Binary_Compatibility_Issues_With_C%2B%2B

Best regards,
Boris

Bug#919487: [libqxmpp0] Bump SONAME of library and add symbols file

[Boris Pek]

Package: libqxmpp0
Version: 1.0.0-1
Severity: important
X-Debbugs-CC: jeremy.la...@m4x.org


Hi Jeremy,

During long time of maintaining of qxmpp package in Debian archive there
were no packages which were depending from it, so unchanged SONAME (and
package name) did not cause to any problems.

But recently I have found that since 2015 [1] kadu package has become a
reverse dependency of qxmpp.

Unfortunately I have found it after upload of qxmpp/1.0.0-1 to unstable.
Happily qxmpp have a stable API and no changes in kadu sources are
required. But ABI of libqxmpp0 has been somehow changed since 0.9.3-1
and kadu package needs rebuild against it.

I thought that simple binNMU will resolve a situation. But Release Team
requires [2] an increasing of SONAME of library before binNMU.

So my current plan is:
* Change SONAME of library to libqxmpp.so.1 (patch in Debian package +
  similar commit in upstream).
* Rename package libqxmpp0 to libqxmpp1 and upload it to experimental
  (and wait its processing through a NEW queue).
* Upload updated package to unstable and request a binNMU for kadu
  package.

As for changes in ABI between qxmpp/0.9.3-1 and xmpp/1.0.0-1, it is
difficult to find the root of these changes now: they may be caused by
changes in order of functions, in size of structures, in compiler
options, etc.

Unfortunately, we did not provide a symbols file for qxmpp library in a
package in the past so changes in ABI were not detected in time.

I am going to add a symbols file to a package to prevent repeating of
such situation in a future.

More over thanks to special PPA on Launchpad [3] we will be able to
notice ABI changes during library development.

As for library versions in SONAME I decided to increase it only to "1"
(libqxmpp.so.1), because this it enough for now.

After the monitoring the speed of ABI changes in the future we will be
able to switch to any convenient versions scheme (libqxmpp.so.X or
libqxmpp.so.X.Y). (Where X and Y are not related anyhow to library
version as far as you know.)

If you don't have objections I will do changes described above ASAP.

[1] https://tracker.debian.org/media/packages/k/kadu/changelog-4.1-1.1
[2] https://bugs.debian.org/918748
[3] https://launchpad.net/~tehnick/+archive/ubuntu/qxmpp-devel

Best regards,
Boris

Bug#918748: nmu: kadu_4.1-1.1

[Boris Pek]

>>  This is my first binNMUs, so please correct me if I am doing anything wrong.
>
> qxmpp didn't bump the SONAME. So why does kadu need a rebuild?

Library API was not changed, so where were no reasons to bump SOVERSION.
But it looks what there are some changes in ABI which cause to segmentation
fault during connection to XMPP network (after entering of password):

(gdb) bt full
#0  0x7617ed98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7618e7e0 in QString::compare_helper(QChar const*, int, char 
const*, int, Qt::CaseSensitivity) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fffe07f5fb5 in QXmppRosterManager::handleStanza(QDomElement const&) 
()
at /usr/lib/x86_64-linux-gnu/libqxmpp.so.0
#3  0x7fffe07d8661 in QXmppClient::_q_elementReceived(QDomElement const&, 
bool&) ()
at /usr/lib/x86_64-linux-gnu/libqxmpp.so.0
#4  0x7fffe0820545 in  () at /usr/lib/x86_64-linux-gnu/libqxmpp.so.0
#5  0x762e36cb in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
...

After rebuilding of kadu with new qxmpp it works fine.

Best regards,
Boris

Bug#918748: nmu: kadu_4.1-1.1

[Boris Pek]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-CC: sha...@debian.org

Package with qxmpp library was updated today and is successfully built for all
supported architectures: https://buildd.debian.org/status/package.php?p=qxmpp
Please schedule the binNMUs for rebuilding of kadu packages with qxmpp/1.0.0-1.

  nmu kadu_4.1-1.1 . ANY . buster . -m "rebuild after update of qxmpp"

This is my first binNMUs, so please correct me if I am doing anything wrong.

Thanks,
Boris

Bug#541538: Processed: severity of 697119 is important

[Boris Pek]

Hi Felipe,

Why have you decreased the level of severity of this bug report?
Have you seen the justification for increasing it to "grave"?

Best regards,
Boris

Bug#910506: split package into architecture dependent and independent ones

[Boris Pek]

Hi Martin,

> Currently only one, architecture dependent package is created.
> However, most of prosody consists of architecture independent files.
>
> I like to separate the few .so files into prosody-lib to save some
> space on the archive.
>
> Any objections?

Yes, I have ones.

At first let's look at package size:
https://packages.debian.org/experimental/prosody
It is about 282.4 KB. And this is very small size.

Next, let's remember that each separate package increases size of list
of packages in Debian archive:
https://cdn-aws.deb.debian.org/debian/dists/unstable/main/
which will be downloaded by all Debian users even is they do not use
this package.

And the last but not least: as far as I know there are no other programs
which will use this library, even in perspective.

Thus you offer to increase complexity of source package (split on few
packages with declaration of relationships between them), possibly
increase work of ftp-masters (think about changing of SOVERSIONs in the
future, etc.) and increase of size of lists of packages just for
decreasing size of binary packages to about tens of kilobytes?

I would suggest you to reconsider all pros and cons of this decision.

Best regards,
Boris

Bug#908962: wine: please add q4wine package to Suggests

[Boris Pek]

Package: wine
Version: 3.0.2-3
Severity: wishlist


Dear maintainer,

Please add q4wine package to Suggests of wine package.

Best regards,
Boris

Bug#905659: qt5keychain-dev still makes psi-plus ftbfs

[Boris Pek]

Control: tags -1 - ftbfs

Hi Helmut,

> Control: severity -1 serious
> Control: tags -1 + ftbfs
> Control: affects -1 + src:psi-plus
>
> Give that the bug is a FTBFS it should still be serious. If you disagree
> with the severity on qt5keychain-dev, the solution is to clone a lower
> severity bug and leave the rc bug with psi-plus.
>
> Lowering the severity or removing the ftbfs tag will simply cause people
> to file duplicates.

It was not my idea to reassign this bug report to qt5keychain-dev package
instead of opening a new one. But this was done and now this bug report is
not about psi-plus package anymore, so its meta-data should be related to
package src:qtkeychain.

Package src:qtkeychain is not FTBFS, so this tag is wrong. I am not sure
which severity is better, but severity "serious" looks wrong to me.

As for src:psi-plus package: it is not FTBFS now (I have updated it this
night, see [1]), so nor duplicates, not new bug reports are required.
But I have not checked other reverse dependencies of src:qtkeychain package
due to lack of free time. Let's hope that qtkeychain maintainers will do it.

[1] https://tracker.debian.org/media/packages/p/psi-plus/changelog-1.3.400-1

Best regards,
Boris

Bug#905659: psi-plus FTBFS: cannot find -lsecret-1

[Boris Pek]

control: reassign -1 qt5keychain-dev
control: found -1 0.9.0-1


07.08.2018, 23:54, "Sune Vuorela" :
> reassign -1 qt5keychain-dev
> thank you
>
> After a quick investigation, the issue seems to be the cmake configuration
> files in qt5keychain-dev:
>
> $ grep -i secret /usr/lib/x86_64-linux-gnu/cmake/Qt5Keychain/*
> /usr/lib/x86_64-linux-gnu/cmake/Qt5Keychain/Qt5KeychainLibraryDepends-
> debian.cmake: IMPORTED_LINK_INTERFACE_LIBRARIES_DEBIAN
> "Qt5::Core;secret-1;gio-2.0;gobject-2.0;glib-2.0;Qt5::DBus"
>
> which basically tells users that "whenever you link Qt5Keychain, you should
> also link these...".
>
> Given that Qt5Keychain seems to only expose QtCore types on the api, all the
> others seems to not be needed and should be removed.
>
> The fix is probably that QtKeychain always link everything PUBLIC in
> target_link_libraries in CMakeLists.txt.
>
> The CMakeLists.txt in general could need a bit of modern cmake love.
>
> /Sune

Bug#905659: psi-plus FTBFS: cannot find -lsecret-1

[Boris Pek]

> | /usr/bin/ld: cannot find -lsecret-1
> | collect2: error: ld returned 1 exit status
> | make[4]: *** [src/CMakeFiles/psi-plus.dir/build.make:6175: psi/psi-plus] 
> Error 1
> | make[4]: Leaving directory '/<>/debian/builddir1'
> | make[3]: *** [CMakeFiles/Makefile2:283: src/CMakeFiles/psi-plus.dir/all] 
> Error 2
> | make[3]: Leaving directory '/<>/debian/builddir1'
> | make[2]: *** [Makefile:133: all] Error 2
> | make[2]: Leaving directory '/<>/debian/builddir1'
> | dh_auto_build: cd debian/builddir1 && make -j8 "INSTALL=install 
> --strip-program=true" returned exit code 2
> | make[1]: *** [debian/rules:43: override_dh_auto_build] Error 2
> | make[1]: Leaving directory '/<>'
> | make: *** [debian/rules:36: build] Error 2
> | dpkg-buildpackage: error: debian/rules build subprocess returned exit 
> status 2
>
> libsecret-1-dev is not installed during build. Maybe a missing
> dependency?

Hi Helmut,

Thanks for a bug report. As far as I see this is due to changes in
qtkeychain 0.9.0-1 [1]:

>  * Add new build dependencies (pkg-config and libsecret-1).

[1] 
https://metadata.ftp-master.debian.org/changelogs/main/q/qtkeychain/qtkeychain_0.9.0-1_changelog

Dear qtkeychain maintainers,

Please make a correct library transition next time.

Best regards,
Boris

Bug#897338: sddm: Cannot launch SDDM at boot time and from console

[Boris Pek]

Hi,

> Hi, I am on Debian Unstable on real hardware and I have the same problem,
> SDDM launches but there is dark screen on TTY7 with only my mouse.

Try instructions from Debian wiki [1]. They solved this problem for NVIDIA
GeForce GTX 1050 Ti Mobile on my laptop.

[1] https://wiki.debian.org/NvidiaGraphicsDrivers/Optimus

Best wishes,
Boris

Bug#902181: pulseaudio: new pulseaudio update try to remove kde stuff

[Boris Pek]

Hi,

> Both plasma-pa and paprefs need porting. Each have their respective
> (severity serious) bug. Pulseaudio itself does not need fixing. Therefore
> I'm closing this bug.

Could you explain why there were no transition (via experimental)?

Best regards,
Boris

Bug#902118: quassel-core: quasselcore unable to load installed libQt5Core.so.5

[Boris Pek]

Hi,

I am not a maintainer of this package, but have some thoughts about possible
reasons of your problem.

Could you show the output of few commands?

$ ls -lh /usr/lib/x86_64-linux-gnu/libQt5Core.so.*
$ file /usr/lib/x86_64-linux-gnu/libQt5Core.so.*

Try to reinstall libqt5core5a package:

$ sudo apt-get install --reinstall libqt5core5a

Best wishes,
Boris

Bug#901948: [libsignal-protocol-c] New version of library is available

[Boris Pek]

Source: libsignal-protocol-c
Version: 2.3.1+git20171007-3
Severity: wishlist


Hi,

Could you update this library to latest git tag [1]?
Small discussion about it may be found at [2].

[1] https://github.com/signalapp/libsignal-protocol-c/releases/tag/v2.3.2
[2] https://github.com/signalapp/libsignal-protocol-c/issues/107

Best regards,
Boris

Bug#892509: [chromium] uBlock Origin extension do not work anymore

[Boris Pek]

Package: chromium
Version: 65.0.3325.146-1
Severity: important


Hi,

uBlock Origin extension do not work with new version of chromium
(65.0.3325.146-1), with previous version from unstable (64.0.3282.119-2) all
works fine. What have changed? Any recommendations how to fix loading of this
popular ad blocker?

Best regards,
Boris


--- System information. ---
Kernel:   Linux 4.15.0-1-amd64

Debian Release: buster/sid
  500 unstableriot.im 
  500 unstabledeb.debian.org 
  500 unstabledeb-multimedia.org 
1 experimentaldeb.debian.org 

Bug#884956: vlc: icons are too big

[Boris Pek]

Hi,

VLC 3.0.1 has been released recently. There is interesting note in its 
[changelog]:
...
Qt Interface:
 * Improve scaling on HiDPI displays
...

Try this new version of VLC please to check if the bug is still reproducible.

[changelog] 
http://git.videolan.org/?p=vlc/vlc-3.0.git;a=blob;f=NEWS;hb=399713b542d29c81300d23a657fd2ec22bc927b6

Best wishes,
Boris

Bug#891123: RM: open-axiom -- RoQA; dead upstream, unmaintained

[Boris Pek]

Package: ftp.debian.org
Severity: normal


Hi,

Please remove src:open-axiom from Debian unstable:
* last package update was in the end of 2013
* package is FTBFS since the beginning of 2015 and there is no activity from
  package maintainer during this time
* nobody was interested enough for preparing a patch or NMU for fixing build
  of this package
* upstream project looks dead: last stable release was April 1 2013 [1] and
  last commit in SVN repo was November 03 2015
* there is alternative package src:axiom which is in a good shape

[1] http://www.open-axiom.org/news.html
[2] https://sourceforge.net/p/open-axiom/code/commit_browser

Best regards,
Boris

Bug#886514: Verdigris - header only Qt moc replacement

[Boris Pek]

Hi,

> I was wondering if Verdigris would be suitable for this team.
> Here's RFP: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886514
>
> It has just reached 1.0,
> and I am thinking about Debian packaging.
> Your team and sponsorship would be very helpful.

I have seen this article [1] long time ago (about 2016 IIRC). And provided
library was just a proof of concept. Have anything changed since that time?

Are developers going to support this library on constant basis?
Do you have examples of applications which use this library?

[1] https://woboq.com/blog/verdigris-qt-without-moc.html

Best wishes,
Boris

Bug#889044: udev: system upgrade is broken

[Boris Pek]

Package: udev
Version: 237-1
Severity: normal


Dear Maintainer,

I have upgraded a remote system (connected via ssh) as usual, but this
time the upgrading process was broken with strange results:

dina@Dina:~$ export LC_ALL=C
dina@Dina:~$ sudo apt-get dist-upgrade -V
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up udev (237-1) ...
Failed to connect to bus: No such file or directory
Failed to connect to bus: No such file or directory
invoke-rc.d: could not determine current runlevel
Failed to connect to bus: No such file or directory
Failed to connect to bus: No such file or directory
Failed to connect to bus: No such file or directory
invoke-rc.d: initscript udev, action "restart" failed.
Failed to connect to bus: No such file or directory
dpkg: error processing package udev (--configure):
 installed udev package post-installation script subprocess returned error exit 
status 1
Setting up exim4-daemon-light (4.90-5) ...
Failed to connect to bus: No such file or directory
invoke-rc.d: could not determine current runlevel
Failed to connect to bus: No such file or directory
Failed to connect to bus: No such file or directory
Failed to connect to bus: No such file or directory
invoke-rc.d: initscript exim4, action "start" failed.
Failed to connect to bus: No such file or directory
dpkg: error processing package exim4-daemon-light (--configure):
 installed exim4-daemon-light package post-installation script subprocess 
returned error exit status 1
Errors were encountered while processing:
 udev
 exim4-daemon-light
E: Sub-process /usr/bin/dpkg returned an error code (1)


And now I cannot even reboot a system remotely...


dina@Dina:~$ sudo shutdown -r now
Failed to connect to bus: No such file or directory
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon.


dina@Dina:~$ ls -alp /dev/initctl
lrwxrwxrwx 1 root root 25 Jan 27 09:44 /dev/initctl -> /run/systemd/initctl/fifo
dina@Dina:~$ ls -alp /dev/initctl /run/systemd/initctl/fifo
lrwxrwxrwx 1 root root 25 Jan 27 09:44 /dev/initctl -> /run/systemd/initctl/fifo
prw--- 1 root root  0 Feb  1 14:46 /run/systemd/initctl/fifo


dina@Dina:~$ sudo dmesg | grep -i systemd
[3.958989] systemd[1]: RTC configured in localtime, applying delta of 180 
minutes to system time.
[3.985200] systemd[1]: systemd 236 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN 
default-hierarchy=hybrid)
[4.004135] systemd[1]: Detected architecture x86-64.
[4.004258] systemd[1]: Set hostname to .
[4.027669] systemd[1]: File /lib/systemd/system/systemd-journald.service:35 
configures an IP firewall (IPAddressDeny=any), but the local system does not 
support BPF/cgroup based firewalling.
[4.027671] systemd[1]: Proceeding WITHOUT firewalling in effect! (This 
warning is only shown for the first loaded unit using IP firewalling.)
[4.059766] systemd[1]: System is tainted: local-hwclock:var-run-bad
[4.060039] systemd[1]: Created slice User and Session Slice.
[4.060133] systemd[1]: Created slice System Slice.
[4.060212] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[4.060242] systemd[1]: Listening on Syslog Socket.
[4.107197] systemd-journald[251]: Received request to flush runtime journal 
from PID 1
[427045.160058] systemd: 43 output lines suppressed due to ratelimiting
[427045.167709] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid)
[427045.168054] systemd[1]: Detected architecture x86-64.
[427045.210868] systemd[1]: File /lib/systemd/system/systemd-logind.service:37 
configures an IP firewall (IPAddressDeny=any), but the local system does not 
support BPF/cgroup based firewalling.
[427045.210870] systemd[1]: Proceeding WITHOUT firewalling in effect! (This 
warning is only shown for the first loaded unit using IP firewalling.)
[427045.228374] systemd[1]: Failed to connect to system bus: No such file or 
directory
[427045.228377] systemd[1]: Failed to initialize D-Bus connection: No such file 
or directory


dina@Dina:~$ dpkg -l '*systemd*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture   
Description
+++-===-==-==-===

Bug#541538: pulseaudio: disable flat volumes

[Boris Pek]

control: severity 541538 grave
justification: (physically) harms users


Hi Roland,

> I came here because I was just playing [1] on headphones, and Firefox
> seemed to think that it would be a good idea to set the master volume to
> 100%. My ears are still ringing.

You are not the only one who has faced with such unpleasant experience.

> At least now I know what to do.
> The fix of changing "flat-volumes = yes" to "flat-volumes = no" in
> /etc/pulse/daemon.conf seems to be fairly easy to implement,

Yes, the fix for a problem is very easy and it could be found in Google
very quickly. Probably, this is the main reason why it is considered
as not very important.

Personally I added this fix to my installation script very long time ago.
This script I use for installation of Debian for my relatives, friends and
acquaintances. Also I always warn about this bug new Debian users in XMPP
group chats and at forums, where I am registered.

>From my point of view this bug is significantly harming to image of Debian
amongst users of desktop systems.

I have asked users of other GNU/Linux distributions what default value is
used in their system and after the check all of them replied that
"flat-volumes" is set to "no". Here is the list of tested distributions:
Ubuntu (including Kubuntu and other builds)
Linux Mint (Linux Mint Debian Edition was not tested though)
Arch Linux (including Manjaro Linux)
Alt Linux
Fedora

Especially funny that this option is set to "no" by default even in Fedora,
the distro which is used by the main pulseaudio developers as far as I know.

> considering
> the fact that this bug is blocking a great number of other bugs, and no
> one here apparently has to say any word against it in the comments. Is
> there something else blocking it?

As far as I see the real problem is that maintainers of the package do not
consider this problem as bug in pulseaudio but as bug in all third-party
applications.

Dear pulseaudio maintainers, please change the default value of
"flat-volumes" to "no". It is not possible to fix all other applications
which cause to problems on user side.

Best regards,
Boris

Bug#879811: psi-translations: update to version 1.3

[Boris Pek]

Hi,

>>  On Thu, Oct 26, 2017 at 11:59:57AM +0300, Boris Pek wrote:
>>>   Please update package src:psi-translations to version 1.3 and keep it in 
>>> sync
>>>   with src:psi package.
>>
>>  Definitely a good idea, yes!
>>
>>  Unfortunately, I currently don't have much spare time, so it may take
>>  some time.
>>
>>>   Localization files:
>>>   https://github.com/psi-im/psi-l10n
>>>
>>>   Example of packaging rules:
>>>   https://github.com/tehnick/psi-plus-l10n-debian
>>
>>  Thanks for the pointers, those will be very useful for updating the
>>  package.
>
> It looks that you do not have enough free time to maintain this package.
>
> How about maintaining of src:psi and src:psi-translations packages under
> umbrella of Debian XMPP Maintainers team [1] using git repos [2] at Salsa [3]?
>
> In this case I would prepare a team upload for updating of 
> src:psi-translations.
>
> [1] https://wiki.debian.org/Teams/pkg-xmpp
> [2] https://salsa.debian.org/xmpp-team
> [3] https://wiki.debian.org/Salsa/Doc

Any comments regarding to moving packages to Debian XMPP Maintainers team?

Best regards,
Boris

Bug#885797: [Pkg-matrix-maintainers] Bug#885797: revolt: please build-depend on libglib2.0-dev-bin

[Boris Pek]

Hi,

>> I don't think we have any
>> uploads for Revolt planned in the near future, so we can just let the
>> NMU go through.
>
> Thanks, I've rescheduled it to 0-day so this bug can go away sooner.
>
> The collab-maint repository declared in the source package doesn't seem
> to exist, so I haven't pushed my changes. Please apply the change to
> whatever VCS you use for the next upload.

Imported using `gbp import-dscs`:
https://salsa.debian.org/matrix-team/revolt/commits/master

Thanks.

-- 
Boris

Bug#879811: psi-translations: update to version 1.3

[Boris Pek]

Hi Jan,

> On Thu, Oct 26, 2017 at 11:59:57AM +0300, Boris Pek wrote:
>>  Please update package src:psi-translations to version 1.3 and keep it in 
>> sync
>>  with src:psi package.
>
> Definitely a good idea, yes!
>
> Unfortunately, I currently don't have much spare time, so it may take
> some time.
>
>>  Localization files:
>>  https://github.com/psi-im/psi-l10n
>>
>>  Example of packaging rules:
>>  https://github.com/tehnick/psi-plus-l10n-debian
>
> Thanks for the pointers, those will be very useful for updating the
> package.

It looks that you do not have enough free time to maintain this package.

How about maintaining of src:psi and src:psi-translations packages under
umbrella of Debian XMPP Maintainers team [1] using git repos [2] at Salsa [3]?

In this case I would prepare a team upload for updating of src:psi-translations.

[1] https://wiki.debian.org/Teams/pkg-xmpp
[2] https://salsa.debian.org/xmpp-team
[3] https://wiki.debian.org/Salsa/Doc

Best regards,
Boris

Bug#881966: nheko: program lacks icon in a system tray

[Boris Pek]

Package: nheko
Version: 0.0+git20170715.3c1f969-2
Severity: normal


Hi,

Program lacks icon in system tray when it is launched in KDE Plasma 5.x.
Only image is missed (or it is completely transparent), mouse clicks work fine.

Best regards,
Boris

Bug#881965: nheko: manual page is missed

[Boris Pek]

Package: nheko
Version: 0.0+git20170715.3c1f969-2
Severity: important
Justification: Policy 12.1


Hi,

Please add manual page for a program.

Best regards,
Boris

Bug#881963: revolt: manual page is missed

[Boris Pek]

Package: revolt
Version: 0.0+git20170627.3f5112b-1
Severity: important
Justification: Policy 12.1


Hi,

Please add manual page for a program.

Best regards,
Boris

Bug#881962: revolt: missed dependency from gir1.2-webkit2-4.0

[Boris Pek]

Package: revolt
Version: 0.0+git20170627.3f5112b-1
Severity: serious
Justification: Policy 3.5


Hi,

$ revolt  
Traceback (most recent call last): 
  File "/usr/bin/revolt", line 23, in  
from revolt import main 
  File "/usr/share/revolt/py/revolt/__init__.py", line 12, in  
GLib="2.0")) 
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 141, in 
require_versions 
require_version(module_name, module_version) 
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 118, in 
require_version 
raise ValueError('Namespace %s not available' % namespace) 
ValueError: Namespace WebKit2 not available

But after:
$ sudo apt-get install gir1.2-webkit2-4.0
all work as expected.

Best regards,
Boris


--- System information. ---
Architecture: 
Kernel:   Linux 4.13.0-1-amd64

Debian Release: buster/sid

--- Package information. ---
Depends (Version) | Installed
=-+-==
python3:any (>= 3.3.2-2~) | 
python3-gi| 3.24.1-6
libwebkit2gtk-4.0-37  | 2.18.3-1
dconf-gsettings-backend   | 0.26.1-1
 OR gsettings-backend | 


Package's Recommends field is empty.

Package's Suggests field is empty.

Bug#879713: konsole: Konsole freezes for a minute when I press backspace in empty command line

[Boris Pek]

Hi,

> Since a few days (or weeks?) I experience a strange behavior in konsole.
> When editing a command line, if I press backspace too many times finally
> trying to delete a character from an empty line, konsole freezes for ca.
> one minute. The CPU load is almost 0%, other programs in the X windows
> session work corectly. Even other konsole windows work correctly.
>
> The interesting thing is that the problem occurs exactly ones in each
> konsole window. It doesn't matter how many tabs I open. If I press backspace
> in the empty command line for the first time in one of open tabs, the whole
> window freezes. After it recovers, I can safely press backspace in all tabs
> without any problems.

Try to use [Tab] key from keyboard to complete the command or path when you
are typing something. You will get exactly the same freeze.

> In fact it looks like konsole gets blocked trying to connect to certain not
> running network service.
>
> I don't know it it matters, but I use konsole in the MATE session.

Yes, this is important. When program is launched directly in KDE session this
bug is not reproducible.

But this bug could but easily reproduced even in KDE session. If there are two
users in your system (user1 and user2) and you have logged in as user1 then
launch:

$ ssh -C -X -p 22 user2@localhost konsole

and you will be able to see a number of issues in launched KDE application.
One of these issues is a bug described above.

Best regards,
Boris

Bug#880306: psi-plus-l10n: FTBFS: mv: cannot stat 'translations/*.qm': No such file or directory

[Boris Pek]

Hi,

> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part (hopefully):
>>  ...
>>  lrelease: could not exec '/usr/lib/x86_64-linux-gnu/qt5/bin/lrelease' since 
>> it links to lrelease itself. Check your installation.
>>  ...

Really!?

-- 
Boris

Bug#879811: psi-translations: update to version 1.3

[Boris Pek]

Hi Jan,

> BTW, I wonder if it would be possible to use a common l10n package for
> both psi ans psi+. The differences seem to be rather small.

I do not think that this is a good idea.

Yes, now the difference between Psi+ and Psi sources is not such huge as in the
past. But they have been developing with a different speed [1]: Psi has been
developing using classic releases model, but for Psi+ the rolling release
development model is used.

And even if there are very few new text strings are came into Psi+, the old
text strings might be changed. (As it was in recent releases.)

More over, stable releases of Psi are prepared in a separate git branches and
they include only part of changes from master branch, where patches from Psi+
are come.

Because of this Psi will have much more untranslated strings if it will use
Psi+ translations directly. And that is why I keep support two independent git
repos with translations for Psi [2] and Psi+ [3].

[1] https://en.wikipedia.org/wiki/Psi_(instant_messaging_client)#History
[2] https://github.com/psi-im/psi-l10n
[3] https://github.com/psi-plus/psi-plus-l10n

Best regards,
Boris

Bug#879811: psi-translations: update to version 1.3

[Boris Pek]

Source: psi-translations
Version: 1.11
Severity: important


Hi,

Please update package src:psi-translations to version 1.3 and keep it in sync
with src:psi package.

Localization files:
https://github.com/psi-im/psi-l10n

Example of packaging rules:
https://github.com/tehnick/psi-plus-l10n-debian

Best regards,
Boris

Bug#874872: [eiskaltdcpp] Future Qt4 removal from Buster

[Boris Pek]

Hi,

> As you might know we the Qt/KDE team are preparing to remove Qt4
> as [announced] in:
>
> [announced] 
> 

Just for note. Qt 5.x is well supported in a next stable release of
EiskaltDC++ (2.4.0) which is going to be released soon. I will update the
package once this happens. But updated package should go through NEW queue
due to changing of SOVERSION of internal library. So I cannot predict the
time when package will reach archive.

Best regards,
Boris

Bug#858436: eiskaltdcpp: Please migrate to openssl1.1 in buster

[Boris Pek]

Hi,

> this is a remainder about the openssl transition [0]. We really want to
> remove libssl1.0-dev from unstable for Buster. I will raise the severity
> of this bug to serious in a month. Please react before that happens.
>
> [0] https://bugs.debian.org/871056#55

Just for note. OpenSSL >= 1.1 will be supported in a next stable release of
EiskaltDC++ (2.4.0) which is going to be released soon. I will update the
package once this happens. But updated package should go through NEW queue
due to changing of SOVERSION of internal library. So I cannot predict the
time when package will reach archive.

Best regards,
Boris

Bug#877627: stretch-pu: package kde-gtk-config/5.8.6-1+deb9u1

[Boris Pek]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-CC: debian-qt-...@lists.debian.org


Dear release team,

I would like to push a fix for src:kde-gtk-config package in stable. Without
this fix package kde-config-gtk-style lacks one very convenient feature
(previewing GTK+ 2.x and GTK+ 3.x themes before applying them) and package
kde-config-gtk-style-preview is absolutely useless (because binaries from it
cannot be used).

Proposed changes have been applied in package in unstable since 04 Aug 2017
(kde-gtk-config/4:5.10.4-1) and all works fine.

Please consider accepting this as a stretch-pu.

Thanks,
Boris
diff -Nru kde-gtk-config-5.8.6/debian/changelog kde-gtk-config-5.8.6/debian/changelog
--- kde-gtk-config-5.8.6/debian/changelog	2017-03-14 17:23:29.0 +0300
+++ kde-gtk-config-5.8.6/debian/changelog	2017-10-03 17:31:46.0 +0300
@@ -1,3 +1,15 @@
+kde-gtk-config (4:5.8.6-1+deb9u1) stable; urgency=medium
+
+  * Update debian/rules:
+set DATA_INSTALL_DIR variable in configuration options: it is required
+for correct search of preview.ui file in gtk*_preview programs.
+(These programs have not been working since version 4:5.1.95-0ubuntu1)
+  * Add patch fix-search-of-gtk-preview-executables.
+It is required for showing preview buttons in KDE-GTK-config UI.
+(These buttons have not been working since version 4:5.1.95-0ubuntu1)
+
+ -- Boris Pek <tehn...@debian.org>  Tue, 03 Oct 2017 17:31:46 +0300
+
 kde-gtk-config (4:5.8.6-1) unstable; urgency=medium
 
   * New upstream release (5.8.6)
diff -Nru kde-gtk-config-5.8.6/debian/patches/fix-search-of-gtk-preview-executables.patch kde-gtk-config-5.8.6/debian/patches/fix-search-of-gtk-preview-executables.patch
--- kde-gtk-config-5.8.6/debian/patches/fix-search-of-gtk-preview-executables.patch	1970-01-01 03:00:00.0 +0300
+++ kde-gtk-config-5.8.6/debian/patches/fix-search-of-gtk-preview-executables.patch	2017-08-04 17:00:50.0 +0300
@@ -0,0 +1,43 @@
+Forwarded: no
+Description: Fix search of gtk*_preview executables
+ Due to Debian multiarch support gtk_preview and gtk3_preview executables are
+ installed into non-standard path (/usr/lib/*/libexec/) which is out of
+ search scope of QStandardPaths::findExecutable() function.
+ .
+ This patch is required for showing preview buttons in KDE-GTK-config UI.
+Author: Boris Pek <tehnic...@yandex.ru>
+Last-Update: 2017-08-04
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+--- a/CMakeLists.txt
 b/CMakeLists.txt
+@@ -26,6 +26,8 @@
+ 
+ # Set KI18n translation domain
+ add_definitions(-DTRANSLATION_DOMAIN=\"kde-gtk-config\")
++add_definitions(-DCMAKE_INSTALL_PREFIX=\"${CMAKE_INSTALL_PREFIX}\")
++add_definitions(-DLIBEXEC_INSTALL_DIR=\"${LIBEXEC_INSTALL_DIR}\")
+ 
+ set(kcm_SRCS
+  src/iconthemesmodel.cpp
+diff --git a/src/gtkconfigkcmodule.cpp b/src/gtkconfigkcmodule.cpp
+--- a/src/gtkconfigkcmodule.cpp
 b/src/gtkconfigkcmodule.cpp
+@@ -87,6 +87,17 @@
+ QString gtk2Preview = QStandardPaths::findExecutable("gtk_preview");
+ QString gtk3Preview = QStandardPaths::findExecutable("gtk3_preview");
+ 
++// KStandardDirs::findExe was replaced by QStandardPaths::findExecutable
++// in a wrong way. See for details:
++// https://community.kde.org/Frameworks/Porting_Notes/KStandardDirs
++static const QString searchPath = CMAKE_INSTALL_PREFIX "/" LIBEXEC_INSTALL_DIR;
++if(gtk2Preview.isEmpty()) {
++gtk2Preview = QStandardPaths::findExecutable("gtk_preview", QStringList() << searchPath);
++}
++if(gtk3Preview.isEmpty()) {
++gtk3Preview = QStandardPaths::findExecutable("gtk3_preview", QStringList() << searchPath);
++}
++
+ m_p2 = new KProcess(this);
+ m_p2->setEnv("GTK2_RC_FILES", m_tempGtk2Preview, true);
+ if(!gtk2Preview.isEmpty()) {
diff -Nru kde-gtk-config-5.8.6/debian/patches/series kde-gtk-config-5.8.6/debian/patches/series
--- kde-gtk-config-5.8.6/debian/patches/series	1970-01-01 03:00:00.0 +0300
+++ kde-gtk-config-5.8.6/debian/patches/series	2017-08-04 17:00:50.0 +0300
@@ -0,0 +1 @@
+fix-search-of-gtk-preview-executables.patch
diff -Nru kde-gtk-config-5.8.6/debian/rules kde-gtk-config-5.8.6/debian/rules
--- kde-gtk-config-5.8.6/debian/rules	2017-03-14 17:23:29.0 +0300
+++ kde-gtk-config-5.8.6/debian/rules	2017-10-03 17:29:35.0 +0300
@@ -2,6 +2,9 @@
 
 include /usr/share/pkg-kde-tools/qt-kde-team/3/debian-qt-kde.mk
 
+override_dh_auto_configure:
+	dh_auto_configure -- -DDATA_INSTALL_DIR="/usr/share/"
+
 override_dh_auto_test:
 	# Disable dh_auto_test at build time
 	:

Bug#877342: stretch-pu: package qtcurve/1.8.18+git20160320-3d8622c-3+deb9u1

[Boris Pek]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Dear release team,

I would like to push a fix for qtcurve bug #865765 (crash when using QtCurve
widget style with Breeze preset).

Debdiff looks big but in fact it is very simple: just s/memcmp/strncmp/

Please consider accepting this as a stretch-pu.

Thanks,
Boris
diff -Nru qtcurve-1.8.18+git20160320-3d8622c/debian/changelog qtcurve-1.8.18+git20160320-3d8622c/debian/changelog
--- qtcurve-1.8.18+git20160320-3d8622c/debian/changelog	2016-05-11 23:52:09.0 +0300
+++ qtcurve-1.8.18+git20160320-3d8622c/debian/changelog	2017-09-30 19:37:12.0 +0300
@@ -1,3 +1,11 @@
+qtcurve (1.8.18+git20160320-3d8622c-3+deb9u1) stable; urgency=medium
+
+  * Add patch replace-memcmp-with-strncmp. It fixes crash when using QtCurve
+widget style and Breeze preset. (Closes: #865765)
+[Thanks to Sergey Sharybin]
+
+ -- Boris Pek <tehn...@debian.org>  Sat, 30 Sep 2017 19:37:12 +0300
+
 qtcurve (1.8.18+git20160320-3d8622c-3) unstable; urgency=medium
 
   * Add workaround-for-kwin-x11-crashes.patch. (Closes: #823674)
diff -Nru qtcurve-1.8.18+git20160320-3d8622c/debian/patches/replace-memcmp-with-strncmp.patch qtcurve-1.8.18+git20160320-3d8622c/debian/patches/replace-memcmp-with-strncmp.patch
--- qtcurve-1.8.18+git20160320-3d8622c/debian/patches/replace-memcmp-with-strncmp.patch	1970-01-01 03:00:00.0 +0300
+++ qtcurve-1.8.18+git20160320-3d8622c/debian/patches/replace-memcmp-with-strncmp.patch	2017-09-07 18:52:54.0 +0300
@@ -0,0 +1,1337 @@
+Description: Replace memcmp with strncmp
+ Do not exceed string buffer length while parsing config file.
+Origin: upstream, https://cgit.kde.org/qtcurve.git/commit/?id=f164a4b69
+Bug: https://bugs.kde.org/show_bug.cgi?id=374046
+Bug-Debian: https://bugs.debian.org/865765
+Last-Update: 2017-08-03
+
+--- a/gtk2/common/config_file.cpp
 b/gtk2/common/config_file.cpp
+@@ -88,17 +88,17 @@
+ {
+ if(str && 0!=str[0])
+ {
+-if(0==memcmp(str, "dashes", 6))
++if(0==strncmp(str, "dashes", 6))
+ return LINE_DASHES;
+-if(0==memcmp(str, "none", 4))
++if(0==strncmp(str, "none", 4))
+ return LINE_NONE;
+-if(0==memcmp(str, "sunken", 6))
++if(0==strncmp(str, "sunken", 6))
+ return LINE_SUNKEN;
+-if(0==memcmp(str, "dots", 4))
++if(0==strncmp(str, "dots", 4))
+ return LINE_DOTS;
+-if(0==memcmp(str, "flat", 4))
++if(0==strncmp(str, "flat", 4))
+ return LINE_FLAT;
+-if(0==memcmp(str, "1dot", 5))
++if(0==strncmp(str, "1dot", 5))
+ return LINE_1DOT;
+ }
+ return def;
+@@ -108,12 +108,12 @@
+ {
+ if(str && 0!=str[0])
+ {
+-if(0==memcmp(str, "dark", 4))
+-return 0==memcmp([4], "-all", 4) ? TB_DARK_ALL : TB_DARK;
+-if(0==memcmp(str, "none", 4))
++if(0==strncmp(str, "dark", 4))
++return 0==strncmp([4], "-all", 4) ? TB_DARK_ALL : TB_DARK;
++if(0==strncmp(str, "none", 4))
+ return TB_NONE;
+-if(0==memcmp(str, "light", 5))
+-return 0==memcmp([5], "-all", 4) ? TB_LIGHT_ALL : TB_LIGHT;
++if(0==strncmp(str, "light", 5))
++return 0==strncmp([5], "-all", 4) ? TB_LIGHT_ALL : TB_LIGHT;
+ }
+ return def;
+ }
+@@ -122,15 +122,15 @@
+ {
+ if(str && 0!=str[0])
+ {
+-if(0==memcmp(str, "true", 4) || 0==memcmp(str, "colored", 7))
++if(0==strncmp(str, "true", 4) || 0==strncmp(str, "colored", 7))
+ return MO_COLORED;
+-if(0==memcmp(str, "thickcolored", 12))
++if(0==strncmp(str, "thickcolored", 12))
+ return MO_COLORED_THICK;
+-if(0==memcmp(str, "plastik", 7))
++if(0==strncmp(str, "plastik", 7))
+ return MO_PLASTIK;
+-if(0==memcmp(str, "glow", 4))
++if(0==strncmp(str, "glow", 4))
+ return MO_GLOW;
+-if(0==memcmp(str, "false", 4) || 0==memcmp(str, "none", 4))
++if(0==strncmp(str, "false", 4) || 0==strncmp(str, "none", 4))
+ return MO_NONE;
+ }
+ return def;
+@@ -140,40 +140,40 @@
+ {
+ if(str && 0!=str[0])
+ {
+-if(0==memcmp(str, "flat", 4))
++if(0==strncmp(str, "flat", 4))
+ return APPEARANCE_FLAT;
+-if(0==memcmp(str, "raised", 6))
++if(0==strncmp(str, "raised", 6))
+ return APPEARANCE_RAISED;
+-if(0==memcmp(str, "dullglass

Bug#875442: RM: elmer-doc/experimental -- ROM; useless without elmerfem

[Boris Pek]

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: debian-science-maintain...@lists.alioth.debian.org


Hi,

Please remove src:elmer-doc from Debian experimental. It is completely useless
without elmerfem package which has been removed recently [1].

[1] https://bugs.debian.org/875347

Best regards,
Boris

Bug#875441: RM: elmer-doc -- ROM; useless without elmerfem

[Boris Pek]

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: debian-science-maintain...@lists.alioth.debian.org


Hi,

Please remove src:elmer-doc from Debian unstable. It is completely useless
without elmerfem package which has been removed recently [1].

[1] https://bugs.debian.org/870922

Best regards,
Boris

Bug#874561: Considders environment http_proxy and/or https_proxy

[Boris Pek]

Hi,

> Apart from bug #874481, I found some more problems. The new version
> seems to read the environment $http_proxy and use it even if the
> connection is set up to use no proxy.
>
> That is suboptimal for many reasons. First the http_proxy does not
> define a socks proxy. Second it leads to strange problems that it tries
> to connect the http_proxy from a potential remote system (In my case I
> started using tsocks to mitigate bug #874481 and found some strange
> connection tries on the remote system to the proxy in $http_proxy).
>
> Unsetting that environments before starting psi does help (and the
> connection via tsocks work).

As far as I see this problem is not directly in Psi+:
boradmin@Tehnick:~/Hobby/Devel/Psi+/repositories/psi-plus-snapshots$ grep -ri 
http_proxy | wc -l
0
boradmin@Tehnick:~/Hobby/Devel/Psi+/repositories/psi-plus-snapshots$ grep -ri 
https_proxy | wc -l
0

But in QtBase:
boradmin@Tehnick:~/Hobby/Devel/Qt-opensource/qtbase$ git checkout v5.9.1
HEAD is now at 160533328c... Remove mention of reverted fix
boradmin@Tehnick:~/Hobby/Devel/Qt-opensource/qtbase$ grep -r http_proxy
src/network/kernel/qnetworkproxy.cpp:the "http_proxy" environment variable. 
This variable must be a URL
src/network/kernel/qnetworkproxy_generic.cpp: * Construct a proxy from the 
environment variables http_proxy and no_proxy.
src/network/kernel/qnetworkproxy_generic.cpp:proxy_env = 
qgetenv("http_proxy");
src/network/kernel/qnetworkproxy_generic.cpp:// Fallback to http_proxy is 
no protocol specific proxy was found
src/network/kernel/qnetworkproxy_generic.cpp:proxy_env = 
qgetenv("http_proxy");
tests/auto/network/kernel/qnetworkproxyfactory/tst_qnetworkproxyfactory.cpp:
QTest::newRow("no proxy") << QByteArray("http_proxy") << QByteArray() << 
QNetworkProxy::NoProxy
tests/auto/network/kernel/qnetworkproxyfactory/tst_qnetworkproxyfactory.cpp:
QTest::newRow("socks5") << QByteArray("http_proxy") << 
QByteArray("socks5://127.0.0.1:4242")
tests/auto/network/kernel/qnetworkproxyfactory/tst_qnetworkproxyfactory.cpp:
QTest::newRow("http") << QByteArray("http_proxy") << 
QByteArray("http://example.com:666;)
boradmin@Tehnick:~/Hobby/Devel/Qt-opensource/qtbase$ grep -r https_proxy
src/network/kernel/qnetworkproxy_generic.cpp:proxy_env = 
qgetenv("https_proxy");

More dipper investigation is required.

Best regards,
Boris

Bug#874481: Proxy settings or setting a different IP doesn't work anymore

[Boris Pek]

control: forwarded 874481 https://github.com/psi-im/psi/issues/311

Hi,

This bug is reproducible and I have found the problematic commit.
Let's hope that Psi+ developers will fix it soon.

Best regards,
Boris

Bug#869562: transifex-client: `tx push ...` does not work anymore

[Boris Pek]

Package: transifex-client
Version: 0.12.2-1
Severity: important

X-Debbugs-CC: h...@eds.org


Hi,

IIRC since the beginning of July current version of transifex-client from Debian
repos cannot push files to transifex.com. Here is typical output:
$ tx push -s -t --skip
Pushing translations for resource psi-plus.full:
Pushing source file (translations/psi-plus.full/psi_en.ts)
HTTPSConnectionPool(host=u'www.transifex.com', port=443): Max retries exceeded 
with url: /api/2/project/psi-plus/resource/full/content/ (Caused by 
ProtocolError('Connection aborted.', BadStatusLine("''",)))

I have tried transifex-client version 0.12.4-1 from [0] and it works fine.
Please upload updated package into Debian repository.

[0] https://anonscm.debian.org/cgit/python-modules/packages/transifex-client.git

Best regards,
Boris

Bug#865765: [qtcurve] Crash when using QtCurve widget style and Breeze preset

[Boris Pek]

control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=374046

> I don't think there is anything to be discussed actually.
>
> After closer studying of the latest upstream sources of QtCurve it
> appears same exact bug was submitted a while back to them. Same exact
> patch was committed to the upstream, see [1]. And here is an original
> bug report [2].
>
> So guess it's either matter downstreaming the fix or waiting for 1.9.0
> to be out (it is at RC1 state atm).
>
> [1] https://cgit.kde.org/qtcurve.git/commit/?id=f164a4b69
> [2] https://bugs.kde.org/show_bug.cgi?id=374046

I had not time to check last commits in upstream VCS, so I was not aware of 
this.
Thanks for the links, I'll update the package soon.

Best regards,
Boris

Bug#865765: [qtcurve] Crash when using QtCurve widget style and Breeze preset

[Boris Pek]

Hi Sergey,

> Patch had some malformed header (was mixing information from previous
> maintainer patch and residue of some older description). Here is an
> updated patch with hopefully all headers filled correct.
>
> Hopefully this one will work fine :)

Please discuss this patch with QtCurve developers in upstream BTS.

Best regards,
Boris

Bug#867576: [Pkg-kde-extras] Bug#867576: qtcurve: FTBFS with Qt 5.9: static assertion failed: QFlags is only usable on enumeration types.

[Boris Pek]

Hi Dmitry,

> On Fri, Jul 07, 2017 at 05:18:41PM +0300, Dmitry Shachnev wrote:
>>  qtcurve fails to build with Qt 5.9 (available in experimental):
>>
>>  [...]
>>
>>  This upstream commit fixes this failure:
>>  https://cgit.kde.org/qtcurve.git/commit/?id=7ddd3782ea5635cc
>
> I have now committed this fix to the packaging Git [1], and I am going
> to do a team upload. Do you have any objections against that?
>
> [1]: 
> https://anonscm.debian.org/git/pkg-kde/kde-extras/qtcurve.git/commit/?id=784e65e9dc406d7c

Thank  you for the patch! I'll look on this package today and will upload it.

Best regards,
Boris

Bug#837523: New maintainer

[Boris Pek]

Hi there,

I am going to switch package to new upstream [1] and to update it to latest
release 2.4.1 [2].

Hope to find time in this month.

[1] https://github.com/FastCGI-Archives
[2] https://github.com/FastCGI-Archives/fcgi2/tags

-- 
Boris

Bug#867174: reportbug-ng: incorrect work with kmail

[Boris Pek]

Package: reportbug-ng
Version: 2.1
Severity: normal

Hi,

Reportbug NG sends URL-encoded text to KMail (see attachment).

Best regards,
Boris

Bug#867171: qgit: keyboard shortcut Ctrl+C calls unexpected action

[Boris Pek]

Package: qgit
Version: 2.7-1
Severity: normal

Hi,

In current version of QGit keyboard shortcut Ctrl+C is used for calling of
"Checkout..." action. Such behavior is extremely inconvenient for users who got
used to use this keyboard shortcut for copy-and-paste purpose.

Please change or remove keyboard shortcut for "Checkout..." action in debian
package and report bug to upstream BTS.

I may prepare patch if necessary.

Best regards,
Boris

Bug#861619: q4wine: Version bump request: q4wine 1.3.4

[Boris Pek]

> Is it something to do with compile-time warnings you send me earlier?

No. This is about localization files and doxygen documentation.

Best wishes,
Boris

Bug#861619: q4wine: Version bump request: q4wine 1.3.4

[Boris Pek]

Hi,

> Please bump version to 1.3.4, this version fixes an issue where program icons 
> cannot be seen with qt 5.7

Official tarball for this version of program at SF has some problems. Upstream
was notified about this and once q4wine 1.3.5 with fixes will be released the
package in Debian will be updated.

Also have in mind that q4wine 1.3.5 will not land into Debian stretch repo,
it will be available only in stretch-backports.

Best wishes,
Boris

Bug#622905: spawn-fcgi: No init.d script provided

[Boris Pek]

Hi,

> I vote for closing this "feature request" :)

+1 for closing this issue.

> What would be great would be to provide an example of systemd user
> service file. (and distribute examples using debian/examples).

You may look at simple example here:
https://github.com/tehnick/bosixnet/blob/master/src/bosixnet-webui/bosixnet-webui.service
https://github.com/tehnick/bosixnet/blob/master/src/bosixnet-webui/webui_launcher

Best regards,
Boris

Bug#836429: q4wine: Please clarify upstream status and homepage

[Boris Pek]

Hi,

> I (co-maintainer of Wine) just saw on
> https://wiki.winehq.org/Third_Party_Applications
> that q4wine is listed as an obsolete application. So I wanted to see why
> q4wine is still in Debian ...
>
> However after a bit of investigation it looks to me as if it is actively
> developed, and still works and is useful with both wine and
> wine-development. Can you confirm this?

Yes, it was quite long period of stagnation in this project due to main
developer frustration about political situation in his country. At that time
there were no new stable releases and project's website was broken [1][2][3].
But there were rare commits from other developers and debian package was
always in a good shape. So program was always in working state.

[1] http://web.archive.org/web/20151106085751/http://q4wine.brezblock.org.ua/
[2] https://bugs.debian.org/761968
[3] https://bugs.launchpad.net/ubuntu/+source/q4wine/+bug/1332725

Now main developer came back to active development of q4wine project and
almost all is fine.

> Would it be correct to change this classification on winehq.org?

Yes, sure.

> [Actual bug report:]
>
> While investigating I noticed that the homepage field in d/control seems
> to be outdated (reason stated in #761968):
>
> Homepage:
> https://web.archive.org/web/20131204020055/http://q4wine.brezblock.org.ua/

I may update this link to more recent version (for example [4]), but I do not
want to use direct link to website [5] because access to it is limited [6] from
Russian Federation (and from few other world regions) due to main developer's
political opinion. Also I am not sure that he will never change this website
into state [1] again.

[4] http://web.archive.org/web/20160417203147/http://q4wine.brezblock.org.ua/
[5] http://q4wine.brezblock.org.ua/
[6] http://www.susepaste.org/view/raw/77888454

> d/watch has:
> http://sf.net/q4wine/q4wine-(.+)\.tar\.bz2 \
> -> seems valid

Yes, tarballs for stable releases of q4wine are distributed via SourceForge.

> Checking the web I see:
>
> http://q4wine.brezblock.org.ua/
> -> seems valid for q4wine itself (again), and points to these 2 resources:

Look above.

> https://github.com/brezerk/q4wine/tree/master
> https://sourceforge.net/projects/q4wine/
> -> both seem to be valid
>
> So I think one of these 3 sites should be set as Homepage in d/control.
> I don't know if any other change that was made because of #761968 needs
> reconsideration.

Website [5] contains the most of information about project and it looks as
the most useful entry point for usual users unlike links to GitHub and
SourceForge which are more useful for maintainers, translators, etc..

Personally I do not see the necessity to change Homepage link in this package.
Other opinions are welcome.

Best regards,
Boris

Bug#830129: RM: plasma-widget-cwp -- ROM; Not compatibile with KDE Plasma 5

[Boris Pek]

Package: ftp.debian.org
Severity: normal

Hi FTP masters,

Developer has explicitly stated that he does not have time and interest to port
this plasmoid from KDE 4 to KDE Plasma 5.

Please remove plasma-widget-cwp package from unstable.

Thanks

Bug#827615: RM: xembed-sni-proxy -- ROM; Moved into plasma-workspace

[Boris Pek]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: tehn...@debian.org, pkg-kde-ext...@lists.alioth.debian.org

Hi FTP masters,

xembedsniproxy module was included into plasma-workspace since 5.5.0 release
and plasma-workspace/4:5.6.4-2 is already in testing, so a separate package
is not required anymore.

Please remove xembed-sni-proxy package from unstable.

Thanks

Bug#823186: chromium: crashes on many websites

[Boris Pek]

Hi,

> A backtrace that includes chromium's debugging symbols would be more
> helpful than the "me too" messages.

How about stack traces from a first message? Are they useless?

If you want full backtrace from gdb then describe how to get if, because usual
approach (gdb  --> run --> segfault --> bt full) will not work with
chromium as far as I understand.

Or you may easily install 32-bit chromium in your 64-bit system and reproduce
segfaults by yourself.

> The biggest difference from deb8u1 is embedded instead of system
> ffmpeg. It would be useful to know whether building with the embedded
> library fixes it (just unapply ffmpeg.patch).

I have built chromium/51.0.2704.79-1.1 without this patch and all works fine.
So the root of problem is exactly here.

But please do not ask to test any patches, because in my system this package
was building during 8.5 hours and all this time my laptop was too hot and I was
worrying it will be overheated.

Best wishes,
Boris

Bug#823186: chromium: crashes on many websites

[Boris Pek]

Hi,

I have tested Chromium 50.0.2661.94-1 on few other PCs and laptop and there are
such results:
* it works absolutely fine on PC and laptop with amd64 Debian Sid systems
* it crashes at tested web sites on PC with i686 Debian Sid system
  (as well as on my laptop with i686 Debian Sid system)

It looks that something is broken on 32-bit systems. Probably it is related with
discontinuing of support of Google Chrome for 32-bit Linux-based systems...

Best regards,
Boris

Bug#823186: chromium: crashes on many websites

[Boris Pek]

control: reopen 823186 =
control: notfixed 823186 50.0.2661.75-2
control: severity 823186 important


Hi,

>>  Chromium become completely unusable at many websites since version
>>  50.0.2661.75-1. See screenshot and stack trace examples in attachments.
>>  And this is not duplicate of bug #821154, because watching videos at
>>  youtube.com have been fixed in 50.0.2661.75-2 and still works, but other
>>  websites -- do not.
>>
>>  After updating from chromium 49.0.2623.108-1 some packages are no longer
>>  required:
>> libavcodec-ffmpeg56 (7:2.8.6-1+b2)
>> libavformat-ffmpeg56 (7:2.8.6-1+b2)
>> libavutil-ffmpeg54 (7:2.8.6-1+b2)
>> libswresample-ffmpeg1 (7:2.8.6-1+b2)
>>
>>  Probably chromium was built incorrectly it lacks some mandatory features.
>
> This issue was fixed in 50.0.2661.75-2.

Please read bug reports carefully before closing them.

In 50.0.2661.75-2 you have fixed only HTML5 videos on websites like youtube.com.

But problem from this bug report is not fixed nor in 50.0.2661.75-2, nor in
50.0.2661.94-1. It 100% reproducible. For example, open URL [1] and chromium tab
will crash immediately. Another crash you may see if you click on any play
button at [2]. And there are more affected websites. In my case the most
annoying problem is that I can't access to my email correspondence via Web UI,
as you may see at screenshot in attachments.

I have tested chromium with and without extensions.

[1] https://www.chess.com/echess/game?id=131722832
[2] https://music.yandex.ru/artist/233138


Next:

$ apt-cache show chromium
Package: chromium
...
Version: 50.0.2661.94-1
...
Architecture: i386
...
Depends: libasound2 (>= 1.0.16), libatk1.0-0 (>= 1.12.4),
 libavcodec57 (>= 7:3.0) | libavcodec-extra57 (>= 7:3.0),
 libavformat57 (>= 7:3.0), libavutil55 (>= 7:3.0), libc6 (>= 2.15),
 libcairo2 (>= 1.6.0), libcups2 (>= 1.4.0), libdbus-1-3 (>= 1.9.14),
 libexpat1 (>= 2.0.1), libfontconfig1 (>= 2.11), libfreetype6 (>= 2.4.2),
 libgcc1 (>= 1:4.2), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.41.1),
 libgnome-keyring0 (>= 3.2.2-2~), libgtk2.0-0 (>= 2.24.0),
 libjpeg62-turbo (>= 1.3.1), libnspr4 (>= 2:4.9-2~) | libnspr4-0d (>= 1.8.0.10),
 libnss3 (>= 2:3.13.4-2~) | libnss3-1d (>= 3.12.4), libpango-1.0-0 (>= 1.14.0),
 libpangocairo-1.0-0 (>= 1.14.0), libpci3 (>= 1:3.3.1-1),
 libspeechd2 (>= 0.7.1), libstdc++6 (>= 5.2), libx11-6 (>= 2:1.4.99.1),
 libxcomposite1 (>= 1:0.3-1), libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1),
 libxext6, libxfixes3, libxi6 (>= 2:1.2.99.4), libxml2 (>= 2.7.4),
 libxrandr2 (>= 2:1.2.99.2), libxrender1, libxslt1.1 (>= 1.1.25), libxss1,
 libxtst6, x11-utils, xdg-utils
...

I don't see anything related to libswresample. It may be related to the problem
or not related. Just a note which may be useful.


My system is up to date Debian Sid with i686-pae kernel.

Please ask if you need more info or any tests, but do not just close bug report.

Best regards,
Boris

Bug#784510: [psi-plus] Qt4's WebKit removal

[Boris Pek]

Hi,

> As we intend to go further with this removal we are bumping it's severity.
> If you need help please do not hesitate in replying to the bug, I am 
> subscribed to it.

Just for info: new versions of Psi+ are already ported to Qt5. Once Qt5 build
will be considered as stable enough by developers I'll use it for packaging.
Most likely it will be done in this or next month.

Best regards,
Boris

Bug#785891: psimedia: Please update to GStreamer 1.x

[Boris Pek]

Hi Moritz,

> what's the status, is there pending work to fix this upstream? The
> list of remaining gstreamer 0.10 is now becoming really short, so
> at one point psimedia will have to be removed along if it doesn't
> get fixed.

Unfortunately there is no any progress in porting psimedia to gstreamer 1.x in
upstream. If nothing changes I'll do it myself. But I am not sure when I will
find time for this.

Best regards,
Boris

Bug#812319: wine: FTBFS on amd64 and arm64

[Boris Pek]

Source: wine
Version: 1.8-5
Severity: serious
Justification: fails to build from source


Dear Maintainer,

wine/1.8-5 fails to build on amd64 and arm64:
https://buildd.debian.org/status/fetch.php?pkg=wine=amd64=1.8-5=1453164865
https://buildd.debian.org/status/fetch.php?pkg=wine=arm64=1.8-5=1453168393

wine/1.8-4 is successfully built on them. Unfortunately, you forgot to push
recent commits into git repo, so I could not find the problematic changes
immediately. Maybe I'll look deeply later.

Best regards,
Boris

Bug#806500: quassel-client: Client configuration is world readable and contains password in plain text

[Boris Pek]

Hi,

> As I was trying to setup CertFP I had a look at
> ~/.config/quassel-irc.org and noticed the following:
> -rw-r--r-- 1 diederik diederik 8101 nov 28 03:01 quasselclient.conf
>
> Looking into that file I could easily see my password and that combined
> with the security settings of that file did not make me happy.

This is a wrong assumption, just look at directory access permissions:

$ LC_ALL=C ls -alp ~/.config/ | grep '\./'
drwx--  96 user user   4096 Nov 28 23:44 ./
drwx-- 192 user user  12288 Nov 28 22:39 ../

Best wishes,
Boris

Bug#806500: quassel-client: Client configuration is world readable and contains password in plain text

[Boris Pek]

>>  This is a wrong assumption, just look at directory access permissions:
>>
>>  $ LC_ALL=C ls -alp ~/.config/ | grep '\./'
>>  drwx-- 96 user user 4096 Nov 28 23:44 ./
>>  drwx-- 192 user user 12288 Nov 28 22:39 ../
>
> Mine are not the same:
>
> diederik@bagend:~$ LC_ALL=C ls -alp ~/.config/ | grep '\./'
> drwxr-xr-x 45 diederik diederik 4096 Nov 28 19:29 ./
> drwxr-x--- 68 diederik diederik 12288 Nov 28 17:59 ../
> diederik@bagend:~$ ls -ld ~/.config/
> drwxr-xr-x 45 diederik diederik 4096 nov 28 19:29 /home/diederik/.config/
> diederik@bagend:~$ ls -ld ~/.config/quassel-irc.org/
> drwxr-xr-x 2 diederik diederik 4096 nov 28 11:10 
> /home/diederik/.config/quassel-irc.org/

This should be enough I think:
> drwxr-x--- 68 diederik diederik 12288 Nov 28 17:59 ../

Try something like this:
$ LC_ALL=C su another-user -c 'ls -alp /home/diederik/.config'
Password: 
ls: cannot access /home/diederik/.config: Permission denied

Best wishes,
Boris

Bug#802200: [plasma-systray-legacy] Minor Icon Problems

[Boris Pek]

Hi,

Could you check if your bugs are still present in
plasma-systray-legacy/0~git20151104-ded1538-1 ?

Best regards,
Boris

Bug#777200: libcdaudio1 is not Multi-Arch compatible

[Boris Pek]

Hi,

I am not a maintainer of this package, I am just interested in QA...

> This bug is still present. Any progress on this?
> Does the proposed patch need to be modified?

Could you show actual debdiff? Provided tarball is inconvenient for
quick view of changes. Have you tested the package with you patch for
possible regressions?

Also IIRC gstreamer0.10* will be removed from Debian repos soon.
(Just for a note.)

Best regards,
Boris

Bug#800698: Kmail2 display garbled (after a while)

[Boris Pek]

Hi Tim,

> since I installed kde5 I have a kmail2 issue.
>
> After a while the kmail2 display window becomes drawn unreadable.
> See this screenshot:
> https://drive.google.com/open?id=0B_loju3MX2rTZlNOdDRxblVTWDg
>
> Stopping and starting kmail does not help.
> Stopping and starting kdm helps for a while (until it suddenly happens again).
>
> I can't see anything obvious in 'dmesg' or .xsession-errors. Well I see lot's
> of 'BadDrawable' messages, but these are not limited to kmail.
>
> I am on Debian SID with latest dist-upgrade, have the problem with kernel 4.1
> and 4.2 (didn't test any older kernels). Grafix is internal Intel i3 (Sandy
> Bridge).
>
> Any ideas how to work around that or how to pin the problem ?

$ ldd /usr/bin/kmail | grep QtGui
libQtGui.so.4 => /usr/lib/x86_64-linux-gnu/libQtGui.so.4 (0x7f984cbb)

kmail is currently built with old Qt4 based KDE libs. It looks that you have
faced with issue from #800698. Please try to launch kmail from terminal and
show the output.

Best regards,
Boris

Bug#800698: libqtgui4: GUI applications are unusable on amd64 systems

[Boris Pek]

Hi,

>>  control: retitle 800698 libqtgui4: GUI applications become unusable when
>>  shared memory is exhausted
>
> With this title I'm even more convinced that this is not a bug ;) Please read
> below.

This is only an assumption which is based on found bug reports in other 
projects.

>>  >> but hey, why Qt5 based and Gtk+
>>  >> based programs were working without any issues in the same conditions?
>>  >
>>  > I do have an idea. Where those java applications creating an icon in the
>>  > taskbar?
>>  >
>>  > The only change that *might* be causing the problem here is the addition
>>  > of a patch that allows the systray to use sni-qt.
>>
>>  At first look I do not see anything related to shared memory usage in patch
>>  [1].
>>
>>  [1]
>>  
>> http://anonscm.debian.org/cgit/pkg-kde/qt/qt4-x11.git/tree/debian/patches/plugin_system_for_systemtray.patch?h=debian/4.8.7%2bdfsg-3
>>  > Did any of the Java created a taskbar icon?
>>
>>  If you had in mind a notification area, then yes, the most complex of these
>>  Java based programs creates an icon in system tray. And this icon is
>>  blinking when some events inside program trigger it.
>
> The only source change between the versions you mentioned in the original bug
> report is that patch. And I know Qt4 is using (X-11-related?) shared memory to
> draw things because I remember having to fix some permissions issues in past
> releases (for Wheezy IIRC).
>
> I don't know why GTK doesn't fails, and I *guess* that Qt5 might be using some
> OpenGL-related stuff that might make things go without problems.

Yes, it looks that Qt4 uses X11 rendering by default. I have checked [1] and 
[2].
In the first case GUI rendering is broken and unusable and there are a lot of 
repeated X11 error messages in console [3]. But in the second case program looks
more or less fine (only font in the main menu and in context menus looks ugly
because of font hinting does not work here).

[1] okular --graphicssystem raster
[2] okular --graphicssystem opengl
[3] The beginning of log from stderr:
QNativeImage: Unable to attach to shared memory segment. 
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 56 (X_ChangeGC)
  Resource id:  0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
...

> Are you running sni-qt? If so maybe the bug is there, or at least related.

I have removed sni-qt package and after reboot bug is still present.

>>  The main question is what to do with Qt4 libraries?
>>
>>  Other Debian users may face to this bug because package default-jdk depends
>>  from openjdk-7-jdk in Debian Stretch.
>
> Well, if the memory gets exhausted is no wonder that Qt4 fails. Now I hardly
> doubt that this is a bug in Qt4 due to the amount of testing the current
> version has, after all it's just bug fixes from stable, and not many linux-
> related precisely. And the behavior started with just a patch for sni-qt.
>
> If you have sni-qt installed I would definitely take a look there first.

sni-qt does not cause to this bug. The problem is somewhere else.

Unfortunately, I do not have cowbuilder environment for amd64 now thus I cannot
rebuild qt4-x11 package without discussed patch for testing, but I have force
installed libqtgui4/4:4.8.7+dfsg-1 from Debian snapshots archive [4] (yes, only
this one package and nothing more) and after reboot I can reproduce the bug.
So the problem is definitely not in the plugin_system_for_systemtray.patch.

Probably an update in completely anoter package have lead to this bug.

[4] 
http://snapshot.debian.org/archive/debian/20150526T221958Z/pool/main/q/qt4-x11/libqtgui4_4.8.7%2Bdfsg-1_amd64.deb

> I'll leave the bug open tagged as moreinfo in case you want to reassign it,
> else I'll close it in a couple of weeks, as nothing shows this is really a Qt4
> bug.

I do not have any experience in Java and I do not have enough time and interest
for investigating the bug in openjdk-7 dipper. Also we can do nothing from Qt4
side. And there is a known workaround. So this bug report might be closed now.

Best regards,
Boris

Bug#801264: ITP: xembed-sni-proxy -- XEmbed SNI Proxy

[Boris Pek]

Package: wnpp
Severity: wishlist

* Package name: xembed-sni-proxy
  Upstream Contact: David Edmundson 
* URL: https://github.com/davidedmundson/xembed-sni-proxy
* License: LGPL-2.1+, GPL-2, GPL-3
  Programming Lang: C++
  Description: XEmbed SNI Proxy

This special proxy converts XEmbed system tray icons to SNI icons. It allows
one to use applications which supports only legacy system tray icons in modern
desktop environments (i.e KDE Plasma 5, GNOME Shell, etc.) which support only
StatusNotifierItem specification.

For more details see: http://blog.davidedmundson.co.uk/blog/xembed_back

Bug#800698: libqtgui4: GUI applications are unusable on amd64 systems

[Boris Pek]

control: retitle 800698 libqtgui4: GUI applications become unusable when shared 
memory is exhausted


Hi Lisandro,

>>  Today I had some a bit time for searching of possible root of this bug.
>>  And I have found similar bug report [1] for one of Qt4 based applications.
>>
>>  [1] https://github.com/git-cola/git-cola/issues/482
>>
>>  When I have killed all openjdk-7 applications, my problem was solved.
>>  Then I have replaced openjdk-7* packages to openjdk-8* packages and all
>>  is working fine during few hours.
>>
>>  It looks that problem is in openjdk-7,
>
> It might probably be.
>
>>  but hey, why Qt5 based and Gtk+
>>  based programs were working without any issues in the same conditions?
>
> I do have an idea. Where those java applications creating an icon in the
> taskbar?
>
> The only change that *might* be causing the problem here is the addition of a
> patch that allows the systray to use sni-qt.

At first look I do not see anything related to shared memory usage in patch [1].

[1] 
http://anonscm.debian.org/cgit/pkg-kde/qt/qt4-x11.git/tree/debian/patches/plugin_system_for_systemtray.patch?h=debian/4.8.7%2bdfsg-3

> Did any of the Java created a taskbar icon?

If you had in mind a notification area, then yes, the most complex of these
Java based programs creates an icon in system tray. And this icon is blinking
when some events inside program trigger it.

> The reason why openjdk-8 *might* be working is that they might be using the
> new protocol for the taskbar.

No, Java applications launched with openjdk-8 still use legacy system tray.
Also I have tested openjdk-6 and in this case all Qt4 based applications worked
fine too. So bug is present only when openjdk-7 is used for Java programs.
(Though I haven't tested openjdk-9 from experimental yet.)

The main question is what to do with Qt4 libraries?

Other Debian users may face to this bug because package default-jdk depends
from openjdk-7-jdk in Debian Stretch.

Best regards,
Boris

Bug#800698: libqtgui4: GUI applications are unusable on amd64 systems

[Boris Pek]

Hi,

Today I had some a bit time for searching of possible root of this bug.
And I have found similar bug report [1] for one of Qt4 based applications.

[1] https://github.com/git-cola/git-cola/issues/482

When I have killed all openjdk-7 applications, my problem was solved.
Then I have replaced openjdk-7* packages to openjdk-8* packages and all
is working fine during few hours.

It looks that problem is in openjdk-7, but hey, why Qt5 based and Gtk+
based programs were working without any issues in the same conditions?

I do not know what to do with this bug report further. Any ideas?

Best regards,
Boris

Bug#799142: sddm: fails to build architecture independent packages

[Boris Pek]

Source: sddm
Version: 0.12.0-3
Severity: serious

Dear maintainer,

Recently you have done source-only upload of sddm/0.12.0-3 package.
Unfortunately this package is not yet ready for building of architecture
independent packages separately[1], therefor sddm-theme-maui,
sddm-theme-circles, sddm-theme-elarun and sddm-theme-maldives packages
are currently unavailable in Debian unstable.

[1] 
https://buildd.debian.org/status/fetch.php?pkg=sddm=all=0.12.0-3=1442259701

Please fix this FTBFS or upload package in usual way.

You may test architecture independent builds using something like this:
dpkg-buildpackage -rfakeroot -A

Best regards,
Boris

Bug#799146: FTBFS on hurd

[Boris Pek]

Source: sddm
Version: 0.12.0-1
Severity: normal


Hi,

As we can see in logs[1] sddm/0.11.0 packages were built fine on hurd. But since
sddm/0.12.0-1 these builds are broken. Please report bug to upstream.

[1] https://buildd.debian.org/status/logs.php?pkg=sddm=hurd-i386

Best regards,
Boris

Bug#799147: FTBFS on kfreebsd

[Boris Pek]

Source: sddm
Version: 0.12.0-1
Severity: normal


Hi,

As we can see in logs[1][2] sddm/0.11.0 packages were built fine on kfreebsd.
But since sddm/0.12.0 these builds are broken. Please report bug to upstream.

While Debian GNU/kFreeBSD is not officially supported[3] the severity of this
issue is normal. But it would be nice to bring back the official support of
kfreebsd in the next stable release of Debian.

[1] https://buildd.debian.org/status/logs.php?pkg=sddm=kfreebsd-i386
[2] https://buildd.debian.org/status/logs.php?pkg=sddm=kfreebsd-amd64
[3] https://lists.debian.org/debian-devel-announce/2014/11/msg5.html

Best regards,
Boris

Bug#796179: tesseract-ocr: tesseract fails to generate output

[Boris Pek]

control: severity 796179 normal
control: tags 796179 = moreinfo unreproducible


Hi,

I have tested [1] tesseract/3.04.00-5 [2] on two Debian testing systems (amd64)
and on two Debian unstable systems (amd64 and i386) and I can not reproduce this
problem. All works as expected. Therefore I decrease the severity of this bug
and tag it as moreinfo and unreproducible. Maybe it should be closed at all.
But this is a maintainer decision.

Best regards,
Boris


[1] Only english and russian text were checked from yagf and from command line.
[2] List of tesseract packages:
$ LC_ALL=C dpkg -l '*tesseract*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion  Architecture Description
+++-===---===
ii  libtesseract3   3.04.00-5i386 Tesseract OCR 
library
ii  tesseract-ocr   3.04.00-5i386 Tesseract command 
line OCR tool
un  tesseract-ocr-data(no description 
available)
ii  tesseract-ocr-eng   3.04.00-1all  tesseract-ocr 
language files for English
ii  tesseract-ocr-equ   3.04.00-1all  tesseract-ocr 
language files for equations
ii  tesseract-ocr-osd   3.04.00-1all  tesseract-ocr 
language files for script and
ii  tesseract-ocr-rus   3.04.00-1all  tesseract-ocr 
language files for Russian
ii  tesseract-ocr-ukr   3.04.00-1all  tesseract-ocr 
language files for Ukranian

Bug#793869: Solvable by removing kde-style-qtcurve

[Boris Pek]

Hi,

 This is solvable by removing kde-style-qtcurve.

 Then libqtcurve-utils1 is not required as kde-style-qtcurve-qt5 requires
 libqtcurve-utils2.

 Maybe kde-style-qtcurve needs to be recompiled with libqtcurve-utils2 as well,
 or is it obsoleted by kde-style-qtcurve-qt5?

Please read changelog [1]. I believe you will find the answer in it.

[1] 
http://anonscm.debian.org/cgit/pkg-kde/kde-extras/qtcurve.git/tree/debian/changelog

Best regards,
Boris


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