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

2018-05-01 Thread 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


kbackup_18.04.0-1_amd64.changes is NEW

2018-05-01 Thread Debian FTP Masters
binary:kbackup is NEW.
binary:kbackup is NEW.
source:kbackup 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.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports



Processing of kbackup_18.04.0-1_amd64.changes

2018-05-01 Thread Debian FTP Masters
kbackup_18.04.0-1_amd64.changes uploaded successfully to localhost
along with the files:
  kbackup_18.04.0-1.dsc
  kbackup_18.04.0.orig.tar.xz
  kbackup_18.04.0.orig.tar.xz.asc
  kbackup_18.04.0-1.debian.tar.xz
  kbackup-dbgsym_18.04.0-1_amd64.deb
  kbackup_18.04.0-1_amd64.buildinfo
  kbackup_18.04.0-1_amd64.deb

Greetings,

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



kbackup_18.04.0-1_source.changes REJECTED

2018-05-01 Thread Debian FTP Masters


Source-only uploads to NEW are not allowed.

binary:kbackup is NEW.
source:kbackup is NEW.

===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.



Processing of kbackup_18.04.0-1_source.changes

2018-05-01 Thread Debian FTP Masters
kbackup_18.04.0-1_source.changes uploaded successfully to localhost
along with the files:
  kbackup_18.04.0-1.dsc
  kbackup_18.04.0.orig.tar.xz
  kbackup_18.04.0.orig.tar.xz.asc
  kbackup_18.04.0-1.debian.tar.xz
  kbackup_18.04.0-1_source.buildinfo

Greetings,

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



Bug#897388: Logs accessed files, etc. to syslog

2018-05-01 Thread Anthony DeRobertis
Package: kactivitymanagerd
Version: 5.12.1-1
Severity: important

Similar (but nowhere near as bad as) bug #805399, ActivityManager is
logging files I access to the systemd journal & syslog. Some examples:

May  1 16:43:33 Zia org.kde.ActivityManager[4152]: Creating the cache for:  
"applications:tora.desktop"
May  1 16:43:33 Zia org.kde.ActivityManager[4152]: Already in database?  true
May  1 16:43:33 Zia org.kde.ActivityManager[4152]:   First update :  
QDateTime(2016-10-11 13:24:44.000 EDT Qt::TimeSpec(LocalTime))
May  1 16:43:33 Zia org.kde.ActivityManager[4152]:Last update :  
QDateTime(2018-05-01 14:48:00.000 EDT Qt::TimeSpec(LocalTime))
May  1 16:43:33 Zia org.kde.ActivityManager[4152]: After the adjustment
May  1 16:43:33 Zia org.kde.ActivityManager[4152]:  Current score :  4.5649
May  1 16:43:33 Zia org.kde.ActivityManager[4152]:   First update :  
QDateTime(2016-10-11 13:24:44.000 EDT Qt::TimeSpec(LocalTime))
May  1 16:43:33 Zia org.kde.ActivityManager[4152]:Last update :  
QDateTime(2018-05-01 14:48:00.000 EDT Qt::TimeSpec(LocalTime))
May  1 16:43:33 Zia org.kde.ActivityManager[4152]: Interval length is  0
May  1 16:43:33 Zia org.kde.ActivityManager[4152]:  New score :  5.5649
May  1 16:43:33 Zia org.kde.ActivityManager[4152]: ResourceScoreUpdated: 
"beff6de3-1dc1-42b8-ab3d-2510f77b2ddf" "org.kde.krunner" 
"applications:tora.desktop"
May  1 17:33:32 Zia org.kde.ActivityManager[4152]: Creating the cache for:  
"/mnt/Haruhi/netadmin/HPM Retention Comparison EXPORT.pdf"
May  1 17:33:32 Zia org.kde.ActivityManager[4152]: Already in database?  true
May  1 17:33:32 Zia org.kde.ActivityManager[4152]:   First update :  
QDateTime(2018-05-01 17:32:38.000 EDT Qt::TimeSpec(LocalTime))
May  1 17:33:32 Zia org.kde.ActivityManager[4152]:Last update :  
QDateTime(2018-05-01 17:32:38.000 EDT Qt::TimeSpec(LocalTime))
May  1 17:33:32 Zia org.kde.ActivityManager[4152]: After the adjustment
May  1 17:33:32 Zia org.kde.ActivityManager[4152]:  Current score :  0
May  1 17:33:32 Zia org.kde.ActivityManager[4152]:   First update :  
QDateTime(2018-05-01 17:32:38.000 EDT Qt::TimeSpec(LocalTime))
May  1 17:33:32 Zia org.kde.ActivityManager[4152]:Last update :  
QDateTime(2018-05-01 17:32:38.000 EDT Qt::TimeSpec(LocalTime))
May  1 17:33:32 Zia org.kde.ActivityManager[4152]: Interval length is  21
May  1 17:33:32 Zia org.kde.ActivityManager[4152]:  New score :  0.35
May  1 17:33:32 Zia org.kde.ActivityManager[4152]: ResourceScoreUpdated: 
"beff6de3-1dc1-42b8-ab3d-2510f77b2ddf" "okular" "/mnt/Haruhi/netadmin/HPM 
Retention Comparison EXPORT.pdf"

while hopefully the database itself is in my home director and
mode go-rw, the same can't be said for syslog and journal. This violates
user privacy on a multi-user system as the sysadmin is expected to read
syslog, but respect the privacy of $HOME. In addition, syslog and
journal are available to members of group adm, who may not have root.

From the journal, it appears that kactivymanagerd may be speweing this
to stdout, which is ultimately being picked up by systemd (I think
that's what _TRANSPORT of stdout means):

{
   "_EXE" : "/usr/bin/dbus-daemon",
   "_GID" : "1000",
   "__CURSOR" : "[[redacted]]",
   "_SYSTEMD_OWNER_UID" : "1000",
   "_COMM" : "dbus-daemon",
   "_UID" : "1000",
   "_SYSTEMD_CGROUP" : 
"/user.slice/user-1000.slice/user@1000.service/dbus.service",
   "_MACHINE_ID" : "[[redacted]]",
   "_HOSTNAME" : "Zia",
   "_SYSTEMD_USER_SLICE" : "-.slice",
   "_BOOT_ID" : "[[redacted]]",
   "MESSAGE" : "Creating the cache for:  \"/mnt/Haruhi/netadmin/HPM Retention 
Comparison EXPORT.pdf\"",
   "__MONOTONIC_TIMESTAMP" : "1231383365390",
   "_CAP_EFFECTIVE" : "0",
   "_SYSTEMD_INVOCATION_ID" : "[[redacted]]",
   "__REALTIME_TIMESTAMP" : "1525210358022301",
   "_CMDLINE" : "/usr/bin/dbus-daemon --session --address=systemd: --nofork 
--nopidfile --systemd-activation --syslog-only",
   "_TRANSPORT" : "stdout",
   "SYSLOG_IDENTIFIER" : "org.kde.ActivityManager",
   "_SYSTEMD_USER_UNIT" : "dbus.service",
   "PRIORITY" : "4",
   "_SYSTEMD_SLICE" : "user-1000.slice",
   "_SELINUX_CONTEXT" : "unconfined\n",
   "_AUDIT_SESSION" : "6",
   "_PID" : "4152",
   "_STREAM_ID" : "[[redacted]]",
   "_AUDIT_LOGINUID" : "1000",
   "_SYSTEMD_UNIT" : "user@1000.service"
}


-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'testing'), (200, 'unstable'), (150, 'stable'), (100, 'experimental'), (1, 
'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages kactivitymanagerd depends on:
ii  kio  5.44.0-2
ii  libc62.27-3
ii  libkf5co

Bug#897385: Existence of Dropbox plugin is not documented

2018-05-01 Thread James Lu
Package: src:dolphin-plugins
Version: 4:18.04.0-1
Severity: minor

Dear maintainers,

The dolphin-plugins package provides a Dropbox integration plugin[1],
which works well but isn't documented in e.g. the package description.
This makes it fairly difficult to find.

Because Dropbox is not technically a VCS, perhaps it would also make
sense to split it into a separate package for better searchability.

Best,
James

[1]: https://packages.debian.org/sid/amd64/dolphin-plugins/filelist



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

2018-05-01 Thread Alexander Kernozhitsky
Package: sddm
Version: 0.17.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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.

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

Kernel: Linux 4.15.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (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.117
ii  debconf [debconf-2.0]   1.5.66
ii  libc6   2.27-3
ii  libgcc1 1:8-20180425-1
ii  libpam0g1.1.8-3.7
ii  libqt5core5a5.10.1+dfsg-5
ii  libqt5dbus5 5.10.1+dfsg-5
ii  libqt5gui5  5.10.1+dfsg-5
ii  libqt5network5  5.10.1+dfsg-5
ii  libqt5qml5  5.10.1-4
ii  libqt5quick55.10.1-4
ii  libstdc++6  8-20180425-1
ii  libsystemd0 238-4
ii  libxcb-xkb1 1.13-1
ii  libxcb1 1.13-1
ii  qml-module-qtquick2 5.10.1-4
ii  x11-common  1:7.7+19
ii  xserver-xorg [xserver]  1:7.7+19

Versions of packages sddm recommends:
ii  libpam-systemd   238-4
ii  sddm-theme-debian-maui [sddm-theme]  0.17.0-1

Versions of packages sddm suggests:
ii  libpam-kwallet5   5.12.1-1
pn  qtvirtualkeyboard-plugin  

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


libkf5libkleo_17.12.3-2_source.changes ACCEPTED into unstable

2018-05-01 Thread Debian FTP Masters


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 01 May 2018 14:40:30 +0200
Source: libkf5libkleo
Binary: libkf5libkleo-data libkf5libkleo-dev libkf5libkleo5
Architecture: source
Version: 4:17.12.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Description:
 libkf5libkleo-data - KDE PIM cryptographic library, data files
 libkf5libkleo-dev - KDE PIM cryptographic library, devel files
 libkf5libkleo5 - KDE PIM cryptographic library
Changes:
 libkf5libkleo (4:17.12.3-2) unstable; urgency=medium
 .
   * Team upload.
   * Update symbols file from logs of buildds.
   * Remove the alternative libqgpgme7-dev build dependency, as it does not
 exist.
   * Remove the unused 'testsuite' autopkgtest.
   * Remove the alternative libgpgme7-dev dependency in libkf5libkleo-dev,
 as it does not exist.
   * Bump Standards-Version to 4.1.4, no changes required.
   * Remove the unused ${shlibs:Depends} substvar in libkf5libkleo-dev.
Checksums-Sha1:
 769c53215a13190dcc1da6f8b444291e5a9692f2 2933 libkf5libkleo_17.12.3-2.dsc
 497ec8e2a2cba981a4b60b5b2a2e9e5a74470ab6 16984 
libkf5libkleo_17.12.3-2.debian.tar.xz
 22d03a19738c3b486f2aa5fdcf185342dba7c4ba 19250 
libkf5libkleo_17.12.3-2_source.buildinfo
Checksums-Sha256:
 519ec14f7bc475b1ef1cfe710024f9da766bb96a940d9c3ad14073ee2357acfc 2933 
libkf5libkleo_17.12.3-2.dsc
 3ccf4bc3eb920d5d2c3310ee1339bc956780f2d8647335e6e3a4b3b5f4833ee2 16984 
libkf5libkleo_17.12.3-2.debian.tar.xz
 21091b2bf22c3e289a936a79a551910aa653eaa010a983eb5455106ee934d39b 19250 
libkf5libkleo_17.12.3-2_source.buildinfo
Files:
 7b18d05d4a836e45f66c96d6443f7a1f 2933 libs optional libkf5libkleo_17.12.3-2.dsc
 fb5b30a53167cb037195d50ed307050b 16984 libs optional 
libkf5libkleo_17.12.3-2.debian.tar.xz
 584897fec269919ed37d65a0a3905cd4 19250 libs optional 
libkf5libkleo_17.12.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAlroYGsACgkQLRkciEOx
P02uaA/9HdkpEB+KrF9WqekmaEY7aslrBTAEye46dcECU5rf7E9a4Brp1SEvePld
Ywf1CipXPH+X084IsnYlwbv7K8FRy3LQIL/rZoJj8aSd921aXmr9FPhhqYePdHP+
6VRfQXcp9RDxqK8tdKZ/YqOqLbMNTpc3/BseZuM71cBe6i4SOHiXoHAP2A3OmPT7
eVFC88mD/T3AYWpyLMvXsnbppJHZwDJa6df5LF6AtljP0WZxeIUxvWbT3595qSNb
RrLZ5QJMNohi/9tCqNuEc/x/AF4NY/6Ef+BoxSqoZCjCBdCIDQHw657Rolt5lfiI
PtpASf0llXouwvY3h+s66rGQiwmAleORVWdEAehSb+bCvpG9WwLbk3n1Z55zrdqx
Cz+v/8XIsRNhMq9+G7LypxwD4mRq1cSYJ8AMvkdyS8cIxvz3F6g0q6Q2q+eJQCIe
gJVjlCeYS2OAvY+y+cR3Mne4hDugbmQBeMkM4oI5AFsKWBIpIVK3cm4vx7ImFP1/
sJcpFi1vL33ODEaxNMRpGjujSs2QJi88IAGoc8GCSWnhIQk/sBduB+sUz1KF0F7N
okcYR1DgGwBQwV1tBYD6k+w19iaXNLDHO4PTFhUilTSYMMe/DD9lr7hQNhQ219xk
HyrI9GZLklkJyEdBEOP0UlPV84sPbXgh7w2yBNc8Eyq3pypKo4s=
=f/VI
-END PGP SIGNATURE-


Thank you for your contribution to Debian.



Bug#896658: qtbase-opensource-src FTBFS on alpha: ambiguous call of atime()

2018-05-01 Thread Lisandro Damián Nicanor Pérez Meyer
Hi Michael! Sorry for the delay.


El lunes, 23 de abril de 2018 06:27:34 -03 Michael Cree escribió:
> Source: qtbase-opensource-src
> Version: 5.10.1+dfsg-5
> Severity: important
> Justification: fails to build from source (but built in past)
> User: debian-al...@lists.debian.org
> Usertags: ftbfs
> Tags: patch
> 
> qtbase-opensource-src FTBFS on Alpha [1] due to an ambiguous
> resolution of the overloaded call to atime() with definitions of
> atime() at lines 246, 254 and 299 in
> src/corelib/io/qfilesystemengine_unix.cpp. The one at line 299
> is declared as:
> 
> Q_DECL_UNUSED static typename std::enable_if<(&T::st_atimensec, true)
> ...
> 
> which I guess (I don't know C++ very well) means that if the field
> st_atimensec is present then include that declaration of atime().  On
> Alpha Linux this field is present in the struct stat declaration in
> the header file (sys/stat.h) inside a union declaration, which looks
> to be a unique definition of struct stat amongst the Linicies.  So
> this definition of atime() at line 299 applies on Alpha Linux and
> conflicts with one of the earlier definitions at lines 246 and 254.
> 
> I don't know if this is a bug in the header file (i.e. glibc) or
> present for historical reasons (Alpha Linux being the first 64-bit
> Linux does have some idiosyncrasies not repeated in later 64-bit
> Linicies), nevertheless I attach a patch that disables the second
> confounding definition of atime() at line 299 on Alpha only.  With
> the patch qtbase-opensource-src builds to completion on Alpha.

Thanks for the very clear explanation! There are two possible ways out here:

1) Preferred by us Qt maintainers: file a bug in bugreports.qt.io and send us 
the link so we can follow it. Notice that I'm asking you to do it because you 
are the alpha porter, so you will be the right one to reply to possible 
upstream's questions. Of course as soon as you send us the bug link I'll 
subscribe to it to follow it and try to help if possible.

I can also push this simple patch to upstream's gerrit once the bug is filed 
(had it be more involved I would need to ask you to do it because of 
copyright, but in this case it's pretty straightforward).

Why is this preferable? Because upstream tends to know if the solution is 
right or if it should be fixed in, let's say, glibc. They also know the code 
quirks much better than us and will probably notice if this affects something 
else.

2) We ship a Debian delta for this. Doable, but definitely not the best thing.

So, pick one ;-) (pun intended :-P)

Cheers, Lisandro.

-- 
Trabaja como si no necesitaras el dinero.
Ama como si nunca hubieses sido herido.
Baila como si nadie estuviera mirando.
Canta como si nadie escuchara.
Vive como si fuera el Cielo en la Tierra.
  Anónimo

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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


Processing of libkf5libkleo_17.12.3-2_source.changes

2018-05-01 Thread Debian FTP Masters
libkf5libkleo_17.12.3-2_source.changes uploaded successfully to localhost
along with the files:
  libkf5libkleo_17.12.3-2.dsc
  libkf5libkleo_17.12.3-2.debian.tar.xz
  libkf5libkleo_17.12.3-2_source.buildinfo

Greetings,

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