http://bugzilla.novell.com/show_bug.cgi?id=571941http://bugzilla.novell.com/show_bug.cgi?id=571941#c0
Summary: YaST2 System/Date and Time uses Gnome button order in
KDE
Classification: openSUSE
Product: openSUSE 11.2
Version: Final
Platform: x86-64
OS/Version: openSUSE 11.2
Status: NEW
Severity: Minor
Priority: P5 - None
Component: YaST2
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: bbregister(a)gmail.com
QAContact: jsrain(a)novell.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64;
Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729;
NET CLR 1.1.4322; MS-RTC LM 8; MS-RTC EA 2)
Specifically, this applet uses Cancel/OK, and therefore looks out of place on a
KDE desktop. There may also be other places where this applet uses the wrong
button order, and it may be worth reviewing every dialog for both button order
and placement.
Please refer to the wiki about how to handle Gnome/KDE button order differences
using the ButtonBox widget:
http://en.opensuse.org/YaST/Development/Misc/Button_Order
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=571917http://bugzilla.novell.com/show_bug.cgi?id=571917#c0
Summary: YaST2 Software/Online Update uses Gnome button order
in KDE
Classification: openSUSE
Product: openSUSE 11.2
Version: Final
Platform: x86-64
OS/Version: openSUSE 11.2
Status: NEW
Severity: Minor
Priority: P5 - None
Component: YaST2
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: bbregister(a)gmail.com
QAContact: jsrain(a)novell.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64;
Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729;
NET CLR 1.1.4322; MS-RTC LM 8; MS-RTC EA 2)
Specifically, this applet uses Cancel/Accept, and therefore looks out of place
on a KDE desktop. There may also be other places where this applet uses the
wrong button order, and it may be worth reviewing every dialog for both button
order and placement.
Please refer to the wiki about how to handle Gnome/KDE button order differences
using the ButtonBox widget:
http://en.opensuse.org/YaST/Development/Misc/Button_Order
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=571924http://bugzilla.novell.com/show_bug.cgi?id=571924#c0
Summary: YaST2 Hardware/Infrared Device uses Gnome button order
in KDE
Classification: openSUSE
Product: openSUSE 11.2
Version: Final
Platform: Other
OS/Version: Other
Status: NEW
Severity: Minor
Priority: P5 - None
Component: YaST2
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: bbregister(a)gmail.com
QAContact: jsrain(a)novell.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64;
Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729;
NET CLR 1.1.4322; MS-RTC LM 8; MS-RTC EA 2)
Specifically, this applet uses Cancel/OK, and therefore looks out of place on a
KDE desktop. There may also be other places where this applet uses the wrong
button order, and it may be worth reviewing every dialog for both button order
and placement.
Please refer to the wiki about how to handle Gnome/KDE button order differences
using the ButtonBox widget:
http://en.opensuse.org/YaST/Development/Misc/Button_Order
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=571528http://bugzilla.novell.com/show_bug.cgi?id=571528#c2
T. Lingk <TLingk(a)vdsvossk.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|TLingk(a)vdsvossk.de |
--- Comment #2 from T. Lingk <TLingk(a)vdsvossk.de> 2010-02-01 08:45:47 UTC ---
I can confirm that the .depend.boot contains the statements you mentioned. The
only thing I noticed, is that the order is different:
boot.localfs: boot.clock boot.udev boot.rottfsck boot.dmraid boot.md
boot.loadmodules.
I can also confirm that the /etc/sysconfig/dmraid contains
DMRAID_DEVICE_TIMEOUT="60"
(Actually, dmraid itself never seemed to have problems assembling the raid, it
was the fsck that failed.)
By the way: Is it possible to update OpenSuse 11.2 to dmraid 1.0.0.rc16 since
it solves some problems that are still present in 1.0.0.rc15 (that is currently
present in OpenSuse 11.2)?
Best regards
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=569973http://bugzilla.novell.com/show_bug.cgi?id=569973#c0
Summary: bacula mtx-changer.conf in wrong place
Classification: openSUSE
Product: openSUSE 11.2
Version: Final
Platform: x86-64
OS/Version: openSUSE 11.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: jpschewe(a)mtu.net
QAContact: qa(a)suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7
In the factory bacula RPMS mtx-changer.conf is put in /etc/bacula, however
/usr/lib64/bacula/mtx-changer expects it in /usr/lib64/bacula/
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=529381
Summary: dmraid broken / possibly not loading on installation
medium
Classification: openSUSE
Product: openSUSE 11.2
Version: Factory
Platform: x86-64
OS/Version: SuSE Other
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Kernel
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: deanjo(a)sasktel.net
QAContact: qa(a)suse.de
Found By: ---
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.2)
Gecko/20090730 SUSE/3.5.2-1.1 Firefox/3.5.2
Once again dmraid appears to be broken in the installation medium. It will not
recognize the drive geometry on raid 0 setups. Yast logs attached. Can we
please get this fixed soon as it blocks further testing of 11.2.
Reproducible: Always
Steps to Reproduce:
1.Boot off installation DVD with dmraid partitions already setup
2.
3.
Actual Results:
Thinks the partition setup is invalid
Expected Results:
To work and recognize the existing geometry of dmraid 0 setups
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=571528http://bugzilla.novell.com/show_bug.cgi?id=571528#c1
Neil Brown <nfbrown(a)novell.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Info Provider| |TLingk(a)vdsvossk.de
--- Comment #1 from Neil Brown <nfbrown(a)novell.com> 2010-02-01 01:22:11 UTC ---
This is very surprising.
boot.dmraid contains:
# X-Start-Before: boot.localfs
which should cause it to run before boot.localfs
This causes
/etc/init.d/.depend.boot
To contain:
boot.localfs: boot.clock boot.dmraid boot.udev boot.rootfsck boot.md
boot.loadmo
which further shows they should be run in the correct order.
If you could check that the files on your system actually contain the lines
quoted above that would help.
Also, please check that
/etc/sysconfig/dmraid
still contains:
DMRAID_DEVICE_TIMEOUT="60"
Thanks.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.