Package: kdeconnect
Version: 1.3.3-2
Followup-For: Bug #841762
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I've reproduced this crash today. One factor - which
may merely be a red herring - is that my devices on
the network didn't have Internet access. They were
both blocked by network login
Processing control commands:
> tags -1 buster-ignore
Bug #784479 [src:kde4libs] [kde4libs] Qt4's WebKit removal
Added tag(s) buster-ignore.
--
784479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 buster-ignore
On Thu, Apr 04, 2019 at 10:39:25PM +0200, Ivo De Decker wrote:
> On Tue, Apr 02, 2019 at 11:30:44PM +0200, Moritz Muehlenhoff wrote:
> > Sure, if the release team agrees with that approach, the canonical way to do
> > that would be to tag the bug as "buster-ignore".
Processing control commands:
> tags -1 buster-ignore
Bug #876905 [src:qtwebkit] qtwebkit should not be released with buster
Added tag(s) buster-ignore.
--
876905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876905
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 buster-ignore
Hi,
On Tue, Apr 02, 2019 at 11:30:44PM +0200, Moritz Muehlenhoff wrote:
> Sure, if the release team agrees with that approach, the canonical way to do
> that would be to tag the bug as "buster-ignore".
OK, tagging 876905 ("qtwebkit should not be released with
Processing control commands:
> tags -1 buster-ignore
Bug #784477 [src:kde-runtime] [kde-runtime] Qt4's WebKit removal
Added tag(s) buster-ignore.
--
784477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
#
# bts-link upstream status pull for source package src:grantlee5
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#
user debian-bts-l...@lists.debian.org
# remote status report for #917711
#
# bts-link upstream status pull for source package src:plasma-workspace
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#
user debian-bts-l...@lists.debian.org
# remote status report for #926066
Note that the error message and the button "Details" are provided
automatically by the Akonadi library if Akonadi fails to start up. AFAIK, you
would see exactly the same display in any other Akonadi-dependent application
if Akonadi failed to start. So, although you see the fault in KAlarm, the
Package: src:oxygen-icons5,dpkg-dev,tar
Tags: ftbfs
Dear maintainer:
I tried to build "oxygen-icons5" in buster but it failed:
+--+
| Build environment|
Package: kalarm
Version: 4:16.04.3-4~deb9u1
Severity: important
When kalarm has an error starting up (for example the problem with Akonadi,
reported already in bug #836873)
then there is button "Details" below the error message (the error message that
covers entire window of the application).
The OP I think didn't written what is the problem.
The problem, that I also encountered, is that always when you start
kalarm, then it does not work at all - instead the entire main window is
covered with an error message
(that can not be copy-pasted, sadly) stating that there was error using
12 matches
Mail list logo
