[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Launch Bug Report Wizard failing on Apple OS X (was "ksycoca4")
From:       Ian Wadham <iandw.au () gmail ! com>
Date:       2014-03-23 10:55:02
Message-ID: 47D74B5E-2EE0-4447-8ABB-58283A683E92 () gmail ! com
[Download RAW message or body]

On 23/03/2014, at 6:38 PM, mk-lists@email.de wrote:

> On 22 Mar 2014, at 23:41 , Ian Wadham <iandw.au@gmail.com> wrote:
> > That is a normal message. It just tells you where KDE libs is looking \
> > for the SyCoCa.
> OK. Good to know.
> 
> > I see you are running your tutorial2 as if it was a UNIX or Linux app, \
> > i.e. by direct execution of the executable file which the compile/build \
> > just created.  That
> Yes, simply because I wanted to see any console output, which is \
> swallowed by the app if done via “open tutorial2.app”, as you described \
> in your post. 
> > See the thread "taskgated: no signature" on the MacPorts Users list for \
> > the (slow) dawning of my understanding of this.
> I am aware of this thread.
> 
> > Try again? … :-)
> I did. :-)
> 
> Well, the tutorial doesn’t fire up a web browser as it should be doing. \
> :-( 
> I assumed here that the KDE framework deals with the bug reporter menu \
> item on its own and doesn’t require the tutorial code to implement \
> anything to open up the browser.

No, I don't think so. If you can see the Help->Report Bug… menu item in \
your test app, it should work.  The whole Help menu is standard kit in KDE \
apps.

> Please, correct me if I am wrong there.

I tried Help->Report Bug… and clicking on the "Launch Bug Report Wizard"
button in the KDE application I am currently working on (Palapeli).  It \
fails however I run it: Linux-style or Apple style.  The older Palapeli \
which Macports installed for me also fails.

In all three cases, an icon appears in the Dock (task bar equivalent) and \
vanishes too soon to see what it is.  Additionally, I am finding messages \
on the Apple OS X Console log (see attached).  Can a KDE guy tell Marko and \
me what is going wrong here?  And perhaps where else to look to narrow down \
the problem?

Any ideas?

Regards, Ian W.


["PalapeliBugReport.log" (PalapeliBugReport.log)]

23/03/14 9:39:50.017 PM	[0x0-0x4b04b].palapeli	palapeli(920)/kdeui \
(KMainWindow) KMainWindow::applyMainWindowSettings: \
KMainWindow::applyMainWindowSettings  "MainWindow" 23/03/14 9:39:50.100 \
PM	[0x0-0x4b04b].palapeli	palapeli(920)/kdecore (KConfigSkeleton) \
KCoreConfigSkeleton::writeConfig: 23/03/14 9:40:11.245 \
PM	[0x0-0x4b04b].palapeli	palapeli(920)/kdecore (KSycoca) \
KSycocaPrivate::openDatabase: Trying to open ksycoca from \
"/private/var/tmp/kde4dev-ianw/kdecache-ianw/ksycoca4" 23/03/14 9:40:11.279 \
PM	[0x0-0x10010].org.kde.kdeinit4	klauncher(283)/kio (KLauncher) \
KLauncher::processRequestReturn: "/opt/local/bin/kfmclient" (pid 923) up \
and running. 23/03/14 9:40:11.852 \
PM	[0x0-0x10010].org.kde.kdeinit4	klauncher(283)/kio (KLauncher) \
KLauncher::slotGotOutput: kfmclient(923)/kdecore (KSycoca) \
KSycocaPrivate::openDatabase: Trying to open ksycoca from \
"/private/var/tmp/kdecache-ianw/ksycoca4" 23/03/14 9:40:11.864 \
PM	[0x0-0x10010].org.kde.kdeinit4	klauncher(283)/kio (KLauncher) \
KLauncher::slotGotOutput: kfmclient(923)/kurifilter (plugins) \
KShortUriFilter::filterUri: \
"https://bugs.kde.org/enter_bug.cgi?format=guided&product=palapeli&version=2.0"
 23/03/14 9:40:11.864 PM	[0x0-0x10010].org.kde.kdeinit4	klauncher(283)/kio \
(KLauncher) KLauncher::slotGotOutput: kfmclient(923)/kurifilter \
KUriFilterPlugin::setFilteredUri: Got filtered to: \
KUrl("https://bugs.kde.org/enter_bug.cgi?format=guided&product=palapeli&version=2.0")
 23/03/14 9:40:11.864 PM	[0x0-0x10010].org.kde.kdeinit4	klauncher(283)/kio \
(KLauncher) KLauncher::slotGotOutput: kfmclient(923)/kurifilter (plugins) \
KUriSearchFilter::filterUri: \
"https://bugs.kde.org/enter_bug.cgi?format=guided&product=palapeli&version=2.0"
 23/03/14 9:40:11.864 \
PM	[0x0-0x10010].org.kde.kdeinit4	kfmclient(923)/kurifilter (plugins) \
LocalDomainUriFilter::filterUri: \
"https://bugs.kde.org/enter_bug.cgi?format=guided&product=palapeli&version=2.0"
 23/03/14 9:40:11.864 \
PM	[0x0-0x10010].org.kde.kdeinit4	kfmclient(923)/kurifilter (plugins) \
FixHostUriFilter::filterUri: \
"https://bugs.kde.org/enter_bug.cgi?format=guided&product=palapeli&version=2.0"
 23/03/14 9:40:11.864 \
PM	[0x0-0x10010].org.kde.kdeinit4	kfmclient(923)/kurifilter (plugins) \
FixHostUriFilter::filterUri: url: \
KUrl("https://bugs.kde.org/enter_bug.cgi?format=guided&product=palapeli&version=2.0") \
type: 0 23/03/14 9:40:11.865 \
PM	[0x0-0x10010].org.kde.kdeinit4	klauncher(283)/kio (KLauncher) \
KLauncher::slotGotOutput: kfmclient(923)/kurifilter (plugins) \
KAutoWebSearch::filterUri: \
"https://bugs.kde.org/enter_bug.cgi?format=guided&product=palapeli&version=2.0"
 23/03/14 9:40:11.877 PM	[0x0-0x10010].org.kde.kdeinit4	klauncher(283)/kio \
(KLauncher) KLauncher::slotFinished: process finished exitcode= 0 \
exitStatus= 0





>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]