July 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 604049] New: build-compare can't handle meinproc generated files
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=604049 http://bugzilla.novell.com/show_bug.cgi?id=604049#c0 Summary: build-compare can't handle meinproc generated files Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: cmorve69(a)yahoo.es QAContact: qa(a)suse.de CC: aj(a)novell.com, coolo(a)novell.com Found By: Community User Blocker: --- It is somehow common to see packages from KDE:KDE4:Factory:Desktop not passing the build-compare test because of index.cache files generated by meinproc4 from docbook files. The problem is meinproc uses libxslt and a XSL file that uses the generate-id() function (http://svn.gnome.org/viewvc/libxslt/trunk/libxslt/functions.c?view=markup) Either libxslt should be patched to generate deterministics IDs or build-compare enhanced to ignore these differences. The relevant XSL files: http://websvn.kde.org/tags/KDE/4.4.3/kdelibs/kdoctools/customization/kde-ch… http://websvn.kde.org/tags/KDE/4.4.3/kdelibs/kdoctools/docbook/xsl/html/aut… -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 36

[Bug 604046] New: phonon 4.4.1 xine backend does not play sound through pulseaudio
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=604046 http://bugzilla.novell.com/show_bug.cgi?id=604046#c0 Summary: phonon 4.4.1 xine backend does not play sound through pulseaudio Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: e.kunig(a)home.nl QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.3) Gecko/20100401 SUSE/3.6.3-1.2 Firefox/3.6.3 After the update to KDE 4.4.3, which comes with phonon 4.4.1, the phonon xine backend does not play sound through pulseaudio. It connects to pulseaudio, I can see the phonon applications like amarok or knotify as playback sources pavucontrol, thus they connect properly to pulseaudio, but I can hear nothing. The sound of other applications, like Firefox, is played perfectly. A downgrade to phonon 4.4.0 solves the problem. Reproducible: Always Steps to Reproduce: 1. Update to KDE 4.4.3 with phonon 4.4.1 2. Set the phonon backend to xine in the KDE system settings / multimedia 3. try to playback with Amarok2 Actual Results: Nothing can be heared from amarok. Expected Results: The playback from amarok should be heared. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 13

[Bug 603620] New: mkfs.btrfs fails on 3 TB partition
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=603620 http://bugzilla.novell.com/show_bug.cgi?id=603620#c0 Summary: mkfs.btrfs fails on 3 TB partition Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 6 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: aschnell(a)novell.com QAContact: qa(a)suse.de CC: mhopf(a)novell.com Found By: Development Blocker: --- mkfs.btrfs fails on 3 TB partition with a seg. fault. -- Configure bugmail: http://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 603328] New: addpart does not cope with command line parameters larger than 2^31-1
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=603328 http://bugzilla.novell.com/show_bug.cgi?id=603328#c0 Summary: addpart does not cope with command line parameters larger than 2^31-1 Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 6 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: fehr(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- While testing with a virtual disk of size 3TB Arvin found that addpart (which is called by libstorage) is not able to handle command line parameters larger than than 2147483647 since it uses atol instead of atoll to convert from string to long long type. Attached patch fixes the problem. -- Configure bugmail: http://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 603316] New: OpenOffice_org seems to run out of file descriptors
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=603316 http://bugzilla.novell.com/show_bug.cgi?id=603316#c0 Summary: OpenOffice_org seems to run out of file descriptors Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 6 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: OpenOffice.org AssignedTo: bnc-team-ooo(a)forge.provo.novell.com ReportedBy: thomas(a)novell.com QAContact: cwei(a)novell.com Found By: Community User Blocker: --- Dann, a community user, reports OOo failing while saving documents. I was able to reproduce it on my 11.3m6 installation. - start oowriter (or aonther component) - enter something - try to save it - error message about an i/o error The strace output indicates that oowriter runs out of filedescriptors: 5850 open("/proc/self/maps", O_RDONLY) = 1023 5850 fstat64(1023, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0 5850 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x83216000 5850 read(1023, "08048000-0804a000 r-xp 00000000 "..., 1024) = 1024 5850 read(1023, "m/libspellli.so\n835c6000-835c700"..., 1024) = 1024 5850 read(1023, ".11.1.so\n83612000-83613000 r--p "..., 1024) = 1024 [...] 5850 munmap(0xbf8a4000, 12288) = 0 5850 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 5850 gettid() = 5850 5850 rt_sigprocmask(SIG_SETMASK, ~[RTMIN RT_1], [], 8) = 0 5850 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 5850 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0 5850 rt_sigprocmask(SIG_UNBLOCK, [HUP INT ILL BUS FPE SEGV USR2 TERM], NULL, 8) = 0 5850 rt_sigprocmask(SIG_BLOCK, [QUIT], NULL, 8) = 0 5850 open("/proc/self/maps", O_RDONLY) = -1 EMFILE (Too many open files) thomas> grep EMFILE ~/w.trc | wc -l 1299 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 22

[Bug 603291] New: To prevent issues with leases timing out, the network should be shut down when suspending
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=603291 http://bugzilla.novell.com/show_bug.cgi?id=603291#c0 Summary: To prevent issues with leases timing out, the network should be shut down when suspending Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dieter.jurzitza(a)t-online.de QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=360055) --> (http://bugzilla.novell.com/attachment.cgi?id=360055) fix that should go into /usr/lib/pm-utils/sleep.d User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.3) Gecko/20100401 SUSE/3.6.3-1.1 Firefox/3.6.3 If you use the traditional way of managing your network, the network is not shut down when doing a suspend / resume. This is not an issue if you have fixed IP-Adresses or if you have DHCP with infinite lease times. However, given you have finite lease times and you shut down your pc during the night, you will run into issues in the morning. The dhcpd does not perform a new request when restarted but assumes the old IP to be valid. This may cause all kind of issues in a company network. The DHCP-server assumes the IP to be free, however, your computer thinks it is still valid. Therefore the network should be shut down prior to suspend. Reproducible: Always Steps to Reproduce: 1. run your pc in a dhcp-network with finite lease times, 2. suspend longer than the lease time 3. reboot and watch what happens Actual Results: machine is using invalid IP address Expected Results: dhcpd should request a new address after resume This files fixes the behaviour as it stops network prior to suspend and restarts it after a resume -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 13

[Bug 603247] New: yast2-priter: call WaitForUpdatedConfigFiles after hp-setup finished
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=603247 http://bugzilla.novell.com/show_bug.cgi?id=603247#c0 Summary: yast2-priter: call WaitForUpdatedConfigFiles after hp-setup finished Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: All OS/Version: openSUSE 11.3 Status: ASSIGNED Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: jsmeix(a)novell.com ReportedBy: jsmeix(a)novell.com QAContact: jsrain(a)novell.com CC: mzugec(a)novell.com Found By: Development Blocker: --- yast2-printer can launch hp-setup to set up HP devices. When hp-setup has finished, it is likely that a new print queue was created by it and therefore yast2-printer should call Printerlib::WaitForUpdatedConfigFiles after hp-setup finished. -- Configure bugmail: http://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 603182] New: YaST2 printer: Change method of selection for individual options in "all options for current driver" window
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=603182 http://bugzilla.novell.com/show_bug.cgi?id=603182#c0 Summary: YaST2 printer: Change method of selection for individual options in "all options for current driver" window Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 6 Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: badshah400(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Created an attachment (id=359920) --> (http://bugzilla.novell.com/attachment.cgi?id=359920) All options window showing the currently selected option for Duplex printing User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.4) Gecko/20100417 SUSE/3.6.4-1.1 Firefox/3.6.4 The present implementation of the individual options in the window that shows up when one clicks on "All options for current driver" is non-intuitive and difficult to understand. It uses an expander box for a selected option that shows "Currently selected" upon expanding. It would be better to replace this by a check-box like implementation that makes it easier to understand for a user as to what current option is selected etc. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://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 603161] New: 11.3 / FACTORY ISOs don't boot in FACTORY's kvm
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=603161 http://bugzilla.novell.com/show_bug.cgi?id=603161#c0 Summary: 11.3 / FACTORY ISOs don't boot in FACTORY's kvm Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: seife(a)novell.slipkontur.de QAContact: qa(a)suse.de CC: snwint(a)novell.com Found By: Community User Blocker: --- I'm trying to boot 11.3M6 in a KVM on a FACTORY installed machine. (thinkpad x200s, core2 duo L9400, vmx capable, kvm-0.12.2-3.13.x86_64) Unfortunately, I never get past the first second of graphical boot menu, then qemu-kvm starts spinning with 100% CPU load and nothing happens anymore. I'm starting qemu like this: qemu-kvm -no-quit -m 1024 -hda opensuse-11_3m6.img \ -monitor stdio \ -net nic,model=e1000 -net user,hostname=opensuse-11_3m6 \ -soundhw ac97 -cdrom ../openSUSE-NET-Build0577-i586.iso I tried -no-kvm and -nographic, which both did not help anything. It seems to stop ~1 second into the boot menu, if I hit "space" early enough, I see the boot selection screen (but cannot select anything), if I don't, it stays at the "welcome" screen forever. 11.2 ISOs work fine, as do Fedora12 and debian 5.04 It also does work with kvm-78.0.10.6-0.1.1 on an openSUSE 11.1 host. I'm not sure who's to blame - if the graphical boot code is buggy (but then, why does it work on older kvm), or if kvm is broken, but it is obvious, that nobody ever tried using KVM on FACTORY ;) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 38

[Bug 602773] New: "udevadm trigger" does not seem to work, resulting in bluetooth being disabled
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=602773 http://bugzilla.novell.com/show_bug.cgi?id=602773#c0 Summary: "udevadm trigger" does not seem to work, resulting in bluetooth being disabled Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: seife(a)novell.slipkontur.de QAContact: qa(a)suse.de CC: kasievers(a)novell.com, vbotka(a)novell.com Found By: Community User Blocker: --- running current factory with KOTD kernel and bluez from home:seife:testing (the same version is now in FACTORY), I noticed today, that bluetooth is not active after booting. Note that due to boot ordering constraints (bluez needs d-bus, but is started via udev), there is a "bluez-coldplug" init-script, that basically does udevadm trigger --subsystem-match=bluetooth after d-bus is started, to make sure that the bluez rule is triggered again. this is the rule: ACTION=="add", SUBSYSTEM=="bluetooth", RUN+="/lib/udev/bluetooth.sh" trying manually, i get: susi:~ # udevadm trigger --verbose --subsystem-match=bluetooth /sys/devices/pci0000:00/0000:00:1a.1/usb4/4-2/4-2:1.0/bluetooth/hci0 but /lib/udev/bluetooth.sh is not triggered. I strace'd udevd and found it does read all rules, but execute no action. Help! ;-) susi:~ # uname -a Linux susi 2.6.34-rc6-28-desktop #1 SMP PREEMPT 2010-05-02 19:55:56 +0200 x86_64 x86_64 x86_64 GNU/Linux susi:~ # rpm -q udev udev-153-1.2.x86_64 susi:~ # rpm -q bluez bluez-4.64-50.3.x86_64 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5