Opened 12 years ago

Closed 12 years ago

#36644 closed defect (worksforme)

kde4-kile does not fire-up

Reported by: ramebal@… Owned by: NicosPavlov
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: Cc:
Port: kde4-kile

Description

Installing kde4-kile worked fine. However, when I start kile by opening the kile icon from macports applications basket, it tries coming up for some time and then vanishes without firing up. I followed procedure described at http://www.tosnos.com/?p=28. I tried solution suggested in ticket #36503, but did not help. Is there a solution? Thanks.

Change History (7)

comment:1 Changed 12 years ago by mf2k (Frank Schima)

Owner: changed from macports-tickets@… to nicos@…
Port: kde4-kile added

In the future, please fill in the Port field and Cc the port maintainer(s).

comment:2 Changed 12 years ago by NicosPavlov

I don't think it is possible to know the issue without more information. Are there log lines from Kile in the log (System.log in /Utilities/Console), or is there an output when launching the application from the Terminal (/Applications/MacPorts/KDE4/Kile.app/Contents/MacOS/Kile in cas of standard paths) ?

comment:3 Changed 12 years ago by mf2k (Frank Schima)

Do other X11 applications work such as xeyes?

comment:4 Changed 12 years ago by ramebal@…

Apologies... Following is the output as Kile crashes when I start from the terminal as suggested. Hope this helps... I do not use xeyes but xfig and xmgrace work with no problems

ramesh

----------------

QIODevice::setTextModeEnabled: The device is not open kile(790)/KSharedDataCache ensureFileAllocated: This system misses support for posix_fallocate() -- ensure this partition has room for at least 10547296 bytes. kile(790)/KSharedDataCache: Unable to find an appropriate lock to guard the shared cache. This *should* be essentially impossible. :( kile(790)/KSharedDataCache: Unable to perform initial setup, this system probably does not really support process-shared pthreads or semaphores, even though it claims otherwise. kile(790)/KSharedDataCache: Unable to unmap shared memory segment 0x109b9d000 Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! kile(790)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) KCrash: Application 'Kile' crashing... KCrash: Attempting to start from kdeinit Warning: Path of socketfile exceeds UNIX_PATH_MAX. KCrash: Attempting to start directly KCrash failed to exec(), errno = 2

comment:5 Changed 12 years ago by ramebal@…

just installed and checked that xeyes works too... - ramesh

comment:6 Changed 12 years ago by ramebal@…

Following the answer to ticket #31958, I launched dbus (had not know that it had to be started manually) and started kile and it is working now! Thanks for the support on this forum.

comment:7 Changed 12 years ago by NicosPavlov

Resolution: worksforme
Status: newclosed

Ok, good to know that it is now working.

Every KDE software indeed requires dbus to be launched with the command indicated during installation.

Note: See TracTickets for help on using tickets.