Re: [Cooker] no authorized user

2000-01-05 Thread Scott Haug

This was fixed.  Download the latest SysVinit.

-Scott

$ rpm -q SysVinit
SysVinit-2.77-7mdk
$ rpm -q --changelog SysVinit
* Tue Jan 04 2000 Yoann Vandoorselaere <[EMAIL PROTECTED]>

- Clean up... All appear to work fine. 
- Oups, dumb little fix (but important)

* Mon Jan 03 2000 Yoann Vandoorselaere <[EMAIL PROTECTED]>

- Patch : take care of the -a options even if shutdown.allow doesn't exist.

* Tue Oct 19 1999 Chmouel Boudjnah <[EMAIL PROTECTED]>

- Merge with redhat changes.

* Tue Sep 28 1999 Axalon Bloodstone <[EMAIL PROTECTED]>

- nologin patch isn't needed

* Tue Sep 14 1999 Daouda LO <[EMAIL PROTECTED]>

- 2.77


On Wed, Jan 05, 2000 at 12:38:35PM -0900, WH Bouterse wrote:
> I'm hitting the "no authorized user logged in" 
> message on a hybrid L-M6.1 with 7.0Beta Upgrade.
> 
> Looking in the archives I saw the add
> /etc/shutdown.allow then the  'shutdown -a' 
> command, but it only got me to a single user shell.
> 
> I still had to do a 'telinit 6' to actually
> shutdown and reboot.
> 
> I am missing the obvious I'm sure!
> 
> William Bouterse
> Juneau Alaska

-- 



Re: [Cooker] New Install of Oxygen - Few things....

2000-01-01 Thread Scott Haug

On Sat, Jan 01, 2000 at 09:59:09PM -0500, Heath Doane wrote:
> Greetings,
>   3) "Normal" user is unable to run X successfully.   Root has no problems,
> but when a regular user starts X, the server loads, the screen goes blue
> with an "X" cursor, but the KDE desktop never appears (some drive activity,
> but no desktop)
> 

I had this problem when I installed a fresh oxygen while retaining my previous
/home partition.  I created new users using the same name as the previous users
(thus reusing the old user's dirs), but the install gave them new uid's.  So
when I tried to log in to my old account, I had no permissions to write to my
account, which I believe is necessary when starting kde.  You may want to check
if your normal user account is owned by the user you think is supposed to own
it.  If this isn't the problem, I don't know what it might be.  But because
root can log in, I wouldn't be surprised if its permissions-related.

-Scott



Re: [Cooker] gtk list selection causes display problems

1999-12-30 Thread Scott Haug

On Thu, Dec 30, 1999 at 03:10:21PM +0100, Pixel wrote:
> Scott Haug <[EMAIL PROTECTED]> writes:
> 
> > 
> > Has anyone else noticed this phenomenon?  Or am I going crazy?
> 
> it is a known problem of the SVGA X server for 3dfx's (at least some of them)
> 

That would make sense.  I have a Voodoo Banshee.  The other individual who had
similar problems also has a Voodoo Banshee.  

-Scott

-- 



Re: [Cooker] gtk list selection causes display problems

1999-12-29 Thread Scott Haug

I've uploaded screenshots of the problem described below.  They are of the xmms
file select dialog.  

http://www.cs.wustl.edu/~sth2/noprob.png
http://www.cs.wustl.edu/~sth2/prob.png

noprob.png shows the dialog without anything selected.  The mouse pointer is
over the "Add selected files" button, which is why it is highlighted.

prob.png shows the same dialog with one of the items in the file dialog list
selected.  Notice how all the buttons, the pulldown directory menu, and the
slider bars are all outlined now as if they have been pressed.  This was
achieved simply by passing the mouse over each of these elements, without
actually pressing any of them.  Sometimes the elements can be brought back to
their correct state by passing the mouse over them again, but this behavior is
somewhat inconsistent.  Again, this only happens when something in the list is 
selected.

I get this behavior in almost every gtk application with a list selection
element, such as MandrakeUpdate, freeamp, or the gimp.

Has anyone else noticed this phenomenon?  Or am I going crazy?

-Scott

On Wed, Dec 29, 1999 at 10:21:15AM -0700, Axalon Bloodstone wrote:
> On Wed, 29 Dec 1999, Scott Haug wrote:
> 
> > This is a problem that has plagued me for quite some time under 6.0/6.1, so I
> > was hoping a fresh install of 7.0 would solve the problem.  Unfortunately, it
> > still persists.
> > 
> > The problem is that when I select an item from a gtk list, such as a package to
> > upgrade in MandrakeUpdate or a file in the standard gtk file dialog, it causes
> > display problems with other gui elements (usually buttons) in the dialog.  For
> > example, when a list item is selected, the button that currently has focus will
> > suddenly change its visual state to look like it does when it is "pressed".
> > Passing the mouse mouse over any gtk button (when a list item is selected)
> > toggles its visual state similarly, so that it alternates between looking
> > "pressed" and "unpressed".  The app itself functions correctly; it's only the
> > gui's appearance that is affected.
> > 
> > This is on a fresh install of Oxygen from last night.
> > 
> > gtk+-1.2.6-3mdk
> > glib-1.2.6-1mdk
> > 
> > The current desktop environment doesn't affect the situation; this problem
> > happens everytime regardless of whether I'm in kde or gnome.
> > 
> > Has anyone else experienced this problem?  Is there a fix?  It's annoying as
> > all get-out... :)
> > 
> > -Scott
> 
> Can you get some screen shots, also what gtk theme? 
> 
> -- 

-- 



Re: [Cooker] gtk list selection causes display problems

1999-12-29 Thread Scott Haug

On Wed, Dec 29, 1999 at 10:21:15AM -0700, Axalon Bloodstone wrote:
> On Wed, 29 Dec 1999, Scott Haug wrote:
> 
> > This is a problem that has plagued me for quite some time under 6.0/6.1, so I
> > was hoping a fresh install of 7.0 would solve the problem.  Unfortunately, it
> > still persists.
> > 
> > The problem is that when I select an item from a gtk list, such as a package to
> > upgrade in MandrakeUpdate or a file in the standard gtk file dialog, it causes
> > display problems with other gui elements (usually buttons) in the dialog.  For
> > example, when a list item is selected, the button that currently has focus will
> > suddenly change its visual state to look like it does when it is "pressed".
> > Passing the mouse mouse over any gtk button (when a list item is selected)
> > toggles its visual state similarly, so that it alternates between looking
> > "pressed" and "unpressed".  The app itself functions correctly; it's only the
> > gui's appearance that is affected.
> > 
> > This is on a fresh install of Oxygen from last night.
> > 
> > gtk+-1.2.6-3mdk
> > glib-1.2.6-1mdk
> > 
> > The current desktop environment doesn't affect the situation; this problem
> > happens everytime regardless of whether I'm in kde or gnome.
> > 
> > Has anyone else experienced this problem?  Is there a fix?  It's annoying as
> > all get-out... :)
> > 
> > -Scott
> 
> Can you get some screen shots, also what gtk theme? 
> 

I'm away from the affected machine at the moment, so I'll have to post some
screenshots tonight.  I never selected a new gtk theme for the current install,
so I guess it's the default theme, but I've had it happen independent of theme
on my previous installations.

-Scott

-- 



[Cooker] gtk list selection causes display problems

1999-12-29 Thread Scott Haug

This is a problem that has plagued me for quite some time under 6.0/6.1, so I
was hoping a fresh install of 7.0 would solve the problem.  Unfortunately, it
still persists.

The problem is that when I select an item from a gtk list, such as a package to
upgrade in MandrakeUpdate or a file in the standard gtk file dialog, it causes
display problems with other gui elements (usually buttons) in the dialog.  For
example, when a list item is selected, the button that currently has focus will
suddenly change its visual state to look like it does when it is "pressed".
Passing the mouse mouse over any gtk button (when a list item is selected)
toggles its visual state similarly, so that it alternates between looking
"pressed" and "unpressed".  The app itself functions correctly; it's only the
gui's appearance that is affected.

This is on a fresh install of Oxygen from last night.

gtk+-1.2.6-3mdk
glib-1.2.6-1mdk

The current desktop environment doesn't affect the situation; this problem
happens everytime regardless of whether I'm in kde or gnome.

Has anyone else experienced this problem?  Is there a fix?  It's annoying as
all get-out... :)

-Scott
--