Bug 321601 - kile always crashes during the startup process.
Summary: kile always crashes during the startup process.
Status: RESOLVED WORKSFORME
Alias: None
Product: kile
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Michel Ludwig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-25 14:36 UTC by Marcus
Modified: 2013-09-17 00:47 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus 2013-06-25 14:36:16 UTC
Version: Kile 3 beta 1
OS: Windows 7 32 bit, KDE 4.10.2 for Windows

There are no exceptions, but no obvious reasons for the behavior of kile. I click on Start -> Programs -> KDE release 4.10.2 -> Office Tools -> Kile. Kile starts and displays the Home screen "Kile ³ beta 1". Then Kile crashed (before it has finished loading).

Reproducible: Always

Steps to Reproduce:
1. Start Kile
2. Kile crashed while the start process.
Comment 1 mh00h 2013-06-25 18:01:30 UTC
I can confirm this bug in vanilla Ubuntu 13.10. Here is what I have noticed so far:

Kile originally was crashing whenever I closed a popup window of any kind. Opening a file, creating a new file, tips of the day- whenever the pop up window closed, kile would crash with it.

Running kile from a terminal would only show an undefined X server error.

If I run "gksudo Kile" it solves the problem, but I loose theming. Kile is basically unusable for the moment :(    :(    :(
Comment 2 Jekyll Wu 2013-06-26 02:43:57 UTC
(In reply to comment #1)
> I can confirm this bug in vanilla Ubuntu 13.10. Here is what I have noticed
> so far:
> 
> Kile originally was crashing whenever I closed a popup window of any kind.
> Opening a file, creating a new file, tips of the day- whenever the pop up
> window closed, kile would crash with it.
> 
> Running kile from a terminal would only show an undefined X server error.
> 
> If I run "gksudo Kile" it solves the problem, but I loose theming. Kile is
> basically unusable for the moment :(    :(    :(

Your problem is probably a different one. Please provide the backtrace of the crash.
Comment 3 mh00h 2013-06-26 20:24:38 UTC
~  kile
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
kile(11077)/kdecore (KLibrary) findLibraryInternal: plugins should not have a 'lib' prefix: "libkonsolepart.so"
kile(11077) KSambaSharePrivate::getNetUserShareInfo: We got some errors while running 'net usershare info' 
kile(11077) KSambaSharePrivate::getNetUserShareInfo: "info_fn: file /var/lib/samba/usershares/netshare is not a well formed usershare file.
info_fn: Error was Path is not a directory.
" 
kile(11077)/konsole Konsole::Session::run: Attempted to re-run an already running session. 
kile(11077) KSambaSharePrivate::getNetUserShareInfo: We got some errors while running 'net usershare info' 
kile(11077) KSambaSharePrivate::getNetUserShareInfo: "info_fn: file /var/lib/samba/usershares/netshare is not a well formed usershare file.
info_fn: Error was Path is not a directory.
" 
kile(11077) KSambaSharePrivate::getNetUserShareInfo: We got some errors while running 'net usershare info' 
kile(11077) KSambaSharePrivate::getNetUserShareInfo: "info_fn: file /var/lib/samba/usershares/netshare is not a well formed usershare file.
info_fn: Error was Path is not a directory.
" 

##################close popup window on kile startup

The program 'kile' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 1567 error_code 3 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
kile(11077)/konsole Konsole::SessionManager::~SessionManager: Konsole SessionManager destroyed with sessions still alive 
➜  ~
Comment 4 Christoph Feck 2013-07-05 12:56:30 UTC
Matt, this is not a backtrace, but only the Konsole output. For more information about creating backtraces for crashes, please see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 5 Jekyll Wu 2013-07-09 15:58:07 UTC
The problem in comment #3 is a problem of ubuntu packages, see https://bugs.launchpad.net/ubuntu/+source/kile/+bug/1195007. Very unlikely to be related with the original report.
Comment 6 mh00h 2013-07-09 18:11:02 UTC
Ah- thank you very much for pointing that out. I retract my previous comments. Thank you again.
Comment 7 Jekyll Wu 2013-09-16 02:50:52 UTC
Marcus, could you problem the backtrace of the crash ?
Comment 8 Marcus 2013-09-16 15:47:10 UTC
Am 16.09.2013 04:50, schrieb Jekyll Wu:
> https://bugs.kde.org/show_bug.cgi?id=321601
>
> Jekyll Wu <adaptee@gmail.com> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>               Status|UNCONFIRMED                 |NEEDSINFO
>           Resolution|---                         |BACKTRACE
>
> --- Comment #7 from Jekyll Wu <adaptee@gmail.com> ---
> Marcus, could you problem the backtrace of the crash ?
>

Hello all together,

meanwhile I have re-installed KDE for Windows. This solves the problem 
(the devil knows what the reason was). Now I have KDE 4.10.2 release and 
Kile beta 3 version 9.2.60.

Best regards
Marcus
Comment 9 Jekyll Wu 2013-09-17 00:47:49 UTC
Glad to here it is working for you now.