Bug#963955: qtbase5-dev: Packages that build-depend on both Qt and TBB FTBFS

2020-06-29 Thread Gard Spreemann 
Package: qtbase5-dev
Version: 5.14
Severity: normal
Tags: upstream

Dear Maintainer,

As of Qt 5.14, a change to moc means that packages that build-depend
on both Qt and TBB (libtbb-dev) fail to build. This is
QTBUG-80990/QTBUG-80578 [1,2]. I have verified that this is a problem
for src:gudhi, which fails to build with Qt 5.14.2. The upstream bug
also indicates that packages that build-depend on both Qt and MongoDB
may be affected.

There is a patch upstream for the 5.15 branch, but it does not apply
cleanly to the current Debian version (5.14.2), so I did not
investigate further.

[1] https://bugreports.qt.io/browse/QTBUG-80990

[2] https://bugreports.qt.io/browse/QTBUG-80578

Re: Is anyone else experiencing intermittent Plasma freezes as of very recently?

2016-12-16 Thread Gard Spreemann 
On Wednesday, 14 December 2016 14:36:27 CET bruno zanetti wrote:
> It's likely https://bugs.kde.org/show_bug.cgi?id=373131

Thanks, that's useful.

Should we hope that Debian bugs #846779 and #847025 cover our
situation, or should we file a separate bug against xserver-xorg-core?

At any rate, it seems clear that this is a bug with Xorg upstream.


 Best,
 Gard

Re: Is anyone else experiencing intermittent Plasma freezes as of very recently?

2016-12-14 Thread Gard Spreemann 
On Wednesday, 14 December 2016 11:55:05 CET Gard Spreemann wrote:
> Before I file a bug and investigate further: is anyone else
> experiencing the same thing? Does anyone have any idea as to which
> upgrade may have caused the problem? I can't believe the update
> happened more than a week ago.

Judging by the Fedora bug and my dpkg.log, the problem started with
the recent Xorg upgrade (2:1.18.4-2 to 2:1.19.0-2). Also, again
judging by the Fedora bug, the problem might only affect nouveau
users.


 Best,
 Gard

Is anyone else experiencing intermittent Plasma freezes as of very recently?

2016-12-14 Thread Gard Spreemann 
Hello,

Some recent package upgrade in Stretch (I'm trying to pin down which)
has caused parts of my Plasma desktop to freeze at seemingly random
intervals. When it happens (every few minutes), all windows continue
to behave normally, and new programs can be started with
alt-F2. However, the desktop area itself, the taskbar and any
notifications become unresponsive. Switching to a console and then
back to X, without doing anything else, makes everything work again
for a while.

This seems to be exactly what is described in a recent Fedora bug [1].

Before I file a bug and investigate further: is anyone else
experiencing the same thing? Does anyone have any idea as to which
upgrade may have caused the problem? I can't believe the update
happened more than a week ago.

Thanks.

(I'm not subscribed to the list).

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1399396


 Best,
 Gard

Bug#814199: Possible upstream references

2016-10-04 Thread Gard Spreemann 
Hello,

As far as I can tell, this seems related to the following two upstream
bugs:

 - https://bugs.kde.org/show_bug.cgi?id=347195
 
 - https://bugs.kde.org/show_bug.cgi?id=356225

The latter is marked as fixed, but judging by the comments that
doesn't really seem to be the case.

Bug#829614: plasma-workspace: krunner no longer launches application

2016-07-09 Thread Gard Spreemann 
On Saturday 09 July 2016 16:41:13 Diederik de Haas wrote:
> On zaterdag 9 juli 2016 16:29:27 CEST Gard Spreemann wrote:
> > Do I mark it as fixed in 5.23.0, or do we instead consider this a
> > non-bug I experienced because I had inadvertendly mixed Plasma
> > versions?
> 
> I'd say neither.
> The issue seems (very much) to be caused by various framework packages not
> being at the same versions.
> It is still not known whether they all need to be at the same versions or
> only a subset of those framework packages and which that would be.
> 
> And as it causes real issues, it is a valid bug.

Alright. This is a working combination for plasma-workspace
4:5.6.5.1-1:

ii  libkf5activities55.22.0-2
ii  libkf5auth5  5.23.0-1
ii  libkf5baloo5 5.22.0-2
ii  libkf5bookmarks5 5.22.0-2
ii  libkf5completion55.23.0-1
ii  libkf5configcore55.23.0-1
ii  libkf5configgui5 5.23.0-1
ii  libkf5configwidgets5 5.22.0-1
ii  libkf5coreaddons55.23.0-1
ii  libkf5crash5 5.23.0-1
ii  libkf5dbusaddons55.23.0-1
ii  libkf5declarative5   5.22.0-1+b1
ii  libkf5globalaccel-bin5.23.0-1
ii  libkf5globalaccel5   5.23.0-1
ii  libkf5guiaddons5 5.23.0-1
ii  libkf5i18n5  5.22.1-1
ii  libkf5iconthemes55.22.0-1
ii  libkf5idletime5  5.23.0-1
ii  libkf5itemviews5 5.23.0-1
ii  libkf5jobwidgets55.23.0-1
ii  libkf5js55.23.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.23.0-1
ii  libkf5newstuff5  5.22.0-1
ii  libkf5notifications5 5.23.0-1
ii  libkf5notifyconfig5  5.22.0-1
ii  libkf5package5   5.22.0-1
ii  libkf5plasma55.23.0-1
ii  libkf5plasmaquick5   5.22.0-1
ii  libkf5quickaddons5   5.22.0-1+b1
ii  libkf5runner55.22.0-1
ii  libkf5screen-bin 4:5.6.5-1
ii  libkf5screen74:5.6.5-1
ii  libkf5service-bin5.22.0-1
ii  libkf5service5   5.22.0-1
ii  libkf5solid5 5.23.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.23.0-1
ii  libkf5widgetsaddons5 5.23.0-1
ii  libkf5windowsystem5  5.23.0-1
ii  libkf5xmlgui55.22.0-1
ii  libkf5xmlrpcclient5  5.22.0-1


With 5.22.0-1 of libkf5plasma5 instead, the combination does not work
(exhibits the bug).


Thanks a lot for your help in figuring this out.


 Best,
 Gard

Bug#829614: plasma-workspace: krunner no longer launches application

2016-07-09 Thread Gard Spreemann 
On Wed, 06 Jul 2016 12:51:59 +0200 Diederik de Haas <didi.deb...@cknow.org> 
wrote:
> On maandag 4 juli 2016 20:03:54 CEST Gard Spreemann wrote:
> > After upgrading plasma-workspace from 4:5.6.4-2 to 4:5.6.5.1-1 today,
> > krunner has stopped functioning correctly. 
> >
> > -- System Information:
> > Debian Release: stretch/sid
> >   APT prefers testing
> >   APT policy: (990, 'testing'), (500, 'unstable')
> 
> I see that various packages are at version 5.22.x while others are
> at 5.23.x.  What happens if you upgrade those packages to the 5.23.x
> version, available in sid/unstable?

Hi all, and apologies for being slow to reply (I incorrectly
remembered having subscribed to the bug without actually having done
so).

After upgrading (only) libkf5plasma55.22.0-1 to 5.23.0-1, I am no
longer experiencing this bug.

Do I mark it as fixed in 5.23.0, or do we instead consider this a
non-bug I experienced because I had inadvertendly mixed Plasma
versions?


 Best,
 Gard

Bug#829614: plasma-workspace: krunner no longer launches application

2016-07-04 Thread Gard Spreemann 
Package: plasma-workspace
Version: 4:5.6.5.1-1
Severity: normal

Dear Maintainer,

After upgrading plasma-workspace from 4:5.6.4-2 to 4:5.6.5.1-1 today,
krunner has stopped functioning correctly. Hitting enter has no
effect, nomatter what I type into krunner's textbox. Entering for
example "emacs" or "kate" used to launch the corresponding program and
remove the krunner window. Now neither happens.


 Best,
 Gard

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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-minimal [gdb]7.11.1-2
ii  kde-cli-tools4:5.6.5-1
ii  kded55.22.0-1
ii  kinit5.22.0-1
ii  kio  5.22.0-1
ii  libc62.22-13
ii  libcln6  1.3.4-1
ii  libdbusmenu-qt5-20.9.3+16.04.20160218-1
ii  libgcc1  1:6.1.1-7
ii  libgps22 3.16-2
ii  libice6  2:1.0.9-1+b1
ii  libkf5activities55.22.0-2
ii  libkf5auth5  5.23.0-1
ii  libkf5baloo5 5.22.0-2
ii  libkf5bookmarks5 5.22.0-2
ii  libkf5completion55.23.0-1
ii  libkf5configcore55.23.0-1
ii  libkf5configgui5 5.23.0-1
ii  libkf5configwidgets5 5.22.0-1
ii  libkf5coreaddons55.23.0-1
ii  libkf5crash5 5.23.0-1
ii  libkf5dbusaddons55.23.0-1
ii  libkf5declarative5   5.22.0-1+b1
ii  libkf5globalaccel-bin5.23.0-1
ii  libkf5globalaccel5   5.23.0-1
ii  libkf5guiaddons5 5.23.0-1
ii  libkf5i18n5  5.22.1-1
ii  libkf5iconthemes55.22.0-1
ii  libkf5idletime5  5.23.0-1
ii  libkf5itemviews5 5.23.0-1
ii  libkf5jobwidgets55.23.0-1
ii  libkf5js55.23.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.23.0-1
ii  libkf5newstuff5  5.22.0-1
ii  libkf5notifications5 5.23.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+b1
ii  libkf5runner55.22.0-1
ii  libkf5screen-bin 4:5.6.5-1
ii  libkf5screen74:5.6.5-1
ii  libkf5service-bin5.22.0-1
ii  libkf5service5   5.22.0-1
ii  libkf5solid5 5.23.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.23.0-1
ii  libkf5widgetsaddons5 5.23.0-1
ii  libkf5windowsystem5  5.23.0-1
ii  libkf5xmlgui55.22.0-1
ii  libkf5xmlrpcclient5  5.22.0-1
ii  libkscreenlocker55.6.5-1
ii  libksgrd74:5.6.5-1
ii  libkworkspace5-5 4:5.6.5.1-1
ii  libphonon4qt5-4  4:4.9.0-3
ii  libplasma-geolocation-interface5 4:5.6.5.1-1
ii  libprocesscore7  4:5.6.5-1
ii  libprocessui74:5.6.5-1
ii  libqalculate5v5  0.9.7-9.1+b1
ii  libqt5core5a 5.6.1+dfsg-3
ii  libqt5dbus5  5.6.1+dfsg-3
ii  libqt5gui5   5.6.1+dfsg-3
ii  libqt5network5   5.6.1+dfsg-3
ii  libqt5qml5   5.6.1-4
ii

Bug#810626: plasma-workspace: plasmashell leaks memory

2016-01-10 Thread Gard Spreemann 
Package: plasma-workspace
Version: 4:5.4.3-1
Severity: important
Tags: upstream fixed-upstream

Dear Maintainer,

plasmashell seems to leak memory. After three days of intermittent
use, the process' RSS is 800 MB, many times higher than what it was a
few days ago.

The upstream bug report [1] indicates (comment 108) that the problem
is resolved in 5.5.2.

[1] https://bugs.kde.org/show_bug.cgi?id=344879


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

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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-x111.10.6-1
ii  frameworkintegration5.16.0-1
ii  gdb-minimal [gdb]   7.10-1
ii  kactivities 5.16.0-1
ii  kde-cli-tools   4:5.4.3-1
ii  kded5   5.16.0-1
ii  kinit   5.16.0-1
ii  kio 5.16.0-1
ii  libc6   2.21-6
ii  libcln6 1.3.4-1
ii  libdbusmenu-qt5-2   0.9.3+15.10.20150604-1
ii  libgcc1 1:5.3.1-5
ii  libgps223.15-2
ii  libice6 2:1.0.9-1+b1
ii  libkf5activities5   5.16.0-1
ii  libkf5auth5 5.16.0-1
ii  libkf5baloo55.16.0-1
ii  libkf5bookmarks55.16.0-1
ii  libkf5completion5   5.16.0-1
ii  libkf5configcore5   5.16.0-1
ii  libkf5configgui55.16.0-1
ii  libkf5configwidgets55.16.0-1
ii  libkf5coreaddons5   5.16.0-1
ii  libkf5crash55.16.0-1
ii  libkf5dbusaddons5   5.16.0-1
ii  libkf5declarative5  5.16.0-1
ii  libkf5globalaccel-bin   5.16.0-1
ii  libkf5globalaccel5  5.16.0-1
ii  libkf5guiaddons55.16.0-1
ii  libkf5i18n5 5.16.0-1
ii  libkf5iconthemes5   5.16.0-1
ii  libkf5idletime5 5.16.0-1
ii  libkf5itemviews55.16.0-1
ii  libkf5jobwidgets5   5.16.0-1
ii  libkf5js5   5.16.0-1
ii  libkf5jsembed5  5.16.0-1
ii  libkf5kdelibs4support5  5.16.0-1
ii  libkf5kiocore5  5.16.0-1
ii  libkf5kiofilewidgets5   5.16.0-1
ii  libkf5kiowidgets5   5.16.0-1
ii  libkf5networkmanagerqt6 5.16.0-1
ii  libkf5newstuff5 5.16.0-1
ii  libkf5notifications55.16.0-1
ii  libkf5notifyconfig5 5.16.0-1
ii  libkf5package5  5.16.0-1
ii  libkf5plasma5   5.16.0-1
ii  libkf5plasmaquick5  5.16.0-1
ii  libkf5quickaddons5  5.16.0-1
ii  libkf5runner5   5.16.0-1
ii  libkf5screen6   4:5.4.3-1
ii  libkf5service-bin   5.16.0-1
ii  libkf5service5  5.16.0-1
ii  libkf5solid55.16.0-1
ii  libkf5su5   5.16.0-1
ii  libkf5texteditor5   5.16.0-1
ii  libkf5textwidgets5  5.16.0-1
ii  libkf5wallet-bin5.16.0-1
ii  libkf5wallet5   5.16.0-1
ii  libkf5waylandclient54:5.4.3-1
ii  libkf5waylandserver54:5.4.3-1
ii  libkf5webkit5   5.16.0-1
ii  libkf5widgetsaddons55.16.0-1
ii  libkf5windowsystem5 5.16.0-1
ii  libkf5xmlgui5   5.16.0-1
ii  libkf5xmlrpcclient5 5.16.0-1
ii  libksgrd7   4:5.4.3-1
ii  libkworkspace5-54:5.4.3-1
ii  libpam0g1.1.8-3.1
ii  libphonon4qt5-4 4:4.8.3-2
ii  libplasma-geolocation-interface54:5.4.3-1
ii  libprocesscore7 4:5.4.3-1
ii  libprocessui7   4:5.4.3-1
ii  libqalculate5v5 0.9.7-9.1+b1
ii  libqt5core5a5.5.1+dfsg-10
ii  libqt5dbus5 5.5.1+dfsg-10
ii  libqt5gui5  5.5.1+dfsg-10
ii  libqt5network5  5.5.1+dfsg-10
ii  libqt5qml5  5.5.1-3
ii  libqt5quick55.5.1-3
ii  libqt5script5   5.5.1+dfsg-2
ii  libqt5sql5  5.5.1+dfsg-10
ii  libqt5webkit5   5.5.1+dfsg-2
ii  libqt5widgets5  5.5.1+dfsg-10
ii  libqt5x11extras55.5.1-3
ii  libqt5xml5

Bug#807902: Kopete segfault started occurring at same time

2015-12-28 Thread Gard Spreemann 
On Tue, 22 Dec 2015 17:31:36 +0100 Gard Spreemann <gspreem...@gmail.com> 
wrote:
> It may or may not be relevant, or helpful, but Kopete
> (4:15.08.3-1+b1) also started segfaulting when its last window is
> closed around the same time. It could be related.

With the updated Qt that just entered testing (5.5.1+dfsg-10), Kopete
no longer segfaults like this.

-- Gard Spreemann

Bug#807902: Kopete segfault started occurring at same time

2015-12-22 Thread Gard Spreemann 
Hi,

It may or may not be relevant, or helpful, but Kopete (4:15.08.3-1+b1)
also started segfaulting when its last window is closed around the
same time. It could be related.

-- Gard Spreemann