Bug#881383: systemsettings: Touchpad settings don't actually work

2017-11-10 Thread Ben Longbons
Package: systemsettings
Version: 4:5.8.4-1
Severity: normal

Dear Maintainer,

In Hardware->Input Devices->Touchpad->Enable/Disable Touchpad:

There is a checkbox "Disable touchpad while typing". However,
even when unchecked (and the system restarted), the touchpad
still disables itself whenever any key is pressed.


Debugging on IRC produced the following observations:

evtest *does* show touchpad events when keys are pressed
but xev does not
and libinput-debug-events does not
(libinput-debug-events --disable-dwt does, however).

libinput-list-devices mentions: Disable-w-typing: enabled

So apparently this is a driver switch or something? Where KDE is only
applying the settings to the driver that isn't actually used anymore.


-- System Information:
Debian Release: 9.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages systemsettings depends on:
ii  kio   5.28.0-2
ii  libc6 2.24-11+deb9u1
ii  libkf5auth5   5.28.0-2
ii  libkf5completion5 5.28.0-1
ii  libkf5configcore5 5.28.0-2
ii  libkf5configgui5  5.28.0-2
ii  libkf5configwidgets5  5.28.0-2
ii  libkf5coreaddons5 5.28.0-2
ii  libkf5dbusaddons5 5.28.0-1
ii  libkf5i18n5   5.28.0-2
ii  libkf5iconthemes5 5.28.0-2
ii  libkf5itemviews5  5.28.0-1
ii  libkf5kcmutils5   5.28.0-2
ii  libkf5khtml5  5.28.0-2
ii  libkf5kiowidgets5 5.28.0-2
ii  libkf5service-bin 5.28.0-1
ii  libkf5service55.28.0-1
ii  libkf5widgetsaddons5  5.28.0-3
ii  libkf5windowsystem5   5.28.0-2
ii  libkf5xmlgui5 5.28.0-1
ii  libqt5core5a  5.7.1+dfsg-3+b1
ii  libqt5dbus5   5.7.1+dfsg-3+b1
ii  libqt5gui55.7.1+dfsg-3+b1
ii  libqt5widgets55.7.1+dfsg-3+b1
ii  libstdc++66.3.0-18

systemsettings recommends no packages.

systemsettings suggests no packages.

-- no debconf information



Bug#860778: okular: Often fails to open via symlinks

2017-04-19 Thread Ben Longbons
Package: okular
Version: 4:16.08.2-1+b1
Severity: normal

Dear Maintainer,

The following perfectly-legitimate, common, use of symlinks works with
*all* programs that don't go out of their way to *break* it.

Okular manages to do this wrong, presumably by trying to do filesystem
operations without, you know, talking to the filesystem.


#!/bin/sh
set -e
mkdir -p /tmp/okular-bug/
cd /tmp/okular-bug/
mkdir -p bar/baz
echo 'Hello, World!' > bar/hello.txt
ln -sf bar/baz foo
cat bar/hello.txt
okular bar/hello.txt
cat foo/../hello.txt
okular foo/../hello.txt

-Ben


-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386, x32, arm64

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

Versions of packages okular depends on:
ii  kde-runtime 4:16.08.3-2
ii  libc6   2.24-10
ii  libfreetype62.6.3-3.1
ii  libjpeg62-turbo 1:1.5.1-2
ii  libkdecore5 4:4.14.26-1
ii  libkdeui5   4:4.14.26-1
ii  libkexiv2-114:15.04.3-1
ii  libkio5 4:4.14.26-1
ii  libkparts4  4:4.14.26-1
ii  libkprintutils4 4:4.14.26-1
ii  libkpty44:4.14.26-1
ii  libokularcore7  4:16.08.2-1+b1
ii  libphonon4  4:4.9.0-4
ii  libpoppler-qt4-40.48.0-2
ii  libqca2 2.1.1-4+b2
ii  libqimageblitz4 1:0.0.6-4+b2
ii  libqmobipocket1 4:16.08.0-1
ii  libqt4-dbus 4:4.8.7+dfsg-11
ii  libqt4-declarative  4:4.8.7+dfsg-11
ii  libqt4-svg  4:4.8.7+dfsg-11
ii  libqt4-xml  4:4.8.7+dfsg-11
ii  libqtcore4  4:4.8.7+dfsg-11
ii  libqtgui4   4:4.8.7+dfsg-11
ii  libsolid4   4:4.14.26-1
ii  libspectre1 0.2.8-1
ii  libstdc++6  7-20170407-1
ii  phonon  4:4.9.0-4
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages okular recommends:
ii  cups-bsd  2.2.1-8

Versions of packages okular suggests:
ii  ghostscript9.20~dfsg-3
ii  jovie  4:16.08.0-1+b1
ii  okular-extra-backends  4:16.08.2-1+b1
ii  poppler-data   0.4.7-8
ii  texlive-binaries   2016.20160513.41080.dfsg-2
pn  unrar  

-- no debconf information



Bug#848523: More info

2017-01-23 Thread Ben Longbons
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:

00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Richland [Radeon HD 8610G] [1002:990f] (prog-if 00 [VGA
controller])
Subsystem: Hewlett-Packard Company Richland [Radeon HD 8610G]
[103c:216b]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- 
Kernel driver in use: radeon
Kernel modules: radeon



Bug#848602: Depends: nodejs-legacy

2016-12-18 Thread Ben Longbons
Package: libkf5purpose-bin
Version: 1.1-3
Severity: serious
Justification: Policy 10.1

Dear Maintainer,

Per CTTE decree, packages may not depend on nodejs-legacy. It exists
solely for compatibility with non-Debian packages that are unaware of
the fact that someone else claimed the name 'node' many years before.

For details, see bug #614907 and
https://lists.debian.org/debian-devel-announce/2012/07/msg2.html

-Ben


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

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



Bug#848524: kwin-wayland: rapid memory leak

2016-12-17 Thread Ben Longbons
Package: kwin-wayland
Version: 4:5.8.4-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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.

-Ben


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

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

Versions of packages 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
ii  libc62.24-8
ii  libepoxy01.3.1-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libkf5coreaddons55.27.0-1
ii  libkf5i18n5  5.27.0-2
ii  libkf5idletime5  5.27.0-1
ii  libkf5waylandclient5 4:5.28.0-1
ii  libkf5waylandserver5 4:5.28.0-1
ii  libkf5windowsystem5  5.27.0-1
ii  libkwineffects9  4:5.8.4-1
ii  libqt5core5a [qtbase-abi-5-7-1]  5.7.1~20161021+dfsg-6
ii  libqt5dbus5  5.7.1~20161021+dfsg-6
ii  libqt5gui5   5.7.1~20161021+dfsg-6
ii  libqt5widgets5   5.7.1~20161021+dfsg-6
ii  libstdc++6   7-20161201-1
ii  libwayland-egl1-mesa [libwayland-egl1]   13.0.2-1
ii  libxcb1  1.12-1
ii  qtwayland5   5.7.1~20161021-2
ii  xwayland 2:1.19.0-2

kwin-wayland recommends no packages.

kwin-wayland suggests no packages.

-- no debconf information



Bug#848523: kwin-x11: Fails to start

2016-12-17 Thread Ben Longbons
Package: kwin-x11
Version: 4:5.8.4-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

With some recent upgrade, kwin-x11 fails to start properly. Usually I
track testing, but .

I can see the process *running*, but it doesn't actually decorate any
windows (if I manually e.g. start an xterm), and plasma never even gets
started.

Starting a different window manager *sometimes* allows Plasma to start,
but not reliably - I'm not sure how startkde waits for the WM to
activate.

While kwin *has* been unstable in the past, usually just killing the
drkonqi processes would fix everything.

-Ben


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

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

Versions of packages kwin-x11 depends on:
ii  kwin-common   4:5.8.4-1
ii  libc6 2.24-8
ii  libepoxy0 1.3.1-1
ii  libgcc1   1:7-20161201-1
ii  libkf5configcore5 5.27.0-1
ii  libkf5coreaddons5 5.27.0-1
ii  libkf5crash5  5.27.0-1
ii  libkf5i18n5   5.27.0-2
ii  libkf5windowsystem5   5.27.0-1
ii  libkwinglutils9   4:5.8.2-1+b1
ii  libkwinxrenderutils9  4:5.8.2-1+b1
ii  libqt5core5a  5.7.1~20161021+dfsg-6
ii  libqt5gui55.7.1~20161021+dfsg-6
ii  libqt5widgets55.7.1~20161021+dfsg-6
ii  libqt5x11extras5  5.7.1~20161021-2
ii  libstdc++67-20161201-1
ii  libx11-6  2:1.6.4-2
ii  libxcb-cursor00.1.1-3
ii  libxcb-randr0 1.12-1
ii  libxcb-xfixes01.12-1
ii  libxcb1   1.12-1
ii  libxi62:1.7.8-1

kwin-x11 recommends no packages.

kwin-x11 suggests no packages.

-- no debconf information



Bug#848162: konsole: Interprets options even after -e

2016-12-14 Thread Ben Longbons
Package: konsole
Version: 4:16.08.3-1
Severity: serious
Justification: Policy 11.8.3

Dear Maintainer,


Quoting policy:

>To be an x-terminal-emulator, a program must:

> * Support the command-line option -e command, which creates a new terminal 
> window[106] and runs the specified command, interpreting the entirety of the 
> rest of the command line as a command to pass straight to exec, in the manner 
> that xterm does.


While konsole *almost* does this, the following minimal example fails:

$ konsole -e sh -c sh
Unknown option 'c'.

(Incidentally, bug #563352 is totally bogus and can be closed - policy
should be updated to clarify "in the manner that xterm does when argv0
has no space").


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

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

Versions of packages konsole depends on:
ii  kio   5.27.0-2
ii  konsole-kpart 4:16.08.3-1
ii  libc6 2.24-7
ii  libkf5completion5 5.27.0-1
ii  libkf5configcore5 5.27.0-1
ii  libkf5configgui5  5.27.0-1
ii  libkf5configwidgets5  5.27.0-1
ii  libkf5coreaddons5 5.27.0-1
ii  libkf5crash5  5.27.0-1
ii  libkf5dbusaddons5 5.27.0-1
ii  libkf5i18n5   5.27.0-2
ii  libkf5iconthemes5 5.27.0-1
ii  libkf5kiowidgets5 5.27.0-2
ii  libkf5notifyconfig5   5.27.0-1
ii  libkf5widgetsaddons5  5.27.0-1
ii  libkf5windowsystem5   5.27.0-1
ii  libkf5xmlgui5 5.27.0-1
ii  libqt5core5a  5.7.1~20161021+dfsg-6
ii  libqt5gui55.7.1~20161021+dfsg-6
ii  libqt5widgets55.7.1~20161021+dfsg-6
ii  libstdc++67-20161201-1

konsole recommends no packages.

konsole suggests no packages.

-- no debconf information



Bug#819112: /usr/bin/plasmashell: Re: /usr/bin/plasmashell: Date not updated in all clocks.

2016-06-13 Thread Ben Longbons
Package: plasma-workspace
Version: 4:5.6.4-2
Followup-For: Bug #819112

Dear Maintainer,

After recent upgrades, my UTC clock just shows the date as a set of
black boxes. Which I suppose is *technically* better than inaccurate
information, but more significantly might point to where the actual bug
is - the date part appears to never be redrawn, unlike the time part.

-Ben

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

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

Versions of packages plasma-workspace depends on:
ii  dbus-x11 1.10.8-1
ii  frameworkintegration 5.22.0-1
ii  gdb  7.10-1.1
ii  kde-cli-tools4:5.6.4-1
ii  kded55.22.0-1
ii  kinit5.22.0-1
ii  kio  5.22.0-1
ii  libc62.22-11
ii  libcln6  1.3.4-1
ii  libdbusmenu-qt5-20.9.3+16.04.20160218-1
ii  libgcc1  1:6.1.1-4
ii  libgps22 3.16-2
ii  libice6  2:1.0.9-1+b1
ii  libkf5activities55.22.0-2
ii  libkf5auth5  5.22.0-1
ii  libkf5baloo5 5.22.0-2
ii  libkf5bookmarks5 5.22.0-2
ii  libkf5completion55.22.0-1
ii  libkf5configcore55.22.0-1
ii  libkf5configgui5 5.22.0-1
ii  libkf5configwidgets5 5.22.0-1
ii  libkf5coreaddons55.22.0-1
ii  libkf5crash5 5.22.0-1
ii  libkf5dbusaddons55.22.0-1
ii  libkf5declarative5   5.22.0-1
ii  libkf5globalaccel-bin5.22.0-1
ii  libkf5globalaccel5   5.22.0-1
ii  libkf5guiaddons5 5.22.0-1
ii  libkf5i18n5  5.22.1-1
ii  libkf5iconthemes55.22.0-1
ii  libkf5idletime5  5.22.0-1
ii  libkf5itemviews5 5.22.0-1
ii  libkf5jobwidgets55.22.0-1
ii  libkf5js55.22.0-1
ii  libkf5jsembed5   5.22.0-1
ii  libkf5kdelibs4support5   5.22.0-2
ii  libkf5kiocore5   5.22.0-1
ii  libkf5kiofilewidgets55.22.0-1
ii  libkf5kiowidgets55.22.0-1
ii  libkf5networkmanagerqt6  5.22.0-2
ii  libkf5newstuff5  5.22.0-1
ii  libkf5notifications5 5.22.0-1
ii  libkf5notifyconfig5  5.22.0-1
ii  libkf5package5   5.22.0-1
ii  libkf5plasma55.22.0-1
ii  libkf5plasmaquick5   5.22.0-1
ii  libkf5quickaddons5   5.22.0-1
ii  libkf5runner55.22.0-1
ii  libkf5screen-bin 4:5.6.4-3
ii  libkf5screen74:5.6.4-3
ii  libkf5service-bin5.22.0-1
ii  libkf5service5   5.22.0-1
ii  libkf5solid5 5.22.0-1
ii  libkf5su55.22.0-1
ii  libkf5texteditor55.22.0-1
ii  libkf5textwidgets5   5.22.0-1
ii  libkf5wallet-bin 5.22.0-1
ii  libkf5wallet55.22.0-1
ii  libkf5waylandclient5 4:5.22.0-1
ii  libkf5widgetsaddons5 5.22.0-1
ii  libkf5windowsystem5  5.22.0-1
ii  libkf5xmlgui55.22.0-1
ii  libkf5xmlrpcclient5  5.22.0-1
ii  libkscreenlocker55.6.4-2
ii  libksgrd74:5.6.4-1
ii  libkworkspace5-5 4:5.6.4-2
ii  libphonon4qt5-4  4:4.9.0-2
ii  libplasma-geolocation-interface5 4:5.6.4-2
ii  libprocesscore7  4:5.6.4-1
ii  libprocessui74:5.6.4-1
ii  libqalculate5v5  0.9.7-9.1+b1
ii  libqt5core5a 5.5.1+dfsg-17
ii  libqt5dbus5  5.5.1+dfsg-17
ii  libqt5gui5   5.5.1+dfsg-17
ii  libqt5network5   5.5.1+dfsg-17
ii  libqt5qml5  

Bug#819112: /usr/bin/plasmashell: Date not updated in all clocks.

2016-03-23 Thread Ben Longbons
Package: plasma-workspace
Version: 4:5.4.3-2
Severity: minor
File: /usr/bin/plasmashell

Dear Maintainer,

I add two clock widgets to my taskbar: one in local time and one in UTC.

However, while the *time* updates in both widgets, the date only gets
updated in the one that shows local time. The UTC clock sticks to the
date from the time Plasma started (or the time the widget's "show date?"
option was turned on).

I only noticed this a day or so ago, at which point the UTC clock was
showing the date for about a week ago (likely the last time either
plasma or kwin crashed).

Due to plasmashell's single-process architecture, it is difficult to
figure out which parts are responsible for anything (such as this
unresponsiveness or the excessive CPU usage I reported earlier).


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

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

Versions of packages plasma-workspace depends on:
ii  dbus-x11 1.10.8-1
ii  frameworkintegration 5.16.0-1
ii  gdb  7.10-1+b1
ii  kactivities  5.16.0-1
ii  kde-cli-tools4:5.4.3-1
ii  kded55.16.0-1
ii  kinit5.16.0-1
ii  kio  5.16.0-1
ii  libc62.22-3
ii  libcln6  1.3.4-1
ii  libdbusmenu-qt5-20.9.3+15.10.20150604-1
ii  libgcc1  1:5.3.1-11
ii  libgps22 3.15-2
ii  libice6  2:1.0.9-1+b1
ii  libkf5activities55.16.0-1
ii  libkf5auth5  5.16.0-1
ii  libkf5baloo5 5.16.0-1
ii  libkf5bookmarks5 5.16.0-1
ii  libkf5completion55.16.0-1
ii  libkf5configcore55.16.0-1
ii  libkf5configgui5 5.16.0-1
ii  libkf5configwidgets5 5.16.0-1
ii  libkf5coreaddons55.16.0-1
ii  libkf5crash5 5.16.0-1
ii  libkf5dbusaddons55.16.0-1
ii  libkf5declarative5   5.16.0-1
ii  libkf5globalaccel-bin5.16.0-1
ii  libkf5globalaccel5   5.16.0-1
ii  libkf5guiaddons5 5.16.0-1
ii  libkf5i18n5  5.16.0-1
ii  libkf5iconthemes55.16.0-1
ii  libkf5idletime5  5.16.0-1
ii  libkf5itemviews5 5.16.0-1
ii  libkf5jobwidgets55.16.0-1
ii  libkf5js55.16.0-1
ii  libkf5jsembed5   5.16.0-1
ii  libkf5kdelibs4support5   5.16.0-1
ii  libkf5kiocore5   5.16.0-1
ii  libkf5kiofilewidgets55.16.0-1
ii  libkf5kiowidgets55.16.0-1
ii  libkf5networkmanagerqt6  5.16.0-1
ii  libkf5newstuff5  5.16.0-1
ii  libkf5notifications5 5.16.0-1
ii  libkf5notifyconfig5  5.16.0-1
ii  libkf5package5   5.16.0-1
ii  libkf5plasma55.16.0-1
ii  libkf5plasmaquick5   5.16.0-1
ii  libkf5quickaddons5   5.16.0-1
ii  libkf5runner55.16.0-1
ii  libkf5screen64:5.4.3-1
ii  libkf5service-bin5.16.0-1
ii  libkf5service5   5.16.0-1
ii  libkf5solid5 5.16.0-1
ii  libkf5su55.16.0-1
ii  libkf5texteditor55.16.0-1
ii  libkf5textwidgets5   5.16.0-1
ii  libkf5wallet-bin 5.16.0-1
ii  libkf5wallet55.16.0-1
ii  libkf5waylandclient5 4:5.4.3-1
ii  libkf5waylandserver5 4:5.4.3-1
ii  libkf5webkit55.16.0-1
ii  libkf5widgetsaddons5 5.16.0-1
ii  libkf5windowsystem5  5.16.0-1
ii  libkf5xmlgui55.16.0-1
ii  libkf5xmlrpcclient5  5.16.0-1
ii  libksgrd74:5.4.3-1
ii  libkworkspace5-5 4:5.4.3-2
ii  libpam0g 1.1.8-3.2
ii  libphonon4qt5-4  4:4.8.3-2

Bug#803523: After installing plasma-pa I have 2 volume applets too

2015-11-18 Thread Ben Longbons
Thanks for isolating, removing that package worked.

I guess this bug can be reassigned to tell plasma-pa to suicide itself
in the presence of its superior. Otherwise, the packages should add a
Conflicts: dependency or something.

On Wed, Nov 18, 2015 at 12:10 PM, Diederik de Haas
 wrote:
> I just installed plasma-pa and when I rebooted I have two applets too.
> Do you have that package too?



Bug#803612: libqt5gui5: "ambiguous shortcut" regression

2015-11-02 Thread Ben Longbons
A fresh user does not reproduce by default, but  with a little help
from strace I managed to find a way to reproduce what's happening with
my main user.

Edit the file ~/.config/kdeglobals, and add or replace the following lines:

[Shortcuts]
New=Ctrl+N; Ctrl+N

(This is visible in systemsettings5 as Standard Shortcuts, but the UI
will prevent *setting* a conflict there now)

Then all Qt (not just KDE! Does Qt have some plugin mechanism
perhaps?) applications will read this file and conflict whenever you
try to create a new file.

Obviously some previous version of Qt (or even KDE) was buggy in that
it was capable of generating the config file with these contents.

But the current version of Qt remains buggy in that it is willing to
*read* such a file without discarding the duplicate.

-Ben


On Mon, Nov 2, 2015 at 8:33 AM, Lisandro Damián Nicanor Pérez Meyer
<perezme...@gmail.com> wrote:
> On Sunday 01 November 2015 14:28:08 Ben Longbons wrote:
>> Among others, it happens in Kate (but it is not KDE-specific, it
>> happens in pure Qt applications too, I just can't think of one off the
>> top of my head that everyone is likely to have installed).
>>
>> Press Ctrl-N, receive a popup instead of a new file:
>>
>> (title) Ambiguous Shortcut Detected — Kate
>> The key sequence 'Ctrl+N' is ambiguous. Use 'Configure Shortcuts'
>> from the 'Settings' menu to solve the ambiguity.
>> No action will be triggered.
>
> Still can't reproduce it. Moreover my kate config is the default.
>
> Can you try creating a new user and see what happens?
>
>
> --
> "So long, and thanks for all the fish!"
>   The Hitchhickers guide to the Galaxy
>
> Lisandro Damián Nicanor Pérez Meyer
> http://perezmeyer.com.ar/
> http://perezmeyer.blogspot.com/



Bug#803612: libqt5gui5: "ambiguous shortcut" regression

2015-11-01 Thread Ben Longbons
Among others, it happens in Kate (but it is not KDE-specific, it
happens in pure Qt applications too, I just can't think of one off the
top of my head that everyone is likely to have installed).

Press Ctrl-N, receive a popup instead of a new file:

(title) Ambiguous Shortcut Detected — Kate
The key sequence 'Ctrl+N' is ambiguous. Use 'Configure Shortcuts'
from the 'Settings' menu to solve the ambiguity.
No action will be triggered.

Go to Settings -> Configure shortcuts, search for "new"
Set alternate shortcut to "custom - None".

Ctrl-N now works.

bad kate package: 4:15.08.2-1 (stretch/sid)
good kate package: 4:4.14.2-2 (jessie - can be easily downgraded)

On further investigation, the Qt4 version of kate had the alternate
shortcut set to None by default instead of a duplicate of the primary
shortcut like the Qt5 version does.

-Ben

On Sun, Nov 1, 2015 at 9:47 AM, Lisandro Damián Nicanor Pérez Meyer
<perezme...@gmail.com> wrote:
> tag 803612 moreinfo unreproducible
> thanks
>
> On Saturday 31 October 2015 12:58:49 Ben Longbons wrote:
>> Package: libqt5gui5
>> Version: 5.5.1+dfsg-5
>> Severity: important
>>
>> Dear Maintainer,
>>
>> In all Qt applications, pressing nearly any shortcut does not perform
>> the requested action. Instead, it just pops up a box saying "ambiguous
>> shortcut detected".
>
> Hi Ben! For what it's worth I don't see this bahvior on any Qt5 app. It would
> be good if you can give us more info, like what DM are you using, an example
> app and shortcut to use, etc.
>
>> This is caused by the fact that, by default, the primary and alternate
>> keybindings are set to the same key sequence.
>>
>> Apparently, the dispatcher
>> logic is unable to detect that the two shortcuts refer to the same
>> action.
>>
>> In previous versions of Qt, this was not a problem.
>
> Please please give us an example.
>
> Kinds regards, Lisandro.
>
> --
> Antiguo proverbio de El Machi: "Dado el apropiado grado de profundidad, la
> ineptitud es indistinguible del sabotaje"
>
> Lisandro Damián Nicanor Pérez Meyer
> http://perezmeyer.com.ar/
> http://perezmeyer.blogspot.com/



Bug#803612: libqt5gui5: "ambiguous shortcut" regression

2015-10-31 Thread Ben Longbons
Package: libqt5gui5
Version: 5.5.1+dfsg-5
Severity: important

Dear Maintainer,

In all Qt applications, pressing nearly any shortcut does not perform
the requested action. Instead, it just pops up a box saying "ambiguous
shortcut detected".

This is caused by the fact that, by default, the primary and alternate
keybindings are set to the same key sequence. Apparently, the dispatcher
logic is unable to detect that the two shortcuts refer to the same
action.

In previous versions of Qt, this was not a problem.

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

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

Versions of packages libqt5gui5 depends on:
ii  fontconfig   2.11.0-6.3
ii  libc62.19-22
ii  libegl1-mesa [libegl1-x11]   10.6.8-1
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.6-2
ii  libgl1-mesa-glx [libgl1] 10.6.8-1
ii  libglib2.0-0 2.46.1-1
ii  libharfbuzz0b1.0.1-1+b1
ii  libinput10   1.0.1-1
ii  libjpeg62-turbo  1:1.4.1-2
ii  libmtdev11.1.5-1
ii  libpng12-0   1.2.50-2+b2
ii  libqt5core5a [qtbase-abi-5-5-1]  5.5.1+dfsg-5
ii  libqt5dbus5  5.5.1+dfsg-5
ii  libqt5network5   5.5.1+dfsg-5
ii  libqt5xcbqpa55.5.1+dfsg-5
ii  libstdc++6   5.2.1-22
ii  libudev1 227-2
ii  libx11-6 2:1.6.3-1
ii  libxkbcommon00.5.0-1
ii  libxrender1  1:0.9.8-1+b1
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages libqt5gui5 recommends:
ii  libqt5svg5  5.5.1-2

Versions of packages libqt5gui5 suggests:
pn  libqt5libqgtk2 
ii  qt5-image-formats-plugins  5.5.1-2
ii  qtwayland5 5.5.1-2

-- no debconf information



Bug#803523: kmix: Should kill competing volume applet

2015-10-30 Thread Ben Longbons
Package: kmix
Version: 4:15.08.1-1
Severity: normal

Dear Maintainer,

Since I upgraded to KDE5, there is another volume applet in the system tray.

I don't know where it is coming from, it just says "Plasma" when I try
xwininfo.

I don't want to use the other one, because kmix is so much better (for
example, per application volume controls, which I use a lot).

The other audio applet can be *hidden* in the system tray options (under
Extra Items), but still appears to be handling volume-key presses, often
leading to race conditions (e.g. one application thinks the press was
held long enough to change the volume 20%, then the other detects it and
tries to change it 5%, but actually sets it *back* 15%).

Please figure out where the inferior volume control applet is coming
from, and ensure that it dies whenever kmix is available.

Thanks.

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

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

Versions of packages kmix depends on:
ii  kde-runtime  4:15.08.2-1
ii  libasound2   1.0.29-1
ii  libc62.19-22
ii  libcanberra0 0.30-2.1
ii  libkdecore5  4:4.14.13-1
ii  libkdeui54:4.14.13-1
ii  libplasma3   4:4.14.13-1
ii  libpulse-mainloop-glib0  7.0-1
ii  libpulse07.0-1
ii  libqt4-dbus  4:4.8.7+dfsg-3
ii  libqt4-xml   4:4.8.7+dfsg-3
ii  libqtcore4   4:4.8.7+dfsg-3
ii  libqtgui44:4.8.7+dfsg-3
ii  libsolid44:4.14.13-1
ii  libstdc++6   5.2.1-22

kmix recommends no packages.

kmix suggests no packages.

-- no debconf information



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

2015-09-18 Thread Ben Longbons
Package: kate
Version: 4:15.08.0-1
Severity: serious
Justification: license violation

Dear Maintainer,

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

See #798421 for more information.


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

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

Versions of packages kate depends on:
ii  kate5-data   4:15.08.0-1
ii  katepart 4:4.14.3-2
ii  ktexteditor-katepart 5.13.0-1+b1
ii  libc62.19-20
ii  libgit2-23   0.23.1-1
ii  libkf5activities55.13.0-1
ii  libkf5bookmarks5 5.13.0-1
ii  libkf5completion55.13.0-1
ii  libkf5configcore55.13.0-1
ii  libkf5configgui5 5.13.0-1
ii  libkf5configwidgets5 5.13.0-2
ii  libkf5coreaddons55.13.0-1
ii  libkf5dbusaddons55.13.0-1
ii  libkf5guiaddons5 5.13.0-1
ii  libkf5i18n5  5.13.0-1
ii  libkf5iconthemes55.13.0-1
ii  libkf5itemmodels55.13.0-1
ii  libkf5jobwidgets55.13.0-1
ii  libkf5kiocore5   5.13.0-1
ii  libkf5kiofilewidgets55.13.0-1
ii  libkf5kiowidgets55.13.0-1
ii  libkf5newstuff5  5.13.0-1
ii  libkf5notifications5 5.13.0-1
ii  libkf5parts5 5.13.0-1
ii  libkf5plasma55.13.0-1
ii  libkf5service5   5.13.0-2
ii  libkf5texteditor55.13.0-1+b1
ii  libkf5textwidgets5   5.13.0-1
ii  libkf5threadweaver5  5.13.0-1
ii  libkf5wallet55.13.0-1
ii  libkf5widgetsaddons5 5.13.0-1
ii  libkf5windowsystem5  5.13.0-3
ii  libkf5xmlgui55.13.0-1
ii  libqt5core5a 5.4.2+dfsg-9
ii  libqt5dbus5  5.4.2+dfsg-9
ii  libqt5gui5   5.4.2+dfsg-9
ii  libqt5sql5   5.4.2+dfsg-9
ii  libqt5widgets5   5.4.2+dfsg-9
ii  libqt5xml5   5.4.2+dfsg-9
ii  libstdc++6   5.2.1-17
ii  plasma-framework 5.13.0-1
ii  qml-module-org-kde-kquickcontrolsaddons  5.13.0-1
ii  qml-module-qtquick-layouts   5.4.2-2+b1
ii  qml-module-qtquick2  5.4.2-6

kate recommends no packages.

Versions of packages kate suggests:
ii  aspell 0.60.7~20110707-3
ii  ispell 3.4.00-3
ii  khelpcenter4:5.4.1-1
ii  konsole-kpart  4:15.08.0-1

-- no debconf information



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

2015-09-18 Thread Ben Longbons
Package: libkf5texteditor5
Version: 5.13.0-1+b1
Severity: serious
Justification: license violation

Dear Maintainer,

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

See #798421 for more information.


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

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

Versions of packages libkf5texteditor5 depends on:
ii  ktexteditor-data   5.13.0-1
ii  libc6  2.19-20
ii  libgit2-23 0.23.1-1
ii  libjs-underscore   1.7.0~dfsg-1
ii  libkf5archive5 5.13.0-1
ii  libkf5codecs5  5.13.0-1
ii  libkf5completion5  5.13.0-1
ii  libkf5configcore5  5.13.0-1
ii  libkf5configgui5   5.13.0-1
ii  libkf5configwidgets5   5.13.0-2
ii  libkf5coreaddons5  5.13.0-1
ii  libkf5guiaddons5   5.13.0-1
ii  libkf5i18n55.13.0-1
ii  libkf5iconthemes5  5.13.0-1
ii  libkf5itemviews5   5.13.0-1
ii  libkf5jobwidgets5  5.13.0-1
ii  libkf5kiocore5 5.13.0-1
ii  libkf5kiofilewidgets5  5.13.0-1
ii  libkf5kiowidgets5  5.13.0-1
ii  libkf5parts5   5.13.0-1
ii  libkf5sonnetcore5  5.13.0-1
ii  libkf5sonnetui55.13.0-1
ii  libkf5textwidgets5 5.13.0-1
ii  libkf5widgetsaddons5   5.13.0-1
ii  libkf5xmlgui5  5.13.0-1
ii  libqt5core5a   5.4.2+dfsg-9
ii  libqt5gui5 5.4.2+dfsg-9
ii  libqt5printsupport55.4.2+dfsg-9
ii  libqt5script5  5.4.2+dfsg-4
ii  libqt5widgets5 5.4.2+dfsg-9
ii  libqt5xml5 5.4.2+dfsg-9
ii  libstdc++6 5.2.1-17

Versions of packages libkf5texteditor5 recommends:
ii  ktexteditor-katepart  5.13.0-1+b1

libkf5texteditor5 suggests no packages.

-- no debconf information



Bug#794419: sddm doesn't source /etc/profile and $HOME/.profile

2015-08-26 Thread Ben Longbons
Also trying to run games from the K menu gives a *really* weird error:

 KDEInit could not launch 'supertuxkart':

 Could not open library '/usr/lib/x86_64-linux-gnu/libkdeinit5_supertuxkart'.

 Cannot load library /usr/lib/x86_64-linux-gnu/libkdeinit5_supertuxkart: 
 (/usr/lib/x86_64-linux-gnu/libkdeinit5_supertuxkart.so: cannot open shared 
 object file: No such file or directory)



Bug#795923: klipper: Missing transitional package for KDE5 transition

2015-08-17 Thread Ben Longbons
Package: klipper
Severity: minor

Dear Maintainer,

I recently upgraded from jessie to testing and had to do a little manual
intervention.

The KDE4 `klipper` package's contents are now included in the
`plasma-workspace` package.

In order to ensure a correct upgrade experience, an empty binary `klipper`
package should exist containing just `Depends: plasma-workspace` and
the `plasma-workspace` package should add all three of:
`Conflicts: klipper` (to ensure both can't be installed at the same time),
`Replaces: klipper` (to ensure the upgraded package can be installed),
and `Provides: klipper` (to ensure that any packages with `Depends: klipper`
still work).

These transitional measures can be removed in `buster` since it is only
supported to upgrade one release at a time.

I also noticed `kde-workspace{,-bin,-data}` only exists in KDE4 but did
not figure out where exactly its contents moved. Likely there are more
packages: I don't have a full KDE install, and sometimes the package
manager is smart enough to find a way to install the new package even
if the control fields are wrong.


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (600, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, powerpc, arm64, armhf

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

Versions of packages klipper depends on:
ii  kde-runtime  4:4.14.2-2
ii  libc62.19-19
ii  libkdecore5  4:4.14.2-5
ii  libkdeui54:4.14.2-5
ii  libprison0   1.1.1-1
ii  libqt4-dbus  4:4.8.7+dfsg-1
ii  libqtcore4   4:4.8.7+dfsg-1
ii  libqtgui44:4.8.7+dfsg-1
ii  libstdc++6   5.1.1-14
ii  libx11-6 2:1.6.3-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

klipper recommends no packages.

klipper suggests no packages.