> Am 17.01.2021 um 01:02 schrieb Samuel Sieb :
>
> On 1/16/21 5:31 AM, Richard Shaw wrote:
>> So as far as I can remember I haven't done anything custom here but...
>> Problem 1: package cockpit-bridge-235-1.fc33.x86_64 conflicts with
>> cockpit-dashboard < 233 provided by cockpit-dashboard-22
On 1/16/21 5:31 AM, Richard Shaw wrote:
So as far as I can remember I haven't done anything custom here but...
Problem 1: package cockpit-bridge-235-1.fc33.x86_64 conflicts with
cockpit-dashboard < 233 provided by cockpit-dashboard-229-1.fc33.noarch
- cannot install the best update candida
On 1/16/21 3:12 PM, Peter Boy wrote:
Am 16.01.2021 um 23:07 schrieb Samuel Sieb :
That is strange. This is what I get:
# dnf install cockpit
According your list you don’t have cockpit-dashboard installed, which is the
culprit
Oops, you're right! I missed that. However:
# dnf install coc
> Am 16.01.2021 um 23:07 schrieb Samuel Sieb :
>
> That is strange. This is what I get:
>
> # dnf install cockpit
> Last metadata expiration check: 3:19:39 ago on Sat 16 Jan 2021 07:45:05 AM
> PST.
> Dependencies resolved.
>
On 1/16/21 12:31 PM, Patrick Mansfield via users wrote:
On Sat, Jan 16, 2021 at 03:49:41PM +0100, Peter Boy wrote:
Is it me or a packaging problem?
I had the same problem on several servers. I just removed dashboard - not the
best solution but the quickest.
After hitting the problem for a
On Sat, Jan 16, 2021 at 03:49:41PM +0100, Peter Boy wrote:
> >
> > Is it me or a packaging problem?
>
>
> I had the same problem on several servers. I just removed dashboard - not the
> best solution but the quickest.
After hitting the problem for a few days, thinking the mirrors were out of
On Sat, 2021-01-16 at 20:22 +0100, Frédéric wrote:
> > Once again, this would be better discussed on the Fedora KDE list.
> > Many
> > people have had problems with switching and it's something that's
> > being
> > actively worked on. There was a thread about it a couple of months
> > ago
> > IIRC.
> Once again, this would be better discussed on the Fedora KDE list. Many
> people have had problems with switching and it's something that's being
> actively worked on. There was a thread about it a couple of months ago
> IIRC. I didn't mean to suggest that changing the DM would fix these as
> tha
On 1/16/21 5:31 AM, Richard Shaw wrote:
So as far as I can remember I haven't done anything custom here but...
Problem 1: package cockpit-bridge-235-1.fc33.x86_64 conflicts with
cockpit-dashboard < 233 provided by cockpit-dashboard-229-1.fc33.noarch
Looks like this is the missing piece.
I
On Sat, 2021-01-16 at 15:50 +0100, Frédéric wrote:
> > If everything fails you can always switch to lightdm.
> > It works for me :-)
>
> not more success with lightdm, I just get a black screen with a login
> as if I had done Ctrl+Alt+F2 but the screen then blinks.
Once again, this would be bette
General observation: Building from source doesn't mean you
built it the same way. There are often a gazillion ifdefs
in source code. Might want to download the fedora source rpm
and see what flags the spec file uses to build.
___
users mailing list -- use
> If everything fails you can always switch to lightdm.
> It works for me :-)
not more success with lightdm, I just get a black screen with a login
as if I had done Ctrl+Alt+F2 but the screen then blinks.
Best regards,
F
___
users mailing list -- users
> Am 16.01.2021 um 14:31 schrieb Richard Shaw :
>
> So as far as I can remember I haven't done anything custom here but...
>
> Problem 1: package cockpit-bridge-235-1.fc33.x86_64 conflicts with
> cockpit-dashboard < 233 provided by cockpit-dashboard-229-1.fc33.noarch
> - cannot install the
So as far as I can remember I haven't done anything custom here but...
Problem 1: package cockpit-bridge-235-1.fc33.x86_64 conflicts with
cockpit-dashboard < 233 provided by cockpit-dashboard-229-1.fc33.noarch
- cannot install the best update candidate for package
cockpit-dashboard-229-1.fc33.n
On 16/01/2021 04:14, Dr. Michael J. Chudobiak wrote:
If I install the moserial rpm from the repos, I can communicate with a serial
device on /dev/ttyS0 just fine.
However, if I remove the rpm, and compile it from source, the program launches
and connects to /dev/ttyS0 (as reported by lsof), b
I tried sddm but it didn't work properly, I did not manage to come
back to the first session. I'll try lightdm then!
Note that in the past, I moved from sddm to kdm because of a bug (full
back screen).
Thanks
F
Le ven. 15 janv. 2021 à 23:32, Bob Marcan a écrit :
>
> On Fri, 15 Jan 2021 22:49:48 +
Noticed this same error in the logs, as I try to figure out if it's
related to the nvidia drivers being no longer loaded after yesterday's
updates.
I'm not sure if it's related, just suspecting it..
On Sat, 16 Jan 2021 at 03:55, Frank McCormick wrote:
>
>
>
> On 1/14/21 11:50 PM, Frank McCormick
17 matches
Mail list logo