:(

JavaScript is disabled!

We have carefully crafted an innovative experience for the Korora community and hope you find us trustworthy enough to enable JavaScript try it out in its full glory. This entire website, including all of our JavaScript, is open source.

[Solved] Problems with other DE's

I installed Korora 25 GNOME on a secondary HDD on my computer, and it worked for a while. I decided to install Cinnamon as a second DE, and it was fine for a few days. Today I loaded Korora, and nouveau (the unofficial nVidia driver) was disabled, so I re-enabled it, which wasn't too hard, but my Cinnamon DE won't start. I select my user, Enter the password, change the DE from GNOME to Cinnamon, and the screen goes black for a second, then goes back to the GDM log on screen. I also tried it with KDE, same issue.

If anyone has any Idea on how to fix this, it would be greatly appreciated, as I need to use Cinnamon for my YouTube channel, as OBS won't record in GNOME for some reason.

cardcinnamondesktopenvironmentgnomegraphicskdenvidiasoftware

asked 4 months ago

by Naln1

Is the system up to date? If so try booting with an older kernel. You should have a couple of older kernels on the grub boot screen.

It is strange that Nouveau would be disabled. You have installed or tried to install the proprietary drivers have you?

For the second issue have you tried starting Gnome in X instead of Wayland? There is an option for that where you select the DE to run. Many applications don't run under Wayland, at least not yet.

replied 4 months ago

by ozjd

ozjd wrote:
It is strange that Nouveau would be disabled. You have installed or tried to install the proprietary drivers have you?

Yes, I did try to install official nVidia drivers, and that probably caused the problem

ozjd wrote:
For the second issue have you tried starting Gnome in X instead of Wayland?...

GNOME on Xorg doesn't work either, I know Cinnamon & KDE use Xorg too, so that may be the issue. I'll try to reinstall Xorg.

EDIT: I need help re-installing Xorg, so help with that would be greatly appreciated.

replied 4 months ago

by Naln1

I doubt you need to install Xorg, it is more likely a problem with the Nvidia drivers. How did you install them? Did you select the correct driver for your card? There is a guide at https://rpmfusion.org/Howto/nVidia.

replied 4 months ago

by ozjd

ozjd wrote:
How did you install them? Did you select the correct driver for your card?

I selected the right drivers (I'm not an Idiot), but the installer said something about failing? I don't remember. So, I uninstalled the nVidia stuff that it put on my hard drive, (it didn't undo itself), and removed the blacklists for nouveau. And here I am, writing in this forum.

Naln1 wrote:
I selected the right drivers (I'm not an Idiot),
Didn't mean t offend you but that is a common problem. Many people don't realise there are more than one version of the driver and the current driver doesn't work for older cards. The other common reason for failure is Optimus which is dual graphics, Intel and Nvidia. The driver doesn't handle that yet although I understand that isn't far away.
.

Uh... Actually I didn't get it working... I've just been busy lately. I am going to try to do a clean install of korora today. The korora was very new when this happened, and I won't lose anything. Thank you for your help.

Code Spans

Use single backticks to create an inline <code> span:

The `$` character is just a shortcut for `window.jQuery`.

(The backtick key is in the upper left corner of most keyboards.)

Like code blocks, code spans will be displayed in a monospaced font. Markdown and HTML will not work within them. Note that, unlike code blocks, code spans require you to manually escape any HTML within!

If your code itself contains backticks, you may have to use double backticks as delimiters:

The name ``Tuple`2`` is a valid .NET type name.

Linebreaks

End a line with two spaces to add a <br/> linebreak:

How do I love thee?
Let me count the ways

Italics and Bold

*This is italicized*, and so is _this_.
**This is bold**, and so is __this__.
Use *** italics and bold together*** if you ___have to___.

Links

Basic Links

There are three ways to write links. Each is easier to read than the last:

Here's an inline link to [Google](http://www.google.com/).
Here's a reference-style link to [Google][1].
Here's a very readable link to [Yahoo!][yahoo].
[1]: http://www.google.com/
[yahoo]: http://www.yahoo.com/

The link definitions can appear anywhere in the document -- before or after the place where you use them. The link definition names [1] and [yahoo] can be any unique string, and are case-insensitive; [yahoo] is the same as [YAHOO].

Advanced Links

Links can have a title attribute, which will show up on hover. Title attributes can also be added; they are helpful if the link itself is not descriptive enough to tell users where they're going.

Advanced lists: Nesting

1.Lists in a list item:
-Indented four spaces.
*indented eight spaces.
-Four spaces again.
2.Multiple paragraphs in a list items:
It's best to indent the paragraphs four spaces
You can get away with three, but it can get
confusing when you nest other things.
Stick to four.
We indented the first line an extra space to align
it with these paragraphs. In real use, we might do
that to the entire list so that all items line up.
This paragraph is still part of the list item, but it looks messy to humans. So it's a good idea to wrap your nested paragraphs manually, as we did with the first two.
3.Blockquotes in a list item:
> Skip a line and
> indent the >'s four spaces.
4.Preformatted text in a list item:
Skip a line and indent eight spaces.
That's four spaces for the list
and four to trigger the code block.

Simple blockquotes

Add a > to the beginning of any line to create a blockquote. Ensure that after any quoteing you leave a blank line to resume normal paragraph text.

> The syntax is based on the way email programs
> usually do quotations. You don't need to hard-wrap
> the paragraphs in your blockquotes, but it looks much nicer if you do. Depends how lazy you feel.
New paragraphs start after a blank line.

Advanced blockquotes: Nesting

To put other Markdown blocks in a blockquote, just add a > followed by a space.

To put other Markdown blocks in a blockquote, just add a > followed by a space:

> The > on the blank lines is optional.
> Include it or don't; Markdown doesn't care.
>> But your plain text looks better to
> humans if you include the extra `>`
> between paragraphs.

Blockquotes within a blockquote:

> A standard blockquote is indented
>> A nested blockquote is indented more
>>>> You can nest to any depth.

Lists in a blockquote:

>- A list in a blockquote
>- With a &gt; and space in front of it
>* A sublist

Preformatted text in a blockquote:

>Indent five spaces total. The first
>one is part of the blockquote designator.

Images

Images are exactly like links, but they have an exclamation point in front of them:

![Valid XHTML](http://w3.org/Icons/valid-xhtml10).

The word in square brackets is the alt text, which gets displayed if the browser can't show the image. Be sure to include meaningful alt text for screen-reading software.

Just like links, images work with reference syntax and titles:

This page is ![valid XHTML][checkmark].
[checkmark]: http://w3.org/Icons/valid-xhtml10
"What are you smiling at?"

Note: Markdown does not currently support the shortest reference syntax for images:

Here's a broken ![checkmark].

But you can use a slightly more verbose version of implicit reference names:

This ![checkmark][] works.

The reference name is also used as the alt text.

You can also use standard HTML image syntax, which allows you to scale the width and height of the image.

<img src="http://example.com/sample.png" width="100" height="100">

URLs can be relative or full.

YouTube & Vimeo

You can embed YouTube or Vimeo videos that can be useful for demonstrating artefacts or desired behaviours. To embed a YouTube or Vimeo video, use the youtube! and vimeo! prefixes respectively, followed by the YouTube/Vimeo ID.

Below are two videos highlighting the artefacts in question
youtube!ZEH9k3eXZCs
vimeo!68400837