:(

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] Owncloud Client does not show up

Hi there,

i tried to install the nextcloud client and it worked. I was able to configure it and it loaded all my files to the desired location.
After the setup, if I try to open the client, nothing happens. Also the little statusbar icon doesn't show up.
Nextcloud itself seems to work just fine. The files are there, the folder shows the green arrow-icon and the process is running.

But i want this GUI-Client to set things up and see if there are any problems. So I uninstalled nextcloud, and installed owncloud, after i read that nextcloud doesn't really use an own client. I installed it, but not even the setup dialog shows up when I try to start it (but the process is running).

I'm using Korora 25 with GNOME (3.22.2) and installed every update.

Edit: Wow, just after i hit the "save" button on this post, i discovered the little cloud-symbol in the bottom left corner. I feel stupid now, but is really small and...
but I feel happy now. It's first of 6 distros I tried this week where everything works :)

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