December 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 783967] New: After upgrading to 5.10.0, wrong timestamps are reported on kernel lines
by bugzilla_noreply＠novell.com 04 Dec '12

04 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=783967 https://bugzilla.novell.com/show_bug.cgi?id=783967#c0 Summary: After upgrading to 5.10.0, wrong timestamps are reported on kernel lines Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: r.ems(a)gmx.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0.1 Hi all, checking /var/log/messages I noticed about 5 hours timestamp difference on kernel messages and other application's messages. This in on openSUSE 12.1 64 bit with rsyslog-5.10.0-6.7.1.x86_64, running kernel 3.3.6. Downgrading to rsyslog=5.8.5-6.4.1 makes the kernel timestamps be reported fine again. See a short extract of /var/log/messages: (compare timestamps on kernel and other lines) Oct 8 17:01:36 X sshd[5728]: Connection closed by x.x.x.x [preauth] Oct 8 11:48:50 X kernel: svc: 127.0.0.1, port=34531: unknown version (0 for prog 100003, nfsd) Oct 8 11:50:01 X kernel: svc: 192.168.30.191, port=753: unknown version (4 for prog 100003, nfsd) Oct 8 17:03:23 X rpc.mountd[32185]: authenticated mount request from xxx:989 for /usr/local/software (/usr/local/software) Oct 8 11:50:50 X kernel: svc: 127.0.0.1, port=41823: unknown version (0 for prog 100003, nfsd) Oct 8 17:05:01 X sshd[6392]: Accepted publickey for username from x.x.x.x port 37304 ssh2 Oct 8 17:05:01 X /USR/SBIN/CRON[6399]: (munin) CMD (test -x /usr/bin/munin-cron && /usr/bin/munin-cron 2>&1 | grep -v "Lock already exists") We are going back to rsyslog=5.8.5-6.4.1 now on our servers. We have found now this error on two of our servers, one running kernel 3.3.6, the other is running 3.4.11. The 2nd one has a time difference of about 45 min. Any more info needed? Thanks, Richard 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.

1 49

[Bug 734672] New: repeated log entries "rsyslogd: imuxsock: recvfrom UNIX: Resource temporarily unavailable"
by bugzilla_noreply＠novell.com 04 Dec '12

04 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=734672 https://bugzilla.novell.com/show_bug.cgi?id=734672#c0 Summary: repeated log entries "rsyslogd: imuxsock: recvfrom UNIX: Resource temporarily unavailable" Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: pat(a)indy.rr.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.8 (KHTML, like Gecko) Chrome/17.0.922.0 Safari/535.8 SUSE/17.0.922.0 5104 log entries in 17 hrs 49 minutes today: Dec 2 17:45:26 Crash rsyslogd: imuxsock: recvfrom UNIX: Resource temporarily unavailable Reproducible: Always Steps to Reproduce: 1.run system 2.look a /var/log/messages 3. Actual Results: run system Expected Results: no imuxsock errors in /var/log/messages 12.1 tumbleweed system updated from 11.4 tumbleweed Note: error does not appear on 12.1 MS1 system updated to 12.1 GM -- 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.

1 28

[Bug 789607] New: Currently emulating unsupported memory accesses in /lib/tls glibc libraries.
by bugzilla_noreply＠novell.com 04 Dec '12

04 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=789607 https://bugzilla.novell.com/show_bug.cgi?id=789607#c0 Summary: Currently emulating unsupported memory accesses in /lib/tls glibc libraries. Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: per(a)computer.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 Hardware: temp65: HP Proliant DL380G3, dual 2.8GHz HT Xeon, 4Gb memory, RAID5 Software: openSUSE 12.2, xen-4.2.0 built from source. This is from a xenhost on openSUSE 12.2: *************************************************************** ** WARNING: Currently emulating unsupported memory accesses ** ** in /lib/tls glibc libraries. The emulation is ** ** slow. To ensure full performance you should ** ** install a 'xen-friendly' (nosegneg) version of ** ** the library, or disable tls support by executing ** ** the following as root: ** ** mv /lib/tls /lib/tls.disabled ** ** Offending process: mount (pid=45) ** *************************************************************** /lib/tls does not exist. Andreas, the following do exist: # ls -1 /lib/i686/nosegneg/ libc-2.15.so libc.so.6 libm-2.15.so libm.so.6 libpthread-2.15.so libpthread.so.0 librt-2.15.so librt.so.1 libthread_db-1.0.so libthread_db.so.1 I don't know if they're being used or not. It is entirely possible that I just need to build xen with the right configure option. 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.

1 24

[Bug 792430] New: Can't remove openSUSE 11.4 from Java:openjdk6:Factory - BuildService API error: unknown (400)
by bugzilla_noreply＠novell.com 04 Dec '12

04 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=792430 https://bugzilla.novell.com/show_bug.cgi?id=792430#c0 Summary: Can't remove openSUSE 11.4 from Java:openjdk6:Factory - BuildService API error: unknown (400) Classification: Internal Novell Products Product: openSUSE Build Service Version: master Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: api AssignedTo: adrian(a)suse.com ReportedBy: mvyskocil(a)suse.com QAContact: adrian(a)suse.com Found By: Development Blocker: --- Hallo, osc meta prj -e -f Java:openjdk6:Factory # remove the openSUSE_11.4 repository configuration Sending meta data... BuildService API error: unknown (400) Internal Server Error Try again? ([y/N]): -- 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.

1 3

[Bug 777642] New: kdevelop subversion module crash
by bugzilla_noreply＠novell.com 04 Dec '12

04 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=777642 https://bugzilla.novell.com/show_bug.cgi?id=777642#c0 Summary: kdevelop subversion module crash Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: i586 OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: george.gugulea(a)certsign.ro QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20100101 Firefox/14.0.1 in subversion package, in subversion/libsvn_wc/wc_db_wcroot.c in funnction svn_wc__db_wcroot_parse_local_abspath svn_wc__db_t *db is NULL the first call: probe_wcroot = apr_hash_get(db->dir_data, local_abspath, APR_HASH_KEY_STRING); finishes with a crash, so kdevelop will crash (when subversion module is activated) I recommend checking for db pointer and wait for subversion to update the code. Reproducible: Always Steps to Reproduce: 1. enable subversion module 2. start kdevelop 3. (sometimes) create a new project from template, no gui. 0x11275081 in svn_wc__db_wcroot_parse_local_abspath (wcroot=0x11fbbd18, local_relpath=0x11fbbd1c, db=0x0, local_abspath=0x110b5508 "/home/georgeg/Projects/TestKdev4.1", result_pool=0x110bf018, scratch_pool=0x110bf018) at subversion/libsvn_wc/wc_db_wcroot.c:383 383 probe_wcroot = apr_hash_get(db->dir_data, local_abspath, (gdb) p db $1 = (svn_wc__db_t *) 0x0 -- 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.

1 2

[Bug 786421] New: KDevelop should have a runtime dependency on Kate
by bugzilla_noreply＠novell.com 04 Dec '12

04 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=786421 https://bugzilla.novell.com/show_bug.cgi?id=786421#c0 Summary: KDevelop should have a runtime dependency on Kate Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: novell(a)monroe.nu QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0 If you run KDevelop without having Kate installed, it complains that it can't find KTextEditor, suggests you install kate and then closes. I didn't have Kate installed despite installing KDevelop via a 'zypper in kdevelop4'. I was using kdevelop from the KDE_Release_49_openSUSE_12.2 repo. But I doubt this is anything new. 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.

1 3

[Bug 790153] New: KDE:Distro:Factory/kdevelop4: Outdated. 4.4.1 released.
by bugzilla_noreply＠novell.com 04 Dec '12

04 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=790153 https://bugzilla.novell.com/show_bug.cgi?id=790153#c0 Summary: KDE:Distro:Factory/kdevelop4: Outdated. 4.4.1 released. Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: kde-maintainers(a)suse.de ReportedBy: kamikazow(a)web.de QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- See http://kdevelop.org/44/kdevelop-441-available Should also be updated in UpdatedApps and KR49. -- 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.

1 1

[Bug 791867] New: Calibre fails to start because of sip API mismatch
by bugzilla_noreply＠novell.com 04 Dec '12

04 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=791867 https://bugzilla.novell.com/show_bug.cgi?id=791867#c0 Summary: Calibre fails to start because of sip API mismatch Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: myrosia(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Firefox/17.0 After an upgrade from 12.1 to 12.2 calibre fails to start with an error. RuntimeError: Failed to load the Progress Indicator plugin: the sip module implements API v9.0 to v9.1 but the progress_indicator module requires API v8.1 My current packages are: rpm -q calibre calibre-0.8.63-1.1.1.x86_64 rpm -q python-sip python-sip-4.14.1-94.1.x86_64 Reproducible: Always Steps to Reproduce: 1. calibre Actual Results: Calibre prints an error message listed above and fails to start Expected Results: Calibre starts up -- 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.

1 2

[Bug 792536] New: karma object in openSUSE connect doesn't work correctly
by bugzilla_noreply＠novell.com 03 Dec '12

03 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=792536 https://bugzilla.novell.com/show_bug.cgi?id=792536#c0 Summary: karma object in openSUSE connect doesn't work correctly Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Board AssignedTo: mhrusecky(a)suse.com ReportedBy: tcech(a)suse.com QAContact: board(a)opensuse.org CC: coolo(a)suse.com Found By: --- Blocker: --- Karma object on dashboard doesn't provide valid information about build service commits. This is just minor issue but it hurts my ego so need to be reported. Bigger problem is that there is no product or component for openSUSE connect. -- 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.

1 0

[Bug 792507] New: octave: Keep site octaverc during update
by bugzilla_noreply＠novell.com 03 Dec '12

03 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=792507 https://bugzilla.novell.com/show_bug.cgi?id=792507#c0 Summary: octave: Keep site octaverc during update Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 1 Platform: Other OS/Version: Other Status: ASSIGNED Severity: Enhancement Priority: P5 - None Component: Development AssignedTo: pgajdos(a)suse.com ReportedBy: pgajdos(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- On Wed, Oct 31, 2012 at 06:04:14AM +0000, Jurzitza Dieter wrote: > Dear Mr. Gajdos, > > from the spec-file I have seen that you are actively working on the packaging > of octave for openSUSE. I just wanted to suggest to include a check in the > installer (I guess in the spec-file) that if /usr/share/octave/site/m/startup/ > octaverc exists to just keep it … it is annoying to re-modify this file every > other time in order to keep track of the local configuration if an update is > made and it gets deleted each time. > > Thank you very much for your efforts, > > take care > > > > > > > > > > > > Dieter Jurzitza -- 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.

1 1