August 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 520876] New: Update to mysql-5.1.35-34.1 fails to restart mysql
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=520876 Summary: Update to mysql-5.1.35-34.1 fails to restart mysql Classification: openSUSE Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: drankinatty(a)suddenlinkmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.11) Gecko/2009060200 SUSE/3.0.11-0.1 Firefox/3.0.11 On 10.3 updating mysql to mysql-5.1.35-34.1 fails to restart mysql after the upgrade is complete. I guess there is something broken in the post-install script that does not restart the server. The my.cnf (installed as my.cnf.rpmnew) is identical to the existing my.cnf so there isn't any reason mysql should not be restarted. Reproducible: Always Steps to Reproduce: 1. zypper up -t package (with the database repository active) 2. update mysql to mysql-5.1.35-34.1 3. Actual Results: mysql is not restarted after the update Expected Results: mysql should be restarted after the upgrade -- 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 12

[Bug 520532] New: Mark files in webapps/ROOT as %config(noreplace)
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=520532 User mvyskocil(a)novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=520532#c520038 Summary: Mark files in webapps/ROOT as %config(noreplace) Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: ASSIGNED Severity: Critical Priority: P5 - None Component: Java AssignedTo: mvyskocil(a)novell.com ReportedBy: mvyskocil(a)novell.com QAContact: qa(a)suse.de Found By: Community User Moved from bug#520038 2. A more serious error also took place in my webapps/ROOT directory. My own index.html file that was located there, was replaced by the default index.html file that comes with the base tomcat6 installation. In other words, the index.html that the Jakarta-Apache folks supply showing documentation on the tomcat server itself. THIS HAD TO HAVE RESULTED SOMEHOW FROM THIS SECURITY UPDATE!!! I have NOT changed anything else in these directories for some time now. (Good thing I have everything in the webapps directory backed up so I was able to restore it easily enough) tomcat6-webapps installs following files to webapps/ROOT: /srv/tomcat6/webapps/ROOT/RELEASE-NOTES.txt /srv/tomcat6/webapps/ROOT/WEB-INF /srv/tomcat6/webapps/ROOT/WEB-INF/web.xml /srv/tomcat6/webapps/ROOT/asf-logo-wide.gif /srv/tomcat6/webapps/ROOT/build.xml /srv/tomcat6/webapps/ROOT/favicon.ico /srv/tomcat6/webapps/ROOT/index.html /srv/tomcat6/webapps/ROOT/index.jsp /srv/tomcat6/webapps/ROOT/tomcat-power.gif /srv/tomcat6/webapps/ROOT/tomcat.gif /srv/tomcat6/webapps/ROOT/tomcat.svg At least following files needs to be marked as %config(noreplace): /srv/tomcat6/webapps/ROOT/WEB-INF/web.xml /srv/tomcat6/webapps/ROOT/build.xml /srv/tomcat6/webapps/ROOT/favicon.ico /srv/tomcat6/webapps/ROOT/index.html /srv/tomcat6/webapps/ROOT/index.jsp Affects all tomcat6 packages (11.0, 11.1, sle11, 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 6

[Bug 520311] New: sm-notify doesn't notify due to bug in patch
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=520311 Summary: sm-notify doesn't notify due to bug in patch Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: zuziak(a)math.ku.dk QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.0.11) Gecko/2009060200 SUSE/3.0.11-5.2 Firefox/3.0.11 The nfs-utils-1.1.3-18.2.1 source rpm contains the patch sm-notify-no-sync.patch which adds a log statement "Already notifying clients; Exiting" following an if statement. But it doesn't add the required braces around the log statement and the following exit. Thus the exit becomes unconditional making sm-notify exit before sending notifications. Reproducible: Always -- 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 14

[Bug 520013] New: apparmor reports wrong line numbers on error.
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=520013 Summary: apparmor reports wrong line numbers on error. Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor AssignedTo: jeffm(a)novell.com ReportedBy: grey-olli(a)ya.ru QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.11) Gecko/2009060200 SUSE/3.0.11-0.1.1 Firefox/3.0.11 ---- Wed Jul 08, 03:55:57 , /etc/apparmor.d acer15 # cat -n usr.bin.skype | tail -n 3 56 audit deny /home/olli/bin* mrwkx, 57 58 } ---- Wed Jul 08, 03:57:22 , /etc/apparmor.d acer15 # service boot.apparmor restart Reloading AppArmor profiles AppArmor parser error in /etc/apparmor.d/usr.bin.skype at line 491: syntax error, unexpected TOK_AUDIT, expecting TOK_MODE Profile /etc/apparmor.d/usr.bin.skype failed to load failed ---- Wed Jul 08, 03:57:29 , /etc/apparmor.d acer15 # Reproducible: Always Steps to Reproduce: 1. make a bug in a profile 2. service boot.apparmor restart 3. the bug is displayed w/ buggy file name, but line number is invalid. Actual Results: in my case displays line number far after the last line of a file. Expected Results: should show right line number. -- 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 519526] New: Enhancement request: Add option in /etc/sysconfig/SuSEfirewall2 to disable NOTRACK on lo
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=519526 Summary: Enhancement request: Add option in /etc/sysconfig/SuSEfirewall2 to disable NOTRACK on lo Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Enhancement Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: opensuse(a)jeffshantz.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.4) Gecko/2008103100 SUSE/3.0.4-4.6 Firefox/3.0.4 I spoke with Ludwig Nussel about a problem I was having setting up a transparent proxy. I set up Dansguardian (port 8080) and Squid (3128) and had a few custom iptables rules in /etc/sysconfig/scripts/SuSEfirewall2-custom: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner --uid-owner squid -j ACCEPT iptables -t nat -A OUTPUT -p tcp --dport 3128 -m owner --uid-owner squid -j ACCEPT iptables -t nat -A OUTPUT -p tcp --dport 80 -j REDIRECT --to-ports 8080 However, pages just kept loading forever when SuSEfirewall2 was enabled. Ludwig suggested I disable the NOTRACK rules that are put on lo for performance reasons. I did so, and pages loaded fine after this. He suggested I submit a feature enhancement request asking that an option be added to /etc/sysconfig/SuSEfirewall2 to allow a user to enable/disable the NOTRACK rules. Thank you. Reproducible: Always Steps to Reproduce: 1. Configure any proxy service on a given port 2. Turn on SuSEfirewall2 3. Redirect all requests on port 80 to that service using: iptables -t nat -A OUTPUT -p tcp --dport 80 -j REDIRECT --to-ports <service_port> 4. Try loading a page -- nothing will load. 5. Disable the NOTRACK rules: iptables -t raw -F 6. Try loading a page, everything should now work. Actual Results: All pages now load properly (NAT works properly) after deleting the NOTRACK rules Expected Results: There should probably be an option in /etc/sysconfig/SuSEfirewall2 to remove the NOTRACK rules without having to delete them manually. -- 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

[Bug 518603] New: Firefox 3.5 Bouncing Cursor
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=518603 Summary: Firefox 3.5 Bouncing Cursor Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: caf4926(a)opensuse-forums.org QAContact: adrian(a)novell.com Found By: Customer Bouncing Cursor continues at launch of FF for 25-30 secs Current work around by changing 30sec Launch Feedback setting to 5 secs. Mozilla repo (Not beta) kde4.3 RC1 -- 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 11

[Bug 518219] New: sm-notify runs before dhcpcd sets hostname
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=518219 Summary: sm-notify runs before dhcpcd sets hostname Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: zuziak(a)math.ku.dk QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.0.11) Gecko/2009060200 SUSE/3.0.11-0.1.1 Firefox/3.0.11 Sometimes sm-notify is run before the dhcp client has set the correct hostname. This means that the notify messages sent to nfs servers contain the wrong hostname so any locks held by the client are not released. This seems to happen on about every other boot when parallel execution of init scripts is disabled. Reproducible: Sometimes -- 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 23

[Bug 517947] New: dd_rescue: useless "Invalid argument" warnings
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=517947 Summary: dd_rescue: useless "Invalid argument" warnings Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: Beta-Customer For whatever reason, dd_rescue spews a non-fatal Invalid argument warning every 32M (why 32?). # dd_rescue /dev/zero /dev/null dd_rescue: (warning): /dev/null (32768.0k): Invalid argument! 31744.0k dd_rescue: (warning): /dev/null (65536.0k): Invalid argument! 64512.0k dd_rescue: (warning): /dev/null (98304.0k): Invalid argument! 97280.0k dd_rescue: (warning): /dev/null (131072.0k): Invalid argument! 130048.0k dd_rescue: (warning): /dev/null (163840.0k): Invalid argument! 162816.0k dd_rescue: (warning): /dev/null (196608.0k): Invalid argument! 195584.0k dd_rescue: (warning): /dev/null (229376.0k): Invalid argument! 228352.0k dd_rescue: (warning): /dev/null (262144.0k): Invalid argument! 261120.0k dd_rescue: (warning): /dev/null (294912.0k): Invalid argument! 293888.0k dd_rescue: (warning): /dev/null (327680.0k): Invalid argument! 326656.0k dd_rescue: (warning): /dev/null (360448.0k): Invalid argument! 359424.0k dd_rescue: (warning): /dev/null (393216.0k): Invalid argument! 392192.0k dd_rescue: (warning): /dev/null (425984.0k): Invalid argument! 424960.0k dd_rescue: (warning): /dev/null (458752.0k): Invalid argument! 457728.0k dd_rescue: (warning): /dev/null (491520.0k): Invalid argument! 490496.0k dd_rescue: (warning): /dev/null (524288.0k): Invalid argument! 523264.0k dd_rescue: (info): ipos: 539648.0k, opos: 539648.0k, xferd: 539648.0k errs: 0, errxfer: 0.0k, succxfer: 539648.0k +curr.rate: 1182266kB/s, avg.rate: 1047984kB/s, avg.load: 50.5% -- 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 517722] New: tog-pegasus-2.9.0-1.7: possible off by one error in for loop
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=517722 Summary: tog-pegasus-2.9.0-1.7: possible off by one error in for loop Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: All OS/Version: All Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dcb314(a)hotmail.com QAContact: qa(a)suse.de Found By: --- I just had a look at factory package tog-pegasus-2.9.0-1.7 For source code file pegasus/src/Pegasus/Common/Logger.cpp, around line 258 is the source code for (unsigned int i=0; i<=timeStamp.size(); i++) { if(timeStamp[i] == '/' || timeStamp[i] == ':') { Clearly broken code. Suggest new code for (unsigned int i = 0; i < timeStamp.size(); i++) -- 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

[Bug 517281] New: sane-backends-1.0.20: bad for loop
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=517281 Summary: sane-backends-1.0.20: bad for loop Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dcb314(a)hotmail.com QAContact: qa(a)suse.de Found By: --- I just had a look at factory package sane-backends-1.0.20-2.2 For source code file sane-backends-1.0.20/backend/hp3900_config.c around line 940 is the source code for (a = 0; a < 12; a++) { if (myreg[a].resolution == resolution) but struct myreg only has six entries, not 12. Suggest rework code. -- 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