Changing channel is slow

[Trouilliez vincent]

Zapping is very slow to change channel

Zapping is very slow to change channel. It takes about one second. It's not very consistent, too : sometimes it will take a bit more than a second, sometimes a bit less.

XawTV switches channel a lot faster, almost instantly, so hopefully Zapping can do it too, would be great.

[Lothar Braun (typecast)]

Does this problem persist on edgy?

[Trouilliez vincent (vincent-trouilliez-modulonet)]

The problem appears to be fixed in Dapper. I can't say for Edgy though, as I have removed it (was too buggy so I reverted to Dapper).
I tried in Feisty, but it keeps crashing so I can't test it.

[Lothar Braun (typecast)]

Hi,

did you have a chance to test it on feisty now?

Regards,
  Lothar

[Trouilliez vincent (vincent-trouilliez-modulonet)]

I just tested it on Feisty. Yes, it still crashes/quits as soon as I click on Edit->Preferences, or Edit->Channels
I started from the command line, and when the crash occurs, it prints a critical Warning, hope that helps:

(zapping:7305): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
Segmentation fault (core dumped)
vincent@Lotus-Esprit:~$

[Lothar Braun (typecast)]

Ah. This seems to be a duplicate of #39845.

[Trouilliez vincent (vincent-trouilliez-modulonet)]

No it isn't, please un-mark it, it's not a duplicate ! :-O

My bug is about slow channel switching, not crashes...

However the crash I am experiencing indeed looks like that other bug you found, so I subscribed to it. Thanks for the link.

[Lothar Braun (typecast)]

Hmm. You're right, i'll get it back to unconfirmed. So we need to find someone how can reproduce the problem or tell us if the problem is fixed persist on edgy.

[Martin Nemec (spocky)]

still the status is set to "new"

[Daniel T Chen (crimsun)]

Is this symptom reproducible in 8.10 alpha?

[Trouilliez vincent (vincent-trouilliez-modulonet)]

I don't know, I don't use Zapping anymore (gave up on it).

If nobody else cares about it, might as well close the bug ?

[Connor Imes (ckimes)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!