January 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 279329] New: Crash in c44 (djvulibre)
by bugzilla_noreply＠novell.com 04 Jan '08

04 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=279329 Summary: Crash in c44 (djvulibre) Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: robin.listas(a)telefonica.net QAContact: qa(a)suse.de I'm trying to convert a big image to djvu format, and c44 crashes with message: pngtopnm mosaico.png > mosaico.pnm c44 -dpi 72 -slice "72+11+10+10" mosaico.pnm terminate called after throwing an instance of 'DJVU::GException' <===== Aborted The image is so big that c44 reserves 2.5 GiB of memory (mosaico.pnm is 1.7 GiB). It is 16384x16384 pixels (I haven't been able to open it with gimp, yet) rpm is version «djvulibre-3.5.17-27» -- 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, or are watching someone who is.

1 15

[Bug 339807] New: cscope does not remove its temporary files when used with vim
by bugzilla_noreply＠novell.com 04 Jan '08

04 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=339807 Summary: cscope does not remove its temporary files when used with vim Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: tony(a)daylessday.org QAContact: qa(a)suse.de Found By: Other cscope removes temporary files in myexit() function which is called on shutdown and/or when SIGHUP/SIGINT/SIGQUIT received. vim sends SIGTERM to cscope on shutdown, so myexit() is never called and temporary files are not removed (so I get dozens cscope.XXXX directories in /tmp a day). A possible solution is to register myexit() as a handler for SIGTERM. See the patch below. This bug has been reported to the mainstream (see http://sourceforge.net/tracker/index.php?func=detail&aid=1827519&group_id=4…) and hopefully will get there sooner or later. --- cscope-15.6.orig/src/main.c 2006-09-30 12:13:00.000000000 +0400 +++ cscope-15.6/src/main.c 2007-11-07 16:35:44.000000000 +0300 @@ -379,6 +379,7 @@ } /* cleanup on the hangup signal */ signal(SIGHUP, myexit); + signal(SIGTERM, myexit); /* if the database path is relative and it can't be created */ if (reffile[0] != '/' && access(".", WRITE) != 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 7

[Bug 350663] New: How to turn off message "kernel: SoftMAC: Scanning finished: scanned 13 channels starting with channel 1" in /var/ log/messages
by bugzilla_noreply＠novell.com 04 Jan '08

04 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=350663 Summary: How to turn off message "kernel: SoftMAC: Scanning finished: scanned 13 channels starting with channel 1" in /var/log/messages Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gdoig(a)pcug.org.au QAContact: qa(a)suse.de Found By: --- I get lots of these messages in /var/log/messages In 1 hour it logs 28 or so. # grep -i "scanned 13 channels" /var/log/messages | grep -i "Dec 26 10:"| wc -l 28 Overall its logged todate 6009 # grep -i "scanned 13 channels" /var/log/messages | wc -l 6009 How do I turn this message off ? -- 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 299670] New: bits/sigcontext. h from glibc-devel includes non-existant asm/sigcontext.h
by bugzilla_noreply＠novell.com 04 Jan '08

04 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=299670 Summary: bits/sigcontext.h from glibc-devel includes non-existant asm/sigcontext.h Product: openSUSE 10.3 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: jigish.gohil(a)gmail.com QAContact: qa(a)suse.de Found By: --- linux-kernel-headers-2.6.22-5 installs /usr/include/asm-<arch>/*. linux-kernel-header package need to do the following in %post according to the arch it gets installed on, for example on i686. ln -s /usr/include/asm-i386 /usr/include/asm Or line 28 of /usr/include/bits/sigcontext.h from glibc-devel need to be fixed: # include <asm-i386/sigcontext.h> Any package that includes /usr/include/bits/sigcontext.h will fail to build. -- 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 32

[Bug 351442] New: pam_mount fails to update common-auth and common-session
by bugzilla_noreply＠novell.com 03 Jan '08

03 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=351442 Summary: pam_mount fails to update common-auth and common-session Product: openSUSE 10.3 Version: Final Platform: i586 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jrobiso2(a)ford.com QAContact: qa(a)suse.de Found By: Beta-Customer The pam_mount rpm, when installed, does not update /etc/pam.d/common-auth or common-session, both of which are required in order to work. Hand editing these files is dangerous for those not familiar enough with pam. I can verify this as I have had to use a live CD in the past to restore backup pam files after I edited them ... and screwed them up. As the file entries are dependent on what type of user authentication is being used (i.e. "If you use pam_ldap, pam_winbind, or any other authentication services that make use of PAM's sufficient keyword, . . .") it isn't a trivial matter to incorporate scripts into the rpm to handle this. However, it must be considered for work for 11.0, and I believe should be fixed for 10.3 and sent out as an update. This will also require modification of the "user authentication" setup items in YaST as well to ensure they respect the use of pam_mount. -- 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 291347] New: Unable to upload 250MB source tarball via webclient
by bugzilla_noreply＠novell.com 03 Jan '08

03 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=291347 Summary: Unable to upload 250MB source tarball via webclient Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lmichnovic(a)novell.com QAContact: adrian(a)novell.com Found By: --- I'm unable to upload 250 MB large tarball to my project(lmich) package openarena. The server error response was: OpenSUSE Webclient Error: Error Details: Errorcode: 500 Message: failed to allocate memory Exception from Webclient: NoMemoryError: failed to allocate memory Stack Trace: (eval):3:in `read' (eval):3:in `read' /srv/www/opensuse/webclient/current/public/../config/../app/models/package.rb:19:in `save_file' /srv/www/opensuse/webclient/current/public/../config/../app/controllers/package_controller.rb:344:in `save_file' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/base.rb:1095:in `perform_action_without_filters' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:632:in `call_filter' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:638:in `call_filter' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:438:in `call' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:637:in `call_filter' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:638:in `call_filter' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:438:in `call' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:637:in `call_filter' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:638:in `call_filter' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:438:in `call' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:637:in `call_filter' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:638:in `call_filter' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:438:in `call' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:637:in `call_filter' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:638:in `call_filter' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:449:in `call' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:637:in `call_filter' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:619:in `perform_action_without_benchmark' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/benchmarking.rb:66:in `perform_action_without_rescue' /usr/lib64/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/benchmarking.rb:66:in `perform_action_without_rescue' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/rescue.rb:83:in `perform_action' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/base.rb:430:in `process_without_filters' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/filters.rb:624:in `process_without_session_management_support' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/session_management.rb:114:in `process' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.13.3/lib/action_controller/base.rb:330:in `process' /usr/lib64/ruby/gems/1.8/gems/rails-1.2.3/lib/dispatcher.rb:41:in `dispatch' /usr/lib64/ruby/gems/1.8/gems/rails-1.2.3/lib/fcgi_handler.rb:168:in `process_request' /usr/lib64/ruby/gems/1.8/gems/rails-1.2.3/lib/fcgi_handler.rb:143:in `process_each_request!' /usr/lib64/ruby/gems/1.8/gems/rails-1.2.3/lib/fcgi_handler.rb:109:in `with_signal_handler' /usr/lib64/ruby/gems/1.8/gems/rails-1.2.3/lib/fcgi_handler.rb:142:in `process_each_request!' /usr/lib64/ruby/1.8/fcgi.rb:612:in `each_cgi' /usr/lib64/ruby/1.8/fcgi.rb:609:in `each_cgi' /usr/lib64/ruby/gems/1.8/gems/rails-1.2.3/lib/fcgi_handler.rb:141:in `process_each_request!' /usr/lib64/ruby/gems/1.8/gems/rails-1.2.3/lib/fcgi_handler.rb:55:in `process!' /usr/lib64/ruby/gems/1.8/gems/rails-1.2.3/lib/fcgi_handler.rb:25:in `process!' /srv/www/opensuse/webclient/current/public/dispatch.fcgi:24 -- 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 342148] New: after kernel upadate: e1000 ethernet only works while in promiscuous mode
by bugzilla_noreply＠novell.com 03 Jan '08

03 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=342148#c1 Summary: after kernel upadate: e1000 ethernet only works while in promiscuous mode Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: koenig(a)linux.de QAContact: qa(a)suse.de Found By: --- last weekend I got a new kernel via online update to harald > uname -a Linux harald 2.6.22.12-0.1-default #1 SMP 2007/11/06 23:05:18 UTC x86_64 x86_64 x86_64 GNU/Linux on an IBM T60 notebook with e1000. now since monday I have major problems with dhcp and network setup in our company, before none of these problems showed up regularly (not with 10.3 before last update and not with 10.1/10.2 before). 1) the weirdest effect to me is that now a ping to the default gateway only works while eth1 (e1000) is in promiscuous mode by running tcpdump. as soon as I stop tcpdump, I can't reach the gateway anymore :-( completely stopping firewall doesn't make any difference. finally I did a "rmmod e1000 ; modprobe e1000" and "ping gateway" works again without running tcpdump. other observations: 2) on monday (day 1 after update;) the same "can't ping gateway" happend. at that time I finally stoppted testing and did reboot the notebook (usually I only do suspend2ram for weeks -- typically until kernel update;). 3) dhcp takes very long (many minutes and/or multiple unplug/plug of RJ45). today our net admin checked the dhcp server logs and noticed that the first dhcp answer from the dhcp server seemed to be ignored from the notebook. it took 15 minutes until the notebook got it's (static/reserved) ip-adress via dhcpcd. tough ping to gateway didn't work then (see above). are there known/similar problems with the current kernel 2.6.22.12-0.1 ? any suggestion for testing in case the same problems show up again tomorrow morning ? before I found out that running tcpdump fixes the "can't ping gateway" problem, I planned for next morning to run tcpdump on eth1 before I connect the RJ45 and capture all packets, so that later I can check and compare the dhcp server log with the tcpdump log of the received dhcp packets. but now it might happen that running tcpdump might influence just the problem which I try to test -- can this be a heisenbug ? any thoughts about good tests -- or any suggestion about new kernel/setttings ? one scenario for next week is to step back to last kernel version. comments on that ? -- 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 351336] New: KDE:KDE4 builds referes to uninstalled packages named . x86-64
by bugzilla_noreply＠novell.com 03 Jan '08

03 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=351336 Summary: KDE:KDE4 builds referes to uninstalled packages named .x86-64 Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: roger.larsson(a)norran.net QAContact: qa(a)suse.de Found By: --- but the packages are installed but without the .x86-64 prefix. As an example: kde4-digikam-3.97.1.svn749246-1.8.x86_64 needs liblcms-1.16-39.2.x86_64 > locate liblcms /usr/lib/liblcms.so.1 /usr/lib/liblcms.so.1.0.16 /usr/lib64/liblcms.a /usr/lib64/liblcms.la /usr/lib64/liblcms.so /usr/lib64/liblcms.so.1 /usr/lib64/liblcms.so.1.0.16 - - - > locate liblcms | xargs rpm -q -f | sort -u file /var/cache/zypp/raw/openSUSE-10.3-Updates/repodata/patch-liblcms-4629.xml is not owned by any package liblcms-1.16-39.2 liblcms-32bit-1.16-39.2 liblcms-devel-1.16-39.2 So, I do have the package, my only problem is naming liblcms-1.16-39.2 v. liblcms-1.16-39.2.x86_64 Locking through packaging instructions http://en.opensuse.org/SUSE_Package_Conventions/RPM_Style "Release Tag" says nothing about a .x86_64 postfix -- 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 350775] New: Can rpm version be updated to perhaps this released version (rpm-4.5-0.4. src.rpm)
by bugzilla_noreply＠novell.com 03 Jan '08

03 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=350775 Summary: Can rpm version be updated to perhaps this released version (rpm-4.5-0.4.src.rpm) Product: openSUSE 11.0 Version: unspecified Platform: x86-64 OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gdoig(a)pcug.org.au QAContact: qa(a)suse.de Found By: --- Can rpm version be updated to perhaps this released version (rpm-4.5-0.4.src.rpm) http://rpm5.org/files/rpm/rpm-4.5/rpm-4.5-0.4.src.rpm See http://rpm5.org/files/rpm/rpm-4.5/ Thankyou. -- 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 349039] New: Updater Fails to Update
by bugzilla_noreply＠novell.com 03 Jan '08

03 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=349039 Summary: Updater Fails to Update Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: crispin(a)crispincowan.com QAContact: jsrain(a)novell.com Found By: Customer Created an attachment (id=187738) --> (https://bugzilla.novell.com/attachment.cgi?id=187738) relevant YaST2Logs The GNOME update agent tells me I have updates, I click it and start the update process, and the process completes abnormally quickly and it turns red again, telling me I need the same updates. Weird artifact: when I click the updater, it says that there are "5 mandatory updates" and "0 additional updates". When I select "details", the list of packages to be updated has 8 items in it: NetworkManager alsa gnome-screensaver kmps libvirt openssh pm-utils timezone glib2 Hmmm. Then I try to reproduce this result, and "details" now only shows me 5 items: NetworkManager libvirt openssh pm-utils timezone Then, when I try to run the "detailed" update, it wedges mid-way through: Retrieving pm-utils...OK OK Installing ./suse/i586/pm-utils-0.99.3.20070618-29.i586.rpm: "Tools to suspend and hibernate computers" OK Retrieving timezone...OK Installing ./suse/i586/timezone-2007j-3.i586.rpm: "Timezone Descriptions" OK Retrieving libvirt...OK Installing ./suse/i586/libvirt-0.3.3-26.i586.rpm: "A C toolkit to interract with the virtualization capabilities of Linux" (stalls here for a couple of hours ...) Y2Logs 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 2