[opensuse] Knotify4 crashes in KDE 4.4.4
Knotify4 crashes in KDE 4.4.4. I use kopete and when new message comes, the notification window looks strange. When I press "open", it almost always crashes (KDE debugger runs with segmentation errors). It seems was working ok till my unsuccessful try to switch to KDE 4.5. But the same problem I met at fresh opensuse 11.3 system. I'm not sure, if it's a kopete problem, because I don't get other notifications to check it. Does anyone has any suggestions what to do? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 05/09/10 17:41, arygroup@gmail.com wrote:
Knotify4 crashes in KDE 4.4.4. I use kopete and when new message comes, the notification window looks strange. When I press "open", it almost always crashes (KDE debugger runs with segmentation errors).
It seems was working ok till my unsuccessful try to switch to KDE 4.5. But the same problem I met at fresh opensuse 11.3 system.
I'm not sure, if it's a kopete problem, because I don't get other notifications to check it.
Does anyone has any suggestions what to do?
Im I the only person who meet this problem? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday, September 06, 2010 03:49:20 pm arygroup@gmail.com wrote:
Im I the only person who meet this problem?
i run kopete a lot, but switched off most notifications. when a new message comes in, the taskbar thingy starts rotating, but never crashed so far. perhaps a video driver issue? those sometimes mess up small things like that? no other 'funny' things happening on your system, display-related? -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 06/09/10 13:36, phanisvara das wrote:
On Monday, September 06, 2010 03:49:20 pm arygroup@gmail.com wrote:
Im I the only person who meet this problem?
i run kopete a lot, but switched off most notifications. when a new message comes in, the taskbar thingy starts rotating, but never crashed so far. perhaps a video driver issue? those sometimes mess up small things like that? no other 'funny' things happening on your system, display-related?
-- phani.
Nothing else strange seems to happen. Other, non-kopete notifies fail too. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 06 September 2010 12:19:20 arygroup@gmail.com wrote:
Im I the only person who meet this problem?
There's not enough information there to say. Read http://en.opensuse.org/openSUSE:Bugreport_KDE#Useful_Crash_Reports and then we might be able to help. Will -- Will Stephenson, KDE Developer, openSUSE Boosters Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 06/09/10 13:46, Will Stephenson wrote:
On Monday 06 September 2010 12:19:20 arygroup@gmail.com wrote:
Im I the only person who meet this problem?
There's not enough information there to say. Read http://en.opensuse.org/openSUSE:Bugreport_KDE#Useful_Crash_Reports and then we might be able to help.
I followed those steps till it asked me if my bug is a duplication of another and showed me a list of several bugs. I don't know what to do to be correct in this case. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 06 September 2010, arygroup@gmail.com wrote:
On 06/09/10 13:46, Will Stephenson wrote:
On Monday 06 September 2010 12:19:20 arygroup@gmail.com wrote:
Im I the only person who meet this problem?
There's not enough information there to say. Read http://en.opensuse.org/openSUSE:Bugreport_KDE#Useful_Crash_Reports and then we might be able to help.
I followed those steps till it asked me if my bug is a duplication of another and showed me a list of several bugs. I don't know what to do to be correct in this case.
You read the description of each bug - if one matches your experience then add your information to that bug - else create your new bug Simple -- “ ‘... but there is so much else behind what I say. It makes itself known to me so slowly, so incompletely! ...’ ” -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 06/09/10 12:41, arygroup@gmail.com wrote:
On 06/09/10 13:46, Will Stephenson wrote:
On Monday 06 September 2010 12:19:20 arygroup@gmail.com wrote:
Im I the only person who meet this problem? There's not enough information there to say. Read http://en.opensuse.org/openSUSE:Bugreport_KDE#Useful_Crash_Reports and then we might be able to help.
I followed those steps till it asked me if my bug is a duplication of another and showed me a list of several bugs. I don't know what to do to be correct in this case.
It's quite simple actually. Click on the title of a bug in the list of duplicates. This will display the details for that bug. If the description is similar to your issue, then just make a comment that you've got a similar issue, and describe anything different. If none of the duplicates match your issue, then proceed to create a new issue. There's nothing to be afraid of :-) -- Regards, Vadym ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ********************************************************************** -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 06/09/10 14:52, Vadym Krevs wrote:
It's quite simple actually. Click on the title of a bug in the list of duplicates. This will display the details for that bug. If the description is similar to your issue, then just make a comment that you've got a similar issue, and describe anything different. If none of the duplicates match your issue, then proceed to create a new issue. There's nothing to be afraid of :-)
It seems my bug report is a duplication of another. But the solution there is to install Qt 4.7.1 I searched for libqt4 in Yast and default repositories allow only 4.6.3 version. http://software.opensuse.org/search gives max 4.6.95 but I'm afraid installing it will cause many dependencies to change, -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 06 September 2010 15:31:32 arygroup@gmail.com wrote:
On 06/09/10 14:52, Vadym Krevs wrote:
It's quite simple actually. Click on the title of a bug in the list of duplicates. This will display the details for that bug. If the description is similar to your issue, then just make a comment that you've got a similar issue, and describe anything different. If none of the duplicates match your issue, then proceed to create a new issue. There's nothing to be afraid of :-)
It seems my bug report is a duplication of another. But the solution there is to install Qt 4.7.1 I searched for libqt4 in Yast and default repositories allow only 4.6.3 version.
That's impossible - Qt 4.7.1 (or any Qt 4.7 version) has not yet been released. Tell us what duplicate bug number you found. Will -- Will Stephenson, KDE Developer, openSUSE Boosters Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 06/09/10 17:09, Will Stephenson wrote:
On Monday 06 September 2010 15:31:32 arygroup@gmail.com wrote:
On 06/09/10 14:52, Vadym Krevs wrote:
It's quite simple actually. Click on the title of a bug in the list of duplicates. This will display the details for that bug. If the description is similar to your issue, then just make a comment that you've got a similar issue, and describe anything different. If none of the duplicates match your issue, then proceed to create a new issue. There's nothing to be afraid of :-)
It seems my bug report is a duplication of another. But the solution there is to install Qt 4.7.1 I searched for libqt4 in Yast and default repositories allow only 4.6.3 version.
That's impossible - Qt 4.7.1 (or any Qt 4.7 version) has not yet been released. Tell us what duplicate bug number you found.
Will
Well, then I didn't understand what I read. #226721 There was phrase: Patch landed in Qt 4.7.1 When I try to append my report is warns me, because it may be the same issue, as already submitted. It say I have to submit, if I'm sure that my bug is dufferent. I'm not sure, I'm a newbie. Besides, it said, that the bug is closed because it's not a KDE problem. but another package problem. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am Montag, 6. September 2010, 16:36:20 schrieb arygroup@gmail.com:
That's impossible - Qt 4.7.1 (or any Qt 4.7 version) has not yet been released. Tell us what duplicate bug number you found.
Well, then I didn't understand what I read. #226721
There was phrase: Patch landed in Qt 4.7.1
Yet Qt 4.7.1 is not released yet and it is in .1 because .0 already had release candidate status when the fix was added.
Besides, it said, that the bug is closed because it's not a KDE problem. but another package problem.
It is a Qt bug thus the bug report was "moved" to Qt's bug tracker. Sven -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 08/09/10 11:37, Sven Burmeister wrote:
Am Montag, 6. September 2010, 16:36:20 schrieb arygroup@gmail.com:
That's impossible - Qt 4.7.1 (or any Qt 4.7 version) has not yet been released. Tell us what duplicate bug number you found.
Well, then I didn't understand what I read. #226721
There was phrase: Patch landed in Qt 4.7.1
Yet Qt 4.7.1 is not released yet and it is in .1 because .0 already had release candidate status when the fix was added.
Besides, it said, that the bug is closed because it's not a KDE problem. but another package problem.
It is a Qt bug thus the bug report was "moved" to Qt's bug tracker.
Sven
I had to remove xfce4-notifyd to stop notification crashes in KDE. It seems xfce4-notifyd was the problem. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2010/09/08 12:07 (GMT+0300) arygroup@gmail.com composed:
On 08/09/10 11:37, Sven Burmeister wrote:
Am Montag, 6. September 2010, 16:36:20 schrieb arygroup@gmail.com:
That's impossible - Qt 4.7.1 (or any Qt 4.7 version) has not yet been released. Tell us what duplicate bug number you found.
Well, then I didn't understand what I read. #226721
I get "You are not authorized to access bug #226721." on attempting to find out what it's about. Is that a Novell bug, or https://bugs.kde.org/show_bug.cgi?id=226721 ? When referring to bugs, please always give full URL.
There was phrase: Patch landed in Qt 4.7.1
Yet Qt 4.7.1 is not released yet and it is in .1 because .0 already had release candidate status when the fix was added.
Besides, it said, that the bug is closed because it's not a KDE problem. but another package problem.
It is a Qt bug thus the bug report was "moved" to Qt's bug tracker.
I had to remove xfce4-notifyd to stop notification crashes in KDE. It seems xfce4-notifyd was the problem.
*notifyd* is not installed on my 11.2 KDE3 system, yet I get knotify4 crash notifications on logging into KDE3 each time. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 08/09/10 14:01, Felix Miata wrote:
I get "You are not authorized to access bug #226721." on attempting to find out what it's about. Is that a Novell bug, or https://bugs.kde.org/show_bug.cgi?id=226721 ? When referring to bugs, please always give full URL.
I saw the number in my KDE-bug report window. There was no any URL there, or I didn't mention it.
I had to remove xfce4-notifyd to stop notification crashes in KDE. It seems xfce4-notifyd was the problem.
*notifyd* is not installed on my 11.2 KDE3 system, yet I get knotify4 crash notifications on logging into KDE3 each time.
:-( -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 08/09/10 14:01, Felix Miata wrote:
*notifyd* is not installed on my 11.2 KDE3 system, yet I get knotify4 crash notifications on logging into KDE3 each time.
I fount out what is wrong when alt-tabbing with a notification popup active. My crash was each time I opend or closed the notification. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
arygroup＠gmail.com -
Dylan -
Felix Miata -
phanisvara das -
Sven Burmeister -
Vadym Krevs -
Will Stephenson