May 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 928749] memory handling error with case insensitive sort using UTF-8
by bugzilla_noreply＠novell.com 06 May '15

06 May '15

http://bugzilla.novell.com/show_bug.cgi?id=928749 Andreas Schwab <schwab(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|schwab(a)suse.de |pth(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 924314] New: malformed string in ssh options during installation
by bugzilla_noreply＠novell.com 06 May '15

06 May '15

http://bugzilla.opensuse.org/show_bug.cgi?id=924314 Bug ID: 924314 Summary: malformed string in ssh options during installation Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Translations Assignee: ke(a)suse.com Reporter: trcs(a)gmx.com QA Contact: ke(a)suse.com CC: guillaume.gardet(a)opensuse.org, jreidinger(a)suse.com, sbphr(a)volted.net, trcs(a)gmx.com Depends on: 903881 Found By: --- Blocker: --- Created attachment 628657 --> http://bugzilla.opensuse.org/attachment.cgi?id=628657&action=edit File generated by "save_y2logs /tmp/y2logs.tgz" after installation. +++ This bug was initially created as a clone of Bug #903881 +++ When you reach the "Installation Settings" screen it appears the same message, it only changes the fast_gettext version (0.9.2 in this case). Steps to Reproduce: 1. Launch installation with Spanish selected as default language. 2. Continue until you reach the aforementioned screen. Actual Results: Error pop-up displaying the following message: Error Internal error. Please report a bug report with logs. Details: malformed format string - %" Caller: /usr/lib64/ruby/gems/2.1.0/gems/fast_gettext-0.9.2/lib/fast_gettext/vendor/string.rb:70:in `%' If you press the OK button then it appears a new pop-up: Error Internal error. Please report a bug report with logs. Details: undefined method `[]' for false:FalseClass Caller: /usr/share/YaST2/lib/installation/proposal_runner.rb:378:in `block in make_proposal' And there is a third pop-up when you push the OK button: Calling the YaST module `inst_proposal has failed. More information can be found near the end of the '/var/log/YaST2/y2log' file. This is worth reporting a bug at http://bugzilla.novell.com/. Please, attach also all YaST logs stored in the '/var/log/YaST2/' directory. See http://en.opensuse.org/Bugs/YaST for more information about YaST logs. You can continue the installation if you press the Next button, but you can't make any changes in this step. Expected Results: There's should work fine and let you make whatever change you want to before starting the installation. Build Date & Hardware: The bug is present in at least the following two snapshots: openSUSE-Tumbleweed-DVD-x86_64-Snapshot20150312-Media.iso openSUSE-Tumbleweed-DVD-x86_64-Snapshot20150319-Media.iso Additional Information: Any other useful information: Logs attached as suggested. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 918158] error 4 segfault in systemd and systemd-udev
by bugzilla_noreply＠novell.com 06 May '15

06 May '15

http://bugzilla.suse.com/show_bug.cgi?id=918158 --- Comment #41 from Thomas Blume <thomas.blume(a)suse.com> --- (In reply to Ivan Topolsky from comment #39) > Created attachment 633326 [details] > rsyslog (xz-compresesd) > > I just realized that, as systemd has crashed, journald would be missing some > parts. (systemd's segfault isn't in there). > > Here's rsyslog's output in /var/log/messages of the same time frame. Uh, there are more processes that show segfaults: -->-- grep segfault log.20150430.rs 2015-04-29T02:43:17.104174+02:00 argo kernel: [420779.641913] Chrome_ChildThr[24640]: segfault at 0 ip 00007f8410d57d6e sp 00007f83ff3ec440 error 6 in libmozalloc.so;553fb361 (deleted)[7f8410d55000+5000] 2015-04-29T02:43:58.943174+02:00 argo kernel: [420821.508383] python[32479]: segfault at 85c70008 ip 00007f47b484d280 sp 00007ffe9ef8db48 error 4 in libpython2.7.so.1.0[7f47b4776000+161000] 2015-04-29T02:43:59.221291+02:00 argo kernel: [420821.786844] bitcoin-opencon[919]: segfault at 12f8fae8 ip 00007fce6215ee4e sp 00007fce2b3037e8 error 4 in libc-2.19.so[7fce620cf000+19e000] 2015-04-30T19:03:43.860876+02:00 argo kernel: [541390.712732] systemd[1]: segfault at 4a800150 ip 000000000049c1d0 sp 00007ffcb5a303d0 error 4 in systemd[400000+116000] 2015-04-30T19:58:00.969919+02:00 argo kernel: [544649.967254] akonadi_agent_l[18453]: segfault at 0 ip 00007fc27e62f150 sp 00007ffdab57b690 error 4 in libQtDBus.so.4.8.6[7fc27e616000+7b000] 2015-04-30T19:58:00.971273+02:00 argo kernel: [544649.967966] akonadi_agent_l[18436]: segfault at 1200000018 ip 00007f7ddd506bf8 sp 00007ffe84c6e2c0 error 4 in libc-2.19.so[7f7ddd48e000+19e000] 2015-04-30T19:58:01.505877+02:00 argo kernel: [544650.503186] python[19344]: segfault at 764d0000 ip 00007fa442b95e29 sp 00007ffecf185050 error 4 in libpython2.7.so.1.0[7fa442adf000+161000] 2015-04-30T19:58:42.586285+02:00 argo kernel: [544691.609727] python[19430]: segfault at 85c70008 ip 00007fa442bb6280 sp 00007ffecf185458 error 4 in libpython2.7.so.1.0[7fa442adf000+161000] --<-- All of them with error 4 or 6 suggesting that there are pointers to invalid memory addresses. It is quite unlikely that the code in all of these programs is buggy. If your physical RAM isn't broken, something else is silently corrupting your memory. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 929648] [ICE] [aarch64] cc1plus segmentation fault on aarch64/ARM when building lucene++
by bugzilla_noreply＠novell.com 06 May '15

06 May '15

http://bugzilla.novell.com/show_bug.cgi?id=929648 Richard Biener <rguenther(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |astieger(a)suse.com Flags| |needinfo?(astieger(a)suse.com | |) --- Comment #3 from Richard Biener <rguenther(a)suse.com> --- Please attach preprocesed source and the output of appending -v to the failing compiler command line. You might also just want to wait until we switch to GCC 5. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 922402] New: Hylafax+: update overwrites settings to systemd config
by bugzilla_noreply＠novell.com 06 May '15

06 May '15

http://bugzilla.opensuse.org/show_bug.cgi?id=922402 Bug ID: 922402 Summary: Hylafax+: update overwrites settings to systemd config Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: axel.braun(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- According to the description in README.SUSE the /usr/lib/systemd/system/hylafax-hfaxd.service can be modified to reflect a send-only environment. An update overwrites this setting. This should be changed. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 860778] audit messages in kernel spamming system logs and vttys
by bugzilla_noreply＠novell.com 06 May '15

06 May '15

http://bugzilla.opensuse.org/show_bug.cgi?id=860778 --- Comment #28 from Felix Miata <mrmazda(a)earthlink.net> --- Created attachment 633356 --> http://bugzilla.opensuse.org/attachment.cgi?id=633356&action=edit Factory y2logs from host gx28b July 2014 Attachment is from system experiencing the litter on which neither audit nor rsyslog were ever installed. I disagree that there is no bug, and that nothing has changed. These messages should not be littering the vttys by default on any installation. If either audit or rsyslog or quiet or loglevel=4 are required to avoid the litter, then the minimal install process should ensure at least one of them is applied during installation. That hasn't been happening since sometime after 13.1 release, which included installation of rsyslog, which stopped sometime before July 2014, after which neither audit nor rsyslog were being installed. Bug 916773 has y2logs from such an installation (minimal X in February onto multiboot system with bootloader already present). Neither any bootloader (obviating the likelihood of knowing quiet or loglevel=4 kludges are among various workaround requireds), nor audit, nor rsyslog were installed, resulting in an installation experiencing the spam until I quashed it by installing audit. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 905639] Enabling autofs delays login by letting systemd-logind fail
by bugzilla_noreply＠novell.com 06 May '15

06 May '15

http://bugzilla.suse.com/show_bug.cgi?id=905639 Dr. Werner Fink <werner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fcrozat(a)suse.com --- Comment #54 from Dr. Werner Fink <werner(a)suse.com> --- (Re)adding all maintainers of NetworkManager due to comment #53 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 927033] X11 does not work with qemu and KVM
by bugzilla_noreply＠novell.com 06 May '15

06 May '15

http://bugzilla.suse.com/show_bug.cgi?id=927033 --- Comment #3 from Lin Ma <lma(a)suse.com> --- (In reply to Lin Ma from comment #2) > (In reply to Bruce Rogers from comment #1) > > I added a reference to https://bugzilla.suse.com/show_bug.cgi?id=893892 > > because it sounded like the same issue. I haven't taken the time to validate > > that. But if it is, it might be also worth checking whether the very latest > > SEABIOS git tree has this fixed. > In my understanding, It may be not the same issue. > I imported a sles 12 guest image(runlevel 3, no X11 installed) with cirrus > vga card, The screen goes blank as well > This cirrus issue is now being tracked in a new bug. Please refer to https://bugzilla.suse.com/show_bug.cgi?id=929812 - KMS for cirrus doesn't work well under multi-user.target, It causes VM's screen remains black > > Just a few weeks ago, another fix for this issue was included there. It is a > > known issue for which there are already many "work arounds" there to attempt > > to still be compatible with a quite inadequate x86emu implementation > > included in older X11. (see "Subject: [SeaBIOS] [PATCH 0/3] Emulate "leal" > > instruction to workaround x86emu bugs" on the SEABIOS ML as the culminating > > patch series of the recently reported issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 918158] error 4 segfault in systemd and systemd-udev
by bugzilla_noreply＠novell.com 06 May '15

06 May '15

http://bugzilla.suse.com/show_bug.cgi?id=918158 --- Comment #40 from Dr. Werner Fink <werner(a)suse.com> --- (In reply to Ivan Topolsky from comment #39) The logs from rsyslog are the logs from systemd upto the point of the crash due to the fact that the socket /dev/log is hold by systemd and any message will be forwarded to journald and if installed to rsyslog -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 929711] vsftpd virtual users not working
by bugzilla_noreply＠novell.com 06 May '15

06 May '15

http://bugzilla.suse.com/show_bug.cgi?id=929711 Martin Pluskal <mpluskal(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpluskal(a)suse.com Assignee|varkoly(a)suse.com |tchvatal(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0