https://bugzilla.novell.com/show_bug.cgi?id=478602
Summary: setting the computer name
Classification: openSUSE
Product: openSUSE 11.2
Version: Factory
Platform: x86-64
OS/Version: SuSE Other
Status: NEW
Severity: Enhancement
Priority: P5 - None
Component: Installation
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: alinm.elena(a)gmail.com
QAContact: jsrain(a)novell.com
Found By: ---
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.6)
Gecko/2009012700 SUSE/3.0.6-0.1.2 Firefox/3.0.6
It may be very useful if the user can change the name of the computer even if
is in Automatic configuration during the installation.
Reason why? All other major OS let you do that. This should save a lot of bytes
on internet from people asking how to change the hostname after install.
Alin
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=480709
Summary: sound not working with Multimedia audio controller:
Yamaha Corporation YMF-744B
Classification: openSUSE
Product: openSUSE 11.1
Version: Final
Platform: i586
OS/Version: openSUSE 11.1
Status: NEW
Severity: Major
Priority: P5 - None
Component: Sound
AssignedTo: tiwai(a)novell.com
ReportedBy: emoenke(a)gwdg.de
QAContact: qa(a)suse.de
Found By: ---
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.10)
Gecko/20060911 SUSE/1.5.0.10-0.2 Firefox/1.5.0.10
Sound is silent.
Reproducible: Always
Steps to Reproduce:
1.try it.
2.try it.
3.try it.
Actual Results:
Nothing special - sound does not work.
I still have at least 2 other chipsets with non-working sound - i will bugzilla
them all, but I suspect you MUST already know something.
Expected Results:
Stitty new guidance - i am not an isiot.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=480751
Summary: software management: search mode is broken
Classification: openSUSE
Product: openSUSE 11.1
Version: Final
Platform: x86-64
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: bluedzins(a)wp.pl
QAContact: jsrain(a)novell.com
Found By: ---
software management: search mode is broken
Reproduce:
1. run SM
2. enter "flash-player"
3. search
4. remember the results
5. switch search mode from "contains" to "exact match"
6. search again
7. here I see "flash-player" and "pullin-flash-player"
So according to SM
"pullin-flash-player" == "flash-player"
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=480810
Summary: halt command doesn't always work
Classification: openSUSE
Product: openSUSE 11.1
Version: Final
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Bootloader
AssignedTo: jsrain(a)novell.com
ReportedBy: jakub.rusinek(a)gmail.com
QAContact: jsrain(a)novell.com
Found By: ---
User-Agent: Mozilla/5.0 (X11; U; Linux i686; pl; rv:1.9.0.6)
Gecko/2009011912 Firefox/3.0.6
My GRUB doesn't always turn my computer off when I call halt.
Reproducible: Always
Steps to Reproduce:
1. turn computer on, let grub load menu [depending on conf.]
2. exit gfxboot by hitting escape
3. hit c
4. call halt
Actual Results:
It doesn't always work (like a bad joke)
Expected Results:
Working halt command.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=478089
Summary: replace "Abort" string with "Cancel" string in
progress.ycp
Classification: openSUSE
Product: openSUSE 11.2
Version: Alpha 0
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: mschmidkunz(a)novell.com
QAContact: jsrain(a)novell.com
Found By: ---
According to the YaST style guide "Abort" should not be used in YaST modules
anymore.
The reasons for that are
* consistency with dektop labels (GNOME & KDE use both "Cancel" as label)
* conistency within YaST modules (some use "Cancel", some use "Abort" and
having one label will make the work easer for translators, look the whole YaST
more professional and icrease usability)
* consistency with YaST libraries like popup.ycp which uses "Cancel"
* "Abort" has a disrespecful connotation in English
Please replace the "Abort" string in progress.ycp with "Cancel"
Thanks a lot in advance!
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=480874
Summary: Spell check does not select correctly the underlined
word
Classification: openSUSE
Product: openSUSE 11.1
Version: Final
Platform: All
OS/Version: openSUSE 11.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE4 Applications
AssignedTo: kde-maintainers(a)suse.de
ReportedBy: branislav.klocok(a)orava.sk
QAContact: qa(a)suse.de
Found By: ---
User-Agent: Mozilla/5.0 (compatible; Konqueror/4.2; Linux) KHTML/4.2.0
(like Gecko) SUSE
When clicking on the underlined word by spell check (while typing) a wrong set
of characters (before the word) is being selected and when a option for
corrections is chosen its being placed on the place of wrongly selected
characters. (as shown in attachment)
When I run the spellcheck as a separate task it behaves correctly.
Same behavior happens in KDE 4.1.3 and 4.2.0
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=480770
Summary: Second stage hangs on "Detecting TV cards" in
VirtualBox
Classification: openSUSE
Product: openSUSE 11.2
Version: Alpha 0
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Live Medium
AssignedTo: coolo(a)novell.com
ReportedBy: captain.magnus(a)opensuse.org
QAContact: qa(a)suse.de
Found By: ---
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.5)
Gecko/2008121300 SUSE/3.0.5-1.3 Firefox/3.0.5
Using openSUSE-Factory-GNOME-LiveCD-x86_64-Build0001-Media.iso with VirtualBox.
Install hangs on second stage while probing for TV cards. Used ps aux and
killed the last started instance of yast made it proceed
Reproducible: Always
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=438263
Summary: b44: constantly "powering down PHY" during high network
load after resume
Product: openSUSE 11.0
Version: Final
Platform: 64bit
OS/Version: openSUSE 11.0
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Network
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: andreas.pfaller(a)gmail.com
QAContact: qa(a)suse.de
Found By: Community User
On my Dell Inspiron 1720 Laptop the b44 network driver constantly reports
"powering down PHY" during some high network load after a resume from
"Suspend to RAM", e.g.
..
Oct 22 11:49:29 i1720 kernel: b44: eth0: powering down PHY
Oct 22 11:49:30 i1720 kernel: b44: eth0: Link is down.
Oct 22 11:49:30 i1720 nm-dispatcher.action: Script
'/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.
Oct 22 11:49:30 i1720 syslog-ng[2637]: io.c: do_write: write() failed (errno
22), Invalid argument
Oct 22 11:49:30 i1720 syslog-ng[2637]: Connection broken to
AF_INET(192.168.1.6:514), reopening in 60 seconds
Oct 22 11:49:30 i1720 nm-dispatcher.action: Script
'/etc/NetworkManager/dispatcher.d/smbfs' exited with error status 6.
Oct 22 11:49:32 i1720 kernel: b44: eth0: Link is up at 100 Mbps, full duplex.
Oct 22 11:49:32 i1720 kernel: b44: eth0: Flow control is off for TX and off for
RX.
Oct 22 11:49:33 i1720 nm-dispatcher.action: Script
'/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.
Oct 22 11:49:34 i1720 SuSEfirewall2: SuSEfirewall2 not active
Oct 22 11:49:34 i1720 nm-dispatcher.action: Script
'/etc/NetworkManager/dispatcher.d/netcontrol_global_hooks' exited with error
status 1.
Oct 22 11:49:34 i1720 nm-dispatcher.action: Script
'/etc/NetworkManager/dispatcher.d/nfs' exited with error status 2.
Oct 22 11:49:34 i1720 nm-dispatcher.action: Script
'/etc/NetworkManager/dispatcher.d/smbfs' exited with error status 6.
Oct 22 11:49:38 i1720 kernel: b44: eth0: powering down PHY
Oct 22 11:49:39 i1720 kernel: b44: eth0: Link is down.
Oct 22 11:49:39 i1720 nm-dispatcher.action: Script
'/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.
Oct 22 11:49:40 i1720 nm-dispatcher.action: Script
'/etc/NetworkManager/dispatcher.d/smbfs' exited with error status 6.
Oct 22 11:49:42 i1720 kernel: b44: eth0: Link is up at 100 Mbps, full duplex.
Oct 22 11:49:42 i1720 kernel: b44: eth0: Flow control is off for TX and off for
RX.
Oct 22 11:49:43 i1720 nm-dispatcher.action: Script
'/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.
..
A rebooted system works without problem. Light network usage after "Suspend
to RAM" also does not trigger the problem. This problem is 100% reproducable
e.g. with "bonnie -s 2048" on an mounted nfs share (the problem only starts
at the start of bonnies "rewriting" test) or when the laptop takes part on
a bigger "icecream" compile.
If the load decreases (e.g. ^C of bonnie) the interface recovers after some
time and is usable with light network load (e.g. ssh).
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=405793
Summary: knetworkmanager doesn't handle vpnc well
Product: openSUSE 11.0
Version: Final
Platform: 64bit
OS/Version: openSUSE 11.0
Status: NEW
Severity: Major
Priority: P5 - None
Component: KDE3
AssignedTo: kde-maintainers(a)suse.de
ReportedBy: chris.brown(a)sybase.com
QAContact: qa(a)suse.de
Found By: Other
I'm using kde 3.5.9, openSUSE 11.0, 64-bit.
In comparison to openSUSE 10.3, knetworkmanager has some regressions when using
the vpnc plugin, as listed below.
1). No progress bar is given when trying to connect to the vpn server, and the
icon doesn't change in any way once connected (if it connects). Therefore, no
feedback is given to the user as to the status of the connection.
2). If the VPN server returns a message (for example, something to the effect
of a 'security notice' .. in 10.3 that would be shown on the screen in a dialog
box. This no longer happens in 11.0.
3). The vpn connection drops after a few seconds / minutes of use, with no
indication to the end user. Command-line 'vpnc' doesn't have this problem and
will stay connected for 8+ hours.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.