Bug 562293

Created attachment 389182 [details]
File: backtrace

Can you reliably reproduce this?  Please describe the exact conditions that
lead to the crash.  Crash reports without detailed information describing
exactly how to reproduce the bug are almost impossible to fix.

How to reproduce
-----
1. double click an avi file to play in miro
2.
3.


Comment
-----
The WAN link was very congested

(In reply to comment #3)
> 
> How to reproduce
> -----
> 1. double click an avi file to play in miro

That's really not specific enough.  Was it all avi files, or just particular one's that triggered this bug.  Can you provide a URL to download the particular troublesome avi fi.e

> The WAN link was very congested    

Not sure what you mean by this, do you mean that the network was congested as a result of clicking the file to play in Miro, or before?

Will: have you seen this bug before?  Several people have reported it.

(Incidentally I notice you are no longer on the bugzilla watchlist for Miro, is this intentional, or did you not get added to the recent branches (F-12 and later)?)

(In reply to comment #5)
> Will: have you seen this bug before?  Several people have reported it.
> 
> (Incidentally I notice you are no longer on the bugzilla watchlist for Miro, is
> this intentional, or did you not get added to the recent branches (F-12 and
> later)?)    

I've never seen this before, but I'm not really sure what I'm looking at with this bug, either.

I didn't intentionally drop off a watchlist.  Is it the case that every time there's a new F, I have to sign up for a new watchlist?

(In reply to comment #6)
> (In reply to comment #5)
> > Will: have you seen this bug before?  Several people have reported it.
> > 
> > (Incidentally I notice you are no longer on the bugzilla watchlist for Miro, is
> > this intentional, or did you not get added to the recent branches (F-12 and
> > later)?)    
> 
> I've never seen this before, but I'm not really sure what I'm looking at with
> this bug, either.
> 
> I didn't intentionally drop off a watchlist.  Is it the case that every time
> there's a new F, I have to sign up for a new watchlist?    

I think you need to be watching the "devel" (aka "rawhide") branch in order to be "rolled-over" from release to release.  Best thing to do would be add yourself as watchbugzilla and watchcommits on the devel, F-13, F-12 branches here:

https://admin.fedoraproject.org/pkgdb/acls/name/Miro

(In reply to comment #4)
> (In reply to comment #3)
> > 
> > How to reproduce
> > -----
> > 1. double click an avi file to play in miro
> 
> That's really not specific enough.  Was it all avi files, or just particular
> one's that triggered this bug.  Can you provide a URL to download the
> particular troublesome avi fi.e
> 
> > The WAN link was very congested    
> 
> Not sure what you mean by this, do you mean that the network was congested as a
> result of clicking the file to play in Miro, or before?    

Hi Alex ... my apologies for being vague.

I can't confirm that all occurrences are for the same internal issue in Miro, but I frequently experience this:
1.  I have a 384k ADSL line.  I run ktorrent, and it's usually running at max incoming, but throttled to 7 kilobytes/sec upload.
2.  On an already downloaded file on my drive, I right-click on an AVI that I wish to watch (so it's not always the same file) and select "Open with Miro".  3.  Sometimes then Miro crashes and ABRT pops up.  But in last night's case, after it crashed I just tried again and then it worked (on the same file).

When it DOESN'T crash, it opens and then a green dot flicks next to the "Video" word on the left had panel.  I don't know if Miro is looking something up on the Web each time it opens.  That is why I thought that if my ADSL line was congested it might cause a timeout or host unreachable condition which might be the cause of the fault.  But that is guess-work on my part.

I will be sure to look out for more specifics next time it happens.

Regards
Louis

(In reply to comment #8)
> I can't confirm that all occurrences are for the same internal issue in Miro,
> but I frequently experience this:
> 1.  I have a 384k ADSL line.  I run ktorrent, and it's usually running at max
> incoming, but throttled to 7 kilobytes/sec upload.
> 2.  On an already downloaded file on my drive, I right-click on an AVI that I
> wish to watch (so it's not always the same file) and select "Open with Miro". 
> 3.  Sometimes then Miro crashes and ABRT pops up.  But in last night's case,
> after it crashed I just tried again and then it worked (on the same file).
> 
> When it DOESN'T crash, it opens and then a green dot flicks next to the "Video"
> word on the left had panel.  I don't know if Miro is looking something up on
> the Web each time it opens.  That is why I thought that if my ADSL line was
> congested it might cause a timeout or host unreachable condition which might be
> the cause of the fault.  But that is guess-work on my part.
> 
> I will be sure to look out for more specifics next time it happens.

The error in the bug description is a gconf error where gconf is trying to access its data and can't.

Is your home directory on an NFS mount or something like that?  What's unusual about your system setup?

(In reply to comment #9)
> (In reply to comment #8)
> > I can't confirm that all occurrences are for the same internal issue in Miro,
> > but I frequently experience this:
> > 1.  I have a 384k ADSL line.  I run ktorrent, and it's usually running at max
> > incoming, but throttled to 7 kilobytes/sec upload.
> > 2.  On an already downloaded file on my drive, I right-click on an AVI that I
> > wish to watch (so it's not always the same file) and select "Open with Miro". 
> > 3.  Sometimes then Miro crashes and ABRT pops up.  But in last night's case,
> > after it crashed I just tried again and then it worked (on the same file).
> > 
> > When it DOESN'T crash, it opens and then a green dot flicks next to the "Video"
> > word on the left had panel.  I don't know if Miro is looking something up on
> > the Web each time it opens.  That is why I thought that if my ADSL line was
> > congested it might cause a timeout or host unreachable condition which might be
> > the cause of the fault.  But that is guess-work on my part.
> > 
> > I will be sure to look out for more specifics next time it happens.
> 
> The error in the bug description is a gconf error where gconf is trying to
> access its data and can't.
> 
> Is your home directory on an NFS mount or something like that?  What's unusual
> about your system setup?    

The system was upgraded from Fedora 10 to 11 and then to 12. It has two additrional ext3 partitions mounted under /mnt/a2 and /mnt/b1. I download to my home folder and move to these two mounts. The motherboard had to be chbnaged while on F11. It was always 64 bit buT has gone from AMD cpu with ATI GPU to Intel cpu and onboard intel gpu.

I can't think of anythinng else.

Reporter: can you still reproduce this in the current version of Miro: 3.0.2?  If not, or if I don't hear a response within 1 week, I'll close this bug.  If you can reproduce you're always free to re-open it.

Miro-3.0.3-1.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/Miro-3.0.3-1.fc14

Miro-3.0.3-1.fc13 has been submitted as an update for Fedora 13.
https://admin.fedoraproject.org/updates/Miro-3.0.3-1.fc13

Miro-3.0.3-1.fc12 has been submitted as an update for Fedora 12.
https://admin.fedoraproject.org/updates/Miro-3.0.3-1.fc12

Miro-3.0.3-1.fc14 has been pushed to the Fedora 14 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 Miro'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/Miro-3.0.3-1.fc14

Miro-3.0.3-1.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

Miro-3.0.3-1.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Miro-3.0.3-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

I would like to reopen this bug cause abrt found it for my issue.

upgrade.py:77:upgrade:GError: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)

Traceback (most recent call last):
  File "/usr/bin/miro.real", line 48, in <module>
    upgrade.upgrade()
  File "/usr/lib64/python2.6/site-packages/miro/plat/upgrade.py", line 77, in upgrade
    if client.dir_exists("/apps/democracy/player") and not client.dir_exists("/apps/miro"):
GError: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)

Local variables in innermost frame:
old_file: '/home/raphael/.config/autostart/democracyplayer.desktop'
src: '/home/raphael/.democracy'
config_home: '~/.config'
dst: '/home/raphael/.miro'
destination: '/home/raphael/.config/autostart/miro.desktop'
autostart_dir: '/home/raphael/.config/autostart'
client: <gconf.Client object at 0x1e61550 (GConfClient at 0x1ea9860)>
_copy_gconf: <function _copy_gconf at 0x1d662a8>

(In reply to comment #19)
And it is reproducable always with every try to start Miro ...

Hi Raphael,

are you saying the issue happens to you with Miro 2.5.4 or with Miro 3.0.3? If the former, please update (the update is available on F-12 too, see comment #17). If the latter, then do reopen.

How are you running Miro -- are you in a graphical desktop? which one (GNOME/KDE/XFCE/LXDE/...)? accessing locally or remotely? Could you provide the output of 

   ps auxwww | grep gconf

just after the crash?

(In reply to comment #21)
Miro-3.0.3-1.fc13.x86_64

Linux schlebby 2.6.34.6-54.fc13.x86_64 #1 SMP Sun Sep 5 17:16:27 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux

LXDE

raphael   1935  0.0  0.0 131532  1032 ?        S    Sep17   0:00 /usr/libexec/gconfd-2
raphael  26246  0.0  0.0 105272   808 pts/1    S+   14:23   0:00 grep gconf

(In reply to comment #22)
Errr, i mean XFCE, not LXDE ... Sorry.

OK. I'll install XFCE on my F-13 machine and try and reproduce this.

Interesting. When I try to open an .avi movie directly with Miro, it just works fine.

So, to summarize:
- "$ miro /path/to/movie.avi" works
- "$ miro" fails as you describe

I've not been able to replicate the problem using XFCE on an F-13 box -- Miro works just fine. Could you provide the following:

- content of /etc/fstab
- ls -l / | grep tmp
- and whether the problem still occurs if you do rm -rf /tmp/* , restart the machine, and retry
- whether it affects any other application, like Firefox

Many thanks!

(In reply to comment #26)
To be honest, it works again like a charme (maybe fixed mystically while I tried to open an avi directly).

drwxrwxrwt.  20 root root   4096 21. Sep 23:23 tmp

... yes, I use some cleaning script for /tmp and /var/tmp that deletes files older than last access was some days ago or something like that. So, maybe a corrupted tmp file was the cause, dunno.

Firefox? I try to use Midori mostly.

Created attachment 448816 [details]
fstab after several crashes of miro and working again