Thread: [aKregator-devel] [Bug 142306] akregator segfaults and crashes on startup.
Brought to you by:
lippel
From: Bram S. <bra...@kd...> - 2007-02-28 19:46:15
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=142306 bramschoenmakers kde nl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID ------- Additional Comments From bramschoenmakers kde nl 2007-02-28 20:45 ------- Whenever you want to run bleeding edge software, make sure you know what you are doing. Those undefined symbols are most probably due to a wrong environment. |
From: Vic F. <vi...@sh...> - 2007-02-28 19:59:38
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=142306 vic shellsage com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID | ------- Additional Comments From vic shellsage com 2007-02-28 20:59 ------- Actually, the environment is a vanilla instance of what's described here: http://techbase.kde.org/Getting_Started/Build/Unstable_Version . And, other applications work fine, without issue. I was aware that there were DBus errors listed in the debug output, but that doesn't make the bug invalid off the bat. |
From: Frank O. <fra...@kd...> - 2007-02-28 20:19:55
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=142306 frank.osterfeld kdemail net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID ------- Additional Comments From frank.osterfeld kdemail net 2007-02-28 21:19 ------- This bug is reproducible and already known, however, the bug tracker is for reporting bugs against released versions (or stable branches), not for KDE4 development snapshots or trunk checkouts (if that was changed officially, I'd stand corrected, but I don't think it was). trunk is known to be extremely buggy, reporting each and every bug from there won't help and just shadow the important bugs from 3.5.x versions. |
From: Vic F. <vi...@sh...> - 2007-02-28 20:23:48
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=142306 ------- Additional Comments From vic shellsage com 2007-02-28 21:23 ------- Thanks Frank. That's fine, but in the bug wizard there was an option for "Recent SVN or Snapshot Version", and thus I thought I'd file it. Is there a better place to report/work on bugs like this? |
From: Frank O. <fra...@kd...> - 2007-02-28 20:47:05
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=142306 ------- Additional Comments From frank.osterfeld kdemail net 2007-02-28 21:47 ------- Hmm, there is no systematic way for this - but actually it's a good idea to write them down - especially the bugs that are more subtle and hidden than this one. I created a wiki page as a start: http://akregator.kde.org/wiki/index.php/Main_Page Feel free to add it there - short notes like "Akregator crashes on startup when loading metakit plugin" might be even better suited here than extensive reports (which wiki pages aren't very useful for I think). |
From: Vic F. <vi...@sh...> - 2007-02-28 21:02:27
|
------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=142306 ------- Additional Comments From vic shellsage com 2007-02-28 22:02 ------- Great, I created the page with that first bug. Thanks again. |