October 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 776060] New: RabbitMQ won't start
by bugzilla_noreply＠novell.com 15 Oct '12

15 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=776060 https://bugzilla.novell.com/show_bug.cgi?id=776060#c0 Summary: RabbitMQ won't start Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: robert.martin(a)martronix.co.uk QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1 Version 2.8.2-2.1.3-x86_64 When trying to start a rabbitmq server it fails and the following can be found in /var/log/rabbitmq/startup_log Activating RabbitMQ plugins ... {"init terminating in do_boot",{{badmatch,{error,{edge,{bad_vertex,xmerl},rabbitmq_management,xmerl}}},[{rabbit_plugins,calculate_dependencies,3},{rabbit_prelaunch,prepare_plugins,3},{rabbit_prelaunch,start,0},{init,start_it,1},{init,start_em,1}]}} If the rabbitmq-server-plugins aren't installed it appears to start OK. The actual error is that xmerl is missing from the erlang installation that it depends on. If erlang is installed from source, then rabbitmq-server will start. Reproducible: Always Steps to Reproduce: 1. Install Erlang 2. Install rabbitmq server, including rabbitmq-server-plugins 3. Start rabbitmq-server using either "rcrabbitmq-server start" or "systemctl start rabbitmq-server.service" 4. Observe message and check log files Actual Results: /var/log/rabbitmq/startup_log In log file /var/log/rabbitmq/startup_log Activating RabbitMQ plugins ... {"init terminating in do_boot",{{badmatch,{error,{edge,{bad_vertex,xmerl},rabbitmq_management,xmerl}}},[{rabbit_plugins,calculate_dependencies,3},{rabbit_prelaunch,prepare_plugins,3},{rabbit_prelaunch,start,0},{init,start_it,1},{init,start_em,1}]}} Expected Results: No error messages -- 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 5

[Bug 781022] New: Xemacs loading of perl mode fails
by bugzilla_noreply＠novell.com 15 Oct '12

15 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=781022 https://bugzilla.novell.com/show_bug.cgi?id=781022#c0 Summary: Xemacs loading of perl mode fails Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rschweikert(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- When opening a perl file with Xemacs the following trace is generated: (1) (file-mode-spec/warning) Error in File mode specification: Wrong type argument: fixnump, nil Backtrace follows: backtrace(nil t) # bind (standard-output standard-output handler-arg-name) backtrace-in-condition-handler-eliminating-handler(call-trapping-errors-Ldc9FC5Hr) # bind (errstr call-trapping-errors-Ldc9FC5Hr) #<compiled-function (from "/home/abuild/rpmbuild/BUILD/xemacs-21.5.31/lisp/files.elc") (call-trapping-errors-Ldc9FC5Hr) "...(17)" [call-trapping-errors-Ldc9FC5Hr errstr error-message-string lwarn file-mode-spec warning "Error in %s: %s\n\nBacktrace follows:\n\n%s" "File mode specification" backtrace-in-condition-handler-eliminating-handler] 8 0x7e9>((wrong-type-argument fixnump nil)) # bind (v) byte-code("..." [v "$Revision$" string-match ":\\s *\$[0-9.]+\$" 1] 3) (defvar cperl-version (byte-code "ÁÂÃ\"ÄÄO)" [v "$Revision$" string-match ":\\s *\$[0-9.]+\$" 1] 3) ("/usr/share/xemacs/xemacs-packages/lisp/perl-modes/cperl-mode.elc" . 192444)) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) load-internal("cperl-mode" nil nil nil binary) # bind (handler path nosuffix nomessage noerror filename) load("cperl-mode" nil nil nil) # (unwind-protect ...) cperl-mode() # bind (alist mode name keep-going) # (unwind-protect ...) # bind (just-from-file-name) set-auto-mode() #<compiled-function (from "/home/abuild/rpmbuild/BUILD/xemacs-21.5.31/lisp/files.elc") nil "...(5)" [set-auto-mode t] 1 0x7ea>() # (unwind-protect ...) call-with-condition-handler(#<compiled-function (from "/home/abuild/rpmbuild/BUILD/xemacs-21.5.31/lisp/files.elc") (call-trapping-errors-Ldc9FC5Hr) "...(17)" [call-trapping-errors-Ldc9FC5Hr errstr error-message-string lwarn file-mode-spec warning "Error in %s: %s\n\nBacktrace follows:\n\n%s" "File mode specification" backtrace-in-condition-handler-eliminating-handler] 8 0x7e9> #<compiled-function (from "/home/abuild/rpmbuild/BUILD/xemacs-21.5.31/lisp/files.elc") nil "...(5)" [set-auto-mode t] 1 0x7ea>) # (condition-case ... . ((error))) # bind (find-file) normal-mode(t) # bind (nomodes after-find-file-from-revert-buffer noauto warn error) after-find-file(nil t) # (unwind-protect ...) # bind (inhibit-read-only error number truename rawfile nowarn filename buf) find-file-noselect-1(#<buffer "KIWIXMLPXEDeployData.pm"> "/home/rjschwei/work/kiwi_dev/kiwi/modules/KIWIXMLPXEDeployData.pm" nil nil "/home/rjschwei/work/kiwi_dev/kiwi/modules/KIWIXMLPXEDeployData.pm" (141365458 2051)) byte-code("..." [number truename rawfile nowarn filename buf set-buffer-major-mode find-file-noselect-1] 7) # (condition-case ... . ((t (byte-code "Â!Ã @ A\"" [buf data kill-buffer signal] 3)))) # bind (number truename buf wildcards rawfile nowarn filename) find-file-noselect("/home/rjschwei/work/kiwi_dev/kiwi/modules/KIWIXMLPXEDeployData.pm" nil nil nil) # bind (coding-system-for-read wildcards codesys filename) find-file("/home/rjschwei/work/kiwi_dev/kiwi/modules/KIWIXMLPXEDeployData.pm") # bind (dir file-count line end-of-options file-p arg tem) command-line-1() # bind (command-line-args-left) command-line() # (condition-case ... . ((t (byte-code " Â" [error-data data nil] 1)))) # bind (error-data) normal-top-level() # (condition-case ... . error) # (catch top-level ...) -- 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 15

[Bug 725090] New: ktimetracker: totally broken
by bugzilla_noreply＠novell.com 15 Oct '12

15 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=725090 https://bugzilla.novell.com/show_bug.cgi?id=725090#c0 Summary: ktimetracker: totally broken Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: suse-beta(a)cboltz.de QAContact: qa(a)suse.de Found By: --- Blocker: --- (Factory, last updated yesterday, ktimetracker-4.7.2-1.3.x86_64) When I try to start ktimetracker, I get the following error dialog: Fehler - KDE-Zeitplaner Die Komponente für den KDE-Zeitplaner kann nicht erstellt werden. translated: Error - KDE timetracker The component for the KDE timetracker could not be created. Then the main window opens, but it is completely empty and useless. The konsole output is: # ktimetracker Object::connect: No such slot TimetrackerWidget::updateTabs() Object::connect: No such slot ktimetrackerpart::keyBindings() Object::connect: (sender name: 'options_configure_keybinding') BTW: The title "Zeitplaner" sounds like a mistranslation - the better word would be "Zeiterfassung". -- 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 21

[Bug 781422] New: Running rciscsitarget stop does not stop ietd
by bugzilla_noreply＠novell.com 15 Oct '12

15 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=781422 https://bugzilla.novell.com/show_bug.cgi?id=781422#c0 Summary: Running rciscsitarget stop does not stop ietd Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: per(a)opensuse.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 Trying to stop ietd with "rciscsitarget" doesn't work, i.e. ietd is not stopped. I've tried a few different invocations, including running the commands from the init-script separately. a) rciscitarget - doesn't work. b) cd /etc/init.d; ./iscsitarget stop : # ./iscsitarget stop redirecting to systemctl Stopping iSCSI target service: failed c) the script does essentially: ietadm -op delete killproc -p $PIDFILE -TERM $DAEMON Doing those manually works. 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 8

[Bug 781687] New: DISPLAYMANAGER_KDM_THEME isn't updated in 12.1 to 12.2 upgrade causing generic KDM theme
by bugzilla_noreply＠novell.com 15 Oct '12

15 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=781687 https://bugzilla.novell.com/show_bug.cgi?id=781687#c0 Summary: DISPLAYMANAGER_KDM_THEME isn't updated in 12.1 to 12.2 upgrade causing generic KDM theme Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jdmulloy(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=506691) --> (http://bugzilla.novell.com/attachment.cgi?id=506691) Screenshot of the KDM theme that you get after upgrading to 12.2 User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.81 Safari/537.1 After upgrading my laptop from 12.1 to 12.2 via a USB stick with the DVD image on it, I got a KDM theme that was very nice, but generic. It turns out that from 12.1 to 12.2 the default theme was renamed from "SUSE" to "openSUSE". Changing the DISPLAYMANAGER_KDM_THEME parameter in /etc/sysconfig via YaST (/etc/sysconfig editor -> Desktop -> Display manager) from "SUSE" to "openSUSE" fixes the problem. The upgrade scripts should check to see if this value is set to "SUSE" and if it is, change it to "openSUSE". Reproducible: Always Steps to Reproduce: 1. Upgrade 12.1 to 12.2 with the DVD installer (Possibly happens with other upgrade procedures) 2. 3. Actual Results: KDM has generic theme Expected Results: KDM has nice new openSUSE Theme -- 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 7

[Bug 783288] New: KDE: Grub2 integration does not work if grub2 uses submenus
by bugzilla_noreply＠novell.com 15 Oct '12

15 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=783288 https://bugzilla.novell.com/show_bug.cgi?id=783288#c0 Summary: KDE: Grub2 integration does not work if grub2 uses submenus Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: wbauer(a)tmo.at QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux) KHTML/4.9.2 (like Gecko) Konqueror/4.9 SUSE KDE 4.8.4/4.8.5 doesn't support submenus in grub2. But the standard grub2 bootmenu in openSUSE 12.2 contains a submenu "Advanced Options..." So, if you select a bootmenu entry in the restart dialog except the first one, the wrong entry gets booted. This is especially annoying if you have a dual boot system. See upstream bug: https://bugs.kde.org/show_bug.cgi?id=297209 This has been fixed upstream after KDE 4.8.5 was released. The relevant commit for the 4.8 branch can be found here: http://commits.kde.org/kde-workspace/b8e506743429fa28694b3565a231e48e52cfa6… Would it be possible to provide an online update for this? 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 765948] AUDIT-0: qemu and kvm setuid bridge helper setuid binary
by bugzilla_noreply＠novell.com 15 Oct '12

15 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=765948 https://bugzilla.novell.com/show_bug.cgi?id=765948#c12 --- Comment #12 from Sebastian Krahmer <krahmer(a)suse.com> 2012-10-15 08:50:17 UTC --- Ok, in particular dropping the privileges after doing the prvileged operation is necessary. -- 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 783419] New: partprobe does not do anything if no partition table is found on device
by bugzilla_noreply＠novell.com 15 Oct '12

15 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=783419 https://bugzilla.novell.com/show_bug.cgi?id=783419#c0 Summary: partprobe does not do anything if no partition table is found on device Classification: openSUSE Product: openSUSE 12.2 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: jnelson-suse(a)jamponi.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 I had a pair of devices (/dev/sdc and /dev/sdd) that *had* partitions on them, but then I zeroed the disk with dd. partprobe, however, did not change the listing of the partitions in /dev -- despite /dev/sdc and /dev/sdd not having any. I had to use cfdisk to make an empty partition table and *then* it worked. partprobe should report *zero* partitions found if, in fact, there aren't even (in fact, when there is no partition table found at all). 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 3

[Bug 777891] New: packagekit: can't install fortune, zypper can.
by bugzilla_noreply＠novell.com 15 Oct '12

15 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=777891 https://bugzilla.novell.com/show_bug.cgi?id=777891#c0 Summary: packagekit: can't install fortune, zypper can. Classification: openSUSE Product: openSUSE 12.2 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: jnelson-suse(a)jamponi.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20100101 Firefox/13.0.1 jnelson@worklaptop:~> pkcon install fortune Simulating install [=========================] Waiting in queue [=========================] Starting [=========================] Refreshing software list [=========================] Querying [=========================] Resolving dependencies [=========================] Fatal error: fortune-1.99.1-2.1.4.i586 requires librecode.so.0, but this requirement cannot be provided jnelson@worklaptop:~> sudo zypper in fortune Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW package is going to be installed: fortune 1 new package to install. Overall download size: 1.4 MiB. After the operation, additional 4.3 MiB will be used. Continue? [y/n/?] (y): Retrieving package fortune-1.99.1-2.1.4.x86_64 (1/1), 1.4 MiB ( 4.3 MiB unpacked) Retrieving: fortune-1.99.1-2.1.4.x86_64.rpm .........................................................................................................................................[done (316.6 KiB/s)] Installing: fortune-1.99.1-2.1.4 ..................................................................................................................................................................[done] jnelson@worklaptop:~> sudo rpm -e fortune jnelson@worklaptop:~> pkcon install fortune Simulating install [=========================] Waiting in queue [=========================] Starting [=========================] Refreshing software list [=========================] Querying [=========================] Resolving dependencies [=========================] Fatal error: fortune-1.99.1-2.1.4.i586 requires librecode.so.0, but this requirement cannot be provided jnelson@worklaptop:~> NOTE: *please* add a "package management" Component to Bugzilla. 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 6

[Bug 770068] New: rusxmms patch for taglib is missing after update
by bugzilla_noreply＠novell.com 15 Oct '12

15 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=770068 https://bugzilla.novell.com/show_bug.cgi?id=770068#c0 Summary: rusxmms patch for taglib is missing after update Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: i586 OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: vy(a)samiznaetekogo.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20100101 Firefox/13.0 rusxmms patch for taglib, that was once accepted (https://features.opensuse.org/313273) is missing after taglib 1.7-8.7.1 update from Updates repository. Reproducible: Always Steps to Reproduce: 1. Install updated taglib 2. Compare decoded from non UTF-8 encoding cyrillic tags with ones decoded by taglib from home:tuoma repository. Actual Results: Cyrillic tags in non UTF-8 encoding displayed incorrectly Expected Results: Cyrillic tags in non UTF-8 encoding displayed correctly -- 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 4