April 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 383939] Package GNU ddrescue
by bugzilla_noreply＠novell.com 04 Apr '11

04 Apr '11

https://bugzilla.novell.com/show_bug.cgi?id=383939 https://bugzilla.novell.com/show_bug.cgi?id=383939#c5 Bruno Friedmann <bruno(a)ioda-net.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED CC| |jengelh(a)medozas.de Platform|Other |All AssignedTo|bnc-team-screening(a)forge.pr |jengelh(a)medozas.de |ovo.novell.com | OS/Version|Other |openSUSE 11.4 --- Comment #5 from Bruno Friedmann <bruno(a)ioda-net.ch> 2011-04-04 16:48:05 UTC --- David I was really refering to gnu-ddrescue We already have both, and more up-to-date http://download.opensuse.org/distribution/11.4/repo/oss/suse/i586/dd_rescue… and http://download.opensuse.org/distribution/11.4/repo/oss/suse/i586/ddrescue-… which are absolutely different and are findable in zypper zypper se -s rescue Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+-----------+---------+-----------------+------+----------- | dd_rescue | package | 1.23_0.0.6-3.4 | i586 | repo-oss i | ddrescue | package | 1.14_0.0.6-77.1 | i586 | repo-oss zypper info dd_rescue Loading repository data... Reading installed packages... Information for package dd_rescue: Repository: repo-oss Name: dd_rescue Version: 1.23_0.0.6-3.4 Arch: i586 Vendor: openSUSE Installed: No Status: not installed Installed Size: 87.0 KiB Summary: Data Copying in the Presence of I/O Errors Description: dd_rescue helps when nothing else can: your disk has crashed and you try to copy it over to another one. While standard Unix tools like cp, cat, and dd wail "abort" on every I/O error, dd_rescue does not. Authors: -------- Kurt Garloff <garloff(a)suse.de> and source linked to http://www.garloff.de/kurt/linux/ddrescue/dd_rescue-1.23.tar.gz zypper info ddrescue Loading repository data... Reading installed packages... Information for package ddrescue: Repository: @System Name: ddrescue Version: 1.14_0.0.6-77.1 Arch: i586 Vendor: openSUSE Installed: Yes Status: up-to-date Installed Size: 81.0 KiB Summary: Data Copying in the Presence of I/O Errors Description: dd_rescue helps when nothing else can: your disk has crashed and you try to copy it over to another one. While standard Unix tools like cp, cat, and dd wail "abort" on every I/O error, dd_rescue does not. with source linked to http://gd.tuwien.ac.at/gnu/gnusrc/ddrescue/ddrescue-1.14.tar.lz rpm -q --changelog ddrescue * Sun Sep 19 2010 jengelh(a)medozas.de - Use %_smp_mflags for building - Ignore EINVAL on fsync. Fixes bnc#517947. So my best bet is contacting last packager of ddrescue, or create him a good description for the package to be included in the spec, and not a copy/paste of the dd_rescue one like there's several good build in OBS home users http://software.opensuse.org/search?q=ddrescue&baseproject=openSUSE%3A11.4&… Time to merge all these efforts. :-) -- 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 517967] New: Firefox 3.5 (stable) crashes with 'BadWindow (invalid Window parameter)'
by bugzilla_noreply＠novell.com 04 Apr '11

04 Apr '11

http://bugzilla.novell.com/show_bug.cgi?id=517967 Summary: Firefox 3.5 (stable) crashes with 'BadWindow (invalid Window parameter)' Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com ReportedBy: w.flamme(a)web.de QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.20) Gecko/20081217 Firefox/2.0.0.20 Hi, on both my office and my home box I use openSUSE 11.1 x86_64, on both I updated Firefox to the latest version from BuildService's mozilla repo today (mozilla-xulrunner191-1.9.1.0-2.1.x86_64.rpm, mozilla-xulrunner191-translations-1.9.1.0-2.1.x86_64.rpm, MozillaFirefox-3.5.0-2.1.x86_64.rpm, MozillaFirefox-branding-openSUSE-3.5-1.2.x86_64.rpm, and MozillaFirefox-translations-3.5.0-2.1.x86_64.rpm). On both boxes I use KDE 3.5.10. I started FF manually (from an console window) by entering "/usr/bin/firefox -P". On both boxes I get the "Choose Profile" box, I create an empty one, select it, and then the application crashes with the output: ---snip--- The program 'firefox' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 3918 error_code 3 request_code 20 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) ---pins--- Seems to be a hard error... Regards, Werner Reproducible: Always Steps to Reproduce: 1. install the given rpms 2. /usr/bin/firefox -P 3. select an empty profile Actual Results: The program 'firefox' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 3918 error_code 3 request_code 20 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Expected Results: The software should have started, not crashed. Luckily, I still have a 32 bit FF 2 in /usr/local ;-) - just in case I need Java... -- 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 680450] New: /proc/net/nf_conntrack without Line feeds
by bugzilla_noreply＠novell.com 04 Apr '11

04 Apr '11

https://bugzilla.novell.com/show_bug.cgi?id=680450 https://bugzilla.novell.com/show_bug.cgi?id=680450#c0 Summary: /proc/net/nf_conntrack without Line feeds Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: diego.ercolani(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b12) Gecko/20110222 Firefox/4.0b12 With OpenSuSe 11.4 (kernel kernel-default-2.6.37.1-1.2.2.x86_64) if you issue the command: cat /proc/net/nf_conntrack you get a single line output like this: ipv4 2 tcp 6 431989 ESTABLISHED src=192.168.10.218 dst=74.125.232.150 sport=56823 dport=443 src=74.125.232.150 dst=192.168.10.218 sport=443 dport=56823 [ASSURED] mark=0 ipv4 2 tcp 6 430540 ESTABLISHED src=192.168.10.218 dst=192.168.10.220 sport=59640 dport=443 src=192.168.10.220 dst=192.168.10.218 sport=443 dport=59640 [ASSURED] mark=0 ipv4 2 tcp 6 431951 ESTABLISHED src=192.168.10.218 dst=66.220.151.69 sport=38203 dport=80 src=66.220.151.69 dst=192.168.10.218 sport=80 dport=38203 [ASSURED] mark=0 ipv4 2 tcp 6 431968 ESTABLISHED src=192.168.10.218 dst=192.168.10.61 sport=57049 dport=445 src=192.168.10.61 dst=192.168.10.218 sport=445 dport=57049 [ASSURED] mark=0 ipv4 2 tcp 6 431833 ESTABLISHED src=192.168.10.218 dst=192.168.10.220 sport=60180 dport=443 src=192.168.10.220 dst=192.168.10.218 sport=443 dport=60180 [ASSURED] mark=0 ipv4 2 tcp 6 431983 ESTABLISHED src=192.168.10.218 dst=74.125.232.151 sport=44137 dport=443 src=74.125.232.151 dst=192.168.10.218 sport=443 dport=44137 [ASSURED] mark=0 with conntrack-tools-0.9.15-2.1.x86_64 installed in the same situation you can't get any output: conntrack -L conntrack v0.9.15 (conntrack-tools): 0 flow entries have been shown. And I think the conntrack doesn't work, as I added a source nat rule with iptables anche the returning packet isn't "denatted" so question is sended but answer doesn't come back to the client. 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 1

[Bug 682678] New: tar-1.25 seriously broken - produces *empty* backups with amanda
by bugzilla_noreply＠novell.com 04 Apr '11

04 Apr '11

https://bugzilla.novell.com/show_bug.cgi?id=682678 https://bugzilla.novell.com/show_bug.cgi?id=682678#c0 Summary: tar-1.25 seriously broken - produces *empty* backups with amanda Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i686 OS/Version: openSUSE 11.4 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andreas.bolsch(a)alumni.tu-berlin.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0.0) Gecko/20100101 Firefox/4.0 After upgrade from 11.3 (tar 1.23) to 11.4 (tar 1.25) level 0 backups produced by amanda are empty (execpt for top level directory). Amanda configuration wasn't touched at all. This is a known problem: http://wiki.zmanda.com/index.php/FAQ:What_versions_of_GNU_Tar_are_Amanda-co… (contains a link to detailed description) The options '--listed-incremental' '--one-file-system' seem to cause trouble. Reproducible: Always Actual Results: see 'Details' Expected Results: see 'Details' Release notes of tar-1.26 state explicitly that this bug had been fixed. I've just replaced the original sources (1.25) by those of 1.26 and rebuild the package with slightly adjusted specfile of tar-1.25-6.1. Works as expected, so the bug has gone indeed with 1.26. -- 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 9

[Bug 506066] New: "nphelix.so: cannot open shared object file" errors from NSPlugin Viewer
by bugzilla_noreply＠novell.com 04 Apr '11

04 Apr '11

http://bugzilla.novell.com/show_bug.cgi?id=506066 Summary: "nphelix.so: cannot open shared object file" errors from NSPlugin Viewer Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com ReportedBy: psychonaut(a)nothingisreal.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.21) Gecko/20090410 SUSE/1.1.16-1.5 SeaMonkey/1.1.16 Both Firefox and SeaMonkey complain about not being able to open nphelix.so. Reproducible: Always Steps to Reproduce: 1. Launch Firefox or SeaMonkey from the command line. 2. Visit about:plugins Actual Results: 3. The following is output to the console: [psy@weasel:~]$ firefox *** nss-shared-helper: Shared database disabled (set NSS_USE_SHARED_DB to enable). *** NSPlugin Viewer *** ERROR: /usr/lib/browser-plugins/nphelix.so: cannot open shared object file: No such file or directory [psy@weasel:"]$ seamonkey *** NSPlugin Viewer *** ERROR: /usr/lib/browser-plugins/nphelix.so: cannot open shared object file: No such file or directory [psy@weasel:/etc/alternatives]$ According to locate, the file nphelix.so doesn't exist anywhere on my system. The command "rpm -qail | fgrep helix" also doesn't return anything relevant. This bug doesn't seem to have any detrimental effect, except that the Mozilla folks are refusing to accept bug reports from afflicted browsers. They always say, "Well, maybe your problem is caused by this nphelix.so message! Fix that first!" -- 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 4

[Bug 678389] New: hdspmixer crashing with RME Multiface
by bugzilla_noreply＠novell.com 04 Apr '11

04 Apr '11

https://bugzilla.novell.com/show_bug.cgi?id=678389 https://bugzilla.novell.com/show_bug.cgi?id=678389#c0 Summary: hdspmixer crashing with RME Multiface Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai(a)novell.com ReportedBy: georg.rudolph(a)schwaben.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13 openSuse 11.4 carries the alsa-tools-1.0.24 Release, which holds un incomplete rework of hdspmixer. In upstream in alsa-tools this got recently fixed. Could hdspmixer from alsa-tools head be incorporated into openSuse 11.4? hdspmixer was already broken in openSuse 11.3, so it would be nice to have it okay out of the box in 11.4 again. In openSuse hdspmixer is found in the package alsa-tools-gui. I testet this on openSuse 11.4 RC2 and 11.3. It's both on x86 and x86-64. 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 8

[Bug 681048] New: compcache: fix init script to work with 11.4
by bugzilla_noreply＠novell.com 04 Apr '11

04 Apr '11

https://bugzilla.novell.com/show_bug.cgi?id=681048 https://bugzilla.novell.com/show_bug.cgi?id=681048#c0 Summary: compcache: fix init script to work with 11.4 Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: cyberorg(a)opensuse.org QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=420334) --> (http://bugzilla.novell.com/attachment.cgi?id=420334) get COMPCACHE_SIZE_KB if nothing is specified in config file User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0b12) Gecko/20110222 Firefox/4.0b12 /etc/init.d/boot.compcache requires COMPCACHE_SIZE_KB calculated 25% of available RAM if nothing is specified in /etc/sysconfig/compcache. patch attached. 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 11

[Bug 679975] New: Output volume can't keep value after reboot or poweroff/on
by bugzilla_noreply＠novell.com 04 Apr '11

04 Apr '11

https://bugzilla.novell.com/show_bug.cgi?id=679975 https://bugzilla.novell.com/show_bug.cgi?id=679975#c0 Summary: Output volume can't keep value after reboot or poweroff/on Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai(a)novell.com ReportedBy: ldai(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- if you adjust volume to met your requirement, after reboot or poweroff/on, the volume was reset to 100% by default. -- 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 17

[Bug 679170] New: shipped strongswan-4.5.0 has know bug
by bugzilla_noreply＠novell.com 04 Apr '11

04 Apr '11

https://bugzilla.novell.com/show_bug.cgi?id=679170 https://bugzilla.novell.com/show_bug.cgi?id=679170#c0 Summary: shipped strongswan-4.5.0 has know bug Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alex.wilms(a)adminguru.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b12) Gecko/20110222 Firefox/4.0b12 The shipped strongswan charon daemon crashes few seconds after after tunnel is established. This is a know bug and fixed in 4.5.1. URL to patch http://git.strongswan.org/strongswan.git/?p=strongswan.git;a=commitdiff_pla… The 4.5.1 Version from home:j-engel works. Reproducible: Always Steps to Reproduce: 1. create an IKEv2 Connection 2.fire up the tunnel 3.check /var/log/messages for: charon: 04[DMN] killing ourself, received critical signal ipsec_starter[11055]: charon has died -- restart scheduled (5sec) -- 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 14

[Bug 682726] New: Reference suggests only "su" instead of "su -"/su -l/su --login "make the shell a login shell"
by bugzilla_noreply＠novell.com 04 Apr '11

04 Apr '11

https://bugzilla.novell.com/show_bug.cgi?id=682726 https://bugzilla.novell.com/show_bug.cgi?id=682726#c0 Summary: Reference suggests only "su" instead of "su -"/su -l/su --login "make the shell a login shell" Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Documentation AssignedTo: ke(a)novell.com ReportedBy: Martin.Seidler(a)web.de QAContact: ke(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0.0) Gecko/20100101 Firefox/4.0 The manual "Referece" describes only to get superuser privileges without really becoming root (without using a login shell or an equivalent). So the user will get root rights without using the environment of the user root. Reproducible: Always Steps to Reproduce: 1. Open the documentation/Manual "Reference" http://doc.opensuse.org/products/opensuse/openSUSE/opensuse-reference 2. Go to Reference > Chapter 21. Shell Basics > 21.4. Becoming Root > 21.4.1. Using su http://doc.opensuse.org/products/opensuse/openSUSE/opensuse-reference/cha.n… 3. Read Actual Results: "su" The procedure of getting superuser privileges but not logging in as superuser actual is described: [CITE] 21.4.1. Using su¶ In order to temporarily become root in a shell, proceed as follows: 1. Enter su. You are prompted for the root password. 2. Enter the password. If you mistyped the root password, the shell displays a message. In this case, you have to re-enter su before retyping the password. If your password is correct, a hash symbol # appears at the end of the prompt, signaling that you are acting as root now. [...] [/CITE] Expected Results: "su -"="su -l"="su -login" should be described. The procedure of getting superuser privileges and simultaneous logging in as root with root's enviorment should be described. In addition a warning before using only "su" might be appropriate. See also: Vincent Untz Re: [opensuse-factory] Trouble starting yast2 from terminal Date: Thu, 10 Mar 2011 10:47:34 +0100 Message-id: <20110310094734.GC27272(a)vuntz.net> http://lists.opensuse.org/opensuse-factory/2011-03/msg00298.html [CITE] Use "su -", not "su". I'm actively wondering if there's any reason to keep the "su" default behavior around. It just keeps harming us again and again. [/CITE] Guido Berhörster Bug 655751 - gdbus aborting due to unauthorized socket in DBUS_SESSION_BUS_ADDRESS Comment 10 of that thread 2011-03-17 18:51:17 UTC [CITE](In reply to comment #9) > You are right. I wasn't using "-" before. I tested it and it worked. While I > k now that is the standard way of doing things, previous versions of Suse > didn't require it--made me lazy I guess. You shouldn't do that, GNU coreutils su has in contrast to other implementations like Solaris su no security precautions at all and if you don't request a login shell, $PATH and any $LD_* variables are happily passed along. But this is getting offtopic, this bug is about glib not handling an invalid $DBUS_SESSION_BUS_ADDRESS gracefully. [/CITE] SDB:Login as root # A longer terminal session as root http://en.opensuse.org/SDB:Login_as_root#A_longer_terminal_session_as_root http://en.wikipedia.org/wiki/Su_%28Unix%29#Usage [CITE][...]It should generally be used with a hyphen by administrators (su -, which is identical to su - root), which can be used to start a login shell. This way users can assume the user environment of the target user:[..] [/CITE] Because of that I presume the Serverity Major is appropriate. -- 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