Fedora: Difference between revisions

Line 84:

::adding a picture will show it on the GDM login screen.

:4-)If you hold down Alt, a 'Shut Down' option appears in place of suspend

:4-) If you hold down Alt, a 'Shut Down' option appears in place of suspend

:5-)the Shell simply always behaves so there's exactly one empty workspace.

:5-)

So when you start a session you have one workspace.

the Shell simply always behaves so there's exactly one empty workspace.

As soon as you run something it goes into that workspace and

So when you start a session you have one workspace.

you get a second empty workspace. As soon as you put any app into that

As soon as you run something it goes into that workspace and

empty workspace, a new empty workspace is created. If you remove

you get a second empty workspace. As soon as you put any app into that

everything from any workspace, it will disappear, so there's still only

empty workspace, a new empty workspace is created. If you remove

one empty workspace at the bottom of the list. So, there's never any

everything from any workspace, it will disappear, so there's still only

need to manually add a new workspace. Pretty neat system.

one empty workspace at the bottom of the list. So, there's never any

need to manually add a new workspace. Pretty neat system.

:6-) I've just installed F15 alpha in a virtualbox machine and at the first boot I

get a gnome 3 error explaining that it can't be fully initialised because 3D is

not supported.

GNOME3 is not expected to work in virtualized environments where

hardware accelerated graphics are not available.

:7-)

Line 133:

Line 134:

acceleration passthrough. But it's not at all guaranteed that we'll

manage either in time for f15.

:8-)test Digest, Vol 85, Issue 78

Unable to log in after update:

'''yum downgrade rsyslog fixed it'''

The minimum memory required is 1GB, due to anaconda changes.

When you see "populate_rootfs" in the panic, it's caused by that.

Message: 16

don't know whether modifying services is reasonable, but what is not

reasonable is for a user no longer to be able to boot his system and not to be

able to log in after an update. For the less experienced user, this particular

problem required a reinstallation of the system. For me, a somewhat more savvy

user, this required using all the skills I had just to avoid reinstallation,

and only a tip on this list from another affected user to get me out of an

unsolvable situation.

====Update Log====

# 178 03/12? on install

@@ Line 84: / Line 84: @@
 ::adding a picture will show it on the GDM login screen.
-:4-)If you hold down Alt, a 'Shut Down' option appears in place of suspend
+:4-)   If you hold down Alt, a 'Shut Down' option appears in place of suspend
-:5-)the Shell simply always behaves so there's exactly one empty workspace.
+:5-)
-So when you start a session you have one workspace.
+       the Shell simply always behaves so there's exactly one empty workspace.
-As soon as you run something it goes into that workspace and
+       So when you start a session you have one workspace.
-you get a second empty workspace. As soon as you put any app into that
+       As soon as you run something it goes into that workspace and
-empty workspace, a new empty workspace is created. If you remove
+       you get a second empty workspace. As soon as you put any app into that
-everything from any workspace, it will disappear, so there's still only
+       empty workspace, a new empty workspace is created. If you remove
-one empty workspace at the bottom of the list. So, there's never any
+       everything from any workspace, it will disappear, so there's still only
-need to manually add a new workspace. Pretty neat system.
+       one empty workspace at the bottom of the list. So, there's never any
+       need to manually add a new workspace. Pretty neat system.
-:6-) I've just installed F15 alpha in a virtualbox machine and at the first boot I
+:6-)   I've just installed F15 alpha in a virtualbox machine and at the first boot I
-get a gnome 3 error explaining that it can't be fully initialised because 3D is
+       get a gnome 3 error explaining that it can't be fully initialised because 3D is
-not supported.
+       not supported.
-GNOME3 is not expected to work in virtualized environments where
+       GNOME3 is not expected to work in virtualized environments where
-hardware accelerated graphics are not available.
+       hardware accelerated graphics are not available.
 :7-)
@@ Line 133: / Line 134: @@
          acceleration passthrough. But it's not at all guaranteed that we'll
          manage either in time for f15.
+:8-)test Digest, Vol 85, Issue 78
+        Unable to log in after update:
+        '''yum downgrade rsyslog fixed it'''
+        The minimum memory required is 1GB, due to anaconda changes.
+        When you see "populate_rootfs" in the panic, it's caused by that.
+        Message: 16
+        don't know whether modifying services is reasonable, but what is not
+        reasonable is for a user no longer to be able to boot his system and not to be
+        able to log in after an update. For the less experienced user, this particular
+        problem required a reinstallation of the system. For me, a somewhat more savvy
+        user, this required using all the skills I had just to avoid reinstallation,
+        and only a tip on this list from another affected user to get me out of an
+        unsolvable situation.
 ====Update Log====
 # 178 03/12?  on install