[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#815670: marked as done (kalarm: Some KDE applications do not autorstart properly)

Your message dated Thu, 04 Jan 2018 00:17:43 +0100
with message-id <1998184.A2ug4xbGee@tuxin>
and subject line Re: Bug#815670: kalarm: Some KDE applications do not autorstart properly
has caused the Debian Bug report #815670,
regarding kalarm: Some KDE applications do not autorstart properly
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
815670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815670
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: kalarm
Version: 4:4.14.10-2
Severity: grave
Justification: renders package unusable

I am having trouble with some KDE applications and their start-up process. After reporting a KDE bug
they told me it was likely to be a Debian issue. I agrre that it could very well be the case, if so
more likely a missing dependency or incorrect minimum version dependency on some KDE packages.

The bug report starts as a more specific problem but we eventually figured out it'a wider issue. We came
down to this error message as the culprit:

kalarmautostart(14710) AutostartApp::slotAutostart: No command line

The full bug report can be found here https://bugs.kde.org/show_bug.cgi?id=358027

I am tagging this as a grave bug because if the applications are supposed to be automatically
run at login and they aren't it could render them unusable to a normal user. Luckily I have
the knowledge to set up some scripts to deal with it in my own system.

This is probably a wider KDE issue, not only kdepim's or kalarm's so let me know if
this should be reported elsewhere and if I can help with further information or testing.


-- 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/8 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 kalarm depends on:
ii  kde-runtime             4:15.08.3-1+b1
ii  kdepim-runtime          4:4.14.10-2
ii  kdepimlibs-kio-plugins  4:4.14.10-1
ii  libakonadi-contact4     4:4.14.10-1
ii  libakonadi-kde4         4:4.14.10-1
ii  libakonadi-kmime4       4:4.14.10-1
ii  libc6                   2.21-9
ii  libgcc1                 1:5.3.1-8
ii  libkabc4                4:4.14.10-1
ii  libkalarmcal2           4:4.14.10-1
ii  libkcalcore4            4:4.14.10-1
ii  libkcalutils4           4:4.14.10-1
ii  libkdecore5             4:4.14.14-1+b1
ii  libkdepim4              4:4.14.10-2
ii  libkdeui5               4:4.14.14-1+b1
ii  libkholidays4           4:4.14.10-1
ii  libkio5                 4:4.14.14-1+b1
ii  libkmime4               4:4.14.10-1
ii  libkpimidentities4      4:4.14.10-1
ii  libkpimutils4           4:4.14.10-1
ii  libmailtransport4       4:4.14.10-1
ii  libphonon4              4:4.8.3-2
ii  libqt4-dbus             4:4.8.7+dfsg-6
ii  libqt4-network          4:4.8.7+dfsg-6
ii  libqtcore4              4:4.8.7+dfsg-6
ii  libqtgui4               4:4.8.7+dfsg-6
ii  libstdc++6              5.3.1-8
ii  libx11-6                2:1.6.3-1
ii  perl                    5.22.1-7
ii  phonon                  4:4.8.3-2

kalarm recommends no packages.

Versions of packages kalarm suggests:
pn  jovie  <none>

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 4:15.08.3-1

lets close this bug properly.

hefee

--
On Freitag, 13. Mai 2016 22:33:44 CET Maximiliano Curia wrote:
> Control: severity -1 normal
> Control: fixed -1 4:15.08.3-1
> Control: tag -1 + upstream
> Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=358027
> 
> Hi,
> 
> As mentioned in the upstream bug, the bug is particular to the way the kde4
> version of kalarm used to autostart itself, and is fixed in a new upstream
> release. I'm tagging the corresponding fixed version, and downgrading the
> severity as this doesn't seem to be a broader issue.
> 
> Happy hacking,

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


--- End Message ---
Reply to: