Re: Launch Bug Report Wizard failing on Apple OS X (was "ksycoca4")
On 05 May 2014, at 21:25 , Thomas Lübking wrote: > -> can you lookup your local KDE code for the section in kfmclient.cpp? Since I am using current KDE 4.12.4 here this change is - of course - present. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Launch Bug Report Wizard failing on Apple OS X (was "ksycoca4")
On Montag, 5. Mai 2014 21:05:46 CEST, mk-li...@email.de wrote:
On 05 May 2014, at 21:00 , Thomas Lübking wrote:
Many thanks for the update - let's see whether Jose can
confirm this observation.
You’re welcome. We’ll see.
The only odd thing is that some kio_client apps clutter up
the dock, which I’ve also seen for kglobalaccel in
konversation [1].
Actually this does match [2] where many [kioclient]
processes hang around - do you get them as well? ("ps ax"
should also work under OSX)
Yup.
I found
https://bugs.kde.org/show_bug.cgi?id=294554
which *might* be https://bugs.kde.org/show_bug.cgi?id=290936 which was
apparently caused in an attempt to fix
https://bugs.kde.org/show_bug.cgi?id=182591 but is supposed to be fixed by
https://projects.kde.org/projects/kde/applications/kde-baseapps/repository/revisions/c37d81c2076cfa70c1952c49e5dd31f2034521f6/diff/konqueror/client/kfmclient.cpp
-> can you lookup your local KDE code for the section in kfmclient.cpp?
Cheers,
Thomas
Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Launch Bug Report Wizard failing on Apple OS X (was "ksycoca4")
On 05 May 2014, at 21:00 , Thomas Lübking wrote:
> Many thanks for the update - let's see whether Jose can confirm this
> observation.
You’re welcome. We’ll see.
>> The only odd thing is that some kio_client apps clutter up the dock, which
>> I’ve also seen for kglobalaccel in konversation [1].
> Actually this does match [2] where many [kioclient] processes hang
> around - do you get them as well? ("ps ax" should also work under OSX)
Yup.
signature.asc
Description: Message signed with OpenPGP using GPGMail
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Launch Bug Report Wizard failing on Apple OS X (was "ksycoca4")
On Samstag, 3. Mai 2014 23:38:22 CEST, mk-li...@email.de wrote:
On 23 Mar 2014, at 19:18 , Thomas Lübking wrote:
Another idea would be that OSX doesn't like the "!" prefix (no
idea why componentchooser writes it - here. Works fine w/o as
well)
Hmm, I think that’s indeed the problem!
Many thanks for the update - let's see whether Jose can confirm this
observation.
The only odd thing is that some kio_client apps clutter up the
dock, which I’ve also seen for kglobalaccel in konversation [1].
Actually this does match [2] where many [kioclient] processes hang around - do
you get them as well? ("ps ax" should also work under OSX)
Cheers,
Thomas
[1] https://bugs.kde.org/show_bug.cgi?id=334174
[2] https://sourceforge.net/p/be-shell/tickets/21/
Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Launch Bug Report Wizard failing on Apple OS X (was "ksycoca4")
Hi Thomas, On 23 Mar 2014, at 19:18 , Thomas Lübking wrote: > Another idea would be that OSX doesn't like the "!" prefix (no idea why > componentchooser writes it - here. Works fine w/o as well) Hmm, I think that’s indeed the problem! I did this test once again with konqueror, but this time I selected konqueror via the “KDE control module” itself using the “Select preferred Web browser application” dialog under "Internet/Konqueror" instead of specifying the path to the executable directly in the application package... AND -> THIS TIME THERE WAS NO ENDLESS RESPAWNING HAPPENING ANYMORE! The only odd thing is that some kio_client apps clutter up the dock, which I’ve also seen for kglobalaccel in konversation [1]. But they disappear after a while (i.e. a few mins). So, eventually, the exclamation mark is the dangerous thing here, as it seems! I guess one should cross-check that as well with [2]! Perhaps the user also used the exclamation mark there. Greets, Marko [1] https://bugs.kde.org/show_bug.cgi?id=334174 [2] https://sourceforge.net/p/be-shell/tickets/21/ signature.asc Description: Message signed with OpenPGP using GPGMail >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Launch Bug Report Wizard failing on Apple OS X (was "ksycoca4")
On Sonntag, 23. März 2014 16:31:42 CEST, mk-li...@email.de wrote: kwriteconfig --group General --key BrowserApplication '!safari’ If I specify the full path to Safari and start kioclient it will SPAWN AN ENDLESS AMOUNT of Safaris (at a rate of ~2/s) Interesting. I got a similar bug[1] report because of spawning dolphins in a different context (but it doesn't happen here in either case) The major difference i could tell is that the config entry is marked expandable when written by the component chooser - unfortunately there seems no way to do this with kwriteconfig. If KDE on MacOS also uses ~/.kde/share/config for configuration (or any other ini style config you can locate - "kde4-config --path config"), you could try to edit "~/.kde/share/config/kdeglobals" directly. Locate the [General] group, find the BrowserApplication key and make it BrowserApplication[$e]=!safari Another idea would be that OSX doesn't like the "!" prefix (no idea why componentchooser writes it - here. Works fine w/o as well) Because of the linked bug, i'd be pretty interested in *why* safari/konqueror/whatever spawns endlessy. H… Didn’t look into that now, but one could simply use the kwriteconfig line of yours once after kdelibs installation. You'd have to write it globally in order to affect every user (and not just root) Cheers, Thomas [1] https://sourceforge.net/p/be-shell/tickets/21/ Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Launch Bug Report Wizard failing on Apple OS X (was "ksycoca4")
Thanks Thomas, for your valuable hints! :-) On 23 Mar 2014, at 12:19 , Thomas Lübking wrote: > Do you get a dialog for >kcmshell4 componentchooser OK, I located the executable eventually: — $ /Applications/MacPorts/KDE4/kcmshell4.app/Contents/MacOS/kcmshell4 componentchooser kcmshell(3530)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/private/var/tmp/kdecache-marko/ksycoca4" kcmshell(3530)/kutils (KCMultiDialog) *KCMultiDialog::addModule: "Default Applications" kcmshell(3530)/kutils (KCModuleProxy) KCModuleProxyPrivate::loadModule: Module not already loaded, loading module "Default Applications" from library "kcm_componentchooser" using symbol "kcm_componentchooser" kcmshell(3530)/kutils (KCMultiDialog) *KCMultiDialog::addModule: adding KCM "Default Applications" at the top level kcmshell(3530)/kutils (KCMultiDialog) KCMultiDialogPrivate::_k_slotCurrentPageChanged: kcmshell(3530)/kutils (KCMultiDialog) KCMultiDialogPrivate::_k_clientChanged: kcmshell(3530)/kutils (KCMultiDialog) KCMultiDialogPrivate::_k_clientChanged: kcmshell(3530)/kutils (KCMultiDialog) KCMultiDialogPrivate::_k_dialogClosed: 2014-03-23 13:42:57.451 kcmshell4[3530:507] modalSession has been exited prematurely - check for a reentrant call to endModalSession: — I then selected konqueror deliberately in the component chooser and NOW it indeed gets fired up when I call "kioclient exec 'http://www.kde.org/'” Now also the bug report web page is displayed in konqueror when clicking on the corresponding menu item in said tutorial app. Great. OK, this proves that the KDE setup isn’t properly carried out correctly on MacPorts at the moment. > try: > kwriteconfig --group General --key BrowserApplication '!safari’ If I specify the full path to Safari and start kioclient it will SPAWN AN ENDLESS AMOUNT of Safaris (at a rate of ~2/s) which fill up the dock bit by bit. — $ kioclient exec 'http://www.kde.org/' … (in my system log:) 23/03/14 14:00:12,483 com.apple.launchd.peruser.502[272]: (0x7fb848506610.anonymous.Safari[3758]) Unmanaged jobs may not make XPC Events requests. 23/03/14 14:00:12,835 com.apple.launchd.peruser.502[272]: (0x7fb848705f60.anonymous.Safari[3768]) Unmanaged jobs may not make XPC Events requests. 23/03/14 14:00:13,298 com.apple.launchd.peruser.502[272]: (0x7fb848506f00.anonymous.Safari[3772]) Unmanaged jobs may not make XPC Events requests. . . . — This I could only stop by logging off... And now I see that — $ kwriteconfig --group General --key BrowserApplication '!/Applications/MacPorts/KDE4/konqueror.app/Contents/MacOS/konqueror’ $ kioclient exec 'http://www.kde.org/' … — will also FIRE UP COUNTLESS konquerors at the same rate like Safaris. So, it’s not related to Safari then! What’s going on there? > To do that for every user, one could make use of kiosk (basically provide > /usr/share/config/kdeglobals with appropriate entry in [General] - whether > that works on MacOS, i don't know. H… Didn’t look into that now, but one could simply use the kwriteconfig line of yours once after kdelibs installation. Greets, Marko >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Launch Bug Report Wizard failing on Apple OS X (was "ksycoca4")
On Sonntag, 23. März 2014 13:08:50 CEST, mk-li...@email.de wrote: Does this open kde.org in any browser? No, it didn’t open a browser. Do you get a dialog for kcmshell4 componentchooser $ kcmshell4 componentchooser -bash: kcmshell4: command not found Well, I seem to have to install some other port to get kcmshell4 into my system... and can you select a webbrowser (safari) there? Need to search now which port contains that kcmshell4. Is there perhaps another way to define the standard web browser at install time in such a way that Safari would be used as the initial default? try: kwriteconfig --group General --key BrowserApplication '!safari' To do that for every user, one could make use of kiosk (basically provide /usr/share/config/kdeglobals with appropriate entry in [General] - whether that works on MacOS, i don't know. Cheers, Thomas Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Launch Bug Report Wizard failing on Apple OS X (was "ksycoca4")
On 23 Mar 2014, at 12:19 , Thomas Lübking wrote:
> kioclient exec 'http://www.kde.org/'
$ kioclient exec 'http://www.kde.org/'
kioclient(2672)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open
ksycoca from "/private/var/tmp/kdecache-marko/ksycoca4"
kioclient(2672)/kio (Scheduler) KIO::SchedulerPrivate::doJob:
KIO::SimpleJob(0x7f91a0c84cd0)
kioclient(2672)/kio (Scheduler) *KIO::SchedulerPrivate::protoQ: creating
ProtoQueue instance for "http"
kioclient(2672)/kio (Scheduler) KIO::ProtoQueue::ProtoQueue:
m_maxConnectionsTotal: 20 m_maxConnectionsPerHost: 5
kioclient(2672)/kdeui (kdelibs) KWindowSystem::setIcons:
KWindowSystem::setIcons( WId win, const QPixmap& icon, const QPixmap& miniIcon
) isn't yet implemented!
kioclient(2672)/kio (KIOConnection) KIO::ConnectionServer::listenForRemote:
Listening on
"local:/private/var/folders/79/1f244yjd38v_g1qq6qfw8qx8gp/T/ksocket-marko/kioclientDH2672.slave-socket"
kioclient(2672)/kio (Scheduler) *KIO::SchedulerPrivate::heldSlaveForJob: HOLD:
Reusing klauncher held slave ( KIO::Slave(0x7f91a0ca3bf0) )
kioclient(2672)/kio (Scheduler) KIO::SchedulerPrivate::putSlaveOnHold:
KIO::TransferJob(0x7f91a0c84cd0) KUrl("http://www.kde.org/";)
KIO::Slave(0x7f91a0ca3bf0)
kioclient(2672)/kio (Scheduler) KIO::SchedulerPrivate::cancelJob:
KIO::TransferJob(0x7f91a0c84cd0) QObject(0x0)
kioclient(2672)/kio (Scheduler) KIO::SchedulerPrivate::jobFinished:
KIO::TransferJob(0x7f91a0c84cd0) QObject(0x0)
kioclient(2672)/kio (Scheduler) KIO::SchedulerPrivate::publishSlaveOnHold:
KIO::Slave(0x7f91a0ca3bf0)
> Does this open kde.org in any browser?
No, it didn’t open a browser.
> Do you get a dialog for
>kcmshell4 componentchooser
$ kcmshell4 componentchooser
-bash: kcmshell4: command not found
Well, I seem to have to install some other port to get kcmshell4 into my
system...
> and can you select a webbrowser (safari) there?
Need to search now which port contains that kcmshell4.
Is there perhaps another way to define the standard web browser at install time
in such a way that Safari would be used as the initial default?
Not every user might install all KDE ports - including konqueror - just to
install e.g. KMyMoney.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Launch Bug Report Wizard failing on Apple OS X (was "ksycoca4")
On Sonntag, 23. März 2014 11:55:02 CEST, Ian Wadham wrote: 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? There's probably no known URI filter or the filter points konqueror or so. kioclient exec 'http://www.kde.org/' Does this open kde.org in any browser? Do you get a dialog for kcmshell4 componentchooser and can you select a webbrowser (safari) there? (I frankly don't know what "in an application based on the contents of the URL" means) Cheers, Thomas Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Launch Bug Report Wizard failing on Apple OS X (was "ksycoca4")
On 23/03/2014, at 6:38 PM, mk-li...@email.de wrote: > On 22 Mar 2014, at 23:41 , Ian Wadham 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 Description: Binary data >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: ksycoca4
On 22 Mar 2014, at 23:41 , Ian Wadham 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. Please, correct me if I am wrong there. Greets, Marko >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: ksycoca4
On 23/03/2014, at 4:52 AM, mk-li...@email.de wrote: > I just tried to start KDE's bug reporter from a little tutorial application > on MacOSX, but I got this spat out at the console: > — > $ tutorial2.app/Contents/MacOS/tutorial2 > tutorial2(1006)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to > open ksycoca from "/private/var/tmp/kdecache-marko/ksycoca4” That is a normal message. It just tells you where KDE libs is looking for the SyCoCa. 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 is OK most of the time. I do it routinely when building/testing KDE games. However, as I discovered only a few days ago, if KDE libs has to start another process, such as a plugin or maybe the bug reporter, you can fall foul of Apple OS X execution conventions --- or rather their absence. See the thread "taskgated: no signature" on the MacPorts Users list for the (slow) dawning of my understanding of this. Briefly, if you do "make install" with your test program, KDE's CMake-generated makefile will create an Apple OS X app "bundle" at /Applications/KDE4/tutorial2.app, which you can then execute in the proper Apple OS X way with: open /Applications/KDE4/tutorial2.app and all your special test-environment variables will also be effective. You might then find that your test works: my Palapeli plugin certainly did for me, but it had always crashed Palapeli before when testing UNIX/Linux-style, because although the plugin was found, it could not be loaded by the O/S. The drawback of using "open" to run the app is that your app's debugging output goes to the Apple OS X Console log, rather than stderr. For KDE bystanders: Apple OS X installs apps as "bundles" --- a tree of directories and files, starting at /.app --- and that tree contains all the info the app needs to run, not just the executables. I am about to dive into the following link (when I have time): https://developer.apple.com/library/ios/documentation/CoreFoundation/Conceptual/CFBundles/Introduction/Introduction.html As I said to Frank a while back, "They just do things differently in that town". > — > and nothing happened. > > I don’t know what goes wrong here. > Perhaps nothing? Try again? … :-) Cheers, Ian W. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: ksycoca4
On 22 Mar 2014, at 22:28 , Thomas Lübking wrote: > Define "nothing" - and what would you have expected? > Do you return to the prompt or would you expect a window to show up? > A link to the tutorial code would be helpful (to know what it's supposed to > do) It’s just a very basic app and I forgot to mention that I chose the “Help/Report Bug…” from the programs menu and then clicked “Launch Bug Report Wizard”… But the app doesn’t fire up a browser at b.k.o as it was supposed to do. Sorry, I missed to describe that above, because I got distracted when I posted that before... >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: ksycoca4
On Samstag, 22. März 2014 18:52:14 CEST, Marko wrote: Hi, I just tried to start KDE's bug reporter from a little tutorial application on MacOSX, but I got this spat out at the console: — $ tutorial2.app/Contents/MacOS/tutorial2 tutorial2(1006)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/private/var/tmp/kdecache-marko/ksycoca4” — and nothing happened. Define "nothing" - and what would you have expected? Do you return to the prompt or would you expect a window to show up? A link to the tutorial code would be helpful (to know what it's supposed to do) Cheers, Thomas Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
ksycoca4
Hi, I just tried to start KDE's bug reporter from a little tutorial application on MacOSX, but I got this spat out at the console: — $ tutorial2.app/Contents/MacOS/tutorial2 tutorial2(1006)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/private/var/tmp/kdecache-marko/ksycoca4” — and nothing happened. I don’t know what goes wrong here. Perhaps nothing? Greets, Marko >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
