October 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 741910] New: Claws Mail starts minimized
by bugzilla_noreply＠novell.com 29 Oct '12

29 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=741910 https://bugzilla.novell.com/show_bug.cgi?id=741910#c0 Summary: Claws Mail starts minimized Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 URL: http://www.thewildbeast.co.uk/claws-mail/bugzilla/show _bug.cgi?id=2396 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jdelvare(a)suse.com QAContact: qa(a)suse.de CC: dimstar(a)opensuse.org, vuntz(a)suse.com Found By: Community User Blocker: --- Running under Gnome 3.2 / openSUSE 12.1, Claws Mail starts with its main window minimized. I have to visit the "Windows" view to find it. This is a known issue, Red Hat has two bugs for it already: https://bugzilla.redhat.com/show_bug.cgi?id=693846 https://bugzilla.redhat.com/show_bug.cgi?id=693990 And upstream has one as well: http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2396 It's not entirely clear whether this is a gnome-shell bug or claws-mail bug. Upstream claws-mail developers say it's a bug in gnome-shell, but have applied a workaround nevertheless: http://www.claws-mail.org/tracker/getpatchset.php?ver=3.7.10cvs55 http://www.claws-mail.org/tracker/getpatchset.php?ver=3.7.10cvs75 On the gnome side I found this: https://bugzilla.gnome.org/show_bug.cgi?id=653061 But apparently no fix so far. -- 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 764870] New: When installing opensuse (almost all versions): "Make sure that cd number 1 is your drive" is displayed
by bugzilla_noreply＠novell.com 29 Oct '12

29 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=764870 https://bugzilla.novell.com/show_bug.cgi?id=764870#c0 Summary: When installing opensuse (almost all versions): "Make sure that cd number 1 is your drive" is displayed Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: 64bit OS/Version: openSUSE 12.1 Status: NEW Severity: Critical Priority: P5 - None Component: System Imaging AssignedTo: ms(a)suse.com ReportedBy: agunet(a)internet.com.uy QAContact: adrian(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20100101 Firefox/12.0 Basically, I have this hardware: • Processor INTEL Core™ i3-2100 de 3.1GHz (2 cores, 64 bits, 5 GT/s DMI, 3MB de caché, 32nm) • 4GB RAM (1 x 4GB DDR3 1333MHz) • Hard disk de 500GB SATA II • DVD double layer MotherBoard AsRock H61M-VS • 8 portss USB (6 back y 2 in the front) • Sound integrated VIA® VT1705 HD, sound 5.1 • Video card EVGA GeForce 8400GS 1GB DDR3 • Tarjeta de red integrada Atheros AR8152 - 10/100 Everytime I try to intstall opensuse: 12.1 11.4 11.3 11.1 10.3 12.2 (all of thos versions above happens the same) I enter the cd, the installation begins normally, After checking some acpi usb a message with text screen is displayed: "Make sure that disk number 1 is in your drive" The install can't continue from there Reproducible: Always Steps to Reproduce: 1. Insert a cd installation (any version. 12.1, 12.2, 11.4 will be better) 2. Make the steps to make a normal installation. 3. A message saying "Make sure that cd number 1 is in your drive" You can't do anything here with that message. Pressing "ok" will show the same message again Pressing "Back" will tell to chose language installation then to choose keyboard language then to choose some option that doesn't work or exit or reboot. 4. Reboot or halt your system Actual Results: A message saying "Make sure that cd number 1 is in your drive" Expected Results: Continue with the graphical installation. -- 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 784666] New: For plural handling ngettext(), dngettext(), etc. wanted
by bugzilla_noreply＠novell.com 29 Oct '12

29 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=784666 https://bugzilla.novell.com/show_bug.cgi?id=784666#c0 Summary: For plural handling ngettext(), dngettext(), etc. wanted Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: ke(a)suse.com QAContact: qa-bugs(a)suse.de CC: ma(a)suse.com, meissner(a)suse.com Found By: Documentation Blocker: --- To avoid translations such as this: #. we will throw this later if no URL checks out fine #: zypp/RepoManager.cc:913 msgid "Valid metadata not found at specified URL(s)" msgstr "Keine gültigen Metadaten bei de(m|n) festgelegten URL(s) gefunden" please use ngettext and friends for plural handling. It is documented in the libc resp. gettext manuals; see http://www.gnu.org/software/libc/manual/html_node/Advanced-gettext-function… (or in the Info file of the installed system). -- 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 775694] New: I/O subsystem completely broken; no multitasking possible
by bugzilla_noreply＠novell.com 29 Oct '12

29 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=775694 https://bugzilla.novell.com/show_bug.cgi?id=775694#c0 Summary: I/O subsystem completely broken; no multitasking possible Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: mantel(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: --- When one process is doing significant I/O, no other process can read or write data and is suspended until the first process finally finishes. How to reproduce: Play some music with your favorite music player. Then in some shell, type something like: cp -a hugefile.in hugefile.out after some seconds, music will stop playing and only continue after the cp has finished. I'm currently copying a 53 GB file and music stopped more than one minute ago! Currently the Linux multitasking is worse than it ever was in Windows a decade ago when it still had "cooperative multitasking". Oh, and it's not the hugetables bug: Mandelbrot:/sys/kernel/mm/transparent_hugepage # cat enabled always madvise [never] Mandelbrot:/sys/kernel/mm/transparent_hugepage # uname -a Linux Mandelbrot 3.1.10-1.9-desktop #1 SMP PREEMPT Thu Apr 5 18:48:38 UTC 2012 (4a97ec8) x86_64 x86_64 x86_64 GNU/Linux Mandelbrot:/sys/kernel/mm/transparent_hugepage # Meanwhile the "cp" has finished and music continues to play. After 2 (TWO!!!) minutes. On a system with 8 GB RAM and core-7 processor. -- 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 787124] New: Cannot add custom build-repository to my home project
by bugzilla_noreply＠novell.com 29 Oct '12

29 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=787124 https://bugzilla.novell.com/show_bug.cgi?id=787124#c0 Summary: Cannot add custom build-repository to my home project Classification: Internal Novell Products Product: openSUSE Build Service Version: master Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: webui AssignedTo: adrian(a)suse.com ReportedBy: locilka(a)suse.com QAContact: adrian(a)suse.com Found By: Development Blocker: --- https://build.suse.de/project/add_repository?project=home%3Alocilka%3ASLE11… Project: Project Repository: Repository New name: New Name [x] i586 [x] x86_64 (BTW: Searching didn't work for me) Click [ Add Repository ] You'll get a backtrace: OBS Web Interface Error: Error Details: Errorcode: unknown Message: undefined method `each' for "New Name":String Exception from Webclient: NoMethodError: undefined method `each' for "New Name":String Stack Trace: /srv/www/obs/webui/app/controllers/project_controller.rb:691:in `save_targets' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_controller/metal/implicit_render.rb:4:in `send_action' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/abstract_controller/base.rb:167:in `process_action' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_controller/metal/rendering.rb:10:in `process_action' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/abstract_controller/callbacks.rb:18:in `block in process_action' /usr/lib64/ruby/gems/1.9.1/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:502:in `_run__1015807991966375562__process_action__4298281668977685779__callbacks' /usr/lib64/ruby/gems/1.9.1/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:405:in `__run_callback' /usr/lib64/ruby/gems/1.9.1/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:385:in `_run_process_action_callbacks' /usr/lib64/ruby/gems/1.9.1/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:81:in `run_callbacks' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/abstract_controller/callbacks.rb:17:in `process_action' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_controller/metal/rescue.rb:29:in `process_action' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_controller/metal/instrumentation.rb:30:in `block in process_action' /usr/lib64/ruby/gems/1.9.1/gems/activesupport-3.2.8/lib/active_support/notifications.rb:123:in `block in instrument' /usr/lib64/ruby/gems/1.9.1/gems/activesupport-3.2.8/lib/active_support/notifications/instrumenter.rb:20:in `instrument' /usr/lib64/ruby/gems/1.9.1/gems/activesupport-3.2.8/lib/active_support/notifications.rb:123:in `instrument' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_controller/metal/instrumentation.rb:29:in `process_action' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_controller/metal/params_wrapper.rb:207:in `process_action' /usr/lib64/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/railties/controller_runtime.rb:18:in `process_action' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/abstract_controller/base.rb:121:in `process' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/abstract_controller/rendering.rb:45:in `process' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_controller/metal.rb:203:in `dispatch' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_controller/metal/rack_delegation.rb:14:in `dispatch' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_controller/metal.rb:246:in `block in action' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_dispatch/routing/route_set.rb:73:in `call' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_dispatch/routing/route_set.rb:73:in `dispatch' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_dispatch/routing/route_set.rb:36:in `call' /usr/lib64/ruby/gems/1.9.1/gems/journey-1.0.4/lib/journey/router.rb:68:in `block in call' /usr/lib64/ruby/gems/1.9.1/gems/journey-1.0.4/lib/journey/router.rb:56:in `each' /usr/lib64/ruby/gems/1.9.1/gems/journey-1.0.4/lib/journey/router.rb:56:in `call' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_dispatch/routing/route_set.rb:600:in `call' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_dispatch/middleware/best_standards_support.rb:17:in `call' /usr/lib64/ruby/gems/1.9.1/gems/rack-1.4.1/lib/rack/etag.rb:23:in `call' /usr/lib64/ruby/gems/1.9.1/gems/rack-1.4.1/lib/rack/conditionalget.rb:35:in `call' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_dispatch/middleware/head.rb:14:in `call' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_dispatch/middleware/params_parser.rb:21:in `call' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_dispatch/middleware/flash.rb:242:in `call' /usr/lib64/ruby/gems/1.9.1/gems/rack-1.4.1/lib/rack/session/abstract/id.rb:205:in `context' /usr/lib64/ruby/gems/1.9.1/gems/rack-1.4.1/lib/rack/session/abstract/id.rb:200:in `call' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_dispatch/middleware/cookies.rb:339:in `call' /usr/lib64/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/query_cache.rb:64:in `call' /usr/lib64/ruby/gems/1.9.1/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:473:in `call' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_dispatch/middleware/callbacks.rb:28:in `block in call' /usr/lib64/ruby/gems/1.9.1/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:405:in `_run__711790095152841478__call__1742955655617055946__callbacks' /usr/lib64/ruby/gems/1.9.1/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:405:in `__run_callback' /usr/lib64/ruby/gems/1.9.1/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:385:in `_run_call_callbacks' /usr/lib64/ruby/gems/1.9.1/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:81:in `run_callbacks' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_dispatch/middleware/callbacks.rb:27:in `call' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_dispatch/middleware/remote_ip.rb:31:in `call' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_dispatch/middleware/debug_exceptions.rb:16:in `call' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_dispatch/middleware/show_exceptions.rb:56:in `call' /usr/lib64/ruby/gems/1.9.1/gems/railties-3.2.8/lib/rails/rack/logger.rb:26:in `call_app' /usr/lib64/ruby/gems/1.9.1/gems/railties-3.2.8/lib/rails/rack/logger.rb:16:in `call' /usr/lib64/ruby/gems/1.9.1/gems/actionpack-3.2.8/lib/action_dispatch/middleware/request_id.rb:22:in `call' /usr/lib64/ruby/gems/1.9.1/gems/rack-1.4.1/lib/rack/methodoverride.rb:21:in `call' /usr/lib64/ruby/gems/1.9.1/gems/rack-1.4.1/lib/rack/runtime.rb:17:in `call' /usr/lib64/ruby/gems/1.9.1/gems/activesupport-3.2.8/lib/active_support/cache/strategy/local_cache.rb:72:in `call' /usr/lib64/ruby/gems/1.9.1/gems/rack-1.4.1/lib/rack/lock.rb:15:in `call' /usr/lib64/ruby/gems/1.9.1/gems/rack-cache-1.2/lib/rack/cache/context.rb:136:in `forward' /usr/lib64/ruby/gems/1.9.1/gems/rack-cache-1.2/lib/rack/cache/context.rb:143:in `pass' /usr/lib64/ruby/gems/1.9.1/gems/rack-cache-1.2/lib/rack/cache/context.rb:155:in `invalidate' /usr/lib64/ruby/gems/1.9.1/gems/rack-cache-1.2/lib/rack/cache/context.rb:71:in `call!' /usr/lib64/ruby/gems/1.9.1/gems/rack-cache-1.2/lib/rack/cache/context.rb:51:in `call' /usr/lib64/ruby/gems/1.9.1/gems/railties-3.2.8/lib/rails/engine.rb:479:in `call' /usr/lib64/ruby/gems/1.9.1/gems/railties-3.2.8/lib/rails/application.rb:223:in `call' /usr/lib64/ruby/gems/1.9.1/gems/railties-3.2.8/lib/rails/railtie/configurable.rb:30:in `method_missing' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/rack/request_handler.rb:96:in `process_request' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/abstract_request_handler.rb:516:in `accept_and_process_next_request' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/abstract_request_handler.rb:274:in `main_loop' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/rack/application_spawner.rb:206:in `start_request_handler' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/rack/application_spawner.rb:171:in `block in handle_spawn_application' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/utils.rb:470:in `safe_fork' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/rack/application_spawner.rb:166:in `handle_spawn_application' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/abstract_server.rb:357:in `server_main_loop' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/abstract_server.rb:206:in `start_synchronously' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/abstract_server.rb:180:in `start' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/rack/application_spawner.rb:129:in `start' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/spawn_manager.rb:253:in `block (2 levels) in spawn_rack_application' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/abstract_server_collection.rb:132:in `lookup_or_add' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/spawn_manager.rb:246:in `block in spawn_rack_application' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/abstract_server_collection.rb:82:in `block in synchronize' <internal:prelude>:10:in `synchronize' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/spawn_manager.rb:244:in `spawn_rack_application' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/spawn_manager.rb:137:in `spawn_application' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/spawn_manager.rb:275:in `handle_spawn_application' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/abstract_server.rb:357:in `server_main_loop' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/lib/phusion_passenger/abstract_server.rb:206:in `start_synchronously' /usr/lib64/ruby/gems/1.9.1/gems/passenger-3.0.17/helper-scripts/passenger-spawn-server:99:in `<main>' -- 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 779425] New: Logging in for xfce: login hangs for 1 min without disk activity, then xfce starts (happens only after boot).
by bugzilla_noreply＠novell.com 29 Oct '12

29 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=779425 https://bugzilla.novell.com/show_bug.cgi?id=779425#c0 Summary: Logging in for xfce: login hangs for 1 min without disk activity, then xfce starts (happens only after boot). Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Xfce AssignedTo: bnc-team-xfce(a)forge.provo.novell.com ReportedBy: post(a)jbechtel.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64; U; de) Presto/2.10.289 Version/12.02 That's what I mesured: After boot: Enter password, press enter. ~61 s nothing (password greyed out, cursor not accessible via mouse, but via left/right key you can move the cursor in password field. Button "Anmelden" (login) still clickable) ~12 s load (screen changes, xfce splash, hard disk activity, ...) Then XFCE is loaded. Reproducible: Always Steps to Reproduce: Case A: Start system, login for XFCE Case B: Start system, login for XFCE, logout, login for XFCE Case C: Start system, login for Gnome, logout, login for XFCE Actual Results: Case A: login takes 1 additional minute Case B: the second login takes only 5 seconds. Case C: the Gnome login is as fast as usual, the second login is fast (without displaying the login manager for long time) Expected Results: Case A: Get XFCE in 12 seconds. (Case B: The second login is OK as it is.) (Case C: This is OK, too.) I recently switched from Gnome to XFCE When I turn on my system, the login manager is in Gnome design - I don't know weather this is right. -- 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 769546] New: ntop not starting, config error
by bugzilla_noreply＠novell.com 29 Oct '12

29 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=769546 https://bugzilla.novell.com/show_bug.cgi?id=769546#c0 Summary: ntop not starting, config error Classification: openSUSE Product: openSUSE 12.2 Version: Beta 2 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: a.klausmann(a)cida.de 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 ntop is not starting A message appears "run 'ntop -A -u ntop' This does not solve the problem. '**ERROR** ... open of /var/ntop/prefsCache.db fialed: File open error' Reproducible: Always Steps to Reproduce: 1. 2. 3. The directory /var/ntop does not exist. In previous releases of openSUSE the command were 'ntop -A -u wwwrun' and the directory were /var/lib/ntop. To solve this i did 1. rm /var/lib/ntop/* 2. run 'ntop -A -u wwwrun -P /var/lib/ntop' 3. rcntop start -- 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 787061] New: enabling 1 desktop effect basically freezes KDE - potential KWIN problem
by bugzilla_noreply＠novell.com 28 Oct '12

28 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=787061 https://bugzilla.novell.com/show_bug.cgi?id=787061#c0 Summary: enabling 1 desktop effect basically freezes KDE - potential KWIN problem Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: axel.braun(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=511104) --> (http://bugzilla.novell.com/attachment.cgi?id=511104) Hardware info User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20100101 Firefox/16.0 I have a clean install of 12.2 on a eeepc 901 GO. everything worked fine with even good response times. In standard installation, desktop effects were enabled. Then i enabled the search for the cursor-position. From that moment onwards kwin uses around 50% of CPU. Clicking the green menu button takes about 9 seconds to respond (open menu). The desktop becomes basically unuseable. workaround: disable all desktop effects and reboot. Nevertheless, that should be fixed.... Reproducible: Always Steps to Reproduce: 1. enable one desktop effect beside standard effects... 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 757199] New: isv:ownCloud:devel/owncloud: Bug
by bugzilla_noreply＠novell.com 28 Oct '12

28 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=757199 https://bugzilla.novell.com/show_bug.cgi?id=757199#c0 Summary: isv:ownCloud:devel/owncloud: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: VMWare OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: freitag(a)opensuse.org ReportedBy: sakanamax(a)hotmail.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Created an attachment (id=486172) --> (http://bugzilla.novell.com/attachment.cgi?id=486172) log about add minisub app Can not add minisub apps log "Error core Failed to open archive when installing app" -- 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 757198] New: isv:ownCloud:owncloud3/owncloud: Bug
by bugzilla_noreply＠novell.com 28 Oct '12

28 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=757198 https://bugzilla.novell.com/show_bug.cgi?id=757198#c0 Summary: isv:ownCloud:owncloud3/owncloud: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: VMWare OS/Version: openSUSE 12.1 Status: NEW Severity: Critical Priority: P5 - None Component: 3rd party software AssignedTo: freitag(a)opensuse.org ReportedBy: sakanamax(a)hotmail.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Can't init the owncloud 3 When input the username and password in http://Server_IP/owncloud It can install, but it can't finish init. -- 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