August 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 899394] New: qemu pc-q35-2.1 does not properly support -smbios file=...
by bugzilla_noreply＠novell.com 13 Apr '18

13 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=899394 Bug ID: 899394 Summary: qemu pc-q35-2.1 does not properly support -smbios file=... Classification: openSUSE Product: openSUSE Factory Version: 201409* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: afaerber(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In openQA we use the -smbios file=... option to pass dmi tables in order to change the form factor of the system to laptop. The new default machine pc-q35-2.1 does not seem to support that properly though. /sys/devices/virtual/dmi/id/ doesn't contain any chassis fields in that machine. pc-q35-2.0 works fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 918949] New: Kstars will not compile to include INDI for remote telescope control
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.opensuse.org/show_bug.cgi?id=918949 Bug ID: 918949 Summary: Kstars will not compile to include INDI for remote telescope control Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: All OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Applications Assignee: kde-maintainers(a)suse.de Reporter: john_82(a)tiscali.co.uk QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64) Presto/2.12.388 Version/12.16 Build Identifier: I have tried various ways of obtaining Kstars/Ekos and INDI but have had no luck at all. Kstars should include the extras if INDI has been installed. I haven't got far enough to see if the digital single lens remote camera control software can be added Reproducible: Always Steps to Reproduce: 1.Install / Compile Kstars with the requisites for including Ekos and indi around 2. 3. Actual Results: No signs of the control facilities in Kstars Expected Results: Control facilities in Kstars This web page shows what should happen http://www.indilib.org/about/ekos/setup.html :-( Ubuntu provide the lot in one package. There may also be a problem with installing the remote digital camera control sofware for canon, nikon and others. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 908383] New: VirtualBox Kernelmodule not loaded if fstab with not mountable cifs mountpoint
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.opensuse.org/show_bug.cgi?id=908383 Bug ID: 908383 Summary: VirtualBox Kernelmodule not loaded if fstab with not mountable cifs mountpoint Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: juergenhuber(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- 1. Install openSUSE 64bit from scratch 2. Install VirtualBox-qt with yast, install all recommended dependencies 3. Create a new Machine with an .iso - CD-ROM-File -> test Startup of VM -> VM starts up. 4. Add an remote cifs mountpoint to your fstab which isn't online 5. Reboot the Machine 6. Try to start the even working new VM -> VirtualBox reports that the startup isn't possible because the kernel module is missing. 7. Remove the fstab Entry from 4. -> Reboot -> Restart VM, Works again. My sample-Entry to fstab: //192.168.0.1/dat /server cifs users,credentials=/etc/.pass-pw,gid=users,uid=jue 0 0 The credentials-file was available (double-checked). In my case the remote-share is inside of a VM, so the first mount during startup will fail. Since the error appears the mount will never work because the VM cannot come up. Same configuration on openSUSE 12.3 worked. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 943443] New: no keyboard input after manually installing yast2
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=943443 Bug ID: 943443 Summary: no keyboard input after manually installing yast2 Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: choeger(a)open-xchange.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- this is related to bug 943442 keyboard input does not work in any textarea in Yast2. error message: xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb Qt: Failed to create XKB context! Use QT_XKB_CONFIG_ROOT environmental variable to provide an additional search path, add ':' as separator to provide several search paths and/or make sure that XKB configuration data directory contains recent enough contents, to update please see http://cgit.freedesktop.org/xkeyboard-config/ . libGL error: failed to load driver: swrast Workaround found here: http://stackoverflow.com/questions/26974644/no-keyboard-input-in-qt-creator… export QT_XKB_CONFIG_ROOT=/usr/share/X11/xkb -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 940796] New: Sound always resets to 100% in Firefox
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=940796 Bug ID: 940796 Summary: Sound always resets to 100% in Firefox Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: stephan.barth(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since the last update, about 2 weeks ago, the Audiostream in Firefox always moves back to 100% after a web page stopped playing. This is very loud! This doesn't happen with audacity, cmus player or lmms. pavucontrol displays the Audiostream as CubebUtils. See the attached screenshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 934226] New: [yast2-storage] Changing the disk for a mount point fails silently (if in one go)
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=934226 Bug ID: 934226 Summary: [yast2-storage] Changing the disk for a mount point fails silently (if in one go) Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: svollath(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 637324 --> http://bugzilla.suse.com/attachment.cgi?id=637324&action=edit yast2 debug logs "yast2 disk" fails (silently) to un-/mount disks for an existing mount point that's in use, because actions will be summarized in the wrong order (1. add mount point, 2.remove mount point). How to reproduce: 1. e.g. have /dev/sda3 mounted to /datadisk 2. have /dev/sdb5 ready to be used as new "datadisk" disk 3. start YaST2 Expert Partitioner 4. edit partition e.g. "/dev/sda2" to not being mounted anymore 5. edit partition e.g. "/dev/sdb5" to be mounted as "/datadisk" 6. click finish and see wrong (bad idea-) summary (first add, then remove) 7. continue, realizing "yast2 disk" will finish without any error 8. check with "df" that the initial disk is mounted, still This should not happen. 1. I expected Yast2 to order actions accordingly (remove/add) 2. I expected Yast2 to throw an error for the first failing command (mount point already in use) 3. The second command wasn't executed, otherwise "/dev/sda3" wouldn't be mounted to "/datadisk" anymore ((It's reproducible with e.g. SLES-11-SP4-RC2, so most likely true for all prior versions)) Find debug logs attached. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 932010] New: passing string to UI changes encoding
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=932010 Bug ID: 932010 Summary: passing string to UI changes encoding Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: aschnell(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 635194 --> http://bugzilla.suse.com/attachment.cgi?id=635194&action=edit example script Passing a string to the UI and back changes the encoding. See example script (that even throws an exception during logging which I will report as individual bug). -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 931429] New: readd tcp wrappers until dropped by upstream
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=931429 Bug ID: 931429 Summary: readd tcp wrappers until dropped by upstream Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: pcerny(a)suse.com Reporter: meissner(a)suse.com QA Contact: qa-bugs(a)suse.de CC: crrodriguez(a)opensuse.org Found By: --- Blocker: --- user is angry that tcp wrapper support was dropped from openssh. ------------------------------------------------------------------- Sat May 17 22:31:29 UTC 2014 - crrodriguez(a)opensuse.org - Remove tcpwrappers support now, This feature was removed in upstream code at the end of April and the underlying libraries are abandonware. See: http://comments.gmane.org/gmane.linux.suse.general/348119 It should still stay in until upstream drops it. http://lists.opensuse.org/opensuse-de/2015-05/msg00232.html http://lists.opensuse.org/opensuse-de/2015-05/msg00251.html -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 929634] New: Dialogue for adding mail accounts misleading
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=929634 Bug ID: 929634 Summary: Dialogue for adding mail accounts misleading Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Minor Priority: P5 - None Component: Evolution Assignee: bnc-team-evolution(a)forge.provo.novell.com Reporter: oneukum(a)suse.com QA Contact: lakhil(a)novell.com Found By: --- Blocker: --- Created attachment 633235 --> http://bugzilla.suse.com/attachment.cgi?id=633235&action=edit screenshot of dialogue The dialogue for adding a mail account under Evolution asks me to click "Continue", but the button is labeled "Next" -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 929224] New: system can't start/top services anymore, can't reboot, can't be shutdown
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=929224 Bug ID: 929224 Summary: system can't start/top services anymore, can't reboot, can't be shutdown Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: chuller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The problem manifested itself the first time i tried to restart libvirtd: ------------------------snip-------------------------- skaro:~ # rclibvirtd restart Failed to restart libvirtd.service: Transaction is destructive ------------------------snip-------------------------- The message only appeared lie 5 minutes after entering the command Next i wanted to reboot the system, which simply just did not do anything at all, it just hung: ------------------------snip-------------------------- skaro:/usr/src/chuller/pennyworth # reboot ------------------------snip-------------------------- So I started looking for logs or any indication on why it does behave so weird. dmesg did not show anything suspicious but one i ran journalctl it became pretty clear that systemd somehow seems to be responsible for the current state my machine was in. It showed a entry saying "systemd[1]: Looping too fast. Throttling execution a little." every single second: ------------------------snip-------------------------- -- Logs begin at Fri 2014-11-28 18:35:55 CET, end at Thu 2015-04-30 14:53:41 CEST. -- Apr 30 14:53:41 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:40 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:39 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:38 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:36 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:35 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:34 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:32 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:31 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:30 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:28 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:27 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:26 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:24 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:23 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:22 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:21 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:19 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:18 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:17 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:15 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:14 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:13 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:11 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:10 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:09 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:08 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:06 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:05 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:04 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:02 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:01 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:53:00 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:58 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:57 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:56 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:54 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:53 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:52 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:51 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:49 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:48 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:47 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:45 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:44 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:43 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:41 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:40 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:39 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:38 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:36 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:35 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:34 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:32 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:31 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:30 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:28 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:27 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:26 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:25 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:23 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:22 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:21 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:19 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:18 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:17 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:15 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:14 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:13 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:12 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:10 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:09 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:08 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:06 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:05 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:04 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:02 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:01 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:52:00 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:51:58 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:51:57 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:51:56 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:51:54 skaro systemd[1]: Looping too fast. Throttling execution a little. Apr 30 14:51:53 skaro systemd[1]: Looping too fast. Throttling execution a little. ------------------------snip-------------------------- which also made me chek ho much of diskspace the log file already uses: ------------------------snip-------------------------- skaro:~ # journalctl --disk-usage Journals take up 552.0M on disk. ------------------------snip-------------------------- that made me try some more journalctl functions and it turned out my journal was not consistent anymore as well: ------------------------snip-------------------------- skaro:~ # journalctl --verify 392b28: unused data (entry_offset==0)░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 0% 3912e8: unused data (entry_offset==0)░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 0% ccbd68: unused data (entry_offset==0)██████████████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 46% ccbdc8: unused data (entry_offset==0) Entry number mismatch File corruption detected at /var/log/journal/74fc18841ff54a7f8e09f6b58d4bad53/system@00051483eed4fe2e-4ab91595e03ea8a3.journal~:000000 (of 16777216 bytes, 0%). FAIL: /var/log/journal/74fc18841ff54a7f8e09f6b58d4bad53/system(a)00051483eed4fe2e-4ab91595e03ea8a3.journal~ (Bad message) 391bb0: unused data (entry_offset==0)░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 0% Data object references invalid entry at 4002856███████████████████████████████████████████████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 75% File corruption detected at /var/log/journal/74fc18841ff54a7f8e09f6b58d4bad53/system.journal:000000 (of 16777216 bytes, 0%). FAIL: /var/log/journal/74fc18841ff54a7f8e09f6b58d4bad53/system.journal (Bad message) ------------------------snip-------------------------- Please advise on how to be able to reboot the system once in such a stage, or even better on how to fix the problem without a reboot. I currently am unable to do productive work with it and need to get it back into a state where i can do QA on kvm/libvirt environments. -- You are receiving this mail because: You are on the CC list for the bug.

1 7