#
# bts-link upstream status pull for source package marble
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #663373 (http://bugs.debian.org/663373)
# Bug title: [marble] directions should
#
# bts-link upstream status pull for source package kde-baseapps
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #609995 (http://bugs.debian.org/609995)
# Bug title: konqueror: SIGSEGV in auto
Package: okular
Version: 4:4.8.4-2
Severity: grave
Justification: renders package unusable
Sometimes, starting Okular fails without any error message. The only output
when started from a terminal is this:
$ okular
okular(30054)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
Processing commands for cont...@bugs.debian.org:
severity 681807 important
Bug #681807 [okular] okular: sometimes fails to start, but no error message
Severity set to 'important' from 'grave'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
681807:
severity 681807 important
thanks
Alle lunedì 16 luglio 2012, Felix Zweig ha scritto:
Sometimes, starting Okular fails without any error message.
fails is bit too generic; what does it happen?
You get back to the console prompt, or it hangs?
Since when it is happening?
Does the problem happens
Your message dated Tue, 17 Jul 2012 07:11:42 +0200
with message-id 201207170711.52840.lorenz.wen...@fsfe.org
and subject line Done: [plasma-desktop] Fetch job Error, cannot select this
collection right after login
has caused the Debian Bug report #680594,
regarding [plasma-desktop] Fetch job
6 matches
Mail list logo
