Your message dated Thu, 2 Jun 2016 13:19:21 +0200 with message-id <20160602111921.GA4232@polynomio.collabora.co.uk> and subject line Re: Bug#785339: weston: running weston blanks screen, and makes system unresponsive when running i386 through vmware player has caused the Debian Bug report #785339, regarding weston: running weston blanks screen, and makes system unresponsive when running i386 through vmware player to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 785339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785339 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: weston: running weston blanks screen, and makes system unresponsive when running i386 through vmware player
- From: jsmith <fake@email.com>
- Date: Thu, 14 May 2015 19:21:51 -0400
- Message-id: <20150514232151.728.3863.reportbug@debian2>
Package: weston Version: 1.6.0-2+b1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 4.0.0-1-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages weston depends on: ii adduser 3.113+nmu3 ii libc6 2.19-18 ii libcairo2 1.14.0-2.1 ii libcolord2 1.2.1-1+b2 ii libdbus-1-3 1.8.16-2 ii libdrm2 2.4.60-3 ii libegl1-mesa [libegl1-x11] 10.5.5-1 ii libgbm1 10.5.5-1 ii libgles2-mesa [libgles2] 10.5.5-1 ii libglib2.0-0 2.44.0-3 ii libinput5 0.6.0+dfsg-2 ii libjpeg62-turbo 1:1.4.0-7 ii liblcms2-2 2.6-3+b3 ii libmtdev1 1.1.5-1 ii libpam0g 1.1.8-3.1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpixman-1-0 0.32.6-3 ii libpng12-0 1.2.50-2+b2 ii libsystemd0 215-17 ii libudev1 215-17 ii libwayland-client0 1.6.0-2 ii libwayland-cursor0 1.6.0-2 ii libwayland-egl1-mesa [libwayland-egl1] 10.5.5-1 ii libwayland-server0 1.6.0-2 ii libx11-6 2:1.6.3-1 ii libx11-xcb1 2:1.6.3-1 ii libxcb-composite0 1.10-3+b1 ii libxcb-render0 1.10-3+b1 ii libxcb-shape0 1.10-3+b1 ii libxcb-shm0 1.10-3+b1 ii libxcb-xfixes0 1.10-3+b1 ii libxcb-xkb1 1.10-3+b1 ii libxcb1 1.10-3+b1 ii libxcursor1 1:1.1.14-1+b1 ii libxkbcommon0 0.4.3-2 Versions of packages weston recommends: ii libgl1-mesa-dri 10.5.5-1 weston suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---
- To: jsmith <fake@email.com>, 785339-close@bugs.debian.org
- Subject: Re: Bug#785339: weston: running weston blanks screen, and makes system unresponsive when running i386 through vmware player
- From: Hector Oron <zumbi@debian.org>
- Date: Thu, 2 Jun 2016 13:19:21 +0200
- Message-id: <20160602111921.GA4232@polynomio.collabora.co.uk>
- In-reply-to: <20160214001205.GA27762@polynomio.collabora.co.uk>
- References: <20150514232151.728.3863.reportbug@debian2> <20160214001205.GA27762@polynomio.collabora.co.uk>
On Sun, Feb 14, 2016 at 01:12:05AM +0100, Hector Oron wrote: > On Thu, May 14, 2015 at 07:21:51PM -0400, jsmith wrote: > > Package: weston > > Version: 1.6.0-2+b1 > > Severity: important > > > > Dear Maintainer, > > > > *** Reporter, please consider answering these questions, where appropriate *** > > > > * What led up to the situation? > > * What exactly did you do (or not do) that was effective (or > > ineffective)? > > * What was the outcome of this action? > > * What outcome did you expect instead? > > Could you please provide more information? It might be a valid bug, however we lack information, thus I am closing it, please reopen a new bug if the issue persists. Regards -- Hector OronAttachment: signature.asc
Description: PGP signature
--- End Message ---