[akregator] [Bug 393672] akregator crashing on startup

2018-05-11 Thread Bernd Steinhauser
https://bugs.kde.org/show_bug.cgi?id=393672

--- Comment #1 from Bernd Steinhauser  ---
I updated Qt from 5.9 to 5.10 and with that akregator works again, so I think
this might have been caused by a upstream bug in Qt.
Feel free to close it.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 393672] New: akregator crashing on startup

2018-04-30 Thread Bernd Steinhauser
https://bugs.kde.org/show_bug.cgi?id=393672

Bug ID: 393672
   Summary: akregator crashing on startup
   Product: akregator
   Version: unspecified
  Platform: Exherbo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: li...@bernd-steinhauser.de
  Target Milestone: ---

Since 16.04 (maybe in combination with a KF5 update, can't tell), akregator is
crashing on me.
I've already tried with a clean config, because at first I thought it was
config-related.

If I start it from within konsole, I get these messages:
[1:1:0100/00.357507:ERROR:broker_posix.cc(41)] Invalid node channel message
[1:1:0100/00.358594:ERROR:broker_posix.cc(41)] Invalid node channel message
QSocketNotifier: Invalid socket 12 and type 'Read', disabling...
QSocketNotifier: Invalid socket 54 and type 'Read', disabling...
QSocketNotifier: Invalid socket 52 and type 'Read', disabling...
KCrash: Application 'akregator' crashing...
KCrash: Attempting to start /usr/x86_64-pc-linux-gnu/libexec/drkonqi from
kdeinit
sock_file=/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 76 and type 'Read', disabling...
QSocketNotifier: Invalid socket 71 and type 'Read', disabling...
zsh: suspended (signal)  akregator

(the above file existent)
Hence, I think it might be related to kdeinit5 or rather the socket it's trying
to connect to, but I'm not sure.
If I start Akregator from another user that does have access to X11 (as in: can
show a window), but doesn't have access to kdeinit and dbus, akregator will
start and not crash (it won't work either, though, because of the missing
connectivity).

Backtrace:

Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library
"/usr/x86_64-pc-linux-gnu/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f017ade5b40 (LWP 2502))]

Thread 34 (Thread 0x7f00b1536700 (LWP 2552)):
#0  0x7f0168cdd294 in pthread_cond_wait () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#1  0x7f0150cd1b7b in util_queue_thread_func () from
/usr/x86_64-pc-linux-gnu/lib/dri/radeonsi_dri.so
#2  0x7f0150cd1ac7 in impl_thrd_routine () from
/usr/x86_64-pc-linux-gnu/lib/dri/radeonsi_dri.so
#3  0x7f0168cd750a in start_thread () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#4  0x7f017aedbc8f in clone () from /usr/x86_64-pc-linux-gnu/lib/libc.so.6

Thread 33 (Thread 0x7f00b1d37700 (LWP 2551)):
#0  0x7f0168cdd294 in pthread_cond_wait () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#1  0x7f0150cd1b7b in util_queue_thread_func () from
/usr/x86_64-pc-linux-gnu/lib/dri/radeonsi_dri.so
#2  0x7f0150cd1ac7 in impl_thrd_routine () from
/usr/x86_64-pc-linux-gnu/lib/dri/radeonsi_dri.so
#3  0x7f0168cd750a in start_thread () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#4  0x7f017aedbc8f in clone () from /usr/x86_64-pc-linux-gnu/lib/libc.so.6

Thread 32 (Thread 0x7f00b2ffd700 (LWP 2544)):
#0  0x7f0168cdd5ca in pthread_cond_timedwait () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#1  0x7f017b776e28 in QWaitConditionPrivate::wait_relative (time=3,
this=0x557547396680) at thread/qwaitcondition_unix.cpp:133
#2  QWaitConditionPrivate::wait (time=3, this=0x557547396680) at
thread/qwaitcondition_unix.cpp:141
#3  QWaitCondition::wait (this=this@entry=0x557547396390,
mutex=mutex@entry=0x55754738bc70, time=3) at
thread/qwaitcondition_unix.cpp:215
#4  0x7f017b7719c0 in QThreadPoolThread::run (this=0x557547396380) at
thread/qthreadpool.cpp:144
#5  0x7f017b776861 in QThreadPrivate::start (arg=0x557547396380) at
thread/qthread_unix.cpp:368
#6  0x7f0168cd750a in start_thread () from
/usr/x86_64-pc-linux-gnu/lib/libpthread.so.0
#7  0x7f017aedbc8f in clone () from /usr/x86_64-pc-linux-gnu/lib/libc.so.6

Thread 31 (Thread 0x7f00b37fe700 (LWP 2543)):
#0  0x7f0162e586a0 in g_poll () from
/usr/x86_64-pc-linux-gnu/lib/libglib-2.0.so.0
#1  0x7f0162e49a11 in g_main_context_iterate.isra () from
/usr/x86_64-pc-linux-gnu/lib/libglib-2.0.so.0
#2  0x7f0162e49b1c in g_main_context_iteration () from
/usr/x86_64-pc-linux-gnu/lib/libglib-2.0.so.0
#3  0x7f017b984500 in QEventDispatcherGlib::processEvents
(this=0x5575473888d0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f017b92ab53 in QEventLoop::processEvents
(this=this@entry=0x7f00b37fda60, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:134
#5  0x7f017b92af68 in QEventLoop::exec (this=this@entry=0x7f00b37fda60,
flags=flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f017b770410 in QThread::exec (this=) at
thread/qthread.cpp:515
#7  0x7f017b770495 in QThread::run (this=) at
thread/qthread.cpp:582
#8  0x7f017b776861 in QThreadPrivate::start (arg=0x7f00ac035170) at
thread/qthread_unix.cpp:368
#9  0x7f0168cd750a in start_thread () from
/usr/x86_64

[akregator] [Bug 381929] Feeds list gets corrupted when akregator is restored on log in

2017-07-17 Thread Bernd Steinhauser
https://bugs.kde.org/show_bug.cgi?id=381929

--- Comment #10 from Bernd Steinhauser  ---
(In reply to Christophe Giboudeaux from comment #9)
> did it start refreshing a feed when you closed it ?

Sorry, did not pay attention to that, so can't really tell.

Afterwards, I did try to enforce that by hitting the fetch all feeds button and
then closing Akregator, but it didn't trigger this.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 381929] Feeds list gets corrupted when akregator is restored on log in

2017-07-16 Thread Bernd Steinhauser
https://bugs.kde.org/show_bug.cgi?id=381929

--- Comment #8 from Bernd Steinhauser  ---
Just tried again and it's definitely not only on log in.
Took me maybe 10 restarts of Akregator until I got the message that the feed
list is corrupted.
In that case it also told me that Akregator didn't close properly, although
there was no indication of a crash (no coredump, no bug message etc.).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 381929] Akregator looses feed list

2017-07-16 Thread Bernd Steinhauser
https://bugs.kde.org/show_bug.cgi?id=381929

--- Comment #6 from Bernd Steinhauser  ---
Maybe I should add that I've seen the corruption after quitting Akregator only
once (out of 10-20 times), it seems much more unlikely.
When you don't specifically close Akregator before reboot, it seems much more
likely that the list gets corrupted (maybe 2 out of 3 times).

To me this smells like some sort of race condition.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 381929] Akregator looses feed list

2017-07-16 Thread Bernd Steinhauser
https://bugs.kde.org/show_bug.cgi?id=381929

--- Comment #5 from Bernd Steinhauser  ---
(In reply to Christian Boltz from comment #4)
> (In reply to Bernd Steinhauser from comment #3)
> d) using the menu File - Quit
I chose
e) right-click on the tray icon and choose Quit, which should be the same
thing. Next start of Akregator (without rebooting) -> list trashed

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 381929] Akregator looses feed list

2017-07-16 Thread Bernd Steinhauser
https://bugs.kde.org/show_bug.cgi?id=381929

--- Comment #3 from Bernd Steinhauser  ---
Just wanted to add that I observed this bug as well when I close Akregator
manually.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 381929] Akregator looses feed list

2017-07-15 Thread Bernd Steinhauser
https://bugs.kde.org/show_bug.cgi?id=381929

Bernd Steinhauser  changed:

   What|Removed |Added

 CC||li...@bernd-steinhauser.de

--- Comment #2 from Bernd Steinhauser  ---
Possibly a duplicate of bug 381822.

Anyway, I started to see this problem as well and it started exactly after I
upgraded Qt from 5.8.0 to 5.9.1.
I did rebuild Akregator and it's dependencies (up from Qt, obviously), but that
didn't help either.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 45760] don't show folders / emails / etc. selected with the right mouse button

2010-05-08 Thread Bernd Steinhauser
https://bugs.kde.org/show_bug.cgi?id=45760


Bernd Steinhauser  changed:

   What|Removed |Added

 CC||li...@bernd-steinhauser.de




-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs