Bug 560516

Summary: [abrt] crash in tk-1:8.5.7-3.fc12
Product: [Fedora] Fedora Reporter: mtwollet
Component: tkAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: agentbwoy007, albielshani86, aldotafoya, alejandro183, bartlett_adrian, boby_drack, christine.henry92, claudiomar.costa, covenist5, daniel.bouches, dannyel.olivares, davesama, ejderz, fedora, genarolaw, giovanni.conconi, horous68, inss.pamram, istanbulcu, jskarvad, leo.perrin, ljn917, luigi.cardeles, marco_fortina, maxime.tierre, mosky_7, mrpowerup, muadibas25, myclonepc, nobutyeahbutno, npajkovs, psummitt, ranjeetsih, ray, th-topo, tncarrolls, tvilarim, ulrich, yn.abid, youngster2002, zgarcia83
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:a2bfde0bdeaf0f9b5223f2147a8ea5084a35457e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 23:30:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
File: backtrace none

Description mtwollet 2010-02-01 01:34:22 UTC
abrt 1.0.4 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: wish /usr/bin/amsn
comment: tried to setup masn webcam on acer aspire one to view video and setup microphone								
component: tk
executable: /usr/bin/wish8.5
kernel: 2.6.31.12-174.2.3.fc12.i686.PAE
package: tk-1:8.5.7-3.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.in gnome went into sound prefs,  and set input to microphone 2 full volume
2.in amsn ran audio setup wizard , then when choosing input device i seleted plug:hw0
3.And continuning any futher result in a crash to record a sample file

Comment 1 mtwollet 2010-02-01 01:34:23 UTC
Created attachment 387931 [details]
File: backtrace

Comment 2 Nikola Pajkovsky 2010-02-25 18:23:44 UTC
*** Bug 554576 has been marked as a duplicate of this bug. ***

Comment 3 Nikola Pajkovsky 2010-02-25 18:27:03 UTC
*** Bug 553084 has been marked as a duplicate of this bug. ***

Comment 4 Nikola Pajkovsky 2010-02-25 18:27:32 UTC
*** Bug 547902 has been marked as a duplicate of this bug. ***

Comment 5 Nikola Pajkovsky 2010-02-25 18:32:13 UTC
*** Bug 546725 has been marked as a duplicate of this bug. ***

Comment 6 Amram 2010-03-21 03:35:23 UTC

How to reproduce
-----
1.Pidgin crash unexpectedly, only one XMPP account active at that moment
2.
3.


Comment
-----
Pidgin crash unexpectedly, only one XMPP account active at that moment

Comment 7 Amram 2010-03-22 21:29:25 UTC

How to reproduce
-----
1. AMSN crashed by itself.
2.
3.


Comment
-----
AMSN crashed by itself.

Comment 8 Amram 2010-03-24 14:13:18 UTC

How to reproduce
-----
1. it just crashed
2.
3.


Comment
-----
it just crashed

Comment 9 Jaroslav Škarvada 2010-03-24 14:43:04 UTC
I am new package maintainer, I am going to take closer look on it soon. For now I am unable to reproduce the crash with amsn. I will do more testing.

Comment 10 Jaroslav Škarvada 2010-03-28 22:50:36 UTC
Should anybody provide steps for reproducing the crash? I can't reproduce it from the steps described here. I was playing with amsn intensively for several days and no problem encountered so far.

Comment 11 Jaroslav Škarvada 2010-03-28 23:17:21 UTC
*** Bug 575617 has been marked as a duplicate of this bug. ***

Comment 12 Jaroslav Škarvada 2010-03-28 23:19:39 UTC
*** Bug 577447 has been marked as a duplicate of this bug. ***

Comment 13 Paul M. Summitt 2010-03-30 04:38:54 UTC

Comment
-----
tried to view video

Comment 14 Jaroslav Škarvada 2010-03-30 12:39:56 UTC
According to bugreports there is apparently problem but I cannot reproduce it. I just finished video call (thanks to Pavel Krivanek for being my testing peer) without any problem. I will go through all dumps (feel free to send here if you have any). I am also planning to push tk-8.5.8 update through Bodhi soon, maybe it will helps. Which version of amsn do you have? Mine amsn is version 0.98.1-3.fc12.

Comment 15 Jaroslav Škarvada 2010-03-30 12:55:43 UTC
*** Bug 563383 has been marked as a duplicate of this bug. ***

Comment 16 Jaroslav Škarvada 2010-03-30 12:58:57 UTC
*** Bug 565900 has been marked as a duplicate of this bug. ***

Comment 17 Jaroslav Škarvada 2010-03-30 13:00:52 UTC
*** Bug 563390 has been marked as a duplicate of this bug. ***

Comment 18 Jaroslav Škarvada 2010-03-30 13:02:59 UTC
*** Bug 560828 has been marked as a duplicate of this bug. ***

Comment 19 Jaroslav Škarvada 2010-03-30 13:07:49 UTC
*** Bug 551287 has been marked as a duplicate of this bug. ***

Comment 20 Jaroslav Škarvada 2010-03-30 13:11:06 UTC
*** Bug 540633 has been marked as a duplicate of this bug. ***

Comment 21 ranjeet kumar singh 2010-03-30 17:59:06 UTC

How to reproduce
-----
1.normal operation
2.
3.

Comment 22 CMB 2010-03-30 20:50:14 UTC

How to reproduce
-----
1.Im not sure.
2.But i think its when i recieve a message.
3.I have caught this behaving like this before and have reported many bug crashes with wish.


Comment
-----
These Are A Few Running plug Ins

"Eliza Perl v0.1"
"aMSN Plus v2.6"
"Jake v0.5.0"

Maybe the arguments.

I dont know if its plugins that are messing it up
but if i stop all plugins it doesnt crash.
Attached is pic of running plugins.

h**p://tinypic.com/view.php?pic=1zg9daw&s=5
h**p://yfrog.com/59runningamsnpluginsp

If need be i can upload their settings in text format.
Any config files of plugins can be hosted.

Comment 23 CMB 2010-03-30 20:58:11 UTC
aMSN-v0.98.1 (10/19/2009)

Comment 24 Amram 2010-03-31 00:17:55 UTC

How to reproduce
-----
1. amsn just crashed.
2.
3.

Comment 25 Jaroslav Škarvada 2010-03-31 14:39:11 UTC
After several days of playing with it I still didn't encounter the crash. The abrt dumps didn't help me to move. Maybe sometimes it is something wrong with TclEvalEx, sometimes not. Is there anybody who encounter crash on amsn without plugins? Should anybody provide full coredumps?

For anybody interested I just created patched experimental scratchbuilds:
http://jskarvad.fedorapeople.org/amsn/

Please report if you encounter crash with it. Please note it is only for testing purposes and uninstall it after testing - this builds won't be supported and may be incompatible with future updates.

Comment 26 Ulrich Walczak 2010-04-04 15:43:48 UTC

Comment
-----
adjusting sound in aMSN/Account/Preferences/Others/Audio and Video settings/Configuring audio settings - Step 3 - when I changed output device back to default and set volume to 100 it crashed

Comment 27 Jaroslav Škarvada 2010-04-04 18:28:41 UTC
(In reply to comment #26)
> 
> Comment
> -----
> adjusting sound in aMSN/Account/Preferences/Others/Audio and Video
> settings/Configuring audio settings - Step 3 - when I changed output device
> back to default and set volume to 100 it crashed    

Tested several times and works perfectly for me. 

I have been playing extensively with amsn (messages/video calls) since 2010-03-24 and so far I have encountered no crash.

Anybody with feedback to comment 25? Any improvement with these builds?

Comment 28 Luigi Cardeles 2010-04-04 18:50:53 UTC
@Jaroslav

this problem happen with me when i tried to make a video call with amsn with a msn account.
1 - start a video call with a msn account with another msn account using amsn.
2 - stop the video call
3 - start again the same or another video call.

This problem also happens if i use the webcam with another software (like cheese to take snapshots) and later try to use with amsn.

installed app:
amsn-0.98.1-3.fc12.x86_64
tk-8.5.7-3.fc12.x86_64
tcl-8.5.7-5.fc12.x86_64

Comment 29 Jaroslav Škarvada 2010-04-04 20:10:58 UTC
(In reply to comment #28)
> @Jaroslav
> 
> this problem happen with me when i tried to make a video call with amsn with a
> msn account.
> 1 - start a video call with a msn account with another msn account using amsn.
> 2 - stop the video call
> 3 - start again the same or another video call.
> 
> This problem also happens if i use the webcam with another software (like
> cheese to take snapshots) and later try to use with amsn.
> 
> installed app:
> amsn-0.98.1-3.fc12.x86_64
> tk-8.5.7-3.fc12.x86_64
> tcl-8.5.7-5.fc12.x86_64    

Great, thank you, looks like the right way - this is the first time I encountered freeze (but not crash) maybe the race condition - I end up with two "wish" processes holding the /dev/video. I will try this approach more times for debugging.

Please also try to install:

tcl-8.5.8-1.fc12.x86_64.rpm
tk-8.5.8-1.fc12.x86_64.rpm
amsn-0.98.3-1.fc12.x86_64.rpm 

experimental builds from link in comment 25 and check if the problem persists. Please report results.

Comment 30 CMB 2010-04-10 19:15:18 UTC

How to reproduce
-----
1.Make a new hotmail account
2.Add contact
3.Wait for crash


Comment
-----
My girlfriend made a new msn account on a windows box with windows live messenger
She added me as a contact that is runnung aMSN on fc12
As soon as she added me it crashed aMSN

Comment 31 CMB 2010-04-13 16:32:23 UTC

How to reproduce
-----
1.Leave amsn on all night.
2.Have a message up on desktop.
3.Close message, wait for crash which took about 5 mins to take place.


Comment
-----
Nothing out of ordinary was taking place while this crashed.
My responde bots worked as the chat window was open and i could see the post.
However my friend in which i was chating with had logged off and back on
a number off times as this was listed in the window showing his logoff times.
I have now had to install 2 new pkgs libs since updates to report this.

Comment 32 Amram 2010-04-18 19:51:11 UTC

How to reproduce
-----
1. just the msn account opened
2.
3.

Comment 33 Amram 2010-04-19 06:08:49 UTC

How to reproduce
-----
1. program was just opened with msn messenger.
2.
3.

Comment 34 muadibas25 2010-04-22 08:35:55 UTC

Comment
-----
It was randomly created when using aMSN.

Comment 35 Jaroslav Škarvada 2010-04-26 08:07:14 UTC
*** Bug 585682 has been marked as a duplicate of this bug. ***

Comment 36 Jaroslav Škarvada 2010-05-03 10:20:27 UTC
*** Bug 588066 has been marked as a duplicate of this bug. ***

Comment 37 Jaroslav Škarvada 2010-05-03 10:22:50 UTC
*** Bug 585436 has been marked as a duplicate of this bug. ***

Comment 38 Jaroslav Škarvada 2010-05-03 10:24:58 UTC
*** Bug 587092 has been marked as a duplicate of this bug. ***

Comment 39 Jaroslav Škarvada 2010-05-03 10:26:26 UTC
*** Bug 587936 has been marked as a duplicate of this bug. ***

Comment 40 Jaroslav Škarvada 2010-05-03 10:27:54 UTC
*** Bug 587954 has been marked as a duplicate of this bug. ***

Comment 41 Jaroslav Škarvada 2010-05-31 07:15:00 UTC
*** Bug 595172 has been marked as a duplicate of this bug. ***

Comment 42 Jaroslav Škarvada 2010-05-31 07:17:01 UTC
*** Bug 588539 has been marked as a duplicate of this bug. ***

Comment 43 Jaroslav Škarvada 2010-05-31 07:19:14 UTC
*** Bug 589341 has been marked as a duplicate of this bug. ***

Comment 44 Jaroslav Škarvada 2010-05-31 07:21:35 UTC
*** Bug 590585 has been marked as a duplicate of this bug. ***

Comment 45 Jaroslav Škarvada 2010-05-31 07:24:35 UTC
*** Bug 590860 has been marked as a duplicate of this bug. ***

Comment 46 Dave Gordon 2010-05-31 10:25:09 UTC
Package: tk-1:8.5.7-3.fc12
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


Comment
-----
Don't know what happened - was sleeping at the time :D

Comment 47 Dave Gordon 2010-06-02 00:29:10 UTC
Package: tk-1:8.5.7-3.fc12
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


Comment
-----
Didn't see it happen

Comment 48 Dave Gordon 2010-06-04 03:14:45 UTC
Package: tk-1:8.5.7-3.fc12
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


Comment
-----
? happened when I was not present

Comment 49 Jaroslav Škarvada 2010-06-07 07:32:27 UTC
*** Bug 600887 has been marked as a duplicate of this bug. ***

Comment 50 Jaroslav Škarvada 2010-06-08 09:31:25 UTC
*** Bug 601463 has been marked as a duplicate of this bug. ***

Comment 51 Dave Gordon 2010-06-08 11:25:11 UTC
Package: tk-1:8.5.7-3.fc12
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


Comment
-----
Was not aware it had crashed

Comment 52 Jaroslav Škarvada 2010-06-14 14:10:11 UTC
*** Bug 601678 has been marked as a duplicate of this bug. ***

Comment 53 Jaroslav Škarvada 2010-06-14 14:11:58 UTC
*** Bug 602583 has been marked as a duplicate of this bug. ***

Comment 54 Dave Gordon 2010-06-15 13:40:03 UTC
Package: tk-1:8.5.7-3.fc12
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


Comment
-----
Dont know what happened

Comment 55 juju 2010-06-19 15:05:59 UTC
Package: tk-1:8.5.7-3.fc12
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.start amsn
2.wait for a long time..
3.then crash (i was away from keyboard so i didn't see what's happened)

Comment 56 th-topo 2010-06-23 12:10:12 UTC
Package: tk-1:8.5.7-3.fc12
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


Comment
-----
nothing

Comment 57 Jaroslav Škarvada 2010-06-23 14:43:37 UTC
*** Bug 604816 has been marked as a duplicate of this bug. ***

Comment 58 Jaroslav Škarvada 2010-06-23 14:46:02 UTC
*** Bug 604823 has been marked as a duplicate of this bug. ***

Comment 59 Jaroslav Škarvada 2010-06-23 14:47:28 UTC
*** Bug 605284 has been marked as a duplicate of this bug. ***

Comment 60 Jaroslav Škarvada 2010-06-23 14:51:46 UTC
*** Bug 605449 has been marked as a duplicate of this bug. ***

Comment 61 Jaroslav Škarvada 2010-06-23 14:53:21 UTC
*** Bug 605551 has been marked as a duplicate of this bug. ***

Comment 62 Jaroslav Škarvada 2010-06-23 15:11:38 UTC
Please, could anybody try with tcl, tk version 8.5.8? There were several leaks fixed, hope it helps. Instructions for testers:

# wget "http://jskarvad.fedorapeople.org/amsn/tcl-8.5.8-1.fc12.x86_64.rpm"
# wget "http://jskarvad.fedorapeople.org/amsn/tk-8.5.8-1.fc12.x86_64.rpm"
# yum update --nogpgcheck tcl-8.5.8-1.fc12.x86_64.rpm tk-8.5.8-1.fc12.x86_64.rpm

You can get back to your previous (repo) versions with:
# yum downgrade tcl tk

These instructions are applicable for F12 and also for F13 (both x86_64). I can also provide builds for x86 if anybody is interested. Please anybody test it and let me know if it is still hanging, thanks. I cannot reproduce these hangs on my machines, sorry about that.

Comment 63 Giovanni Conconi 2010-06-23 16:08:40 UTC
(In reply to comment #62)

I'm interested in x86 builds, how can I get them?

Comment 64 juju 2010-06-23 16:09:27 UTC
Package: tk-1:8.5.7-3.fc12
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.start amsn.. and let the time roll..
2.
3.

Comment 65 juju 2010-06-23 16:31:40 UTC
i'm installing those files ... and i will test. Futur news ..later !

(In reply to comment #62)
> Please, could anybody try with tcl, tk version 8.5.8? There were several leaks
> fixed, hope it helps. Instructions for testers:
> 
> # wget "http://jskarvad.fedorapeople.org/amsn/tcl-8.5.8-1.fc12.x86_64.rpm"
> # wget "http://jskarvad.fedorapeople.org/amsn/tk-8.5.8-1.fc12.x86_64.rpm"
> # yum update --nogpgcheck tcl-8.5.8-1.fc12.x86_64.rpm
> tk-8.5.8-1.fc12.x86_64.rpm
> 
> You can get back to your previous (repo) versions with:
> # yum downgrade tcl tk
> 
> These instructions are applicable for F12 and also for F13 (both x86_64). I can
> also provide builds for x86 if anybody is interested. Please anybody test it
> and let me know if it is still hanging, thanks. I cannot reproduce these hangs
> on my machines, sorry about that.

Comment 66 Jiannan Liu 2010-06-24 08:11:47 UTC
(In reply to comment #62)
> Please, could anybody try with tcl, tk version 8.5.8? There were several leaks
> fixed, hope it helps. Instructions for testers:
> 
> # wget "http://jskarvad.fedorapeople.org/amsn/tcl-8.5.8-1.fc12.x86_64.rpm"
> # wget "http://jskarvad.fedorapeople.org/amsn/tk-8.5.8-1.fc12.x86_64.rpm"
> # yum update --nogpgcheck tcl-8.5.8-1.fc12.x86_64.rpm
> tk-8.5.8-1.fc12.x86_64.rpm
> 
> You can get back to your previous (repo) versions with:
> # yum downgrade tcl tk
> 
> These instructions are applicable for F12 and also for F13 (both x86_64). I can
> also provide builds for x86 if anybody is interested. Please anybody test it
> and let me know if it is still hanging, thanks. I cannot reproduce these hangs
> on my machines, sorry about that.    

I also want to know how to get x86 version.

Comment 68 juju 2010-06-24 12:14:50 UTC
i installed your files yesterday and started amsn just after... since i noticed nothing bad ! i thank the bug is over.. IMAO

Comment 69 Dave Gordon 2010-06-25 08:00:58 UTC
Package: tk-1:8.5.7-3.fc12
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


Comment
-----
was sleeping when it crashed

Comment 71 Fedora Update System 2010-07-07 19:25:32 UTC
tk-8.5.8-1.fc13,tcl-8.5.8-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/tk-8.5.8-1.fc13,tcl-8.5.8-1.fc13

Comment 72 Jaroslav Škarvada 2010-07-09 13:57:08 UTC
*** Bug 610935 has been marked as a duplicate of this bug. ***

Comment 73 Fedora Update System 2010-07-13 07:30:50 UTC
tk-8.5.8-1.fc13, tcl-8.5.8-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 74 Jaroslav Škarvada 2010-07-27 07:03:00 UTC
*** Bug 613052 has been marked as a duplicate of this bug. ***

Comment 75 Jaroslav Škarvada 2010-07-27 07:04:47 UTC
*** Bug 614261 has been marked as a duplicate of this bug. ***

Comment 76 Jaroslav Škarvada 2010-07-27 07:06:25 UTC
*** Bug 614268 has been marked as a duplicate of this bug. ***

Comment 77 Jaroslav Škarvada 2010-07-27 07:11:29 UTC
*** Bug 615098 has been marked as a duplicate of this bug. ***

Comment 78 Jaroslav Škarvada 2010-07-27 07:14:02 UTC
tcl/tk 8.5.8 update for F12 was pushed through bodhi. This bug will be auto-closed when it reach stable. If the problem persists feel free to reopen.

Comment 79 Fedora Update System 2010-07-27 07:19:40 UTC
tk-8.5.8-1.fc12,tcl-8.5.8-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/tk-8.5.8-1.fc12,tcl-8.5.8-1.fc12

Comment 80 Fedora Update System 2010-07-30 08:34:09 UTC
tk-8.5.8-1.fc12, tcl-8.5.8-1.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update tk tcl'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/tk-8.5.8-1.fc12,tcl-8.5.8-1.fc12

Comment 81 Bug Zapper 2010-11-03 23:23:52 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 82 Bug Zapper 2010-12-03 23:30:48 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.