February 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 469784] New: Nautilus : disapearing scroll bar using tabs
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=469784 Summary: Nautilus : disapearing scroll bar using tabs Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: jc(a)phocean.net QAContact: qa(a)suse.de Found By: --- Created an attachment (id=267925) --> (https://bugzilla.novell.com/attachment.cgi?id=267925) nautilus scroll bar issue User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; fr; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-1.1 Firefox/3.0.5 When I open a new tab in Nautilus and then go back to the first tab, the scroll bar has disapeared. Refreshing the window makes the scroll bar reappearing. Please check the screenshots. Reproducible: Always Steps to Reproduce: 1. Open Nautilus on a folder that requires scrolling 2. Open a new tab (ctrl-t) 3. Go back to the first tab : the scroll bar has disappeared 4. Refreshing the window (F5) makes the scroll reappearing -- 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.

1 5

[Bug 463365] New: Vertcal scroll-bar disappears while switching tabs using Nautilus
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=463365 Summary: Vertcal scroll-bar disappears while switching tabs using Nautilus Product: openSUSE 11.1 Version: Final Platform: 32bit OS/Version: openSUSE 11.1 Status: NEW Severity: Minor Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: russo.giansergio(a)tiscali.it QAContact: qa(a)suse.de Found By: Community User Vertical scrollbar disappears when switching from one tab to another one in Nautilus (icon-view mode with more than one tab opened). To reinstate the bar a window refresh or resize is needed. -- 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.

1 3

[Bug 442475] New: The Cancel and Skip Refresh still does Not Operate with a Higher Priory than the Yast Application Itself
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=442475 Summary: The Cancel and Skip Refresh still does Not Operate with a Higher Priory than the Yast Application Itself Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alpha096(a)virginbroadband.com.au QAContact: jsrain(a)novell.com Found By: Customer If a Yast Application stalls at any point, using the Cancel Button has NO effect on the Yast Application. There needs to have both Cancel and Skip Refresh and Abort buttons operate with a much higher Priority that the Yast Application itself. Using the 'Skip Refresh' button certainly does work most of the time but not 100% of the time - Its Priority still needs to be higher. The cancel or Abort buttons - never close or stop a misbehaving Yast Application or abouts the saving of a Yast Application and is essentially useless. Both Abort, Cancel and Skip Refresh, all need to operate with the Highest CPU authority or always higher than the Yast Application itself. We have taken for granted that both cancel or Abort buttons never function after we commit to any changes via a Yast Application Window and perhaps it is long overdue for us to correct this -- 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.

1 16

[Bug 476298] New: Creating an NTP Server in Yast and Selecting Open Firewall Does Not Add NTP Services to Allowed Services List in the Firewall
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=476298 Summary: Creating an NTP Server in Yast and Selecting Open Firewall Does Not Add NTP Services to Allowed Services List in the Firewall Classification: openSUSE Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alpha096(a)virginbroadband.com.au QAContact: jsrain(a)novell.com Found By: --- Created an attachment (id=273130) --> (https://bugzilla.novell.com/attachment.cgi?id=273130) 1 of 2 images 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 Firefox/3.0.6 If we create a Public NTP Server via Yast ans we select Open Firewall in the Securities Options the NTP Service Permissions is not added to the list of Allowed Services Reproducible: Always Steps to Reproduce: 1.Yast 2.Network Services 3.NTP Server 4.Creat Public NTP Server and open Firewall option. Actual Results: NTP Services are not automatically added to allowed services so the NTP Server will never test or function at all Expected Results: When the Open Firewall Box is checked the NTP Server should be auto added to the Firewall's Allowed Services -- 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.

1 12

[Bug 479005] New: bluetooth-applet shouldn't specify pairing code
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=479005 Summary: bluetooth-applet shouldn't specify pairing code Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: riggwelter(a)opensuse.org QAContact: qa(a)suse.de Found By: --- When pairing with a device that requires a code, bluetooth-applet tells you the code to use rather than the old behaviour of asking the user to specify it. This is fine when pairing with a device such as a phone which asks the user for the code. The problem comes when pairing with a device with no input facility - such as speakers. These have their own hard-coded codes which makes it impossible to pair with them. -- 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.

1 8

[Bug 479622] New: Display becomes corrupt after whiching to battery, if booting up on battery X hangs.
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=479622 Summary: Display becomes corrupt after whiching to battery, if booting up on battery X hangs. Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: jefowler(a)hughes.net QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1.2 Firefox/3.0.6 I have the following hardware: Compaq 6910p with ATI X2300 video display. I am currently using the ATI Catalyst 9.2 driver, problem was manifest in 9.1 driver, problem can be seen in the opensource drivers radeon, OSS radeonhd, and vesa drivers. Did not have issue prior to upgrading to 11.1, worked okay with 11.0 and 10.2. Basically, if I am on ac power everything is working okay. Once I unplug the AC power, the screen starts to become corrupt, until it is an unusable grabage screen. If I try to boot up on AC power, once X server starts the system will hang, and lock up. Can not do anything but a hard power off to get back control of the system. Also during the lock the fans will kick on full speed. Which would give the impress of something hung in a loop and using up all the cpu. Tested the power up issue, had the system boot to runlevel 3, and then modified xorg.conf to use the radeon, radeonhd, and vesa drivers saw same issue, when startx was issued. Reproducible: Always Steps to Reproduce: 1.If on ac power unplug ac and screen will start to corrupt. 2.Power up without AC power, and X will hang as soon as it starts. 3.Tested the power up issue, with radeon, radeonhd, and vesa drivers Actual Results: Nothing special here simple unplug the ac power and screen corruption will begin immediately. Same for booting without AC power. Expected Results: This should function as it did before, with the 11.0, and 10.2 versions of opensuse. do not have a serial port on the laptop, and so far have not been able to login remotely either. System appears to be hung solid. Have performed a reinstall from scratch did not resolve issue. Unforunately, since it is present in the open source drivers switching to them did does not help. Also using the open source ones for some reason X becomes unstable, and can hang during normal use. -- 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.

1 10

[Bug 457046] New: documentation for apparmor included twice and confusingly packaged ...
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=457046 Summary: documentation for apparmor included twice and confusingly packaged ... Product: openSUSE 11.1 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: ke(a)novell.com ReportedBy: felix(a)derklecks.de QAContact: ke(a)novell.com Found By: --- I was just looking for apparmor documentation and found two packages: # zypper se -s apparmor-admin_en-pdf Daten des Repositorys laden... Installierte Pakete lesen... S | Name | Typ | Version | Arch | Repository --+--------------------------------+-------+-----------+--------+----------- i | apparmor-admin_en-pdf | Paket | 10.3-8.86 | noarch | oss i | opensuse-apparmor-admin_en-pdf | Paket | 11.1-28.2 | noarch | oss # rpm -ql apparmor-admin_en-pdf opensuse-apparmor-admin_en-pdf /usr/share/doc/manual /usr/share/doc/manual/apparmor-admin_en-pdf /usr/share/doc/manual/apparmor-admin_en-pdf/APPARMOR-admin_en.pdf /usr/share/doc/manual/opensuse-apparmor-admin_en-pdf /usr/share/doc/manual/opensuse-apparmor-admin_en-pdf/LICENSE.txt /usr/share/doc/manual/opensuse-apparmor-admin_en-pdf/opensuse-apparmor-admin_en.pdf The supposingly SLES documentation has the following pdf metadata: fm@macbook:~> pdfinfo /usr/share/doc/manual/apparmor-admin_en-pdf/APPARMOR-admin_en.pdf | head -n 3 Title: openSUSE Documentation Author: Unknown Creator: Unknown The openSUSE one has: fm@macbook:~> pdfinfo /usr/share/doc/manual/opensuse-apparmor-admin_en-pdf/opensuse-apparmor-admin_en.pdf | head -n 3 Title: Documentation Author: SUSE Creator: DocBook V1.74.0 So are really two packages needed? And at least the title of APPARMOR-admin_en.pdf is wrong ... -- 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.

1 12

[Bug 458891] New: Cannot set IPv6 default gateway
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=458891 Summary: Cannot set IPv6 default gateway Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mstopka(a)opensuse.org QAContact: qa(a)suse.de Found By: --- IPv6 support in YaST is not so good yet, because YaST make ma able to set an IPv6 addresses for interfaces, but not make me able to set default IPv6 gateway. Currently I can set addresses like this: 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 00:16:d4:61:ae:81 brd ff:ff:ff:ff:ff:ff inet 82.209.54.76/29 brd 82.209.54.79 scope global eth0 inet6 2001:15c0:668e::2/48 scope global valid_lft forever preferred_lft forever inet6 2002:52d1:364a::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::216:d4ff:fe61:ae81/64 scope link valid_lft forever preferred_lft forever but I have two choices I can set default IPv4 gateway like default via 82.209.54.73 dev eth0 or IPv6 gateway, not both so dual stack IPv4 and IPv6 is not possible, at least not easily possible only using YaST. I can set as default gateway 2001:15c0:668e::1 but then I have IPv6 up and running, but not IPv4 for global communication, only for 82.209.54.72/29. I think YaST should detect if there is any IPv6 address on any interface (?except loopback) and if so, YaST should show one more field for default gateway marked like "Default IPv6 gateway". I think something like this would be fine also for IPv4 networking... I mean if there is no IPv4 address on any interface (?except loopback) YaST should not show me an field marked as "Default gateway"... Or to be more precise I think "Default gateway" field should be renamed as "IPv4 default gateway" and this one filed should not be seeing if there is no IPv4 address on any interface. -- 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.

1 4

[Bug 451011] New: "Create virtual machines" does not open and has no user visible error message
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=451011 Summary: "Create virtual machines" does not open and has no user visible error message Product: openSUSE 11.1 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hfiguiere(a)novell.com QAContact: jsrain(a)novell.com Found By: --- xend is not runing because I don't run a Xen kernel. If I click on "Create Virtual Machines" (because I just installed the tools), it does NOTHING. I get in the console (started yast from the command line): libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock': No such file or directory libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock-ro': No such file or directory Error: unable to connect to '/var/run/libvirt/libvirt-sock': No such file or directory Expected: A user visible message explaining it can connect to the hypervisor or something. -- 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.

1 7

[Bug 457083] New: Virtual machine for WinXP doesn' t support National Language Keyboard layout
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=457083 Summary: Virtual machine for WinXP doesn't support National Language Keyboard layout Product: openSUSE 11.1 Version: RC 1 Platform: x86-64 OS/Version: Windows XP Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: cgriffin(a)novell.com ReportedBy: terje(a)nordland-teknikk.no QAContact: qa(a)suse.de Found By: --- With YaST2 I created a virtual machine for WindowsXP and succeeded to install Windows XP (Norwegian version) from CD-ROM installation source. A couple of issues during the early XP installation phases, as shown on the attached screenshots, were 1. Typing the <F8> key to accept the XP license agreement didn't work. Had to send F8 from the context menu instead 2. After copying the XP files, an error message told that the VM Console couldn't be opened, and the XP installation was quitted (disappeared). I had to manually start VM Manager from YaST to be able to continue the WinXP setup part of the installation Norwegian Language layout for the keyboard was selected during this setup. 3. The major issue that was discovered during the late XP setup, writing in the fields for user name and hostname, was the that the Norwegian keyboard language didn't work. When typing the special Norwegian keys for the characters 'æøå' or 'ÆØÅ', nothing was written, while typing '-' became '+' instead. After the installation, starting XP and WordPad, the same happened. (I think a related issue previous on Suse/SLE-10 prohibited to enter the right registering codes for Windows XP, as not all keys worked) -- 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.

1 11