Bug 624310

1. Please attach y2logs (http://en.opensuse.org/openSUSE:Bugreport_YaST)

2. Report the problem with English texts, we are not all fluent in German.

Created attachment 378198 [details]
y2logs

1. y2logs attached
2. That are the names of the German menu entries. I am not sure about the correct names of the English version but I guess:

Export in "Software-Manager" File->Export... fails when pressing save with
"Error exporting package list to '(null)'"

yast2-gtk not handling correctly that there's a package lock? 
Or libzypp problem?

This was a stupid bug at the gtk plugin level. It's not an esoteric corner case at all, one simple test would have caught it.

Fixed over svn for trunk and the 11.3 branch. Will build a package for Factory soon.

Should we also try to see to it that a patch gets released?

Submitted to build service; id 44010.

Fixed then.

(In reply to comment #4)
> This was a stupid bug at the gtk plugin level. It's not an esoteric corner case
> at all, one simple test would have caught it.
> 
> Fixed over svn for trunk and the 11.3 branch. Will build a package for Factory
> soon.
> 
> Should we also try to see to it that a patch gets released?

I would like to get a patch for this released for online update for 11.3. 

Ricardo, is it okay to make patches using this version at svn
http://svn.opensuse.org/svn/yast/branches/SuSE-Linux-11_3-Branch/gtk/ ?

Atri,

Yes, I fixed the feature in the 11_3 branch too. In fact, my build service submission comes from that code base. But my submission is still in hold:

https://build.opensuse.org/request/show/44010

Anyway, make sure the patch is under the "suggested" category. I mean, judging by the duplicate count, this isn't a terribly popular functionality. Plus, there is no crash or loss of data, and the error message clearly indicates something is wrong with the software. (I think this does warrant a patch; just alerting to adjusting the priority appropriately, because some people may want to review and apply only the most urgent ones.)

Build service submission accepted (comment 8).

Anyhow, Michael makes the point it's good practice for non-security / low urgency fixes to be deferred and grouped together with future fixes, given that each patch involves an investment on the part of the support team.

Let's give it 2 weeks? 4 weeks? Atri, it's up to you.

(In reply to comment #9)
> Build service submission accepted (comment 8).
> 
> Anyhow, Michael makes the point it's good practice for non-security / low
> urgency fixes to be deferred and grouped together with future fixes, given that
> each patch involves an investment on the part of the support team.
> 
> Let's give it 2 weeks? 4 weeks? Atri, it's up to you.

Indeed that is what has kept me from already submitting updates. Let us wait and see if there are other little bugs here and there.

*** Bug 629912 has been marked as a duplicate of this bug. ***

So, we probably want to defer the patch so we also ship fixes for:
* bug 632377
* bug 633173

Possibly also:
* bug 633498

All the aforementioned have been fixed. Let's give it a week for testing...

(In reply to comment #14)
> All the aforementioned have been fixed. Let's give it a week for testing...

I have the packages ready.

Ricardo, please confirm that I am to submit the current YaST:Head yast2-gtk package (that is built from the svn/SUSE-Linux-11_3-branch and does not contain Factory changes right?)

@Maintenance
The proposed version update of yast2-gtk to version 2.21.70 fixes the following bugs including this one
bug 633498
bug 632377
bug 633173

Please consider the proposed update candidate.
Thanks

Yep, I submitted fixes for those bugs as version 2.21.70 to YaST:Head:
https://build.opensuse.org/package/show?package=yast2-gtk&project=YaST%3AHead

Maintenance guys: here is a categorical description of the fixes involved in that submission, to see if you guys feel that, taken together, they warrant issuing an update: (none of the fixes, in isolation, would be update worthy, but we might met the requirements for a collective update.)
* bug 624310 (this one): function loss (a couple of entries clinically dead). User audience is small, and same function is provided by other system tools.
* bug 633498: UI (cosmetic?): window too small for those who use very big fonts.
* bug 632377: UI: showing incorrect package count number, if user changed some setting.
* bug 633173: potential crash: not sure about any real world case, but according to the API of a library, we were not handling some value case.

Time for an update I think ... +1

Atri, recently, yast2-gtk wasn't compiling for Factory because of change to the gtk2 package. Anyhow, some folks fixed that and uploaded the trunk/ code to Yast:Head.

I guess we want to re-upload the 11_3 branch code, right? (because trunk has some modified strings) If so, let's suspend the patch process...

Wrt my previous comment, see bug 635439.

Uploaded again the 11.3 branch code. Request id: 46681. Version: 2.21.72

We'll have to wait for it to get approved...

Packages ready for submission, waiting for approval from maintenance. I guess we need one more vote right? :)

i think its ready. all works fine here after i installed this package

@maintenance
Packages ready, waiting for swampid

Ok, no one against from maintenance team, so starting update.

Be so kind and submit the fixed sources against openSUSE:11.3:Update:Test and submit a patchinfo.

The SWAMPID for this issue is 35699.
This issue was rated as low.
Please submit fixed packages until 2010-10-05.
Also create a patchinfo file using this link:
https://swamp.suse.de/webswamp/wf/35699

Sorry guys, but we probably want to interrupt the patch procedure, because there is a relatively nasty bug we will want to include.

The thing is that, when the user unselects "Dependencies > Autocheck", the qt plugin still applies a final solver run. But the gtk plugin doesn't. This is really problematic if an user relies on that behavior (few those may be), and doesn't apply a manual check.

See bug 637761.

@maintenance
I have submitted the updated version of yast2-gtk to Update/Testing that also fixes bug 637761. Please let me know if I am required to submit an updated patchinfo too.

Thanks

Update released for: yast2-gtk, yast2-gtk-debuginfo, yast2-gtk-debugsource
Products:
openSUSE 11.3 (debug, i586, x86_64)

released io guess.

Is
yast2-gtk-2.21.70-2.2.1.i586.rpm
the correct version which solves that problem?

Markus, yeah, that version is the latest update release, and it addresses all bugs mentioned in this bug report.

I am not sure what is the particular bug you're referring (several are discussed in this bug report), but here are the bugs addressed: (many of them are minor cosmetic fixes)

- sw_single: package count wrong on the filters box when
show-debug or show-devel when de-selected (bcn#632377)
- fixed potential crash when file picking file of esoteric
filename (bnc#633173)
- window size too small when using big fonts: correlate
window size to font size (bnc#633498)
- sw_single: fix file > import / export menu items (bcn#624310)
- sw_single: fixed duplicate separator item in context menu.
- build for bnc#620513 patch.
- adjust window size to cope with big fonts.
- more comsmetic fixes related to bnc#620513.
- comsmetic fixes related to bnc#620513.
- typo correction.
- fix sw_single post-procedure scrolling glitch.
- dependencies box sometimes freezes when open (bnc#620513).
- versions box not visible enough: swap position with
details box (bnc#620513).
- ommit online-update configuration menu item when
not running online-update (bnc#609778s)

If you are still experiencing problems, please let us know.