Bug#952332: marked as pending in kxd

[Maximiliano Curia]

Control: tag -1 pending

Hello,

Bug #952332 in kxd reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/kxd/-/commit/78d1549172adb8bc65b7cdfbb810a5d8e82197f5


Set absolute path in d/rules closes: #952332


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952332

Bug#952332: kxd: diff for NMU version 0.14-1.1

[Maximiliano Curia]

On 2020-04-05 06:38, Håvard Flaget Aasen wrote:

Control: tags 952332 + patch
Control: tags 952332 + pending

Dear maintainer,

I've prepared an NMU for kxd (versioned as 0.14-1.1) and
uploaded it to mentors. Please feel free to tell me if I
should remove it.


Thanks, could you prepare a merge request against
https://salsa.debian.org/debian/kxd ?

Thanks,
--
Saludos /\/\ /\ >< `/


signature.asc
Description: OpenPGP digital signature

Bug#932872: [libkscreenlocker5] Doesn't lock automatically by timeout

[Maximiliano Curia]

Control: severity -1 normal
Control: tags -1 + unreproducible

On 2019-07-24 01:49, Alex Volkov wrote:

Package: libkscreenlocker5
Version: 5.14.5-1
Severity: grave


Doesn't lock automatically by timeout, which presents a security issue. 
Seems
to work in a newly created test user setup, and randomly works 
sometimes in my
user, but I have no idea what makes in work. Probably some app 
"inhibits" the

automatic timeout, but I have no idea how to check it with all that
"brilliant" dbus crap.  Ubuntu has https://wiki.ubuntu.com/
DebuggingScreenLocking, but it's for Gnome, not KDE.


Hi Alex,

I'm really sorry that kscreenlocker is not working right for you, sadly 
I'm not being able to reproduce this issue, and as far as I can see it 
works as expected. But, there are a couple of catches in this, for 
example Xserver won't allow a screen lockeer to work whenever a context 
menu window or a tooltip is being shown, this is a known problem in the 
X11 world [1] [2] [3] that's only solved by migrating to wayland.


From the side of the inhibitors, I'm not sure if there is an api you can 
call to obtain the current inhibitors, but you can always try to lock 
the screen by hand and see if the screen does in fact get locked or not. 
Some known inhibitors are: google-chrome in certain situations, slide 
programs in presentation mode, and most video players.


Hope this help you figuring out where is the problem you are seeing.

[1]: https://bugs.kde.org/show_bug.cgi?id=78871
[2]: 
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/49579
[3]: 
http://blog.martin-graesslin.com/blog/2015/01/why-screen-lockers-on-x11-cannot-be-secure/




--- System information. ---
Architecture:
Kernel:   Linux 4.19.37-bootes0-iommu-p-1000

Debian Release: 10.0
  991 stable  security.debian.org
  991 stable  ftp.fi.debian.org
  990 buster-backports ftp.debian.org
   99 stable  www.deb-multimedia.org
  500 stable  dl.google.com
  500 stable  deb.torproject.org


Happy hacking,
--
Saludos /\/\ /\ >< `/


signature.asc
Description: OpenPGP digital signature

Bug#939400: sddm: Auth: sddm-helper exited with 11

[Maximiliano Curia]

Control: severity -1 normal

¡Hola Konomi!

El 2019-09-05 a las 01:14 +1000, Konomi escribió:

Package: sddm
Version: 0.18.0-1
Severity: grave
Tags: upstream
Justification: renders package unusable



Quoting the upstream bug report:



"sddm-greeter needs execution rights at 
/var/lib/sddm/.cache/sddm-greeter/qmlcache/*.qmlc.
krunner needs execution at /home/user/.cache/krunner/qmlcache/*.qmlc. It breaks
when /var and /home partitions are mounted with noexec flag which is often used 
on
hardened setups or Trusted Path Execution available on hardened linux kernels.



As for now it could be fixed by disabling qml cache by setting 
QML_DISABLE_DISK_CACHE=1
environment variable. Is there a chance that qt will check permission rights 
first then
quietly disable qmlcache per app instead of crashing?



Alternatively it could create cachedir somewhere in /usr/lib/qt same as python3 
have
it's pycache dir."



Upstream bug report: https://bugreports.qt.io/browse/QTBUG-58508



The work around of adding QML_DISABLE_DISK_CACHE=1 to /etc/enviroment got sddm 
working
for me again. Without the work around sddm will start but show just a black 
screen, so
I've marked this bug as grave since it completely breaks the package.


I don't see any reference that a program needs to support a hardened setup in 
Debian, and this is clearly something not supported upstream, as such I'm 
degrading the severity of this issue.


Let's see what do the qt maintainers think about setting a different cache dir 
or patching qt to disable the disk cache if the cache won't be loadable.


Happy hacking,
--
"It's a well-known fact that computing devices such as the abacus were 
invented thousands of years ago. But it's not well known that the first use of 
common computer protocol occurred in the Old Testament. This, of course, was 
when Moses aborted the Egyptians' process with a control-sea."

-- Tom Galloway (recs.arts.comics, February 1992)
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#931483: konsole: Konsole will not launch from mate-panel or from KDE Application Launcher.

[Maximiliano Curia]

Control: severity -1 important
Control: tag -1 moreinfo unreproducible

¡Hola David!

El 2019-07-05 a las 21:19 -0400, David J. Ring escribió:

Package: konsole
Version: 4:18.04.0-1
Severity: grave
Justification: renders package unusable



Dear Maintainer,



konsole will not launch from mate-panel shortcut or from KDE Application menu.



konsole WILL launch from mate-terminal and will subsequently open both new 
windows and new tabs.



konsole is unusable because of the problem, but I do not know if the problem is 
konsole or the KDE launcher or mate-panel.


I'm not able to reproduce the issue as reported, can you check running konsole 
from a different terminal and see what's kind of errors are you getting (it 
might also be useful to check your ~/.xsession-errors)?


Happy hacking,
--
A computer scientist is someone who, when told to "Go to Hell," 
sees the "go to," rather than the destination, as harmful.

Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#922502: plasma-desktop: regional settings allow do select system incompatible locales

[Maximiliano Curia]

Control: reassign -1 libqt5core5a/5.11.3+dfsg-2
Control: affects -1 plasma-desktop

Control: severity -1 important

Please, don't abuse the bugs severity just to get more attention.

El 2019-02-17 a las 10:06 +0100, Charlemagne Lasse escribió:

Package: plasma-desktop
Version: 4:5.14.5-1
Severity: critical
Justification: makes unrelated software break on the system



The "regional settings" allow to select various regions which are not
available on the system (even with locales-all). An example here is
en_DE (Germany) for "Time". This is then exported at the next login in
the env variable LC_TIME as "en_DE.UTF-8". This is not supported on
any Debian buster installation and is causing other software to break.


This is a known issue (see https://bugs.debian.org/845788), plasma desktop 
here simply shows the result of calling:

QList allLocales = QLocale::matchingLocales(QLocale::AnyLanguage, 
QLocale::AnyScript, QLocale::AnyCountry);

(See kcms/formats/kcmformats.cpp in plasma-desktop) supplied by qt, which 
contains a rather large set of locales definitions, some of which don't have a 
libc's locales equivalent.


It would be nice to either limit qt's locales to the ones available to libc 
somehow, this might be done patching qtlocale at build time, or patching the 
kcmformats to reduce the list to the ones matching the currently generated 
locales.


Patches to either approach would be welcome.

Happy hacking,
--
"If you are in a hole, stop digging." -- The First Rule of Excavation
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#907297: breeze-gtk-theme: Breaks xfce4-notes (invalid string constant in "/usr/share/themes/Breeze/gtk-2.0/widgets/styles")

[Maximiliano Curia]

Control: severity -1 normal
Control: tag -1 + unreproducible

¡Hola Dmitry!

El 2018-08-26 a las 15:53 +1000, Dmitry Smirnov escribió:

Package: breeze-gtk-theme
Version: 5.13.4-1
Severity: normal
Control: affects -1 xfce4-notes



breeze-gtk-theme breaks xfce4-notes:




$ xfce4-notes
/usr/share/themes/Breeze/gtk-2.0/widgets/styles:7: error: invalid string constant 
"notebook", expected valid string constant
/usr/share/themes/Breeze/gtk-2.0/widgets/styles:2: error: invalid string constant 
"scrollbar", expected valid string constant
/usr/share/themes/Breeze/gtk-2.0/widgets/styles:4: error: invalid string constant 
"entry", expected valid string constant
/usr/share/themes/Breeze/gtk-2.0/widgets/styles:4: error: invalid string constant 
"entry", expected valid string constant
/usr/share/themes/Breeze/gtk-2.0/widgets/styles:1: error: invalid string constant 
"default", expected valid string constant
/usr/share/themes/Breeze/gtk-2.0/widgets/styles:1: error: invalid string constant 
"default", expected valid string constant
/usr/share/themes/Breeze/gtk-2.0/widgets/styles:8: error: invalid string constant 
"range", expected valid string constant
^C




I could only use xfce4-notes after uninstalling "breeze-gtk-theme"...


I couldn't reproduce the issue, executing xfce4-notes shows no errors in the 
termianl and it seems to be working fine, this of course, while using the 
breeze theme.


Thus setting the severity back to normal, and tagging the issue as 
unreproducible. Is there anything special about your setup that could somehow 
caused that the other files in /usr/share/themes/Breeze/gtk-2.0/widgets/ 
directory could not be loaded? A limit on the number of open files, perhaps?


Happy hacking,
--
"Brilliant opportunities are cleverly disguised as insolvable problems."
-- Gardener's Philosophy

"The reverse is also true." -- Corollary
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#916010: Bug #916010 in fotoxx marked as pending

[Maximiliano Curia]

Control: tag -1 pending

Hello,

Bug #916010 in fotoxx reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/fotoxx/commit/4829fb753d53bbeca6345b9260eb6fb83f30eff8


New upstream version 18.07.2 (closes: #916010)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/916010

Bug#908676: [kwin-wayland] Plasma wayland session restarted after pluging or unpluging secondary monitor over thunderbolt

[Maximiliano Curia]

Control: severity -1 normal

¡Hola Jiri!

El 2018-09-12 a las 22:50 +1000, Jiri Kanicky escribió:

Package: kwin-wayland
Version: 4:5.13.5-1
Severity: serious



When I plug or unplug external monitor over thunderbolt the session logs
me out, sometimes the system crashes.


I'm sorry to hear that. Sadly wayland in general is not particularly stable. 
Quoting the package description:


This package provides the wayland version, which is still a work in progress
project, and is available as a PREVIEW release. Don't expect the same
stability as with the x11 version.

On the other hand, I would suspect that the real issue here is not caused by 
kwin but by kscreen or by wayland itself. For the wayland part you could test 
if the issue is reproducible using gnome under wayland. I'm not sure about how 
to test if the issue is in kscreen.


Happy hacking,
--
"I decry the current tendency to seek patents on algorithms. There are better 
ways to earn a living than to prevent other people from making use of one's 
contributions to computer science."

-- Donald Knuth
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#897792: [Pkg-kde-extras] Bug#897792: libqaccessibilityclient: ftbfs with GCC-8

[Maximiliano Curia]

¡Hola!

El 2018-05-04 a las 12:22 +, Matthias Klose escribió:

Package: src:libqaccessibilityclient
Version: 0.1.1-5
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8



Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.



The package fails to build in a test rebuild on at least amd64 with
gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.



The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/libqaccessibilityclient_0.1.1-5_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.



To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.



 apt-get -t=experimental install g++



Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-8/porting_to.html


It seems to me that src:libqaccessibilityclient currently has not reverse 
dependencies, and since it's still qt4 based, we might want to get rid of it. 
Although, there is an "unstable" qt5 release
(https://download.kde.org/unstable/libqaccessibilityclient/), and recent 
versions of kmag seem to be trying to use that.


I'm ccing Sandro, as he might be working in kmag and adding the support of 
libqaccessibilityclient to our packages [1].


[1]: 
https://salsa.debian.org/qt-kde-team/kde/kmag/commit/6fd9637477b4eb9da465e3c5fe782352a20f607a

Sandro, if you plan to upload libqaccessibilityclient 0.2 please close this 
issue with it.


Happy hacking,
--
"Executive ability is deciding quickly and getting somebody else to do the
work."
-- Pollard's Postulate
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#903713: plasma-browser-integration: "This_file_is_part_of_KDE" in debian/copyright?

[Maximiliano Curia]

¡Hola Luigi!

El 2018-07-14 a las 10:37 +0100, Chris Lamb escribió:

My interpretation of this is that the intention is to assign the copyright
to the kde project, although it's not a hundred percent clear.



I should have been clearer, sorry — I understand you are going with
whatever the file says but I am requesting that you make this clearer,
perhaps by getting a statement from upstream or similar.



"This_file_is_part_of_KDE" is really not suitable as an author,
whatever the file says, after all.


Chris raised the issue of the po files distributed by kde containing some (not 
very clear) template parts, in particular the copyright assignments to 
This_file_is_part_of_KDE.


With your kde i18n team hat on, would you consider it feasible to replace 
these strings with something clearer?


If the intention is for the translators to assign the copyright to kde it 
should be assigned to KDE.e.V, if the intention is for each translator to keep 
the copyright assignment the This_file_is_part_of_KDE part of the template 
needs to be updated to say AUTHOR .


The first case should be "scriptable" the second case, would need to manually 
modifying each po file that contains the "This_file_is_part_of_KDE" text.


Happy hacking,
--
"Brilliant opportunities are cleverly disguised as insolvable problems."
-- Gardener's Philosophy

"The reverse is also true." -- Corollary
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#903713: plasma-browser-integration: "This_file_is_part_of_KDE" in debian/copyright?

[Maximiliano Curia]

¡Hola Chris!

El 2018-07-13 a las 16:39 +0100, Chris Lamb escribió:

Source: plasma-browser-integration
Version: 5.13.1-1
Severity: serious
X-Debbugs-CC: Maximiliano Curia 



I just ACCEPTed plasma-browser-integration from NEW but noticed it
declares "This_file_is_part_of_KDE" as an copyright holder.



This seems very... odd.


Agreed, this is caused by the templates used in po files. For example in 
po/ca/plasma_runner_browsertabs.po it says:

# Translation of plasma_runner_browsertabs.po to Catalan
# Copyright (C) 2017 This_file_is_part_of_KDE
# This file is distributed under the license LGPL version 2.1 or
# version 3 or later versions approved by the membership of KDE e.V.
#
# Josep Ma. Ferrer , 2017.

Josep here is clearly the author, but there is no copyright assigment 
statement with his name. My interpretation of this is that the intention 
is to assign the copyright to the kde project, although it's not a hundred 
percent clear. So I go with whatever the file says.


Happy hacking,
--
"The best way to predict the future is to invent it."
-- Alan Kay
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#900352: new xorg-server version causes a random freezes in plasmashell

[Maximiliano Curia]

Package: src:xorg-server
Version: 2:1.20.0-2
Severity: critical
Tags: upstream

Hi,

The severity is set as it breaks "unrelated programs" although I'm not sure a 
desktop environment can be called "unrelated" to x, but in any case, it would 
be better if this version of xorg does not migrate to testing till this is 
fixed.


The new xorg-server version seems to be causing plasmashell to freeze. This 
was first reported in #900145, and it's also seen in other distros: 
https://bugs.archlinux.org/task/58549


Upstream seems to have a patch for this (actually two patches that fix this 
with two different aproaches), that I havent tested: 
https://lists.x.org/archives/xorg-devel/2018-May/056829.html


Happy hacking,

-- System Information:
Debian Release: buster/sid
 APT prefers testing-debug
 APT policy: (700, 'testing-debug'), (700, 'testing'), (600, 'stable-updates'), 
(600, 'stable-debug'), (600, 'proposed-updates'), (600, 'stable'), (500, 
'buildd-unstable'), (50, 'unstable-debug'), (50, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

--
"Always code as if the person who ends up maintaining your code is a violent 
psychopath who knows where you live."

-- John Woods
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#898556: [kwin-wayland] Closing windows in Plasma Wayland crashes the entire session

[Maximiliano Curia]

Control: severity -1 important

¡Hola Alexander!

El 2018-05-13 a las 17:09 +0300, Alexander Kernozhitsky escribió:

Package: kwin-wayland
Version: 4:5.12.5-1
Severity: grave



I tried Plasma session on Wayland today. Closing a window in it crashes the
session and returns me back to SDDM.


I'm sorry to hear that, but most of the wayland support in Debian is in 
preview release mode, in fact, I think that that problem that you are 
reporting might be in xwayland or in a lower layer of the wayland stack (see 
#897390[1], for example).


I couldn't reproduce the issue in my machine. Is there any other wayland 
desktop session that does work for you?


Given this, I'm lowering the severity.

Happy hacking,

[1]: https://bugs.debian.org/897390
--
"It's a well-known fact that computing devices such as the abacus were 
invented thousands of years ago. But it's not well known that the first use of 
common computer protocol occurred in the Old Testament. This, of course, was 
when Moses aborted the Egyptians' process with a control-sea."

-- Tom Galloway (recs.arts.comics, February 1992)
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#897338: Tested on hardware

[Maximiliano Curia]

¡Hola Александр!

El 2018-05-03 a las 07:54 +0300, Александр Керножицкий escribió:

I tried Debian Testing on real hardware and SDDM seems to work there. So I can 
reproduce the bug only on VirtualBox.


It seems that the new sddm requires virtualbox-guest-dkms and 
virtualbox-guest-x11 to run inside a virtualbox, I'm not sure why.


Happy hacking,
--
"We must be very careful when we give advice to younger people: sometimes they 
follow it!"

-- Edsger W. Dijkstra
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

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

[Maximiliano Curia]

¡Hola Alexander!

El 2018-05-01 a las 17:12 +0300, Alexander Kernozhitsky escribió:

Package: sddm
Version: 0.17.0-1
Severity: grave
Justification: renders package unusable


I tried to do a fresh install of Debian Testing with KDE. After installing 
it, SDDM did not launch. Launching it manually with "sudo systemctl start 
sddm" did not have effect also.



"systemctl status sddm" shows the following:



● sddm.service - Simple Desktop Display Manager
  Loaded: loaded (/lib/systemd/system/sddm.service; indirect; vendor preset: 
enabled)
  Active: active (running) since Tue 2018-05-01 16:56:33 +03; 12min ago
Docs: man:sddm(1)
  man:sddm.conf(5)
 Process: 412 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 
2>/dev/
Main PID: 421 (sddm)
   Tasks: 2 (limit: 1156)
  Memory: 11.7M
  CGroup: /system.slice/sddm.service
  └─421 /usr/bin/sddm



Though I don't see the login screen, tty7 is blank.


I tried to rebuild and install sddm from Ubuntu Bionic (where it works), but 
met the same problem. Installing sddm 0.14.0-4 from stable did solve the 
problem.


Is X started at all?

What's the output of `` update-alternatives --query sddm-debian-theme `` ?

It seems that there is a known issue upstream with some nvidia drivers:
https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1762885
https://github.com/sddm/sddm/issues/1019

Are you using a nvidia card? Can you please check if the problem goes away 
with an older version of the nvidia drivers?


Happy hacking,
--
"Anytime you have a fifty-fifty chance of getting something right, there's a
90 percent probability you'll get it wrong."
-- The 50-50-90 rule
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#892596: [systemsettings] Comes up with black windows

[Maximiliano Curia]

Control: severity -1 important
Control: tag -1 unreproducible

¡Hola David!

El 2018-03-11 a las 11:29 +0200, David Baron escribió:
Package: systemsettings 
Version: 4:5.12.3-1 
Severity: grave


--- Please enter the report below this line. --- 
Previous version and current version:
Application comes up with black windows. The left pane will show its MouseOver 
toolboxes.


I failed to reproduce this issue. Can you still reproduce it? Do you get any 
output in the terminale if you launch systemsettings from it?


Debian Release: buster/sid 
 500 yakkety ppa.launchpad.net 
 500 sid linux.dropbox.com 
 500 lucid   ppa.launchpad.net 


reportbug-ng is not very helpful here.

--- Package information. --- 
Depends(Version) | Installed 
-+- 
qml-module-org-kde-kcm   | 5.42.0-2 
qml-module-org-kde-kirigami2 | 5.42.0-3 
qml-module-qtquick-controls  | 5.9.2-2 
qml-module-qtquick-layouts   | 5.9.2-3 
qml-module-qtquick2  | 5.9.2-3 
kio  | 5.42.0-3 
kpackagetool5| 5.42.0-2 
libc6  (>= 2.14) | 
libkf5activities5(>= 4.96.0) | 
libkf5activitiesstats1 (>= 5.20) | 
libkf5auth5  (>= 4.96.0) | 
libkf5completion5(>= 4.97.0) | 
libkf5configcore5(>= 4.98.0) | 
libkf5configgui5 (>= 4.97.0) | 
libkf5configwidgets5 (>= 4.96.0) | 
libkf5coreaddons5(>= 5.16.0) | 
libkf5crash5 (>= 5.15.0) | 
libkf5dbusaddons5(>= 4.99.0) | 
libkf5declarative5   (>= 4.96.0) | 
libkf5i18n5  (>= 5.17.0) | 
libkf5iconthemes5(>= 4.96.0) | 
libkf5itemviews5 (>= 4.96.0) | 
libkf5kcmutils5  (>= 4.96.0) | 
libkf5khtml5 (>= 4.96.0) | 
libkf5kiowidgets5(>= 4.96.0) | 
libkf5package5(>= 5.5.0+git) | 
libkf5service-bin| 
libkf5service5   (>= 4.99.0) | 
libkf5widgetsaddons5 (>= 5.35.0) | 
libkf5windowsystem5  (>= 4.96.0) | 
libkf5xmlgui5(>= 4.98.0) | 
libqt5core5a (>= 5.9.0~beta) | 
libqt5dbus5  (>= 5.7.0~) | 
libqt5gui5(>= 5.7.0) | 
libqt5qml5(>= 5.0.2) | 
libqt5quick5  (>= 5.0.2) | 
libqt5quickwidgets5   (>= 5.5.0) | 
libqt5widgets5   (>= 5.7.0~) | 
libstdc++6(>= 4.1.1) |


And definitelly not helpful in not showing the installed versions, for most of 
the dependencies. Could you please use reportbug to generate the package 
information again?


Happy hacking,
--
"Fighting patents one by one will never eliminate the danger of software
patents, any more than swatting mosquitoes will eliminate malaria."
-- Richard M. Stallman
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#873370: kmenuedit: All versions in repositories are extremely out of date.

[Maximiliano Curia]

¡Hola Brice!

El 2017-08-26 a las 21:51 -0600, Brice Hunt escribió:
Package: kmenuedit 
Version: 4:5.8.4-1 
Severity: grave 


Don't abuse the bug severities.


Justification: renders package unusable


The out of date kmenuedit saves configuration files in the wrong directories, causing most menu edits to be lost. 
The newest version in repositories is 4.8.5. The newest version available from upstream is 5.10.5. The version of kmenuedit 
in the repositories does not work with the version of plasma that is available in the repositories.



The recommended solution is to package a more up-to-date version for Debian and 
submit it.


Closing the issue as, it's not really an issue for 4:5.8.4-1 (when using with 
plasma 5.8) nor a current issue with plasma 5.10.


Happy hacking,
--
"By definition, when you are investigating the unknown, you do not know what
you will find"
-- The Ultimate Principle
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#879901: kded5 mem ballooning consumes over 6520.81MB of RAM!

[Maximiliano Curia]

Control: severity -1 important

kded acts as a proxy to the background kde services, most likely the leak is 
in one of them, not in kded per se. I'm degrading the severity as I can't 
reproduce it.


¡Hola Nicholas!

El 2017-11-29 a las 05:14 -0500, Nicholas D Steeves escribió:
Please let me know what I can do to help debug this further, because 
I'd like to help solve this asap.


It would be helpful to know which threads kded is executing, in order to do 
that please run the following command: pstree -tp | less, and look for the kded 
processes.


Also it would be interesting to know which services are being managed by kded, 
to find that out you can use the system settings' "Startup and Shutdown" 
"Background services", you can see which services are currently running in you 
session, you can attach your ~/.config/kded5rc that stores this information.


A known culprit on wasting resources is the baloo file indexer (which should 
be disabled by default), I don't remember seeing a leak in kded related to 
baloo, but I haven't paid much attention to it since we disabled it. You can 
check if your file indexer is disabled in: "System Settings" "Search" "File 
Search" "Enable File Search"


Happy hacking,
--
"Any change looks terrible at first." -- Principle of Design Inertia
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#875317: python-astropy is no longer installable in unstable

[Maximiliano Curia]

Source: python-astropy
Version: 2.0.1-2
Severity: grave

Hi,

With the upload of python2.7 2.7.14~rc1-3, libpython2.7-stdlib introduces a 
breaks against python-astropy, as python-astropy uses symbols related to the 
_PyFPE module which was removed in the latest python2.7 version.


That means that python-astropy is currently uninstallable in unstable, thus 
the severity of this bug. (Also, this makes astrometry.net uninstallable and 
thus it makes kstars FTBFS).


Happy hacking,

-- System Information:
Debian Release: 9.1
 APT prefers stable-updates
 APT policy: (600, 'stable-updates'), (600, 'stable-debug'), (600, 
'proposed-updates'), (600, 'stable'), (60, 'testing-debug'), (60, 'testing'), 
(50, 'unstable-debug'), (50, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

--
"If the code and the comments disagree, then both are probable wrong."
-- Norm Schryer
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#874169: AppStreamQtConfig.cmake no longer usable in i386

[Maximiliano Curia]

¡Hola Matthias!

El 2017-09-03 a las 21:45 +0200, Matthias Klumpp escribió:

2017-09-03 21:15 GMT+02:00 Maximiliano Curia <m...@debian.org>:

[...]
# check that the installed version has the same 32/64bit-ness as the one 
which is currently searching:
if(NOT CMAKE_SIZEOF_VOID_P STREQUAL "8") 
  math(EXPR installedBits "8 * 8") 
  set(PACKAGE_VERSION "${PACKAGE_VERSION} (${installedBits}bit)") 
  set(PACKAGE_VERSION_UNSUITABLE TRUE) 
endif()


This last part `NOT CMAKE_SIZEOF_VOID_P STREQUAL "8"', seems to indicate 
that it would never work on a 32 bit system. Is the "8" here meant to be 
replaced at build time?


Can you try removing that entire section and see if that fixes it? 
It serves no real purpose in how AppStreamQt is used anyway.


Commenting out that block allowed frameworkintegration to build.

Happy hacking,
--
"Any change looks terrible at first." -- Principle of Design Inertia
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#874169: AppStreamQtConfig.cmake no longer usable in i386

[Maximiliano Curia]

Source: appstream
Version: 0.11.4-1
Severity: critical

The latest appstream release migrates the build system to meson, but builds a 
cmake file for compatibility, so far so good. Sadly, the logic to 
detect if the build was for 32 bits or for 64 bits seems to be incorrect, 
which makes software that build depends on libappstreamqt-dev to ftbfs [1].


I looked at the code but couldn't find the root of the issue. The end of the generated 
file (/usr/lib/i386-linux-gnu/cmake/AppStreamQt/AppStreamQtConfigVersion.cmake) says:


# check that the installed version has the same 32/64bit-ness as the one which 
is currently searching:
if(NOT CMAKE_SIZEOF_VOID_P STREQUAL "8")
  math(EXPR installedBits "8 * 8")
  set(PACKAGE_VERSION "${PACKAGE_VERSION} (${installedBits}bit)")
  set(PACKAGE_VERSION_UNSUITABLE TRUE)
endif()

This last part `NOT CMAKE_SIZEOF_VOID_P STREQUAL "8"', seems to indicate that it 
would never work on a 32 bit system. Is the "8" here meant to be replaced at 
build time?


Happy hacking,

[1]
https://buildd.debian.org/status/fetch.php?pkg=frameworkintegration=i386=5.37.0-2=1504461982=0

-- System Information:
Debian Release: 9.1
 APT prefers stable-debug
 APT policy: (600, 'stable-debug'), (600, 'proposed-updates'), (600, 'stable'), 
(60, 'testing-debug'), (60, 'testing'), (50, 'unstable-debug'), (50, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

--
"C makes it easy to shoot yourself in the foot; C++ makes it harder,
but when you do it blows your whole leg off."
-- Bjarne Stroustrup
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#873696: marked as pending

[Maximiliano Curia]

tag 873696 pending
thanks

Hello,

Bug #873696 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/python-modules/packages/python-intbitset.git/commit/?id=2cf38b2

---
commit 2cf38b2cd179b06af8a94c318fea59524fab3522
Author: Maximiliano Curia <m...@gnuservers.com.ar>
Date:   Wed Aug 30 22:09:41 2017 +0200

Update the debian/changelog

Gbp-Dch: Ignore

diff --git a/debian/changelog b/debian/changelog
index 21e17de..c8c6be7 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,10 @@
 python-intbitset (2.3.0-2~) UNRELEASED; urgency=medium
 
   * New revision
+  * Disable extra_compile_options.
+Thanks to Adrian Bunk for the report (Closes: 873696)
 
- -- Maximiliano Curia <m...@debian.org>  Wed, 30 Aug 2017 19:23:46 +0200
+ -- Maximiliano Curia <m...@debian.org>  Wed, 30 Aug 2017 22:09:11 +0200
 
 python-intbitset (2.3.0-1) sid; urgency=medium
 

Bug#864705: [plasma-desktop] "KDE Menu"/"Alt+F2" runner don't work if "Focus stealing prevention" set "High" or "Extream" and any window focused

[Maximiliano Curia]

Control: severity -1 minor

¡Hola Sergey!

El 2017-06-13 a las 11:57 +0700, Sergey Nikitin escribió:
Package: plasma-desktop 
Version: 4:5.8.6-1 
Severity: criticaldd


Please don't abuse the bug severities.

If you set 
System settings->Window Management->Window Behavior: "Click To Focus" 
and "Focus stealing prevention" to "High"/"Extream" 
You can't open KDE Menu by menu-key or mouse click, and can't open 
task-runner by Alt+F2 shortcut also, if any window already had 
focused.


Happy hacking,
--
"If you are in a hole, stop digging." -- The First Rule of Excavation
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#860515: Many translations missing in french KDE lang packages while we're close to release

[Maximiliano Curia]

Control: severity -1 important
Control: forcemerge 857647 860515

¡Hola Julien!

El 2017-04-18 a las 06:59 +0200, Julien Aubin escribió:
Package: kde-l10n-fr 
Version: 4:16.04.3-1 
Severity: grave


I know that the severity is exagerated but this is because we're very close to 
release and the issue is still not fixed.


Please don't create duplicated bugs with unjustified severities, this only 
reduces the value of the bugs being reported (and increases the time we need 
to expend dealing with them instead of fixing them)


There are still many missing translations in French KDE translation package, 
such as many "Apply" buttons left untranslated, some "do you want to continue" 
questions untranslated and so on. The issue is due to some translations in 
Debian being too old, as the same package, kde-l10n-fr 16.04 in Gentoo is not 
affected.


It seems to me that the missing translations are from qt5's QDialog stock 
buttons. So this might need to be addressed in the qt packages.


This is, at least for the dolphin settings dialog (which creates a 
QDialogButtonBox with:

QDialogButtonBox* box = new QDialogButtonBox(QDialogButtonBox::Ok
 | QDialogButtonBox::Apply | QDialogButtonBox::Cancel | 
QDialogButtonBox::RestoreDefaults);

And it doesn't override the buttons texts.

Happy hacking,
--
"Seek simplicity, and distrust it." -- Whitehead's Rule
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#856904: ksirk FTBFS on architectures where char is unsigned

[Maximiliano Curia]

¡Hola John!

El 2017-03-13 a las 12:40 +0100, John Paul Adrian Glaubitz escribió:

Hi!

On 03/06/2017 10:49 AM, John Paul Adrian Glaubitz wrote:
The attached debdiff contains a trivial patch which changes the declaration 
of tbl[] from "char" to "signed char". With the patch applied, I verified 
that the package builds successfully on armhf.



Any progress on this?


Not really.


Shall I go ahead and perform an NMU?


Sure. Thanks a lot for working on this.

Happy hacking,
--
"C makes it easy to shoot yourself in the foot; C++ makes it harder,
but when you do it blows your whole leg off."
-- Bjarne Stroustrup
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#850114: kscd: Only play first trackon all modes(loop track, loop ,and no loop and random and no random mode)

[Maximiliano Curia]

¡Hola John!

El 2017-03-08 a las 09:43 +0100, John Paul Adrian Glaubitz escribió:

On 03/08/2017 08:27 AM, Maximiliano Curia wrote:

Thanks a lot for finding this.


You're welcome. Let me know if you want me to perform the NMU or if you can do it 
yourself quickly so we can get this bug off the RC list for Stretch.


Built... Uploaded. I'll send an unblock request.

PS: It would be great if you could forward your MusicBrainz5 patch to upstream. 
   The kscd upstream repository still receives some updates from time to time.


Back when I prepared the patch I created review request for it:
https://git.reviewboard.kde.org/r/127196/

But the musicbrainz servers started giving back 503 responses on every 
request, so I couldn't test the patch any further. Also, the hacky hardcoded 
id was needed in my case as I don't have any audio cd around.


So maybe you could send a follow up in the review request?

Happy hacking,
--
"Backtracking algorithms are nondeterministic, not in the sense of being
random, but in the sense of having free will."
-- Robert W. Floyd
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#850114: kscd: Only play first trackon all modes(loop track, loop ,and no loop and random and no random mode)

[Maximiliano Curia]

¡Hola John!

El 2017-03-06 a las 20:12 +0100, John Paul Adrian Glaubitz escribió:

Control: tags -1 patch



The attached debdiff contains a patch which fixes the issue.


It turns out that someone, for whatever reasons, had hard-coded the disc ID to 
"64e.YDM.N2tZJzmqrN48iWfJ9.4-" [1] which is the ID for Nirvana's "Smells Like 
Teen Spirit" album. Just reverting the patch fixes the issue for me and audio 
CDs are detected properly again.


Ouch, that was part of my tests when I was preparing the musicbrainz patch. 
That should never have reached the Debian repos.


Thanks a lot for finding this.
--
"Brilliant opportunities are cleverly disguised as insolvable problems."
-- Gardener's Philosophy

"The reverse is also true." -- Corollary
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#856002: sddm: only shows white screen

[Maximiliano Curia]

Control: fixed -1 0.14.0-1

¡Hola Dominik!

El 2017-02-24 a las 11:30 +0100, Dominik George escribió:
sddm logs the output to the syslog, please check that, and possibly the 
Xorg.0.log, for errors. Which video card are you using?


Nothing suspicious in the logs. I am using an Intel HD Graphics 4400 
something-whatever-on-board thingy.


Also, could you test sddm 0.14.0-1 (which is currently available in 
experimental)?


0.14.0-1 indeed works. And when starting, it loaded some default them 
and complaint that the breeze theme could not be found and I in turn 
found that the sddm-theme-breeze package was not installed. Maybe that's 
the issue with 0.13.0 as well and it simply fails to complain?


For 0.13, breeze is indeed the default theme, but if it's not installed, it 
reverts to whatever is found (searching in alphabetic order, iirc). From the 
original report I see that you had maui installed, so that should be the theme 
that's trying to be launched in 0.13, even more, For 0.14, the theme that's 
embedded is in fact maui. I'm not sure why it's not working for you in 0.13 
but it's working in 0.14. But hopefully we might get the release team approval 
for 0.14.0-2 (#855624).


Happy hacking,
--
"Whenever possible, steal code." -- Tom Duff
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#856002: sddm: only shows white screen

[Maximiliano Curia]

Control: tag -1 + moreinfo

¡Hola Dominik!

El 2017-02-24 a las 08:59 +0100, Dominik George escribió:
Package: sddm 
Version: 0.13.0-1 
Severity: grave 
Justification: renders package unusable



sddm only shows a white screen after starting. sddm.log remains empty.


sddm logs the output to the syslog, please check that, and possibly the 
Xorg.0.log, for errors. Which video card are you using?


Also, could you test sddm 0.14.0-1 (which is currently available in 
experimental)?


Happy hacking,
--
"Haskell is faster than C++, more concise than Perl, more regular than Python,
more flexible than Ruby, more typeful than C#, more robust than Java, and has
absolutely nothing in common with PHP."
-- Audrey Tang
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#853844: sddm: purging fails because of deluser/userdel (sddm is currently used by a process)

[Maximiliano Curia]

Control: clone -1 -2
Control: reassign -2 debconf 1.5.60
Control: retitle -2 db_purge: exits with error code 8 when using deluser in the 
same postinst

¡Hola Laurent!

El 2017-02-01 a las 13:31 +0100, Laurent Bonnaud escribió:
Package: sddm 
Version: 0.14.0-1 
Severity: serious



here is the problem:


# apt purge sddm   sddm-theme-breeze 
Reading package lists... Done 
Building dependency tree 
Reading state information... Done 
The following packages will be REMOVED:
 sddm* sddm-theme-breeze* 
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. 
After this operation, 2 595 kB disk space will be freed. 
Do you want to continue? [Y/n]
(Reading database ... 261837 files and directories currently installed.) 
Removing sddm (0.14.0-1) .]
Please be sure to run "dpkg-reconfigure gdm3". 
Removing sddm-theme-breeze (4:5.8.5-1) ... 
Processing triggers for man-db (2.7.6.1-2) ... 
(Reading database ... 261663 files and directories currently installed.) 
Purging configuration files for sddm (0.14.0-1) ... 
Removing user `sddm' ... 
Warning: group `sddm' has no more members. 
userdel: user sddm is currently used by process 658 
/usr/sbin/deluser: `/usr/sbin/userdel sddm' returned error code 8. Exiting. 
Could not remove sddm user. 
/usr/sbin/delgroup: `sddm' still has `sddm' as their primary group! 
Could not remove sddm group.



Stopping the service before the purge fixes the problem.


This is the expected output when sddm is still running. We don't want to stop 
the running display manager as it will kill the graphical user session.


userdel: user sddm is currently used by process 658 
/usr/sbin/deluser: `/usr/sbin/userdel sddm' returned error code 8. Exiting. 
/usr/sbin/delgroup: `sddm' still has `sddm' as their primary group!


This part is not caused by us. Mmh, after a closer inspection this is caused 
by the debconf purge, which get's confused with any message written to stdout.


I'm cloning the issue to debconf, as it would be better if db_purge wouldn't be 
trying to parse whatever was printed to the stdout.


On the sddm usecase, I'll add the deluser and echo redirections (>&2).

Happy hacking,
--
A computer scientist is someone who, when told to "Go to Hell,"
sees the "go to," rather than the destination, as harmful.
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#848523: More info

[Maximiliano Curia]

Control: severity -1 normal

¡Hola Ben!

El 2017-01-23 a las 09:54 -0800, Ben Longbons escribió:
Sorry, I've since upgraded my *entire* system from testing to 
unstable, and the problem went away at some point.


If it wasn't a bug in some dependency, my guess is that something had 
migrated to testing without all of its true dependencies having 
migrated. There are a lot of ways that that can happen - plugins, 
changes in the *use* of some already-existing library call (e.g. 
accepting new enum values).


You can debootstrap from 
http://snapshot.debian.org/archive/debian/20161219T152404Z/ to 
investigate the underlying cause, since if it's a missing dependency 
problem, it *will* cause problems again sooner or later.



But here's the information you requested, for what it's worth:


kwin hasn't entered into testing because of this bug and the #848524 report, 
this package was installed from sid, bringing only a small part of it's 
dependencies, from the original report:


ii  libkwinglutils9   4:5.8.2-1+b1
ii  libkwinxrenderutils9  4:5.8.2-1+b1

There are some parts in your kwin-x11 that weren't correctely upgraded, I'll 
bump this runtime dependencies.


Happy hacking,
--
"C makes it easy to shoot yourself in the foot; C++ makes it harder,
but when you do it blows your whole leg off."
-- Bjarne Stroustrup
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#848524: kwin-wayland: rapid memory leak

[Maximiliano Curia]

Control: severity -1 normal

¡Hola Ben!

El 2016-12-17 a las 20:19 -0800, Ben Longbons escribió:
Package: kwin-wayland 
Version: 4:5.8.4-1 
Severity: grave 
Justification: renders package unusable


Since kwin-x11 was being even crashier than usual, I tried the other 
Plasma (wayland) entry for a change.



To my great joy, it worked flawlessly ... for the first several minutes.


After that, however, everything became nonresponsive, and I observed 
kwin-wayland using over 2GB each of both RAM and SWAP as I killed it.



I'm not desperate enough to use GNOME, so I'm stuck on the CLI for now.


kwin-wayland and the Plasma (wayland) desktop sessions are work in progress 
versions. Packaged to be tested, but not (currently) real alternatives. I'll 
add this information to the package descriptions of kwin-wayland and 
plasma-workspace-wayland.



Versions of packages kwin-wayland depends on:
ii  kwayland-integration 5.8.4-1 
ii  kwin-common  4:5.8.4-1 
ii  kwin-wayland-backend-drm [kwin-wayland-backend]  4:5.8.2-1+b1


Your kwin was not completely upgraded. I guess this shows a missing stronger 
runtime dependency.


Happy hacking,
--
"The use of COBOL cripples the mind; its teaching should, therefore, be
regarded as a criminal offense."
-- Edsger W. Dijkstra
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#854838: kde-full: When kde-full is installed, upgrading from jessie to stretch is extremely hard (if not impossible for beginners)

[Maximiliano Curia]

Control: severity -1 normal

¡Hola Julien!

El 2017-02-11 a las 00:28 +0100, Julien Aubin escribió:
Package: kde-full 
Version: 5:92 
Severity: critical 
Justification: breaks the whole system


If anything is "apt upgrade" in jessie the one blame here, please see bellow.

This bug only appears when upgrading a jessie system to stretch, but is a 
release blocker at least w/ amd64 arch with foreign i386 arch enabled.


As per documentation, dist upgrade from jessie to stretch should work as 
follows :
1/ update sources.list 
2/ apt update 
3/ apt upgrade 
4/ apt dist-upgrade


The issue actually lies at the apt upgrade step, as it is reported that package 
kdepimlibs-data breaks several other packages, so the upgrade cannot be 
performed.


The upgrade in apt doesn't behaves in the same way as the upgrade in apt-get. 
The first one tries to install the new packages that the new versions depend 
on, while the one in apt tries to avoid installing and removing packages.


apt-get upgrade should take care of upgrading the packages that don't bring 
new dependencies (about half of my test installation).


I'll blame the upgrade procedure you are trying to follow, is it documented as 
such somewhere?


After that, apt-get dist-upgrade seems to do almost everything else, but it 
tried to remove aptitude, so:

apt-get dist-upgrade aptitude libcwidget3v5

Would do the right thing for me. As a general recommendation, it's always a 
good idea to check the list of new packages and the list of packages to 
remove.


In another instance of the test computer I tried upgrading kde first, and:
apt install kde-full

Seems to do the right thing.

So then you have either to attempt to fix manually the issue, or with a dist- 
upgrade, but in both situations the result is the same : the situation becomes 
completely messy, with many broken packages you have to fix manually with dpkg 
commands. It is not impossible to run the upgrade this way, but anyway it is 
painful.


I don't see how kde-full could fix apt's upgrade behavior in jessie, I think 
that the behavior in stretch is better, but even so, nothing from the kde-full 
side. Please use apt-get upgrade to upgrade the upgradable parts in a jessie 
system.


Happy hacking,
--
"There are only two things wrong with C++: The initial concept and the
implementation."
-- Bertrand Meyer
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#854355: Acknowledgement (/usr/bin/kmail: Unable to send emails - Could not compose message: Inappropriate ioctl for device)

[Maximiliano Curia]

Control: tag -1 + moreinfo

¡Hola Dennis!

El 2017-02-06 a las 13:01 +0100, Dennis Schridde escribió:
The reason for this seems to be gnupg related: When I start KMail from a 
terminal and try to send a message, a text ssh-askpass dialogue is shown on 
the terminal. If I enter my gnupg key password there, the email is being send 
without any problems.



My assumption is now that ksshaskpass is somewhat broken.



ksshaskpass/testing,unstable,now 4:5.8.4-1 amd64 [installed,automatic]


The program launched by gnupg to ask the passphrase is pinentry (which is an 
alternative). What's your pinentry and pinentry-x11?


$ ls -l /etc/alternatives/pinentry*

Is the problem reproducible for you, if you set pinentry to pinentry-qt?

Happy hacking,
--
"It is practically impossible to teach good programming to students that have
had a prior exposure to BASIC: as potential programmers they are mentally
mutilated beyond hope of regeneration."
-- Edsger W. Dijkstra
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#811980: libusbtc08: FTBFS with GCC 6: symbol changes

[Maximiliano Curia]

¡Hola Nobuhiro!

El 2017-02-11 a las 15:48 +0900, Nobuhiro Iwamatsu escribió:

Control: tags 811980 + patch


This package fails to build with GCC 6.  GCC 6 has not been released 
yet, but it's expected that GCC 6 will become the default compiler for 
stretch.


Note that only the first error is reported; there might be more.  You 
can find a snapshot of GCC 6 in experimental.  To build with GCC 6, 
you can set CC=gcc-6 CXX=g++-6 explicitly.


You may be able to find out more about this issue at 
https://gcc.gnu.org/gcc-6/changes.html


I create a patch which update symboles file. 
Could you check this patch?


I've considered requesting the removal of libusbtc08 as I'm no longer using 
it, it seems that there aren't any users for it, and upstream stopped 
distributing their source code for the newer versions 
(https://www.picotech.com/downloads/linux).


If you want to take care of libusbtc08 as is and/or work with upstream please 
consider taking over this package.


In any case, I'm listed in the https://wiki.debian.org/LowThresholdNmu, feel 
free to upload the fix without asking for permission.


Happy hacking,

> --- libusbtc08-1.7.2/debian/libusbtc08-1.symbols   2015-08-27 
05:37:20.0 +0900
> +++ libusbtc08-1.7.2/debian/libusbtc08-1.symbols   2017-02-11 
15:30:30.0 +0900
> @@ -67,9 +67,6 @@
>  _ZN13PicoUsbDevice4InitEv@Base 1.7.2
>  _ZN13PicoUsbDevice5CountEt@Base 1.7.2
>  _ZN13PicoUsbDevice9EnumerateEPPS_jt@Base 1.7.2
> - (optional=gccinternal)_ZN13PicoUsbDeviceD0Ev@Base 1.7.2
> - (optional=gccinternal)_ZN13PicoUsbDeviceD1Ev@Base 1.7.2
> - (optional=gccinternal)_ZN13PicoUsbDeviceD2Ev@Base 1.7.2

No need to drop optional fields (these are the default destructors, and might 
show up again in a future version of gcc).


...

> - (optional=gccinternal)_ZTV13PicoUsbDevice@Base 1.7.2

Mmh, this one should probably stay, as the class is still present and 
contains virtual methods


Most likely you would need a second upload after processing all the buildds 
logs, it might make sense to use the pkg-kde-tools symbolshelper for this.


Happy hacking,
--
"There are two major products that come out of Berkeley: LSD and BSD.
We don't believe this to be a coincidence."
-- Jeremy S. Anderson
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#846877: plasma-desktop: Sddm can not start kde. Then panel is not working.

[Maximiliano Curia]

Control: severity -1 important
Control: tag -1 - upstream

¡Hola laurent!

El 2016-12-03 a las 22:14 +0100, laurent B escribió:
Package: plasma-desktop 
Version: 4:5.8.4-1 
Severity: grave 
Tags: upstream 
Justification: renders package unusable



Dear Maintainer,



*** Reporter, please consider answering these questions, where appropriate ***

  * What led up to the situation? 
  upgrade some packages on debian sid (this week from 28 november to 2th december 2016) 
  * What exactly did you do (or not do) that was effective (or 
ineffective)? 
try to login in plasma-kde from sddm 
  * What was the outcome of this action? 
  the blackcreen with K icon  showed off but hand out indefinitely. However 
  I found a simple workaourd : go to tty1 then back to tty7 and get greeted 
  with the sound of plasma login. However then at some point  the panel will 
  stop work and i could only manage to switch from one windows to another 
  going in the to left side of the screen.


It seems that you are suffering from two different issues, the first one seems 
to be related to the screen handling, which might be related to an issue of 
the video driver as reported in the previous reply. Please try the mentioned 
workarounds and report back.


The second issue is that plasmashell crashes after a while (when using certain 
plasmoids), which seems to be caused by an issue in qtdeclarative. There is a 
new upcoming version of qtdeclarative and it might be fixed in that one.


Happy hacking,
--
"People get lost in thought because it is unfamiliar territory."
-- Fix's Principle
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#846252: kf5-kdepim-apps-libs: FTBFS: recipe for target 'kaddressbookgrantlee/src/CMakeFiles/KF5KaddressbookGrantlee.dir/all' failed

[Maximiliano Curia]

Control: severity -1 important

¡Hola Chris!

El 2016-11-29 a las 16:33 +0100, Chris Lamb escribió:
Source: kf5-kdepim-apps-libs 
Version: 4:16.04.2-2 
Severity: serious 
Justification: fails to build from source 
User: reproducible-bui...@lists.alioth.debian.org 
Usertags: ftbfs 
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org


This should have been fixed with the upload of gpgmepp 16.04.3-2, but since we 
are planning to remove gpgmepp in favor of the c++ interfaces provided in 
gpgme1.0 for stretch, we still need to work on this package.


Happy hacking.
--
"By definition, when you are investigating the unknown, you do not know what
you will find"
-- The Ultimate Principle
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#847064: KGPG does not start

[Maximiliano Curia]

Control: tag -1 + unreproducible moreinfo
Control: severity -1 normal

¡Hola Karsten!

About the subject, if your kgpg is already configured kgpg starts as a 
systemtray icon. Please check that.


El 2016-12-05 a las 10:59 +0100, Karsten Malcher escribió:
Package: kgpg 
Version: 4:4.14.2-1 
Justification: renders package unusable 
Severity: grave


As a general rule, do not set a grave severity without checking that the 
issue is only present for you.



When i try to start KGPG i can see the following messages in the console:


$ kgpg 
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. 
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.


This message isn't important, you can safely ignore it.

Happy hacking,
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are–by
definition–not smart enough to debug it."
-- Brian Kernighan
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#828363: kde4libs: FTBFS with openssl 1.1.0

[Maximiliano Curia]

Control: tag -1 + pending

¡Hola Scott!

El 2016-11-18 a las 20:18 -0500, Scott Kitterman escribió:

On November 18, 2016 7:37:31 PM EST, John Paul Adrian Glaubitz 
 wrote:

Hi!


Would it be possible to change the build dependency from libssl-dev to 
libssl1.0-dev for the time being to temporarily resolve this issue?


It's rather ugly to have a library as central as kde4libs FTBFS because 
it blocks archive rebuilds or the bootstrapping of new architectures.


I think we should wait and see what the release team has to say about the 
transition first.  They are apparently cooking something up.


Currently qt4 is using libssl1.0-dev, so it seems that the only solution is to 
update the build dependencies. I've already fixed this in my local build.


If the release team comes up with some other solution, and qt4 adopts it, we 
might want to update the package again.


Happy hacking,
--
"Any sufficiently advanced technology is indistinguishable from magic."
-- Clarke's Third Law
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#842128: [Pkg-kde-extras] Bug#842128: gammaray: Package uninstallable due to unmet dependancies

[Maximiliano Curia]

¡Hola Jaap!

El 2016-10-26 a las 07:58 +0200, Jaap Keuter escribió:
Source: gammaray 
Severity: serious 
Justification: Policy 7.2


You are trying to install a package from stable using testing to solve it's 
dependencies, that's not going to work. This is not a policy issue (also, 7.2 
is not about archive consistency, afaik).


gammaray was removed from testing, almost a year ago, as part of a qt 
transition. The later uploads haven't build in all the required arches 
needed to migrate from unstable to testing again.


When attempting to install (through aptitude or apt-get) the dependancy to 
the virtual package qtbase-abi-5-3-2 somehow prevents this to complete.


That's working as intended, the gammaray in stable was built against qt 5.3.2, 
and as gammaray uses internal qt parts it will only work with the specific qt 
version it was built against.


If you just want to install gammaray, you can use the version currently in 
unstable. If you want to help gammaray so it's in testing again, please 
consider trying to fix build failures in arm,armhf,mips,mips64el or requesting 
the maintainer to drop gammaray from those architectures.


Happy hacking,
--
"Inside every large problem is a small problem struggling to get out."
-- Hoare's Law of Large Problems
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#840841: [Pkg-kde-extras] Bug#840841: No its no more installable

[Maximiliano Curia]

¡Hola Eric!

El 2016-10-22 a las 12:47 +0200, Eric Valette escribió:
digikam-private-libs : Dépend: libmarblewidget-qt5-24 put now its at 
libmarblewidget-qt5-25


Ups, my fault. Sorry, I forgot about digikam depending on marble libs. The 
package is there, but uninstallable together with marble.


A rebuild should fix this. I'll ask for it.

Happy hacking,
--
"C makes it easy to shoot yourself in the foot; C++ makes it harder,
but when you do it blows your whole leg off."
-- Bjarne Stroustrup
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#838266: Salvaging pylibtiff to Debian Python team or removing it from Debian?

[Maximiliano Curia]

¡Hola Andreas!

El 2016-10-21 a las 09:36 +0200, Andreas Tille escribió:
the former maintainer of pylibtiff inside Debian Med team Mathieu 
Malaterre does not care for the package any more and thus I tried 
my luck to salvage it.  I have no personal interest in this package 
nor does it have any rdepends.  There is no direct connection to 
the Debian Med topic but since there are some users according to 
popcon[1] it might be worth saving.


I won't be able to work on this in the foreseeable future, but I can probably 
help with the mentioned errors.


 File "/usr/lib/python2.7/dist-packages/libtiff/libtiff_ctypes.py", line 36 
   print 'You should add %r to PATH environment variable and reboot.' % (os.path.dirname (lib)) 
^ 
SyntaxError: invalid syntax


This looks valid, but probably fails if using:
from __future__ import print_function
you can probably fix this by adding the parenthesis needed for the function 
invocation:

print('You should add %r to PATH environment variable and reboot.' % 
(os.path.dirname (lib)))

 File "/usr/lib/python2.7/dist-packages/libtiff/optparse_gui.py", line 201 
   print(msg, file=sys.stderr) 
  ^ 
SyntaxError: invalid syntax


This is probably failing because of a missing:
from __future__ import print_function
at the beginning of the file (it needs to be added before any other import).

In python2 print is a statement that you use as print "Hi", in python3 it's a
function that you use as print("Hi"), using the __future__ snippet you can use 
(in python 2.7) print as a function, this is generally a good idea as it eases 
the migration to python3 process.


Happy hacking,
--
"If you have too many special cases, you are doing it wrong." -- Craig Zarouni
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#838303: kde-plasma-desktop: KDE does not start after log in

[Maximiliano Curia]

Control: tag -1 + moreinfo

¡Hola Gabor!

El 2016-09-19 a las 16:33 +0100, Gabor Nagy escribió:
Package: kde-plasma-desktop 
Version: 5:91 
Severity: grave 
Justification: renders package unusable



On the 15th of September I have upgraded some packages


It might be useful to know the list of upgraded packages that broke your 
installation, this information can usually be obtained from the 
/var/log/dpkg.log* files.



  * What was the outcome of this action?


Next time when I started this computer, after the sddm login screen when I 
successfully log in, I can see a KDE loading splash screen as expected, but 
after the spalsh screen I see only a blank black screen, with the mouse pointer 
on the left edge. I can move the pointer up and down, but it doesn't move 
horizontally.


From this I would think that this could be a kscreen issue. There are some 
fixes in kscreen included in the plasma 5.8 release (in particular 
https://bugs.kde.org/show_bug.cgi?id=366067), it should be worth checking if 
upgrading your kde installation to plasma 5.8 fixes your desktop.


ii  plasma-desktop4:5.6.5-1 
ii  plasma-workspace  4:5.6.5.1-1 
ii  kwin-x11  4:5.7.0-1 


You had some mixed versions of plasma, given the plugins nature of some plasma 
parts mixing different versions is highly disrecommended, this should be 
prevented with the new packages.


Happy hacking,
--
"Executive ability is deciding quickly and getting somebody else to do the
work."
-- Pollard's Postulate
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#832649: multi-display is broken (menu and panel appears only on external display)

[Maximiliano Curia]

¡Hola Pirate!

El 2016-09-06 a las 12:52 +0530, Pirate Praveen escribió:
That might be related, sadly, while it claims that's fixed for 5.8, it 
doesn't point to the corresponding commits, so we can only wait for 5.8.


Lets hope that fixes it.


plasma 5.8.2 should be available in archive now. Is this bug still 
reproducible for you with it?



--
Se necesitan voluntarios para dominar el mundo.
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#840692: [pkg-cinnamon] Bug#840692: nemo-python: plugin is not recognized or loaded by Nemo

[Maximiliano Curia]

Control: tag -1 + unreproducible
Control: severity -1 normal

¡Hola Nathan!

El 2016-10-13 a las 15:25 -0700, Nathan Osman escribió:
Package: nemo-python 
Version: 3.0.0-3 
Severity: grave 
Justification: renders package unusable


The nemo-python extension is not displayed in the "Extensions" list under 
Edit->Plugins. This is further confirmed by the fact that none of the Python 
extensions I have installed work. Running Nemo under KDE, Gnome, and Cinnamon 
doesn't appear to make any difference.


The libnemo-python extension provides a meta extension that allows other 
extensions to be written in python, and as such it's not listed in nemo as an 
individual extension.


Using the provided examples (located in /usr/share/doc/nemo-python/examples/) 
it works fine. Please try testing it with these, the 
/usr/share/doc/nemo-python/examples/README file explains how to 
install this test extensions.


Happy hacking,
--
"It is not the task of the University to offer what society asks for, but to
give what society needs."
-- Edsger W. Dijkstra
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#839710: plasma-workspace: Comic Plasma Widget causes black screen, restart X necessary

[Maximiliano Curia]

Control: severity -1 important
Control: tag -1 + confirmed upstream
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=370194

¡Hola Maria!

El 2016-10-04 a las 10:55 +0200, Maria escribió:
Package: plasma-workspace 
Version: 4:5.7.4-1 


The bug is also reproducible in plasma 5.8.0.

Severity: critical 
Justification: breaks unrelated software


I think that the critical severity is an bit too much. But this definitely 
needs to be discussed with upstream. A plasmoid shouldn't cause plasmashell to 
crash.



Dear Maintainer,


Step 1: place Comic Widget on your Desktop 
Step 2: install PhD Comics 
Step 3: by today (04.10.2016) go 9 steps back (to the previous comics) 


For the record the "evil" comic is: 
http://phdcomics.com/comics/archive.php?comicid=1889


I'm not sure if this is caused by the multiple images, the video link or some 
different parsing error.


Result: Complete black screen, only possibillity to escape is killing X with 
Ctrl-Alt-Backspace


When this happens you can restart plasmashell with krunner (Alt+Space is the 
default shortcut).


Also kwin and all the other applications should still be working, so you can 
save your work, switch between windows, etc, if you decide to restart your 
session.



Reproducible: always



Expected behaviour:
I expect the Widget to not allow an installed Comic to break my system, however 
bad/corrupt it might be build.


I am sorry if I categorized this Bug report in the wrong section, but as I had 
to kill my actual session (which in many circumstances can cause serious data 
loss) I've put it in this category.


This needs to be discussed upstream. I've forwarded the plasmashell issue, 
which I think it's the real issue here, to:

https://bugs.kde.org/show_bug.cgi?id=370194

If you consider the plasmoid issue to be important enough, please forward that 
bug upstream as well.


Happy hacking,
--
"Any change looks terrible at first." -- Principle of Design Inertia
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#832649: multi-display is broken (menu and panel appears only on external display)

[Maximiliano Curia]

Control: reassign -1 kscreen 4:5.7.0-1
Control: tag -1 + unreproducible moreinfo

¡Hola Pirate!

El 2016-07-28 a las 11:31 +0530, Pirate Praveen escribió:
package: systemsettings 
version: 4:5.7.0-1 
severity: grave


I have connected an HDMI monitor to my laptop and the menu and panel 
appears on the HDMI monitor, but when I remove the HDMI cable, the menu 
and panel does not appear on the laptop screen.


I have to use run command and alt tab as a fallback. But I miss 
notifications, especially the power status and network status.


This should be handled by kscreen, so I'm reassigning the issue. I can't 
reproduce the issue here (with an Intel HD Graphics 3000), I'm not sure if 
this is somehow fixed in 5.7.4 or it was caused by something external 
(hardware or dependency). Is the issue still reproducible using kscreen 5.7.4?

What shows the xrandr output before and after unplugging the hdmi cable?

Searching in the upstream bugs I found this one:
https://bugs.kde.org/show_bug.cgi?id=366067

That might be related, sadly, while it claims that's fixed for 5.8, it doesn't 
point to the corresponding commits, so we can only wait for 5.8.


Happy hacking,
--
"It is practically impossible to teach good programming to students that have
had a prior exposure to BASIC: as potential programmers they are mentally
mutilated beyond hope of regeneration."
-- Edsger W. Dijkstra
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#834401: sddm cannot set per user desktop choices

[Maximiliano Curia]

Control: severity -1 normal

¡Hola Pirate!

El 2016-08-15 a las 14:24 +0530, Pirate Praveen escribió:
package: sddm 
version: 0.13.0-1 
severity: grave


Sorry, this is bug alright, it's annoying, but still, it's a bug, it doesn't 
merit a grave severity.


I have two users in my system and when using sddm, each user has to 
select their preferred desktop session **EVERY** single time. One user 
wants KDE/Plasma and another GNOME. When first users selects GNOME and 
logout, the second user also gets GNOME, even when they have selected 
KDE/Plasma as their preferred session in previous login.


As a workaround you could use the .xsession script to start the desired 
session to each user.


Happy hacking,
--
"Nothing ever goes away." -- Commoner's Law of Ecology
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#833625: Request for fixing

[Maximiliano Curia]

¡Hola Garrett!

El 2016-09-03 a las 19:32 -0400, Garrett Kajmowicz escribió:
Can we get some traction on this issue. I'm having the exact same problem. 
However, I don't want to delete my SQLITE databases because they contain any 
additional annotations and tags that I've added. I would expect a software 
version upgrade to handle this transparently.


Ideally, you should be able to dump the sqlite data (unless the database can't 
be opened anymore, which I don't think it's the case), move the old database 
away, generate a new one starting akonadi, and load the data back.


If the issue is produced by the akonadi upgrade, having a way to reproduce the 
issue (as minimal as possible) should help.

Something along the lines:
Initial environment:
 - Starting a new vm from foobar.
 - Running the akonadi, kmail, and such as such packages from the snapshot [1] 
version X (or from jessie)

Working configuration:
 - Setting up sqlite
 - Configuring kmail2

 * Everything works
   - Backup the database for future checks

Upgrade:
 - Upgrading only such and such packages to version X, Y

 * Results in a database corruption
   - Backup the database for further debugging

Test restoring the old database:
 - ...

Test deleting the database:
 - ...

Test new user:
 - Setting up sqlite
 - Configuring kmail2

 * Everything works
   - Backup database for further debugging

Could you try to produce such a recipe for reproducing the issue and report 
the issue upstream?


Happy hacking,
[1] http://snapshot.debian.org/
--
"If I ask another professor what he teaches in the introductory programming
course, whether he answers proudly "Pascal" or diffidently "FORTRAN," I know
that he is teaching a grammar, a set of semantic rules, and some finished
algorithms, leaving the students to discover, on their own, some process of
design."
-- Robert W. Floyd
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#836011: akregator: Akregator keep crashing at exit, sometimes do not save recent feeds

[Maximiliano Curia]

Control: tag -1 + pending

¡Hola Sandro!

El 2016-09-02 a las 08:51 +0200, Sandro Knauß escribió:

Control: tags -1 +patch



thanks, for the backtrace. This helps to track this down.


I can reproduce this, but currently I can't test the patch for it. But this 
only happens if akregator is started as single application. My normal way to 
use akregator is via kontact and this way it does not crash.


I looks that we have to test the partenNode if this is a valid 
pointer.Akregator::SubscriptionListModel::index



Akregator::SubscriptionListModel::index



add this add line 248:
   if (!parentNode) { 
   return QModelIndex(); 
   }


Oh, I had came up with the same patch. :)
I could finally test this, and the patch fixes the segfault. Could you push 
this upstream (for 16.08.1, I guess)?


Happy hacking
--
"There are only two things wrong with C++: The initial concept and the
implementation."
-- Bertrand Meyer
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#836011: akregator: Akregator keep crashing at exit, sometimes do not save recent feeds

[Maximiliano Curia]

¡Hola Ismael!

El 2016-08-30 a las 01:13 -0300, Ismael escribió:
Package: akregator 
Version: 4:16.04.3-1 
Severity: grave 
Justification: causes non-serious data loss



  * What led up to the situation?


Since a recent upgrade (less than a month ago). After reading a feed when 
closing Akregator it will crash without saving feeds state. The next time it 
will load like it didn't fetch any feed.


  * What exactly did you do (or not do) that was effective (or 
ineffective)?


If I remaing in the welcome page I can synchronize without problems, and 
Akregator will close correctly.


But If I read a post from a feed or load the list of post in a folder. It will 
crash when closing Akregator.



  * What was the outcome of this action?



Run under gdb generates the following stack trace


#0  0x7fffd4079f48 in Akregator::SubscriptionListModel::index(int, int, 
QModelIndex const&) const () 
  from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so 
#1  0x75dac951 in QTreeView::isRowHidden(int, QModelIndex const&) const 
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 


Thanks for the report. I can't reproduce the issue here, and sadly the gdb 
output sent doesn't have enough debugging information. Could you please 
install akregator-dbgsym, and qtbase5-dbg and run it under gdb again?


The -dbgsym packages are in separated repositories, so you'll probably need to 
add:
deb http://debug.mirrors.debian.org/debian-debug unstable-debug main
to your sources.list. (For more information [1])

Also, kde applications are heavily threaded so you'll need to ask gdb to 
produce a backtrace for each thread, this can be achieved with:

(gdb) thread apply all backtrace
(For more information [2])

Happy hacking,
[1]: https://wiki.debian.org/AutomaticDebugPackages
[2]: 
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
--
"EIEIO Go home and have a glass of warm, dairy-fresh milk"
-- The GNU C Library Reference Manual, Chapter 2.2, Error Codes
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#834273: kmailtransport: FTBFS in testing

[Maximiliano Curia]

¡Hola Santiago!

El 2016-08-14 a las 02:24 +0200, Santiago Vila escribió:
Package: src:kmailtransport 
Version: 16.04.2-2 
Severity: serious



This package currently fails to build from source in stretch:
-- 
cd /build/kmailtransport-16.04.2/obj-x86_64-linux-gnu/src && /usr/bin/c++   -DKCOREADDONS_LIB -DKF5MailTransport_EXPORTS -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_DISABLE_DEPRECATED_BEFORE=0 -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_DEBUG -DQT_NO_URL_CAST_FROM_STRING -DQT_USE_FAST_OPERATOR_PLUS -DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB -DQT_XML_LIB -DTRANSLATION_DOMAIN=\"libmailtransport5\" -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/build/kmailtransport-16.04.2/obj-x86_64-linux-gnu/src -I/build/kmailtransport-16.04.2/src -isystem /usr/include/KF5/KWallet -isystem /usr/include/KF5 -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -isystem /usr/include/KF5/AkonadiCore -isystem /usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KItemModels -isystem /usr/include/KF5/KMime -isystem /usr/include/KF5/Akonadi/KMime -isystem /usr 
/include/KF5/akonadi/kmime -isystem /usr/include/KF5/KI18n -isystem /usr/include/KF5/KIOCore -isystem /usr/include/KF5/KService -isystem /usr/include/KF5/KConfigCore -isystem /usr/include/KF5/KConfigGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem /usr/include/KF5/KWidgetsAddons -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KCodecs -isystem /usr/include/KF5/KAuth -isystem /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/KF5/KCompletion  -g -O2 -fdebug-prefix-map=/build/kmailtransport-16.04.2=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2  -std=c++0x -fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -pedantic -fPIC -fvisibility=hid 
den -fvisibility-inlines-hidden   -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -fPIC -fexceptions -o CMakeFiles/KF5MailTransport.dir/resourcesendjob.cpp.o -c /build/kmailtransport-16.04.2/src/resourcesendjob.cpp 
In file included from /usr/include/KF5/AkonadiCore/exception.h:28:0, 
from /usr/include/KF5/AkonadiCore/item.h:26, 
from /build/kmailtransport-16.04.2/src/filteractionjob_p.h:25, 
from /build/kmailtransport-16.04.2/src/outboxactions_p.h:24, 
from /build/kmailtransport-16.04.2/src/outboxactions.cpp:20:
/usr/include/KF5/AkonadiCore/std_exception.h:1:40: fatal error: /usr/include/c++/5/exception: No such file or directory 
#include "/usr/include/c++/5/exception" 
   ^ 
compilation terminated. 
--


This issue is caused by akonadi, and the migration to g++-6, the file 
/usr/include/KF5/AkonadiCore/std_exception.h is generated and includes the 
mentioned full path (/usr/include/c++/5/exception or 
/usr/include/c++/6/exception), which is a bad idea (tm)...


I've uploaded new version of akonadi that will be compiled against g++-6, and 
this issue will be solved when akonadi migrates to stretch. If I have the time, 
I would like to fix the generated std_exception.h so this is not a problem in 
future g++ upgrades.



There are full logs available here:



https://tests.reproducible-builds.org/debian/rb-pkg/testing/amd64/kmailtransport.html


Happy hacking,
--
"Brilliant opportunities are cleverly disguised as insolvable problems."
-- Gardener's Philosophy
"The reverse is also true." -- Corollary
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#833625: kmail crash at start

[Maximiliano Curia]

¡Hola Samuele!

El 2016-08-11 a las 20:46 +0200, Samuele Battarra escribió:

On Tuesday 09 August 2016 10:19:56 Maximiliano Curia wrote:
I was expecting kcrash to catch a kmail crash and show a window with the 
backtrace information, if that's not the case, then running kmail under gdb 
should give something similar:


No kcrash, here the gdb log. 
After some run the message error changed, now it is:
konadicore_log: Failed CollectionCreateJob. "Could not create collection 
templates, resourceId: 2" 
repeated for every folder, see attachment


Thanks for the information.

Sadly to have an idea of the code error we still need more debug symbols. 
Could you produce the backtrace again after installing qtbase5-dbg , 
libkf5mailcommon5-dbgsym and kde-style-breeze-dbgsym ?


Database "/home/samuele/.local/share/akonadi/akonadi.db" opened using driver "QSQLITE3" 


Please be aware that the sqlite support hasn't been the most cared for 
upstream for quite some long time now.


> DATABASE ERROR:
> Error code: 2067
> DB error:  "UNIQUE constraint failed: CollectionTable.parentId, 
CollectionTable.name"
> Error text: "UNIQUE constraint failed: CollectionTable.parentId, 
CollectionTable.name Unable to fetch row"
> Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, 
resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, 
cachePolicyCheckInterval, cachePolicyCacheTimeout, cachePolicySyncOnDemand, 
cachePolicyLocalParts, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10, :11, 
:12, :13, :14)"
> Error during insertion into table "CollectionTable" "UNIQUE constraint failed: 
CollectionTable.parentId, CollectionTable.name Unable to fetch row"
> akonadicore_log: Failed SpecialCollectionsRequestJob::slotResult "Could not create 
collection outbox, resourceId: 2"
> log_maildispatcher: Failed to get outbox folder. Retrying in:  5000
> akonadicore_log: Failed CollectionCreateJob. "Could not create collection outbox, 
resourceId: 2"
> QDBusObjectPath Akonadi::Server::NotificationManager::subscribe(const QString&, bool) 
Akonadi::Server::NotificationManager(0x801dd0) "akonadi_mailfilter_agent_6555_8m4kX2" 
false
> DATABASE ERROR:
> Error code: 2067
> DB error:  "UNIQUE constraint failed: CollectionTable.parentId, 
CollectionTable.name"
> Error text: "UNIQUE constraint failed: CollectionTable.parentId, 
CollectionTable.name Unable to fetch row"
> Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, 
resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, 
cachePolicyCheckInterval, cachePolicyCacheTimeout, cachePolicySyncOnDemand, 
cachePolicyLocalParts, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10, :11, 
:12, :13, :14)"
> Error during insertion into table "CollectionTable" "UNIQUE constraint failed: 
CollectionTable.parentId, CollectionTable.name Unable to fetch row"

(mostly speaking to myself)

And the database seems to be corrupted somehow. Maybe the schema update from 
the previous version failed, maybe it was already corrupted in a way that 
wasn't affecting kmail before. This is going to be very hard to figure out.


> log_pop3resource: Got a slave error: "Your POP3 server claims to support TLS but 
negotiation was unsuccessful.\nYou can disable TLS in the POP account settings dialog."
> log_pop3resource: == ERROR DURING POP3 SYNC 
==
> log_pop3resource: "Unable to login to the server localhost.\nYour POP3 server 
claims to support TLS but negotiation was unsuccessful.\nYou can disable TLS in the POP 
account settings dialog."
> log_pop3resource: UID list from server is not valid.
> [Thread 0x7fff357f9700 (LWP 6839) exited]
> Shutting down "/subscriber/kmail2_6510_5GV1Hh" ...
> [Thread 0x7fff6a904700 (LWP 6784) exited]
> [Thread 0x7fffd2afe700 (LWP 6515) exited]
> void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) 
Notification source "kmail2_6510_NKaXvq" now serving: ()
> void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) 
Notification source "kmail2_6510_JUYr6i" now serving: ()
> void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) 
Notification source "kmail2_6510_JHAa4N" now serving: ()
> void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) 
Notification source "kmail2_6510_pb3V52" now serving: ()
> void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) 
Notification source "kmail2_6510_5GV1Hh" now serving: ()
> void Akonadi::Server::NotificationSource::serviceUnregistered(const 

Bug#833625: kmail crash at start

[Maximiliano Curia]

¡Hola Samuele!

El 2016-08-09 a las 09:25 +0200, Samuele Battarra escribió:
Package: kmail 
Version: 4:16.04.3-1 
Followup-For: Bug #833625


Have you closed your plasma session after upgrading kmail and akonadi? 

I have rebooted my pc, kmail still crashes.


please install the additional dbgsym packages ... 
Installed kmail-dbgsym, other packages? 
Where i can find logs? 
You can send me privately info how to get debug logs?


I was expecting kcrash to catch a kmail crash and show a window with the 
backtrace information, if that's not the case, then running kmail under gdb 
should give something similar:


$ gdb kmail
[ ... ]
(gdb) r
[ ... Wait for the crash ... ]
(gdb) thread apply all backtrace

This is better explained in: 
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports


Happy hacking,
--
Se necesitan voluntarios para dominar el mundo.
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#814762: kmail: CSS from HTML mail interfers with header layout

[Maximiliano Curia]

Control: severity -1 important

¡Hola Dominik!

El 2016-07-24 a las 22:11 +0200, Dominik George escribió:
Package: kmail 
Version: 4:16.04.3-1 
Followup-For: Bug #814762


It got worse. Today, I stumbled about a legitimate HTML mail that just 
trashed the whole UI.



Find attached the mail that caused the issue and a screenshot.


Raising severity to grave. Please do something! Firstly, I am certain 
this is a security-relevant bug; secondly, it now makes stuff break in 
daily use.


I'm temporarily lowering the severity of this mail to finish the kdepim 16.04 
transition.


Also, I think that this issue should be easily reproduceable in the older 
kmail2 versions, thus I see no reason to block the transition by this.


Even more, a mail header can be "spoofed" using simpler tools, like an smtp 
server, thus I'm not really convinced that this bug deserves a "grave" 
severity.


Happy hacking,
--
"There are only two things wrong with C++: The initial concept and the
implementation."
-- Bertrand Meyer
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#831759: backup-manager: FTBFS: Running test t15-dupes.sh: failed

[Maximiliano Curia]

Control: tag -1 + unreproducible moreinfo
Control: severity -1 important

On Tuesday, 19 July 2016 09:04:35 CEST Chris Lamb wrote:
> Source: backup-manager
> Version: 0.7.12-1
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
 
> backup-manager fails to build from source in unstable/amd64:

>   [t 16] Running test t15-dupes.sh: failed

Sorry, but I can't reproduce the error. Maybe there is some difference in the 
running environment. Can you test the failling test with set -x ?

Happy hacking,
-- 
"If you optimize everything, you will always be unhappy."
-- Donald Knuth
Saludos /\/\ /\ >< `/


signature.asc
Description: This is a digitally signed message part.

Bug#818810: FTBFS with libc 2.23: 'isnan' was not declared in this scope

[Maximiliano Curia]

Version: 4:16.04.1-1

¡Hola Martin!

El 2016-03-20 a las 16:02 -0400, Martin Michlmayr escribió:
Package: kmplot 
Version: 4:15.08.3-1 
Severity: important 
User: debian-gl...@lists.debian.org 
Usertags: 2.23


This package fails to build with libc6 2.23 (2.23-0experimental0 from 
experimental).


sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux 
... 

In file included from /<>/kmplot/kgradientdialog.cpp:27:0:
/usr/include/KF5/KDELibs4Support/kcolordialog.h:211:41: note: declared here 
 class KDELIBS4SUPPORT_DEPRECATED_EXPORT KColorDialog : public KDialog 
 ^ 
/<>/kmplot/view.cpp: In member function 'QPointF View::toPixel(const QPointF&, View::ClipBehaviour, const QPointF&)':
/<>/kmplot/view.cpp:479:14: error: 'isnan' was not declared in this scope 
  if ( isnan(x) ) 



/<>/kmplot/view.cpp:479:14: note: suggested alternative:
In file included from /usr/include/c++/5/random:38:0, 
 from /usr/include/c++/5/bits/stl_algo.h:66, 
 from /usr/include/c++/5/algorithm:62, 
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:85, 
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:37, 
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:37, 
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/QVector:1, 
 from /<>/kmplot/vector.h:28, 
 from /<>/kmplot/function.h:29, 
 from /<>/kmplot/view.h:29, 
 from /<>/kmplot/view.cpp:26:
/usr/include/c++/5/cmath:641:5: note:   'std::isnan' 
 isnan(_Tp __x) 
 ^ 
/<>/kmplot/view.cpp:499:15: error: 'isinf' was not declared in this scope 
   if ( isinf(x) == -1 ) 
   ^ 
/<>/kmplot/view.cpp:499:15: note: suggested alternative:
In file included from /usr/include/c++/5/random:38:0, 
 from /usr/include/c++/5/bits/stl_algo.h:66, 
 from /usr/include/c++/5/algorithm:62, 
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:85, 
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:37, 
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:37, 
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/QVector:1, 
 from /<>/kmplot/vector.h:28, 
 from /<>/kmplot/function.h:29, 
 from /<>/kmplot/view.h:29, 
 from /<>/kmplot/view.cpp:26:
/usr/include/c++/5/cmath:621:5: note:   'std::isinf' 
 isinf(_Tp __x) 
 ^ 
/<>/kmplot/view.cpp:506:14: error: 'isnan' was not declared in this scope 
  if ( isnan(y) ) 
  ^ 
/<>/kmplot/view.cpp:506:14: note: suggested alternative:
In file included from /usr/include/c++/5/random:38:0, 
 from /usr/include/c++/5/bits/stl_algo.h:66, 
 from /usr/include/c++/5/algorithm:62, 
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:85, 
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:37, 
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:37, 
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/QVector:1, 
 from /<>/kmplot/vector.h:28, 
 from /<>/kmplot/function.h:29, 
 from /<>/kmplot/view.h:29, 
 from /<>/kmplot/view.cpp:26:
/usr/include/c++/5/cmath:641:5: note:   'std::isnan' 
 isnan(_Tp __x) 
 ^ 
/<>/kmplot/view.cpp:526:15: error: 'isinf' was not declared in this scope 
   if ( isinf(y) == -1 ) 
   ^ 


This was fixed upstream in 16.03.80, thus fixed in the 4:16.04.1-1 Debian 
package.


Happy hacking,
--
"If you optimize everything, you will always be unhappy."
-- Donald Knuth
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#830990: baloo: Build-Depends on cruft package libakonadi-dev

[Maximiliano Curia]

¡Hola Daniel!

El 2016-07-13 a las 08:10 -0700, Daniel Schepler escribió:
Source: baloo 
Version: 4:4.14.2-2 
Severity: serious


The baloo source package Build-Depends on libakonadi-dev, which is 
only available in sid from older versions of src:akonadi than the 
latest one. 


Ups, I forgot to upload src:akonadi4 to unstable, that is currently only in 
experimental. Uploading it now.


Happy hacking,
--
“First, solve the problem. Then, write the code.” -- John Johnson
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#830763: akonadiconsole: crashes hard

[Maximiliano Curia]

¡Hola Thorsten!

El 2016-07-11 a las 10:46 +0200, Thorsten Glaser escribió:
Package: akonadiconsole 
Version: 4:4.14.10-2 
Severity: serious 
Justification: makes the package unusable


While trying to debug #830762 (to see if the new messages are in fact 
downloaded) I tried to start akonadiconsole, with, well, limited success:


Once again, please upgrade akonadiconsole to 4:16.04.2-2. I'll add the kmail, 
korganizer and akonadiconsole breaks to new akonadi-server.


Happy hacking,
--
"If a pickpocket meets a saint, he sees only his pockets."
-- Kegley's Law
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#830762: kmail: empty folders list

[Maximiliano Curia]

¡Hola Thorsten!

El 2016-07-11 a las 10:43 +0200, Thorsten Glaser escribió:
Package: kmail 
Version: 4:4.14.10-2 
Severity: serious 
Justification: makes the package unusable


After the recent KDEPIM-related updates (including involving a wallet 
migration, which seems to have worked, and a reboot, so the last traces 
of old Akonadi/KDEPIM are gone from the process table), parts of Kontact 
stop working altogether.


You haven't upgraded kmail, so it seems that you haven't a fully upgraded 
kdepim. Make sure that you have the version 4:16.04.2-2 installed.


The same happens for the Calendar component – the bottom-left part which 
normally holds the various calendars and their colours is empty.


Similarly, korganizer also needs to be upgraded to 4:16.04.2-2.

Interestingly enough, the Feeds component not only works but shows very 
up-to-date content (as of this morning), so it’s not a general Kontact 
problem.


That's akregator.

Happy hacking,
--
"EIEIO Go home and have a glass of warm, dairy-fresh milk"
-- The GNU C Library Reference Manual, Chapter 2.2, Error Codes
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#821686: PHP packages for libkolab

[Maximiliano Curia]

I'll fix that in the next upload

On July 8, 2016 11:51:32 AM GMT+02:00, "Sandro Knauß"  
wrote:
>Hey,
>
>I saw that you pushed libkolab 1.0 to unstable but you introduced the
>php 
>bindings again. I think you overlooked the NMU (0.6.0-3.1) made by
>Ondřej Surý 
>  had removed the php bindings for libkolab, because
>swig 
>isn't ready for php7.0 (see #821715). As far as I understand swig now
>don't 
>create php bindings anymore for the moment.
>
>Regards,
>
>sandro

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

Bug#828114: kdewebdev: FTBFS: src/tidy/tidyx.h:52:20: fatal error: buffio.h: No such file or directory

[Maximiliano Curia]

Control: reassign -1 libtidy-dev 1:5.2.0-1
Control: merge -1 827891
Control: affects -1 + kdewebdev

On Saturday, 25 June 2016 09:32:04 CEST Chris Lamb wrote:
> Source: kdewebdev
> Version: 4:15.08.3-2
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

> kdewebdev fails to build from source in unstable/amd64:

Till #827891 is fixed I would expect ftbfs's in all the libtidy-dev reverse 
dependencies.

Happy hacking,
-- 
"Good judgement comes from experience, and experience comes from bad
judgement."
-- Fred Brooks
Saludos /\/\ /\ >< `/

Bug#827724: closed by Andreas Metzler <ametz...@debian.org> (Bug#827724: fixed in findutils 4.6.0+git+20160517-4)

[Maximiliano Curia]

¡Hola!

El 2016-06-20 a las 18:36 +, Debian Bug Tracking System escribió:
This is an automatic notification regarding your Bug report 
which was filed against the findutils package:


#827724: findutils: find -type f matches symlinks in armel armhf and mipsel

It has been closed by Andreas Metzler .


As I mentioned in my previous mail, findutils also fails to build from source 
due to this issue, so it's now failing in armel, armhf, mipsel and hurd-i386. 
:(


Are you planning to do a binary only upload for these arches?

Alternatively, adding:
override_dh_md5sums:
   PATH="$$(pwd)/find:$$PATH" dh_md5sums

To the debian/rules file would allow the build to finish successfully.

Happy hacking,
--
"There are two major products that come out of Berkeley: LSD and BSD.
We don't believe this to be a coincidence."
-- Jeremy S. Anderson
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#827724: findutils: find -type f matches symlinks in armel armhf and mipsel

[Maximiliano Curia]

Control: tag -1 + patch
¡Hola!

El 2016-06-20 a las 10:58 +0200, Maximiliano Curia escribió:
Package: findutils 
Version: 4.6.0+git+20160126-3 
Severity: critical 
Justification: breaks unrelated software


The new version of find has a weird behaviour, at least in the arches: armhf armel and mipsel. 
As simple test:


dir=$(mktemp -d) 
cd $dir 
ln -s a b 
find -type f



Shows ./b while it shouldn't.



Interestingly:
$ find -type l 
find: Duplicate file type 'l' in the argument list to -type



Both examples work fine in amd64.


I haven't followed the code thoroughly, but it seems that the type is using a 
float to hold a bit mask, maybe this is not so well behaved in all arches.


This breaks dh_md5summs in the mentioned arches, producing a number of 
ftbfs's, and probably many other things, thus the severity.


With the addition of multiple types in one -type option, the args union of the 
predicate struct has grown and the new space is not being initialized.
(The initialization of args is done as a args.str = NULL, but args.types is a 
bool types[FTYPE_COUNT]; with count being 8, that's 32 bytes vs 4 that are 
currently initialized in a 32 bits arch.


Replacing the xmalloc invocation by a xzalloc one "fixes" the issue as it 
initializes all of the predicate components.


I'm attaching a patch that does this.

Sadly, findutils also fails to build from source due this findutils issue, 
so the build should be done either against an older version of findutils or 
tweak the PATH so that debhelper uses the recently built find.


P.S. After following the code I noticed that the rate variable wasn't used as a 
bitmask sorry for the confussion, a comment in the code lead me to think that 
it was.


--
"It is practically impossible to teach good programming to students that have
had a prior exposure to BASIC: as potential programmers they are mentally
mutilated beyond hope of regeneration."
-- Edsger W. Dijkstra
Saludos /\/\ /\ >< `/
Description: Replace xmalloc with xzalloc
Author: Maximiliano Curia <m...@debian.org>

--- findutils-4.6.0+git+20160517.orig/find/tree.c
+++ findutils-4.6.0+git+20160517/find/tree.c
@@ -865,7 +865,7 @@ set_new_parent (struct predicate *curr,
 {
   struct predicate *new_parent;
 
-  new_parent = xmalloc (sizeof (struct predicate));
+  new_parent = xzalloc (sizeof (struct predicate));
   new_parent->p_type = BI_OP;
   new_parent->p_prec = high_prec;
   new_parent->need_stat = false;
@@ -1491,12 +1491,12 @@ get_new_pred (const struct parser_table
   if (predicates == NULL)
 {
   predicates = (struct predicate *)
-	xmalloc (sizeof (struct predicate));
+	xzalloc (sizeof (struct predicate));
   last_pred = predicates;
 }
   else
 {
-  new_pred = xmalloc (sizeof (struct predicate));
+  new_pred = xzalloc (sizeof (struct predicate));
   last_pred->pred_next = new_pred;
   last_pred = new_pred;
 }


signature.asc
Description: Digital signature

Bug#827724: findutils: find -type f matches symlinks in armel armhf and mipsel

[Maximiliano Curia]

Package: findutils
Version: 4.6.0+git+20160126-3
Severity: critical
Justification: breaks unrelated software

Hi,

The new version of find has a weird behaviour, at least in the arches: armhf 
armel and mipsel.
As simple test:

dir=$(mktemp -d)
cd $dir
ln -s a b
find -type f

Shows ./b while it shouldn't.

Interestingly:
$ find -type l
find: Duplicate file type 'l' in the argument list to -type

Both examples work fine in amd64.

I haven't followed the code thoroughly, but it seems that the type is using a 
float to hold a bit mask, maybe this is not so well behaved in all arches.

This breaks dh_md5summs in the mentioned arches, producing a number of 
ftbfs's, and probably many other things, thus the severity.

Happy hacking,
-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

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

Versions of packages findutils depends on:
ii  libc62.22-11
ii  libselinux1  2.5-3

findutils recommends no packages.

Versions of packages findutils suggests:
ii  mlocate  0.26-1

-- no debconf information

Bug#826599: kdepim-runtime depends and build-depends on packages that are no longer built.

[Maximiliano Curia]

Control: reassign -1 kdepim-runtime 4:4.14.10-2
Control: tag -1 pending

¡Hola peter!

El 2016-06-06 a las 20:34 +0100, peter green escribió:
package: kdepim-runtime 
severity: serious 
version: 2.2.0-2


The version seems to be the one for libkgapi2-2, but you are reporting it to 
kdepim-runtime.


Even though libkgapi is the offending package here, this will be solved with 
the upload of kdepim-runtime and kdepim.


kdepim-runtime depends on libkgapi2-2 and build-depends on 
libkgapi-dev . These packages were previously built by the source 
package libkgapi but are no longer built.


There is a pending transition for this, that will be completed when kdepim 
enters unstable.

https://release.debian.org/transitions/html/auto-libkgapi.html

This was noted via irc by a release team member and we agreed that 
this could wait for now. At least if it's not breaking anything right now, 
I could upload a src:libkgapi2 if the current state is really affecting 
anything.


This appears to be fixed in the version in experimental, maybe it's 
time to upload that to sid?


Not yet, we still need a few more packages that need to go through the NEW
queue.

Happy hacking,
--
"Seek simplicity, and distrust it." -- Whitehead's Rule
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#801308: umbrello: Can't save to file - "UMLDoc::saveDocument moving with error"

[Maximiliano Curia]

Control: tag -1 + pending

¡Hola Grégory!

Sorry for replying earliear.

El 2015-10-08 a las 13:18 +0200, Grégory DAVID escribió:
Package: umbrello 
Version: 4:15.08.1-1 
Severity: grave 
Justification: renders package unusable


  * What led up to the situation? 
After starting the application umbrello, even if there's or not some content in the diagram, saving file shows up a dialog box saying: "There was a problem saving file: /path/to/the/file/to/be/saved


  * What exactly did you do (or not do) that was effective (or 
ineffective)? 
Starting umbrello in CLI to see log messages and see the error as:
  klauncher not running... launching kdeinit 
  klauncher not running... launching kdeinit 
  klauncher not running... launching kdeinit 
  couldn't create slave: "Cannot talk to klauncher: The name org.kde.klauncher5 was not provided by any .service files" 
  umbrello: UMLDoc::saveDocument moving with error =  "/tmp/umbrello.X20558"  to   QUrl( "file:///home/groolot/file.xmi" )


It seems that you don't have kinit installed, I'm adding it as an umbrello 
dependency, it should be there in the next upload.



Happy hacking,
--
"A computer program does what you tell it to do, not what you want it to do."
-- Greer's Law
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#807067: konsole makes kde freeze

[Maximiliano Curia]

Control: tag -1 unreproducible moreinfo
Control: severity -1 important

¡Hola Cosimo!

El 2015-12-04 a las 21:52 +0100, Cosimo Morelli escribió:
Package: konsole 
Version: 4:15.08.2-1 
Severity: critical 
Justification: breaks the whole system



I open konsole after login



## MY .xsession-errors ##
kdeinit5: Got EXT_EXEC '/usr/bin/konsole' from launcher. 
kdeinit5: preparing to launch '/usr/bin/konsole' 
QXcbConnection: XCB error: 3 (BadWindow), sequence: 43664, resource id:
27262977, major code: 18 (ChangeProperty), minor code: 0 
QCoreApplication::arguments: Please instantiate the QApplication object first 
QDBusConnection: session D-Bus connection created before QCoreApplication. 
Application may misbehave. 
QDBusConnection: session D-Bus connection created before QCoreApplication. 
Application may misbehave. 
kdeinit5: PID 2517 terminated. 
Application::crashHandler() called with signal 11; recent crashes: 1 
KCrash: crashing... crashRecursionCounter = 2 
KCrash: Application Name = kwin_x11 path = /usr/bin pid = 1578 
KCrash: Arguments: /usr/bin/kwin_x11 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from 
kdeinit 
kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/libexec/drkonqi' from 
wrapper. 
kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/drkonqi' 
kcm_keyboard: configuring layouts false configuring options true




Sorry for taking so long to reply to this issue. I've tried to reproduce the 
issue in a new vm and I couldn't, most likely it's related to a temporary 
packaging glitch.


Are still encountering this issue with an updated system?

If so, can you provide a backtrace of the problem?

Happy hacking,
--
"By definition, when you are investigating the unknown, you do not know what
you will find"
-- The Ultimate Principle
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#825789: kshisen crashes

[Maximiliano Curia]

Control: tag -1 unreproducible moreinfo
Control: severity -1 important

¡Hola shirish!

El 2016-05-29 a las 22:44 +, shirish शिरीष escribió:
Package: kshisen 
Version: 4:16.04.1-1 
Justification: renders package unusable


Dear Maintainer, 
Get the following when trying to launch the new kshisen on Debian testing -



[$] kshisen


AL lib: (WW) ALCjackBackendFactory_init: jack_client_open() failed, 0x01 
AL lib: (WW) alc_initconfig: Failed to initialize backend "jack" 
AL lib: (WW) alc_initconfig: Failed to initialize backend "pulse" 
log_libkmahjongg: Using background at 
"/usr/share/kmahjongglib/backgrounds/summerfield.svg" 
terminate called after throwing an instance of 'std::out_of_range' 
 what():  vector::_M_range_check: __n (which is 0) >= this->size() (which is 0) 
[1]24324 abort (core dumped)  kshisen



Please fix the issue mentioned above.


I couldn't reproduce the issue, to test it I installed kshisen in a base 
system together with openbox and xserver-xorg, and kshisen launched fine, 
although some icons are missing.



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


In order to take into account the pinning I removed kshisen and all it's auto 
installed denpencies (apt remove kshisen; apt autoremove); added the pinning, 
and reinstalled kshisen. Still, kshisen seems to be working fine.


Can you provide a backtrace?

Happy hacking,
--
"Programs must be written for people to read, and only incidentally for
machines to execute."
-- Hal Abelson, "Structure and Interpretation of Computer Programs"
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#819777: Seems to be fixed when starting to install 5.21 material

[Maximiliano Curia]

On Mon, 9 May 2016 23:42:07 +0200 Eric Valette  wrote:


-- eric

Bug#810256: kwin-x11: Kwin continue to crash every time

[Maximiliano Curia]

Control: tag -1 + unreproducible moreinfo
Control: severity -1 important

¡Hola cosimo!

El 2016-02-10 a las 22:44 +0100, cosimo morelli escribió:

Still waiting for a fix


I think that this issue was related to a problem in qt 5.5 regarding the 
screen setups. Most of the related issues have been fixed but some will only 
be fixed with qt 5.6.1. In any case, currently I'm not able to reproduce the 
issue, and hopefully neither can you.


Happy hacking,
--
"People get lost in thought because it is unfamiliar territory."
-- Fix's Principle
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#794102: [kde-full] Windows frames disappears!!!!

[Maximiliano Curia]

Control: tag -1 + unreproducible
Control: severity important

¡Hola Marco!

El 2015-07-30 a las 16:21 +0200, Marco Righi escribió:
Package: kde-full 
Version: 5:84 


Hi, 
after the last upgrade session the applications in my KDE Plasma has 
lost the windows frames. Even if I use  alt-tab it is not possible to 
switch from an application to another one.



The only way to get the access to KDE menu' is closing all the applications.



I have try to delete



rm $HOME/.kde* -Rf



without resolving the problem.


I have updated the system setting application (icon) because the 
previous was not executable.



KDE openbox works fine with my previous settings.



Please write me if you think I can provide you informations.


kwin had a couple of unfortunate problems last year, and I think you were 
caught in the middle of it. But this bug seems to be no longer reproducible so 
I'm reducing its severity, and will close it after a while if no one says that 
the bug is still reproducible.



 500 testing-updates ftp.it.debian.org
 500 testing www.deb-multimedia.org
 500 testing security.debian.org
 500 testing ftp.it.debian.org
 500 testing apt.jenslody.de
 500 stable-updates  ftp.it.debian.org
 500 stable  security.debian.org
 500 stable  repo.wuala.com
 500 stable  ftp.it.debian.org
 500 stable  dl.google.com
 500 stable  apt.spideroak.com
 500 sid linux.dropbox.com
 500 debian  packages.linuxmint.com


That's a lot of unofficial repositories, I don't know most of them, but the 
last one, it's a different distribution, and changes made in one distribution 
may not go well in the other (like, for instance, the migration to gcc 5 last 
year).


Happy hacking,
--
"There are two major products that come out of Berkeley: LSD and BSD.
We don't believe this to be a coincidence."
-- Jeremy S. Anderson
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#804310: [Pkg-kde-extras] Bug#804310: oxygen-transparent: Build-Depends on kde-workspace-dev which is gone

[Maximiliano Curia]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: oxygen-transparent/experimental -- ROM; Obsoleted by 
plasma 5

¡Hola Andreas!

El 2016-05-27 a las 19:07 +0200, Andreas Beckmann escribió:

On Sat, 07 Nov 2015 09:35:34 +0100 Andreas Beckmann  wrote:
oxygen-transparent cannot be build in experimental any longer since 
kde-workspace-dev is gone.


That package had only a single upload 2.5 years ago - maybe it should be 
removed?


Agreed.

Happy hacking,
--
"Whenever possible, steal code." -- Tom Duff
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#824586: networkmanager-qt: FTBFS: dh_makeshlibs: failing due to earlier errors

[Maximiliano Curia]

¡Hola Chris!

El 2016-05-17 a las 20:05 +0100, Chris Lamb escribió:
Source: networkmanager-qt 
Version: 5.16.0-1 
Severity: serious 
Justification: fails to build from source 
User: reproducible-bui...@lists.alioth.debian.org 
Usertags: ftbfs 
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org


[Lots of Wimax symbols removed]

This is due to a change in network-manager 1.2.

Fixing this bug requires a binnmu to plasma-nm, but I'm planning to upload the 
newer versions of networkmanager-qt and plasma-nm soonish, and the problem 
will fix itself by then.


Happy hacking,
--
"Las computadoras son inútiles, solo pueden darte respuestas."
-- Pablo Picasso
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#791745: closing 791745

[Maximiliano Curia]

close 791745 
thanks

Closing the bug, it has been fixed in all the available versions.
-- 
Saludos,
Maxy

Bug#824059: plasma-desktop: When used with pulseaudio, can make people deaf

[Maximiliano Curia]

Control: severity -1 important

Hi,

I agree that this bug is important, and I'm aware that it's been around for 
quite sometime now, although I thought it was fixed.


Currently, I'm not being able to reproduce it. Digging into the code I found 
that the knotifications mangling of the volumes was fixed back in frameworks 
5.6, and the kde4 notifications were fixed in kde-runtime 4:15.04. The 
notifications I've tested don't trigger a volume change, I've tested this 
using the gstreamer backend and the vlc backend.


Could you please provide as much detail as possible with regards to how you 
configured the notifications and which notifications are triggering this?


Also please show the output of apt policy kde-runtime, and any other 
information that you consider valuable.


Thanks!

Happy hacking,
--
"Programming today is a race between software engineers striving to build
bigger and better idiot-proof programs, and the Universe trying to produce
bigger and better idiots. So far, the Universe is winning."
-- Rich Cook
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#815670: kalarm: Some KDE applications do not autorstart properly

[Maximiliano Curia]

Control: severity -1 normal
Control: fixed -1 4:15.08.3-1
Control: tag -1 + upstream
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=358027

Hi,

As mentioned in the upstream bug, the bug is particular to the way the kde4 
version of kalarm used to autostart itself, and is fixed in a new upstream 
release. I'm tagging the corresponding fixed version, and downgrading the 
severity as this doesn't seem to be a broader issue.


Happy hacking,
--
"If the code and the comments disagree, then both are probable wrong."
-- Norm Schryer
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#799625: closing 799625

[Maximiliano Curia]

close 799625 4:15.08.3-1
thanks
-- 
Saludos,
Maxy

Bug#799625: notes-mobile: fails to upgrade from 'jessie' - trying to overwrite /usr/share/kde4/apps/notes-mobile/notes.qml

[Maximiliano Curia]

Control: reassign -1 src:kdepim 4:4.14.10-2
Control: affects -1 + notes-mobile
Control: done -1 4:15.08.3-1

Hi,

The newer versions of kdepim dropped the extra "-mobile" applications thus I'm 
closing this bug for the kf5 versions of kdepim.


Happy hacking,
--
"It's a well-known fact that computing devices such as the abacus were
invented thousands of years ago. But it's not well known that the first use of
common computer protocol occurred in the Old Testament. This, of course, was
when Moses aborted the Egyptians' process with a control-sea."
-- Tom Galloway (recs.arts.comics, February 1992)
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#815567: [Pkg-kde-extras] Bug#815567: Amarok should depend on virtual-mysql-server-core to support MariaDB

[Maximiliano Curia]

On Friday, 22 April 2016 17:09:40 CEST Andreas Beckmann wrote:
> Control: reopen -1

> On Mon, 22 Feb 2016 18:06:27 +0200 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
>  wrote:
> > Amarok defines as build dependency:

> > Build-Depends-Indep: mysql-server-core-5.6 | mysql-server-core

> > This should be changed to:

> > Build-Depends-Indep: mysql-server-core-5.6 | virtual-mysql-server-core
 
> That has been implemented, but that's the wrong approach.
 
> The buildds only consider the first alternative. This will break once
> mysql-5.6 gets replaced by mysql-5.7 (or whatever else).
> This will break in stretch in case mysql-5.6 leaves stretch.
> And even if secondary alternatives would be considered by the buildds -
> which provider of virtual-mysql-server-core should be installed? There
> is probably more than one ...
 
> So in this case you would really want a generic real package as first
> alternative:
 
> Build-Depends(-Indep): default-mysql-server-core | virtual-mysql-server-core
 
> except that we currently don't have default-mysql-server-core ...

Would you mind cloning this bug and reassigning it to the mysql maintainers, 
so we either get a default-mysql-server-core  to build depend on or some other 
valid solution.

Happy hacking,
-- 
"Nothing ever goes away." -- Commoner's Law of Ecology
Saludos /\/\ /\ >< `/


signature.asc
Description: This is a digitally signed message part.

Bug#749833: scilab: Scilab include non-free codes

[Maximiliano Curia]

Control: block 816260 by 749833

Hi,

As a request from the release team I have removed the dependency of scilab 
from cantor, I'm adding this block to the corresponding bug in cantor as way 
to remember to reenable the backend once the problem is fixed.

Also, since there is a patch available upstream that's being stale for review 
for sometime now, wouldn't it be feasible to upload a patched scilab to 
experimental as a way to gather some testers/reviewers?

Happy hacking,
-- 
"Politicians and diapers have one thing in common. They should both be changed
regularly, and for the same reason." ― José Maria de Eça de Queiroz
Saludos /\/\ /\ >< `/

Bug#815559: konsole: Konsole fails to use default font when selected font in profile becomes unavailable

[Maximiliano Curia]

Control: severity -1 normal
Control: tag -1 + confirmed upstream
Control: forwarded -1 + https://bugs.kde.org/show_bug.cgi?id=359669

¡Hola Eric!

El 2016-02-22 a las 13:45 +0100, Eric Valette escribió:
Package: konsole 
Version: 4:15.12.1-1 
Severity: grave 
Justification: renders package unusable


I understand that this is very frustrating for you, but there is an easy 
workaround, changing the font through the menu, thus I'm downgrading the bug 
severity.


In my konsole profile, I was using droid fonts that juts habe veen removed. 
So I started my konsole, got the screen but nothing was displayed at all. 
It should at least use a default (backup) font and print something to help 
user fixing the problem.



To reprodure : define a profile witha font, then remove the font and restart.


I've forwarded your bug report upstream, please, if possible, subscribe to the 
upstream bug, so if it needs to be followed up you can give the requested 
feedback.


The upstream bug can be seen here: https://bugs.kde.org/show_bug.cgi?id=359669

Happy hacking,
--
"recursividad 95, 154, 156, 201, 224, 293"
-- El Lenguaje de Programacion C, pag. 293 (Kernighan & Ritchie)
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#814971: libpng12.so.0 without a merged /lib is now a broken symlink

[Maximiliano Curia]

Package: libpng12-dev
Version: 1.2.54-2
Severity: serious

Hi,

The fix for #766809 leaves libpng.so as a dangling symlink:

$ ls -l /usr/lib/x86_64-linux-gnu/libpng*.so*
lrwxrwxrwx 1 root root 11 Feb 16 13:33 /usr/lib/x86_64-linux-gnu/libpng.so -> 
libpng12.so
lrwxrwxrwx 1 root root 13 Feb 16 13:33 /usr/lib/x86_64-linux-gnu/libpng12.so -> 
libpng12.so.0

$ ls -l /lib/x86_64-linux-gnu/libpng*.so*
lrwxrwxrwx 1 root root 18 Feb 16 13:33 /lib/x86_64-linux-gnu/libpng12.so.0 
-> libpng12.so.0.54.0
-rw-r--r-- 1 root root 154664 Feb 16 13:33 
/lib/x86_64-linux-gnu/libpng12.so.0.54.0

This generates an ftbfs for any package that build depends on libpng-dev or 
libpng12-dev, thus the bug severity.

Happy hacking,

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages libpng12-dev depends on:
ii  libpng12-0  1.2.54-2
ii  zlib1g-dev  1:1.2.8.dfsg-2+b1

libpng12-dev recommends no packages.

libpng12-dev suggests no packages.

-- no debconf information

Bug#814699: kcompletion: FTBFS: 25% tests passed, 3 tests failed out of 4

[Maximiliano Curia]

On Sunday, 14 February 2016 19:34:26 CET Lisandro Damián Nicanor Pérez Meyer 
wrote:
> > This issue is produced by a bug in qt5 when working with xvfb (or any kind
> > of display that fakes the modelines). I expect most of the tests to fail
> > under these circumstances.

> > The qt5 maintainers point me out the patch in:
> >  http://code.qt.io/cgit/qt/qtbase.git/commit?id=79447068579ea93d

> > I expect it to be part of the next qt5 upload.
 
> So far this bug only affects KDE stuff in experimental. maxy: do you need an
> upload of both Qt 5.5.1 and 5.6.0~beta or an upload of just one of those is
> OK?

The mentioned commit is part of the v5.6.0-beta1 upstream tag, so I think that 
the version in experimental should be fine. 

I don't know what are the release plans regarding 5.6, but in the meantime a  
5.5.1 with this patch applied would be nice.

Happy hacking,
-- 
"It is practically impossible to teach good programming to students that have
had a prior exposure to BASIC: as potential programmers they are mentally
mutilated beyond hope of regeneration."
-- Edsger W. Dijkstra
Saludos /\/\ /\ >< `/

Bug#814699: kcompletion: FTBFS: 25% tests passed, 3 tests failed out of 4

[Maximiliano Curia]

Control: clone -1 -2
Control: reassign -2 src:qtbase-opensource-src 5.5.1+dfsg-13
Control: block -1 by -2
Control: tag -2 + upstream
Control: forwarded -2 https://bugreports.qt.io/browse/QTBUG-49322

Hi,

On Sunday, 14 February 2016 11:52:38 CET Chris Lamb wrote:
> Source: kcompletion
> Version: 5.16.0-1
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
 
>   1/4 Test #2: klineedit_unittest ...***Exception: Numerical 
> 0.02 sec
 
>   2/4 Test #3: kcombobox_unittest ...***Exception: Numerical 
> 0.02 sec
 
>   3/4 Test #4: ksortablelisttest    Passed0.02 sec
>   4/4 Test #1: kcompletioncoretest ..***Exception: Numerical 
> 0.05 sec

This issue is produced by a bug in qt5 when working with xvfb (or any kind of 
display that fakes the modelines). I expect most of the tests to fail under 
these circumstances.

The qt5 maintainers point me out the patch in:
 http://code.qt.io/cgit/qt/qtbase.git/commit?id=79447068579ea93d

I expect it to be part of the next qt5 upload.

Happy hacking,
-- 
“First, solve the problem. Then, write the code.” -- John Johnson
Saludos /\/\ /\ >< `/

Bug#814200: kdepimlibs: Incorrect Build-Deps

[Maximiliano Curia]

Control: tag 814200 + unreproducible

Hi,

On Tuesday, 9 February 2016 10:59:29 CET Zhang Jingqiang wrote:
> Package: kdepimlibs
> Version: 4:15.12.1-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the
> past)

> It should build-depend on kgendesignerplugin, which install the needed cmake
> files.

This can't be the reason for the failed build, kgendesignerplugin is a 
dependency of libkf5kdelibs4support-dev, so it's available at build time.

But definetly the kdesignerplugin and kgendesignerplugin packages need a 
review.
 
> And the optional prison-dev is not needed, as the really needed one is
> kf5prison which has not been released yet.

Also not a reason to failed to build from source.

The buildds logs show that the issue in experimental was related to the 
version of akonadi-server at the time of the build try. Right now, the buildds 
should be able to rebuild kdepimlibs, afaik (if we kindly ask for a retry).

Am I missing something?

Happy hacking,
-- 
: You are in a dark room with a compiler, emacs, an internet connection,
: and a thermos of coffee.
: Your move ?
Saludos /\/\ /\ >< `/

Bug#793019: kde-config-sddm: Can't save changes

[Maximiliano Curia]

Control: severity -1 normal
Control: tag -1 + unreproducible

On 20/07/15 10:58, Salvo Tomaselli wrote:
> Package: kde-config-sddm
> Version: 4:5.3.2-1
> Severity: grave
> Justification: renders package unusable
> this package should probably depend on whatever plasma5 wants to use to 
> elevate
> privileges.
> Right now, whenever I try to save the changes, I see a notification with a red
> icon, but it disappears within 0.2seconds so I am not really able to read it.
I'm not sure if the bug was generated due to a missing dependency, or was a bug 
in the kauth sddm helper. But I can't reproduce the issue using the current 
unstable packages.

Are you still able to reproduce the issue?

If so, could you provide a list of the packages installed (dpkg 
--get-selections) in the machine that triggers the issue?

Happy hacking,

Bug#803381: step: FTBFS: error: #error Eigen2-support is only available up to version 3.2.

[Maximiliano Curia]

Hi,

On 29/10/15 14:32, Chris Lamb wrote:
> Source: step
> Version: 4:15.08.0-1
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Oh, this is fixed in experimental, thanks to Anton Gladky (and also commited
upstream). Sadly it's not the only thing that is broken, it seems that the
metaproperties conversion mechanism used to convert a double to String is
producing "2.2002" instead of "2.2".

This produces a failure in the tests as used by dh_auto_test.

Mmh, this due to a change in qt 5.5. Ok, building with a workaround.

Happy hacking,
-- 
"There are two major products that come out of Berkeley: LSD and BSD.
We don't believe this to be a coincidence."
-- Jeremy S. Anderson
Saludos /\/\ /\ >< `/



signature.asc
Description: OpenPGP digital signature

Bug#800462: sddm-theme-maui: updating results in WHITE SCREEN and beeing unable to login

[Maximiliano Curia]

On 29/09/15 19:06, Max Görner wrote:
> Severity: critical
> Justification: breaks the whole system


>  I updated from 0.11.0-6 (or something alike) to 0.12.0-4 (or
>  something alike).

>  I can't login anymore, therefore I couldn't do anything.

> Versions of packages sddm-theme-maui recommends:
> ii  sddm  0.11.0-3

Does the problem solves itself if you upgrade the sddm version to 0.12.0-4 ?

-- 
"Elegance is not a dispensable luxury but a quality that decides between
success and failure."
-- Edsger W. Dijkstra
Saludos /\/\ /\ >< `/



signature.asc
Description: OpenPGP digital signature

Bug#799837: sddm becomes unusable after logout

[Maximiliano Curia]

On 23/09/15 08:37, Salvo Tomaselli wrote:
> Justification: breaks the whole system

> 1. KDE took several minutes to disappear
> 2. After it disappeared the screen went off! Backlight off and completely
> dark.

Assuming a long standing session it could involve a number of key upgrades
that trigger this particular error.

> I attach some logs in hope that they can help.

Sep 23 08:28:29 localhost systemd[1]: Started Session c1 of user sddm.
Sep 23 08:28:31 localhost kernel: [461586.521292] sddm-greeter[844]: segfault
at 18 ip 7f7aa72e26f8 sp 7ffd8ea10b20 error 4 in
libqxcb.so[7f7aa7298000+b6000]
> Init: systemd (via /run/systemd/system)

I think this is the most interesting part, and I'm a bit puzzled by this, the
session name indicates a consolekit session, afaik. But even after installing
consolekit I still have the normal systemd sessions naming (just numbers),
disabling libpam-systemd I got no session name, but still no consolekit
session naming.

Do you have any consolekit related configuration?

Is the problem consistently reproducible whenever you log out or its was a one
time error?

Does the problem go away if you boot your machine after removing consolekit?

Happy hacking,
-- 
"UNIX is basically a simple operating system, but you have to be a genius to
understand the simplicity."
-- Dennis Ritchie
Saludos /\/\ /\ >< `/



signature.asc
Description: OpenPGP digital signature

Bug#799430: libkf5texteditor5: libgit2 upgrade pulls in OpenSSL, conflicting with the GPL

[Maximiliano Curia]

Hi,

On 19/09/15 06:24, Ben Longbons wrote:
> Package: libkf5texteditor5
> Version: 5.13.0-1+b1
> Severity: serious
> Justification: license violation

> libgit2-23 now links to OpenSSL, which conflicts with the GPL license
> used by this package.

> See #798421 for more information.

libkf5texteditor is an LGPL-2.1+ project that has optional GPL-2+ data files,
so the code that links against libgit is LGPL-2.1+ in effect and I don't think
that there an issue there. I'll add an extra comment about this in the
copyright file and close this issue in the next upload.

Something like:
 KDE software follows the KDE licensing policy that can be found:
 https://techbase.kde.org/Policies/Licensing_Policy
 Some files might refer to license names that are explained it these the
 mentioned policy.
 .
 Unless otherwise noted the default license used in this framework is
 LGPL-2.1+ for the source code. Some of the optional xml and js files used
 at runtime are under a version of the GPL license.
 .
 In particular, this licensing allows this project to link against libgit2
 (which may, in turn, link against the openssl, which has incompatibilities
 with the GPL), as the linkable code per se is under a version of the LGPL.

Happy hacking,
-- 
"By definition, when you are investigating the unknown, you do not know what
you will find"
-- The Ultimate Principle
Saludos /\/\ /\ >< `/



signature.asc
Description: OpenPGP digital signature

Bug#799430: Bug#799431: kate: libgit2 upgrade pulls in OpenSSL, conflicting with the GPL

[Maximiliano Curia]

Hi,

On 19/09/15 06:24, Ben Longbons wrote:
> Package: kate
> Version: 4:15.08.0-1
> Severity: serious
> Justification: license violation

> libgit2-23 now links to OpenSSL, which conflicts with the GPL license
> used by this package.

> See #798421 for more information.

This one is tougher. The code only uses git from a plugin that is under the
LGPL-2+, that one is fine, also most of the code is LGPL-2.1+, which is,
again, fine. But the whole code links against ktexteditor, even the plugins
that are under GPL-3+, and libssl in turn.

So I guess that either ktexteditor needs to drop the libgit build-dep or
libgit needs to be linked against gnutls after all.

I'll add a similar comment in the copyright file than the one I've sent tho
the #799430 bug, and drop the libgit2-dev build dep in ktexteditor till
#798421 solved.

Happy hacking,
-- 
"If you can't write it down in English, you can't code it." -- Peter Halpern
Saludos /\/\ /\ >< `/



signature.asc
Description: OpenPGP digital signature

Bug#799172: To reproduce

[Maximiliano Curia]

Control: tag -1 + confirmed

On 17/09/15 11:23, Eric Valette wrote:
> A simple
> 
> balooctl disable
> 
> is sufficient.

Interestingly if baloo is installed and disabled from the systemsettings kcm
gwenview works fine.

I think this is a bug in libkf5baloo5, baloo is supposed to be optional at
runtime.

I couldn't find an upstream bug about this that is relavant to the baloo
version in frameworks. Would it be too much to ask you to report this upstream
and add the link of the upstream bug to this report?

Happy hacking,
-- 
"Haskell is faster than C++, more concise than Perl, more regular than Python,
more flexible than Ruby, more typeful than C#, more robust than Java, and has
absolutely nothing in common with PHP."
-- Audrey Tang
Saludos /\/\ /\ >< `/



signature.asc
Description: OpenPGP digital signature

Bug#798906: sddm crashes on boot

[Maximiliano Curia]

Control: severity -1 important
Control: tag -1 + upstream

On 14/09/15 00:34, Carlos Kosloff wrote:
> Severity: grave

The package works in most of the use cases, so I don't think the severity is
justified, downgrading it to important.

> I only removed leftovers of packages that had already been removed by a
> dist-upgrade.
> After that, sddm would not give me a login prompt so I was unable to log into
> KDE the normal way.
> I had to do 'systemctl stop sddm.service', as root.
> Then 'startx startkde' as user to access the desktop, this bypassing sddm.
> I checked the above mentioned packages and they are installed and the latest
> version in stretch.
> In order to log into desktop the normal way I installed kdm and set is as 
> default.

> To help troubleshooting I will attach some traces I collected from error logs.

I couldn't reproduce the bug as reported. But since the log showed starting
sddm from tty1 after an upgrade I tested sddm with a running display-manager,
it fails in similar ways to the reported error.

Either having an X on tty7, an non-stopped kdm, lightdm, or any other display
manager running in tty7 would fail.

I think that sddm is failing to detect the 'seat' already in use. I'll keep on
investigating this issue. In the mean time, it would be nice to if you could
check if stopping a running display manager before starting sddm allows sddm
to work for you, as this would confirm that we are talking about the same issue.

Happy hacking,
-- 
"It is not the task of the University to offer what society asks for, but to
give what society needs."
-- Edsger W. Dijkstra
Saludos /\/\ /\ >< `/



signature.asc
Description: OpenPGP digital signature

Bug#796956: Note that this is a docked laptop using external monitor

[Maximiliano Curia]

Control: severity -1 important

On 08/09/15 10:04, eric2.vale...@orange.com wrote:
> I now have half a dozen boxes that works correctly and this is the only one
> that is a docked laptop using an external monitor with internal LVDS display
> off. So far as I had multiple temporary breakage on various boxes due to
> partial/incompatible packages versions uploads, I did not consider it was a
> specific case but now only this docked laptop remains broken.

Ok, that sounds more like another issue. This seems to be another effect of a
problem in qt5.4 regarding QScreen returning null in unexpected places. And is
currently known to reproducibly fail on machines with one display off, for
instance, closing the lid in a laptop that has an external monitor connected.
This is supposedly fixed in qt5.5, currently in experimental.

I'm downgrading the severity as the problem went from every machine to only one.

Happy hacking,
-- 
"I decry the current tendency to seek patents on algorithms. There are better
ways to earn a living than to prevent other people from making use of one's
contributions to computer science."
-- Donald Knuth
Saludos /\/\ /\ >< `/



signature.asc
Description: OpenPGP digital signature

Bug#795884: closing 795884

[Maximiliano Curia]

close 795884 5.13.0-2
thanks

Hi,

This issue was fixed with the upload of the version 5.13.0-2.

Thanks for reporting,
-- 
Saludos,
Maxy

Bug#777927: closing 777927

[Maximiliano Curia]

close 777927 4:15.08.0-1
thanks

Hi,

This was closed with the latest upload.

Happy hackin,
-- 
Saludos,
Maxy

Bug#794573: Reopening this bug

[Maximiliano Curia]

Control: reassign -1 kdecoration 4:5.3.2-1
Control: fixed -1 4:5.3.2-3

Hi,

On 04/08/15 18:27, Diederik de Haas wrote:
> I'm reopening this bug, since I'm experiencing this too (just send a msg 
> confirming this bug) and just got another person in #debian-kde which ran 
> into 
> this issue too.
> While the gcc-5 transition may be the cause, there should be a RC bug against 
> breeze to prevent it from transitioning to testing.

This bug was actually a problem in the plugins abi breakage caused by the gcc5
transition, sadly the transition tracker doesn't detect this kind of abi
changes. It has been solved in testing with the migration of kdecoration
4:5.3.2-3:
[2015-08-27] kdecoration 4:5.3.2-3 MIGRATED to testing (Britney)

Happy hacking,
-- 
"The cheapest, fastest and most reliable components of a computer system are
those that aren't there."
-- Gordon Bell
Saludos /\/\ /\ >< `/



signature.asc
Description: OpenPGP digital signature

Bug#798786: [libpam-kwallet5] kwalletd5 started by libpam-kwallet5 is not used by kwalletmanager5

[Maximiliano Curia]

Control: severity -1 minor
Control: tag -1 + upstream

On 12/09/15 19:00, Rahul Amaram wrote:
> Severity: grave

> After installing the libpam-kwallet5 package, when I login via SDDM, a process
> such as below is started.

> Konsole outpu rahul12635 12634  0 22:08 ?00:00:00
> /usr/bin/kwalletd5 --pam-login 17 27

The way that libpam-kwallet5 works is that is listens in a socket and waits
for someone to connect to it. Currently the part that connects to it is in the
startkde script that is part of plasma-workspace from the version 5.4.0, sadly
plasma-workspace hasn't migrated to testing and so it shows the current 
behavior.

That said, it means that libpam-kwallet5 is only useful in a session that has
the code snippet from startkde:
if test -n "$PAM_KWALLET5_LOGIN" ; then
env | socat STDIN UNIX-CONNECT:$PAM_KWALLET5_LOGIN
fi
And the kwalletd5 processes will be `hanged' in a session without it.
(You can add the previous snippet to your startkde script to fix this issue
while we wait for plasma-workspace to enter into testing)

This problem was reported upstream as part of the code review done before
packaging it and acknowledged upstream:

http://lists.alioth.debian.org/pipermail/pkg-kde-talk/2014-October/001971.html
and:
http://lists.alioth.debian.org/pipermail/pkg-kde-talk/2015-January/002002.html

Àlex, please consider this a friendly ping about this issue.

Some ideas:
 - Avoid starting a new kwalled5 if there is one already for the same user.
 - Set the environment, if needed, on the first kwalletmanager instantiation.
 - Have a timeout for the environment read (1 minute should be enough).

Happy hacking,
-- 
"It is practically impossible to teach good programming to students that have
had a prior exposure to BASIC: as potential programmers they are mentally
mutilated beyond hope of regeneration."
-- Edsger W. Dijkstra
Saludos /\/\ /\ >< `/



signature.asc
Description: OpenPGP digital signature