On 2020-01-05 02:00, Ed Greshko wrote:
> It is called Plasma. Enter "switchdesk" without parameters to see the
> choices.
I should have checked this yesterday.
"switchdesk" is broken in this release. Selecting Plasma or KDE will not work
as expected.
While the message displayed is
echo "Ple
On 2020-01-05 01:30, Robert McBroom via users wrote:
> On 1/4/20 12:30 AM, Samuel Sieb wrote:
>> On 1/3/20 8:49 PM, Robert McBroom via users wrote:
>>> Hadn't used kde for a few weeks. Trying to start it gave me the message
>>> that it was not installed. Curious since I've had it on my system for
On 1/4/20 12:30 AM, Samuel Sieb wrote:
On 1/3/20 8:49 PM, Robert McBroom via users wrote:
Hadn't used kde for a few weeks. Trying to start it gave me the
message that it was not installed. Curious since I've had it on my
system for years. following the message suggestion ran
What was the comm
On 1/3/20 10:49 PM, Robert McBroom via users wrote:
which happily did nothing but said it was complete. From rpm -qa I see
lots of kde entries. Same thing happened on my laptop. Both systems
running recently updated 31. Has kde completely abandoned x11?
The update from Plasma 5.16 to 5.17 move
On 2020-01-04 13:37, Robert McBroom via users wrote:
> On 1/3/20 11:59 PM, Ed Greshko wrote:
>> On 2020-01-04 12:49, Robert McBroom via users wrote:
>>> Hadn't used kde for a few weeks. Trying to start it gave me the message
>>> that it was not installed. Curious since I've had it on my system for
On 1/3/20 11:59 PM, Ed Greshko wrote:
On 2020-01-04 12:49, Robert McBroom via users wrote:
Hadn't used kde for a few weeks. Trying to start it gave me the message that it
was not installed. Curious since I've had it on my system for years. following
the message suggestion ran
dnf groupinstall
On 1/3/20 8:49 PM, Robert McBroom via users wrote:
Hadn't used kde for a few weeks. Trying to start it gave me the message
that it was not installed. Curious since I've had it on my system for
years. following the message suggestion ran
What was the command you tried and what was the message?
On 2020-01-04 12:49, Robert McBroom via users wrote:
> Hadn't used kde for a few weeks. Trying to start it gave me the message that
> it was not installed. Curious since I've had it on my system for years.
> following the message suggestion ran
>
> dnf groupinstall "KDE (K Desktop Environment)"
>
On Sat, 2019-02-23 at 13:23 +1100, Stephen Morris wrote:
> > AFAIK neither of these '3D acceleration' modes are useful for games. To
> > use the Nvidia drivers in the VM guest the only option is to pass the
> > GPU card directly through to the VM. This means masking it (i.e.
> > blacklisting) in Li
On 22/2/19 11:00 pm, Patrick O'Callaghan wrote:
On Fri, 2019-02-22 at 20:21 +1100, Stephen Morris wrote:
Note that if you actually want to use the Nvidia card to its full
capability within a VM, you need to use GPU passthrough. AFAIK this
currently cannot be done in VMware or Virtual Box, only o
On Fri, 2019-02-22 at 20:21 +1100, Stephen Morris wrote:
> > Note that if you actually want to use the Nvidia card to its full
> > capability within a VM, you need to use GPU passthrough. AFAIK this
> > currently cannot be done in VMware or Virtual Box, only on KVM/QEMU.
> > It's something of a has
On 21/2/19 11:22 pm, Patrick O'Callaghan wrote:
On Thu, 2019-02-21 at 22:32 +1100, Stephen Morris wrote:
On 21/2/19 9:48 pm, Ed Greshko wrote:
On 2/21/19 6:43 PM, Patrick O'Callaghan wrote:
On Thu, 2019-02-21 at 20:29 +1100, Stephen Morris wrote:
On 21/2/19 6:47 am, Samuel Sieb wrote:
On 2/2
On 21/2/19 11:28 pm, Patrick O'Callaghan wrote:
On Thu, 2019-02-21 at 23:00 +1100, Stephen Morris wrote:
Putting the following section in xorg.conf caused Gnome under Xorg to
start with the resolution of the Maximized vmware player, which was
1600x844, as desired. KDE did not start at the resolu
On Thu, 2019-02-21 at 23:00 +1100, Stephen Morris wrote:
> Putting the following section in xorg.conf caused Gnome under Xorg to
> start with the resolution of the Maximized vmware player, which was
> 1600x844, as desired. KDE did not start at the resolution of 1600x844,
> instead starting at 64
On Thu, 2019-02-21 at 22:32 +1100, Stephen Morris wrote:
> On 21/2/19 9:48 pm, Ed Greshko wrote:
> > On 2/21/19 6:43 PM, Patrick O'Callaghan wrote:
> > > On Thu, 2019-02-21 at 20:29 +1100, Stephen Morris wrote:
> > > > On 21/2/19 6:47 am, Samuel Sieb wrote:
> > > > > On 2/20/19 1:02 AM, Stephen Mor
On 21/2/19 10:32 pm, Stephen Morris wrote:
On 21/2/19 9:48 pm, Ed Greshko wrote:
On 2/21/19 6:43 PM, Patrick O'Callaghan wrote:
On Thu, 2019-02-21 at 20:29 +1100, Stephen Morris wrote:
On 21/2/19 6:47 am, Samuel Sieb wrote:
On 2/20/19 1:02 AM, Stephen Morris wrote:
lspci provides the followi
On 21/2/19 9:48 pm, Ed Greshko wrote:
On 2/21/19 6:43 PM, Patrick O'Callaghan wrote:
On Thu, 2019-02-21 at 20:29 +1100, Stephen Morris wrote:
On 21/2/19 6:47 am, Samuel Sieb wrote:
On 2/20/19 1:02 AM, Stephen Morris wrote:
lspci provides the following output for the device:
00:0f.0 VGA compa
On 2/21/19 6:43 PM, Patrick O'Callaghan wrote:
> On Thu, 2019-02-21 at 20:29 +1100, Stephen Morris wrote:
>> On 21/2/19 6:47 am, Samuel Sieb wrote:
>>> On 2/20/19 1:02 AM, Stephen Morris wrote:
lspci provides the following output for the device:
00:0f.0 VGA compatible controller: VMw
On Thu, 2019-02-21 at 20:29 +1100, Stephen Morris wrote:
> On 21/2/19 6:47 am, Samuel Sieb wrote:
> > On 2/20/19 1:02 AM, Stephen Morris wrote:
> > > lspci provides the following output for the device:
> > >
> > > 00:0f.0 VGA compatible controller: VMware SVGA II Adapter
> >
> > As Patrick pointe
On 21/2/19 6:47 am, Samuel Sieb wrote:
On 2/20/19 1:02 AM, Stephen Morris wrote:
lspci provides the following output for the device:
00:0f.0 VGA compatible controller: VMware SVGA II Adapter
As Patrick pointed out, this is clearly not an NVidia device. You can
find out which driver is actua
On 2/20/19 12:01 PM, Joe Zeff wrote:
On 02/20/2019 12:47 PM, Samuel Sieb wrote:
As Patrick pointed out, this is clearly not an NVidia device. You can
find out which driver is actually handling it, by running "lspci -v".
There will be a line with "Kernel driver in use:".
Or, just run lspci |
On 02/20/2019 12:47 PM, Samuel Sieb wrote:
As Patrick pointed out, this is clearly not an NVidia device. You can
find out which driver is actually handling it, by running "lspci -v".
There will be a line with "Kernel driver in use:".
Or, just run lspci | grep VGA and find out right there.
___
On 2/20/19 1:02 AM, Stephen Morris wrote:
lspci provides the following output for the device:
00:0f.0 VGA compatible controller: VMware SVGA II Adapter
As Patrick pointed out, this is clearly not an NVidia device. You can
find out which driver is actually handling it, by running "lspci -v".
On Wed, 2019-02-20 at 20:02 +1100, Stephen Morris wrote:
> On 20/2/19 4:55 pm, Samuel Sieb wrote:
> > On 2/19/19 1:37 AM, Stephen Morris wrote:
> > > I found the Xorg log and found the issue, Xorg couldn't find any
> > > screens to use with the Nvidia driver. Below is the data on the
> > > chipse
On 20/2/19 4:55 pm, Samuel Sieb wrote:
On 2/19/19 1:37 AM, Stephen Morris wrote:
I found the Xorg log and found the issue, Xorg couldn't find any
screens to use with the Nvidia driver. Below is the data on the
chipset that Xorg thinks is available.
(--) PCI:*(0@0:15:0) 15ad:0405:15ad:0405 re
On 2/19/19 1:37 AM, Stephen Morris wrote:
I found the Xorg log and found the issue, Xorg couldn't find any screens
to use with the Nvidia driver. Below is the data on the chipset that
Xorg thinks is available.
(--) PCI:*(0@0:15:0) 15ad:0405:15ad:0405 rev 0, Mem @
0xe800/134217728, 0xfe000
On 19/2/19 7:44 pm, Stephen Morris wrote:
On 19/2/19 7:17 pm, Stephen Morris wrote:
On 19/2/19 4:25 am, Rex Dieter wrote:
Stephen Morris wrote:
Given that it seems that F29 is standardizing
on Wayland instead of Xorg, why doesn't the KDE-desktop-environment
group also install this package to
On 19/2/19 7:17 pm, Stephen Morris wrote:
On 19/2/19 4:25 am, Rex Dieter wrote:
Stephen Morris wrote:
Given that it seems that F29 is standardizing
on Wayland instead of Xorg, why doesn't the KDE-desktop-environment
group also install this package to provide the needed Wayland
support so
KDE
On 19/2/19 4:25 am, Rex Dieter wrote:
Stephen Morris wrote:
Given that it seems that F29 is standardizing
on Wayland instead of Xorg, why doesn't the KDE-desktop-environment
group also install this package to provide the needed Wayland support so
KDE can be started under Wayland, rather than re
On 18/2/19 11:49 pm, Patrick O'Callaghan wrote:
On Mon, 2019-02-18 at 17:51 +0700, Outback Dingo wrote:
On Mon, Feb 18, 2019 at 4:18 PM Patrick O'Callaghan
wrote:
On Mon, 2019-02-18 at 19:45 +1100, Stephen Morris wrote:
Hi,
In order to install the KDE Desktop I used DNF to install the
Stephen Morris wrote:
> Given that it seems that F29 is standardizing
> on Wayland instead of Xorg, why doesn't the KDE-desktop-environment
> group also install this package to provide the needed Wayland support so
> KDE can be started under Wayland, rather than require the user to
> install it ma
On Mon, 2019-02-18 at 17:51 +0700, Outback Dingo wrote:
> On Mon, Feb 18, 2019 at 4:18 PM Patrick O'Callaghan
> wrote:
> > On Mon, 2019-02-18 at 19:45 +1100, Stephen Morris wrote:
> > > Hi,
> > >
> > > In order to install the KDE Desktop I used DNF to install the
> > > KDE-desktop-environmen
On Mon, Feb 18, 2019 at 4:18 PM Patrick O'Callaghan
wrote:
>
> On Mon, 2019-02-18 at 19:45 +1100, Stephen Morris wrote:
> > Hi,
> >
> > In order to install the KDE Desktop I used DNF to install the
> > KDE-desktop-environment group, which place a plasma entry in the desktop
> > manager deskto
On Mon, 2019-02-18 at 19:45 +1100, Stephen Morris wrote:
> Hi,
>
> In order to install the KDE Desktop I used DNF to install the
> KDE-desktop-environment group, which place a plasma entry in the desktop
> manager desktop list, but selecting this entry did not boot into KDE, it
> just cont
> Did you a) configure KDE to start from a saved session (System
> Settings->Startup and Shutdown->Session Management->Restore Manually
> Saved Session), and b) save the session configuration you want
> (Kickoff->Leave->Save Session).
No, I have "start with an empty session".
> Also, note that th
On Tue, 2014-04-01 at 06:59 +0200, Frédéric Bron wrote:
> Every second time I run KDE, the icons on the desktop are not there
> and the desktop is empty. Why? I am speaking of icons that are
> shortcuts to launch applications. KDE graphical component are still
> there.
> Frédéric
Did you a) config
On 08/31/2011 08:46 AM, Rahul Sundaram wrote:
> On 08/31/2011 04:44 PM, Adel ESSAFI wrote:
>> Hello
>> was the KDE desktop removed in F15??
>>
>> ~]# yum grouplist | grep -i kde
>> KDE Software Compilation
>> KDE Software Development
>>
>>
>> I don't find the corresponding group
>
> Softw
On 08/31/2011 04:44 PM, Adel ESSAFI wrote:
> Hello
> was the KDE desktop removed in F15??
>
> ~]# yum grouplist | grep -i kde
>KDE Software Compilation
>KDE Software Development
>
>
> I don't find the corresponding group
Software compilation is the current name but if you find the long na
On Aug 31, 2011, at 7:14 AM, Adel ESSAFI wrote:
was the KDE desktop removed in F15??
No.
KDE Software Compilation
I don't find the corresponding group
Yes, you did. The KDE Software Compilation is the current upstream
name.
smime.p7s
Description: S/MIME cryptographic signature
--
On 08/31/2011 07:14 PM, Adel ESSAFI wrote:
> Hello
> was the KDE desktop removed in F15??
>
> ~]# yum grouplist | grep -i kde
>KDE Software Compilation
>KDE Software Development
>
>
> I don't find the corresponding group
> regards
>
yum groupinfo "KDE Software Compilation"
--
Even if y
On 06/25/2011 04:14 AM, Anoop wrote:
>>
>> downgrading NetworkManager gets thing working again ... nm is
>> complaining bitterly in /var/log/messages ...
> I hit same issue today. Then updated 'kde-plasma-networkmanagement'
> from 'updates-testing' and the issue went away.
>
> Thanks,
> Anoop
On 06/25/2011 01:39 PM, Antonio Olivares wrote:
>
.
>>
>>
>
> Thank you very much Gene :)
>
> # yum update kde-plasma-networkmanagement --enablerepo=updates-testing
>
> fixed it for me.
>
> Regards,
>
> Antonio
Great - thank Anoop :-)
Now that you both tested it - I guess I'll go ahead
--- On Sat, 6/25/11, Genes MailLists wrote:
> From: Genes MailLists
> Subject: Re: kde-desktop crashes after update / NetworkManager
> To: "Community support for Fedora users"
> Cc: "Antonio Olivares"
> Date: Saturday, June 25, 2011, 9:45 AM
> On 0
On 06/25/2011 12:25 PM, Antonio Olivares wrote:
>
> --> Running transaction check
> ---> Package NetworkManager.i686 1:0.8.999-2.git20110509.fc15 will be a
> downgrade
> --> Processing Dependency: NetworkManager-glib = 1:0.8.999-2.git20110509.fc15
> for package: 1:NetworkManager-0.8.999-2.git20
--- On Fri, 6/24/11, Genes MailLists wrote:
> From: Genes MailLists
> Subject: Re: kde-desktop crashes after update / NetworkManager
> To: "Community support for Fedora users"
> Date: Friday, June 24, 2011, 9:11 PM
> On 06/24/2011 11:55 PM, Genes
> MailLists wrot
On 06/25/2011 12:58 AM, Ed Greshko wrote:
> On 06/25/2011 12:11 PM, Genes MailLists wrote:
>> On 06/24/2011 11:55 PM, Genes MailLists wrote:
>>> Best I can tell it is network manager - as soon as it starts - kde
>>> desktop crashes and goes away .. yikes!
>>>
>> downgrading NetworkManager gets th
On Sat, Jun 25, 2011 at 9:41 AM, Genes MailLists wrote:
> On 06/24/2011 11:55 PM, Genes MailLists wrote:
>> Best I can tell it is network manager - as soon as it starts - kde
>> desktop crashes and goes away .. yikes!
>>
>
> downgrading NetworkManager gets thing working again ... nm is
> complai
On 06/25/2011 12:11 PM, Genes MailLists wrote:
> On 06/24/2011 11:55 PM, Genes MailLists wrote:
>> Best I can tell it is network manager - as soon as it starts - kde
>> desktop crashes and goes away .. yikes!
>>
> downgrading NetworkManager gets thing working again ... nm is
> complaining bitterl
On 06/24/2011 11:55 PM, Genes MailLists wrote:
> Best I can tell it is network manager - as soon as it starts - kde
> desktop crashes and goes away .. yikes!
>
downgrading NetworkManager gets thing working again ... nm is
complaining bitterly in /var/log/messages ...
--
users mailing list
user
2010/3/29 Rex Dieter :
> Hiisi wrote:
>
>> 2010/3/29 Ed Greshko :
>>> On 03/29/2010 03:45 PM, amit rp wrote:
How do i install KDE desktop on my fedora 12 i686?
>>> I normally install KDE from the start... However, I hear...
>>>
>>> yum groupinstall "KDE (K Desktop Environment)"
>>>
>>> works
Hiisi wrote:
> 2010/3/29 Ed Greshko :
>> On 03/29/2010 03:45 PM, amit rp wrote:
>>> How do i install KDE desktop on my fedora 12 i686?
>> I normally install KDE from the start... However, I hear...
>>
>> yum groupinstall "KDE (K Desktop Environment)"
>>
>> works just fine...
>>
>>
>
>
> Sorry f
--- On Mon, 3/29/10, Hiisi wrote:
> 2010/3/29 Ed Greshko :
> > On 03/29/2010 03:45 PM, amit rp wrote:
> >> How do i install KDE desktop on my fedora 12
> i686?
> > I normally install KDE from the start... However, I
> hear...
> >
> > yum groupinstall "KDE (K Desktop Environment)"
> >
> > works j
On 03/29/2010 04:15 PM, Hiisi wrote:
> 2010/3/29 Ed Greshko :
>
>> On 03/29/2010 03:45 PM, amit rp wrote:
>>
>>> How do i install KDE desktop on my fedora 12 i686?
>>>
>> I normally install KDE from the start... However, I hear...
>>
>> yum groupinstall "KDE (K Desktop Environment)"
2010/3/29 Ed Greshko :
> On 03/29/2010 03:45 PM, amit rp wrote:
>> How do i install KDE desktop on my fedora 12 i686?
> I normally install KDE from the start... However, I hear...
>
> yum groupinstall "KDE (K Desktop Environment)"
>
> works just fine...
>
>
Sorry for hijacking the thread, but ho
On 03/29/2010 03:45 PM, amit rp wrote:
> How do i install KDE desktop on my fedora 12 i686?
I normally install KDE from the start... However, I hear...
yum groupinstall "KDE (K Desktop Environment)"
works just fine...
signature.asc
Description: OpenPGP digital signature
--
users mailing list
55 matches
Mail list logo
