aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: systray integration bug, KDE 3.2.2  (Read 1741 times)

wolferz

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 12
systray integration bug, KDE 3.2.2
« on: November 23, 2004, 06:42:44 PM »
When i enable systray integration, specificly KDE 3.x, and with minimize to tray selected, amule will crash when minimising, seemlingly at random.  also it will crash when changing windows quickly or maximising amule, or when leaving the options dialog.  im using wxWidgets 2.5.3 linked against GTK 1.2.10.  the problem did not exist when using wxWidgets 2.4.2 though i had other problems then (see http://forum.amule.org/thread.php?threadid=4205&sid= ), with systray integration turned off the crashes go away completely.

i would provide a back trace but unfortunatly when i use gdb as outlined in http://www.amule.org/wiki/index.php/Backtraces i find that amule will not even load fully.  it opens and then displays the number of servers in servers.met, the number of part files, and the number of shared files in the log window, then it freezes.  this is with --enable-debug --disable-optimise, and i tried moving my .aMule folder and .eMule file as well (thinking it might be taking it a long time to parse my huge share folder or something to that effect).

any way my system is 2.5.6-gentoo-r1 on a pentium 3 1ghz.  anything else you need to know ask here ill be checking back later.
Logged

Jacobo221

  • Hero Member
  • *****
  • Karma: 3
  • Offline Offline
  • Posts: 2712
Re: systray integration bug, KDE 3.2.2
« Reply #1 on: November 25, 2004, 01:32:21 PM »
the thing is that systray has been recently rewritten. the new systray code is enabled when using wx 2.5.x while the old systray code is used when using wx 2.4.x
Those bugs you report are known to the systray integration and are being worked on by kry. but some, unfortunately, are wx related, so only wx devs can fix them when releasinga new wxWidgets version :-(let's hope next wx 2.6.x will have htem fixed...

Greetings and thanks for the report!
Logged