When I try to adjust the Download/Upload speed in the Edit, Peference, Speed tab. When I click the Speed tab, it will close out Transmission-gtk completely. Any of the other tabs does not cause it to crash. To reproduce the bug, do the following in Mga2 (testing) with KDE4. 1. Open transmission with some active torrents. 2. Go to Edit --> Preference. 3. Click on the "Speed" tab in the transmission window. Transmission crashes immediately. None of the other tabs crash. No other issues that I can see other then this one. Transmission-gtk v2.51. # rpm -qif /usr/bin/transmission-gtk Name : transmission-gtk Version : 2.51 Release : 1.mga2 Architecture: i586 Install Date: Mon 16 Apr 2012 07:54:39 AM CDT Group : Networking/File transfer Size : 3012170 License : MIT and GPLv2 Signature : RSA/SHA1, Fri 13 Apr 2012 09:22:22 AM CDT, Key ID b742fa8b80420f66 Source RPM : transmission-2.51-1.mga2.src.rpm Build Date : Fri 13 Apr 2012 09:21:22 AM CDT Build Host : ecosse.mageia.org Relocations : (not relocatable) Packager : boklm <boklm> Vendor : Mageia.Org URL : http://www.transmissionbt.com/ Summary : GTK Interface for Transmission BitTorrent client
Target Milestone: --- => Mageia 2
what is your gtk theme ? oxygen ? does it crash to if you use another one ?
Source RPM: (none) => transmission
I'm not a big user of KDE4 but I was using the default theme, assuming Oxygen. Now I'm currently using Gnome3 Fallback mode and accessing the 'Speed' tab does not crash transmission. I'll have to try KDE again with a different theme as soon as I figure out how to change themes. Thnx.
I confirm the crash. Happens only with oxygen-gtk3 as a widget theme. Not with Adwaita. Investigating.
CC: (none) => hugo
Created attachment 2042 [details] Speed settings in transmission-gtk crash is due to some custom comboboxes in the incriminated settings page (the speed), which crash as soon as one calls "gtk_combo_box_check_appearance" (which in turn is called from inside oxygen-gtk via gtk_combo_box_set_wrap_width()) So far I have found no proper way of working this around in oxygen-gtk3, for this widget and this widget only. I suggest this crash (and this explanation) is forwarded upstream, while I keep investigated. The incriminated "custom" comboboxes are visible on the screenshot. They are the "schedule times" comboboxes. also note that they are not rendered properly either (missing the left edge), which I'm not sure how to fix in oxygen-gtk either.
Created attachment 2043 [details] patch to oxygen-gtk This patch fixes it. I'm still checking for regressions before pushing to oxygen-gtk3 code.
after double-checking, I pushed the changes to both oxygen-gtk git repositories. Will become available with oxygen-gtk3-1.0.4 (due in about 1 month)
As announced above, crash is fixed in latest oxygen-gtk3 version, available at: http://download.kde.org/download.php?url=stable/oxygen-gtk3/1.0.4/src/oxygen- gtk3-1.0.4.tar.bz2 Can someone push ?
Assignee: bugsquad => juan.baptisteSource RPM: transmission => oxygen-gtk3
*** Bug 6001 has been marked as a duplicate of this bug. ***
CC: (none) => kristoffer.grundstrom1983
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
still no update in mga2
Keywords: NEEDINFO => (none)CC: (none) => dmorganec, fundawang, olavVersion: Cauldron => 2
dmorgan promised he would make an update. I guess I'll ping him again on IRC. A new oxygen-gtk version will be released in the comming days (but no serious crashes fixed this time, cause I have not been aware of any)
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
Well I'm the correct owner for this bug as I'm currently the maintainer for oxygen-gtk* packages, but as I haven't done anything for this and other oxygen-gtk related bugs due to lack of knowledge and experience with topics, I think that I should drop maintainership of those two packages and someone more competent with them, like tv or hugo (if he's a packager too, dunno if hi is) should grab them and be the owner of this bugs.
Hi Juan Luis, I can take care of fixing bugs upstream (in oxygen-gtk source code), which is better than distribution patches, and therefore am more than happy to be cc'ed to any oxygen-gtk related bug (this helps improve my code). However, I would rather not become a packager (no time available for that, sorry), and therefore not become official assignee of these. If I remember right, dmorgan (dmorganec@gmail.com) might also be able to help on this (the packaging part). Better ping him directly For this particular bug (gtk-transmission), it has been fixed upstream (since release gtk3-1.0.4), and all that's needed is to package this release (or latest one, which is 3-1.0.5). Also, next 'major' release (gtk3-1.1.0) will show up in about one week so maybe it is worth waiting for it. Cheers, Hugo
As this bug is filed against mga2 we probably can't upgrade to a new version. Hugo, is it possible that you direct us to the commit that fixes this problem? Is it possible to patch it on our version of the package?
CC: (none) => sander.lepik
@Sander: bug has been fixed "twice" in fact. First I removed the 'crashing' functionality; second, I re-added it, and made it stable. So two commits: - https://projects.kde.org/projects/playground/artwork/oxygen-gtk/repository/revisions/da10c6bf5d4fe8b39f3337f990e7424222117392 - https://projects.kde.org/projects/playground/artwork/oxygen-gtk/repository/revisions/733af5998fba65f97235ddb5f7602fd004818ffd I think a patch combining the two diffs 'should' work on the oxygen-gtk3-1.0.3 (which is the release shipped with mageia 2). I can help generating such a patch, if needed. Cheers, Hugo
>As this bug is filed against mga2 we probably can't upgrade to a new version. Why ? before the complete frezee it was said (iirc) it's too late to update it but it was ok for after the release
Keywords: (none) => Junior_job
@Manuel yes, I remember that quote too :) (but I'm not the one to decide what should be updated and what should not) What I know for sure though is that Cauldron must get oxygen-gtk3-1.1.0 as soon as it is out, because there are plenty of rendering issues with current release and gtk+-3.3.x (due to changes in gtk+-3), that have been fixed since then Hugo
Created attachment 2535 [details] patch to oxygen-gtk3-1.0.3 This patch should be applied to oxygen-gtk3-1.0.3 It fixes the issue as far as I can tell. It is only necessary if you want to patch the oxygen-gtk3 version shipped with mageia2, rather than update to a more recent release. It is not needed for Cauldron because: 1/ the crash is not reproducible with more recent versions of gtk+-3.0 (namely 3.5.x) 2/ one should update oxygen-gtk3 to v1.1.0 whenever it is released, since it fixes many glitches with the aforementioned version of gtk+-3.0 Hugo
I confirm the same problem. Here also stops transmission-gtk in Mageia 2 x86_64. Tested the transmission-gtk-2.60-1.mga3.x86_64.rpm package and is having the same problem.
CC: (none) => frateraecHardware: i586 => All
i just pushed a new oxygen-gtk3 with this patch
Okay! But I did not find in the repositories core update for Mageia 2. :-(
this is in updates_testing
(In reply to comment #23) > this is in updates_testing thanks Suggested Advisory: ------------- Updated oxygen-gtk3 fix a crash of transmission-gtk when clicking on the speed tab. https://bugs.mageia.org/show_bug.cgi?id=5430 ------------- SRPM: oxygen-gtk3-1.0.3-1.1.mga2.src.rpm
Assignee: juan.baptiste => qa-bugsSummary: Transmission-gtk crashes when clicking the Speed Tab => Transmission-gtk crashes when clicking the Speed Tab [mga2]Source RPM: oxygen-gtk3 => oxygen-gtk3-1.0.3-1.1.mga2.src.rpm
I installed oxygen-gtk3-1.0.3-1.1.mga2 and I rebooted my computer. However, transmission is still crashing when I go to Edition > Preferences > Speed tab I got the following line during the crash >(transmission-gtk:6008): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion `GTK_IS_WIDGET (widget)' failed >Erreur de segmentation Is there any things to do before testing?
CC: (none) => olivier.delaune
Sorry, I forgot to mention I tested on Mageia 2 64-bits.
Oups, I have forgotten to install lib64oxygen-gtk3-1.0.3-1.1.mga2.x86_64.rpm. Now the crashes has disappear. This update fixes the problem here on Mageia 2 64-bits. Thanks.
CC: (none) => stormiWhiteboard: (none) => MGA2-64-OK
Tested ok on Mageia 2 i586. Installed transmission-gtk3, confirmed the crash. Installed oxygen-gtk3 and liboxygen-gtk3 from testing. No more crash Edition > Preferences > Speed tab Thanks.
CC: (none) => maloWhiteboard: MGA2-64-OK => MGA2-64-OK MGA2-32-OK
Validating. Advisory in comment #24 Could sysadmin please push from core/updates_testing to core/updates. Thank you!
Keywords: Junior_job => validated_updateCC: (none) => sysadmin-bugs
Update pushed: https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0136
Status: NEW => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED