May 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 757194] New: virt-manager should depend on python-gconf
by bugzilla_noreply＠novell.com 02 May '12

02 May '12

https://bugzilla.novell.com/show_bug.cgi?id=757194 https://bugzilla.novell.com/show_bug.cgi?id=757194#c0 Summary: virt-manager should depend on python-gconf Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: All OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jackhill(a)jackhill.us QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.7.2 Safari/534.34 See steps to reproduce Reproducible: Always Steps to Reproduce: 0) On a system without python-gconf installed 1) zypper install virt-manager 2) run virt-manager 3) opeserver the error: Error starting Virtual Machine Manager: No module named gconf Traceback (most recent call last): File "/usr/share/virt-manager/virt-manager.py", line 383, in <module> main() File "/usr/share/virt-manager/virt-manager.py", line 313, in main import virtManager.config File "/usr/share/virt-manager/virtManager/config.py", line 24, in <module> import gconf ImportError: No module named gconf 4) zypper install python-gconf 5) run virt-manager again and observe everything working -- 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 755021] New: Installation with autoyast fails if lvm volume group exists on drive
by bugzilla_noreply＠novell.com 02 May '12

02 May '12

https://bugzilla.novell.com/show_bug.cgi?id=755021 https://bugzilla.novell.com/show_bug.cgi?id=755021#c0 Summary: Installation with autoyast fails if lvm volume group exists on drive Classification: openSUSE Product: openSUSE 12.2 Version: Milestone 2 Platform: x86-64 OS/Version: SLES 11 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: frank(a)samaxi.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 When I try to install SLES 11 SP2 via autoyast on a machine which has a configured lvm Volume Group, the Installation process hangs while preparing disks I found this error on SLES 11 SP 2 but as far as i have seen it`s a general problem in libstorage (and maybe affects other suse versions). Reproducible: Always Steps to Reproduce: 1. create lvm volume group on hdd 2. start installation with autoyast 3. "vgremove" will hang. Actual Results: ############################################################################### 2012-03-30 17:26:15 <1> 10.0.7.245(3659) [libstorage] SystemCmd.cc(SystemCmd):49 constructor SystemCmd:"/sbin/vgremove 'system'" 2012-03-30 17:26:15 <1> 10.0.7.245(3659) [libstorage] SystemCmd.cc(execute):93 SystemCmd Executing:"/sbin/vgremove 'system'" 2012-03-30 17:26:15 <1> 10.0.7.245(3659) [libstorage] SystemCmd.cc(addLine):595 Adding Line 1 "Do you really want to remove volume group "system" containing 1 logical volumes? [y/n]: " 2012-03-30 17:26:15 <1> 10.0.7.245(3659) [libstorage] SystemCmd.cc(getUntilEOF):561 pid:5899 added lines:1 stderr:false ############################################################################### Expected Results: Proceed without Installation I checked out git://gitorious.org/opensuse/libstorage.git and think the following diff should fix the problem, but i`m not sure, as i had no chance to test it: diff --git a/storage/LvmVg.cc b/storage/LvmVg.cc index 3365dff..a435756 100644 --- a/storage/LvmVg.cc +++ b/storage/LvmVg.cc @@ -1261,7 +1261,7 @@ LvmVg::doRemoveVg() activate(true); getStorage()->showInfoCb(removeText(true),silent); checkConsistency(); - string cmd = VGREMOVEBIN " " + quote(name()); + string cmd = VGREMOVEBIN " -f " + quote(name()); SystemCmd c( cmd ); if( c.retcode()!=0 ) { -- 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 13

[Bug 754649] New: Unable to install domU on Xen using autoyast with simple partition layout
by bugzilla_noreply＠novell.com 02 May '12

02 May '12

https://bugzilla.novell.com/show_bug.cgi?id=754649 https://bugzilla.novell.com/show_bug.cgi?id=754649#c0 Summary: Unable to install domU on Xen using autoyast with simple partition layout Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: All OS/Version: SLES 11 Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST AssignedTo: ug(a)suse.com ReportedBy: nicolas.michaux(a)c2d.be QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=483828) --> (http://bugzilla.novell.com/attachment.cgi?id=483828) Patch to return 4 MaxPrimary partitions in Partitions.ycp User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.83 Safari/535.11 We used to install domU on Xen using autoyast with this simple partition layout : - /dev/xenvg/machine-root -> xvda1 (root) - /dev/xenvg/machine-swap -> xvda2 (swap) This has always worked fine since SLES10 until SLES11 SP1. With SLES11 SP2, it isn't working anymore, Yast stops with error "Error while configuring partitions". By comparing the logs between SLES11 SP1 and SLES11 SP2, it seems that module Partitions found 0 MaxPrimary partitions in SLES11 SP2 (it finds 4 MaxPrimary partitions with SLES11 SP1). By looking at the code, we can see that SLES11 SP1 was never returning 0 MaxPrimary partitions. The same problem seems to exist in latest trunk of autoyast in Opensuse. It is a very special partitioning scheme, as there is no real disk, only partitions, but it is very handy in virtual environment to work directly with partitions without using disk. Reproducible: Always Steps to Reproduce: 1. Configure an autoyast xml to use 2 partitions : <partitioning config:type="list"> <drive> <device>/dev/xvda</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>max</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> 2. Launch an autoyast installation of a domU in Xen environment with 2 LVM as partitions (xvda1 as root and xvda2 as swap) : disk=[ 'phy:/dev/xenvg/test-root,xvda1,w', 'phy:/dev/xenvg/test-swap,xvda2,w' ] Actual Results: Yast reports an error "Error while configuring partitions" Expected Results: Yast should format /dev/xvda1 with ext3 and use it as root and format /dev/xvda2 as swap and use it as swap. It works as expected with the patch attached. -- 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 731753] New: yast2 disk (expert partitioner) cannot resize partitions that have btrfs
by bugzilla_noreply＠novell.com 02 May '12

02 May '12

https://bugzilla.novell.com/show_bug.cgi?id=731753 https://bugzilla.novell.com/show_bug.cgi?id=731753#c0 Summary: yast2 disk (expert partitioner) cannot resize partitions that have btrfs Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ben.kevan(a)bio-rad.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.8 (KHTML, like Gecko) Chrome/17.0.937.0 Safari/535.8 SUSE/17.0.937.0 I went to resize a partition that had a btrfs filesystem after doing a btrfs fi resize -2G /home on my home partition, only to find out that YaST doesn't yet support resizing of partitions with BTRFS. I get the error: "You cannot resize the selected partition because the file system on this partition does not support resizing." (which is obviously wrong). Reproducible: Always Steps to Reproduce: 1.btrfs fi resize -2G /somepartition 2./sbin/yast2 disk (try to resize the actual partition) 3. Actual Results: Error: "You cannot resize the selected partition because the file system on this partition does not support resizing." (which is obviously wrong). Expected Results: Allow resize of the partition. -- 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

[Bug 759868] New: rtkit-daemon: Failed to make ourselves RT: Operation not permitted
by bugzilla_noreply＠novell.com 02 May '12

02 May '12

https://bugzilla.novell.com/show_bug.cgi?id=759868 https://bugzilla.novell.com/show_bug.cgi?id=759868#c0 Summary: rtkit-daemon: Failed to make ourselves RT: Operation not permitted Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: 64bit OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: johannes.eckhardt(a)ihs.ac.at QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20100101 Firefox/11.0 I frequently find the following in my /var/log/warn: rtkit-daemon: Failed to make ourselves RT: Operation not permitted What does that mean. Can this be the reason for poor sound quality in VMware Workstation? Reproducible: Couldn't Reproduce 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 2

[Bug 753784] New: YaST help dialogs appear fullscreen
by bugzilla_noreply＠novell.com 02 May '12

02 May '12

https://bugzilla.novell.com/show_bug.cgi?id=753784 https://bugzilla.novell.com/show_bug.cgi?id=753784#c0 Summary: YaST help dialogs appear fullscreen Classification: openSUSE Product: openSUSE 12.2 Version: Milestone 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: tgoettlicher(a)suse.com ReportedBy: aschnell(a)suse.com QAContact: jsrain(a)suse.com Found By: Development Blocker: --- YaST help dialogs appear fullscreen. They also lack the search field. -- 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 758408] VUL-0: MozillaFirefox 12 / 10.0.4esr etc
by bugzilla_noreply＠novell.com 02 May '12

02 May '12

https://bugzilla.novell.com/show_bug.cgi?id=758408 https://bugzilla.novell.com/show_bug.cgi?id=758408#c20 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:running:46967:importa |maint:running:46967:importa |nt |nt | |maint:released:sle11-sp1:47 | |035 --- Comment #20 from Swamp Workflow Management <swamp(a)suse.de> 2012-05-02 13:46:20 UTC --- Update released for: MozillaFirefox, MozillaFirefox-branding-upstream, MozillaFirefox-debuginfo, MozillaFirefox-debugsource, MozillaFirefox-devel, MozillaFirefox-translations, libfreebl3, libfreebl3-32bit, libfreebl3-x86, mozilla-nss, mozilla-nss-32bit, mozilla-nss-debuginfo, mozilla-nss-debuginfo-32bit, mozilla-nss-debuginfo-x86, mozilla-nss-debugsource, mozilla-nss-devel, mozilla-nss-tools, mozilla-nss-x86 Products: SLE-DEBUGINFO 11-SP1 (i386, ia64, ppc64, s390x, x86_64) SLE-DESKTOP 11-SP1 (i386, x86_64) SLE-DESKTOP 11-SP1-FOR-SP2 (i386, x86_64) SLE-SDK 11-SP1 (i386, ia64, ppc64, s390x, x86_64) SLE-SDK 11-SP1-FOR-SP2 (i386, ia64, ppc64, s390x, x86_64) SLE-SERVER 11-SP1 (i386, ia64, ppc64, s390x, x86_64) SLE-SERVER 11-SP1-FOR-SP2 (i386, ia64, ppc64, s390x, x86_64) SLE-SERVER 11-SP1-TERADATA (x86_64) SLES4VMWARE 11-SP1 (i386, x86_64) -- 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 758086] New: check_ntp_peer buffer overflow
by bugzilla_noreply＠novell.com 02 May '12

02 May '12

https://bugzilla.novell.com/show_bug.cgi?id=758086 https://bugzilla.novell.com/show_bug.cgi?id=758086#c0 Summary: check_ntp_peer buffer overflow Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: SLES 11 Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: kyle(a)lodge.glasgownet.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.162 Safari/535.19 check_ntp_peer suffers from a buffer overflow that has already been fixed upstream. The bug is still present in SLES 11.1 however. Reproducible: Always Steps to Reproduce: WMSR0007:/etc/nagios # /usr/lib/nagios/plugins/check_ntp_peer -H 10.240.64.39 -w 2 -c 3 *** buffer overflow detected ***: /usr/lib/nagios/plugins/check_ntp_peer terminated ======= Backtrace: ========= /lib64/libc.so.6(__fortify_fail+0x37)[0x7f0c02a46677] /lib64/libc.so.6(+0xe9310)[0x7f0c02a44310] /lib64/libc.so.6(__read_chk+0x28)[0x7f0c02a44888] /usr/lib/nagios/plugins/check_ntp_peer[0x402350] /usr/lib/nagios/plugins/check_ntp_peer[0x402df8] /lib64/libc.so.6(__libc_start_main+0xe6)[0x7f0c02979bc6] /usr/lib/nagios/plugins/check_ntp_peer[0x401469] ======= Memory map: ======== 00400000-00408000 r-xp 00000000 08:02 2926274 /usr/lib/nagios/plugins/check_ntp_peer 00607000-00608000 r--p 00007000 08:02 2926274 /usr/lib/nagios/plugins/check_ntp_peer 00608000-00609000 rw-p 00008000 08:02 2926274 /usr/lib/nagios/plugins/check_ntp_peer 00609000-0062a000 rw-p 00000000 00:00 0 [heap] 7f0c02744000-7f0c0275a000 r-xp 00000000 08:02 82038 /lib64/libgcc_s.so.1 7f0c0275a000-7f0c02959000 ---p 00016000 08:02 82038 /lib64/libgcc_s.so.1 7f0c02959000-7f0c0295a000 r--p 00015000 08:02 82038 /lib64/libgcc_s.so.1 7f0c0295a000-7f0c0295b000 rw-p 00016000 08:02 82038 /lib64/libgcc_s.so.1 7f0c0295b000-7f0c02ab0000 r-xp 00000000 08:02 81928 /lib64/libc-2.11.1.so 7f0c02ab0000-7f0c02caf000 ---p 00155000 08:02 81928 /lib64/libc-2.11.1.so 7f0c02caf000-7f0c02cb3000 r--p 00154000 08:02 81928 /lib64/libc-2.11.1.so 7f0c02cb3000-7f0c02cb4000 rw-p 00158000 08:02 81928 /lib64/libc-2.11.1.so 7f0c02cb4000-7f0c02cb9000 rw-p 00000000 00:00 0 7f0c02cb9000-7f0c02cbb000 r-xp 00000000 08:02 81934 /lib64/libdl-2.11.1.so 7f0c02cbb000-7f0c02ebb000 ---p 00002000 08:02 81934 /lib64/libdl-2.11.1.so 7f0c02ebb000-7f0c02ebc000 r--p 00002000 08:02 81934 /lib64/libdl-2.11.1.so 7f0c02ebc000-7f0c02ebd000 rw-p 00003000 08:02 81934 /lib64/libdl-2.11.1.so 7f0c02ebd000-7f0c02f12000 r-xp 00000000 08:02 81936 /lib64/libm-2.11.1.so 7f0c02f12000-7f0c03111000 ---p 00055000 08:02 81936 /lib64/libm-2.11.1.so 7f0c03111000-7f0c03112000 r--p 00054000 08:02 81936 /lib64/libm-2.11.1.so 7f0c03112000-7f0c03113000 rw-p 00055000 08:02 81936 /lib64/libm-2.11.1.so 7f0c03113000-7f0c03126000 r-xp 00000000 08:02 81956 /lib64/libresolv-2.11.1.so 7f0c03126000-7f0c03326000 ---p 00013000 08:02 81956 /lib64/libresolv-2.11.1.so 7f0c03326000-7f0c03327000 r--p 00013000 08:02 81956 /lib64/libresolv-2.11.1.so 7f0c03327000-7f0c03328000 rw-p 00014000 08:02 81956 /lib64/libresolv-2.11.1.so 7f0c03328000-7f0c0332a000 rw-p 00000000 00:00 0 7f0c0332a000-7f0c0333f000 r-xp 00000000 08:02 81939 /lib64/libnsl-2.11.1.so 7f0c0333f000-7f0c0353e000 ---p 00015000 08:02 81939 /lib64/libnsl-2.11.1.so 7f0c0353e000-7f0c0353f000 r--p 00014000 08:02 81939 /lib64/libnsl-2.11.1.so 7f0c0353f000-7f0c03540000 rw-p 00015000 08:02 81939 /lib64/libnsl-2.11.1.so 7f0c03540000-7f0c03542000 rw-p 00000000 00:00 0 7f0c03542000-7f0c03561000 r-xp 00000000 08:02 82193 /lib64/ld-2.11.1.so 7f0c035d2000-7f0c03611000 r--p 00000000 08:02 2959799 /usr/lib/locale/en_GB.utf8/LC_CTYPE 7f0c03611000-7f0c0372e000 r--p 00000000 08:02 2959800 /usr/lib/locale/en_GB.utf8/LC_COLLATE 7f0c0372e000-7f0c03732000 rw-p 00000000 00:00 0 7f0c0374e000-7f0c0374f000 r--p 00000000 08:02 2957346 /usr/lib/locale/en_GB.utf8/LC_NUMERIC 7f0c0374f000-7f0c03750000 r--p 00000000 08:02 2942566 /usr/lib/locale/en_GB.utf8/LC_TIME 7f0c03750000-7f0c03751000 r--p 00000000 08:02 2942612 /usr/lib/locale/en_GB.utf8/LC_MONETARY 7f0c03751000-7f0c03752000 r--p 00000000 08:02 2950253 /usr/lib/locale/en_GB.utf8/LC_MESSAGES/SYS_LC_MESSAGES 7f0c03752000-7f0c03753000 r--p 00000000 08:02 2957351 /usr/lib/locale/en_GB.utf8/LC_PAPER 7f0c03753000-7f0c03754000 r--p 00000000 08:02 2950198 /usr/lib/locale/en_GB.utf8/LC_NAME 7f0c03754000-7f0c03755000 r--p 00000000 08:02 2942548 /usr/lib/locale/en_GB.utf8/LC_ADDRESS 7f0c03755000-7f0c03756000 r--p 00000000 08:02 2942611 /usr/lib/locale/en_GB.utf8/LC_TELEPHONE 7f0c03756000-7f0c03757000 r--p 00000000 08:02 2959798 /usr/lib/locale/en_GB.utf8/LC_MEASUREMENT 7f0c03757000-7f0c0375e000 r--s 00000000 08:02 2828759 /usr/lib64/gconv/gconv-modules.cache 7f0c0375e000-7f0c0375f000 r--p 00000000 08:02 2941297 /usr/lib/locale/en_GB.utf8/LC_IDENTIFICATION 7f0c0375f000-7f0c03760000 rw-p 00000000 00:00 0 7f0c03760000-7f0c03761000 r--p 0001e000 08:02 82193 /lib64/ld-2.11.1.so 7f0c03761000-7f0c03762000 rw-p 0001f000 08:02 82193 /lib64/ld-2.11.1.so 7f0c03762000-7f0c03763000 rw-p 00000000 00:00 0 7fff81406000-7fff8141b000 rw-p 00000000 00:00 0 [stack] 7fff815ff000-7fff81600000 r-xp 00000000 00:00 0 [vdso] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall] Aborted WMSR0007:/etc/nagios # WMSR0007:/etc/nagios # cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = 1 WMSR0007:/etc/nagios # uname -a Linux WMSR0007 2.6.32.54-0.3-default #1 SMP 2012-01-27 17:38:56 +0100 x86_64 x86_64 x86_64 GNU/Linux WMSR0007:/etc/nagios # rpm -qf /usr/lib/nagios/plugins/check_ntp_peer nagios-plugins-1.4.13-1.35 WMSR0007:/etc/nagios # Actual Results: execute /usr/lib/nagios/plugins/check_ntp_peer -H pool.ntp.org -w 2 -c 3 buffer overflow as described above Expected Results: NTP OK: Offset 0.00071 secs|offset=0.000710s;2.000000;3.000000; -- 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 747802] Yast2 dialogs are smaller than expected
by bugzilla_noreply＠novell.com 02 May '12

02 May '12

https://bugzilla.novell.com/show_bug.cgi?id=747802 https://bugzilla.novell.com/show_bug.cgi?id=747802#c9 Thomas Göttlicher <tgoettlicher(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |tgoettlicher(a)suse.com Resolution| |DUPLICATE --- Comment #9 from Thomas Göttlicher <tgoettlicher(a)suse.com> 2012-05-02 13:33:24 UTC --- duplicate of bug 722053 *** This bug has been marked as a duplicate of bug 722053 *** http://bugzilla.novell.com/show_bug.cgi?id=722053 -- 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 743252] New: Dolphin update results in Wrong Digest
by bugzilla_noreply＠novell.com 02 May '12

02 May '12

https://bugzilla.novell.com/show_bug.cgi?id=743252 https://bugzilla.novell.com/show_bug.cgi?id=743252#c0 Summary: Dolphin update results in Wrong Digest Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: 64bit OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jmcdaniel3(a)austin.rr.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 Wrong Digest for Dolphin: The Expected checksum of file /var/cache/zypp/packages/openSUSE:_12.1:_Update/x86_64/doplphin-4.7.2-4.4.1.x86_64.rpm is 4a73848e62be00c5a04fdfbdeaebe7e7decdb125173de754a65675a6af284d25, but the current checksum is 903b3243f0e3012e5dc9dd01c26b6f618fcb808d65394df97e6724002ce70e4e. This means that the file has been changed by accident or by an attacker since the repository creator signed it. Using it is a big risk for the integrity and security of your system. Reproducible: Always Steps to Reproduce: 1.Open YaST / Software / Software Management 2. Search on dolphin 3. Attempt to update your version (when using KDE) Actual Results: Update fails due to a Wrong Digest error. Expected Results: File should update to the most recent version. This was going on in openSUSE 11.4 as well, but today it seems to be fixed. -- 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