Bug 51020

Summary: [Regression] Weston start with "Bug reports to" log
Product: Wayland Reporter: ZhaoShengyan <shengyanx.zhao>
Component: westonAssignee: Wayland bug list <wayland-bugs>
Status: VERIFIED NOTABUG QA Contact:
Severity: major    
Priority: high    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: weston-log

Description ZhaoShengyan 2012-06-12 22:13:04 UTC
System Environment:
--------------------------
Arch:               i386
Libdrm:             (master) libdrm-2.4.35-8-g325e2e52a96ede6a19e891f769c803cb9ba85e10
Wayland:            (master) 1432bd62df3f30a8a28eba0c5e795113741bade3
Mesa:               (master) ae419a0159eeba6138d8c72a54737190cb6b1626
Xserver:            (master) xorg-server-1.12.0-200-g812786f4d4306cb16f8ed57fa4a1a32bb1d13fe3
Xf86_video_intel:   (master) 2.19.0-240-g392e33a62d729c64c57699505220b4029e015470
Cairo:              (master) dbc0efad7e565558a3abf7f69d7675efddc4688d
Cairo_gl:           (master) 615205cf072935401dac46813b597e70bc8f0a8c
Xkbcommon:          (master) 6992de408a890be7bd66f7d829dc84eb9c4b81a6
Weston:             (master) 04769744e1af5296dc2727e123847d2a65f12092
Kernel_unstable:    (drm-intel-next-queued) 172cf15d18889313bf2c3bfb81fcea08369274ef

Bug detailed description:
-----------------------------
Start weston either drm mode or X mode, weston desktop start with "Bug reports to" logs:

./weston
Date: 2012-06-13 CST
[11:11:34.348] weston 0.89
               http://wayland.freedesktop.org/
               Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=weston
               Build: 0476974 shell: Store focus state in workspaces (2012-06-12 20:20:38 -0400)
[11:11:34.348] OS: Linux, 3.4.0_unstable_20120612+, #1 SMP Tue Jun 12 12:22:32 CST 2012, i686
couldn't open /root/.config/weston.ini
[11:11:34.348] Loading module '/opt/X11R7/lib/weston/drm-backend.so'
[11:11:34.348] initializing drm backend
[11:11:34.348] compositor: using new vt /dev/tty7
[11:11:34.350] using /dev/dri/card0
couldn't open /root/.config/weston.ini
[11:11:34.360] EGL version: 1.4 (DRI2)
[11:11:34.360] EGL vendor: Mesa Project
[11:11:34.360] EGL client APIs: OpenGL OpenGL_ES OpenGL_ES2
[11:11:34.360] EGL extensions: EGL_MESA_drm_image EGL_WL_bind_wayland_display
               EGL_KHR_image_base EGL_KHR_gl_renderbuffer_image
               EGL_KHR_surfaceless_gles1 EGL_KHR_surfaceless_gles2
               EGL_KHR_surfaceless_opengl
[11:11:34.360] GL version: OpenGL ES 2.0 Mesa 8.1-devel (git-ae419a0)
[11:11:34.360] GLSL version: OpenGL ES GLSL ES 1.0.16
[11:11:34.360] GL vendor: Intel Open Source Technology Center
[11:11:34.360] GL renderer: Mesa DRI Intel(R) Sandybridge Desktop x86/MMX/SSE2
[11:11:34.360] GL extensions: GL_EXT_blend_minmax GL_EXT_multi_draw_arrays
               GL_EXT_texture_filter_anisotropic
               GL_EXT_texture_compression_dxt1 GL_EXT_texture_format_BGRA8888
               GL_OES_depth24 GL_OES_element_index_uint
               GL_OES_fbo_render_mipmap GL_OES_mapbuffer GL_OES_rgb8_rgba8
               GL_OES_standard_derivatives GL_OES_stencil8 GL_OES_texture_3D
               GL_OES_texture_npot GL_OES_EGL_image GL_OES_depth_texture
               GL_OES_packed_depth_stencil GL_EXT_texture_type_2_10_10_10_REV
               GL_EXT_read_format_bgra GL_NV_fbo_color_attachments
               GL_EXT_unpack_subimage GL_NV_draw_buffers
[11:11:34.405] kms connector 7, crtc 3 at mode 1280x1024@60.0
[11:11:34.451] Loading module '/opt/X11R7/lib/weston/desktop-shell.so'
couldn't open /root/.config/weston.ini
[11:11:34.451] libwayland: using socket /run/user/root/wayland-0
couldn't open /root/.config/weston.ini
[11:12:36.620] libwayland: disconnect from client 0x99734f0

This issue can be reproduce both with drm mode and X mode.

Reproduce steps:
----------------------------
1. start weston
Comment 1 Scott Moreau 2012-06-13 08:52:54 UTC
> Bug detailed description:
> -----------------------------
> Start weston either drm mode or X mode, weston desktop start with "Bug
> reports
> to" logs:
>
> ./weston
> Date: 2012-06-13 CST
> [11:11:34.348] weston 0.89
>               http://wayland.freedesktop.org/
>               Bug reports to:
> https://bugs.freedesktop.org/enter_bug.cgi?product=weston
>               Build: 0476974 shell: Store focus state in workspaces
> (2012-06-12 20:20:38 -0400)
> [11:11:34.348] OS: Linux, 3.4.0_unstable_20120612+, #1 SMP Tue Jun 12
> 12:22:32
> CST 2012, i686
>
>
The entry is "Bug reports to:
https://bugs.freedesktop.org/enter_bug.cgi?product=weston". I don't
understand why you think this is a problem. As far as I'm concerned, this
is not a bug.
Comment 2 Kristian Høgsberg 2012-06-13 09:02:14 UTC
Yeah, I'm not sure what the problem is either.  The log message tells users where to reports bugs by giving a url to this bugzilla.
Comment 3 ZhaoShengyan 2012-06-13 17:46:15 UTC
Really thanks for your reply, I thought your understanding before, but I have to check with you in case of our misunderstanding about the original information that the author wanna address us. 
Thanks for your patience.
I mark this issue as RESOLVED and NOTABUG.
Comment 4 ZhaoShengyan 2012-06-13 17:48:03 UTC
Mark the issue as VERIFIED and NOTABUG.
Comment 5 Vova 2012-07-24 01:44:13 UTC
Created attachment 64578 [details]
weston-log
Comment 6 Vova 2012-07-24 01:44:55 UTC
Why this not a bug? Regression started from this commit:
http://cgit.freedesktop.org/wayland/weston/commit/?id=76574d1fb7457a0aef14d2fcca6c66f3ffe97cf9

and next:
http://cgit.freedesktop.org/wayland/weston/commit/?id=28f59b027a56da58a2cde306d8f0497a8a804ad3

and similar commit yet related to the planar buffers in mesa. I have builds of weston and mesa befor this commits, on my ati hd 2600xt with radeon it working fine with X and DRI2 backends. All builds after planar buffers commit doesn`t work on any backends.

In attach full debug log. 

------
Thanx
Comment 7 Kristian Høgsberg 2012-07-24 02:01:36 UTC
You have the wrong bug, I think you want 52267.
Comment 8 Vova 2012-07-24 06:02:10 UTC
Sorry, my mistake.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.