July 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 402045] New: krdc SIGSEGV
by bugzilla_noreply＠novell.com 03 Jul '08

03 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=402045 User pnemec(a)novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=402045#c5 Summary: krdc SIGSEGV Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE3 AssignedTo: kde-maintainers(a)suse.de ReportedBy: pnemec(a)novell.com QAContact: qa(a)suse.de Found By: --- krdc called with vnc://sleposlab.suse.cz SIGSEGV randomly (sometime after 2 minutes, sometime after 15, sometimes after 30 seconds). BT: [?1034h[Thread debugging using libthread_db enabled] [New Thread 0x7f43b9439700 (LWP 24567)] [New Thread 0x41014950 (LWP 24586)] [New Thread 0x40813950 (LWP 24585)] [KCrash handler] #5 0x00007f43b60dc5c5 in raise () from /lib64/libc.so.6 #6 0x00007f43b60ddbb3 in abort () from /lib64/libc.so.6 #7 0x00007f43b60d51e9 in __assert_fail () from /lib64/libc.so.6 #8 0x00007f43b675de27 in ?? () from /usr/lib64/libX11.so.6 #9 0x00007f43b6c72112 in XShmPutImage () from /usr/lib64/libXext.so.6 #10 0x000000000043868b in DrawScreenRegionX11Thread (win=24567, x=-1408987520, y=-1237325360, width=<value optimized out>, height=<value optimized out>) at /usr/src/debug/kdenetwork-3.5.9/krdc/vnc/desktop.c:164 #11 0x0000000000430733 in KVncView::customEvent (this=0x7decc0, e=0x7f43ac02c670) at ./krdc/vnc/kvncview.cpp:373 #12 0x00007f43b7408ed1 in QObject::event () from /usr/lib/qt3/lib64/libqt-mt.so.3 #13 0x00007f43b743df53 in QWidget::event () from /usr/lib/qt3/lib64/libqt-mt.so.3 #14 0x00007f43b73aa435 in QApplication::internalNotify () from /usr/lib/qt3/lib64/libqt-mt.so.3 #15 0x00007f43b73ab21a in QApplication::notify () from /usr/lib/qt3/lib64/libqt-mt.so.3 #16 0x00007f43b7f43972 in KApplication::notify () from /opt/kde3/lib64/libkdecore.so.4 #17 0x00007f43b73ac279 in QApplication::sendPostedEvents () from /usr/lib/qt3/lib64/libqt-mt.so.3 #18 0x00007f43b735a775 in QEventLoop::processEvents () from /usr/lib/qt3/lib64/libqt-mt.so.3 #19 0x00007f43b73c0f69 in QEventLoop::enterLoop () from /usr/lib/qt3/lib64/libqt-mt.so.3 #20 0x00007f43b73c0df2 in QEventLoop::exec () from /usr/lib/qt3/lib64/libqt-mt.so.3 #21 0x000000000042c44b in main (argc=<value optimized out>, argv=<value optimized out>) at ./krdc/main.cpp:156 -- 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 404379] New: keyboard. CTRL+C CTRL+V CTRL+X no longer works
by bugzilla_noreply＠novell.com 03 Jul '08

03 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=404379 Summary: keyboard. CTRL+C CTRL+V CTRL+X no longer works Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mmorisot.abonnement(a)belcenter.com QAContact: jsrain(a)novell.com Found By: Customer Hello, The following key combinations do not work under the opensuse 11.0. In applications like kde or console. Thank You. Section "InputDevice" Driver "kbd" Identifier "Keyboard[0]" Option "Protocol" "Standard" Option "XkbLayout" "be" Option "XkbModel" "PC104" Option "XkbRules" "xfree86" EndSection ## Path: Hardware/Keyboard ## Description: Keyboard settings ## Type: string ## Default: "" ## ServiceRestart: kbd # # Keyboard settings for the text console # # Keyboard mapping # (/usr/share/kbd/keymaps/) # e.g. KEYTABLE="de-latin1-nodeadkeys", "us" or empty for US settings # KEYTABLE="be-latin1.map.gz" ## Type: integer ## Default: # # Keyboard delay time in ms (250, 500, 750, 1000) KBD_DELAY="" ## Type: string(2.0,2.1,2.3,2.5,2.7,3.0,3.3,3.7,4.0,4.3,4.6,5.0,5.5,6.0,6.7,7.5,8.0,8.6,9.2, 0.0,10.9,12.0,13.3,15.0,16.0,17.1,18.5,20.0,21.8,24.0,26.7,30.0) ## Default: # # Keyboard repeat rate (2.0 - 30.0) KBD_RATE="" ## Type: list(bios,yes,no) ## Default: bios # # NumLock on? ("yes" or "no" or empty or "bios" for BIOS setting) KBD_NUMLOCK="bios" ## Type: yesno ## Default: no # # ScrollLock on? ("yes" or "no") KBD_SCRLOCK="no" ## Type: yesno ## Default: no # # CapsLock on? ("yes" or "no") KBD_CAPSLOCK="no" ## Type: yesno ## Default: no # # Disable CAPS LOCK and make it a normal Shift key? # (Ctrl Caps Lock will still toggle Caps Lock functionality) # Note that you need to tweak the xkb maps or use xmodmap # if you want to do the same under X-Windows. In ~/.Xmodmap: # keycode 0x42 = Shift_L Shift_L # KBD_DISABLE_CAPS_LOCK="no" ## Type: string ## Default: "tty1 tty2 tty3 tty4 tty5 tty6" # # ttys for the above settings # Example: "tty1 tty2" # "" for all tty's # KBD_TTY="tty1 tty2 tty3 tty4 tty5 tty6" # # Compose tables to be loaded. # Compose tables are good for producing characters, which can not # be directly input from your keyboard, such as characters with # accents, currency signs, ... # Please read /usr/share/doc/packages/kbd/README.SuSE for an # explanation. # You may leave this variable empty (default compose table from kernel # or KEYTABLE will be used then -- most keyboard maps don't have a # compose table, though) # More than one compose table can be given. For a selection of possible # tables see /usr/share/kbd/keymaps/include/compose.* # You can give more than one compose table, but only the last one will # determine the compose combinations. # The word "clear" has a special meaning: # Your compose table will be cleared, before more compose symbols are # added. # The files compose.winkeys and shiftctrl may be used to map the # <compose> key to the W*n menu key and Shift-Ctrl, respectively, # on a PC keyboard. # A typical setting for Latin1 users (with a PC keyboard) may be # COMPOSETABLE="clear winkeys shiftctrl latin1.add" # For latin2, this would be # COMPOSETABLE="clear winkeys shiftctrl latin2" # A typical setting for sb. with a character set, where a matching # compose table is missing (but with a PC keyboard), would be # COMPOSETABLE="winkeys shiftctrl" # COMPOSETABLE="clear latin1.add" # The YaST-internal identifier of the attached keyboard. # YAST_KEYBOARD="belgian,pc104" -- 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 19

[Bug 302324] New: Install software and control center icons are missing from main-menu
by bugzilla_noreply＠novell.com 03 Jul '08

03 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=302324 Summary: Install software and control center icons are missing from main-menu Product: openSUSE 10.3 Version: Beta 2 Platform: i586 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: jimmyk(a)novell.com ReportedBy: timlee(a)novell.com QAContact: qa(a)suse.de Found By: Integration Test * clean default install of build 20070821 from gnome CD iso * clicked on main-menu icon in panel * in system section of slab there were there were the following entries: Help Lock Screen Logout Shutdown Control panel and install software appear to be missing. gnome-main-menu version 0.9.8-64 last changelog entry Aug 18, "Logout item to use libssui.." -- 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 30

[Bug 230694] New: umount.cifs and /etc/mtab
by bugzilla_noreply＠novell.com 03 Jul '08

03 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=230694 Summary: umount.cifs and /etc/mtab Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: golter(a)dubna.ru QAContact: qa(a)suse.de umount.cifs unmount mounted share, but does not remove appropriate record from /etc/mtab. So, I have to use umount -t cifs instead of umount.cifs to unmount share and remove mount point record from /etc/mtab. In both cases /proc/mount is represent the facts. -- 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, or are watching someone who is.

1 12

[Bug 405525] New: Soundcard "Realtek HD" completely disappeared between 10. 3 and 11.0
by bugzilla_noreply＠novell.com 03 Jul '08

03 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=405525 Summary: Soundcard "Realtek HD" completely disappeared between 10.3 and 11.0 Product: openSUSE 11.0 Version: Final Platform: i586 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: Sound AssignedTo: tiwai(a)novell.com ReportedBy: gh55(a)heinzel.name QAContact: qa(a)suse.de Found By: --- My soundcard, which Windows claims to be a Realtek HD, and which worked fine under 10.3, has totally disappeared after updating to 11.0. I installed alsa-firmware, but that didn't change anything. "yast2 sound" does not see it. -- 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 309746] New: gtkmozembed does not work
by bugzilla_noreply＠novell.com 03 Jul '08

03 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=309746 Summary: gtkmozembed does not work Product: openSUSE 10.3 Version: Beta 3 Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: itamarh(a)qumranet.com QAContact: qa(a)suse.de Found By: Development gtkmozembed, part of gnome-python-extras does not work. checked on both 32bit and 64bit editions of beta3. sample program attached (program verified as working on another distro) the window opens, but the page is not loaded. using the "regular workaround" of export LD_LIBRARY_PATH=/usr/lib/firefox (or lib64) causes the program to exit without any message(?!) after the "moz = gtkmozembed.MozEmbed()" line. import gtk import gtkmozembed window = gtk.Window() moz = gtkmozembed.MozEmbed() window.add(moz) moz.load_url("http://www.google.com") window.show_al() gtk.main() -- 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 379647] New:=?UTF-8?Q?=20blank=20screensaver=20do?= esn’t work ( doesn’t blank screen, only locks)
by bugzilla_noreply＠novell.com 03 Jul '08

03 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=379647 Summary: blank screensaver doesn’t work (doesn’t blank screen, only locks) Product: openSUSE 11.0 Version: Factory Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: mfabian(a)novell.com QAContact: qa(a)suse.de Found By: Development blank screensaver doesn’t work (doesn’t blank screen, only locks). -- 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 9

[Bug 402526] New: b43-phy0 ERROR: PHY transmission error
by bugzilla_noreply＠novell.com 03 Jul '08

03 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=402526 Summary: b43-phy0 ERROR: PHY transmission error Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: crrodriguez(a)novell.com QAContact: qa(a)suse.de Found By: Development Using this card: /usr/sbin/hwinfo --wlan 01: PCI 300.0: 0282 WLAN controller [Created at pci.310] UDI: /org/freedesktop/Hal/devices/pci_14e4_4311 Unique ID: y9sn.wZtoJ4c7zyA Parent ID: 3hqH.gMd7Qwtg110 SysFS ID: /devices/pci0000:00/0000:00:03.0/0000:03:00.0 SysFS BusID: 0000:03:00.0 Hardware Class: network Model: "Broadcom BCM94311MCG wlan mini-PCI" Vendor: pci 0x14e4 "Broadcom" Device: pci 0x4311 "BCM94311MCG wlan mini-PCI" SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x1375 Revision: 0x02 Driver: "b43-pci-bridge" Driver Modules: "ssb" Device File: wlan0 Features: WLAN Memory Range: 0xb8000000-0xb8003fff (rw,non-prefetchable) IRQ: 18 (no events) HW Address: 00:1a:73:88:05:9c Link detected: yes WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v000014E4d00004311sv0000103Csd00001375bc02sc80i00" Driver Info #0: Driver Status: ssb is active Driver Activation Cmd: "modprobe ssb" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #18 (PCI bridge) With WPA2 frecuently causes b43-phy0 ERROR: PHY transmission error to be written to the logs, sometimes huge lot of log entries, after that, the network conectivity starts to drop performance dramatically, the system becomes extremely unstable, and then freeze/crashs completely after a certain period of time. -- 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 223773] grub fails boot after update
by bugzilla_noreply＠novell.com 02 Jul '08

02 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=223773 User suse(a)tlinx.org added comment https://bugzilla.novell.com/show_bug.cgi?id=223773#c45 L. A. Walsh <suse(a)tlinx.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suse(a)tlinx.org --- Comment #45 from L. A. Walsh <suse(a)tlinx.org> 2008-07-02 17:27:56 MDT --- "You are not authorized to access bug #144773." -- I'm still being blocked when going to look at this. - > I agree with comment #37: XFS really does suck, especially when it comes to > booting Linux on a PC. Fortunately we do not support it any more for new > installations, an ext2 /boot partition is highly recommended. --- I've been using XFS on root, with certainty, since 9.0 (I remmber getting being bitten by a SuSE9.2 bug where the xfs driver on the installation disk was fault and couldn't read old partitions. I am 'fairly' sure that I've been using it since 7.3. I've never had any problems except when a disk-cable was going bad. Hardly XFS's fault. But I also use lilo. Grub doesn't have accessible documentation. lilo seems more reliable than grub for most purposes -- and grub, while it looks cool -- seems awfully complex for what it does. lilo has been good for dual and triple boot systems (Linux, Win98+Win2k), and dual mode booting on that Win98 partition (native & under VMWare). I've even used the BIOS re-ordering in lilo to allow booting from sda -- as well as the dynamically adjusting hidden/non-hidden partitions that I needed at one point for Win98 (this isn't recent, I'll mind you...). With a simple adjustment in lilo.conf, I could boot off a cloned removable hard disk -- and change the its boot params while it was still a 2ndary hard disk. Then on bootup, hit the BIOS, one-time boot switch (F12?) and boot from the removable instead of the fixed -- and the system would come up off the 2ndary, while calling it "hda" (the old fixed drive became hdb). It was trivial to figure out and it just worked! The same was not true for grub. It always "knew" better than to write to the 2ndary drive without referring to it by BIOS id 0x8[1-3], trying to configure the 2ndary drive to be "0x80" would have grub do its installation on the 1st disk -- not what I wanted. After multiple attempts, I went back and reinstalled lilo -- no problems. I think Grub was taking a higher-level view of the hard disks -- and wouldn't be so easily 'fooled' by a simple text-label change in its config files. I can see that being a benefit if the order changes and you *don't* want the boot order to change -- but in the opposite case, where I wanted the old behavior -- it did everything to protect me from what I needed to do. Maybe grub is expecting more file-driver functionality to be present when the OS isn't fully "awake"? I find it annoying to go from a working lilo+xfs, and now am told that because grub can't deal w/xfs, xfs isn't supported for booting from anymore. Why not continue to support lilo+xfs? It's just that grub -- is a much more complex beast and demands more from the drivers (and users) -- which is fine if one doesn't need to understand or tweak what's going on, whereas lilo being fairly primitive seems to have fewer failure points. Also, I get the _feeling_ (perhaps wrong), but that lilo is still used alot in the kernel development group. That might mean it gets tested more and might be good, at the very least, as a fall-back when grub gets too demanding... -- 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 0

[Bug 382400] New: NetworkManager no longer work when the laptop lid is closed and reopened
by bugzilla_noreply＠novell.com 02 Jul '08

02 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=382400 Summary: NetworkManager no longer work when the laptop lid is closed and reopened Product: openSUSE 10.3 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: jharmon(a)novell.com QAContact: qa(a)suse.de Found By: --- I am running openSUSE 10.3 on a Dell D820 laptop. I often move from meeting to meeting and have to close the laptop lid in order to carry the laptop. Once the lid is reopened, NetworkManager shows as disconnected and I cannot see any wireless access points until I reboot. I cannot connect by using the "Connect to other wireless network" option until I reboot. -- 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