Hi, just completed the upgrade for gnome 3.36.2 and and all went well, but now upon a fresh ego sync and emerge -avDN @world, i'm getting an X warning about my xdm file
tux-x131e ~ # emerge -avDN @world
These are the packages that would be merged, in order:
Calculating dependencies... done!
Total: 0 packages, Size of downloads: 0 KiB
Nothing to merge; quitting.
tux-x131e ~ # emerge --depclean
* Always study the list of packages to be cleaned for any obvious
* mistakes. Packages that are part of the world set will always
* be kept. They can be manually added to this set with
* `emerge --noreplace <atom>`. Packages that are listed in
* package.provided (see portage(5)) will be removed by
* depclean, even if they are part of the world set.
*
* As a safety measure, depclean will not remove any packages
* unless *all* required dependencies have been resolved. As a
* consequence of this, it often becomes necessary to run
* `emerge --update --newuse --deep @world` prior to depclean.
All selected packages: =app-eselect/eselect-opencl-1.2.0 =dev-util/opencl-headers-20190412 =dev-libs/wayland-1.17.0 =virtual/linux-sources-2.6 =dev-libs/ocl-icd-2.2.12-r1 =dev-util/opencl-clhpp-20190207
>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.
>>> Waiting 5 seconds before starting...
>>> (Control-C to abort)...
>>> Unmerging in: 5 4 3 2 1
>>> Unmerging (1 of 6) dev-libs/ocl-icd-2.2.12-r1...
>>> Unmerging (2 of 6) virtual/linux-sources-2.6...
>>> Unmerging (3 of 6) dev-libs/wayland-1.17.0...
>>> Unmerging (4 of 6) app-eselect/eselect-opencl-1.2.0...
>>> Unmerging (5 of 6) dev-util/opencl-clhpp-20190207...
>>> Unmerging (6 of 6) dev-util/opencl-headers-20190412...
Packages installed: 1073
Packages in world: 10
Packages in system: 81
Required packages: 1073
Number removed: 6
* GNU info directory index is up-to-date.
* IMPORTANT: config file '/etc/conf.d/xdm' needs updating.
* See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS
* sections of the emerge man page to learn how to update config files.
tux-x131e ~ #
We always try and start X on a static VT. The various DMs normally default
# to using VT7. If you wish to use the xdm init script, then you should ensure
# that the VT checked is the same VT your DM wants to use. We do this check to
# ensure that you haven't accidentally configured something to run on the VT
# in your /etc/inittab file so that you don't get a dead keyboard.
CHECKVT=7
# What display manager do you use ? [ xdm | gdm | sddm | gpe | lightdm | entrance ]
# NOTE: If this is set in /etc/rc.conf, that setting will override this one.
DISPLAYMANAGER="gdm"
I don't understand what or how it needs to be updated.
X has started flickering and crashing since the update. It happens after 5 minutes when screen dims to go to sleep.
Question
tbuck713
Hi, just completed the upgrade for gnome 3.36.2 and and all went well, but now upon a fresh ego sync and emerge -avDN @world, i'm getting an X warning about my xdm file
tux-x131e ~ # emerge -avDN @world
These are the packages that would be merged, in order:
Calculating dependencies... done!
Total: 0 packages, Size of downloads: 0 KiB
Nothing to merge; quitting.
tux-x131e ~ # emerge --depclean
* Always study the list of packages to be cleaned for any obvious
* mistakes. Packages that are part of the world set will always
* be kept. They can be manually added to this set with
* `emerge --noreplace <atom>`. Packages that are listed in
* package.provided (see portage(5)) will be removed by
* depclean, even if they are part of the world set.
*
* As a safety measure, depclean will not remove any packages
* unless *all* required dependencies have been resolved. As a
* consequence of this, it often becomes necessary to run
* `emerge --update --newuse --deep @world` prior to depclean.
Calculating dependencies... done!
>>> Calculating removal order...
dev-libs/ocl-icd
selected: 2.2.12-r1
protected: none
omitted: none
virtual/linux-sources
selected: 2.6
protected: none
omitted: none
dev-libs/wayland
selected: 1.17.0
protected: none
omitted: none
app-eselect/eselect-opencl
selected: 1.2.0
protected: none
omitted: none
dev-util/opencl-clhpp
selected: 20190207
protected: none
omitted: none
dev-util/opencl-headers
selected: 20190412
protected: none
omitted: none
All selected packages: =app-eselect/eselect-opencl-1.2.0 =dev-util/opencl-headers-20190412 =dev-libs/wayland-1.17.0 =virtual/linux-sources-2.6 =dev-libs/ocl-icd-2.2.12-r1 =dev-util/opencl-clhpp-20190207
>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.
>>> Waiting 5 seconds before starting...
>>> (Control-C to abort)...
>>> Unmerging in: 5 4 3 2 1
>>> Unmerging (1 of 6) dev-libs/ocl-icd-2.2.12-r1...
>>> Unmerging (2 of 6) virtual/linux-sources-2.6...
>>> Unmerging (3 of 6) dev-libs/wayland-1.17.0...
>>> Unmerging (4 of 6) app-eselect/eselect-opencl-1.2.0...
>>> Unmerging (5 of 6) dev-util/opencl-clhpp-20190207...
>>> Unmerging (6 of 6) dev-util/opencl-headers-20190412...
Packages installed: 1073
Packages in world: 10
Packages in system: 81
Required packages: 1073
Number removed: 6
* GNU info directory index is up-to-date.
* IMPORTANT: config file '/etc/conf.d/xdm' needs updating.
* See the CONFIGURATION FILES and CONFIGURATION FILES UPDATE TOOLS
* sections of the emerge man page to learn how to update config files.
tux-x131e ~ #
We always try and start X on a static VT. The various DMs normally default
# to using VT7. If you wish to use the xdm init script, then you should ensure
# that the VT checked is the same VT your DM wants to use. We do this check to
# ensure that you haven't accidentally configured something to run on the VT
# in your /etc/inittab file so that you don't get a dead keyboard.
CHECKVT=7
# What display manager do you use ? [ xdm | gdm | sddm | gpe | lightdm | entrance ]
# NOTE: If this is set in /etc/rc.conf, that setting will override this one.
DISPLAYMANAGER="gdm"
I don't understand what or how it needs to be updated.
X has started flickering and crashing since the update. It happens after 5 minutes when screen dims to go to sleep.
Is there something i neglected to clean up?
regards,
Tom
Link to comment
Share on other sites
1 answer to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now