March 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 777878] New: Unable to set IPv6 to use temporary address in wireless connection
by bugzilla_noreply＠novell.com 07 Mar '14

07 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=777878 https://bugzilla.novell.com/show_bug.cgi?id=777878#c0 Summary: Unable to set IPv6 to use temporary address in wireless connection Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: f.de.kruijf(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1 I am using NetworkManager on a laptop with a WiFi connection. The particular connection has been setup to use automatic connection and System connection. The WiFi router provides IPv4 and IPv6. Both are set to use Basic settings and Automatic (DHCP). When listing the network interface with "ip addr", I see both IPv4 and IPv6 addresses available. However the IPv6 address has been derived from the MAC address. The default should be to use a temporary IPv6 address. When I enter the line 'IFSYSCTL_NETWORKMAGER="yes"' in /etc/sysconfig/network/config and obviously the line 'NETWORKMANAGER="yes"' is there, both without the single quotes, the file /etc/sysconfig/network/ifsysctl containing the line 'net.ipv6.conf.$SYSCTL_IF.use_tempaddr=2', one would expect to have an IPv6 address that is not derived from the MAC address. Reproducible: Always Steps to Reproduce: 1. see above Actual Results: An IPv6 address derived from the MAC address. Expected Results: The lower 64 bits of the IPv6 should be randomly generated. -- 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 746580] New: System suspend does not work on Thinkpad X201
by bugzilla_noreply＠novell.com 07 Mar '14

07 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=746580 https://bugzilla.novell.com/show_bug.cgi?id=746580#c0 Summary: System suspend does not work on Thinkpad X201 Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: rcoo(a)free.fr QAContact: qa(a)suse.de CC: kgast(a)novell.com, cstender(a)suse.com, jiivee(a)iki.fi, ingham(a)i-pi.com, cy6erGn0m(a)gmail.com Found By: Customer Blocker: --- +++ This bug was initially created as a clone of Bug #680674 +++ I previous used OpenSUSE 11.3 (i386 version, not the x86-64 one) on my Thinkpad X201i, it worked essentially fine and did the suspend and hibernate tasks gracefully. I migrated from this to OpenSUSE 12.1 (x86-64) and found that Suspend to RAM functionality is completely broken; the suspend to disk is broken also. Reproducible: Always Steps to Reproduce: 1. Login 2. Click suspend or type the Fn-F4 key. 3. Wait until the black (text-only )screen appears 4. Watch the blinking leds 5. No other remedy than to poweroff. Actual Results: Laptop hangs. Expected Results: Proper poweroff, of course. Laptop: Lenovo Thinkpad X201i -- 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 18

[Bug 865325] New: wicked clobbers hostname
by bugzilla_noreply＠novell.com 07 Mar '14

07 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=865325 https://bugzilla.novell.com/show_bug.cgi?id=865325#c0 Summary: wicked clobbers hostname Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: mt(a)suse.com ReportedBy: schwab(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- If sysconfig/network/config:DHCLIENT_SET_HOSTNAME=no then the hostname must not be changed. -- 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 867371] New: SLES 11 SP2 boot failure with ALUA timeouts on vmware with raw FC attached disk
by bugzilla_noreply＠novell.com 07 Mar '14

07 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=867371 https://bugzilla.novell.com/show_bug.cgi?id=867371#c0 Summary: SLES 11 SP2 boot failure with ALUA timeouts on vmware with raw FC attached disk Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: SLES 11 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: jlinton(a)tributary.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.146 Safari/537.36 Using a SLES 11 SP2 kernel 3.0.101-0.7.17-default, the virtual machine fails to boot when a raw device is passed through the virtual mptsas adapter. In this case the raw device is a ACNC FC attached Jetstor (attached via an emulex FC adapter). The sda/root device (which is just a vmware virtual volume) is accessible if the /dev entries are manually created with mknod, but udev is unable to create them until sd finishes probing the sdb/raw disk device. Here is an OCR'ed screen capture (AKA may contain typos) dmesg output: [ 2.918164] sdev dma_alignment 511 [ 3.917810] mptsas2 ioc02 attaching ssp device2 fw_channel 0, fu_id 1, phg 1, sas_addr 0x5000 c29f6c78b0af [ 3.920204] scsi target0:0:1: mptsas2: ioc02: add device: fw_channel 0, fw_id 1, phy 1, sas_add r 0x5000c29f6c78b0af [ 3.921923] scsi 02021202 Direct-Access JetStor VMB-00 R001 PQ: 0 ANSI: 5 [ 4.824734] scsi 02021202 mptscsih: ioc0: qdepth=64, tagged=1, simple=1, ordered:0, scsi_level:6, cmd_que=1 [ 4.827184] sdev dma_alignment 511 [ 4.828006] scsi 02021202 alua: supports implicit TPGS [ 4.828897] scsi 02021202 alua: target naa.2000001B4D01CA59 port group 01 rel port 1b [ 4.830084] scsi 02021202 alua: Attached [ 4.834297] sd 0:0:0:0: [sda] 33554432 512-byte logical blocks: (17.1 GB/160 GiB) [ 4.835141] sd 02020202 [sda] Write Protect is off [ 4.835954] sd 02020202 [sda] Mode Sense2 61 00 00 00 [ 4.835994] sd 02020202 [sda] Cache data unavailable [ 4.836808] sd 02020202 [sda] Assuming drive cache2 write through [ 4.837718] sd 0:0:1:02 [sdb] 390623744 512-byte logical blocks: (199 GB/186 GiB) [ 4.837756] sd 02020202 [sda] Cache data unavailable [ 4.837758] sd 02020202 [sda] Assuming drive cache2 write through [ 4.870098] sda2 sdal sda2 [ 4.871675] sd 02020202 [sda] Cache data unavailable [ 4.872461] sd 02020202 [sda] Assuming drive cache2 write through [ 4.873243] sd 02020202 [sda] Attached SCSI disk [ 5.622838] sd 02021202 [sdb] Write Protect is off [ 5.624410] sd 02021202 [sdb] Mode Sense2 bf 00 00 08 [ 5.624654] sd 02021202 [sdb] Write cache2 enabled, read cache2 enabled, doesn’t support DPO or FUA [ 364.290276] sd 02021202 timing out command, waited 360s [ 364.291495] sd 02021202 alua2 rtpg failed, Result2 hostbgte=DID_OK driuerbgte:DRIVER_OK [ 364.309198] sdb: sdbl [ 367.890274] sd 02021202 [sdb] Attached SCSI disk Vmware says this about the raw disk device: naa.6001b4d4373468630000000000000000 Device Display Name: JetStor Fibre Channel Disk (naa.6001b4d43734686300000000 00000000) Storage Array Type: VMW_SATP_ALUA Storage Array Type Device Config: {implicit_support=on;explicit_support=off; explicit_allow=on;alua_followover=on;{TPG_id=1,TPG_state=ANO}} Path Selection Policy: VMW_PSP_MRU Path Selection Policy Device Config: Current Path=vmhba5:C0:T0:L1 Path Selection Policy Device Custom Config: Working Paths: vmhba5:C0:T0:L1 Is Local SAS Device: false Is Boot USB Device: false Reproducible: Always Steps to Reproduce: 1. Install/Upgrade latest SLES 11 SP2 on vmware hypervisor/ESXi 5.5 with virtual mptsas adapter 2. Add a RAW device pass-through to a FC attached ACNC Jetstor 742. 3. Reboot Actual Results: Boot failure due to missing /dev/sd* entries. Expected Results: Systems boots. I can probably open a proper support ticket if that helps anyone, otherwise this is not really a high priority (for us, yet) as its in a testing environment. -- 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 1

[Bug 866802] New: Yast2 does not work
by bugzilla_noreply＠novell.com 07 Mar '14

07 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=866802 https://bugzilla.novell.com/show_bug.cgi?id=866802#c0 Summary: Yast2 does not work Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: fbernasek(a)netscape.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 YaST got signal 11 a YCP file /usr/share/YaST2/modules/PackageCallbacks.rb:2159 on install after all NET_install iso the series 008X YaST2 unuseable, crash after execute Software Management is clicked Reproducible: Always Steps to Reproduce: 1. Start YaST2 2. clicked Software Management 3. crashed Actual Results: YaST2 crashed Expected Results: normal working YaST2 -- 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 867337] New: Update of ucode-intel hanging in os-prober
by bugzilla_noreply＠novell.com 07 Mar '14

07 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=867337 https://bugzilla.novell.com/show_bug.cgi?id=867337#c0 Summary: Update of ucode-intel hanging in os-prober Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: dmzhang(a)suse.com ReportedBy: schwab(a)linux-m68k.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- factory:~/:[0]# ps axf | cat PID TTY STAT TIME COMMAND 2 ? S 0:00 [kthreadd] 3 ? S 0:00 \_ [ksoftirqd/0] 5 ? S< 0:00 \_ [kworker/0:0H] 6 ? S 0:00 \_ [kworker/u4:0] 7 ? S 0:00 \_ [rcuc/0] 8 ? S 0:00 \_ [rcub/0] 9 ? S 0:00 \_ [rcu_preempt] 10 ? S 0:00 \_ [rcuop/0] 11 ? S 0:00 \_ [rcuop/1] 12 ? S 0:00 \_ [rcu_sched] 13 ? S 0:00 \_ [rcuos/0] 14 ? S 0:00 \_ [rcuos/1] 15 ? S 0:00 \_ [rcu_bh] 16 ? S 0:00 \_ [rcuob/0] 17 ? S 0:00 \_ [rcuob/1] 18 ? S 0:00 \_ [migration/0] 19 ? S 0:00 \_ [watchdog/0] 20 ? S 0:00 \_ [watchdog/1] 21 ? S 0:00 \_ [migration/1] 22 ? S 0:00 \_ [rcuc/1] 23 ? S 0:00 \_ [ksoftirqd/1] 25 ? S< 0:00 \_ [kworker/1:0H] 26 ? S< 0:00 \_ [khelper] 27 ? S 0:00 \_ [kdevtmpfs] 28 ? S< 0:00 \_ [netns] 29 ? S< 0:00 \_ [writeback] 30 ? S< 0:00 \_ [kintegrityd] 31 ? S< 0:00 \_ [bioset] 32 ? S< 0:00 \_ [kblockd] 33 ? S< 0:00 \_ [ata_sff] 34 ? S 0:00 \_ [khubd] 35 ? S< 0:00 \_ [md] 36 ? S 0:00 \_ [kworker/0:1] 37 ? S 0:00 \_ [kworker/1:1] 38 ? S 0:00 \_ [khungtaskd] 39 ? S 0:00 \_ [kswapd0] 40 ? SN 0:00 \_ [ksmd] 41 ? SN 0:00 \_ [khugepaged] 42 ? S 0:00 \_ [fsnotify_mark] 43 ? S< 0:00 \_ [crypto] 50 ? S< 0:00 \_ [kthrotld] 51 ? S< 0:00 \_ [kpsmoused] 52 ? S< 0:00 \_ [deferwq] 53 ? S 0:00 \_ [kworker/u4:1] 54 ? S 0:00 \_ [kworker/0:2] 60 ? S 0:00 \_ [kauditd] 65 ? S 0:00 \_ [kworker/1:2] 154 ? S< 0:00 \_ [ttm_swap] 157 ? S 0:00 \_ [scsi_eh_0] 159 ? S< 0:00 \_ [kworker/0:1H] 165 ? S 0:00 \_ [jbd2/vda2-8] 166 ? S< 0:00 \_ [ext4-rsv-conver] 185 ? S 0:00 \_ [scsi_eh_1] 186 ? S 0:00 \_ [scsi_eh_2] 317 ? S 0:00 \_ [vballoon] 382 ? S< 0:00 \_ [hd-audio0] 965 ? S< 0:00 \_ [rpciod] 969 ? S< 0:00 \_ [nfsiod] 978 ? S 0:00 \_ [nfsv4.0-svc] 979 ? S< 0:00 \_ [kworker/1:1H] 1 ? Ss 0:00 /usr/lib/systemd/systemd --system --deserialize 18 215 ? Ss 0:00 /usr/lib/systemd/systemd-journald 242 ? Ss 0:00 /usr/lib/systemd/systemd-udevd 478 ? Ss 0:00 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation 479 ? Ss 0:00 avahi-daemon: running [factory.local] 482 ? Ssl 0:00 /usr/sbin/ModemManager 483 ? Ss 0:00 /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log 484 ? Ssl 0:00 /usr/sbin/nscd --foreground 485 ? Ss 0:00 /sbin/rpcbind -w -f 486 ? Ss 0:00 /usr/sbin/haveged -w 1024 -v 0 -F 487 ? Ss 0:00 /usr/sbin/gpm -m /dev/input/mice -t exps2 489 ? Ss 0:00 /usr/lib/systemd/systemd-logind 490 ? SLs 0:00 /usr/sbin/wickedd --systemd --foreground 496 ? Ssl 0:00 /usr/sbin/rsyslogd -n 515 ? SLs 0:00 /usr/lib/wicked/bin/wickedd-dhcp4 --systemd --foreground 516 ? SLs 0:00 /usr/lib/wicked/bin/wickedd-auto4 --systemd --foreground 517 ? SLs 0:00 /usr/lib/wicked/bin/wickedd-dhcp6 --systemd --foreground 518 ? SLs 0:00 /usr/sbin/wickedd-nanny --systemd --foreground 519 ? Ssl 0:00 /usr/lib/polkit-1/polkitd --no-debug 957 ? Ss 0:00 /usr/sbin/cupsd -f 967 ? Ss 0:00 /usr/sbin/sshd -D 1218 ? Ss 0:00 \_ sshd: root@pts/0,pts/1 1220 pts/0 Ss 0:00 \_ -bash 22765 pts/0 S+ 2:00 | \_ zypper dup 22876 pts/0 Z+ 0:00 | \_ [tar] <defunct> 24393 pts/0 S+ 0:00 | \_ rpm --root / --dbpath /var/lib/rpm -U --percent --force --nodeps -- /var/cache/zypp/packages/factory/suse/x86_64/ucode-intel-20140122-1.2.x86_64.rpm 24394 pts/0 S+ 0:00 | \_ /bin/sh /var/tmp/rpm-tmp.dg8xRT 2 24396 pts/0 S+ 0:00 | \_ /bin/bash --norc /sbin/mkinitrd 2719 pts/0 S+ 0:00 | \_ /usr/bin/perl /sbin/update-bootloader --refresh 2727 pts/0 S+ 0:00 | \_ sh -c /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg >/var/log/YaST2/y2log_bootloader 2>&1 2728 pts/0 S+ 0:00 | \_ /bin/sh /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg 3347 pts/0 S+ 0:00 | \_ /bin/sh /etc/grub.d/30_os-prober 3353 pts/0 S+ 0:00 | \_ /bin/sh /etc/grub.d/30_os-prober 3354 pts/0 S+ 0:00 | \_ /bin/sh /usr/bin/os-prober 3376 pts/0 S+ 0:00 | | \_ /bin/sh /usr/bin/os-prober 3392 pts/0 S+ 0:00 | | \_ /bin/sh /usr/bin/os-prober 3393 pts/0 S+ 0:00 | | \_ /bin/sh /usr/bin/os-prober 3395 pts/0 S+ 0:00 | | | \_ lvs --noheadings --separator : -o vg_name,lv_name 3394 pts/0 S+ 0:00 | | \_ sed s|-|--|g;s|^[[:space:]]*$.*$:$.*$$|/dev/mapper/\1-\2| 3355 pts/0 S+ 0:00 | \_ tr ^ 3356 pts/0 S+ 0:00 | \_ paste -s -d 3578 pts/1 Ss 0:00 \_ -bash 3885 pts/1 R+ 0:00 \_ ps axf 3886 pts/1 S+ 0:00 \_ cat 1002 ? Ss 0:00 /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -c /etc/ntp.conf 1098 ? Ss 0:00 /usr/lib/postfix/master -w 1099 ? S 0:00 \_ pickup -l -t fifo -u 1100 ? S 0:00 \_ qmgr -l -t fifo -u 1102 ? Ss 0:00 /usr/bin/kdm 1124 ? Ss 0:00 /usr/sbin/cron -n 1163 ? Ss 0:00 /usr/lib/systemd/systemd --user 1165 ? S 0:00 \_ (sd-pam) 1283 tty1 Ss+ 0:00 /sbin/agetty --noclear tty1 23184 ? S 0:00 /usr/lib/systemd/system-generators/lvm2-activation-generator /run/systemd/generator /run/systemd/generator.early /run/systemd/generator.late 23185 ? Z 0:00 [systemd-insserv] <defunct> 23186 ? Z 0:00 [systemd-efi-boo] <defunct> 23187 ? Z 0:00 [systemd-gpt-aut] <defunct> 23188 ? Z 0:00 [systemd-rc-loca] <defunct> 23189 ? Z 0:00 [systemd-cryptse] <defunct> 23190 ? Z 0:00 [systemd-system-] <defunct> 23191 ? Z 0:00 [systemd-getty-g] <defunct> factory:~/:[0]# rpm -qf $(type -p lvs) lvm2-2.02.98-0.33.1.x86_64 factory:~/:[0]# uname -r 3.13.3-1-desktop factory:~/:[0]# fuser -v /run/lvm/lvmetad.socket USER PID ACCESS COMMAND /run/lvm/lvmetad.socket: root 1 F.... systemd The command "lvs --noheadings --separator : -o vg_name,lv_name" doesn't terminate. There are no LVM volumes configured. -- 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 1

[Bug 867068] New: Incorrect console settings when installing xen guest
by bugzilla_noreply＠novell.com 07 Mar '14

07 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=867068 https://bugzilla.novell.com/show_bug.cgi?id=867068#c0 Summary: Incorrect console settings when installing xen guest Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers(a)suse.de ReportedBy: suse(a)aastral.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.90 Safari/537.1 Xen 13.1 domU guest console is inaccessible immediately after installation. Reproducible: Always Steps to Reproduce: 1. Install 13.1 x86_64 domU in Xen 13.1 x86_64 dom0 2. Shut down guest 3. Change config files to boot using pygrub 4. Boot guest 5. Connect to console in dom0 "xl console guestname" Actual Results: Console doesn't accept input linux-wo1f login: root [ 50.844129] tty_ldisc_hangup_halt: waiting (login) for xvc0 took too long, but we keep waiting... Expected Results: Xen guest console accepts inputs when connected to in dom0 Looks like a yast installation problem To fix I did the following. Not sure if this is the best way to fix, but this is how I did it. Add console=xvc0 to /boot/grub/menu.lst kernel /boot/vmlinuz-3.11.10-7-xen root=/dev/xvda2 resume=/dev/xvda1 splash=0 console=xvc0 showopts Then echo "xvc0" >> /etc/securetty Then ln -s '/usr/lib/systemd/system/getty@.service' '/etc/systemd/system/getty.target.wants/getty(a)xvc0.service' Then reboot guest. -- 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 867145] New: top command doesn't show complete information under certain conditions
by bugzilla_noreply＠novell.com 07 Mar '14

07 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=867145 https://bugzilla.novell.com/show_bug.cgi?id=867145#c0 Summary: top command doesn't show complete information under certain conditions Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: e1665773(a)drdrb.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=581211) --> (http://bugzilla.novell.com/attachment.cgi?id=581211) screenshot after step 3. - PID 1115, 1118, 1119, 1121 of tsx are missing User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 Hi, I just updated to openSUSE 13.1 (x86_64). Problem is that not all threads of a multi threaded program are shown by the top command. The problem occurs only when you limit the view to a certain user. Reproducible: Always Steps to Reproduce: 1. start any c++ program that starts 8 pthreads using pthread_create 2. start "top" on the command line, then press "H" (shift + h) 3. press "u" then type the user name under which you startet the c++ program Actual Results: 2. -> you see 9 threads, the master thread + 8 threads from pthread_create 3. -> you see 5 threads, the master thread + 4 threads from pthread_create Expected Results: 2. -> you see 9 threads, the master thread + 8 threads from pthread_create 3. -> you see 9 threads, the master thread + 4 threads from pthread_create -- 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 865607] New: Xorg segfault launching apps with "xf86-video-mach64" driver
by bugzilla_noreply＠novell.com 07 Mar '14

07 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=865607 https://bugzilla.novell.com/show_bug.cgi?id=865607#c0 Summary: Xorg segfault launching apps with "xf86-video-mach64" driver Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: i586 OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: eheman(a)funsoft.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 Xorg segmentation fault when using the "xf86-video-mach64" driver on x86 platform when launching apps "firefox" and "openoffice" from plasma desktop. This is on a new install of openSuSE 13.1 on x86 32-bit motherboard. Xorg.0.log shows: [CODE] [ 538.135] (EE) [ 538.135] (EE) Backtrace: [ 538.157] (EE) 0: /usr/bin/Xorg (xorg_backtrace+0x49) [0x81df3e9] [ 538.157] (EE) 1: /usr/bin/Xorg (0x8048000+0x19b174) [0x81e3174] [ 538.157] (EE) 2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xb777240c] [ 538.157] (EE) 3: /usr/lib/xorg/modules/drivers/mach64_drv.so (0xb6d2d000+0x1e645) [0xb6d4b645] [ 538.157] (EE) 4: /usr/lib/xorg/modules/drivers/mach64_drv.so (0xb6d2d000+0x1e72c) [0xb6d4b72c] [ 538.157] (EE) 5: /usr/lib/xorg/modules/libexa.so (0xb6358000+0xc609) [0xb6364609] [ 538.157] (EE) 6: /usr/bin/Xorg (0x8048000+0x11a971) [0x8162971] [ 538.157] (EE) 7: /usr/bin/Xorg (CompositeGlyphs+0xa6) [0x8150ec6] [ 538.157] (EE) 8: /usr/bin/Xorg (0x8048000+0x11411c) [0x815c11c] [ 538.157] (EE) 9: /usr/bin/Xorg (0x8048000+0x10fbbd) [0x8157bbd] [ 538.157] (EE) 10: /usr/bin/Xorg (0x8048000+0x36ecd) [0x807eecd] [ 538.157] (EE) 11: /usr/bin/Xorg (0x8048000+0x24f6a) [0x806cf6a] [ 538.157] (EE) 12: /lib/libc.so.6 (__libc_start_main+0xf3) [0xb72749d3] [ 538.157] (EE) 13: /usr/bin/Xorg (0x8048000+0x25339) [0x806d339] [ 538.157] (EE) [ 538.157] (EE) Segmentation fault at address 0xc [ 538.157] (EE) Fatal server error: [ 538.157] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 538.157] (EE) [ 538.157] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 538.157] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 538.157] (EE) [ 538.257] (EE) Server terminated with error (1). Closing log file. [/CODE] Motherboard VGA chip information: [CODE] lspci | grep VGA 00:09.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rage XL PCI (rev 27) [/CODE] This backtrace and symptoms seem to match the problem discussed here: https://bugs.freedesktop.org/show_bug.cgi?id=70556 The upstream bug report and the commit there fixes the crash. Reproducible: Always Steps to Reproduce: 1. Login to KDE desktop 2. Click "firefox" or "openoffice" icons in plasma desktop 3. X crashes and you are presented with the graphical login again Actual Results: Xorg.0.log show segfault pasted above. Expected Results: Normal application launch. Problem and diagnosis was discussed in the following thread. https://forums.opensuse.org/showthread.php/495697-New-13-1-x86-32-bit-insta… In addition to confirming that the upstream commit resolved the crash, so also did the following circumvention while still using the faulty "xf86-video-mach64" driver as suggested in the upstream bug report. Create file named /etc/X11/xorg.conf.d/50-mydevice.conf containing [CODE] Section "Device" Identifier "Default Device" Driver "mach64" Option "ExaNoComposite" "true" EndSection [/CODE] -- 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 15

[Bug 866612] New: udev update breaks network
by bugzilla_noreply＠novell.com 07 Mar '14

07 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=866612 https://bugzilla.novell.com/show_bug.cgi?id=866612#c0 Summary: udev update breaks network Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: ASSIGNED Severity: Critical Priority: P5 - None Component: Network AssignedTo: systemd-maintainers(a)suse.de ReportedBy: schwab(a)linux-m68k.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- The latest udev update (208-19.1) clobbers the name of the ethernet device, which breaks the network setup. There must be a way to stop that madness. -- 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 2