Bug 367239

Summary: yast lan Network Card Setup input field for Change Device Name needs resizing
Product: [openSUSE] openSUSE 11.0 Reporter: Casual J. Programmer <casualprogrammer>
Component: YaST2Assignee: Katarina Machalkova <kmachalkova>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None    
Version: Factory   
Target Milestone: ---   
Hardware: x86   
OS: openSUSE 11.0   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Screenshot of situation
Screenshot of current situation

Description Casual J. Programmer 2008-03-05 09:27:58 UTC 
Notebook: Fujitsu Siemens Amilo Si 1520
Graphics: Fujitsu Siemens Mobile 945GM/GMS/GME, 943/940GML Express
Monitor:  QUANTADISPLAY LCD Monitor 1280x800@60Hz
Wireless: Intel PRO/Wireless 3945ABG Network Connection
Sound:    82801G (ICH7 Family) High Definition Audio Controller
Desktop:  gnome2-SuSE-10.3-163
YaST GUI: yast2-qt-2.16.31-5
OS:       openSUSE 11.0 (i586) Alpha2 VERSION = 11.0
Kernel:   2.6.24.1-6-default

rpm -qa | grep yast | sort

autoyast2-installation-2.16.7-12
yast2-2.16.30-6
yast2-add-on-2.16.1-21
yast2-apparmor-2.16.0-10
yast2-backup-2.16.1-37
yast2-bootloader-2.16.5-22
yast2-ca-management-2.16.5-10
yast2-control-center-2.16.0-29
yast2-control-center-gnome-2.13.2-159
yast2-control-center-qt-2.16.0-29
yast2-core-2.16.38-4
yast2-country-2.16.11-8
yast2-country-data-2.16.11-8
yast2-fingerprint-reader-2.16.2-36
yast2-firewall-2.15.8-68
yast2-ftp-server-2.15.9-88
yast2-hardware-detection-2.16.1-15
yast2-inetd-2.15.1-105
yast2-installation-2.16.19-10
yast2-irda-2.15.1-155
yast2-iscsi-client-2.16.5-11
yast2-kerberos-client-2.16.4-7
yast2-ldap-2.16.0-6
yast2-ldap-client-2.16.9-10
yast2-ldap-server-2.15.5-137
yast2-libyui-2.16.38-4
yast2-mail-2.16.0-22
yast2-metapackage-handler-0.7.3-47
yast2-mouse-2.16.0-46
yast2-ncurses-2.16.18-3
yast2-ncurses-pkg-2.16.3-8
yast2-network-2.16.23-4
yast2-nfs-client-2.15.0-85
yast2-nfs-server-2.15.5-31
yast2-nis-client-2.16.0-56
yast2-ntp-client-2.16.4-12
yast2-online-update-2.16.7-7
yast2-online-update-frontend-2.16.7-7
yast2-packager-2.16.22-6
yast2-pam-2.16.0-57
yast2-perl-bindings-2.16.3-7
yast2-pkg-bindings-2.16.15-6
yast2-printer-2.16.8-5
yast2-profile-manager-2.16.0-47
yast2-qt-2.16.31-5
yast2-qt-pkg-2.16.27-6
yast2-registration-2.16.0-48
yast2-repair-2.16.4-24
yast2-restore-2.16.0-48
yast2-runlevel-2.16.0-48
yast2-samba-client-2.16.2-24
yast2-samba-server-2.16.0-60
yast2-scanner-2.15.5-103
yast2-schema-2.15.0-180
yast2-security-2.15.1-85
yast2-slp-2.15.0-92
yast2-sound-2.16.3-7
yast2-storage-2.16.11-17
yast2-storage-lib-2.16.11-17
yast2-sudo-2.16.0-22
yast2-support-2.15.3-75
yast2-sysconfig-2.15.3-118
yast2-tftp-server-2.14.0-165
yast2-theme-openSUSE-2.16.13-12
yast2-trans-en_US-2.16.1-4
yast2-transfer-2.16.1-30
yast2-trans-stats-2.15.0-63
yast2-tune-2.15.7-86
yast2-tv-2.16.3-29
yast2-update-2.16.4-26
yast2-users-2.16.14-4
yast2-x11-2.15.11-93
yast2-xml-2.16.0-33
yast2-ycp-ui-bindings-2.16.37-5
Comment 1 Casual J. Programmer 2008-03-05 09:28:44 UTC 
Created attachment 198702 [details]
Screenshot of situation
Comment 2 Katarina Machalkova 2008-03-13 09:59:52 UTC 
Hopefully fixed in yast2-network 2.16.25, but please test it yourself (as I'm still using old Qt3 UI on my workstation) and reopen if the problem persists
Comment 3 Casual J. Programmer 2008-03-23 17:44:15 UTC 
This is still not fixed, and I am very doubtful that you can fix it without viewing the result on your ( or a colleagues ) workstation after creating a change. Peculiar work ethics I should say.

Not sure either why QA let's you get away with this kind of "solution"
Comment 4 Casual J. Programmer 2008-03-23 17:45:48 UTC 
Created attachment 203518 [details]
Screenshot of current situation

yast2-network-2.16.26-8
Comment 5 Casual J. Programmer 2008-03-23 17:48:28 UTC 
You have to specify a comment on this change. Please explain your change.
Comment 6 Katarina Machalkova 2008-03-24 11:36:59 UTC 
> why QA let's you get away with this kind of "solution"

QAs have a lot of other work to do and so do I (y2-network is not the only package I have to maintain). There is not a single QA person assigned to testing factory in alpha stage. It is a job of community users.

What about sending in a patch instead of frustrated ranting? Writing YCP dialogs is really simple and straightforward and everyone can learn it quickly ;-)
Comment 7 Casual J. Programmer 2008-03-24 11:48:14 UTC 
Users have a lot of work to do also and it's pure courtesy I am taking the time to make you and your colleagues aware of broken pieces.

If I ever want to write my own stuff, I drop my state as _casual_ programmer and switch to Linux from Scratch.

Nonetheless I wish you happy easter holidays ;-)
Comment 8 Katarina Machalkova 2008-03-31 14:02:57 UTC 
Should be OK by now (y2-not_work 2.16.29)