November 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 586640] New: Weird chars in theme list (menu -> settings -> appearance)
by bugzilla_noreply＠novell.com 24 Mar '12

24 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=586640 http://bugzilla.novell.com/show_bug.cgi?id=586640#c0 Summary: Weird chars in theme list (menu -> settings -> appearance) Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Xfce AssignedTo: bnc-team-xfce(a)forge.provo.novell.com ReportedBy: schaiba(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=347363) --> (http://bugzilla.novell.com/attachment.cgi?id=347363) The look of the weird characters - these characters differ according to theme selected User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.0) Gecko/20100115 SUSE/3.6.0-1.8 Firefox/3.6 The screenshot will speak better than me; this happens regardless of the used theme. If selected, the themes work, only I don't know their names. :) 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 3

[Bug 570455] New: %ghost still requires the file to exist within buildroot
by bugzilla_noreply＠novell.com 24 Mar '12

24 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=570455 http://bugzilla.novell.com/show_bug.cgi?id=570455#c0 Summary: %ghost still requires the file to exist within buildroot Classification: openSUSE Product: openSUSE 11.3 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: bitdealer(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- According to prusnak %ghost from 11.2 on doesn't require the file to be present in buildroot anymore (e.g. one doesn't have to create it by touching it). However, if the file doesn't exist the build still fails with file not found. I tried e.g.: * %ghost %attr(700,root,root) %{_sbindir}/zabbix-server * %attr(0700,root,root) %ghost %{_sbindir}/zabbix-server * %attr(700,root,root) %ghost %{_sbindir}/zabbix-server as soon as I touch %{buildroot}%{_sbindir}/zabbix-server during %install it builds just fine. Cite from http://stick.gk2.sk/blog/2009/09/new-rpm-in-opensuse-factory/ "# %ghost files do not have to be present in the build root anymore. In this case you have to specify their attributes like this: %attr(0644,root,root) %ghost ghostfile." -- 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 694654] New: games: Bug in vdrift
by bugzilla_noreply＠novell.com 24 Mar '12

24 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=694654 https://bugzilla.novell.com/show_bug.cgi?id=694654#c0 Summary: games: Bug in vdrift Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: prusnak(a)novell.com ReportedBy: zmi007(a)gmail.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- ~> zypper se vdrift Loading repository data... Reading installed packages... S | Name | Summary | Type --+---------------------+------------------------------------------------- i | vdrift | VDrift is a cross-platform, open source driving simulation | package | vdrift | VDrift is a cross-platform, open source driving simulation | srcpackage i | vdrift-data | Data files for VDrift | package i | vdrift-data-cars | Cars for VDrift | package i | vdrift-data-drivers | Drivers for VDrift | package i | vdrift-data-sounds | Sounds and music for VDrift | package i | vdrift-data-tracks | Tracks for VDrift | package -------------------------------------------- ~> zypper if vdrift Loading repository data... Reading installed packages... Information for package vdrift: Repository: @System Name: vdrift Version: 20100630-4.1 Arch: x86_64 Vendor: obs://build.opensuse.org/games Installed: Yes Status: up-to-date Installed Size: 3.5 MiB Summary: VDrift is a cross-platform, open source driving simulation Description: VDrift is a cross-platform, open source driving simulation made with drift racing in mind. It's powered by the excellent Vamos physics engine. -------------------------------------------- ~> vdrift INFO: Multi-processor system detected. Run with -multithreaded argument to enable multithreading (EXPERIMENTAL). INFO: Starting VDrift: 2011-04-26-full, Version: , O/S: Unix-like INFO: Home directory: /home/term INFO: Settings file: /home/term/.vdrift/VDrift.config (does not exist, will be created) INFO: Data directory: data DATA_DIR: /usr/share/vdrift/data INFO: Log file: /home/term/.vdrift/log.txt INFO: SDL initialization successful INFO: SDL video query was successful INFO: Disabling antialiasing INFO: Display change was successful: 800x600x16 24z fullscreen=0 INFO: Video card information: Vendor: ATI Technologies Inc. Renderer: ATI Mobility Radeon HD 2600 XT Version: 3.3.10600 Compatibility Profile Context Maximum texture size: 8192 Maximum varying floats: 128 Using GLEW 1.5.8 INFO: Maximum color attachments: 8 INFO: Maximum draw buffers (1 required): 8 INFO: Texture units: 8 full, 16 partial INFO: ----- Start Shader Compile Log for data/shaders/simple/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/simple/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/simple/vertex.glsl and data/shaders/simple/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package simple INFO: ----- Start Shader Compile Log for data/shaders/simple/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/simple/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/simple/vertex.glsl and data/shaders/simple/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package simple, variant simple_premult INFO: ----- Start Shader Compile Log for data/shaders/simple/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/simple/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/simple/vertex.glsl and data/shaders/simple/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package simple, variant simple_gamma_premult INFO: ----- Start Shader Compile Log for data/shaders/simple/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/simple/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/simple/vertex.glsl and data/shaders/simple/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package simple, variant simple_gamma INFO: ----- Start Shader Compile Log for data/shaders/simple/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/simple/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/simple/vertex.glsl and data/shaders/simple/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package simple, variant simplecar INFO: ----- Start Shader Compile Log for data/shaders/logluminance/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/logluminance/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/logluminance/vertex.glsl and data/shaders/logluminance/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package logluminance INFO: ----- Start Shader Compile Log for data/shaders/logluminance/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/logluminance/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/logluminance/vertex.glsl and data/shaders/logluminance/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package logluminance, variant logluminance_tiny INFO: ----- Start Shader Compile Log for data/shaders/tonemap/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/tonemap/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/tonemap/vertex.glsl and data/shaders/tonemap/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package tonemap INFO: ----- Start Shader Compile Log for data/shaders/gbufferfill/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/gbufferfill/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/gbufferfill/vertex.glsl and data/shaders/gbufferfill/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package gbufferfill INFO: ----- Start Shader Compile Log for data/shaders/gbufferfill/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/gbufferfill/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/gbufferfill/vertex.glsl and data/shaders/gbufferfill/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package gbufferfill, variant gbufferfillcar INFO: ----- Start Shader Compile Log for data/shaders/lightaccumulate/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/lightaccumulate/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/lightaccumulate/vertex.glsl and data/shaders/lightaccumulate/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package lightaccumulate, variant lightaccumulate_initial INFO: ----- Start Shader Compile Log for data/shaders/lightaccumulate/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/lightaccumulate/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/lightaccumulate/vertex.glsl and data/shaders/lightaccumulate/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package lightaccumulate, variant lightaccumulate_omni INFO: ----- Start Shader Compile Log for data/shaders/depthgen/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/depthgen/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/depthgen/vertex.glsl and data/shaders/depthgen/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package depthgen INFO: ----- Start Shader Compile Log for data/shaders/depthgen/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/depthgen/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/depthgen/vertex.glsl and data/shaders/depthgen/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package depthgen, variant depthgennoalpha INFO: ----- Start Shader Compile Log for data/shaders/distancefield/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/distancefield/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/distancefield/vertex.glsl and data/shaders/distancefield/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package distancefield INFO: ----- Start Shader Compile Log for data/shaders/deferredskybox/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/deferredskybox/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/deferredskybox/vertex.glsl and data/shaders/deferredskybox/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package deferredskybox INFO: ----- Start Shader Compile Log for data/shaders/deferredskyboxblend/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/deferredskyboxblend/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/deferredskyboxblend/vertex.glsl and data/shaders/deferredskyboxblend/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package deferredskyboxblend INFO: ----- Start Shader Compile Log for data/shaders/softparticle/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/softparticle/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/softparticle/vertex.glsl and data/shaders/softparticle/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package softparticle INFO: ----- Start Shader Compile Log for data/shaders/ppdepthadjust/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/ppdepthadjust/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/ppdepthadjust/vertex.glsl and data/shaders/ppdepthadjust/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package ppdepthadjust INFO: ----- Start Shader Compile Log for data/shaders/ppdepthadjust/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/ppdepthadjust/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/ppdepthadjust/vertex.glsl and data/shaders/ppdepthadjust/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package ppdepthadjust, variant ppcopy INFO: ----- Start Shader Compile Log for data/shaders/ppdepthadjust/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/ppdepthadjust/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/ppdepthadjust/vertex.glsl and data/shaders/ppdepthadjust/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package ppdepthadjust, variant ppcopy_gamma INFO: ----- Start Shader Compile Log for data/shaders/deferredshadows/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/deferredshadows/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/deferredshadows/vertex.glsl and data/shaders/deferredshadows/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package deferredshadows INFO: ----- Start Shader Compile Log for data/shaders/ssao/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/ssao/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/ssao/vertex.glsl and data/shaders/ssao/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package ssao INFO: ----- Start Shader Compile Log for data/shaders/ssao_blur/vertex.glsl ----- INFO: Vertex shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Compile Log for data/shaders/ssao_blur/fragment.glsl ----- INFO: Fragment shader was successfully compiled to run on hardware. INFO: ----- End Shader Compile Log ----- INFO: ----- Start Shader Link Log for data/shaders/ssao_blur/vertex.glsl and data/shaders/ssao_blur/fragment.glsl ----- INFO: Vertex shader(s) linked, fragment shader(s) linked. INFO: ----- End Shader Link Log ----- INFO: Loaded shader package ssao_blur INFO: Successfully enabled shaders INFO: Initialized render output: full_scene_depth (FBO) INFO: Initialized render output: full_scene_color (FBO) INFO: Initialized render output: normal_xy (FBO) INFO: Initialized render output: material_properties (FBO) INFO: Initialized render output: diffuse_albedo (FBO) INFO: Initialized render output: log_luminance (FBO) INFO: Initialized render output: log_luminance_tiny (FBO) INFO: Maximum anisotropy: 16 INFO: 0 joysticks found. INFO: Loading car controls from: /home/term/.vdrift/controls.config INFO: Sound initialization information: INFO: Obtained audio device: Frequency: 44100 Format: 32784 Bits per sample: 16 Channels: 2 Silence: 0 Samples: 940 Size: 3760 Sound initialization successful INFO: Loaded fonts successfully INFO: Loaded GUI successfully INFO: Loading track from path: data/tracks/paulricard88 INFO: Can't find surfaces configfile: data/tracks/paulricard88/surfaces.txt INFO: No Surfaces File. Continuing with standard surfaces INFO: Track timing sectors: 2 INFO: Track object list has 16 params per object, expected 17, this is fine, continuing INFO: Collision objects: 1 INFO: Car loading was successful: XS INFO: Car loading was successful: XS vdrift: include/cartelemetry.h:63: void CARTELEMETRY::Update(CARTELEMETRY::T): Assertion `file' failed. SIGABRT detected, releasing the mouse /usr/bin/vdrift: line 3: 911 Aborted ./bin/vdrift "$@" -- 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 708506] New: Opera Plugin Wrapper
by bugzilla_noreply＠novell.com 24 Mar '12

24 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=708506 https://bugzilla.novell.com/show_bug.cgi?id=708506#c0 Summary: Opera Plugin Wrapper Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: i386 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tatang75(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.112 Safari/534.30 pop up wondow always open upon start up of computer 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 4

[Bug 727204] New: Bash says running ifconfig may require root privileges but it is not true
by bugzilla_noreply＠novell.com 24 Mar '12

24 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=727204 https://bugzilla.novell.com/show_bug.cgi?id=727204#c0 Summary: Bash says running ifconfig may require root privileges but it is not true Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rbyshko(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:6.0) Gecko/20100101 Firefox/6.0 user@linux:~> ifconfig Absolute path to 'ifconfig' is '/sbin/ifconfig', so running it may require superuser privileges (eg. root). Same happens with route. However programs can be run given full path i.e. /sbin/ifconfig. That's why the above error message es extremely annoying. 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 5

[Bug 623420] New: psi fails while connecting to server
by bugzilla_noreply＠novell.com 24 Mar '12

24 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=623420 http://bugzilla.novell.com/show_bug.cgi?id=623420#c0 Summary: psi fails while connecting to server Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: i686 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: honza801(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.1 SUSE/6.0.443.0 (KHTML, like Gecko) Chrome/6.0.443.0 Safari/534.1 hi while starting psi it says: 3049023176:error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error:s23_clnt.c:658: and fails to connect i'm using psi-0.14-5.2.i586 Reproducible: Always Steps to Reproduce: 1. run psi from command line 2. try to connect server Actual Results: above error appears on the commandline and following appears in the dialog box There was an error communicating with the server. Details: TLS handshake error Expected Results: connect successfull on the server (openfire), i've found this message Caused by: javax.net.ssl.SSLException: Unexpected end of handshake data -- 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 10

[Bug 720183] New: Vulture (a graphical Nethack) aborts with "NULL not valid" error when playing as a wizard in Oracle room
by bugzilla_noreply＠novell.com 24 Mar '12

24 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=720183 https://bugzilla.novell.com/show_bug.cgi?id=720183#c0 Summary: Vulture (a graphical Nethack) aborts with "NULL not valid" error when playing as a wizard in Oracle room Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: nn.dm55(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=452842) --> (http://bugzilla.novell.com/attachment.cgi?id=452842) Error log from Vulture User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:6.0.2) Gecko/20100101 Firefox/6.0.2 As a level 7 elven wizard, I was fighting 3 gnomes and a water demon outside the Oracle room alongside my large cat after I talked to the Oracle two or three times. Then the game crashed. I am using version 2.3.67 of Vulture. Reproducible: Didn't try Steps to Reproduce: 1. 2. 3. Actual Results: The game crashed. Expected Results: The game should have been able to handle 3 gnomes and a water demon. -- 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 730880] New: Missing opera-gtk and opera-kde4 packages in 12.1
by bugzilla_noreply＠novell.com 24 Mar '12

24 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=730880 https://bugzilla.novell.com/show_bug.cgi?id=730880#c0 Summary: Missing opera-gtk and opera-kde4 packages in 12.1 Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: All OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: christian.wansart(a)gmx.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64; U; de) Presto/2.9.168 Version/11.52 Since openSUSE 12.1 there is no opera-gtk or opera-kde4 package in the repos, but those packages are required to use the native UI elements of KDE and GTK. In 11.4 there were additional packages opera-gtk and opera-kde4, the official RPM from opera.com contains the required libraries. Reproducible: Always Steps to Reproduce: 1. Start Opera Actual Results: Standard UI elements where used. Expected Results: In my case, Opera should use Qt elements instead. Either add those libraries to the opera package or add the packages opera-kde4 and opera-gtk. -- 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 556929] New: Gnome quick install guide - Firefox
by bugzilla_noreply＠novell.com 23 Mar '12

23 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=556929 http://bugzilla.novell.com/show_bug.cgi?id=556929#c0 Summary: Gnome quick install guide - Firefox Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: ke(a)novell.com ReportedBy: kkemenczy(a)novell.com QAContact: ke(a)novell.com Found By: --- Blocker: --- In the Firefox section: "When starting Firefox for the first time, you need to agree with its license agreement and click OK." these days there is a message row with "Know your rights..." button and this is not necessary to read, you can close it without. -- 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 555564] New: Gnome quick guide - background color
by bugzilla_noreply＠novell.com 23 Mar '12

23 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=555564 Summary: Gnome quick guide - background color Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: ke(a)novell.com ReportedBy: kkemenczy(a)novell.com QAContact: ke(a)novell.com Found By: --- "To display a colored background, select No Wallpaper from the top of the list; then, from Colors, select the fill pattern and the desired colors." There no list anymore and we cannot select No wallpaper, we can select the first picture, which is actually a simple color. -- 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 555563] New: Gnome quick guide - desktop search
by bugzilla_noreply＠novell.com 23 Mar '12

23 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=555563 Summary: Gnome quick guide - desktop search Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: ke(a)novell.com ReportedBy: kkemenczy(a)novell.com QAContact: ke(a)novell.com Found By: --- Created an attachment (id=327540) --> (http://bugzilla.novell.com/attachment.cgi?id=327540) beagle The desktop search is not starts by default. I think we have to add few sentence about how to start the desktop search. Please check the screenshot. By the way there is an untranslated message here... but this will be another bug. -- 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 551733] New: Gnome quickstart guide - evince
by bugzilla_noreply＠novell.com 23 Mar '12

23 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=551733 Summary: Gnome quickstart guide - evince Classification: openSUSE Product: openSUSE 11.2 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: ke(a)novell.com ReportedBy: kkemenczy(a)novell.com QAContact: ke(a)novell.com Found By: --- On page 6 of the Gnome quick start guide in the "Viewing PDF Files" section the 2th paragraph contains the following: "To start Evince, press Alt + F2 and enter evince or click Computer → More Applications → Office → Evince. 1. Click Computer → More Applications → Office → Evince or press Ctrl + F2 and enter evince. 2. To view a PDF file, click File → Open, locate the desired PDF file, then click Open." These should be something like this: "1. To start Evince, click Computer → More Applications → Office → Evince or press Ctrl + F2 and enter evince. 2. To view a PDF file, click File → Open, locate the desired PDF file, then click Open." -- 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 651922] New: GnuPG vs GPG
by bugzilla_noreply＠novell.com 23 Mar '12

23 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=651922 https://bugzilla.novell.com/show_bug.cgi?id=651922#c0 Summary: GnuPG vs GPG Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Documentation AssignedTo: ke(a)novell.com ReportedBy: kkemenczy(a)novell.com QAContact: ke(a)novell.com Found By: --- Blocker: --- It could confusing the reader the two different terminology. imho we have to use only one of them. we use GnuPG: * 1_click_install_i.xml * rpm.xml * yast2_sw_repo.xml * yast2_webpin.xml we use GPG: * utilities.xml * yast2_sw_addon.xml * yast2_sw_repo.xml the software translation also involved: yast, zypper -- 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 629335] New: patching win7 on dual boot weih opensuse 11.3 wipes out bootloader
by bugzilla_noreply＠novell.com 23 Mar '12

23 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=629335 http://bugzilla.novell.com/show_bug.cgi?id=629335#c0 Summary: patching win7 on dual boot weih opensuse 11.3 wipes out bootloader Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: ke(a)novell.com ReportedBy: doiggl(a)velocitynet.com.au QAContact: ke(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.11) Gecko/20100714 SUSE/2.0.6-0.1.1 SeaMonkey/2.0.6 Please add this to documentation section windows7 patching wiped out the existing opensuse setup / grub bootloader Repaired bootloader using this method grub grub> find /boot/grub/menu.ls > returned (hd0,1) grub> root (hd0,1) > returned Filesystem type is .... grub>setup (hd0) returned ....succeeded grub>quit reboot Opensuse boots ok Reproducible: Always Steps to Reproduce: applied windows 7 patches for win 7, the system was a dual bootes with opensuse 11.3. After patching win7 -reboot -grub failed to run - repair grub - reboot - grub now repaired/bootable it can start the operating system selected Actual Results: non booting system. Perhaps have an option to repair bootloader from installation dvd/cd ? Expected Results: would have been nice to have a bootable system but......failed. So It was manually repaired. Here is how it was repaired opensuse starts fine. grub grub> find /boot/grub/menu.ls > returned (hd0,1) grub> root (hd0,1) > returned Filesystem type is .... grub>setup (hd0) returned ....succeeded grub>quit reboot -- 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 543404] New: Provide documentation on setting up a ramdisk on booting opensuse
by bugzilla_noreply＠novell.com 23 Mar '12

23 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=543404 Summary: Provide documentation on setting up a ramdisk on booting opensuse Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 8 Platform: x86-64 OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Documentation AssignedTo: ke(a)novell.com ReportedBy: doiggl(a)velocitynet.com.au QAContact: ke(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-1.1 Firefox/3.5.3 Provide documentation on setting up a ramdisk on booting opensuse, perhaps have options for 15%, 20% or 25% of ram for ramdisk. Reproducible: Always Steps to Reproduce: 1. Documentation Enhancement -- 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 733167] New: zypper lp output nearly useless
by bugzilla_noreply＠novell.com 23 Mar '12

23 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=733167 https://bugzilla.novell.com/show_bug.cgi?id=733167#c0 Summary: zypper lp output nearly useless Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: All Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse-beta(a)cboltz.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- The output of "zypper lp" is nearly useless since openSUSE 12.1 :-( A screen dump is probably the best explanation: # zypper lp Loading repository data... Reading installed packages... Repository | Name | Version | Category | Status ------------+------------------+---------+-------------+------- update-12.1 | openSUSE-2011-16 | 1 | recommended | needed update-12.1 | openSUSE-2011-17 | 1 | recommended | needed update-12.1 | openSUSE-2011-21 | 1 | recommended | needed update-12.1 | openSUSE-2011-22 | 1 | recommended | needed update-12.1 | openSUSE-2011-25 | 1 | recommended | needed update-12.1 | openSUSE-2011-28 | 1 | recommended | needed update-12.1 | openSUSE-2011-29 | 1 | recommended | needed Very helpful information, right? ;-/ If possible, I'd like to have the patchnames from 11.x back, which at least somehow showed what a patch does. -- 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 592968] New: zypper patch should show patch summary
by bugzilla_noreply＠novell.com 23 Mar '12

23 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=592968 http://bugzilla.novell.com/show_bug.cgi?id=592968#c0 Summary: zypper patch should show patch summary Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: jkupec(a)novell.com ReportedBy: dmueller(a)novell.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- instead of just showing the patchfilename (which does not say anything relevant), zypper should list the summary of the patch (short_descr) instead in a list. -- 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 702205] New: RTL8111/8168B hard locking and rebooting machines when under heavy load
by bugzilla_noreply＠novell.com 22 Mar '12

22 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=702205 https://bugzilla.novell.com/show_bug.cgi?id=702205#c0 Summary: RTL8111/8168B hard locking and rebooting machines when under heavy load Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: Happy.Cerberus(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 When this network card (should apply to all cards from this family) is under heavy load (>20MB) it causes hard lockups and/or hard machine reboots. This issue is extremely hard to localize. There are either no errors, or the machine reboots to fast. Plus the actual errors are not very informative ("eth0 link up" is one of the "fatal errors"). Upstream reference: https://bugzilla.kernel.org/show_bug.cgi?id=32962 Ubuntu forum reference: http://ubuntuforums.org/showpost.php?p=10774353&postcount=18 Solution is to use the driver provided by Realtek. I spent two days hunting this problem. Reproducible: Always Steps to Reproduce: 1. do some network heavy stuff 2. watch your machine crash Actual Results: Machine reboots or hard locks. Expected Results: No problems should appear. Please even if you won't fix this soon, at least disable the problematic module, so that users will have some clue where to search, because this is a really, really, really annoying problem that is extremely hard to diagnose. -- 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 10

[Bug 722427] New: /usr/share/fonts-config/suse-hinting.conf.template: change hintfull to hintslight
by bugzilla_noreply＠novell.com 22 Mar '12

22 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=722427 https://bugzilla.novell.com/show_bug.cgi?id=722427#c0 Summary: /usr/share/fonts-config/suse-hinting.conf.template: change hintfull to hintslight Classification: openSUSE Product: openSUSE 12.1 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20100101 Firefox/7.0 /usr/share/fonts-config/suse-hinting.conf.template contains 'hintfull' as the default. hintfull has not worked in many years. hintslight is the only value that /actually/ works - and it makes a HUGE difference in the quality of the displayed fonts. Please change 'hintfull' to 'hintslight'. This is the 'fonts-config' package. Also, the 'fontconfig' package installs a file (/etc/fonts/local.conf.instsys) - really, it should install that file as /etc/fonts/local.conf and mark it as %config(noreplace) - otherwise, a user moves/copies local.conf.instsys to local.conf and local.conf is not tracked by the packaging system. It's a config file, it (may) be edited by the user, therefore it should be marked %config(noreplace). Thanks! 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 10

[Bug 718708] New: Cups hangs in endless loop
by bugzilla_noreply＠novell.com 22 Mar '12

22 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=718708 https://bugzilla.novell.com/show_bug.cgi?id=718708#c0 Summary: Cups hangs in endless loop Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: Printing AssignedTo: jsmeix(a)suse.com ReportedBy: werner(a)suse.com QAContact: jsmeix(a)suse.com Found By: Development Blocker: --- Enabling a printer after cups has started leads very often to the problem that the first print job reamins active but the printer never gets any data. Sometimes cleaning out all printer jobs and restarting cups with `rccups stop && rccups start´ does help. In the /var/log/cups/error_log I've found always the message: cupsdReadClient: 11 WAITING Closing on EOF always in the case of such a hanging but active printer job. This does not depend on the type of the job as it happens with text files, a2ps PS output, with jpegs, and as well with PS output from acroread or printed within acroread or xv. -- 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 732563] New: mount nfs can't work
by bugzilla_noreply＠novell.com 22 Mar '12

22 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=732563 https://bugzilla.novell.com/show_bug.cgi?id=732563#c0 Summary: mount nfs can't work Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bili(a)suse.com QAContact: qa(a)suse.de Found By: --- Blocker: --- When I mount nfs it prompt like below. $sudo mount -t nfs 147.2.207.240:/repo_a /laba/ Starting rpc.statd ... portmapper not running failed mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified When I start the rpcbind, it works fine. So should we change the default portmapper? $ sudo /etc/init.d/rpcbind start redirecting to systemctl -- 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 10

[Bug 620353] New: The beagle plugin is mismatched with the Firefox version.
by bugzilla_noreply＠novell.com 22 Mar '12

22 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=620353 http://bugzilla.novell.com/show_bug.cgi?id=620353#c0 Summary: The beagle plugin is mismatched with the Firefox version. Classification: openSUSE Product: openSUSE 11.3 Version: RC 2 Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Minor Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com ReportedBy: usedonlytosignup(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.2.4) Gecko/20100611 SUSE/3.6.4-3.2 Firefox/3.6.4 The version of beagle-firefox That installs does not work with the version of up to date version Firefox. It's probably just because nobody updated the compatibility meta data and that is all the change which would be needed but I haven't looked under the hood. Reproducible: Always Steps to Reproduce: 1.Install firefox and beagle-firefox 2.Load Firefox 3.Look in plugins list and it shows up as incompatible Actual Results: No beagle in firefox Expected Results: Beagle in 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 683796] New: The eigen2 library computes the wrong results
by bugzilla_noreply＠novell.com 21 Mar '12

21 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=683796 https://bugzilla.novell.com/show_bug.cgi?id=683796#c0 Summary: The eigen2 library computes the wrong results Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dav1dblunk3tt(a)hotmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.2.16) Gecko/20110319 SUSE/3.6.16-0.2.1 Firefox/3.6.16 Sorry scant details - my program using eigen2 started producing erroneous results after an upgrade to suse 11.3. Previous I was using eigen 2 from the eigen website (version eigen2-2.0.5.tar.bz2). After upgrading to suse 11.3 I used the version in the repos which compiled fine but generate erroneous results when performing this calculation: M.lu().solve(V,&A). The same code and same inputs still worked in matlab and also worked using eigen2-2.0.15 from the eigen website. Apologies for the scant information, since I fixed the problem with the new libraries from the eigen site I haven't gone back to investigate further. Reproducible: Always Steps to Reproduce: use the solve in the eigen2 library supplied in the 11.3 repos and get incorrect results. The results are wildly incorrect. Actual Results: The results are wildly incorrect Expected Results: The correct numerical results It will probably be fixed by using a newer version of eigen but this should be tested... -- 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 5

[Bug 730519] New: ddclient caching prevents update after ip change
by bugzilla_noreply＠novell.com 21 Mar '12

21 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=730519 https://bugzilla.novell.com/show_bug.cgi?id=730519#c0 Summary: ddclient caching prevents update after ip change Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: All OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Yarny(a)public-files.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 The initial update of a dyndns account works fine, but ddclient refuses to update this account again with a different ip. It seems that the new ip is "masked" by the old ip which is stored in the cache file. Reproducible: Always Steps to Reproduce: This can be done without a dyndns account or an internet connection. Install ddclient and socat. Create some temporary directory and cd into it. Run this script: ################################################################ testport=50000 cat >| response << eof HTTP/1.1 200 OK Cache-Control: no-cache Content-Type: text/plain Server: Microsoft-IIS/7.5 Date: $(date -R) Connection: close good 1.2.3.4 eof cat >| ddclient.conf << eof min-interval=1 protocol=dyndns2 server=127.0.0.1:${testport} login=yarny password=yarny a.b.c eof rm -f ./ddclient.cache socat tcp4-listen:${testport} 'gopen:response!!stdout' & sleep 2 ddclient \ -file ./ddclient.conf \ -cache ./ddclient.cache \ -nosyslog \ -daemon 0 \ -verbose \ -debug \ -ip 1.2.3.4 sleep 2 ddclient \ -file ./ddclient.conf \ -cache ./ddclient.cache \ -nosyslog \ -daemon 0 \ -verbose \ -debug \ -ip 1.2.3.5 ################################################################ Note: When I try to run this script again, socat complains that the port (50000 here) is blocked. If this happens to you also, you can either wait a minute or change the testport variable. Actual Results: SUCCESS: a.b.c: skipped: IP address was already set to 1.2.3.4. Expected Results: ddclient should try to update to 1.2.3.5 (which would fail of course unless one starts socat again). ddclient version: 3.8.0-13.14.1 perl version: 5.12.3-11.16.1 -- 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 10

[Bug 560929] New: $G_FILENAME_ENCODING not set correctly for csh users
by bugzilla_noreply＠novell.com 21 Mar '12

21 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=560929 http://bugzilla.novell.com/show_bug.cgi?id=560929#c0 Summary: $G_FILENAME_ENCODING not set correctly for csh users Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: wjones(a)fluke.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-6.1 Firefox/3.5.4 $G_FILENAME_ENCODING is set for csh users in /etc/profile.d/zzz-glib2.csh, which is provided by the glib2 package. The variable is set in a switch statement based on the value of $LANG, but none of the cases has a "breaksw". As a result, after the correct case is matched, execution falls through all the remaining cases. The final value of $G_FILENAME_ENCODING is alway set by the last case, "zu_ZA". If you speak Zulu and live in South Africa, that's probably OK. (Actually, the result is fairly reasonable for a lot of other users, but it's not right.) The corresponding logic in /etc/profile.d/zzz-glib2.sh works correctly -- each case is terminated by ";;". Reproducible: Always Steps to Reproduce: 1. Login with csh 2. echo $G_FILENAME_ENCODING Actual Results: $G_FILENAME_ENCODING = G_FILENAME_ENCODING=@locale,UTF-8,ISO-8859-1,CP1252 always. This is the appropriate value for $LANG = zu_ZA* Expected Results: $G_FILENAME_ENCODING should depend on $LANG. -- 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 3

[Bug 711363] New: File descriptor limits don't work in sysconfig
by bugzilla_noreply＠novell.com 21 Mar '12

21 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=711363 https://bugzilla.novell.com/show_bug.cgi?id=711363#c0 Summary: File descriptor limits don't work in sysconfig Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andysem(a)mail.ru QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1 If I set either hard or soft file descriptor limits in /etc/sysconfig editor in yast, the specified values aren't applied at system startup. Apparently, limit values are written to the /etc/sysconfig/ulimit but /etc/initscript fails to interpret them somehow. Reproducible: Always Steps to Reproduce: 1. Open yast, select /etc/sysconfig editor. 2. Navigate to System->Limits->HARDFDLIMIT or SOFTFDLIMIT. 3. Specify a non-default value (e.g. 8192). 4. Save and reboot. 5. After reboot open console and type "ulimit -a | grep 'open files'". Actual Results: The output indicates that the specified limits were not applied (in my case, the output was 1024 instead of 8192). Expected Results: The limits should apply after reboot. The current workaround is to force the limit in /etc/security/limits.conf file. -- 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 12

[Bug 645209] New: Open MPI: Please update to 1.5.0 (currently: 1.3.2)
by bugzilla_noreply＠novell.com 21 Mar '12

21 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=645209 https://bugzilla.novell.com/show_bug.cgi?id=645209#c0 Summary: Open MPI: Please update to 1.5.0 (currently: 1.3.2) Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: burnus(a)gmx.de QAContact: qa(a)suse.de CC: jjolly(a)novell.com Found By: --- Blocker: --- Current version is 1.3.2, just released is 1.5.0. http://www.open-mpi.org/community/lists/devel/2010/10/8585.php Download: http://www.open-mpi.org/software/ompi/v1.5/ Changes: http://svn.open-mpi.org/svn/ompi/branches/v1.5/NEWS Highlight changes (as found browsing the 1.3.2 -> 1.5.0 changelog) - Added many new MPI job process affinity options to mpirun. See the newly-updated mpirun(1) man page for details. - Added "knem" support: direct process-to-process copying for shared memory message passing. See http://runtime.bordeaux.inria.fr/knem/ and the README file for more details. - Added simplistic "libompitrace" contrib package. Using the MPI profiling interface, it essentially prints out to stderr when select MPI functions are invoked. - Update bundled VampirTrace to v5.8.2. - Add several notifier plugins (generally used when Open MPI detects system/network administrator-worthy problems); each have their own MCA parameters to govern their usage. See "ompi_info --param notifier <name>" for more details. - command to execute arbitrary commands (e.g., run a script). - file to send output to a file. - ftb to send output to the Fault Tolerant Backplane (see http://wiki.mcs.anl.gov/cifts/index.php/CIFTS) - hnp to send the output to mpirun. - smtp (requires libesmtp) to send an email. -- 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 549533] New: Screensaver always comes on after 4 mins
by bugzilla_noreply＠novell.com 21 Mar '12

21 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=549533 Summary: Screensaver always comes on after 4 mins Classification: openSUSE Product: openSUSE 11.2 Version: RC 1 Platform: i586 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jkotze(a)novell.com QAContact: qa(a)suse.de Found By: --- Clean install of openSuSE 11.2 RC1 on a Dell D620 laptop. First install was with Gnome and second install was with KDE. The problem was observed in both KDE and Gnome. Steps to reproduce: 1. Change screensaver timeout to 1 hour 2. Uncheck the lock screensaver option 3. Leave the machine alone for 10 mins Result: Screensaver activates after 4 minutes Expected Result: Screensaver should only activate after 1 hour -- 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 8

[Bug 560941] New: $XDG_CONFIG_DIRS not set correctly for csh users.
by bugzilla_noreply＠novell.com 20 Mar '12

20 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=560941 http://bugzilla.novell.com/show_bug.cgi?id=560941#c0 Summary: $XDG_CONFIG_DIRS not set correctly for csh users. Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: All OS/Version: openSUSE 11.2 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: wjones(a)fluke.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-6.1 Firefox/3.5.4 $XDG_CONFIG_DIRS is set for csh users here: /etc/profile.d/xdg-environment.csh The logic doesn't match the corresponding startup file for bash users, and as a result, extra (probably irrelevant) directories are included. Reproducible: Always Steps to Reproduce: 1. Login with csh. 2. echo $XDG_CONFIG_DIRS 3. Login with bash. 4. echo $XDG_CONFIG_DIRS 5. Compare results. Actual Results: $XDG_CONFIG_DIRS contains extra directories under csh. Expected Results: Csh environment should be same as bash environment. This patch to xdg-environment.csh duplicates the logic in xdg-environment.sh: 8c8 < if ( -d "$xdgdir" ) then --- > if ( -d "$xdgdir" && -d "$xdgdir/applications" ) then -- 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 3

[Bug 623106] New: iPod/iPhone not detected properly on KDE but works on Gnome
by bugzilla_noreply＠novell.com 20 Mar '12

20 Mar '12

http://bugzilla.novell.com/show_bug.cgi?id=623106 http://bugzilla.novell.com/show_bug.cgi?id=623106#c0 Summary: iPod/iPhone not detected properly on KDE but works on Gnome Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: mobile-bugs(a)forge.provo.novell.com ReportedBy: ash25.icon(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64; U; en) Presto/2.6.30 Version/10.60 I connected my Apple iPod touch 3G using the USB cable to my PC. It is detected properly on Gnome. I'm able to browse the files in it and Rhythmbox is able to show the music on the ipod. But on KDE neither of these two work. Another person is facing the same problem with his iPhone over here: http://forums.opensuse.org/english/get-help-here/hardware/442064-opensuse-1… Reproducible: Always Steps to Reproduce: 1. Login into a KDE session 2. Connect USB cable from iPod to PC 3. Check for any newly mounted devices 4. Open up Rhythmbox to check for any iPod/iPhone detected Actual Results: Device notifier only gives options for opening with Digikam but no option to browse the files. Rhythmbox does not show any connected devices either. Expected Results: The files in iPod/iPhone should be viewable in Dolphin or equivalent. Rhythmbox should show iPod/iPhone and all the songs present on the device. These two are very much the results with Gnome. So KDE session should also give the same results. -- 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 9

[Bug 730561] New: konsole inserts random deletes/cursor left key events after a while
by bugzilla_noreply＠novell.com 20 Mar '12

20 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=730561 https://bugzilla.novell.com/show_bug.cgi?id=730561#c0 Summary: konsole inserts random deletes/cursor left key events after a while Classification: openSUSE Product: openSUSE 11.2 Version: RC 2 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: bernd.paysan(a)gmx.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.120 Safari/535.2 After a while, konsole randomly inserts deletes or cursor left key strokes into the input stream. Restarting konsole fixes the problem for a while. Reproducible: Always Steps to Reproduce: 1. Start Konsole 2. Use it for some time 3. Get annoyed by little gnarls inserting random delete/cursor left keys Actual Results: Random delete and cursor left keys inserted into keyboard input stream Expected Results: Only keys pressed on the keyboard I use scim as IME. -- 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 677860] New: /etc/mime.types lacks Microsoft Office 2007 file types
by bugzilla_noreply＠novell.com 20 Mar '12

20 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=677860 https://bugzilla.novell.com/show_bug.cgi?id=677860#c0 Summary: /etc/mime.types lacks Microsoft Office 2007 file types Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Markus.Kuhn(a)cl.cam.ac.uk QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=418175) --> (http://bugzilla.novell.com/attachment.cgi?id=418175) patch to add Microsoft Office 2007 file extensions to /etc/mime.types User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.2.14) Gecko/20110221 Ubuntu/10.04 (lucid) Firefox/3.6.14 Eight widely used filename extensions introduced by Microsoft Office 2007 are missing in file /etc/mime.types in package aaa_base. This causes problems if such files are downloaded by Windows/Office users from an openSUSE 11.3 Apache server. Reproducible: Always Steps to Reproduce: 1. Place a Microsoft Office 2007 Word file with *.docx extension onto a web site hosted by the out-of-the-box openSUSE 11.3 Apache web server 2. Access this file using Internet Explorer 8 from Windows XP with Office 2007 installed 3. Use "curl -I <url>" to check the Content-Type HTTP header line in the response. Actual Results: Internet Explorer offers to unzip the file, showing the user the XML inner guts of a *.docx file, rather than the expected Word document. The curl -I test shows that Apache serves the *.docx file with the incorrect HTTP header line "Content-Type: text/plain". Expected Results: The correct HTTP header line "Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document" should have been used by Apache for a *.docx file, which would have caused Internet Explorer to start Microsoft Word to open the file. The cause of the problem was easily identified: The now widely used "Office Open XML" document filename extensions of Microsoft Office 2007 (*.docx, *.pptx, etc.) are not known to Apache, because they are missing in /etc/mime.types. This causes the incorrect MIME type text/plain to be returned in the HTTP header if a user downloads a *.docx file from an openSUSE 11.3 Apache server, leading to undesirable behaviour in Windows web browsers. Solution: Please add to the file /etc/mime.types in the aaa_base package the following eight lines: application/vnd.openxmlformats-officedocument.presentationml.presentation pptx application/vnd.openxmlformats-officedocument.presentationml.slide sldx application/vnd.openxmlformats-officedocument.presentationml.slideshow ppsx application/vnd.openxmlformats-officedocument.presentationml.template potx application/vnd.openxmlformats-officedocument.spreadsheetml.sheet xlsx application/vnd.openxmlformats-officedocument.spreadsheetml.template xltx application/vnd.openxmlformats-officedocument.wordprocessingml.document docx application/vnd.openxmlformats-officedocument.wordprocessingml.template dotx A patch to do this is attached. (alphabetical sorting order is preserved) References: http://support.microsoft.com/kb/936496 http://www.iana.org/assignments/media-types/ -- 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 684588] New: nginx package dependency includes nginx
by bugzilla_noreply＠novell.com 20 Mar '12

20 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=684588 https://bugzilla.novell.com/show_bug.cgi?id=684588#c0 Summary: nginx package dependency includes nginx Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86 URL: http://library.linode.com OS/Version: openSUSE 11.4 Status: NEW Severity: Minor Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sam(a)linode.com QAContact: qa(a)suse.de Found By: Customer Blocker: --- opensuse:~ # zypper install nginx-0.8 Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW packages are going to be installed: apache2 apache2-itk apache2-utils fontconfig gd libapr-util1 libapr1 libfreetype6 libjpeg62 libpng14-14 libxslt make nginx-0.8 ruby ruby-devel rubygem-daemon_controller rubygem-fastthread rubygem-file-tail rubygem-passenger rubygem-passenger-nginx rubygem-rack rubygem-rake rubygem-spruz rubygems xorg-x11-libICE xorg-x11-libSM xorg-x11-libX11 xorg-x11-libXau xorg-x11-libXext xorg-x11-libXpm xorg-x11-libXt xorg-x11-libxcb 32 new packages to install. Overall download size: 13.8 MiB. After the operation, additional 50.2 MiB will be used. Continue? [y/n/?] (y): ----- I think the fix is rudimentary and simple, but I don't have access or contact information for the packager/developer in question. I'm available as "tychoish" on freenode and oftc. -- 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 724164] New: logwatch won't start with service dmeventd due to missing username in cron.d entry
by bugzilla_noreply＠novell.com 20 Mar '12

20 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=724164 https://bugzilla.novell.com/show_bug.cgi?id=724164#c0 Summary: logwatch won't start with service dmeventd due to missing username in cron.d entry Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: All OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sven(a)uebelacker.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20100101 Firefox/7.0 logwatch won't start with service dmeventd due to missing username in cron entry in logwatch-7.3.6-78.82.1.noarch /etc/cron.d/dmeventd says: 0-59 * * * * /usr/sbin/logwatch --service dmeventd missing the username for a cron.d entry. So, you'll get every time in /var/log/messages: /usr/sbin/cron[2110]: (CRON) bad username (/etc/cron.d/dmeventd) 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 17

[Bug 669125] New: include reason in del notifications
by bugzilla_noreply＠novell.com 20 Mar '12

20 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=669125 https://bugzilla.novell.com/show_bug.cgi?id=669125#c0 Summary: include reason in del notifications Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Hermes AssignedTo: freitag(a)novell.com ReportedBy: lnussel(a)novell.com QAContact: adrian(a)novell.com Found By: --- Blocker: --- package delete notification do not contain the reason why a package got removed. If the deletion was caused by a submit request the text of the request could be included in the notification. -- 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 10

[Bug 727923] New: bluedevil (bluez?) not handling PIN code properly; can't register remote device
by bugzilla_noreply＠novell.com 19 Mar '12

19 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=727923 https://bugzilla.novell.com/show_bug.cgi?id=727923#c0 Summary: bluedevil (bluez?) not handling PIN code properly; can't register remote device Classification: openSUSE Product: openSUSE 12.1 Version: RC 1 Platform: x86 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: howard.bryan.webb(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 opensuse 12.1 RC1 bluedevil-1.2.1-1.1 bluez-4.96-5.1 There is definitely a problem with bluedevil, and there is probably a problem with bluez. If there is a problem with bluez, pls forward to those developers for a complete resolution to this problem. Reproducible: Always Steps to Reproduce: 0) While the sequence below is performed... 0A) Run hcidump -t -X in one console 0B) Run tail -f /var/log/messages in a another console 1) Plug bluetooth class 2 bluetooth adapter (hci0) -- bluedevil icon appears in system tray 2) Click on bluedevil icon 2A) Click on "Configure Bluetooth" menu item 2B) "Configure the known Bluetooth remote devices" popup appears -- no devices are listed 3) Click on "Click here to add a remote device" widget 3A) "Bluetooth Device Wizard" (BDW) popup appears -- says "Scanning..." -- no devices are listed 4) Turn on remote bluetooth device -- device is detected during the next scan cycle on hcidump console -- BDW popup displays an icon labeled with the MAC addr of the remote dev -- icon is re-labeled with the remote device name "NXT", MAC addr is gone 5) Select the BDW window NXT icon (now highlighted) 6) Type <Alt-M> to the BDW window, asserts the "Manual PIN" checkbox 7) Type Tab Key, now in PIN field 8) Type in PIN "1234" 9) Type <Alt-N> (i.e. click the Next button) -- BDW wizard now displays "Please introduce the PIN in your device..." -- BDW wizard now also displays Cancel btn 10) Remote device presents confirmation to use PIN "1234" -- Click OK/Accept on Remote Device --------------------------------------- -- BDW popup "Please introduce the PIN..." stays displayed (forever) 11) Click BDW popup Cancel btn 12) Original "Configure the known Bluetooth..." popup has not added NXT device -- Options are OK, Cancel Actual Results: see above, below the --------------------- line Expected Results: 1) According to hcidump, due to some error or other, there was no pairing. hci0 and the remote device should have paired. 2) Should there be a pairing failure, Bluedevil's BDW popup "Please introduce the PIN..." should not stay displayed. Something like a "Pairing Failure" due to protocol error, or incorrect PIN, or whatever should be displayed. Below, is the preceding sequence of steps interspersed with hcidump output and /var/log/messages output. 1) Plug bluetooth class 2 bluetooth adapter (hci0) -- bluedevil icon appears in system tray Nov 2 15:29:00 t4 kernel: [11062.428447] usb 1-1.3: new full speed USB device number 15 using ehci_hcd Nov 2 15:29:00 t4 kernel: [11062.525273] usb 1-1.3: New USB device found, idVendor=0a5c, idProduct=2101 Nov 2 15:29:00 t4 kernel: [11062.525279] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Nov 2 15:29:00 t4 kernel: [11062.525283] usb 1-1.3: Product: BCM92045DG-Flash Nov 2 15:29:00 t4 kernel: [11062.525287] usb 1-1.3: Manufacturer: Broadcom Corp Nov 2 15:29:00 t4 bluetoothd[3722]: Bluetooth daemon 4.96 Nov 2 15:29:00 t4 bluetoothd[3724]: Starting SDP server Nov 2 15:29:00 t4 bluetoothd[3724]: D-Bus failed to register org.bluez.Proximity interface Nov 2 15:29:00 t4 bluetoothd[3724]: Parsing /etc/bluetooth/input.conf failed: No such file or directory Nov 2 15:29:00 t4 bluetoothd[3724]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory Nov 2 15:29:00 t4 bluetoothd[3724]: Listening for HCI events on hci0 Nov 2 15:29:00 t4 bluetoothd[3724]: HCI dev 0 up Nov 2 15:29:00 t4 bluetoothd[3724]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory Nov 2 15:29:00 t4 bluetoothd[3724]: Adapter /org/bluez/3722/hci0 has been enabled Nov 2 15:29:00 t4 pulseaudio[4135]: [pulseaudio] bluetooth-util.c: Error from RegisterEndpoint reply: org.freedesktop.DBus.Error.UnknownMethod Nov 2 15:29:00 t4 pulseaudio[4135]: [pulseaudio] bluetooth-util.c: Error from RegisterEndpoint reply: org.freedesktop.DBus.Error.UnknownMethod Nov 2 15:29:00 t4 pulseaudio[4135]: [pulseaudio] bluetooth-util.c: Error from RegisterEndpoint reply: org.freedesktop.DBus.Error.UnknownMethod Nov 2 15:29:00 t4 bluetoothd[3724]: Inquiry Cancel Failed with status 0x12 2011-11-02 15:29:00.547111 > HCI Event: Command Complete (0x0e) plen 252 Read Local Name (0x03|0x0014) ncmd 1 status 0x00 name 'BCM92045DG-Flash' 2011-11-02 15:29:00.547170 < HCI Command: Read Voice Setting (0x03|0x0025) plen 0 2011-11-02 15:29:00.548110 > HCI Event: Command Complete (0x0e) plen 6 Read Voice Setting (0x03|0x0025) ncmd 1 status 0x00 voice setting 0x0060 2011-11-02 15:29:00.548159 < HCI Command: Set Event Filter (0x03|0x0005) plen 1 type 0 condition 0 Clear all filters 2011-11-02 15:29:00.549119 > HCI Event: Command Complete (0x0e) plen 4 Set Event Filter (0x03|0x0005) ncmd 1 status 0x00 2011-11-02 15:29:00.549161 < HCI Command: Write Connection Accept Timeout (0x03|0x0016) plen 2 timeout 32000 2011-11-02 15:29:00.550129 > HCI Event: Command Complete (0x0e) plen 4 Write Connection Accept Timeout (0x03|0x0016) ncmd 1 status 0x00 2011-11-02 15:29:00.550225 < HCI Command: Delete Stored Link Key (0x03|0x0012) plen 7 bdaddr 00:00:00:00:00:00 all 1 2011-11-02 15:29:00.552117 > HCI Event: Command Complete (0x0e) plen 4 Delete Stored Link Key (0x03|0x0012) ncmd 1 status 0x11 deleted 0 Error: Unsupported Feature or Parameter Value 2011-11-02 15:29:00.552154 < HCI Command: Set Event Mask (0x03|0x0001) plen 8 Mask: 0xfffffbff07180000 2011-11-02 15:29:00.553113 > HCI Event: Command Complete (0x0e) plen 4 Set Event Mask (0x03|0x0001) ncmd 1 status 0x00 2011-11-02 15:29:00.553146 < HCI Command: Read Local Supported Commands (0x04|0x0002) plen 0 2011-11-02 15:29:00.559110 > HCI Event: Command Complete (0x0e) plen 68 Read Local Supported Commands (0x04|0x0002) ncmd 1 status 0x00 Commands: ffffffffffff1ffffffffffff30fffff3f 2011-11-02 15:29:00.559155 < HCI Command: Write Inquiry Mode (0x03|0x0045) plen 1 mode 1 2011-11-02 15:29:00.560104 > HCI Event: Command Complete (0x0e) plen 4 Write Inquiry Mode (0x03|0x0045) ncmd 1 status 0x00 2011-11-02 15:29:00.560128 < HCI Command: Read Local Extended Features (0x04|0x0004) plen 1 page 1 2011-11-02 15:29:00.561109 > HCI Event: Command Complete (0x0e) plen 14 Read Local Extended Features (0x04|0x0004) ncmd 1 status 0x00 page 1 max 0 Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 2011-11-02 15:29:00.561145 < HCI Command: Write Default Link Policy Settings (0x02|0x000f) plen 2 policy 0x0f Link policy: RSWITCH HOLD SNIFF PARK 2011-11-02 15:29:00.562120 > HCI Event: Command Complete (0x0e) plen 4 Write Default Link Policy Settings (0x02|0x000f) ncmd 1 status 0x00 2011-11-02 15:29:00.599771 < HCI Command: Read Local Version Information (0x04|0x0001) plen 0 2011-11-02 15:29:00.601097 > HCI Event: Command Complete (0x0e) plen 12 Read Local Version Information (0x04|0x0001) ncmd 1 status 0x00 HCI Version: 2.0 (0x3) HCI Revision: 0x204d LMP Version: 2.0 (0x3) LMP Subversion: 0x4127 Manufacturer: Broadcom Corporation (15) 2011-11-02 15:29:00.601130 < HCI Command: Write Page Timeout (0x03|0x0018) plen 2 timeout 8192 2011-11-02 15:29:00.602105 > HCI Event: Command Complete (0x0e) plen 4 Write Page Timeout (0x03|0x0018) ncmd 1 status 0x00 2011-11-02 15:29:00.602188 < HCI Command: Read Stored Link Key (0x03|0x000d) plen 7 bdaddr 00:00:00:00:00:00 all 1 2011-11-02 15:29:00.603100 > HCI Event: Command Complete (0x0e) plen 4 Read Stored Link Key (0x03|0x000d) ncmd 1 status 0x11 max 0 num 256 Error: Unsupported Feature or Parameter Value 2011-11-02 15:29:00.654668 < HCI Command: Write Local Name (0x03|0x0013) plen 248 name 't4-0' 2011-11-02 15:29:00.657089 > HCI Event: Command Complete (0x0e) plen 4 Write Local Name (0x03|0x0013) ncmd 1 status 0x00 2011-11-02 15:29:00.658477 < HCI Command: Set Event Mask (0x03|0x0001) plen 8 Mask: 0xfffffbff07180000 2011-11-02 15:29:00.660097 > HCI Event: Command Complete (0x0e) plen 4 Set Event Mask (0x03|0x0001) ncmd 1 status 0x00 2011-11-02 15:29:00.660166 < HCI Command: Write Inquiry Mode (0x03|0x0045) plen 1 mode 1 2011-11-02 15:29:00.662099 > HCI Event: Command Complete (0x0e) plen 4 Write Inquiry Mode (0x03|0x0045) ncmd 1 status 0x00 2011-11-02 15:29:00.662262 < HCI Command: Write Default Link Policy Settings (0x02|0x000f) plen 2 policy 0x0f Link policy: RSWITCH HOLD SNIFF PARK 2011-11-02 15:29:00.664091 > HCI Event: Command Complete (0x0e) plen 4 Write Default Link Policy Settings (0x02|0x000f) ncmd 1 status 0x00 2011-11-02 15:29:00.664131 < HCI Command: Write Local Name (0x03|0x0013) plen 248 name 't4-0' 2011-11-02 15:29:00.666078 > HCI Event: Command Complete (0x0e) plen 4 Write Local Name (0x03|0x0013) ncmd 1 status 0x00 2011-11-02 15:29:00.666206 < HCI Command: Write Class of Device (0x03|0x0024) plen 3 class 0x480100 2011-11-02 15:29:00.667080 > HCI Event: Command Complete (0x0e) plen 4 Write Class of Device (0x03|0x0024) ncmd 1 status 0x00 2011-11-02 15:29:00.667102 < HCI Command: Write Scan Enable (0x03|0x001a) plen 1 enable 2 2011-11-02 15:29:00.669078 > HCI Event: Command Complete (0x0e) plen 4 Write Scan Enable (0x03|0x001a) ncmd 1 status 0x00 2011-11-02 15:29:00.672677 < HCI Command: Inquiry Cancel (0x01|0x0002) plen 0 2011-11-02 15:29:00.674090 > HCI Event: Command Complete (0x0e) plen 4 Inquiry Cancel (0x01|0x0002) ncmd 1 status 0x12 Error: Invalid HCI Command Parameters 2011-11-02 15:29:00.674172 < HCI Command: Read Local Name (0x03|0x0014) plen 0 2011-11-02 15:29:00.691094 > HCI Event: Command Complete (0x0e) plen 252 Read Local Name (0x03|0x0014) ncmd 1 status 0x00 name 't4-0' 2011-11-02 15:29:00.691139 < HCI Command: Read Local Name (0x03|0x0014) plen 0 2011-11-02 15:29:00.708088 > HCI Event: Command Complete (0x0e) plen 252 Read Local Name (0x03|0x0014) ncmd 1 status 0x00 name 't4-0' 2011-11-02 15:29:00.708149 < HCI Command: Read Scan Enable (0x03|0x0019) plen 0 2011-11-02 15:29:00.709083 > HCI Event: Command Complete (0x0e) plen 5 Read Scan Enable (0x03|0x0019) ncmd 1 status 0x00 enable 2 2011-11-02 15:29:00.709131 < HCI Command: Write Class of Device (0x03|0x0024) plen 3 class 0x580100 2011-11-02 15:29:00.710084 > HCI Event: Command Complete (0x0e) plen 4 Write Class of Device (0x03|0x0024) ncmd 1 status 0x00 2) Click on bluedevil icon 2A) Click on "Configure Bluetooth" menu item 2B) "Configure the known Bluetooth remote devices" popup appears -- no devices are listed 3) Click on "Click here to add a remote device" widget 3A) "Bluetooth Device Wizard" (BDW) popup appears -- says "Scanning..." -- no devices are listed Nov 2 15:38:31 t4 bluetoothd[3724]: Discovery session 0xb7794140 with :1.85 activated 2011-11-02 15:38:31.030276 < HCI Command: Inquiry (0x01|0x0001) plen 5 lap 0x9e8b33 len 8 num 0 2011-11-02 15:38:31.032151 > HCI Event: Command Status (0x0f) plen 4 Inquiry (0x01|0x0001) status 0x00 ncmd 1 2011-11-02 15:38:41.268442 > HCI Event: Inquiry Complete (0x01) plen 1 status 0x00 2011-11-02 15:39:11.998166 < HCI Command: Inquiry (0x01|0x0001) plen 5 lap 0x9e8b33 len 8 num 0 2011-11-02 15:39:12.000321 > HCI Event: Command Status (0x0f) plen 4 Inquiry (0x01|0x0001) status 0x00 ncmd 1 2011-11-02 15:39:22.228633 > HCI Event: Inquiry Complete (0x01) plen 1 status 0x00 4) Turn on remote bluetooth device -- device is detected during the next scan cycle on hcidump console 2011-11-02 15:41:55.022190 < HCI Command: Inquiry (0x01|0x0001) plen 5 lap 0x9e8b33 len 8 num 0 2011-11-02 15:41:55.024184 > HCI Event: Command Status (0x0f) plen 4 Inquiry (0x01|0x0001) status 0x00 ncmd 1 2011-11-02 15:41:57.601748 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 bdaddr 00:16:53:01:D5:43 mode 1 clkoffset 0x2315 class 0x000804 rssi -46 2011-11-02 15:41:58.241641 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 bdaddr 00:16:53:01:D5:43 mode 1 clkoffset 0x2314 class 0x000804 rssi -50 2011-11-02 15:41:58.772570 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 bdaddr 00:16:53:01:D5:43 mode 1 clkoffset 0x2314 class 0x000804 rssi -52 2011-11-02 15:41:59.083501 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 bdaddr 00:16:53:01:D5:43 mode 1 clkoffset 0x2315 class 0x000804 rssi -49 2011-11-02 15:41:59.234482 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 bdaddr 00:16:53:01:D5:43 mode 1 clkoffset 0x2314 class 0x000804 rssi -50 2011-11-02 15:41:59.265470 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 bdaddr 00:16:53:01:D5:43 mode 1 clkoffset 0x2315 class 0x000804 rssi -48 2011-11-02 15:41:59.325460 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 bdaddr 00:16:53:01:D5:43 mode 1 clkoffset 0x2314 class 0x000804 rssi -50 2011-11-02 15:41:59.606415 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 bdaddr 00:16:53:01:D5:43 mode 1 clkoffset 0x2315 class 0x000804 rssi -48 2011-11-02 15:41:59.897381 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 bdaddr 00:16:53:01:D5:43 mode 1 clkoffset 0x2315 class 0x000804 rssi -53 2011-11-02 15:41:59.937364 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 bdaddr 00:16:53:01:D5:43 mode 1 clkoffset 0x2314 class 0x000804 rssi -58 2011-11-02 15:42:02.739892 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 bdaddr 00:16:53:01:D5:43 mode 1 clkoffset 0x2315 class 0x000804 rssi -52 2011-11-02 15:42:03.089834 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 bdaddr 00:16:53:01:D5:43 mode 1 clkoffset 0x2314 class 0x000804 rssi -55 2011-11-02 15:42:03.360799 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 bdaddr 00:16:53:01:D5:43 mode 1 clkoffset 0x2315 class 0x000804 rssi -52 2011-11-02 15:42:03.742725 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 bdaddr 00:16:53:01:D5:43 mode 1 clkoffset 0x2315 class 0x000804 rssi -51 2011-11-02 15:42:04.332627 > HCI Event: Inquiry Result with RSSI (0x22) plen 15 bdaddr 00:16:53:01:D5:43 mode 1 clkoffset 0x2314 class 0x000804 rssi -57 2011-11-02 15:42:05.259502 > HCI Event: Inquiry Complete (0x01) plen 1 status 0x00 2011-11-02 15:42:05.260005 < HCI Command: Remote Name Request (0x01|0x0019) plen 10 bdaddr 00:16:53:01:D5:43 mode 2 clkoffset 0x0000 2011-11-02 15:42:05.261488 > HCI Event: Command Status (0x0f) plen 4 Remote Name Request (0x01|0x0019) status 0x00 ncmd 1 2011-11-02 15:42:08.337960 > HCI Event: Remote Name Req Complete (0x07) plen 255 status 0x00 bdaddr 00:16:53:01:D5:43 name 'NXT' -- BDW popup displays an icon labeled with the MAC addr of the remote dev -- icon is re-labeled with the remote device name "NXT", MAC addr is gone 5) Select the BDW window NXT icon (now highlighted) 6) Type <Alt-M> to the BDW window, asserts the "Manual PIN" checkbox 7) Type Tab Key, now in PIN field 8) Type in PIN "1234" 9) Type <Alt-N> (i.e. click the Next button) Nov 2 15:42:16 t4 bluetoothd[3724]: Stopping discovery 2011-11-02 15:42:16.401849 < HCI Command: Create Connection (0x01|0x0005) plen 13 bdaddr 00:16:53:01:D5:43 ptype 0xcc18 rswitch 0x01 clkoffset 0x2314 (valid) Packet type: DM1 DM3 DM5 DH1 DH3 DH5 2011-11-02 15:42:16.403643 > HCI Event: Command Status (0x0f) plen 4 Create Connection (0x01|0x0005) status 0x00 ncmd 1 -- BDW wizard now displays "Please introduce the PIN in your device..." -- BDW wizard now also displays Cancel btn 10) Remote device presents confirmation to use PIN "1234" 2011-11-02 15:42:18.502281 > HCI Event: Link Key Request (0x17) plen 6 bdaddr 00:16:53:01:D5:43 2011-11-02 15:42:18.502432 < HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6 bdaddr 00:16:53:01:D5:43 2011-11-02 15:42:18.504277 > HCI Event: Command Complete (0x0e) plen 10 Link Key Request Negative Reply (0x01|0x000c) ncmd 1 status 0x00 bdaddr 00:16:53:01:D5:43 -- Click OK/Accept on Remote Device <----------------------------------------------- 2011-11-02 15:42:25.564107 > HCI Event: PIN Code Request (0x16) plen 6 bdaddr 00:16:53:01:D5:43 2011-11-02 15:42:35.804201 < HCI Command: PIN Code Request Negative Reply (0x01|0x000e) plen 6 bdaddr 00:16:53:01:D5:43 2011-11-02 15:42:35.805404 > HCI Event: Command Complete (0x0e) plen 10 PIN Code Request Negative Reply (0x01|0x000e) ncmd 1 status 0x00 bdaddr 00:16:53:01:D5:43 2011-11-02 15:42:35.982371 > HCI Event: Connect Complete (0x03) plen 11 status 0x06 handle 11 bdaddr 00:16:53:01:D5:43 type ACL encrypt 0x00 Error: PIN or Key Missing Nov 2 15:42:35 t4 bluetoothd[3724]: Invalid PIN length (0) from agent Nov 2 15:42:35 t4 bluetoothd[3724]: 00:16:53:01:D5:43: error updating services: Invalid exchange (52) -- 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 693617] New: Konqueror crashes switching from KDE Developer profile to Midnight Commander profile
by bugzilla_noreply＠novell.com 19 Mar '12

19 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=693617 https://bugzilla.novell.com/show_bug.cgi?id=693617#c0 Summary: Konqueror crashes switching from KDE Developer profile to Midnight Commander profile Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: giecrilj(a)stegny.2a.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=429528) --> (http://bugzilla.novell.com/attachment.cgi?id=429528) backtrace User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 Konqueror crashes switching from KDE Developer profile to Midnight Commander profile. Reproducible: Always Steps to Reproduce: 1. Tell Konqueror to use KDE Developer profile. 2. Tell Konqueror to use the Midnight Commander profile. Actual Results: 1. Konqueror uses the KDE Developer profile. 2. Crash! Expected Results: 2. Let Konqueror use the Midnight Commander profile. This bug is FIXED upstream. -- 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 687815] New: Mark taskbar entry in konsole for visible sessions doesn't seem to work
by bugzilla_noreply＠novell.com 19 Mar '12

19 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=687815 https://bugzilla.novell.com/show_bug.cgi?id=687815#c0 Summary: Mark taskbar entry in konsole for visible sessions doesn't seem to work Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: dav1dblunk3tt(a)hotmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.2.16) Gecko/20110319 SUSE/3.6.16-0.2.1 Firefox/3.6.16 If I set the notifications in konsole to makr the task bar entry for visible and non visible sessions for bells then the taskbar is marked if the session is minimised (non visible) but is not marked if the session is visible. Reproducible: Always Steps to Reproduce: Set "mark taskbar entry" for visible sessions Produce a bell in the session Taskbar entry is not marked Actual Results: Taskbar entry is not marked Expected Results: Taskbar entry should be marked -- 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 678896] New: Synaptiks - Synaptics touchpad daemon in KDE4 don't see USB mouse
by bugzilla_noreply＠novell.com 19 Mar '12

19 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=678896 https://bugzilla.novell.com/show_bug.cgi?id=678896#c0 Summary: Synaptiks - Synaptics touchpad daemon in KDE4 don't see USB mouse Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: All OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: zarko.pintar(a)inet.hr QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.127 Safari/534.16 If you wish to setup synaptics daemon in KDE4 Settings that disable touchpad when user attach and using USB mouse, nothing happened. This is because this (Synaptiks) KDE4 setting's module depend on HAL, but HAL is abandoned in OpenSuse 11.4 You must package version 0.5 or higher of Synaptiks, so it can use udev instead of HAL. (now, in official repositories is version 4.0 ;) ) Reproducible: Always Steps to Reproduce: 1.Open KDE Settings 2.Go to Input devices 3.Go to TouchPad 4.Then go to setup USB mouse actions Actual Results: No USB mouse are recognized Expected Results: USB Mouse must be recognized, so Synaptiks can disable touchpad -- 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 6

[Bug 670454] New: KWin crash when resizing mlayer
by bugzilla_noreply＠novell.com 19 Mar '12

19 Mar '12

https://bugzilla.novell.com/show_bug.cgi?id=670454 https://bugzilla.novell.com/show_bug.cgi?id=670454#c0 Summary: KWin crash when resizing mlayer Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: suse-beta(a)cboltz.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- Created an attachment (id=412905) --> (http://bugzilla.novell.com/attachment.cgi?id=412905) KWin crashlog KWin just crashed on my system while I resized a MPlayer window with a video playing. Involved repos (all from 2011-02-04): - Factory - KDE:Distro:Factory - Mplayer is from Packman In case it matters: I'm using the NVidia binary driver, and desktop effects are enabled. The crashlog is attached. Reproducable: hopefully not ;-) - seriously: it's the first time this happened to me. -- 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 5