February 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 842794] New: qemu-binfmt-conf.sh raises echo: write error: Invalid argument
by bugzilla_noreply＠novell.com 16 Aug '16

16 Aug '16

https://bugzilla.novell.com/show_bug.cgi?id=842794 https://bugzilla.novell.com/show_bug.cgi?id=842794#c0 Summary: qemu-binfmt-conf.sh raises echo: write error: Invalid argument Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: uli(a)suse.com ReportedBy: mvyskocil(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: --- I was following the advice at https://en.opensuse.org/HCL:Chroot # /usr/sbin/qemu-binfmt-conf.sh /usr/sbin/qemu-binfmt-conf.sh: line 41: echo: write error: Invalid argument /usr/sbin/qemu-binfmt-conf.sh: line 44: echo: write error: Invalid argument /usr/sbin/qemu-binfmt-conf.sh: line 45: echo: write error: Invalid argument /usr/sbin/qemu-binfmt-conf.sh: line 48: echo: write error: Invalid argument /usr/sbin/qemu-binfmt-conf.sh: line 51: echo: write error: Invalid argument Please check cpu value and header information for m68k! /usr/sbin/qemu-binfmt-conf.sh: line 55: echo: write error: Invalid argument /usr/sbin/qemu-binfmt-conf.sh: line 59: echo: write error: Invalid argument /usr/sbin/qemu-binfmt-conf.sh: line 60: echo: write error: Invalid argument /usr/sbin/qemu-binfmt-conf.sh: line 61: echo: write error: Invalid argument /usr/sbin/qemu-binfmt-conf.sh: line 62: echo: write error: Invalid argument /usr/sbin/qemu-binfmt-conf.sh: line 63: echo: write error: Invalid argument /usr/sbin/qemu-binfmt-conf.sh: line 64: echo: write error: Invalid argument /usr/sbin/qemu-binfmt-conf.sh: line 67: echo: write error: Invalid argument /usr/sbin/qemu-binfmt-conf.sh: line 68: echo: write error: Invalid argument /usr/sbin/qemu-binfmt-conf.sh: line 71: echo: write error: Invalid argument I've tried to run the registration manually, but # echo ':arm:M::\x7fELF\x01\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x28\x00:\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff:/usr/bin/qemu-arm-binfmt:P' > /proc/sys/fs/binfmt_misc/register bash: echo: write error: Invalid argument got the same error I run on kernel 3.11.1-4.gddaa978-desktop -- 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 829042] New: Kernel 3.10: broken nested KVM
by bugzilla_noreply＠novell.com 16 Aug '16

16 Aug '16

https://bugzilla.novell.com/show_bug.cgi?id=829042 https://bugzilla.novell.com/show_bug.cgi?id=829042#c0 Summary: Kernel 3.10: broken nested KVM Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: aj(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Product Management Blocker: --- Running openSUSE 12.3 with kernel-desktop-3.10.0-1.1.g3dcd746.x86_64, I'm testing OpenStack (SUSE Cloud 2.0 beta) where I launch on my workstation another kvm as OpenStack compute node and inside that compute node launch guests - using nested virtualization on Intel HW. Layerwise: * Guest image * SLES11 SP3 - compute node * openSUSE 12.3 with Kernel 3.10 This works fine with Kernel 3.9 (just rebooted again to double check) but fails with kernel 3.10. After 10s or so of launching a guest image, it becomes "paused". The libvirt log file contains the following: 2013-07-11 09:34:46.779+0000: starting up LC_ALL=C PATH=/sbin:/usr/sbin:/usr/local/sbin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-kvm -name instance-00000001 -S -machine pc-i440fx-1.4,accel=kvm,usb=off -m 512 -smp 1,sockets=1,cores=1,threads=1 -uuid 165aa207-d002-48e8-ae07-b61afa9f3861 -smbios type=1,manufacturer=OpenStack Foundation,product=OpenStack Nova,version=2013.1.3,serial=fc56a9bc-79ca-9b1f-c7ee-5079e9d9ba60,uuid=165aa207-d002-48e8-ae07-b61afa9f3861 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-00000001.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/nova/instances/165aa207-d002-48e8-ae07-b61afa9f3861/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:b6:0c:08,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/var/lib/nova/instances/165aa207-d002-48e8-ae07-b61afa9f3861/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:0 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 Warning: option deprecated, use lost_tick_policy property of kvm-pit instead. char device redirected to /dev/pts/0 (label charserial1) KVM internal error. Suberror: 2 extra data[0]: 80000202 extra data[1]: 80000202 RAX=0000000000000008 RBX=ffff88001c750655 RCX=0000000000000004 RDX=0000000000000004 RSI=0000000000000001 RDI=ffff88001c68d440 RBP=000000000000e8e7 RSP=ffff88001c50bcd0 R8 =0000000000000001 R9 =ffff88001c760548 R10=ffff88001c7512eb R11=ffff88001c760000 R12=ffff88001f8b6697 R13=ffff88001c760f90 R14=0000000000000006 R15=0000000000000000 RIP=ffffffff812b636d RFL=00000202 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =0000 0000000000000000 000fffff 00000000 CS =0010 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA] SS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] DS =0000 0000000000000000 000fffff 00000000 FS =0000 0000000000000000 000fffff 00000000 GS =0000 ffff88001da00000 000fffff 00000000 LDT=0000 0000000000000000 000fffff 00000000 TR =0040 ffff88001da0ff80 00002087 00008b00 DPL=0 TSS64-busy GDT= ffff88001da0a000 0000007f IDT= ffffffff81c28000 00000fff CR0=8005003b CR2=00000000ffffffff CR3=0000000001a05000 CR4=000006f0 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000d01 Code=4c 24 58 49 89 c8 31 c9 0f 1f 80 00 00 00 00 0f b7 6c 0b 01 <66> 41 89 6c 0a 01 48 83 c1 02 49 83 e8 01 75 eb 4c 8b 44 24 58 4b 8d 4c 00 fe 4c 8b 44 24 qemu: terminating on signal 15 from pid 11088 -- 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

[Bug 741521] New: Spice client disconnect crashes qemu-kvm
by bugzilla_noreply＠novell.com 16 Aug '16

16 Aug '16

https://bugzilla.novell.com/show_bug.cgi?id=741521 https://bugzilla.novell.com/show_bug.cgi?id=741521#c0 Summary: Spice client disconnect crashes qemu-kvm Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gvenkat(a)attglobal.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20100101 Firefox/9.0 When spice-client was terminated on a remote client, the VM shutdown with an exception. System kvm-1.0-131.1.x86_64 libspice-server1-0.10.0-28.1.x86_64 Client spice-client-0.10.0-28.1.i586 Reproducible: Didn't try Steps to Reproduce: 1. Don't know how to reproduce. Only happened once in a situation (closing spice client) that has worked every time before. 2. 3. Actual Results: The VM was shutdown Expected Results: The VM should have stayed up so that the SPICE client could connect again This was reported in the log for the VM related to this crash red_channel_client_disconnect: 0x7f9460033f80 (channel 0x7f9503fb2c80 type 1 id 0) main_channel_client_on_disconnect: rcc=0x7f9460033f80 reds_client_disconnect: red_client_destroy: destroy client with #channels 4 red_channel_client_disconnect: 0x7f9460046a00 (channel 0x7f9503fbd240 type 3 id 0) red_channel_client_disconnect: 0x7f9508ebc400 (channel 0x7f95074c16d0 type 2 id 0) red_channel_remove_client: ASSERT pthread_equal(pthread_self(), rcc->channel->thread_id) failed red_channel_client_disconnect: 0x7f950877ac80 (channel 0x7f950487b830 type 4 id 0) Thread 9 (Thread 0x7f94f8712700 (LWP 13630)): #0 0x00007f9500b7cea4 in __lll_lock_wait () from /lib64/libpthread.so.0 #1 0x00007f9500b78294 in _L_lock_999 () from /lib64/libpthread.so.0 #2 0x00007f9500b780aa in pthread_mutex_lock () from /lib64/libpthread.so.0 #3 0x00007f950312d349 in ?? () #4 0x00007f95031c35c9 in ?? () #5 0x00007f95031992d1 in ?? () #6 0x00007f9500b75a3f in start_thread () from /lib64/libpthread.so.0 #7 0x00007f94ffc1e71d in clone () from /lib64/libc.so.6 #8 0x0000000000000000 in ?? () Thread 8 (Thread 0x7f94f7f11700 (LWP 13631)): #0 0x00007f94ffc16d87 in ioctl () from /lib64/libc.so.6 #1 0x00007f95031c3479 in ?? () #2 0x00007f95031c35c1 in ?? () #3 0x00007f95031992d1 in ?? () #4 0x00007f9500b75a3f in start_thread () from /lib64/libpthread.so.0 #5 0x00007f94ffc1e71d in clone () from /lib64/libc.so.6 #6 0x0000000000000000 in ?? () Thread 7 (Thread 0x7f94f7710700 (LWP 13632)): #0 0x00007f94ffc16d87 in ioctl () from /lib64/libc.so.6 #1 0x00007f95031c3479 in ?? () #2 0x00007f95031c35c1 in ?? () #3 0x00007f95031992d1 in ?? () #4 0x00007f9500b75a3f in start_thread () from /lib64/libpthread.so.0 #5 0x00007f94ffc1e71d in clone () from /lib64/libc.so.6 #6 0x0000000000000000 in ?? () Thread 6 (Thread 0x7f94f6f0f700 (LWP 13633)): #0 0x00007f94ffc16d87 in ioctl () from /lib64/libc.so.6 #1 0x00007f95031c3479 in ?? () #2 0x00007f95031c35c1 in ?? () #3 0x00007f95031992d1 in ?? () #4 0x00007f9500b75a3f in start_thread () from /lib64/libpthread.so.0 #5 0x00007f94ffc1e71d in clone () from /lib64/libc.so.6 #6 0x0000000000000000 in ?? () Thread 5 (Thread 0x7f9468e88700 (LWP 13634)): #0 0x00007f94ffc1ed53 in epoll_wait () from /lib64/libc.so.6 #1 0x00007f950035e65b in ?? () from /usr/lib64/libspice-server.so.1 #2 0x00007f9500b75a3f in start_thread () from /lib64/libpthread.so.0 #3 0x00007f94ffc1e71d in clone () from /lib64/libc.so.6 #4 0x0000000000000000 in ?? () Thread 4 (Thread 0x7f9467e86700 (LWP 11391)): #0 0x00007f9500b7a6f9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f950311542f in ?? () #2 0x00007f9500b75a3f in start_thread () from /lib64/libpthread.so.0 #3 0x00007f94ffc1e71d in clone () from /lib64/libc.so.6 #4 0x0000000000000000 in ?? () Thread 3 (Thread 0x7f94fa2c4700 (LWP 11394)): #0 0x00007f9500b7a6f9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f950311542f in ?? () #2 0x00007f9500b75a3f in start_thread () from /lib64/libpthread.so.0 #3 0x00007f94ffc1e71d in clone () from /lib64/libc.so.6 #4 0x0000000000000000 in ?? () Thread 2 (Thread 0x7f9467685700 (LWP 11395)): #0 0x00007f9500b7a6f9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f950311542f in ?? () #2 0x00007f9500b75a3f in start_thread () from /lib64/libpthread.so.0 #3 0x00007f94ffc1e71d in clone () from /lib64/libc.so.6 #4 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f9502f9c760 (LWP 13614)): #0 0x00007f9500b7d37d in read () from /lib64/libpthread.so.0 #1 0x00007f95003f24c0 in ?? () from /usr/lib64/libspice-server.so.1 #2 0x00007f9500340d38 in ?? () from /usr/lib64/libspice-server.so.1 #3 0x00007f9500342bcb in ?? () from /usr/lib64/libspice-server.so.1 #4 0x00007f950034391d in ?? () from /usr/lib64/libspice-server.so.1 #5 0x00007f9500360cef in ?? () from /usr/lib64/libspice-server.so.1 #6 0x00007f9500341421 in ?? () from /usr/lib64/libspice-server.so.1 #7 0x00007f95003426b8 in ?? () from /usr/lib64/libspice-server.so.1 #8 0x00007f950309d157 in ?? () #9 0x00007f950310768b in ?? () #10 0x00007f9503100407 in main () 2012-01-16 07:27:25.347+0000: shutting down -- 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 854343] New: libvirt installation run inappropriate systemd restart
by bugzilla_noreply＠novell.com 11 Aug '16

11 Aug '16

https://bugzilla.novell.com/show_bug.cgi?id=854343 https://bugzilla.novell.com/show_bug.cgi?id=854343#c0 Summary: libvirt installation run inappropriate systemd restart Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: jdouglas(a)suse.com ReportedBy: bruno(a)ioda-net.ch QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 With the new split of libvirt module there's a new effect. libvirtd is firstly installed and the post script run a systemctl try-restart libvirtd.service But all the associated module comes after, and then are not loaded correctly. zypper ps show that at the end you need to restart again libvirtd.service If you have big/slow guest you need to reboot them twice. Reproducible: Always Steps to Reproduce: 1. install libvirtd and run guest 2. update libvirtd 3. you still have to restart it a second time Actual Results: there's still module that have changed Expected Results: Restart libvirtd once every module are loaded. So all the new modules should be (Pre) installed compared to libvirtd Here the log of today update zypper up -r virtualization Loading repository data... Reading installed packages... The following package update will NOT be installed: perl-Term-ProgressBar The following packages are going to be upgraded: guestfs-tools libguestfs0 libvirt libvirt-client libvirt-daemon libvirt-daemon-config-nwfilter libvirt-daemon-driver-interface libvirt-daemon-driver-libxl libvirt-daemon-driver-lxc libvirt-daemon-driver-network libvirt-daemon-driver-nodedev libvirt-daemon-driver-nwfilter libvirt-daemon-driver-qemu libvirt-daemon-driver-secret libvirt-daemon-driver-storage libvirt-daemon-driver-uml libvirt-daemon-driver-vbox libvirt-daemon-driver-xen libvirt-daemon-lxc libvirt-daemon-qemu libvirt-daemon-uml libvirt-daemon-vbox libvirt-daemon-xen libvirt-doc libvirt-glib-1_0-0 libvirt-python perl-Sys-Guestfs perl-Sys-Virt typelib-1_0-LibvirtGConfig-1_0 typelib-1_0-LibvirtGLib-1_0 typelib-1_0-LibvirtGObject-1_0 virt-install virt-manager virt-manager-common virt-viewer 35 packages to upgrade. Overall download size: 12.6 MiB. After the operation, additional 463.7 KiB will be used. Continue? [y/n/? shows all options] (y): y Retrieving package libvirt-client-1.2.0-353.1.x86_64 Installing: virt-install-0.10.0-143.1 ......................................................................................................................................[done] There are some running programs that use files deleted by recent upgrade. You may wish to restart some of them. Run 'zypper ps' to list these programs. yoda:/etc/zypp/repos.d # zypper ps The following running processes use deleted files: PID | PPID | UID | Login | Command | Service | Files ------+------+-----+-------+----------+----------+-------------------------------------------------------------------------- 26378 | 1 | 0 | root | libvirtd | libvirtd | /usr/lib64/libvirt/connection-driver/libvirt_driver_network.so;52a337e9 | | | | | | /usr/lib64/libvirt/connection-driver/libvirt_driver_nodedev.so;52a337e9 | | | | | | /usr/lib64/libvirt/connection-driver/libvirt_driver_nwfilter.so;52a337e9 | | | | | | /usr/lib64/libvirt/connection-driver/libvirt_driver_interface.so;52a337e9 | | | | | | /usr/lib64/libvirt/connection-driver/libvirt_driver_libxl.so;52a337e9 | | | | | | /usr/lib64/libvirt/connection-driver/libvirt_driver_secret.so;52a337e9 | | | | | | /usr/lib64/libvirt/connection-driver/libvirt_driver_lxc.so | | | | | | /usr/lib64/libvirt/connection-driver/libvirt_driver_xen.so | | | | | | /usr/lib64/libvirt/connection-driver/libvirt_driver_uml.so | | | | | | /usr/lib64/libvirt/connection-driver/libvirt_driver_vbox.so You may wish to restart these processes. See 'man zypper' for information about the meaning of values in the above table. yoda:/etc/zypp/repos.d # systemctl restart libvirtd.service -- 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 20

[Bug 784979] New: wxMaxima can not print correctly cyrilloc text (letters)
by bugzilla_noreply＠novell.com 09 Aug '16

09 Aug '16

https://bugzilla.novell.com/show_bug.cgi?id=784979 https://bugzilla.novell.com/show_bug.cgi?id=784979#c0 Summary: wxMaxima can not print correctly cyrilloc text (letters) Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: kiv(a)mail.orbitel.bg QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.8.5 Safari/534.34 When use latin letters to solve some mathematical problem and tnen print evdeery thing is print as expected. When use cyrillic letters on the screen every thing looks as expected but when print to file or to a printer all cyriltlic letters get replaced by unreadable text. Reproducible: Always Steps to Reproduce: 1. Open wxMaxima 2. Solve some problem using cyrillic and latin letters in the worksheet 3. Try to print the workshee to file. 4. Then open the file and check the cyrillic text - it get unreadable Actual Results: The cyrillic text get unreadable when print the worksheet Expected Results: The cyrillic text get unreadable - letters are replaced by some different letters and symbols. Seems like wrong kodepage used. -- 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 828374] New: xscreensavers output core files with SIGSEGV in select () at ../sysdeps/unix/syscall-template.S:81 on VirtualBox .
by bugzilla_noreply＠novell.com 09 Aug '16

09 Aug '16

https://bugzilla.novell.com/show_bug.cgi?id=828374 https://bugzilla.novell.com/show_bug.cgi?id=828374#c0 Summary: xscreensavers output core files with SIGSEGV in select () at ../sysdeps/unix/syscall-template.S:81 on VirtualBox . Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 2 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Xfce AssignedTo: bnc-team-xfce(a)forge.provo.novell.com ReportedBy: bkbin005(a)rinku.zaq.ne.jp QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=547002) --> (http://bugzilla.novell.com/attachment.cgi?id=547002) GDB backtrace files and glxinfo's output . User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.116 Safari/537.36 I am testing openSUSE 13.1 Milestone 2 x86_64 on VirtualBox 4.2.16 r86992 in Windows 7 SP1 64 bit . Host information: https://dl.dropboxusercontent.com/u/86335040/DxDiag17.txt I made VM from the default (Turn OFF "Display"->"Video"->"Enable 3D acceleration") . I installed Xfce and changed Xfce session . And I selected "Setting Manager" -> "Screensaver" . I selected "Random" mode . Then xscreensavers outputted core files with SIGSEGV in select () at ./sysdeps/unix/syscall-template.S:81 . I attach the GDB backtrace files and glxinfo's output . Reproducible: Always Steps to Reproduce: 1. Prepare VirtualBox . 2. Make VM from the default (Turn OFF "Display"->"Video"->"Enable 3D acceleration") . 3. Install openSUSE 13.1 Milestone 2 in VM . 4. Select Xfce Desktop . 5. Login to Xfce Session . 6. Select "Setting Manager" -> "Screensaver" . 7. Select "Random" mode . 8. Wait for dozens of minutes . Actual Results: The xscreensavers output core files many times with SIGSEGV in select () at ./sysdeps/unix/syscall-template.S:81 . Expected Results: The xscreensavers should not output core files . Ubuntu also has the same problem . Please see also: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1197750 https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1197767 https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1197770 https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1198037 https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1198388 https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1198396 https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1198408 -- 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 828382] New: xscreensaver crashes with Segmentation fault in kill() at ../sysdeps/unix/syscall-template.S:81 and X screen hangs-up .
by bugzilla_noreply＠novell.com 09 Aug '16

09 Aug '16

https://bugzilla.novell.com/show_bug.cgi?id=828382 https://bugzilla.novell.com/show_bug.cgi?id=828382#c0 Summary: xscreensaver crashes with Segmentation fault in kill() at ../sysdeps/unix/syscall-template.S:81 and X screen hangs-up . Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 2 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bkbin005(a)rinku.zaq.ne.jp QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=547006) --> (http://bugzilla.novell.com/attachment.cgi?id=547006) 2 GDB backtrace files . User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.116 Safari/537.36 I am testing openSUSE 13.1 Milestone 2 x86_64 on VirtualBox 4.2.16 r86992 in Windows 7 SP1 64 bit . Host information: https://dl.dropboxusercontent.com/u/86335040/DxDiag17.txt . I changed a setup of VM of "Setting"->"Display"->"Enable 3D acceleration" into "ON" I changed session into Xfce . I selected Applications Menu->"Setting"->"Setting Manager" . I selected "Personal"->"Screensaver" . I changed "Mode" into "Random Screen Saver" . I selected all screen savers . I turned OFF "Lock Screen After" . I changed "Blank After" into 1 minnutes and "Cycle After" into 1 minutes . I closed "Screensaver Preferences" . And I waited without doing anything for 2 days . The xscreensaver crashed twice during the 2 days with Segmentation fault in kill() at ../sysdeps/unix/syscall-template.S:81 and X screen hanged-up . I attach the GDB backtrace files . Reproducible: Sometimes Steps to Reproduce: 0. Change a setup of VM of "Setting"->"Display"->"Enable 3D acceleration" into "ON" 1. Change session into Xfce . 2. Select "Applications Menu"->"Setting"->"Setting Manager" . 3. Select "Personal"->"Screensaver" . 4. Change "Mode" into "Random Screen Saver" . 5. Select all screen savers . 6. Turn OFF "Lock Screen After" . 7. Change "Blank After" into 1 minnutes and "Cycle After" into 1 minutes . 8. Close "Screensaver Preferences" . 9. Wait a number of days without doing anything . Actual Results: The xscreensaver crashed twice during the 2 days with Segmentation fault in kill() at ../sysdeps/unix/syscall-template.S:81 and X screen hanged-up . Expected Results: The xscreensave shoud not crash and X screen should not hang-up . -- 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

[Bug 857438] New: Connecting an external hard disk doesn't mount it automatically
by bugzilla_noreply＠novell.com 09 Aug '16

09 Aug '16

https://bugzilla.novell.com/show_bug.cgi?id=857438 https://bugzilla.novell.com/show_bug.cgi?id=857438#c0 Summary: Connecting an external hard disk doesn't mount it automatically Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: i586 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: coutantp(a)sfr.fr QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:26.0) Gecko/20100101 Firefox/26.0 Connecting an external hard disk doesn't mount it automatically. However it is possible to mount it manually (mount /dev/sdb1 mnt) On older version (SuseLinux 12.2) that was OK. 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.

1 5

[Bug 812607] New: Unmounting of network file system takes long time on restart
by bugzilla_noreply＠novell.com 09 Aug '16

09 Aug '16

https://bugzilla.novell.com/show_bug.cgi?id=812607 https://bugzilla.novell.com/show_bug.cgi?id=812607#c0 Summary: Unmounting of network file system takes long time on restart Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tosiara(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:19.0) Gecko/20100101 Firefox/19.0 If SAMBA share is mounted at /mnt/samba and you do restart - it will take long time and you will see last message - "Unmounting /mnt/samba". Looks like network brought down before unmounting network file share Reproducible: Always Steps to Reproduce: 1. Config network to use ifup, connect over wireless and mount SAMBA share 2. Restart the system 3. Usually it takes few seconds to reboot, but this time the screen hangs at "Unmounting /mnt/samba" for about a minute Actual Results: Restart takes long time because it is waiting for unmount Expected Results: It should umnount samba share before bringing network down and do restart quickly -- 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 6

[Bug 714995] New: open-iscsi script does not properly umount iscsi devices
by bugzilla_noreply＠novell.com 08 Aug '16

08 Aug '16

https://bugzilla.novell.com/show_bug.cgi?id=714995 https://bugzilla.novell.com/show_bug.cgi?id=714995#c0 Summary: open-iscsi script does not properly umount iscsi devices Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: thomas.saupe(a)novell.com QAContact: qa(a)suse.de Found By: Novell Technical Services Services Priority: 1000 Blocker: --- The code for umounting iscsi device in /etc/init.d/open-iscsi is broken, especially if the iscsi devices are used within multipathing. On system shutdown the umount of the mounted iscsi devices fails but the devices itself get logged out. This leads to a hang of the reboot, since the later the boot.localfs init script tries to umount the iscsi mounts that already have lost their devices. Attached a patch to the open-iscsi init script that corrects 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 21