December 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 555566] New: Yast: Software Management-> Update if newer version available -> does not work
by bugzilla_noreply＠novell.com 01 Dec '09

01 Dec '09

http://bugzilla.novell.com/show_bug.cgi?id=555566 Summary: Yast: Software Management-> Update if newer version available -> does not work Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: nugenesis(a)gmx.net QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4 In Yast -> Software Management -> RMB on a package -> select "All in this List" -> "Update if newer Version is available" does not mark the package as "will be updated (green upper arrow)" even if there is a newer version for this package available. Reproducible: Always Steps to Reproduce: 1.Fresh 11.2 intall. 2.Yast->Software Repositories->Add provided Community Repository "Open Suse Build Service - Mozilla" 3.Yast -> Software Management -> Search Package "MozillaFirefox" 4.Have a look on the Version Tab for this package , installed is version 3.5.4.x from "OpenSuse-11.2-Oss" Repository, but there is a newer Version (3.5.5.x) in the "Open Suse Build Service - Mozilla" Repository 4. RMB on MozillaFirefox Package -> select "All in this List" -> "Update if newer Version is available" 5. MozillaFirefox Package is NOT marked as "will be updated" Actual Results: Package will not be updated even if there is a new version available Expected Results: Packages will be updated if there is a new version available -- 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 7

[Bug 412938] No migration path from KDE 3.4 to KDE 4.x
by bugzilla_noreply＠novell.com 01 Dec '09

01 Dec '09

http://bugzilla.novell.com/show_bug.cgi?id=412938 http://bugzilla.novell.com/show_bug.cgi?id=412938#c9 Lars Behrens <lars.behrens(a)pi.uka.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lars.behrens(a)pi.uka.de --- Comment #9 from Lars Behrens <lars.behrens(a)pi.uka.de> 2009-12-01 11:42:50 UTC --- Yes, a migration tool is extremely important! I can't go hunting config files in all of my user's ~ dirs (kmail, knode filters, korganizer dates, ..). In the current state 11.2 won't be usable for us. For Debian there's "kaboom", maybe could take profit of that. -- 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 0

[Bug 432497] Checkinstall fails with some packages.
by bugzilla_noreply＠novell.com 01 Dec '09

01 Dec '09

http://bugzilla.novell.com/show_bug.cgi?id=432497 http://bugzilla.novell.com/show_bug.cgi?id=432497#c5 Philipp Thomas <pth(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|ASSIGNED |RESOLVED Component|Development |Development Resolution| |FIXED Product|openSUSE 11.1 |openSUSE 11.2 Target Milestone|--- |Final --- Comment #5 from Philipp Thomas <pth(a)novell.com> 2009-12-01 11:32:52 UTC --- Long since fixed. -- 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 0

[Bug 431659] df shows invalid filesystem informations while umount is running
by bugzilla_noreply＠novell.com 01 Dec '09

01 Dec '09

http://bugzilla.novell.com/show_bug.cgi?id=431659 http://bugzilla.novell.com/show_bug.cgi?id=431659#c6 Philipp Thomas <pth(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|ASSIGNED |RESOLVED Resolution| |UPSTREAM --- Comment #6 from Philipp Thomas <pth(a)novell.com> 2009-12-01 11:30:16 UTC --- Bug has been reported upstreams. If and when it's fixed openSUSE will get it with the regular updates. -- 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 0

[Bug 559458] New: webYaST: crash after time module during first start
by bugzilla_noreply＠novell.com 01 Dec '09

01 Dec '09

http://bugzilla.novell.com/show_bug.cgi?id=559458 http://bugzilla.novell.com/show_bug.cgi?id=559458#c0 Summary: webYaST: crash after time module during first start Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: WebYaST AssignedTo: kkaempf(a)novell.com ReportedBy: mschmidkunz(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- After the Time module step during first start webYaST crashes with error 401: Failed with 401 Unauthorized The details are: /usr/lib/ruby/gems/1.8/gems/activeresource-2.3.4/lib/active_resource/connection.rb:190:in `handle_response' /usr/lib/ruby/gems/1.8/gems/activeresource-2.3.4/lib/active_resource/connection.rb:173:in `request' /usr/lib/ruby/gems/1.8/gems/activeresource-2.3.4/lib/active_resource/connection.rb:138:in `get' /usr/lib/ruby/gems/1.8/gems/activeresource-2.3.4/lib/active_resource/base.rb:639:in `find_every' /usr/lib/ruby/gems/1.8/gems/activeresource-2.3.4/lib/active_resource/base.rb:582:in `find' /srv/www/yast/lib/yast/service_resource.rb:161:in `permissions' /srv/www/yast/lib/proxy_loader.rb:48:in `load_proxy' /srv/www/yast/vendor/plugins/systemtime/app/controllers/systemtime_controller.rb:89:in `update' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/base.rb:1331:in `send' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/base.rb:1331:in `perform_action_without_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/filters.rb:617:in `call_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/filters.rb:610:in `perform_action_without_benchmark' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.4/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime' /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.4/lib/active_support/core_ext/benchmark.rb:17:in `ms' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/rescue.rb:160:in `perform_action_without_flash' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/flash.rb:146:in `perform_action' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/base.rb:532:in `send' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/base.rb:532:in `process_without_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/filters.rb:606:in `process' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/base.rb:391:in `process' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/base.rb:386:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/routing/route_set.rb:437:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/dispatcher.rb:87:in `dispatch' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/dispatcher.rb:121:in `_call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/dispatcher.rb:130:in `build_middleware_stack' /srv/www/yast/lib/yast/rack/static_overlay.rb:47:in `call' /srv/www/yast/lib/yast/rack/static_overlay.rb:47:in `call' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/query_cache.rb:29:in `call' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/query_cache.rb:9:in `cache' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/query_cache.rb:28:in `call' /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:361:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/head.rb:9:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/methodoverride.rb:24:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/params_parser.rb:15:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/session/cookie_store.rb:93:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/failsafe.rb:26:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `synchronize' /usr/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.4/lib/action_controller/dispatcher.rb:106:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/content_length.rb:13:in `call' /usr/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/handler/fastcgi.rb:56:in `serve' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:103:in `process_request' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:153:in `with_signal_handler' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:101:in `process_request' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:78:in `process_each_request' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:77:in `each' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:77:in `process_each_request' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:76:in `catch' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:76:in `process_each_request' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:51:in `process!' /usr/lib/ruby/gems/1.8/gems/rails-2.3.4/lib/fcgi_handler.rb:23:in `process!' /srv/www/yast/public/dispatch.fcgi:24 -- 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 2

[Bug 556569] New: Scanner Canon LIDE20 driver plustek -- driver activation failed
by bugzilla_noreply＠novell.com 01 Dec '09

01 Dec '09

http://bugzilla.novell.com/show_bug.cgi?id=556569#c0 Summary: Scanner Canon LIDE20 driver plustek -- driver activation failed Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: 64bit OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: michel(a)datiscum.de QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4 The scanner works under 11.1 but now in 11.2 it can not be activated by yast2. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 6

[Bug 429532] IMLIB: can't load pbm files
by bugzilla_noreply＠novell.com 01 Dec '09

01 Dec '09

http://bugzilla.novell.com/show_bug.cgi?id=429532 http://bugzilla.novell.com/show_bug.cgi?id=429532#c4 Philipp Thomas <pth(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #4 from Philipp Thomas <pth(a)novell.com> 2009-12-01 11:15:35 UTC --- 10.3 is dead. -- 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 0

[Bug 559472] New: webYaST: unable to access registration module as root
by bugzilla_noreply＠novell.com 01 Dec '09

01 Dec '09

http://bugzilla.novell.com/show_bug.cgi?id=559472 http://bugzilla.novell.com/show_bug.cgi?id=559472#c0 Summary: webYaST: unable to access registration module as root Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: WebYaST AssignedTo: kkaempf(a)novell.com ReportedBy: mschmidkunz(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- In the git version I am unable to access the registration module. The error message states that I have no permissions for registration but I am logged in as root :-( -- 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 1

[Bug 557196] New: CUPS GUI fails to display some pages (e.g. when adding a class)
by bugzilla_noreply＠novell.com 01 Dec '09

01 Dec '09

http://bugzilla.novell.com/show_bug.cgi?id=557196 http://bugzilla.novell.com/show_bug.cgi?id=557196#c0 Summary: CUPS GUI fails to display some pages (e.g. when adding a class) Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Printing AssignedTo: jsmeix(a)novell.com ReportedBy: Ulrich.Windl(a)rz.uni-regensburg.de QAContact: jsmeix(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.23) Gecko/20090410 SUSE/1.1.18-0.1.1 SeaMonkey/1.1.18 When Adding a class to CUPS using the web interface (http://localhost:631/), an URI is selected that should reload a page, but the page remains blank. For example such an URI is http://localhost:631/admin/?OP=redirect&URL=/classes/postscript-color Reproducible: Always Steps to Reproduce: 1. Add a new class 2. Wait a few seconds Actual Results: An empty page appears Expected Results: The page should not be empty Browser being used was Firefox -- 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 559046] New: Cannot configure SCSI scanner with YaST - detection fails
by bugzilla_noreply＠novell.com 01 Dec '09

01 Dec '09

http://bugzilla.novell.com/show_bug.cgi?id=559046 http://bugzilla.novell.com/show_bug.cgi?id=559046#c0 Summary: Cannot configure SCSI scanner with YaST - detection fails Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alexander.koenig(a)koenig-a.de QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Created an attachment (id=329905) --> (http://bugzilla.novell.com/attachment.cgi?id=329905) Yast logs User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.5) Gecko/20091103 SUSE/3.5.5-1.1.2 Firefox/3.5.5 When I try to configure my SCSI scanner on openSUSE 11.2 the YaST scanner configuration module does not detect it and I am unable to configure it. I suspect that this is because the module uses hp-probe internally (according to /var/log/messages), which seems not to look for SCSI devices at all. Detection, configuration and usage of the scanner works perfectly on openSUSE 11.1 installed on another partition of the same computer. Because of bug 548108 I had to install 11.2 with "acpi=ht" and also boot with this kernel parameter. Reproducible: Always Steps to Reproduce: 1. Attach SCSI scanner to system 2. boot 3. Call up YaST scanner configuration module Actual Results: Scanner is not detected Expected Results: Scanner is detected and configured for sane - CPU: AMD Phenom X4 9550 4x2.2GHz (95W) 65nm Quad Core - Memory: 4GB - 2x2048MB DDR2-800 CL5, Dual Channel 2x1024MB - Motherboard: GIGABYTE GA-MA770-DS3, AMD 770 / SB600 chipsets - Graphics: NVidia GeForce 7300 GS, 256MB, TV-Out, DVI, PCIe - Floppy: 1.44MB - 1. hard disk: 500GB Seagate 7200 RPM SATA II - 2. hard disk: 500GB Seagate 7200 RPM SATA II - DVD-ROM: Optiarc DDU 1615 16x/48x, IDE - DVD-RW: NEC AD-7200, IDE - SCSI-Controller: Adaptec 2940 SCSI adapter, SCSI ID: 7 - Tape Streamer: Seagate (CONNER) CTT8000-S SCSI Tr 4, SCSI ID: 4 - Scanner: UMAX Astra 610S SCSI SCSI ID: 5 - Card Reader: Apacer AE101, 16 card types - DVB Controller: Technotrend/Hauppauge DVB card rev2.1 - Modem: ELSA MicroLink 56k basic V90 - Webcam: Lifetec LT 9338 USB Camera Y2logs is attached Output of lsscsi: 0:0:0:0] disk ATA ST3500820AS SD36 /dev/sda [2:0:0:0] disk ATA ST3500820AS SD36 /dev/sdb [4:0:0:0] disk Generic USB SD Reader 1.00 /dev/sdc [4:0:0:1] disk Generic USB CF Reader 1.01 /dev/sdd [4:0:0:2] disk Generic USB xD/SM Reader 1.02 /dev/sde [4:0:0:3] disk Generic USB MS Reader 1.03 /dev/sdf [5:0:0:0] cd/dvd SONY DVD-ROM DDU1615 GYN2 /dev/sr0 [5:0:1:0] cd/dvd Optiarc DVD RW AD-7200A 1.06 /dev/sr1 [7:0:4:0] tape CONNER CTT8000-S 1.17 /dev/st0 [7:0:5:0] scanner UMAX Astra 610S V1.3 - [8:0:0:0] disk SanDisk Cruzer Micro 0.1 /dev/sdg Output of sane-find-scanner: # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. found SCSI scanner "UMAX Astra 610S V1.3" at /dev/sg9 # Your SCSI scanner was detected. It may or may not be supported by SANE. Try # scanimage -L and read the backend's manpage. Note: sane-find-scanner hangs after printing this. scanimage -L hangs without any output Both processes cannot be terminated - even with kill -9 -- 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 2