public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <g3vbv@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.21-rc1 and 2.6.21-rc2 kwin dies silently
Date: Wed, 28 Feb 2007 16:24:28 +0000	[thread overview]
Message-ID: <45E5ACBC.2050800@blueyonder.co.uk> (raw)

 >>/ openSUSE 10.3 Alpha and KDE-3.5.6, xorg-x11-7.2. KDE is setup not to/
 >>/ require a password to unlock, but it asks for password. When the 
screen/
 >>/ unlocks, kwin is gone with no errors logged in /var/log/kdm or/
 >>/ /var/log/messages. No problems with 2.6.20./
 >>
 >>/ Same problem on openSUSE 10.2 x86_64, KDE-3.5.5 and 2.6.21-rc2./
 >>/ Regards/
 >>/ Sid./

 > This is the linux kernel mailing list. Perhaps you should post your 
problem to
 > the opensuse mailing list.
 >
 > Regards
That's very much appreciated. The point is that all vanilla kernels up 
to 2.6.20+ have not had the problems now seen on 2.6.20-rc1 and 
2.6.20-rc2 and like other problems reported, sic framebuffer, etc., 
there is a distinct likelihood that it's related to those kernels and 
worth reporting here where it will also be seen by the openSUSE kernel 
developers.
Regards
Sid.

-- 
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks



             reply	other threads:[~2007-02-28 16:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28 16:24 Sid Boyce [this message]
     [not found] <45E939E1.8050501@argo.co.il>
2007-03-03 20:30 ` 2.6.21-rc1 and 2.6.21-rc2 kwin dies silently Sid Boyce
     [not found] <45E5DE32.2070902@argo.co.il>
2007-03-01 13:52 ` Sid Boyce
2007-03-01 15:11   ` Avi Kivity
2007-03-02  4:22     ` Sid Boyce
  -- strict thread matches above, loose matches on Subject: below --
2007-02-28 15:19 Sid Boyce
2007-02-28 16:05 ` auxsvr
2007-03-08  5:47   ` Andrew Morton
2007-03-08  7:34     ` Sid Boyce
2007-03-21 17:43       ` Sid Boyce
2007-03-21 19:34         ` Adrian Bunk
2007-03-21 20:17           ` Eric W. Biederman
2007-03-22  1:32             ` Sid Boyce
2007-03-22  1:42               ` Randy Dunlap
2007-03-22 10:59                 ` Adrian Bunk
2007-03-22 19:49                   ` Sid Boyce
2007-03-26 12:02                     ` boris
2007-03-27  3:38                   ` Sid Boyce
2007-03-27 13:48                     ` Eric W. Biederman
2007-03-28  3:26                       ` Sid Boyce
2007-03-28  4:14                         ` Adrian Bunk
2007-03-28 13:17                           ` Eric W. Biederman
2007-03-29 11:35                           ` Sid Boyce
2007-03-30 18:00                             ` Adrian Bunk
2007-03-29  4:04                         ` Eric W. Biederman
2007-03-29 11:37                           ` Sid Boyce
2007-03-29 16:16                             ` Sid Boyce

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45E5ACBC.2050800@blueyonder.co.uk \
    --to=g3vbv@blueyonder.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox