calligra_2.9.11+dfsg-4_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 10 Oct 2016 23:32:39 +0200
Source: calligra
Binary: calligra karbon kexi kexi-data kexi-calligrasheets-driver 
kexi-mysql-driver kexi-postgresql-driver kexi-xbase-driver kexi-sybase-driver 
kexi-web-form-widget calligra-reports-web-element calligrasheets calligraplan 
calligrawords calligrawords-data calligrastage calligrastage-data calligraflow 
calligraflow-data braindump calligraactive calligra-libs calligra-semanticitems 
calligra-data okular-backend-odp okular-backend-odt calligraauthor krita-gemini 
calligra-gemini calligra-gemini-data
Architecture: source
Version: 1:2.9.11+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Description:
 braindump  - ideas organizer application for the Calligra Suite
 calligra   - extensive productivity and creative suite
 calligra-data - common shared data for the Calligra Suite
 calligra-gemini - unified interface for stage and words
 calligra-gemini-data - Calligra Gemini - data files
 calligra-libs - common libraries and binaries for the Calligra Suite
 calligra-reports-web-element - web element for Calligra Reports
 calligra-semanticitems - semantic item plugins for the Calligra Suite
 calligraactive - Tablet version of Calligra
 calligraauthor - Authoring tool for the Calligra Suite
 calligraflow - flowcharting program for the Calligra Suite
 calligraflow-data - data files for Flow flowcharting program
 calligraplan - integrated project management and planning tool
 calligrasheets - spreadsheet for the Calligra Suite
 calligrastage - presentation program for the Calligra Suite
 calligrastage-data - data files for Calligra Stage
 calligrawords - word processor for the Calligra Suite
 calligrawords-data - data files for Words word processor
 karbon - vector graphics application for the Calligra Suite
 kexi   - integrated database environment for the Calligra Suite
 kexi-calligrasheets-driver - Tables plugin for kexi
 kexi-data  - data files for Kexi
 kexi-mysql-driver - MySQL support for kexi
 kexi-postgresql-driver - PostgreSQL support for kexi
 kexi-sybase-driver - Sybase support for kexi
 kexi-web-form-widget - web form widget for Kexi
 kexi-xbase-driver - XBase support for kexi
 krita-gemini - transitional package, replaced with "calligra-gemini"
 okular-backend-odp - Okular backend for ODP documents
 okular-backend-odt - Okular backend for ODT documents
Changes:
 calligra (1:2.9.11+dfsg-4) unstable; urgency=medium
 .
   * Team upload.
   * Create the symlink in calligra-gemini only when the package is built;
 fix arch-indep builds.
Checksums-Sha1:
 b451d44d0725b3128bab403b3ca486a52274f673 4633 calligra_2.9.11+dfsg-4.dsc
 fbbdeb90575e5c3584976fbbe456160fe87e43fa 62260 
calligra_2.9.11+dfsg-4.debian.tar.xz
Checksums-Sha256:
 760ad2304125786f0dce49687a04754e86ff50d9aa55cd8de8a80add917091b1 4633 
calligra_2.9.11+dfsg-4.dsc
 6ffa6fe9fc0552b1f517d118d3799f1a247886b6bfbb336b4d874335658e9e5e 62260 
calligra_2.9.11+dfsg-4.debian.tar.xz
Files:
 919da7c8e255d8301977b2a74ad81ce5 4633 kde optional calligra_2.9.11+dfsg-4.dsc
 6f7c5f0e8ef1b8d30f38a5a9266c0247 62260 kde optional 
calligra_2.9.11+dfsg-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX/AljAAoJEC0ZHIhDsT9NunUP/3wQv8WfFbd0R/58JzehWKEg
jgIIiCj+kg7hIlQdnW2GNoEgvkcjiQvafI6SStX0OLsSZtOCw9OO6ZXhVEqYWxux
XtcBLI98cfphsXfrQT70WOmALBfzyLasRT6dNZkjG16oX+K7N3vLo0LFoWFDUxtf
RA6uxRh9VBSC3vItDMiyPTCFe1g3kKd12+9iSmNMML9cEAf/cBaB/7995b4esiNq
+uqjIY4WRH1EJltgjDWNnngmGhAZUaHDu+42LnQokN+PqBxyEz9VycFLmB7ZYc6x
NderW+XhAa2W5tiTEo9HplT50bZvX8G2GP2kWUyJ6lXY74JwUxfACrfBehoMViGp
TTlrtDaB+9laaphb6N8AsPcS4TpZbTsIwVRlrQFC+RcbXMsW+/v1K0QM2eSm+Hp1
fQILubkmko8G1YS1p5BLLOiUmZDV7HaGCTgUU1YBy7W13p8gvk4ROrkOc3WZPKVl
+uat7MTZAHumH8zjTC/Fw9lr2wdVupuLAneNBXE+6YwBPLa69vT+CUa6DVpT8tzC
huszM7P9ZzWBHcEH6xkXhAIHV/KUrYRSoCJ1PXbGYcIXfXcYIwCw3Uc7HfjRSHxj
Ljm/c2xZAH93ord6SsVgYMJC5Phuln42Mncesy4zNbk4g+DzUTRmJTfeWsJEIuD5
ZmrbjFJi2GIOwHspiud+
=r46B
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Bug#840141: kwin-x11: Short freeze when showing multiple tray notifications

[Alex Dănilă]

Hola!

I believe this is rather and interaction between KWin and Plasmashell. 
If I stopped the Plasmashell process, the freeze doesn't happen anymore 
(those notifications are drawn at the top of the screen in small 
windows). A further argument for this idea is that after the freeze the 
screen goes one "frame" back, and that the music and cursor are not 
affected.


I'll note that after restarting Plasmashell this doesn't happen as 
reliably as before.


However, if you know a good way of triggering this kind of 
notifications, it will be my pleasure to do it.


Thank you,
Alex

On 10/10/16 13:14, Maximiliano Curia wrote:

¡Hola Alex!

El 2016-10-08 a las 22:32 +0300, Alex Dănilă escribió:

Package: kwin-x11 Version: 4:5.7.4-1 Severity: normal


The entire screens freeze for a couple of seconds (3-4, but sometimes 
seemed close to 10) everytime notifications from the tray are about 
to scroll down or disappear. This only affects drawing of screen 
content, it doesn't affect sound or cursor motion.


If relevant, the particular tray notifications are about bluetooth 
devices, I'll attach a screenshot with this. The particular order is 
like this:
-two messages (M1 - connection deactivated, M2 - connection timed 
out) appear one above the other -2-3 seconds pass -freeze -2 -freeze 
ends -M1 disappears, M2 animates going down -messages reappear and 
animate again, but without freezes.


I'll send a screenshot after the bug is created, and if possible a 
recording.


As reported it seems that the issue is bluetooth specific, and it 
might be caused by an underlying issue of the bluetooth kernel module 
or hardware device. In my limited tests I couldn't reproduce this 
behaviour in my laptop.


Would it be feasible for you to test this multiple bluetooth 
notifications in a different desktop environment in order to rule out 
a kernel/hardware issue?


Can you reproduce this triggering a different type of notifications?

Happy hacking,

Processing of calligra_2.9.11+dfsg-4_source.changes

[Debian FTP Masters]

calligra_2.9.11+dfsg-4_source.changes uploaded successfully to localhost
along with the files:
  calligra_2.9.11+dfsg-4.dsc
  calligra_2.9.11+dfsg-4.debian.tar.xz

Greetings,

Your Debian queue daemon (running on host franck.debian.org)

Re: calligra-l10n_2.9.11-1_amd64.changes is NEW

[Scott Kitterman]

On Monday, October 10, 2016 11:42:13 PM Pino Toscano wrote:
> In data sabato 17 settembre 2016 16:29:13 CEST, Debian FTP Masters ha 
scritto:
> > binary:calligra-l10n-tr is NEW.
> > 
> > Your package has been put into the NEW queue, which requires manual action
> > from the ftpteam to process. The upload was otherwise valid (it had a good
> > OpenPGP signature and file hashes are valid), so please be patient.
> > 
> > Packages are routinely processed through to the archive, and do feel
> > free to browse the NEW queue[1].
> > 
> > If there is an issue with the upload, you will receive an email from a
> > member of the ftpteam.
> > 
> > If you have any questions, you may reply to this email.
> 
> Ping? This is a very simple source, data-only (= translation), and the
> only NEW package is the addition of Turkish translations.
> 
> Why is such a simple source held in NEW for three weeks already?
> Was it simply forgotten, or is there any actual issue with it?
> 
> Thanks,

There's no note indicating someone reviewed it an believed there was a 
problem.

Personally, much of the time I've had recently (admittedly not a lot) to work 
on FTP matters has been absorbed by distractions such as maintainers whining 
to the Tech Committee rather than just getting on with doing the work that 
needs to be done.  See [1] if you're curious.  Spending time on things like 
that materially decreases the time the FTP team has to work on things like 
New.

Scott K

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

Re: calligra-l10n_2.9.11-1_amd64.changes is NEW

[Pino Toscano]

In data sabato 17 settembre 2016 16:29:13 CEST, Debian FTP Masters ha scritto:
> binary:calligra-l10n-tr is NEW.
> 
> Your package has been put into the NEW queue, which requires manual action
> from the ftpteam to process. The upload was otherwise valid (it had a good
> OpenPGP signature and file hashes are valid), so please be patient.
> 
> Packages are routinely processed through to the archive, and do feel
> free to browse the NEW queue[1].
> 
> If there is an issue with the upload, you will receive an email from a
> member of the ftpteam.
> 
> If you have any questions, you may reply to this email.

Ping? This is a very simple source, data-only (= translation), and the
only NEW package is the addition of Turkish translations.

Why is such a simple source held in NEW for three weeks already?
Was it simply forgotten, or is there any actual issue with it?

Thanks,
-- 
Pino Toscano

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

Re: Skrooge package

[Pino Toscano]

Hi,

In data lunedì 10 ottobre 2016 22:58:22 CEST, Stephane MANKOWSKI ha scritto:
> I'm the main developer of Skrooge (an application in KDE extragear).
> The version of Skrooge packaged for Debian is the version 1.9.3
> (released in April 2014).:-(

That's the version available in Debian Jessie, that is the current
stable version. What is in stable cannot be updated usually, unless
for very important reasons. Considering that newer versions of skrooge
are based on KDE Frameworks, which do not exist in stable, that makes
an update of stable a no-go option.

> This is a very old version based on Qt4/KDE4.
> The last release is the version 2.5.0 based on Qt5/KF5.

OTOH, currently there is 2.4.0 in Debian testing & unstable, see:
https://packages.qa.debian.org/s/skrooge.html

> Because, I'm on Kubuntu (Sorry for that!), I made a ppa
> (https://launchpad.net/~s-mankowski/+archive/ubuntu/ppa-kf5) to provide
> the last version of Skrooge as soon as possible.

Ubuntu PPAs are useless for Debian. While I have nothing against your
work, and I can perfectly understand you want the latest versions for
your users, at least a quick glance at that packaging gives me so many
wrong details and bits that I'd recommend users to not use it at all.

-- 
Pino Toscano

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

Skrooge package

[Stephane MANKOWSKI]

Hi,

I'm the main developer of Skrooge (an application in KDE extragear).
The version of Skrooge packaged for Debian is the version 1.9.3
(released in April 2014).:-(
This is a very old version based on Qt4/KDE4.
The last release is the version 2.5.0 based on Qt5/KF5.

Because, I'm on Kubuntu (Sorry for that!), I made a ppa
(https://launchpad.net/~s-mankowski/+archive/ubuntu/ppa-kf5) to provide
the last version of Skrooge as soon as possible.

Do you think that's could be better to update the package in Debian
instead of ppa?
If yes, how can I help to update the Debian package?

Thank you in advance for your help.
Regards.
Stephane

Re: Kmail attachment selects two items instead of only one [fixed]

[inkbottle]

Since I follow "testing" and don't want to follow "sid", I did an
adjustment using this line:

aptitude -R --visual-preview -t sid install $(aptitude search -F"%p; %v; %V; 
%d" -t sid '?installed(?maintainer(debian-qt-kde))'|egrep 5.8|cut -d\; -f1|tr 
'\n' ' ')

and inserting attachment is back to normal.

Chris

On Sunday, October 9, 2016 12:40:45 AM CEST you wrote:
> Dear all,
> 
> When I try to attach a file by simply clicking on "attach", two files are
> selected and immediately included.
> 
> When the "contextual file browser" is opened, if I do a right click on the
> file I intend to attach, instead of a mere left click, then I can see two
> file names are written in the "name" line; this gives me the opportunity to
> remove one of those names pressing backspace.
> 
> In case it would have been a "glitch" due to all those Akonady restart I did
> a reboot and try again; it happens all the time.
> 
> I did some searches on the web about that, but to no avail.
> 
> I did a "testing" upgrade, some two days ago, maybe that's why, maybe I
> would better have done a "sid" upgrade; anyway I'm not good at finding why
> this kind of piece of software would go astray: but I report it anyway in
> case it would help.
> 
> Chris

calligra_2.9.11+dfsg-3_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 10 Oct 2016 21:04:44 +0200
Source: calligra
Binary: calligra karbon kexi kexi-data kexi-calligrasheets-driver 
kexi-mysql-driver kexi-postgresql-driver kexi-xbase-driver kexi-sybase-driver 
kexi-web-form-widget calligra-reports-web-element calligrasheets calligraplan 
calligrawords calligrawords-data calligrastage calligrastage-data calligraflow 
calligraflow-data braindump calligraactive calligra-libs calligra-semanticitems 
calligra-data okular-backend-odp okular-backend-odt calligraauthor krita-gemini 
calligra-gemini calligra-gemini-data
Architecture: source
Version: 1:2.9.11+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Description:
 braindump  - ideas organizer application for the Calligra Suite
 calligra   - extensive productivity and creative suite
 calligra-data - common shared data for the Calligra Suite
 calligra-gemini - unified interface for stage and words
 calligra-gemini-data - Calligra Gemini - data files
 calligra-libs - common libraries and binaries for the Calligra Suite
 calligra-reports-web-element - web element for Calligra Reports
 calligra-semanticitems - semantic item plugins for the Calligra Suite
 calligraactive - Tablet version of Calligra
 calligraauthor - Authoring tool for the Calligra Suite
 calligraflow - flowcharting program for the Calligra Suite
 calligraflow-data - data files for Flow flowcharting program
 calligraplan - integrated project management and planning tool
 calligrasheets - spreadsheet for the Calligra Suite
 calligrastage - presentation program for the Calligra Suite
 calligrastage-data - data files for Calligra Stage
 calligrawords - word processor for the Calligra Suite
 calligrawords-data - data files for Words word processor
 karbon - vector graphics application for the Calligra Suite
 kexi   - integrated database environment for the Calligra Suite
 kexi-calligrasheets-driver - Tables plugin for kexi
 kexi-data  - data files for Kexi
 kexi-mysql-driver - MySQL support for kexi
 kexi-postgresql-driver - PostgreSQL support for kexi
 kexi-sybase-driver - Sybase support for kexi
 kexi-web-form-widget - web form widget for Kexi
 kexi-xbase-driver - XBase support for kexi
 krita-gemini - transitional package, replaced with "calligra-gemini"
 okular-backend-odp - Okular backend for ODP documents
 okular-backend-odt - Okular backend for ODT documents
Closes: 840071 840243
Changes:
 calligra (1:2.9.11+dfsg-3) unstable; urgency=medium
 .
   * Team upload.
   * Update Vcs-* fields.
   * Backport upstream commit 843c41decfa85e351349f7a410893ac85c9d60b7 to find
 PostgreSQL 9.6; patch upstream_cmake-find-PostgreSQL-9.6.patch.
 (Closes: #840071)
   * Make calligra-gemini start: (Closes: #840243)
 - create a symlink in the non-multi-arch library directory to the
   multi-arch installation place, as the latter option is not handled by
   kdelibs 4.x
 - add the libqtwebkit-qmlwebkitplugin dependency, as the QtWebKit module
   is used
Checksums-Sha1:
 7053edd4211b2195325c13a57bfe825e59f7e5eb 4633 calligra_2.9.11+dfsg-3.dsc
 9514615881f29aebf09ba5e43700dc350752bd7f 62220 
calligra_2.9.11+dfsg-3.debian.tar.xz
Checksums-Sha256:
 85e0da7cc2e322154f69799a375a7d8a8f81384594b1181431d299cb5d74c95a 4633 
calligra_2.9.11+dfsg-3.dsc
 ab1a9f8291b0390689d0f610323adbe6c7ba5c4abe603ecb31e9d7f12840810f 62220 
calligra_2.9.11+dfsg-3.debian.tar.xz
Files:
 1fc9fa45ab9ea51610e0bb55b81fbb1b 4633 kde optional calligra_2.9.11+dfsg-3.dsc
 f8770746eec068b830421af0792bcbd4 62220 kde optional 
calligra_2.9.11+dfsg-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX++aIAAoJEC0ZHIhDsT9NH3cP+wQbn9hWUPz6vN9VYD2C082r
5ITa3aYYIHtTHBlciuohMSHT5DSEPoW8tSfn9nfoCqsKl1cRVqtcSl7dukEBSrFT
I7xGumx/l6aB6NBH8h1KzO0W1RJSkuydlRD0vcAUWaa+Du3oS/lxQ43pOXVOw0VP
jS3DUqFeVn0sVdObisX1UtLKP9ZflaI12dSkET3SP3i0Y1RulLyG58Tpqk4gTfLB
TZ2Zkbfq25mnYYLBnq9TfxrumgLZhhr1h73I6YEH5vgb/HONvdRiYI2Es/LYRpHJ
xftSBthCUNCdfFnVbqPNRkr377YuwxlBVVBbqY9GxEJqWup8rqlAd1JuADnl8LVg
L/c6met5RCKYc55gzsZVSAZbUSxml+YZSni4z1/eKBH0Ihewemnvu072zHYd/LM3
2TA1i8T2ynMJwleKj5hIz8VCKM733QOoSAoEEHWTxXb6JM8skbViKic01pkKWWgI
Vco5WG+/xcvXpTgcWULinQGS2De8+pkQ2hVElnOaR+A9HsGV+79oDyk5paGqEUGt
qFKpaF9VjP6UxK2cMezhUXyYX+HXtZUJCGkVtx/BrX/XUKfmbJb8hjDLtGlRZIlY
bddf0ip8j2vIKfHngTnI7dY5+c5YR8KjZsDWvDH1+iNcFJCkB+26wtAAuf41MOlq
2W4Z+dRzcJgrKv2eBG0W
=8Emj
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of calligra_2.9.11+dfsg-3_source.changes

[Debian FTP Masters]

calligra_2.9.11+dfsg-3_source.changes uploaded successfully to localhost
along with the files:
  calligra_2.9.11+dfsg-3.dsc
  calligra_2.9.11+dfsg-3.debian.tar.xz

Greetings,

Your Debian queue daemon (running on host franck.debian.org)

Bug#840243: marked as done (calligra-gemini does not launch due to missing QtQuick components)

[Debian Bug Tracking System]

Your message dated Mon, 10 Oct 2016 19:20:40 +
with message-id 
and subject line Bug#840243: fixed in calligra 1:2.9.11+dfsg-3
has caused the Debian Bug report #840243,
regarding calligra-gemini does not launch due to missing QtQuick components
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
840243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: calligra-gemini
Version: 1:2.9.11+dfsg-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

calligra-gemini will not launch due to the following error:

"The Calligra Qt Quick components were not found. This means your installation
is broken."

On the console, the following error message is printed:

file:///usr/share/kde4/apps/calligragemini/calligragemini.qml:22:1: module
"org.calligra.CalligraComponents" is not installed
 import org.calligra.CalligraComponents 0.1 as Calligra

It does not matter if calligra-gemini is installed separately or as part of the
whole calligra suite.

Please make sure these componentes are part of calligra-libs or whichever
package they belong.

Thank you!



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

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

Versions of packages calligra-gemini depends on:
ii  calligra-gemini-data  1:2.9.11+dfsg-2
ii  calligra-libs 1:2.9.11+dfsg-2
ii  calligrastage 1:2.9.11+dfsg-2
ii  calligrawords 1:2.9.11+dfsg-2
ii  kde-runtime   4:16.08.0-1
ii  libc6 2.24-3
ii  libkdecore5   4:4.14.23-1
ii  libkdeui5 4:4.14.23-1
ii  libqt4-declarative4:4.8.7+dfsg-9
ii  libqt4-network4:4.8.7+dfsg-9
ii  libqt4-opengl 4:4.8.7+dfsg-9
ii  libqt4-svg4:4.8.7+dfsg-9
ii  libqtcore44:4.8.7+dfsg-9
ii  libqtgui4 4:4.8.7+dfsg-9
ii  libstdc++66.1.1-11

calligra-gemini recommends no packages.

calligra-gemini suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: calligra
Source-Version: 1:2.9.11+dfsg-3

We believe that the bug you reported is fixed in the latest version of
calligra, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 840...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated calligra package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 10 Oct 2016 21:04:44 +0200
Source: calligra
Binary: calligra karbon kexi kexi-data kexi-calligrasheets-driver 
kexi-mysql-driver kexi-postgresql-driver kexi-xbase-driver kexi-sybase-driver 
kexi-web-form-widget calligra-reports-web-element calligrasheets calligraplan 
calligrawords calligrawords-data calligrastage calligrastage-data calligraflow 
calligraflow-data braindump calligraactive calligra-libs calligra-semanticitems 
calligra-data okular-backend-odp okular-backend-odt calligraauthor krita-gemini 
calligra-gemini calligra-gemini-data
Architecture: source
Version: 1:2.9.11+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Description:
 braindump  - ideas organizer application for the Calligra Suite
 calligra   - extensive productivity and creative suite
 calligra-data - common shared data for the Calligra Suite
 calligra-gemini - unified interface for stage and words
 calligra-gemini-data - Calligra Gemini - data files
 calligra-libs - common libraries and binaries for the Calligra Suite
 calligra-reports-web-element - web element for Calligra Reports
 calligra-semanticitems - semantic item plugins for the Calligra Suite
 calligraactive - Tablet version of Calligra
 calligraauthor - Authoring tool for 

Bug#840071: marked as done (calligra FTBFS, failure to find postgresql.)

[Debian Bug Tracking System]

Your message dated Mon, 10 Oct 2016 19:20:40 +
with message-id 
and subject line Bug#840071: fixed in calligra 1:2.9.11+dfsg-3
has caused the Debian Bug report #840071,
regarding calligra FTBFS, failure to find postgresql.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
840071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

package: calligra
serverity: serious
version: 1:2.9.11+dfsg-2

Calligra FTBFS because it fails to find postgresql resulting in missing 
files.


I first saw this in when doing a build for raspbian stretch, but it can 
also be seen in the Debian reproducable builds tests and in the 
autobuild results for minor debian architectures. For example from the 
mips64el build log.



 -- Could NOT find PostgreSQL (missing:  PostgreSQL_TYPE_INCLUDE_DIR) (found version 
"9.6.0")

<--snip-->

-
-- The following OPTIONAL packages could NOT be located on your system.
-- Consider installing them to enable more features from this software.
-

<--snip-->

   * libpq
 C application programmer's interface to PostgreSQL
 Required by Kexi PostgreSQL driver

<--snip>

dh_install --list-missing
dh_install: Cannot find (any matches for) "usr/lib/kde4/kexidb_pqxxsqldriver.so" (tried in 
"." and "debian/tmp")
dh_install: kexi-postgresql-driver missing files: 
usr/lib/kde4/kexidb_pqxxsqldriver.so
dh_install: Cannot find (any matches for) "usr/lib/kde4/keximigrate_pqxx.so" (tried in 
"." and "debian/tmp")
dh_install: kexi-postgresql-driver missing files: 
usr/lib/kde4/keximigrate_pqxx.so
dh_install: Cannot find (any matches for) 
"usr/share/kde4/services/calligra/kexidb_pqxxsqldriver.desktop" (tried in "." and 
"debian/tmp")
dh_install: kexi-postgresql-driver missing files: 
usr/share/kde4/services/calligra/kexidb_pqxxsqldriver.desktop
dh_install: Cannot find (any matches for) 
"usr/share/kde4/services/calligra/keximigrate_pqxx.desktop" (tried in "." and 
"debian/tmp")
dh_install: kexi-postgresql-driver missing files: 
usr/share/kde4/services/calligra/keximigrate_pqxx.desktop



I belive this was triggered by the removal of postgresql 9.5 from the 
list of supported postgresql versions. I belive the fix is to add 9.6 to 
the list of known postgresql versions in FindCalligraPostgreSQL.cmake , 
testing (in raspbian) now.
--- End Message ---
--- Begin Message ---
Source: calligra
Source-Version: 1:2.9.11+dfsg-3

We believe that the bug you reported is fixed in the latest version of
calligra, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 840...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated calligra package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 10 Oct 2016 21:04:44 +0200
Source: calligra
Binary: calligra karbon kexi kexi-data kexi-calligrasheets-driver 
kexi-mysql-driver kexi-postgresql-driver kexi-xbase-driver kexi-sybase-driver 
kexi-web-form-widget calligra-reports-web-element calligrasheets calligraplan 
calligrawords calligrawords-data calligrastage calligrastage-data calligraflow 
calligraflow-data braindump calligraactive calligra-libs calligra-semanticitems 
calligra-data okular-backend-odp okular-backend-odt calligraauthor krita-gemini 
calligra-gemini calligra-gemini-data
Architecture: source
Version: 1:2.9.11+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Description:
 braindump  - ideas organizer application for the Calligra Suite
 calligra   - extensive productivity and creative suite
 calligra-data - common shared data for the Calligra Suite
 calligra-gemini - unified interface for stage and words
 calligra-gemini-data - Calligra Gemini - data files
 calligra-libs - common libraries and binaries for the Calligra Suite
 

akonadi-search_16.04.3-1_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 10 Oct 2016 19:38:04 +0200
Source: akonadi-search
Binary: libkf5akonadisearch-dev libkf5akonadisearch-bin 
libkf5akonadisearch-plugins libkf5akonadisearch-data libkf5akonadisearchpim5 
libkf5akonadisearchxapian5 libkf5akonadisearchcore5 libkf5akonadisearchdebug5
Architecture: source
Version: 16.04.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Sandro Knauß 
Description:
 libkf5akonadisearch-bin - Akonadi search library - runtime binaries
 libkf5akonadisearch-data - Akonadi search library - data files
 libkf5akonadisearch-dev - Akonadi search library - development files
 libkf5akonadisearch-plugins - Akonadi search library - runtime plugins
 libkf5akonadisearchcore5 - Akonadi search core library
 libkf5akonadisearchdebug5 - Akonadi search debug library
 libkf5akonadisearchpim5 - Akonadi search library
 libkf5akonadisearchxapian5 - Akonadi search xapian library
Closes: 839990
Changes:
 akonadi-search (16.04.3-1) unstable; urgency=medium
 .
   [ Automatic packaging ]
   * Update symbols files from buildds logs (16.04.2-2).
   * Update build-deps and deps with the info from cmake
 .
   [ Sandro Knauß ]
   * Added fix for Xapian 1.4 (Closes: #839990)
 fix_for_xapian_1.4.patch
 (got from upstream)
   * Add myself to Uploades.
Checksums-Sha1:
 e988f1d1824b080d79fe1ffa187cb2bb1f29b411 3305 akonadi-search_16.04.3-1.dsc
 9c450649925fb904b10d80ff25102bd6b38cfa4b 70344 
akonadi-search_16.04.3.orig.tar.xz
 46bd96e97e1c5bb1dc6ccbe79e31c90fc8480931 7916 
akonadi-search_16.04.3-1.debian.tar.xz
Checksums-Sha256:
 c7391020f413a3fc471113450c5c1c192815987bd8b18f9642a4af2f6b469a2c 3305 
akonadi-search_16.04.3-1.dsc
 15795b655439d911a329e541edc1a754862a8938f1ec30a6f8bb66f84ba12f81 70344 
akonadi-search_16.04.3.orig.tar.xz
 bff4d40b4777eb46c406db38ba101944bd72d3837c710e826bc631650dd50bb0 7916 
akonadi-search_16.04.3-1.debian.tar.xz
Files:
 6ec8710a322a1ca26dc4fbcbac92a3dd 3305 libs optional 
akonadi-search_16.04.3-1.dsc
 0dbbb4423abcbc36331737ee01c0a721 70344 libs optional 
akonadi-search_16.04.3.orig.tar.xz
 8076cfb7e72e75db8c65602d89cefa1a 7916 libs optional 
akonadi-search_16.04.3-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIuBAEBCgAYBQJX+9TOERxoZWZlZUBkZWJpYW4ub3JnAAoJEOOtsAhQYFY2MGQP
/jF8mA8TycB/VAtT5Eo+iRC48LvODGuK/y1PJ+AlpotG37D4+jvqqetDRa8/6eyG
Dxo4+i39XACCfeKvoaaYUNwnkbak9aKSkhDt2oE3KA+13mSDvZKQ1g01w96kR3i6
ikNJ5S0zx+7Lg1V3UorJIZgLzpiYjyQ7vpo+qWV7asm34C2OW18ANVs8n58KNikZ
2OGfzUmx3YJlj2D4wuIQ8sFEh80R2UMPdXbpt8uHOBnSIInq7/gpdjh8bSB3MGAK
MvZBljSAq5OBLZra+niS6IG7Vy/P8zRotNaBh2p8vQP2uSeq8n8nMNudspFRz9xa
9NdcoJ38gCNZvDYDCOnZgVbXcOD8F/4xdKnYPPiVNoRHMW+cumgN+1uZdSZD7iYb
wCsgvhrZQC87beHf/Id/fviieVGU64JOqTVpklHxYIazsuDwcJwUv3zUm9OBAV6Z
cq2FwQAQchK05rbqOoJ/JGPx05GMnVw0Peu4qSONAovVN48kuH0iekjP40a7cHvo
1nstumISb1AkyatsxF9mqo6a6m+7ijbGg+2AFbQroQ+hW2aV9B7ogU3qc0InNrT0
ImCAdOQnhQm0XKl6MS6FcxzjIwLlDBf22dSEcHA6gXIe73sryvqm1rYxzzxrlbCN
57hyzTtEsbWdkHVbK+11bYix/y1dYITABadFASa3xu1y
=2JgO
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Bug#839990: marked as done ([akonadi-server] Latest Upgrade Unstable)

[Debian Bug Tracking System]

Your message dated Mon, 10 Oct 2016 18:34:01 +
with message-id 
and subject line Bug#839990: fixed in akonadi-search 16.04.3-1
has caused the Debian Bug report #839990,
regarding [akonadi-server] Latest Upgrade Unstable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
839990: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: akonadi-server
Version: 4:16.04.3-2
Severity: normal

--- Please enter the report below this line. ---
When exercising emails in KMail2, the server will crash out.
Brings up box to "start" it.
Restarts by itself, box disappears

Note: Can duplicate this by stopping server via akonadiconsole.

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

Debian Release: stretch/sid
  500 unstableftp.us.debian.org 
  500 testing ftp.us.debian.org 
  500 sid linux.dropbox.com 
  500 lucid   ppa.launchpad.net 
1 experimentalftp.us.debian.org 

--- Package information. ---
Depends   (Version) | Installed
===-+-=
akonadi-backend-mysql  (= 4:16.04.3-2)  | 4:16.04.3-2
 OR akonadi-backend-sqlite (= 4:16.04.3-2)  | 4:16.04.3-2
 OR akonadi-backend-postgresql  (= 4:16.04.3-2) | 4:16.04.3-2
libc6 (>= 2.14) | 
libgcc1  (>= 1:3.0) | 
libkf5akonadiprivate5   (= 4:16.04.3-2) | 
libkf5configcore5   (>= 4.97.0) | 
libqt5core5a(>= 5.6.0~beta) | 
libqt5dbus5 (>= 5.4.0~) | 
libqt5gui5(>= 5.6.0~rc) | 
libqt5network5  (>= 5.4.0~) | 
libqt5sql5  (>= 5.4.0~) | 
libqt5widgets5  (>= 5.4.0~) | 
libqt5xml5  (>= 5.4.0~) | 
libstdc++6 (>= 5.2) | 


Package's Recommends field is empty.

Suggests (Version) | Installed
==-+-
akonadi-backend-mysql  (= 4:16.04.3-2) | 4:16.04.3-2
akonadi-backend-postgresql (= 4:16.04.3-2) | 4:16.04.3-2
akonadi-backend-sqlite (= 4:16.04.3-2) | 4:16.04.3-2
--- End Message ---
--- Begin Message ---
Source: akonadi-search
Source-Version: 16.04.3-1

We believe that the bug you reported is fixed in the latest version of
akonadi-search, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 839...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Knauß  (supplier of updated akonadi-search package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 10 Oct 2016 19:38:04 +0200
Source: akonadi-search
Binary: libkf5akonadisearch-dev libkf5akonadisearch-bin 
libkf5akonadisearch-plugins libkf5akonadisearch-data libkf5akonadisearchpim5 
libkf5akonadisearchxapian5 libkf5akonadisearchcore5 libkf5akonadisearchdebug5
Architecture: source
Version: 16.04.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Sandro Knauß 
Description:
 libkf5akonadisearch-bin - Akonadi search library - runtime binaries
 libkf5akonadisearch-data - Akonadi search library - data files
 libkf5akonadisearch-dev - Akonadi search library - development files
 libkf5akonadisearch-plugins - Akonadi search library - runtime plugins
 libkf5akonadisearchcore5 - Akonadi search core library
 libkf5akonadisearchdebug5 - Akonadi search debug library
 libkf5akonadisearchpim5 - Akonadi search library
 libkf5akonadisearchxapian5 - Akonadi search xapian library
Closes: 839990
Changes:
 akonadi-search (16.04.3-1) unstable; urgency=medium
 .
   [ Automatic packaging ]
   * Update symbols files from buildds logs (16.04.2-2).
   * Update build-deps and deps with the info from cmake
 .
   [ Sandro Knauß ]
   * Added fix for Xapian 1.4 (Closes: #839990)
 fix_for_xapian_1.4.patch
 (got from 

Processed: tagging 840243

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 840243 + pending
Bug #840243 [calligra-gemini] calligra-gemini does not launch due to missing 
QtQuick components
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
840243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processing of akonadi-search_16.04.3-1_source.changes

[Debian FTP Masters]

akonadi-search_16.04.3-1_source.changes uploaded successfully to localhost
along with the files:
  akonadi-search_16.04.3-1.dsc
  akonadi-search_16.04.3.orig.tar.xz
  akonadi-search_16.04.3-1.debian.tar.xz

Greetings,

Your Debian queue daemon (running on host franck.debian.org)

Processed: severity of 840071 is serious, tagging 840071

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 840071 serious
Bug #840071 [calligra] calligra FTBFS, failure to find postgresql.
Severity set to 'serious' from 'normal'
> tags 840071 + fixed-upstream pending
Bug #840071 [calligra] calligra FTBFS, failure to find postgresql.
Added tag(s) pending and fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
840071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: [bts-link] source package plasma-workspace

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package plasma-workspace
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #839710 (http://bugs.debian.org/839710)
> # Bug title: plasma-workspace: Comic Plasma Widget causes black screen, 
> restart X necessary
> #  * http://bugs.kde.org/show_bug.cgi?id=370194
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> INVALID
> #  * closed upstream
> tags 839710 + fixed-upstream
Bug #839710 [plasma-workspace] plasma-workspace: Comic Plasma Widget causes 
black screen, restart X necessary
Added tag(s) fixed-upstream.
> usertags 839710 + status-RESOLVED resolution-INVALID
There were no usertags set.
Usertags are now: status-RESOLVED resolution-INVALID.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
839710: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: plasma 5.8 upgrade - white desktop i.s.o. sddm login

[Luc Castermans]

Op 09-10-16 om 22:17 schreef Luc Castermans:

Op 09-10-16 om 21:59 schreef Diederik de Haas:

On zondag 9 oktober 2016 21:50:27 CEST Luc Castermans wrote:

Don't think missing kwin is the problem.

Agreed.


I notice an awfull lot, 1048 kworker processes running. is this normal?

I have 21, so 1048 seems (a bit) excessive.


yep.

But when I:

stop sddm   (via ssh PC2)

give ´startx´ (via ssh PC2), then I get the KDE desktop of root on PC1.

In this KDE desktop I do a ¨ log-out¨, then I get into to a bash shell on PC1.

Now I login as normal user and do a ´ startx´   and get nicely in my KDE 
desktop.


Something in the boot to X and/or kwin/sddm is wrong.



after an aptitude purge sddm, and installing several sddm-theme´s all is 
working again.
(Debian stretch/sid, plasma 5.8, KDE Frameworks 5.26.0)

thanks!!

Luc


<>

Re: Akonadiserver crashing frequently

[inkbottle]

On Friday, October 7, 2016 2:38:16 PM CEST Sandro Knauß wrote:
> Hi,
> 
> I can reproduce the behavior yesterday. As I use gdb to debug and see, the
> problem is xapian. My workaround is to remove  libkf5akonadisearchxapian5:
> 
>  apt remove libkf5akonadisearchxapian5
> 
> I may also maybe possible to downgrade to libxapian22v5.
> 
> The bug is already created for Debian and KDE:
> https://bugs.debian.org/839990
> https://bugs.kde.org/show_bug.cgi?id=363741

It seems the bug is fixed upstream:
https://bugs.kde.org/show_bug.cgi?id=363741#c31

Chris


> 
> Regards,
> 
> sandro
> 
> --
> 
> Am Freitag, 7. Oktober 2016, 11:48:27 CEST schrieb Frank Mehnert:
> > Hi,
> > 
> > I assume I suffer from this bug:
> >   https://bugs.kde.org/show_bug.cgi?id=367846
> > 
> > and I provided a backtrace as requested there. I observe these crashes
> > for a few days and they drive me crazy (running up-to-date Sid).
> > 
> > Now I would like to bit the bullet and recreate the IMAP accounts and
> > 
> > recreate the Akonadi database as mentioned in the above bug:
> >   ".. seems to be resolved for me after deleting all imap accounts in
> >   KMail,
> > 
> > then dropping and recreating the akonadi database, then recreating the
> > imap
> > accounts. Since doing that I've not seen KMail2 lose connection to the
> > akonadi server."
> > 
> > Deleting + re-creating the IMAP accounts is no problem but how to drop +
> > recreate the Akonadi database?
> > 
> > Any help is welcome, getting desperate :-(
> > 
> > Frank

Bug#797999: We are now more than one year later and this critical bug is not fixed

[Eric Valette]

On 10/10/2016 02:50 PM, Maximiliano Curia wrote:

¡Hola Eric!

El 2016-10-10 a las 13:54 +0200, Eric Valette escribió:

I cant' : I probably have no X session running. I have a black screen
remember... Can try specifying display explicitly on console.



Can try to open the lid to see if anything is there but I doubt.


After seeing the sddm blank screen switch to a tty (ctrl-alt-f2) and as
root, or as the sddm user run:
XAUTHORITY=/var/run/sddm/* DISPLAY=:0 xrandr


It worked indeed. Result attached. Identical to kdm case

2 r-x-ceva6380:~->xrandr > xrandr_kdm 2>&1
3 r-x-ceva6380:~->diff xrandr_kdm xrandr_sddm
4 r-x-ceva6380:~->

Consistent with the fact that Xorg.0.log reports the same display and 
all nvidia traces are also identical beween kdm launch and sddm launch. 
So X selects correctly the right display (and I have the small drawing 
on the screen after switching X on that show a displayport icon as when 
I start kdm) before evrything goes dark and monitor led turns off.


So I bet sddm or the sddm greeter greeter is at fault. What else can I 
do to help fixing?


--eric

Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 8192 x 8192
VGA-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 connected (normal left inverted right x axis y axis)
   1440x900  59.96 +  39.96  
DP-4 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 
518mm x 324mm
   1920x1200 59.95*+  59.88  
   1920x1080 60.0059.9450.0023.9760.0560.0050.04  
   1600x1200 60.00  
   1280x1024 75.0260.02  
   1280x720  60.0059.9450.00  
   1152x864  75.00  
   1024x768  75.0360.00  
   800x600   75.0060.32  
   720x576   50.0050.08  
   720x480   59.9460.05  
   640x480   75.0059.9459.93  

Bug#797999: We are now more than one year later and this critical bug is not fixed

[Eric Valette]

On 10/10/2016 02:02 PM, Eric Valette wrote:

On 10/10/2016 01:43 PM, Maximiliano Curia wrote:

¡Hola Eric!



It would be interesting to compare it with the xrandr report of a
running sddm.


I did this in the meantime :

cut -c14- /var/log/Xorg.0.log.old > failing_Xorg.0.log
cut -c14- /var/log/Xorg.0.log > working_Xorg.0.log

Just to surpsed the timing information:

diff working_Xorg.0.log failing_Xorg.0.log

Will double check the file /var/log/Xorg.0.log.old  was really created
when failing...


Yes the Xorg.0.log is created and there is no difference compared to 
working one and DP4 is correctly selected with th correct resolution.


Attached is the sddm log file when it fails

I tried to do an xrandr on tty1 console using xranrd -d :0 but it fails 
both with sddm or kdm so I'm not sure how to have it.



[14:31:11.090] (EE) GREETER: QXcbConnection: Could not connect to display :0
[14:31:40.775] (II) GREETER: Reading from "/usr/share/xsessions/fvwm-crystal.desktop"
[14:31:40.775] (II) GREETER: Reading from "/usr/share/xsessions/fvwm.desktop"
[14:31:40.775] (II) GREETER: Reading from "/usr/share/xsessions/plasma.desktop"
[14:31:40.775] (II) GREETER: Reading from "/usr/share/xsessions/twm.desktop"
[14:31:40.776] (II) GREETER: Reading from "/usr/share/xsessions/failsafe.desktop"
[14:31:40.776] (EE) GREETER: Socket error:  "QLocalSocket::connectToServer: Invalid name"
[14:31:41.461] (WW) GREETER: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
[14:34:19.417] (II) GREETER: Reading from "/usr/share/xsessions/fvwm-crystal.desktop"
[14:34:19.418] (II) GREETER: Reading from "/usr/share/xsessions/fvwm.desktop"
[14:34:19.418] (II) GREETER: Reading from "/usr/share/xsessions/plasma.desktop"
[14:34:19.418] (II) GREETER: Reading from "/usr/share/xsessions/twm.desktop"
[14:34:19.418] (II) GREETER: Reading from "/usr/share/xsessions/failsafe.desktop"
[14:34:19.418] (EE) GREETER: Socket error:  "QLocalSocket::connectToServer: Invalid name"
[14:34:19.998] (WW) GREETER: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
[14:34:30.045] (II) GREETER: Reading from "/usr/share/xsessions/fvwm-crystal.desktop"
[14:34:30.045] (WW) GREETER: QIODevice::write: device not open

Bug#797999: We are now more than one year later and this critical bug is not fixed

[Maximiliano Curia]

¡Hola Eric!

El 2016-10-10 a las 13:54 +0200, Eric Valette escribió:
I cant' : I probably have no X session running. I have a black screen 
remember... Can try specifying display explicitly on console.



Can try to open the lid to see if anything is there but I doubt.


After seeing the sddm blank screen switch to a tty (ctrl-alt-f2) and as root, 
or as the sddm user run:

XAUTHORITY=/var/run/sddm/* DISPLAY=:0 xrandr

if the XAUTHORITY is not expanded as is, you might need to check the output of 
ps ax | grep Xorg


the argument of the -auth parameter is what you want to set as the value of 
XAUTHORITY.


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


signature.asc
Description: PGP signature

Re: Enabling PIE by default for Stretch

[Bálint Réczey]

Hi Maximiliano,

2016-10-10 14:21 GMT+02:00 Maximiliano Curia :
> ¡Hola Niels!
>
> El 2016-10-10 a las 05:44 +, Niels Thykier escribió:
>>
>> Niels Thykier:
>>>
>>> As brought up on the meeting last night, I think we should try to go for
>>> PIE by default in Stretch on all release architectures!  * It is a
>>> substantial hardening feature  * Upstream has vastly reduced the performance
>>> penalty for x86  * The majority of all porters believe their release
>>> architecture isready for it.  * We have sufficient time to solve any
>>> issues or revert if it turns outto be too problematic.
>
>
>>> [...]
>
>
>>>  * Deadline for major concerns:  Fri, 7th of October 2016.
>
>
>> It appears that there were no major concerns.  I will follow up #835148
>> and request PIE by default for the following architectures.
>
>
>> * amd64 * arm64 * armel * armhf * i386 * mips * mips64el * mipsel *
>> ppc64el * s390x
>
>
> Such a change will produce unneeded FTBFS's in libraries using -fPIC (such
> as qt5 and all it's dependencies).
>
> Afaik, -fPIC is stronger than -fPIE, at the same time, -fPIE is incompatible
> with -fPIC and -fPIE makes little sense in shared libraries.
>
> And while a single patch should be trivial, I fear they would be many
> specific ones.

Have you seen the results of the test-rebuild performed with the
changed defaults?

I have put together a page with related links and information where
you can find the rebuild results, too:

 https://wiki.debian.org/Hardening/PIEByDefaultTransition

Cheers,
Balint

Re: Enabling PIE by default for Stretch

[Maximiliano Curia]

¡Hola Niels!

El 2016-10-10 a las 05:44 +, Niels Thykier escribió:

Niels Thykier:
As brought up on the meeting last night, I think we should try to go for 
PIE by default in Stretch on all release architectures! 
 * It is a substantial hardening feature 
 * Upstream has vastly reduced the performance penalty for x86 
 * The majority of all porters believe their release architecture is 
   ready for it. 
 * We have sufficient time to solve any issues or revert if it turns out 
   to be too problematic.



[...]



 * Deadline for major concerns:  Fri, 7th of October 2016.


It appears that there were no major concerns.  I will follow up #835148 
and request PIE by default for the following architectures.


* amd64 
* arm64 
* armel 
* armhf 
* i386 
* mips 
* mips64el 
* mipsel 
* ppc64el 
* s390x


Such a change will produce unneeded FTBFS's in libraries using -fPIC (such as 
qt5 and all it's dependencies).


Afaik, -fPIC is stronger than -fPIE, at the same time, -fPIE is incompatible 
with -fPIC and -fPIE makes little sense in shared libraries.


And while a single patch should be trivial, I fear they would be many specific 
ones.


Happy hacking,
--
"If a thing is done wrong often enough, it becomes right" -- Leahy's Law
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#797999: We are now more than one year later and this critical bug is not fixed

[Eric Valette]

On 10/10/2016 01:43 PM, Maximiliano Curia wrote:

¡Hola Eric!



It would be interesting to compare it with the xrandr report of a
running sddm.


I did this in the meantime :

cut -c14- /var/log/Xorg.0.log.old > failing_Xorg.0.log
cut -c14- /var/log/Xorg.0.log > working_Xorg.0.log

Just to surpsed the timing information:

diff working_Xorg.0.log failing_Xorg.0.log

Will double check the file /var/log/Xorg.0.log.old  was really created 
when failing...



> (--) Log file renamed from "/var/log/Xorg.pid-1448.log" to 
"/var/log/Xorg.0.log"

16c17
< (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 10 13:09:42 2016
---
> (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 10 13:04:16 2016
48c49
< (II) Loader magic: 0x55e29c553dc0
---
> (II) Loader magic: 0x5608e2a4adc0
279c280
< (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 
(/dev/input/event10)

---
> (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 
(/dev/input/event8)

282c283
< (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 
(/dev/input/event11)

---
> (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 
(/dev/input/event9)

285c286
< (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 
(/dev/input/event12)

---
> (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 
(/dev/input/event6)

288c289
< (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 
(/dev/input/event13)

---
> (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 
(/dev/input/event7)

330c331
< (II) config/udev: Adding input device HDA Intel MID Dock Line Out 
(/dev/input/event8)

---
> (II) config/udev: Adding input device HDA Intel MID Dock Mic 
(/dev/input/event10)

333c334
< (II) config/udev: Adding input device HDA Intel MID Headphone 
(/dev/input/event9)

---
> (II) config/udev: Adding input device HDA Intel MID Mic 
(/dev/input/event11)

336c337
< (II) config/udev: Adding input device HDA Intel MID Dock Mic 
(/dev/input/event6)

---
> (II) config/udev: Adding input device HDA Intel MID Dock Line Out 
(/dev/input/event12)

339c340
< (II) config/udev: Adding input device HDA Intel MID Mic 
(/dev/input/event7)

---
> (II) config/udev: Adding input device HDA Intel MID Headphone 
(/dev/input/event13)

473a475,491
> (II) UnloadModule: "synaptics"
> (II) evdev: AlpsPS/2 ALPS DualPoint Stick: Close
> (II) UnloadModule: "evdev"
> (II) evdev: AT Translated Set 2 keyboard: Close
> (II) UnloadModule: "evdev"
> (II) evdev: Logitech Logitech USB Optical Mouse: Close
> (II) UnloadModule: "evdev"
> (II) evdev: CHICONY HP Basic USB Keyboard: Close
> (II) UnloadModule: "evdev"
> (II) evdev: Sleep Button: Close
> (II) UnloadModule: "evdev"
> (II) evdev: Power Button: Close
> (II) UnloadModule: "evdev"
> (II) evdev: Power Button: Close
> (II) UnloadModule: "evdev"
> (II) NVIDIA(GPU-0): Deleting GPU-0
> (II) Server terminated successfully (0). Closing log file.

Bug#797999: We are now more than one year later and this critical bug is not fixed

[Eric Valette]

On 10/10/2016 01:43 PM, Maximiliano Curia wrote:

¡Hola Eric!

El 2016-10-10 a las 13:22 +0200, Eric Valette escribió:

The same : a black screen with external monitor led going off. If I
press ctlr-alt-f1, led goes back up and I can login on console. I
switch back to kdm via dpkg-reconfigure and reboot.


Interesting.


kdm knows how to proceed with external monitor when sddm does not.
Period. So its a bug that for me render sddm totally unusable.


kdm and sddm are completely different beasts, but afaik neither have
specific code for handling an external monitor. Also, this nagging about
kdm is not productive, if you don't care about working on this issue,
please switch to a different display manager.


When you say its a bug in the nvidia driver that is also counter 
productive and annoying for me because without external monitor, the 
same drivers, same version same everything  (except as said external 
monitor) works well with sddm on other laptop. I use kdm example just to 
say that the driver is not at fault. I just want to have sddm working 
but see no progress and on my side, there is not much I can do as I have 
no graphical environment at all as soon as I switch to sddm as a launcher.






xrandr  (once launched via kdm)



Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 8192 x 8192
VGA-0 disconnected (normal left inverted right x axis y axis) DP-0
disconnected (normal left inverted right x axis y axis) DP-1
disconnected (normal left inverted right x axis y axis) DP-2
disconnected (normal left inverted right x axis y axis) DP-3 connected
(normal left inverted right x axis y axis)1440x900  59.96 +
39.96  DP-4 connected primary 1920x1200+0+0 (normal left inverted
right x axis y axis) 518mm x 324mm1920x1200 59.95*+  59.88
1920x1080 60.0059.9450.0023.9760.0560.00
50.04 1600x1200 60.00 1280x1024 75.0260.02
1280x720  60.0059.9450.00 1152x864  75.00
1024x768  75.0360.00 800x600   75.0060.32
720x576   50.0050.08 720x480   59.9460.05
640x480   75.0059.9459.93


It would be interesting to compare it with the xrandr report of a
running sddm.


I cant' : I probably have no X session running. I have a black screen 
remember... Can try specifying display explicitly on console.


Can try to open the lid to see if anything is there but I doubt.

-- eric

Bug#797999: We are now more than one year later and this critical bug is not fixed

[Maximiliano Curia]

¡Hola Eric!

El 2016-10-10 a las 13:22 +0200, Eric Valette escribió:
The same : a black screen with external monitor led going off. If I press 
ctlr-alt-f1, led goes back up and I can login on console. I switch back to kdm 
via dpkg-reconfigure and reboot.


Interesting.

kdm knows how to proceed with external monitor when sddm does not. Period. So 
its a bug that for me render sddm totally unusable.


kdm and sddm are completely different beasts, but afaik neither have specific 
code for handling an external monitor. Also, this nagging about kdm is not 
productive, if you don't care about working on this issue, please switch to a 
different display manager.



xrandr  (once launched via kdm)


Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 8192 x 8192 
VGA-0 disconnected (normal left inverted right x axis y axis) 
DP-0 disconnected (normal left inverted right x axis y axis) 
DP-1 disconnected (normal left inverted right x axis y axis) 
DP-2 disconnected (normal left inverted right x axis y axis) 
DP-3 connected (normal left inverted right x axis y axis) 
   1440x900  59.96 +  39.96  
DP-4 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 
518mm x 324mm 
   1920x1200 59.95*+  59.88  
   1920x1080 60.00    59.94    50.00    23.97    60.05    60.00    50.04  
   1600x1200 60.00  
   1280x1024 75.02    60.02  
   1280x720  60.00    59.94    50.00  
   1152x864  75.00  
   1024x768  75.03    60.00  
   800x600   75.00    60.32  
   720x576   50.00    50.08  
   720x480   59.94    60.05  
   640x480   75.00    59.94    59.93 


It would be interesting to compare it with the xrandr report of a running 
sddm.


Happy hacking,
--
"It takes three times the effort to find and fix bugs in system test than when
done by the developer. It takes ten times the effort to find and fix bugs in
the field than when done in system test. Therefore, insist on unit tests by
the developer"
-- Larry Bernstein
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#840300: sddm: conffiles not marked in /usr/share thus cannot reliably customize

[Maximiliano Curia]

¡Hola Boyuan!

El 2016-10-10 a las 19:00 +0800, Boyuan Yang escribió:
Package: sddm 
Version: 0.13.0-1 
Severity: normal


There are a lot of configuration files in /usr/share/sddm/* but edits will be 
overridden after the upgrade.


Please consider writing them (at least some of them, such as 
/usr/share/sddm/scripts/* and /usr/share/sddm/themes/*/*.conf.*) into 
debian/conffiles, or patch upstream and let sddm accept multiple config files 
(both in /etc/sddm/ and /usr/share/sddm).


You are not supposed to have to modify these files. That is, for the themes,
please create a new theme and for the scripts, please use the Xsession.d 
files, or create an /etc/sddm.conf that points the 
DisplayCommand/DisplayStopCommand to the corresponding local scripts.


The configuration keys for the /etc/sddm.conf are:
[X11]
DisplayCommand=/usr/share/sddm/scripts/Xsetup
DisplayStopCommand=/usr/share/sddm/scripts/Xstop

Please refer to sddm.conf(5) for more information.


That would greatly help those who want to customize sddm via config files.


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: PGP signature

Bug#797999: We are now more than one year later and this critical bug is not fixed

[Eric Valette]

  
  
On 10/10/2016 11:48 AM, Maximiliano
  Curia wrote:


  What happens if you use the maui sddm theme?
  


The same : a black screen with external monitor led going off. If I
press ctlr-alt-f1, led goes back up and I can login on console. I
switch back to kdm via dpkg-reconfigure and reboot.
kdm knows how to proceed with external monitor when sddm does not.
Period. So its a bug that for me render sddm totally unusable.


xrandr  (once launched via kdm)

Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 8192 x 8192
VGA-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 connected (normal left inverted right x axis y axis)
   1440x900  59.96 +  39.96  
DP-4 connected primary 1920x1200+0+0 (normal left inverted right x
axis y axis) 518mm x 324mm
   1920x1200 59.95*+  59.88  
   1920x1080 60.00    59.94    50.00    23.97    60.05   
60.00    50.04  
   1600x1200 60.00  
   1280x1024 75.02    60.02  
   1280x720  60.00    59.94    50.00  
   1152x864  75.00  
   1024x768  75.03    60.00  
   800x600   75.00    60.32  
   720x576   50.00    50.08  
   720x480   59.94    60.05  
   640x480   75.00    59.94    59.93  




  

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 295.20  (pbuilder@cake)  Wed Feb 15 20:18:16 UTC 
2012

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 1.0  (buildmeister@builder75)  Fri Mar 12 01:42:27 
PST 2010

Section "ServerLayout"

#InputDevice"Mouse0" "CorePointer"
Identifier "Layout0"
Screen  0  "Screen0" 0 0
InputDevice"Keyboard0" "CoreKeyboard"
InputDevice"Mouse0" "CorePointer"
InputDevice"Keyboard0" "SendCoreEvent"
Option "Xinerama" "0"
#Option"AutoAddDevices" "false"
EndSection

Section "InputDevice"

# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "InputDevice"

# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

# generated from default
Identifier "Keyboard0"
Driver "evdev"
Option "Name" "CHICONY HP Basic USB Keyboard"
#Option"Device" 
"/dev/input/by-id/usb-CHICONY_HP_Basic_USB_Keyboard-event-kbd"
EndSection

Section "InputClass"
Identifier "touchpad catchall"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Driver "synaptics"
Option "LeftEdge"   "100"
Option "RightEdge"  "1750"
Option "TopEdge""100"
Option "BottomEdge" "1250"
Option "FingerLow"  "12"
Option "FingerHigh" "14"
Option "FingerPress""127"
Option "MaxTapTime" "180"
Option "MaxTapMove" "107"
Option "MaxDoubleTapTime"   "180"
Option "SingleTapTimeout"   "180"
Option "ClickTime"  "100"
Option "FastTaps"   "0"
Option "EmulateMidButtonTime"   "75"
Option "EmulateTwoFingerMinZ"   "139"
Option "EmulateTwoFingerMinW"   "7"
Option "VertScrollDelta""44"
Option "HorizScrollDelta"   "44"
Option "VertEdgeScroll" "1"
Option "HorizEdgeScroll""1"
Option "CornerCoasting" "0"
Option "VertTwoFingerScroll""0"
Option "HorizTwoFingerScroll"   "0"
Option "MinSpeed"   "1"
Option "MaxSpeed"   "1.75"
Option "AccelFactor""0.0075"
Option "TrackstickSpeed"

Bug#840300: sddm: conffiles not marked in /usr/share thus cannot reliably customize

[Boyuan Yang]

Package: sddm
Version: 0.13.0-1
Severity: normal

There are a lot of configuration files in /usr/share/sddm/* but edits will be
overridden after the upgrade.

Please consider writing them (at least some of them, such as
/usr/share/sddm/scripts/* and /usr/share/sddm/themes/*/*.conf.*) into
debian/conffiles, or patch upstream and let sddm accept multiple config files
(both in /etc/sddm/ and /usr/share/sddm).

That would greatly help those who want to customize sddm via config files.

Thanks!



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

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

Versions of packages sddm depends on:
ii  adduser 3.115
ii  debconf [debconf-2.0]   1.5.59
ii  libc6   2.24-3
ii  libgcc1 1:6.2.0-5
ii  libpam0g1.1.8-3.3
ii  libqt5core5a5.6.1+dfsg-3+b1
ii  libqt5dbus5 5.6.1+dfsg-3+b1
ii  libqt5gui5  5.6.1+dfsg-3+b1
ii  libqt5network5  5.6.1+dfsg-3+b1
ii  libqt5qml5  5.6.1-11
ii  libqt5quick55.6.1-11
ii  libstdc++6  6.2.0-5
ii  libsystemd0 231-9
ii  libxcb-xkb1 1.12-1
ii  libxcb1 1.12-1
ii  qml-module-qtquick2 5.6.1-11
ii  sddm-theme-breeze [sddm-theme]  4:5.8.0-1

Versions of packages sddm recommends:
ii  libpam-systemd  231-9

Versions of packages sddm suggests:
ii  libpam-kwallet5  5.8.0-1

-- debconf information:
* shared/default-x-display-manager: sddm
  sddm/daemon_name: /usr/bin/sddm

Bug#840141: kwin-x11: Short freeze when showing multiple tray notifications

[Maximiliano Curia]

¡Hola Alex!

El 2016-10-08 a las 22:32 +0300, Alex Dănilă escribió:
Package: kwin-x11 
Version: 4:5.7.4-1 
Severity: normal


The entire screens freeze for a couple of seconds (3-4, but sometimes seemed 
close to 10) everytime notifications from the tray are about to scroll down or 
disappear. This only affects drawing of screen content, it doesn't affect sound 
or cursor motion.


If relevant, the particular tray notifications are about bluetooth devices, 
I'll attach a screenshot with this. 
The particular order is like this:
-two messages (M1 - connection deactivated, M2 - connection timed out) appear 
one above the other 
-2-3 seconds pass 
-freeze 
-2 
-freeze ends 
-M1 disappears, M2 animates going down 
-messages reappear and animate again, but without freezes.



I'll send a screenshot after the bug is created, and if possible a recording.


As reported it seems that the issue is bluetooth specific, and it might be 
caused by an underlying issue of the bluetooth kernel module or hardware 
device. In my limited tests I couldn't reproduce this behaviour in my laptop.


Would it be feasible for you to test this multiple bluetooth notifications 
in a different desktop environment in order to rule out a kernel/hardware 
issue?


Can you reproduce this triggering a different type of notifications?

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


signature.asc
Description: PGP signature

Bug#797999: We are now more than one year later and this critical bug is not fixed

[eric2.valette]

On 10/10/2016 11:48 AM, Maximiliano Curia wrote:

¡Hola eric2.valette!

First of all, the bug is not critical because it only affects a very 
specific setup for a particular video driver.

A docked station using a nvidia driver is not that uncommon I guess...


I suspect that the bug is not present in sddm but in the nvidia 
driver, triggered by sddm by trying to use composite on the video 
output as is left by the X driver initialization.

The bug is not only in the video driver as kdm works...


El 2016-10-10 a las 11:01 +0200, eric2.vale...@orange.com escribió:
Just updated to kde 5.8, and lib  5.26.0 and it still does not 
correctly detect my external screen when lid is closed.


What happens if you use the maui sddm theme?

To test this you'll need to install sddm-theme-maui, and create/modify 
your /etc/sddm.conf to include:


[Theme]
Current=maui

The breeze theme starts sddm in composite mode, which might not be 
correctly initialized for your video card by default in your 
particular setup.

Will try and report.


This kind of disclaimers are useless in public mails, please avoid 
adding them. Consider using a different mail account if you can't 
remove it. 
It is automaically inserted fater I send the mail I cannot do anyting 
agains it. Will try another mail account.


-- eric


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

Bug#797999: We are now more than one year later and this critical bug is not fixed

[Maximiliano Curia]

¡Hola eric2.valette!

First of all, the bug is not critical because it only affects a very specific 
setup for a particular video driver.


I suspect that the bug is not present in sddm but in the nvidia driver, 
triggered by sddm by trying to use composite on the video output as is left by 
the X driver initialization.


El 2016-10-10 a las 11:01 +0200, eric2.vale...@orange.com escribió:
Just updated to kde 5.8, and lib  5.26.0 and it still does not 
correctly detect my external screen when lid is closed.


What happens if you use the maui sddm theme?

To test this you'll need to install sddm-theme-maui, and create/modify your 
/etc/sddm.conf to include:


[Theme]
Current=maui

The breeze theme starts sddm in composite mode, which might not be correctly 
initialized for your video card by default in your particular setup.



I still need kdm!


kdm is gone, dropped upstream and removed from the archive, if you don't want 
to use sddm, I would suggest lightdm.


This message and its attachments may contain confidential or privileged information that may be protected by law; 
they should not be distributed, used or copied without authorisation. 
If you have received this email in error, please notify the sender and delete this message and its attachments. 
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. 


This kind of disclaimers are useless in public mails, please avoid adding 
them. Consider using a different mail account if you can't remove it.


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


signature.asc
Description: PGP signature

Bug#840293: pkg-kde-tools: pkgkde-symbolshelper broken by perl 5.24

[Andreas Beckmann]

Package: pkg-kde-tools
Version: 0.15.23
Severity: important

Hi,

this command worked in the pocl package a month ago:

pkgkde-symbolshelper batchpatch -v 0.13-6~llvm3.8+gcc6 
pocl_unstable_logs/pocl_0.13-7_*build

(and still works in a stable chroot, even with
pkg-kde-tools 0.15.23, but no longer works in stretch)

but now it fails with

[...]
---
| Processing libpocl1 package |
---
Patching symbol file 'debian/libpocl1.symbols' with supplied patches ...
pkgkde-symbolshelper: error: reopen stdout: Bad file descriptor
pkgkde-symbolshelper: error: libpocl1 patching FAILED. Will NOT continue.


Andreas

Bug#797999: We are now more than one year later and this critical bug is not fixed

[eric2.valette]

Just updated to kde 5.8, and lib  5.26.0 and it still does not correctly 
detect my external screen when lid is closed.I still need kdm!


-- eric


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

Fixed: chroot-installation_sid_install_kde-full/1257

[jenkins]

See 
https://jenkins.debian.net/job/chroot-installation_sid_install_kde-full/1257//console
 or just 
https://jenkins.debian.net/job/chroot-installation_sid_install_kde-full/1257/ 
for more information.