On Sun, 2023-04-23 at 08:05 +0100, Ron Yorston wrote:
> "User inactivity" is a poor criterion for suspending a machine.
+20,000
I have machines that run 24/7, whether *I* am using them, or *I* have
left them to their own devices. Even if I log out, I have the machines
doing things that I want th
Jeffrey Walton wrote:
>After 15 minutes of cleanup GDM suspended the machine with an active
>SSH connection.
I was bitten by this too. Left my system logged in to a GNOME desktop
carrying out some backups, went out for a walk, came back to find the
machine unresponsive.
As you say, this
On 04/22/2023 11:44 PM, Jeffrey Walton wrote:
I just keep upgrading it every 6 months.
Even so, there's no reason for you to be running it in full graphical
mode. Multi-user (what used to be runlevel 3) is all you need.
___
users mailing list -- us
On Sun, Apr 23, 2023 at 1:41 AM Joe Zeff wrote:
>
> On 04/22/2023 11:28 PM, Jeffrey Walton wrote:
> > After 15 minutes of cleanup GDM suspended the machine with an active
> > SSH connection.
>
> If the machine is headless, why are you running Gnome on it?
It used to be
On 04/22/2023 11:28 PM, Jeffrey Walton wrote:
After 15 minutes of cleanup GDM suspended the machine with an active
SSH connection.
If the machine is headless, why are you running Gnome on it?
___
users mailing list -- users@lists.fedoraproject.org
To
Hi Everyone,
I have a headless workstation that was upgraded from F37 to F38 this
morning. After the upgrade I SSH'd back in and began performing
post-install tasks, like cleaning up old packages and old symlinks.
After 15 minutes of cleanup GDM suspended the machine with an activ
Solution:
https://bugzilla.redhat.com/show_bug.cgi?id=1960937#c12
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/pro
It turns out the problem is with the radeon driver.
The GDM can be started normally once amdgpu is used instead of radeon
$ cat /proc/cmdline
BOOT_IMAGE=(hd0,gpt3)/ostree/fedora-b84e4d88fe04fad4bc33b6ea17b973b4c73cd56c60843527323ed31290b71b6c/vmlinuz-5.11.20-300.fc34.x86_64
root=UUID=6d7c04a4
The screen is hang on a text mode, all black with only the cursor blinking at
the upper left corner.
Ctrl+Alt+F3 switching works, and sway can be started without issues.
Yesterday still worked normally, but after some update, it shows this problem.
Silverblue Rawhide.20210511.n.2 is working (do
On 27/02/2021 19:18, Frederic Muller wrote:
YES! That was it! Thank you very much for refreshing something I never (or
seldom) use
Good. FWIW, I believe that gear used to appear much closer to the password
entry box making it
much more obvious.
--
People who believe they don't make mistakes
On 2/27/21 6:03 PM, Ed Greshko wrote:
On 27/02/2021 17:40, Frederic Muller wrote:
I did that in the past and can't find how to do it again. Being
searching the web and except forcing either type of session and
logging out and back in I haven't found any other way.
Does anyone know if it's sti
On 27/02/2021 17:40, Frederic Muller wrote:
I did that in the past and can't find how to do it again. Being searching the
web and except forcing either type of session and logging out and back in I
haven't found any other way.
Does anyone know if it's still possible and how to do it?
To me,
Hi!
I did that in the past and can't find how to do it again. Being
searching the web and except forcing either type of session and logging
out and back in I haven't found any other way.
Does anyone know if it's still possible and how to do it?
Thank you.
Fred
__
lp.gnome.org/admin/system-admin-guide/stable/login-banner.html.en
This method is much better than trying to muck around in the gdm user’s
homedir.
--
Jonathan Billings
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an em
On Thu, 3 Dec 2020 17:12:27 -0800
Samuel Sieb wrote:
> these are the steps that worked for me on Wayland
Sounds like useful info. I'll play around when I have time.
Thanks.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an e
On 12/3/20 4:32 PM, Tom Horsley wrote:
Can I run dconf-editor for a different user? (user gdm), or
find some other magical way to disable the notifications
that pop up while logging in?
If you can figure out the setting you need to change, you can add it to
the dconf database in /etc/dconf
Can I run dconf-editor for a different user? (user gdm), or
find some other magical way to disable the notifications
that pop up while logging in?
In particular there is a persistently annoying notification
that my mouse battery is low. I'm fairly certain it is really
the keyboard battery
Tim:
>> If you can't see what you're typing into, you might not be typing
>> into what you think you are. It might not be a locked screen, it
>> could simply be a black screen and you're typing your password into
>> something that might steal it.
>>
>> Get the screen up before you start typing pas
On 2020-06-29 13:41, Tim via users wrote:
> On Sun, 2020-06-28 at 21:35 -0700, Samuel Sieb wrote:
>> You can either start typing the password right away or press ESC to
>> get the shield up and focus the password field.
> I'd advise against that (typing passwords straight away), too.
>
> If you can
On Sun, 2020-06-28 at 21:35 -0700, Samuel Sieb wrote:
> You can either start typing the password right away or press ESC to
> get the shield up and focus the password field.
I'd advise against that (typing passwords straight away), too.
If you can't see what you're typing into, you might not be t
On 6/28/20 4:01 AM, Michael Schwendt wrote:
Has anyone also had this before with GNOME Shell in Fedora 32?
It is new behavior compared with older releases of Fedora.
When I return to a locked screen, my usual habit is to press Return
and then to enter the passphrase. That fails even if unhiding
On Mon, 29 Jun 2020 01:41:28 +0930
Tim via users wrote:
> I always hit a neutral key, like the shift key, to wake up a blanked
> screen.
I definitely noticed that anything you type to wake up
the lock screen is passed to the password entry field. So
it you hit "space" (which is what I'm used to d
On Sun, 2020-06-28 at 13:01 +0200, Michael Schwendt wrote:
> When I return to a locked screen, my usual habit is to press Return
> and then to enter the passphrase. That fails even if unhiding the
> passphrase and verifying that it has been entered correctly. The
> second time I enter the passphras
On 2020-06-28 20:05, Michael Schwendt wrote:
> On Sun, 28 Jun 2020 19:25:48 +0800, Ed Greshko wrote:
>
>> Next time you do it, count the dots just to make sure all keystrokes are
>> being registered.
>>
> I've done that before and have also clicked the "eye" icon to unhide the
> entered passphrase
On Sun, 28 Jun 2020 19:25:48 +0800, Ed Greshko wrote:
> Next time you do it, count the dots just to make sure all keystrokes are
> being registered.
>
I've done that before and have also clicked the "eye" icon to unhide the
entered passphrase, and it is shown correctly but will be rejected.
___
On 2020-06-28 19:01, Michael Schwendt wrote:
> Has anyone also had this before with GNOME Shell in Fedora 32?
> It is new behavior compared with older releases of Fedora.
>
> When I return to a locked screen, my usual habit is to press Return
> and then to enter the passphrase. That fails even if u
Has anyone also had this before with GNOME Shell in Fedora 32?
It is new behavior compared with older releases of Fedora.
When I return to a locked screen, my usual habit is to press Return
and then to enter the passphrase. That fails even if unhiding the passphrase
and verifying that it has been
32 and after
> the upgrade IPA users cannot log in via GDM into Gnome. I can Kinit users
> fine, or log in via another TTY, but using GDM once you enter the password
> the screen goes grey for a few seconds then returns to the login prompt.
>
> I then rebuilt and successfully joined a mac
Hello John,
Turning on Debug logging for GDM I see the following:
May 04 17:35:01 xlt6.i.xrs444.net gdm[1118]: GdmSession: Emitting
'session-exited' signal with exit code '70'
May 04 17:35:01 xlt6.i.xrs444.net gdm[1118]: GdmManager: session exited
with status 70
May 04 17:35:
On Saturday, May 9, 2020 10:03:39 PM MST Thomas Letherby wrote:
> Hello,
>
> Sorry for not replying earlier, I got caught up in work for the week.
>
> I confirmed the HBAC rules contained gdm and gdm-password. I don't think
> it's FreeIPA though as logins work under
Hello,
Sorry for not replying earlier, I got caught up in work for the week.
I confirmed the HBAC rules contained gdm and gdm-password. I don't think
it's FreeIPA though as logins work under F31 just fine, but I patched up
all the servers and still no dice.
Thanks,
Thomas
On Tue, M
he
login services, "gdm" and "gdm-password".
What you're describing sounds like what I was experiencing in Fedora a
few releases ago. I fixed it when I realized that "gdm" was one of the
HBAC services pre-defined in IPA and I didn't hav
nnot log in via GDM into Gnome. I can Kinit users
fine, or log in via another TTY, but using GDM once you enter the password
the screen goes grey for a few seconds then returns to the login prompt.
I then rebuilt and successfully joined a machine, but on login I can see
the prompts once the password
That fixed everything, Ed !
I nominate you and that top for the "bestest / fastest" online support ever
!
Have a great day !
LG
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
ings.
> >
> > Everything works perfectly, except that I can't log into a session with
> kdm or gdm because of an authentication error. I can log into a console
> session without any issues.
> >
> > I have never been able to log into a session using gdm. The sessi
The problem stems from fstab... one of the filesystems is mounted read only.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.or
ude=/tmp --exclude=/boot
>
> It worked fantastically well. I'll post the nity gritty details in another
> thread once I confirm a few things.
>
> Everything works perfectly, except that I can't log into a session with kdm
> or gdm because of an authentication error. I
t the nity gritty details in another
thread once I confirm a few things.
Everything works perfectly, except that I can't log into a session with kdm
or gdm because of an authentication error. I can log into a console
session without any issues.
I have never been able to log into a session
On 6/17/19 11:00 AM, Tim Evans wrote:
I have experienced similar issues with two different F29->F30 upgrades
via dnf. Although what happened wasn't identical on both upgrades, the
results were the same: After upgrade/reboot, the GDM login screen does
not show the primary (previously
On 6/17/19 3:42 PM, Ulf Volmer wrote:
On 17.06.19 17:00, Tim Evans wrote:
of flag, but they are apparently created on login, rather than being
permanent. On both systems the primary userid (UID 1000) is shown as:
SystemAccount=true
Have you checked /etc/login.defs?
Thank you, Ulf. Don't
On 17.06.19 17:00, Tim Evans wrote:
> of flag, but they are apparently created on login, rather than being
> permanent. On both systems the primary userid (UID 1000) is shown as:
>
> SystemAccount=true
Have you checked /etc/login.defs?
Best regards
Ulf
_
I have experienced similar issues with two different F29->F30 upgrades
via dnf. Although what happened wasn't identical on both upgrades, the
results were the same: After upgrade/reboot, the GDM login screen does
not show the primary (previously existing) user name (UID 1000).
In t
On Sun, 2 Jun 2019 22:12:06 +0100
Barry wrote:
> > As near as I can tell, wayland and X treat EDID differently.
>
> I though that the handling was the same, its in the kernel mode setting.
I would have thought that, but with nouveau and wayland I get visible data
on the screen, but a wacky non
> On 2 Jun 2019, at 14:53, Tom Horsley wrote:
>
> On Sun, 2 Jun 2019 11:05:23 +0100
> Barry Scott wrote:
>
>> That's the problem - bad EDID.
>
> As near as I can tell, wayland and X treat EDID differently.
I though that the handling was the same, its in the kernel mode setting.
> Also
> no
On 6/2/19 3:05 AM, Barry Scott wrote:
On 1 Jun 2019, at 19:47, Samuel Sieb wrote:
# find /sys/devices -name 'edid'
/sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid
/sys/devices/pci:00/:00:02.0/drm/card0/card0-VGA-1/edid
/sys/devices/pci:00/:00:02.0/drm/card0/car
On Sun, 2 Jun 2019 11:05:23 +0100
Barry Scott wrote:
> That's the problem - bad EDID.
As near as I can tell, wayland and X treat EDID differently. Also
nouveau and nvidia treat it differently.
I only get proper native resolution with nvidia and X getting
EDID from my LG OLED B6P TV.
https://bug
> On 1 Jun 2019, at 19:47, Samuel Sieb wrote:
>
> On 6/1/19 11:33 AM, Barry Scott wrote:
>> You can look at the details with:
>> $ xrandr --verboes | edid-decode
>> The "Detailed timing" are the monitors prefered mode I recall.
>
> # find /sys/devices -name 'edid'
> /sys/devices/pci:00/000
On 6/1/19 11:33 AM, Barry Scott wrote:
You can look at the details with:
$ xrandr --verboes | edid-decode
The "Detailed timing" are the monitors prefered mode I recall.
# find /sys/devices -name 'edid'
/sys/devices/pci:00/:00:02.0/drm/card0/card0-HDMI-A-1/edid
/sys/devices/pci:00/
> On 12 May 2019, at 23:47, Tom Horsley wrote:
>
> I have similar problems with using my LG OLEDB6P 4K TV as a
> monitor. The nouveau driver seems to be confused by the
> EDID information. Using X it picks some resolution the
> monitor can't even display (invalid signal on monitor),
> using way
I have similar problems with using my LG OLEDB6P 4K TV as a
monitor. The nouveau driver seems to be confused by the
EDID information. Using X it picks some resolution the
monitor can't even display (invalid signal on monitor),
using wayland I thought it worked, but when I examined
the details it pi
The most trivial F29 thing I've spotted so far :-).
I boot the system, get to the GDM login screen, and the
mouse cursor is down near the lower right hand corner
of the screen.
It used to be in the center right where the login prompt
shows up.
Does it work this way for everyone, or is
Hi all
Running an X session via GDM and awesome wm on one tty. And on another
tty there's another GDM login screen waiting ...
I'd like to get rid of that second and useless GDM login screen.
Permanently. Is it doable? Or do I need to switch to another display
manager?
Thank
after restarting my box, I can again run
gnome (wayland) sessions.
My login manager is gdm.
Anybody sees this too?
I'm not seeing this exact issue, I'm seeing an issue where if I use
Gnome or Gnome Classic, logout and try to login to Gnome (Wayland) it
attempts to start but gives up and ret
On 05/31/17 07:40, Rick Leir wrote:
> How many people like me will have a machine out of action for a week
> because that piece of doco did not jump out at them?
I would say an extremely small number. Why? Because the vast majority
would be installing a desktop and using the DM supplied with th
> No, I don't think there should be a dependency that a greeter is
> installed since it is documented that you can use lightdm without a
> greeter if you have an autologin setup.
Ed,
How many people like me will have a machine out of action for a week because
that piece of doco did not jump out
On 05/31/17 00:30, Rick Leir wrote:
>
> > as my cursory searches show, one needs to have a "greeter" installed
>
> Thanks for telling me, I had not heard of "greeter"s (embarrassed).
> Even though I remember FC6. Your advice is most welcome.
>
> Black screen .. that was my problem, and I was deep i
> as my cursory searches show, one needs to have a "greeter" installed
Thanks for telling me, I had not heard of "greeter"s (embarrassed). Even though
I remember FC6. Your advice is most welcome.
Black screen .. that was my problem, and I was deep into X11 logs trying to
find the fix. Do you t
-1.fc26.x86_64
@updates-testing
Install lightdm-gtk-2.0.2-4.fc26.x86_64 @fedora
Install lightdm-gtk-greeter-settings-1.2.0-6.fc26.noarch @fedora
I then rebooted and had lightdm running and a login screen which allowed
me to login my KDE desktop without issue. No need for
LightDM installed
>>> without gdm, gnome-shell, and mutter.
>>> I had a crash while attempting to login using LightDM:
>>
>> Of course F26 is still in Alpha. So, if you managed to get LightDM
>> installed without its dependencies you should report this on the
>&g
On 05/30/17 17:28, Ed Greshko wrote:
> On 05/30/17 17:15, Rick Leir wrote:
>> It seems that Fedora 26 allowed me to have KDM and LightDM installed
>> without gdm, gnome-shell, and mutter.
>> I had a crash while attempting to login using LightDM:
>
> Of course F26 is
On 05/30/17 17:15, Rick Leir wrote:
> It seems that Fedora 26 allowed me to have KDM and LightDM installed
> without gdm, gnome-shell, and mutter.
> I had a crash while attempting to login using LightDM:
Of course F26 is still in Alpha. So, if you managed to get LightDM
installed wi
Hi all
It seems that Fedora 26 allowed me to have KDM and LightDM installed
without gdm, gnome-shell, and mutter.
I had a crash while attempting to login using LightDM:
# journalctl -e
#2
0x7feb273ed783
gnome (wayland) sessions.
My login manager is gdm.
Anybody sees this too?
Kind regards
Joachim Backes
--
Fedora release 25 (Twenty Five)
Kernel-4.10.10-200.fc25.x86_64
Joachim Backes
https://www-user.rhrk.uni-kl.de/~backes/
___
users mailing list --
I'm running Fedora 25 on an iMac.
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Whistler [Radeon HD 6730M/6770M/7690M XT]
After a recent update, GDM will no longer come up. On bootup, I get a list of
activities, which ends at Gnome Display Manager, and the
On 10/21/2016 09:27 PM, Stephen Morris wrote:
On 21/10/16 10:48, Bryon Adams wrote:
On 10/20/2016 05:16 PM, Stephen Morris wrote:
On 20/10/16 11:54, Bryon Adams wrote:
On 10/19/2016 04:38 PM, Stephen Morris wrote:
Hi,
I have downloaded several themes from Gnome-looks.org for GDM,
but
On 21/10/16 18:27, Samuel Sieb wrote:
On 10/19/2016 01:38 PM, Stephen Morris wrote:
Does anyone have any ideas on where I need to put the extracted
directories and how I tell GDM which of those themes to use?
I'm pretty sure everyone that has commented so far is thinking of GTK
t
On 21/10/16 10:48, Bryon Adams wrote:
On 10/20/2016 05:16 PM, Stephen Morris wrote:
On 20/10/16 11:54, Bryon Adams wrote:
On 10/19/2016 04:38 PM, Stephen Morris wrote:
Hi,
I have downloaded several themes from Gnome-looks.org for GDM,
but I
can't find any documentation on the ne
On Fri, 2016-10-21 at 08:16 +1100, Stephen Morris wrote:
> I've extracted the files to their directories and copied
> them into /usr/share/themes, but none of the drop downs in the
> Appearance tab in Gnome-tweak-tool show any of the new themes. Is
> /usr/share/themes to locati
On 10/19/2016 01:38 PM, Stephen Morris wrote:
Does anyone have any ideas on where I need to put the extracted
directories and how I tell GDM which of those themes to use?
I'm pretty sure everyone that has commented so far is thinking of GTK
themes. GDM has become just a mode of
hemes to location for GDM themes?
I shall state the obvious: After doing that, did you log out and back
in again?
*Some* things (and I don't know if this is included), are only looked
into at login time. Changes after login may not be noticed.
--
tim@localhost ~]$ uname -rsvp
Linux 3.19.
On 10/20/2016 05:16 PM, Stephen Morris wrote:
On 20/10/16 11:54, Bryon Adams wrote:
On 10/19/2016 04:38 PM, Stephen Morris wrote:
Hi,
I have downloaded several themes from Gnome-looks.org for GDM, but I
can't find any documentation on the net for installing the theme (not
jus
On 20/10/16 11:54, Bryon Adams wrote:
On 10/19/2016 04:38 PM, Stephen Morris wrote:
Hi,
I have downloaded several themes from Gnome-looks.org for GDM, but I
can't find any documentation on the net for installing the theme (not
just the background picture) that actually works for F24.
On 10/19/2016 04:38 PM, Stephen Morris wrote:
Hi,
I have downloaded several themes from Gnome-looks.org for GDM, but I
can't find any documentation on the net for installing the theme (not
just the background picture) that actually works for F24. I've found
lots of documen
Hi,
I have downloaded several themes from Gnome-looks.org for GDM, but
I can't find any documentation on the net for installing the theme (not
just the background picture) that actually works for F24. I've found
lots of documentation for updating the default background, but non
My wife's laptop recently started having an issue where GDM will come up
but no users are listed.
Any attempt to go to a VT shows the dreaded:
A start job is running for Wait for Plymouth Boot to Quit
Which is never does.
Switching the display manager to lightdm works around the login
On Jun 22, 2016 13:05, "Samuel Sieb" wrote:
>
> On 06/22/2016 09:31 AM, Eric Griffith wrote:
>>
>> ldd /usr/lib64/xorg/modules/extensions/libglx.so
>>
>> libGL.so.1 => /usr/lib64/libglvnd/libGL.so.1 (0x7f5d15e9e000)
>> libGLX.so.0 => /usr/lib64/libglvnd/libGLX.so.0 (0x7f5d15172
On 06/22/2016 09:31 AM, Eric Griffith wrote:
ldd /usr/lib64/xorg/modules/extensions/libglx.so
libGL.so.1 => /usr/lib64/libglvnd/libGL.so.1 (0x7f5d15e9e000)
libGLX.so.0 => /usr/lib64/libglvnd/libGLX.so.0 (0x7f5d15172000)
libGLdispatch.so.0 => /usr/lib64/libglvnd/libGLdispa
55adcdb2b000)
libxcb.so.1 => /lib64/libxcb.so.1 (0x7f5d1450a000)
libXau.so.6 => /lib64/libXau.so.6 (0x7f5d14306000)
and dnf history
60 | remove flatpak-libs | 2016-06-22 12:18 | Erase |
12
59 | history undo 47 | 2016-06-22 02:14 | Erase
On 06/21/2016 11:16 PM, Eric Griffith wrote:
On Jun 22, 2016 01:45, "Samuel Sieb" mailto:sam...@sieb.net>> wrote:
ldd /usr/lib64/dri/i915_dri.so
ldd /usr/lib64/dri/swrast_dri.so
ldd /usr/lib64/xorg/modules/extensions/libglx.so
Will respond with ldd when I can SSH in.
Even if you can't paste
On 06/21/2016 11:16 PM, Eric Griffith wrote:
On Jun 22, 2016 01:45, "Samuel Sieb" mailto:sam...@sieb.net>> wrote:
What is the output of the following commands:
rpm -q mesa-dri-drivers
32 and 64 bit, version 11.2.2.-2.20160614.fc24
Ok, you didn't mention you were on F24. The Fedora number is
27;t PlayOnLinux install various bits and change settings?
>
PlayOnLinux installs...
Cabextract, gstreamer, iconutils, libXaw, p7zip, wxGTK3, wzBase3, wxPython,
and xterm. None of which shouts "Let's break mesa!" to me. Not sure on what
settings it might change.
Just to test, I undid t
On 06/21/2016 10:01 PM, Eric Griffith wrote:
I was using my system earlier tonight, trying to get a couple games
working in wine. Everything was fine.. until I ran PlayOnLinux. It
errored out with saying it couldn't find any OpenGL drivers for my
laptop (Intel Broadwell). Thought it was odd, but
Thought it was odd, but nothing was freaking out, so I didn't think
anything of it. Saw some updates come up, updated, rebooted, and everything
went to hell.
Now whenever I try to boot, GDM errors out
AIGLX error dlopen (path to i915_dri.so, and swrast) undefined symbol
_glapi_get
a text prompt (I assume all processes for runlevel 5 are complete) and
>>> displays "Please enter root password to continue" and then after around
>>> 30-40 seconds, it displays the GDM. I am at a loss as to what is causing
>>> this and I don't know where to start
splays the GDM. I am at a loss as to what is causing
this and I don't know where to start debugging this issue.
Have you looked at /var/log/boot.log, and if so, is there anything
interesting there?
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription
Hello all,
Recently I have seen that whenever I boot up my system, F22, it goes to a
text prompt (I assume all processes for runlevel 5 are complete) and
displays "Please enter root password to continue" and then after around
30-40 seconds, it displays the GDM. I am at a loss as
On Tue, Jun 30, 2015 at 9:36 AM, Chris Murphy wrote:
> If that solves the problem then it's likely related to gdm on Wayland
> and you can search for a bug to me too, or file a new one.
Actually best to file a new one because these problems all seem to be
GPU specific. So include a
On Tue, Jun 30, 2015 at 9:05 AM, Joachim Backes
wrote:
> Hi all F22 users,
>
> having the following problem in F22/gdm with my ATI-Radeon video card 5400:
>
> If logging out from a gnome3 session, it takes a very long time until
> the login screen of gdm re-appears (10-20 secs).
On 06/30/2015 11:05 AM, Joachim Backes wrote:
> having the following problem in F22/gdm with my ATI-Radeon video card 5400:
>
> If logging out from a gnome3 session, it takes a very long time until
> the login screen of gdm re-appears (10-20 secs). Some times I have to
> restart my
Hi all F22 users,
having the following problem in F22/gdm with my ATI-Radeon video card 5400:
If logging out from a gnome3 session, it takes a very long time until
the login screen of gdm re-appears (10-20 secs). Some times I have to
restart my box because the screen remains dark after logging
In /etc/gdm/custom.conf I have:
[daemon]
TimedLoginEnable=true
TimedLogin=mrsam
TimedLoginDelay=10
After updating to F22, the progress bar marks off the ten second wait and
then …nothing. I have to log in manually.
I tried adding WaylandEnable=false, this makes no difference.
Anyone know
On 06/03/2015 07:14 AM, Alex Regan wrote:
It's only a fraction of that here:
I'm using Fedora 22. It got bigger.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: htt
$ a=0; ps axfu | grep ^gdm| awk '{print $6}' | \
(while read x ; do a=$(( a + x )) ; done ; echo $a )
400760
Does anyone else notice that gdm's session takes up 300-400MB of RAM? I
typically defend GNOME, but this is kind of ridiculous.
Is this really an accurate repres
On 06/03/15 10:48, Gordon Messmer wrote:
> $ a=0; ps axfu | grep ^gdm| awk '{print $6}' | \
> (while read x ; do a=$(( a + x )) ; done ; echo $a )
> 400760
>
> Does anyone else notice that gdm's session takes up 300-400MB of RAM? I
> typically defend GNOME, b
$ a=0; ps axfu | grep ^gdm| awk '{print $6}' | \
(while read x ; do a=$(( a + x )) ; done ; echo $a )
400760
Does anyone else notice that gdm's session takes up 300-400MB of RAM? I
typically defend GNOME, but this is kind of ridiculous.
--
users mailing list
users@lists.fedor
On Tue, Jun 02, 2015 at 09:36:31AM -0500, Mike Chambers wrote:
>
> Reboot (not sure just logging off works) and should be using the one
> you chose.
The following sequence should be enough:
# systemctl isolate multi-user.target
# systemctl isolate graphical.target
Or maybe just stop the old
On 06/02/2015 01:56 AM, Rene Harder Olsen wrote:
Hello everybody.
I have read the mails about enabling lightdm and disabling gdm.
I have also tried it and what I found out was, it sets display manager
via and ln which it modifies by creating a new one for the one which is
enabled and removed
On Mon, 2015-06-01 at 09:12 -0400, Paul Cartwright wrote:
> On 06/01/2015 08:50 AM, Max Pyziur wrote:
> > It seems that my GDM is hosed also; I see that both gdm and lightdm
> > are installed (per fedup); how do I make the adjustment?
> >
> > Thank you.
> http://a
Hello everybody.
I have read the mails about enabling lightdm and disabling gdm.
I have also tried it and what I found out was, it sets display manager
via and ln which it modifies by creating a new one for the one which is
enabled and removed the one which is disabled.
Dnf says that kde and
!
>
> Is it then fair to assume that gdm is buggy? Both of my two other
> Fedora machines use gdm (x64s). Since fedup worked (for the most part)
> on this upgrade, should I be safe and flip to lightdm? Otherwise, I
> might have the same problem - no login screen indicating a buggy gdm
1 - 100 of 386 matches
Mail list logo
