Bug#865377: dolphin: Devices list not updated after ejecting Media (external DVD drive)

¡Hola Maximilian! I tested it again today. Actually, that always happens - regardless of where I eject them. I tried hard button, inside dolphin and inside k3b always with the same result of piling. :) There are other things I realized: * All the entries vanish as soon as I close dolphin and

pykde4_4.14.3-3_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 26 Jun 2017 14:47:34 -0400 Source: pykde4 Binary: python-kde4 python-kde4-dev python-kde4-doc python3-pykde4 Architecture: source amd64 all Version: 4:4.14.3-3 Distribution: unstable Urgency: medium Maintainer:

Processing of pykde4_4.14.3-3_amd64.changes

pykde4_4.14.3-3_amd64.changes uploaded successfully to localhost along with the files: pykde4_4.14.3-3.dsc pykde4_4.14.3-3.debian.tar.xz pykde4_4.14.3-3_amd64.buildinfo python-kde4-dbgsym_4.14.3-3_amd64.deb python-kde4-dev_4.14.3-3_all.deb python-kde4-doc_4.14.3-3_all.deb

Bug#865861: marked as done (python-kde4: Qtwebkit not available breaks importing plasma module)

Your message dated Mon, 26 Jun 2017 20:58:19 + with message-id and subject line Bug#865861: fixed in pykde4 4:4.14.3-3 has caused the Debian Bug report #865861, regarding python-kde4: Qtwebkit not available breaks importing plasma module to be marked as

qimageblitz_0.0.6-5_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 26 Jun 2017 19:55:31 +0200 Source: qimageblitz Binary: libqimageblitz4 libqimageblitz-dev Architecture: source Version: 1:0.0.6-5 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers

Bug#865861: python-kde4: Qtwebkit not available breaks importing plasma module

Hi, I created the attached patch and put it in the debian/patches directory and recompiled the package provided in stretch. This one allows importing of plasma from PyKDE4 now. The build-depends: libqtwebkit-dev is also not necessary anymore. Greetings Leszek Am Montag, 26. Juni 2017,

Processing of qimageblitz_0.0.6-5_source.changes

qimageblitz_0.0.6-5_source.changes uploaded successfully to localhost along with the files: qimageblitz_0.0.6-5.dsc qimageblitz_0.0.6-5.debian.tar.xz qimageblitz_0.0.6-5_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#839283: marked as done (qimageblitz FTCBFS: uses the build architecture compiler and detects build architecture capabilities)

Your message dated Mon, 26 Jun 2017 18:18:52 + with message-id and subject line Bug#839283: fixed in qimageblitz 1:0.0.6-5 has caused the Debian Bug report #839283, regarding qimageblitz FTCBFS: uses the build architecture compiler and detects build

Processed: tagging 839283

Processing commands for cont...@bugs.debian.org: > tags 839283 + pending Bug #839283 [src:qimageblitz] qimageblitz FTCBFS: uses the build architecture compiler and detects build architecture capabilities Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need

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

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package plasma-desktop > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

Bug#866013: /usr/bin/krunner: krunner always appears on first virtual desktop under wayland

Package: plasma-workspace Version: 4:5.8.7-1 Severity: normal File: /usr/bin/krunner I am trying the Plasma Wayland desktop. I can start krunner by pressing Alt+F2. However, no matter which one of my four virtual desktops I start it from, it always switches back to the first desktop, and then

Bug#865544: Adding a new default panel segfaults with apparent infinite recursion stack overflow

On Fri, Jun 23, 2017 at 01:16:21PM +0200, Maximiliano Curia wrote: > I can't reproduce the issue here with an intel card, so it might be that the > issue is related to the nvidia drivers. I'm not really sure, can you test if > the issue is still reproducible for you with 4:5.8.7-1, currently in >

Bug#865850: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libkdcraw | 4:15.08.0-1.1 | source libkdcraw-data | 4:15.08.0-1.1 | all libkdcraw-dev | 4:15.08.0-1.1+b1 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386,