After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 547515 - Strange source rendering problems
Strange source rendering problems
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: general
1.2.1
Other Linux
: Normal normal
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-12 23:48 UTC by Michael Monreal
Modified: 2008-08-19 13:39 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Screesnhot 1 (60.00 KB, image/png)
2008-08-12 23:48 UTC, Michael Monreal 		Details
Screenshot 2 (101.98 KB, image/png)
2008-08-12 23:49 UTC, Michael Monreal 		Details
Screenshot 3 (161.56 KB, image/png)
2008-08-13 08:37 UTC, Michael Monreal 		Details
Screenshot 4 (35.33 KB, image/png)
2008-08-13 08:40 UTC, Michael Monreal 		Details

Description Michael Monreal 2008-08-12 23:48:11 UTC 
Banshee 1.2.1 has some problems rendering sources. I first suspected a gtk# version problem but I just rebuild my whole mono stack with the versions from the opensuse mono repository... still no luck.

One problem is that empty sources (library or playlists) look like screenshot 1

Another - maybe related - problem is the display of podcasts as seen in screenshot 2
Comment 1 Michael Monreal 2008-08-12 23:48:35 UTC 
Created attachment 116462 [details]
Screesnhot 1
Comment 2 Michael Monreal 2008-08-12 23:49:11 UTC 
Created attachment 116463 [details]
Screenshot 2
Comment 3 Michael Monreal 2008-08-13 08:37:01 UTC 
Created attachment 116482 [details]
Screenshot 3

Another occurrence of this in smart playlist sources
Comment 4 Michael Monreal 2008-08-13 08:40:19 UTC 
Created attachment 116483 [details]
Screenshot 4

...and radio source. I'm about 98% sure this is some incompatibility with a dependency lib like GTK. Trying to downgrade a few libs now to find the problem.
Comment 5 Michael Monreal 2008-08-13 10:08:46 UTC 
I just reverted GLIB to 2.16.5 and GTK to 2.12.11. With this combination, everything works fine. So I guess this is either a regression in GLIB/GTK or incompatibility of GTK# with newer GTK+. Still worth keeping an eye on imho
Comment 6 Michael Monreal 2008-08-13 10:35:05 UTC 
GLIB trunk together with GTK 2.12.11 still work. Removing GTK 2.12.11 and installing GTK 2.13.6 breaks.
Comment 7 Michael Monreal 2008-08-13 11:19:30 UTC 
I tested various GTK versions now. 2.13.5 still works fine, 2.13.6 breaks.

No idea if this is a GTK+ bug or GTK# and/or Banshee just need to be adapted... please reassign if needed.
Comment 8 Michael Monreal 2008-08-14 10:52:26 UTC 
Got this fixed in GTK trunk! :)
Comment 9 Gilles Dartiguelongue 2008-08-18 14:17:02 UTC 
could you please point out which commit fixed your issue ?
Comment 10 Patryk Zawadzki 2008-08-19 13:39:36 UTC 
I can confirm that this works fine with GTK+ 2.13.7