May 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 915037] scp bash completion removes servername on completion
by bugzilla_noreply＠novell.com 05 May '15

05 May '15

http://bugzilla.suse.com/show_bug.cgi?id=915037 --- Comment #32 from Dr. Werner Fink <werner(a)suse.com> --- Created attachment 633272 --> http://bugzilla.suse.com/attachment.cgi?id=633272&action=edit 0001-Work-around-the-libreadline-colon-trouble-if-COMP_WO.patch Part one -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 869790] split-logfile2 doesn't work anymore
by bugzilla_noreply＠novell.com 05 May '15

05 May '15

http://bugzilla.suse.com/show_bug.cgi?id=869790 Petr Gajdos <pgajdos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kstreitova(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 869790] split-logfile2 doesn't work anymore
by bugzilla_noreply＠novell.com 05 May '15

05 May '15

http://bugzilla.suse.com/show_bug.cgi?id=869790 Petr Gajdos <pgajdos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bruno(a)ioda-net.ch, | |pgajdos(a)suse.com Flags| |needinfo?(bruno(a)ioda-net.ch | |) --- Comment #2 from Petr Gajdos <pgajdos(a)suse.com> --- It seems to be fixed between 2.4.10 and 2.4.12 by: --- httpd-2.4.10/support/split-logfile.in +++ httpd-2.4.12/support/split-logfile.in @@ -29,7 +29,7 @@ use strict; use warnings; -my %is_open = (); +my %log_file = (); while (my $log_line = <STDIN>) { # @@ -54,10 +54,9 @@ while (my $log_line = <STDIN>) { # If the log file for this virtual host isn't opened # yet, do it now. # - if (! $is_open{$vhost}) { - open $vhost, ">>${vhost}.log" + if (! $log_file{$vhost}) { + open $log_file{$vhost}, ">>${vhost}.log" or die ("Can't open ${vhost}.log"); - $is_open{$vhost} = 1; } # # Strip off the first token (which may be null in the @@ -65,6 +64,6 @@ while (my $log_line = <STDIN>) { # record to the current log file. # $log_line =~ s/^\S*\s+//; - printf $vhost "%s", $log_line; + print {$log_file{$vhost}} $log_line; } exit 0; Bruno, does https://svn.apache.org/repos/asf/httpd/httpd/trunk/support/split-logfile.in (with s:@perlbin@:/usr/bin/perl:) work for you? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 913092] mozilla/enigmail: Enigmail fails to verify signatures in Seamonkey
by bugzilla_noreply＠novell.com 05 May '15

05 May '15

http://bugzilla.suse.com/show_bug.cgi?id=913092 Andreas Stieger <astieger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |astieger(a)suse.com Resolution|--- |FIXED --- Comment #4 from Andreas Stieger <astieger(a)suse.com> --- (In reply to Björn Voigt from comment #3) > The next enigmail version may fix this bug. See discussion here > https://www.thunderbird-mail.de/index.php/Thread/67342-Enigmail-1-7-Digital… > Unterschrift/ This should then be resolved in 1.8.1 / 1.8.2 available in mozilla:Factory now. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 923402] thunderbird enigmail plugin screws linebreaks
by bugzilla_noreply＠novell.com 05 May '15

05 May '15

http://bugzilla.suse.com/show_bug.cgi?id=923402 Andreas Stieger <astieger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |astieger(a)suse.com Resolution|--- |UPSTREAM --- Comment #2 from Andreas Stieger <astieger(a)suse.com> --- Which version does this affect? Does this still occur with 1.8.1 / 1.8.2 just submitted to mozilla:Factory? Would you not want to report this as an upstream issue? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 929565] some gui programs are not able to launch due to could not connect to x error
by bugzilla_noreply＠novell.com 05 May '15

05 May '15

http://bugzilla.suse.com/show_bug.cgi?id=929565 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |illumilore(a)gmail.com Flags| |needinfo?(illumilore@gmail. | |com) --- Comment #2 from Stefan Dirsch <sndirsch(a)suse.com> --- If you get this kind of error, you either have no $DISPLAY set, wrong $DISPLAY set or no permission to access it. I assume it works for any other X application in the same terminal and shell? For me this sounds more like a bug in steam. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

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

05 May '15

http://bugzilla.opensuse.org/show_bug.cgi?id=860778 Felix Miata <mrmazda(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tonyj(a)suse.com) | --- Comment #26 from Felix Miata <mrmazda(a)earthlink.net> --- (In reply to Tony Jones from comment #25) > This isn't an audit bug, I've not no idea how his system got into this > state and what is changing his I don't know either, but remind that I don't have "system", I have numerous systems, many of which were doing this until I found out I could stop the problem by installing audit or rsyslog. Also, these installations were all begun either direct TW minimal X installations, or upgrades from what were originally minimal X installations that were zypper dup'd from 13.2, which may originally have been 13.1 minimal X installations dup'd to 13.2. Anything that caused these messages to begin showing up only in TW surely must have been caused by some kind of change in some part of one or more of the underlying subsystems. (In reply to Tony Jones from comment #24) > I suspect this is because I'm booting with cmdline option "quiet" and you > are not. I haven't had quiet in any bootloader stanza for any distro since sometime last century. I find little to no activity on vtty1 during init to be highly annoying. Not having quiet on cmdline has never been a problem before that I can remember. > If this is correct, as root, add "quiet" (or "loglevel=4") to > GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run grub2-mkconfig > > /boot/grub2/grub.cfg [or yast equivalent] and reboot. Grub2 is not installed in any rpm-based distro here. Most installations here are booting from a Grub Legacy installation on a primary partition that is never mounted as /boot. > Or install and enable rsyslog, or install and enable audit. Those would seem to be workarounds, not cures for whatever it is we don't seem to have yet identified. I was having what was probably the same problem in my Fedora installations, but I think they all went away eventually via updates. That seems to be the case here now. As I'm running low on installations left that haven't either had audit installed, or do not exhibit the problem. The three I updated in recent hours (kt400, kt88b & t2240), which had last been dup'd 5-8 weeks ago, had neither audit installed nor the problem. All three just updated do have rsyslog-8.9.0-3.1 installed. T2240 has 7.4.3-1.3 first grep rsyslog return from /var/log/zypp/history, kt88b 7.4.7-1.1, kt400 7.4.4-2.1.2. This leads me to think more recent installs have had rsyslog installed as part of a minimal X, while later installs may not be including it. In contrast, host g5eas last updated a week ago, and originally installed 53 weeks ago does have this problem, and has neither audit nor rsyslog installed. I started to install rsyslog on it, but zypper wants to remove systemd-logger to permit it. Host big last updated a week ago, and originally installed 21 months ago does not have this problem, has rsyslog 8.9.0-3.1 installed now, and originally had 7.4.2-1.1 installed 21 months ago. Host gx270 last updated 3 weeks ago, and originally installed 58 weeks ago did have this problem, and had neither audit nor rsyslog installed. I started to install rsyslog on it, zypper wanted to remove systemd-logger to permit it, and I let it proceed. Problem gone on reboot. I'll have to check rsyslog history on newer original installs to try to affirm this likelihood if you wish. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 926932] New: devel:languages:lua/prosody: Cannot be startet after update to 0.9.8-1.1
by bugzilla_noreply＠novell.com 05 May '15

05 May '15

http://bugzilla.opensuse.org/show_bug.cgi?id=926932 Bug ID: 926932 Summary: devel:languages:lua/prosody: Cannot be startet after update to 0.9.8-1.1 Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: VMWare OS: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software Assignee: pgajdos(a)suse.com Reporter: manfred.herteux(a)martingmbh.de QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- prosodyctl restart results in lua: /usr/bin/prosodyctl:49: module 'util.events' not found: no field package.preload['util.events'] no file '/usr/lib64prosody/util/events.lua' no file '/usr/local/share/lua/5.1/util/events.lua' no file '/usr/local/share/lua/5.1/util/events/init.lua' no file '/usr/local/lib/lua/5.1/util/events.lua' no file '/usr/local/lib/lua/5.1/util/events/init.lua' no file '/usr/share/lua/5.1/util/events.lua' no file '/usr/share/lua/5.1/util/events/init.lua' no file '/usr/lib64prosody/util/events.so' no file '/usr/local/lib/lua/5.1/util/events.so' no file '/usr/lib64/lua/5.1/util/events.so' no file '/usr/local/lib/lua/5.1/loadall.so' no file '/usr/lib64prosody/util.so' no file '/usr/local/lib/lua/5.1/util.so' no file '/usr/lib64/lua/5.1/util.so' no file '/usr/local/lib/lua/5.1/loadall.so' stack traceback: [C]: in function 'require' /usr/bin/prosodyctl:49: in main chunk [C]: ? -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 911310] New: /usr/bin/logger (util-linux-systemd) not prerequired
by bugzilla_noreply＠novell.com 05 May '15

05 May '15

http://bugzilla.suse.com/show_bug.cgi?id=911310 Bug ID: 911310 Summary: /usr/bin/logger (util-linux-systemd) not prerequired Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: wicked-maintainers(a)suse.de Reporter: lmuelle(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: No While zypper dup from openSUSE 13.1 to 13.2 I've seen: ( 878/3412) Installation von: wicked-service-0.6.12-1.1 ......................................................................................................[fertig] Zusätzliche rpm-Ausgabe: Network is managed by NetworkManager.service and rcnetwork does not support '' action. scripts/functions.common: line 138: logger: command not found Use systemctl for systemd specific actions. scripts/functions.common: line 138: logger: command not found I guess that's caused by a missing prereq statement in the wicked-service package. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 926795] boot of opensuse installer as PV DomU, pvgrub2 binary fails to find grub configfile, missing linuxefi/initrdefi commands
by bugzilla_noreply＠novell.com 05 May '15

05 May '15

http://bugzilla.suse.com/show_bug.cgi?id=926795 --- Comment #24 from Olaf Hering <ohering(a)suse.com> --- (In reply to Michael Chang from comment #23) > Created attachment 632936 [details] > Proposed config for default pvgrub2 image > > Hi Olaf, > > What about the attach config? It basically implemented the log described in > your comment#21. This looks good, will test it later this week. There should be a Rescue option too. -- You are receiving this mail because: You are on the CC list for the bug.

1 0