http://bugzilla.novell.com/show_bug.cgi?id=536505
Summary: rrdtool graph has some problems with vertical
auto-scaling
Classification: openSUSE
Product: openSUSE 11.1
Version: Final
Platform: All
OS/Version: SLES 10
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: Ulrich.Windl(a)rz.uni-regensburg.de
QAContact: qa(a)suse.de
Found By: ---
Created an attachment (id=316589)
--> (http://bugzilla.novell.com/attachment.cgi?id=316589)
Example with --rigid: No y scale displayed
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21)
Gecko/20090410 SUSE/1.1.16-1.1.2 SeaMonkey/1.1.16
(Found in current version of SLES10 SP2, rrdtool-1.2.12-13.2)
Specific values (like all between 17.7 and 17.8) cause rrdtool's graph to
autoscale the values at a range of 10 to 20, making actual variations
practically invisible. There are other intervals where similar problems arise,
like [42.0:42.2] where the scale is [40:50].
The --alt-autoscale improves the scaling, but has a problem with not enough
numeric labels for the y-axis being shown, just as --rigid does.
The author of the tool said the current version is much better regarding those
issues.
Reproducible: Sometimes
Steps to Reproduce:
1. Create graphs with automatic scaling where the values vary a little bit
around some undetermined value
Actual Results:
Some graphs are not good enough to show the variations.
Expected Results:
The vertical scale should respect the range of values more that it currently
does.
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=768947https://bugzilla.novell.com/show_bug.cgi?id=768947#c0
Summary: purge-kernels does not log to /var/log/zypp/history
Classification: openSUSE
Product: openSUSE 12.2
Version: Factory
Platform: Other
OS/Version: openSUSE 12.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: libzypp
AssignedTo: mmarek(a)suse.com
ReportedBy: suse-beta(a)cboltz.de
QAContact: qa-bugs(a)suse.de
Found By: Beta-Customer
Blocker: ---
purge-kernels logs to /var/log/messages - but that's a logfile nobody reads
when he wants to check the package installation/removal history.
/var/log/zypp/history is a much better logfile for this - purge-kernels should
write it's removal log there (additional or instead of /var/log/messages).
(Yes, I know that purge-kernels calls rpm directly ;-)
--
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.
http://bugzilla.opensuse.org/show_bug.cgi?id=902779
Bug ID: 902779
Summary: [Factory] Long boot delay "a start job is running
for..."
Classification: openSUSE
Product: openSUSE Factory
Version: 201410*
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: sb56637(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Hi,
My openSUSE Factory installation was taking at least 60 seconds longer than
normal to boot. The delay always occurred on every boot. The delay occured
before initializing the display manager with a message:
"A start job is running for", and it would alternate between four different
services: X display manager, Avahi, NetworkManager, and Modem Manager.
I tried disabling the Modem Manager service, but it still kept hanging on Avahi
and NetworkManager. I eventually tried disabling and later re-enabling the
NetworkManager services, and it now boots quickly without hanging.
I don't really know why this happened or what I did to fix it. Please let me
know what additional information you need to prevent this bug from happening.
Thanks a lot!
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=840485https://bugzilla.novell.com/show_bug.cgi?id=840485#c0
Summary: Firefox 24.0/17.0.9esr security release
Classification: openSUSE
Product: openSUSE 12.3
Version: Final
Platform: Other
OS/Version: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Firefox
AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com
ReportedBy: wolfgang(a)rosenauer.org
QAContact: qa-bugs(a)suse.de
CC: security-team(a)suse.de
Found By: ---
Blocker: ---
2013-09-17 is the announced release date for the following Mozilla applications
which contain security fixes (as always) (https://wiki.mozilla.org/Releases):
Firefox 24.0
Firefox 17.0.9esr
xulrunner 17.0.9esr
Seamonkey 2.21
Thunderbird 17.0.9esr
Thunderbird 24.0
(minimum NSPR 4.10 and NSS 3.15.1 requirements I think already met with last
update round)
I'll provide updates for openSUSE distributions as usual with one exception
where I'd like to get some feedback:
Thunderbird will do a big version update to 24.0 for non-esr versions. Since
esr and non esr versions were 99,9% identical in the 17.0 series we have the
choice to update to 17.0.9esr or 24.0 for released distributions which will
only move the major upgrade around 12 weeks so I'm in favor to follow the big
update now already.
--
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.
http://bugzilla.suse.com/show_bug.cgi?id=901115
Bug ID: 901115
Summary: yast2-network overwrites postfix configuration
Classification: openSUSE
Product: openSUSE Factory
Version: 201410*
Hardware: Other
OS: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: YaST2
Assignee: yast2-maintainers(a)suse.de
Reporter: lmb(a)suse.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
Created attachment 609975
--> http://bugzilla.suse.com/attachment.cgi?id=609975&action=edit
main.cf mods caused by yast2 network
After a long time, I used yast2-network to change something in the network
configuration of my node. (Changed the hostname.)
As a result, my postfix main.cf was overwritten and rendered unusuable. I'm
entirely unsure why some of these parameters were touched - why would it unset
mailbox_command, set mailbox_transport, unset relay_host?
Yes, this was facilitated by me having
/etc/sysconfig/mail:MAIL_CREATE_CONFIG="yes" at the default value, but
normally, none of the yast2 tools overwrites manually modified files silently,
without even creating an in-place backup.
Especially since this looks as if unrelated parameters were touched. I might
have understood rewriting "mydestination", but the other parameters make
absolutely no sense.
I'm attaching the diff here - I restored the main.cf from backup.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=606436http://bugzilla.novell.com/show_bug.cgi?id=606436#c0
Summary: Incorrect VTY charset?
Classification: openSUSE
Product: openSUSE 11.3
Version: Milestone 6
Platform: All
OS/Version: openSUSE 11.3
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: nice(a)titanic.nyme.hu
QAContact: qa(a)suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/5332
(KHTML, like Gecko) Chrome/5.0.342.9 Safari/533.2
I installed openSUSE 11.3 Milestone 6 in the hungarian language. Interestingly
when using the text-mode virtual terminals, (at least) two letters of the
hungarian alphabet are displayed incorrectly: I get õ instead of ő, and û
instead of ű. This is the same as displaying a hungarian text file (written in
iso-8859-2) using iso-8859-1. Isn't it unicode? Or are just the characters
wrongly positioned in the charset table?
Also see: http://bugzilla.novell.com/show_bug.cgi?id=605575
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.
https://bugzilla.novell.com/show_bug.cgi?id=848783https://bugzilla.novell.com/show_bug.cgi?id=848783#c0
Summary: glibc / known bug: "options rotate" in
/etc/resolv.conf causes DNS name reolution FAIL with
IPv6 resolver addresses; patch available
Classification: openSUSE
Product: openSUSE 12.3
Version: Final
Platform: All
OS/Version: openSUSE 12.3
Status: NEW
Severity: Major
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: darx+opensuse(a)sent.com
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
on
uname -a
Linux darxdev.int 3.7.10-1.16-xen #1 SMP Fri May 31 20:21:23 UTC 2013
(97c14ba) x86_64 x86_64 x86_64 GNU/Linux
with
rpm -qa | grep -i glibc | sort
glibc-2.17-4.7.1.x86_64
glibc-32bit-2.17-4.7.1.x86_64
glibc-debuginfo-2.17-4.7.1.x86_64
glibc-devel-2.17-4.7.1.x86_64
glibc-devel-static-2.17-4.7.1.x86_64
glibc-extra-2.17-4.7.1.x86_64
glibc-i18ndata-2.17-4.7.1.noarch
glibc-info-2.17-4.7.1.noarch
glibc-locale-2.17-4.7.1.x86_64
glibc-utils-2.17-4.7.1.x86_64
linux-glibc-devel-3.7.1-2.1.3.noarch
with either IPv4 resolvers
cat /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4
or IPv6 resolvers
cat /etc/resolv.conf
nameserver 2001:4860:4860::8888
nameserver 2001:4860:4860::8844
'svn co' works as expected; in both cases:
S="www.nlnetlabs.nl"
T="svn/nsd/tags/NSD_4_0_0_REL/tpkg/manual"
svn co http://$S/$T test
...
Checked out revision 4089.
next, adding "options rotate" to resolv.conf, with IPv4 rolvers,
cat /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4
options rotate
'svn co' still works,
svn co http://$S/$T test
...
Checked out revision 4089.
but with IPv6, FAILS
cat /etc/resolv.conf
nameserver 2001:4860:4860::8888
nameserver 2001:4860:4860::8844
options rotate
svn co http://$S/$T test
...
svn: E670002: Unable to connect to a repository at URL
'http://www.nlnetlabs.nl/svn/nsd/tags/NSD_4_0_0_REL/tpkg/manual'
svn: E670002: Name or service not known
note, using numeric IP for SVN still works,
svn co http://[2001:7b8:206:1::1]/$T test
...
Checked out revision 4089.
this appears to be due to a glibc bug,
https://bugzilla.redhat.com/show_bug.cgi?id=841787http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627531https://bugzilla.redhat.com/show_bug.cgi?id=804630https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/915272
1st link has a patch, but for an different version of glibc, and on redhat
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.
https://bugzilla.novell.com/show_bug.cgi?id=864716https://bugzilla.novell.com/show_bug.cgi?id=864716#c0
Summary: AUDIT-0: libKF5Auth4.x86_64: W:
suse-dbus-unauthorized-service
/etc/dbus-1/system.d/org.kde.kf5auth.conf
Classification: openSUSE
Product: openSUSE Factory
Version: 13.2 Milestone 0
Platform: Other
OS/Version: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Security
AssignedTo: security-team(a)suse.de
ReportedBy: hrvoje.senjan(a)gmail.com
QAContact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/33.0.1750.91 Safari/537.36 SUSE/33.0.1750.91
Source can be found at KDE:Frameworks5/kauth. As with kinit package, code is
just ported to Qt5/KF5. org.kde.kf5auth.conf was renamed from org.kde.auth.conf
so it can be co-installed with kdelibs4 package(s)
Thus - asking for whitelist =)
Thanks!
Reproducible: Always
--
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.