Re: Fedora 41 Install: Black Screen

fully working and stock Fedora 40. Upon reboot to actually do the install steps, a black screen is presented and everything had to stop. For a second attempt, I elected to blow the Fedora-40 system away, and reinstall from iso.  The blackscreen was presented again, but this time there was also a

Re: Fedora 41 Install: Black Screen

fully working and stock Fedora 40.  Upon reboot to actually do the install steps, a black screen is presented and everything had to stop. This comment will probably annoy some people, but you really should bring this up on the test list. What do you mean by "everything had to stop"? D

Re: Fedora 41 Install: Black Screen

reboot to actually do the install steps, a black screen is presented and everything had to stop. For a second attempt, I elected to blow the Fedora-40 system away, and reinstall from iso. The blackscreen was presented again, but this time there was also a mouse pointer visible. Once again, there

Re: Fedora 41 Install: Black Screen

reboot to actually do the install > steps, a black screen is presented and everything had to stop. > > For a second attempt, I elected to blow the Fedora-40 system away, and > reinstall from iso. The blackscreen was presented again, but this time there > was also a mouse point

Fedora 41 Install: Black Screen

I have an older Fedora 40 machine that I tried to install Fedora 41 on, and got a surprise. For a first attempt, I tried the as-documented dnf system-upgrade steps on a fully working and stock Fedora 40.  Upon reboot to actually do the install steps, a black screen is presented and everything

Re: Black screen after login to F39

monitors in the past. >> >> I start the system in multi-user (CLI) mode and then run "startx" >> to start X11 and Plasma. (I started doing this in F38 because of >> sddm hanging, which I was not able to resolve.) >> >> When I log in with my user acc

Re: Black screen after login to F39

ot; > to start X11 and Plasma. (I started doing this in F38 because of > sddm hanging, which I was not able to resolve.) > > When I log in with my user account and run startx, I get a black > screen (extending across both monitors) with an X cursor. The > cursor moves in response

Re: Black screen after login to F39

t X11 and Plasma. (I started doing this in F38 because of > sddm hanging, which I was not able to resolve.) > When I log in with my user account and run startx, I get a black > screen (extending across both monitors) with an X cursor. The > cursor moves in response to the mouse, but

Re: Black screen after login to F39

t; to start X11 and Plasma.  (I started doing this in F38 because of > sddm hanging, which I was not able to resolve.) > > When I log in with my user account and run startx, I get a black > screen (extending across both monitors) with an X cursor.  The > cursor moves in response to th

Black screen after login to F39

lve.) When I log in with my user account and run startx, I get a black screen (extending across both monitors) with an X cursor. The cursor moves in response to the mouse, but neither left or right mouse button do anything. I can get to an alternate console using alt-F3 and kill the login. I have

Re: [8086:2e32] black screen instead of Xorg/KDM unless preempt=none mitigations=off

Felix Miata composed on 2023-07-19 22:49 (UTC-0400): > # inxi -GxxS > System: > Host: big41 Kernel: 6.3.12-200.fc38.x86_64 arch: x86_64 bits: 64 > compiler: gcc v: 2.39-9.fc38 Console: pty pts/0 DM: 1: KDM 2: XDM > Distro: Fedora release 38 (Thirty Eight) > Graphics: > Device-1: Intel

[8086:2e32] black screen instead of Xorg/KDM unless preempt=none mitigations=off

# inxi -GxxS System: Host: big41 Kernel: 6.3.12-200.fc38.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 2.39-9.fc38 Console: pty pts/0 DM: 1: KDM 2: XDM Distro: Fedora release 38 (Thirty Eight) Graphics: Device-1: Intel 4 Series Integrated Graphics vendor: Biostar Microtech Intl Corp

Re: After upgrade F33->F34, I get a black screen when logging in to Plasma (both Wayland and X11)

> Today, I eventually upgrading my F33 to F34. Everything looks fine > until I get teh sddm login screen. Here if I choose Plasma, either > Wayland or X11, I get a black screen with mouse, nothing else. I found the issue. It was not related to Fedora nor KDE: I had a locally compiled v

Re: After upgrade F33->F34, I get a black screen when logging in to Plasma (both Wayland and X11)

> Today, I eventually upgrading my F33 to F34. Everything looks fine > until I get teh sddm login screen. Here if I choose Plasma, either > Wayland or X11, I get a black screen with mouse, nothing else. How can I install the default desktop (GNOME) from command line on my KDE spin? M

Re: resume from sleep to a black screen

On 13/06/2021 20:02, Joe Zeff wrote: On 6/13/21 12:38 PM, lejeczek via users wrote: Anybody here with similar config to mine - Ryzen 4500U in a Lenovo laptop with external monitor connected - gets black screen instead of login prompt when resume from sleep? Have you tried using Ctrl+Alt+F2

Re: resume from sleep to a black screen

fine Regards René On 13. jun. 2021 at 21.04, Joe Zeff wrote: On 6/13/21 12:38 PM, lejeczek viaf users wrote: > Anybody here with similar config to mine - Ryzen 4500U in a Lenovo > laptop with external monitor connected - gets black screen instead of > login prompt when resume from sleep?

Re: resume from sleep to a black screen

os as well. Brian On 6/13/21 12:02 PM, Joe Zeff wrote: On 6/13/21 12:38 PM, lejeczek via users wrote: Anybody here with similar config to mine - Ryzen 4500U in a Lenovo laptop with external monitor connected - gets black screen instead of login prompt when resume from sleep? Have you tried using C

Re: resume from sleep to a black screen

On 6/13/21 12:38 PM, lejeczek via users wrote: Anybody here with similar config to mine - Ryzen 4500U in a Lenovo laptop with external monitor connected - gets black screen instead of login prompt when resume from sleep? Have you tried using Ctrl+Alt+F2 to get to a text console and logging in

resume from sleep to a black screen

Hi guys. Anybody here with similar config to mine - Ryzen 4500U in a Lenovo laptop with external monitor connected - gets black screen instead of login prompt when resume from sleep? After recent updates on f34 it started and I only can do Ctrl+Alt+Del to reboot the OS, no GUI logon. many

Re: login to black screen

did. Then login to deepin all I get is black screen with cursor. Tried login to kde. Same result. I finally was able to restore my .config directory from a backup (using CLI) and I'm back in business. My question for this group is, what happened? I wish I knew which config file got m

login to black screen

black screen with cursor. Tried login to kde. Same result. I finally was able to restore my .config directory from a backup (using CLI) and I'm back in business. My question for this group is, what happened? I wish I knew which config file got messed up so I could fix more easily. T

Re: VNC shows black screen

e machine running Fedora 29 with latest patches applied. I can connect and provide user's password but the screen is blank. On initial connection I got the Welcome Window that asked for keyboard style and such, but when I closed that window nothing but a black screen

Re: VNC shows black screen

is wrote: > I am trying to get Tiger VNC working on a home machine running Fedora 29 > with latest patches applied. > I can connect and provide user's password but the screen is blank. > > On initial connection I got the Welcome Window that asked for keyboard > style and su

VNC shows black screen

thing but a black screen and that's all I get now when I log in. If I remove the user and add her back I get the Welcome Window again, but when that is done again black screen. Essentially there is no way to start an application and nothing setting the background. Seems the window man

Re: sddm black screen:

Frédéric wrote: > Jul 08 21:41:15 gamma sddm-greeter[2174]: Failed to create OpenGL > context for format QSurfaceFormat(version 2.0, options > QFlags(), depthBufferSize 24, > redBufferSize -1, gree This is likely it: Jul 08 21:41:15 gamma sddm-greeter[2174]: Failed to create OpenGL context for

Re: sddm black screen:

> You showed a portion of the journal (one line): > Jul 08 21:41:18 gamma abrt-notification[2397]: Process 2167 > (sddm-greeter) crashed in ??() > > ... with the backtrace ... > > immediately before that should've been a log entry from sddm itself (instead > of abrt-notification) I see, here is wh

Re: sddm black screen:

Frédéric wrote: >>> #2 0x7fc06f4677a7 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5) >> >> This line means the fatal error was logged to syslog/journal. Look there >> for more details. > > But isn't it what journalctl gives me which I just showed? Where else > should I look at? You show

Re: sddm black screen: PAM unable to dlopen(/usr/lib64/security/pam_elogind.so)

>> #2 0x7fc06f4677a7 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5) > > This line means the fatal error was logged to syslog/journal. Look there > for more details. But isn't it what journalctl gives me which I just showed? Where else should I look at? F _

Re: sddm black screen: PAM unable to dlopen(/usr/lib64/security/pam_elogind.so)

Frédéric wrote: > #2 0x7fc06f4677a7 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5) This line means the fatal error was logged to syslog/journal. Look there for more details. -- Rex ___ users mailing list -- users@lists.fedoraproject.org To un

Re: sddm black screen: PAM unable to dlopen(/usr/lib64/security/pam_elogind.so)

I have the same problem too On Sun, Jul 8, 2018 at 12:46 PM, Frédéric wrote: > > in /etc/pam.d/sddm-greeter check to see if you have the line > > session optional pam_elogind.so > > I had it, I commented it with "-" and now I get status active > (running) for sddm. > However, t

Re: sddm black screen: PAM unable to dlopen(/usr/lib64/security/pam_elogind.so)

> in /etc/pam.d/sddm-greeter check to see if you have the line > session optional pam_elogind.so I had it, I commented it with "-" and now I get status active (running) for sddm. However, the login screen is still black with only the mouse. journalctl says: Jul 08 21:41:18 gamma

Re: sddm black screen: PAM unable to dlopen(/usr/lib64/security/pam_elogind.so)

On 07/07/2018 06:10 PM, solarflow99 wrote: ok, but how to start X from the CLI though? If you normally boot to a CLI, startx will work, but each DE generally has its own customized script. As an example, I use Xfce, and would properly use startxfce4.

Re: sddm black screen: PAM unable to dlopen(/usr/lib64/security/pam_elogind.so)

ok, but how to start X from the CLI though? On Fri, Jul 6, 2018 at 11:30 PM, Ed Greshko wrote: > On 07/07/18 12:29, Frédéric wrote: > > Hi, > > > > I upgraded F27 yesterday night and I cannot start sddm this morning. I > > just get a black screen with the mouse

Re: sddm black screen: PAM unable to dlopen(/usr/lib64/security/pam_elogind.so)

On 07/07/18 12:29, Frédéric wrote: > Hi, > > I upgraded F27 yesterday night and I cannot start sddm this morning. I > just get a black screen with the mouse. > Here is the output of systemctl status sddm: > ● sddm.service - Simple Desktop Display Manager >Loaded: loa

sddm black screen: PAM unable to dlopen(/usr/lib64/security/pam_elogind.so)

Hi, I upgraded F27 yesterday night and I cannot start sddm this morning. I just get a black screen with the mouse. Here is the output of systemctl status sddm: ● sddm.service - Simple Desktop Display Manager Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; vendor preset: disabled

Re: [F25] only black screen with KDE Plasma session

> Well, darn. I was hoping that a "startx" would at least output something > that could > give a clue as to why plasmashell is crashing. He, you are right, I have something in the terminal: xauth: file /home/fred/.serverauth.1393 does not exist X.Org X Server 1.19.3 Release Date: 2017-03-15 ..

Re: [F25] only black screen with KDE Plasma session

On 06/23/17 20:50, Frédéric Bron wrote: >> I would, based on another problem you recently had, that you do the >> following >> Again bring up the system in run level 3. Before you startx >> sudo setenforce 0 >> startx as your normal self. > I did that but it is not better :( Well, darn. I w

Re: [F25] only black screen with KDE Plasma session

> I would, based on another problem you recently had, that you do the > following > Again bring up the system in run level 3. Before you startx > sudo setenforce 0 > startx as your normal self. I did that but it is not better :( Thanks, Frédéric

Re: [F25] only black screen with KDE Plasma session

On 06/23/17 19:33, Frédéric Bron wrote: > I did that as user (not as root). I got: > $DISPLAY is not set or cannot connect to the X server Sorry That should have been "startx" and not "startkde" -- Fedora Users List - The place to go to speculate endlessly signature.asc Description: Ope

Re: [F25] only black screen with KDE Plasma session

On 06/23/17 19:28, Frédéric Bron wrote: > KCrash: Attempting to start /usr/bin/plasmashell from kdeinit > KCrash: Application 'plasmashell' crashing... > KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit Well, that is the problem. Although I must admit that at this point I'm not sur

Re: [F25] only black screen with KDE Plasma session

> Boot to run level 3. > Login in text mode. > startkde I did that as user (not as root). I got: $DISPLAY is not set or cannot connect to the X server Frédéric ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users

Re: [F25] only black screen with KDE Plasma session

> Try looking at ~/.xsession-errors just after things go black to see if > there's anything interesting. I find this: xset: bad font path element (#2), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or s

Re: [F25] only black screen with KDE Plasma session

On 06/23/17 18:50, Frédéric Bron wrote: >> Boot to run level 3. > how do I do that? > When the boot screen comes up with the kernel selections, press "e" to edit. Then scroll down to the linux16 line showing the kernel you are booting and append a 3. Then ctrl-x to continue the boot process. FW

Re: [F25] only black screen with KDE Plasma session

On 06/23/2017 03:49 AM, Frédéric Bron wrote: Since you can login from another system, or switch to a text terminal, can you check if /usr/bin/plasmashell is running when you have the black screen? I see that plasmashell starts just after login, then it disappears when the black screen comes

Re: [F25] only black screen with KDE Plasma session

> Boot to run level 3. how do I do that? Frédéric ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: [F25] only black screen with KDE Plasma session

> Since you can login from another system, or switch to a text terminal, can > you check > if /usr/bin/plasmashell is running when you have the black screen? I see that plasmashell starts just after login, then it disappears when the black screen comes. I can also see this for a few s

Re: [F25] only black screen with KDE Plasma session

> Are you able to plug a secondary screen in? If so, how does it behave? behaves the same. Frédéric ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: [F25] only black screen with KDE Plasma session

On 06/23/17 17:54, Frédéric Bron wrote: > I just tried multiple times again, still the blackout. > I also tried to use a different kernel but both 4.11.4 and 4.11.5 give > the same issue. > I have an nvidia card but I use the nouveau driver on this computer > (never installed the proprietary driver

Re: [F25] only black screen with KDE Plasma session

the proprietary driver). Since you can login from another system, or switch to a text terminal, can you check if /usr/bin/plasmashell is running when you have the black screen? -- Fedora Users List - The place to go to speculate endlessly signature.asc Description: OpenPGP di

Re: [F25] only black screen with KDE Plasma session

Hello Frédéric, On Fri, 23 Jun 2017 11:54:52 +0200 Frédéric Bron wrote: > > Well, it is a selection on the lower left of the sddm login screen. > > I have nothing there. > > >>> Since you can get to a text terminal. Have you tried creating another > >>> user and then > >>> logging in as t

Re: [F25] only black screen with KDE Plasma session

> Well, it is a selection on the lower left of the sddm login screen. I have nothing there. >>> Since you can get to a text terminal. Have you tried creating another user >>> and then >>> logging in as that user? >> just done it, same problem with the new user >> > > Humm. I just tried mul

Re: [F25] only black screen with KDE Plasma session

On 06/23/17 13:38, Frédéric Bron wrote: > Hi, > > Since this morning, after loging in on a Plasma KDE session, I can > first see the desktop then only a black screen with only the mouse > available, nothing else. > Ctrl+Alt+Suppr, brings the log out screen so I can log out. >

Re: [F25] only black screen with KDE Plasma session

On 06/23/17 15:03, Frédéric Bron wrote: > > The screen is not the issue because I get the ssdm login screen perfectly > well. > Also it's a laptop with an external screen. I have tested with and > without the external screen plug-in, same behaviour. OK, I didn't know what your HW was. FWIW, I ha

Re: [F25] only black screen with KDE Plasma session

> First, I can't see how any of the 3 packages updated would be in any way > responsible. > I assume you've already booted at least once more. I tried 3-4 times. > Have you also re-seated video > cables? I've had unexplained video issues cleared up by doing that. The screen is not the issue b

Re: [F25] only black screen with KDE Plasma session

On 06/23/17 13:38, Frédéric Bron wrote: > Since this morning, after loging in on a Plasma KDE session, I can > first see the desktop then only a black screen with only the mouse > available, nothing else. > Ctrl+Alt+Suppr, brings the log out screen so I can log out. > I can also s

[F25] only black screen with KDE Plasma session

Hi, Since this morning, after loging in on a Plasma KDE session, I can first see the desktop then only a black screen with only the mouse available, nothing else. Ctrl+Alt+Suppr, brings the log out screen so I can log out. I can also switch to a text terminal with Ctrl+Alt+F2. That's all. B

Re: black screen

On 04/17/2017 09:28 PM, Frédéric Bron wrote: You might try activating the Magic Sysrq Key and using that instead Thanks, I will try that next time. It's good to know. If you're planning on trying it, activate it now because if you need it, it's too late. You might consider experimenting with

Re: black screen

> You might try activating the Magic Sysrq Key and using that instead Thanks, I will try that next time. It's good to know. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org

list replying, was: black screen

Allegedly, on or about 17 April 2017, Joe Zeff sent: > BTW, when I started to compose this, Thunderbird wanted to send it > only to the poster, not the list. Odd. I'm using Evolution, an old one at the moment. When I hit reply I get a requester popping up asking: /-

Re: black screen

On 04/17/2017 12:42 PM, Frédéric Bron wrote: The only thing that works is to log to a console windows blind with Ctrl+Alt+F2, then login as root without seeing anything (still black screen) and type reboot. You might try activating the Magic Sysrq Key and using that instead: http

black screen

works is to log to a console windows blind with Ctrl+Alt+F2, then login as root without seeing anything (still black screen) and type reboot. This happened twice in the last 2 days. Frédéric ___ users mailing list -- users@lists.fedoraproject.o

Re: Black screen and no response after fedup update to 22?

Michael D. Setzer II wrote: > Just did the update on another older notebook on Saturday, and got the > same black screen and no response after trying to login. Did just the hard > reboot, and opened a terminal window. Installed lightdm, and did the > switch to lightdm instead of gdm,

Black screen and no response after fedup update to 22?

diabling gdm.server after downloading lightdm and making it the active service. But since I had done a number of things, wasn't 100% sure that was it. Just did the update on another older notebook on Saturday, and got the same black screen and no response after trying to login. Did just t

Re: Fedora 23 with KDE: black screen when logout

On Fri, 20 Nov 2015 19:54:25 +0100, Frédéric Bron wrote: > I get a black screen when I logout from my Plasma session. What's wrong > with F23 with KDE, nothing works as before? > Are we obliged to use Gnome? A whole passel of us have been using xfce for months if not y

Re: Fedora 23 with KDE: black screen when logout

> Did you wait long enough? I have noticed that it can > take a while before the display manager is relaunched > (in my case gdm), although it has gotten pretty smooth > in the recent past. more than 1 minute. Frédéric -- users mailing list users@lists.fedoraproject.org To unsubscribe or change

Re: Fedora 23 with KDE: black screen when logout

Frédéric Bron wrote: > I get a black screen when I logout from my Plasma session. Did you wait long enough? I have noticed that it can take a while before the display manager is relaunched (in my case gdm), although it has gotten pretty smooth in the recent past. -- users mailing l

Fedora 23 with KDE: black screen when logout

I get a black screen when I logout from my Plasma session. What's wrong with F23 with KDE, nothing works as before? Are we obliged to use Gnome? Frédéric -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/ma

Re: Booting up to black screen - Log included

I googled about and saw something somebody else tried. I renamed nvidia-xorg.conf to xorg.conf and thus far this seems to have resolved the issue... On 03/07/2015 07:23 PM, Martin Cigorraga wrote: Hello, it's a GPU modules issue, by all means; I experienced the very same the first time I boot

Re: Booting up to black screen - Log included

On 07.03.2015 13:45, linuxnuts...@videotron.ca wrote: ... > boot up to a blank screen. I'm using akmod-nvidia-340xx, but reverting > back to nouveau did not solve the issue. ... NOUVEAU TEST: Part I # yum erase \*nvidia\* # dracut -f # systemctl set-default multi-user.target # systemctl reboo

Re: Booting up to black screen - Log included

Hello, it's a GPU modules issue, by all means; I experienced the very same the first time I booted into the live environment to install Fedora. You need to find a workaround, maybe by adding the needed parameters in your kernel boot line. Regards. On Sat, Mar 7, 2015 at 9:45 AM, wrote: > Greetin

Booting up to black screen - Log included

Greetings, I previously posted that since a fedup to fedora 21, I intermittently boot up to a blank screen. I'm using akmod-nvidia-340xx, but reverting back to nouveau did not solve the issue. One out of every 3 boot results in the problem. I pressed ctrl+alt+F2 and logged in and attempted the

Re: F20: HDMI + Win+P == GDM black screen

2014-04-09 9:35 GMT+01:00 Pedro Francisco : > Didn't work though. Opened bug #1085566 @ > https://bugzilla.redhat.com/show_bug.cgi?id=1085566 Clean reinstall fixed it. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.or

Re: F20: HDMI + Win+P == GDM black screen

2014-04-08 15:57 GMT+01:00 Tim : > Allegedly, on or about 08 April 2014, Pedro Francisco sent: >> a) where does GDM store its monitor settings? > > "locate monitors.xml" as the root user, so you can find all instances of > it on your hard drive. Thanks :) Didn't work though. Opened bug #1085566 @

Re: F20: HDMI + Win+P == GDM black screen

Allegedly, on or about 08 April 2014, Pedro Francisco sent: > a) where does GDM store its monitor settings? "locate monitors.xml" as the root user, so you can find all instances of it on your hard drive. -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UT

F20: HDMI + Win+P == GDM black screen

So, I've used HDMI for the first time this weekend. I have pressed Win+P a few times which resulted in a black screen (turned off, I guess). Suspending and resuming would turn on the internal monitor again (I had the session running so it was easy). But now, after a warm reboot, my GDM

Re: Fedora 19 bugfix causing plymouth black screen (ctrl+alt+F2 won’t work)

On 07/14/13 10:17, Powell, Michael wrote: > Looks like someone beat me to it :) > https://bugzilla.redhat.com/show_bug.cgi?id=984121 Yeah, and it seems you can download and test a potential fix at, https://admin.fedoraproject.org/updates/FEDORA-2013-12886/xorg-x11-server-1.14.2-4.fc19 -- The o

RE: Fedora 19 bugfix causing plymouth black screen (ctrl+alt+F2 won’t work)

> On 07/14/13 09:39, Powell, Michael wrote: > >> On 07/14/13 07:30, Powell, Michael wrote: > >>> Greshko, Ed wrote:> > /var/log/yum.log has date/time updates were applied > >>> Thanks, Ed. Unfortunately I don't need a timestamp of when the > >> updates were applied to the machine, but instead,

Re: Fedora 19 bugfix causing plymouth black screen (ctrl+alt+F2 won’t work)

On 07/14/13 09:39, Powell, Michael wrote: >> On 07/14/13 07:30, Powell, Michael wrote: >>> Greshko, Ed wrote:> /var/log/yum.log has date/time updates were applied >>> Thanks, Ed. Unfortunately I don't need a timestamp of when the >> updates were applied to the machine, but instead, I need a ti

RE: Fedora 19 bugfix causing plymouth black screen (ctrl+alt+F2 won’t work)

> On 07/14/13 07:30, Powell, Michael wrote: > > Greshko, Ed wrote:> > >> /var/log/yum.log has date/time updates were applied > > Thanks, Ed. Unfortunately I don't need a timestamp of when the > updates were applied to the machine, but instead, I need a timestamp of > when those updates were posted

Re: Fedora 19 bugfix causing plymouth black screen (ctrl+alt+F2 won’t work)

On 07/14/13 07:30, Powell, Michael wrote: > Greshko, Ed wrote:> >> /var/log/yum.log has date/time updates were applied > Thanks, Ed. Unfortunately I don't need a timestamp of when the updates were > applied to the machine, but instead, I need a timestamp of when those updates > were posted to th

RE: Fedora 19 bugfix causing plymouth black screen (ctrl+alt+F2 won’t work)

Greshko, Ed wrote:> > /var/log/yum.log has date/time updates were applied Thanks, Ed. Unfortunately I don't need a timestamp of when the updates were applied to the machine, but instead, I need a timestamp of when those updates were posted to the yum server. My thought is that since I know 191

Re: Fedora 19 bugfix causing plymouth black screen (ctrl+alt+F2 won’t work)

On 07/14/13 06:46, Powell, Michael wrote: > Is there some way I can have yum update based on a timestamp or display a > timestamp on when these updates were posted to help me narrow the field? /var/log/yum.log has date/time updates were applied -- The only thing worse than a poorly asked questi

Fedora 19 bugfix causing plymouth black screen (ctrl+alt+F2 won’t work)

The machine details: - Dell XPS 17 (L702X) BIOS A19 - Intel Core i7-2720QM (2.2GHZ) - Intel Sandybridge - Nvidia GeForce GT 555M >From a complete fresh install of F19, I’m seeing 214 updates. The updates >break down into 8 security, 80 bugfix, 22 enhanceme

Re: getting back from a black screen

Tim Evans wrote: On 04/08/2013 01:41 PM, Bill Davidsen wrote: Tim Evans wrote: On 04/08/2013 11:24 AM, Tim wrote: Allegedly, on or about 08 April 2013, Richard Vickery sent: In the case where you have sensitive information that you don't want people looking at it, or children deleting it, how

Re: getting back from a black screen

On 04/08/2013 01:41 PM, Bill Davidsen wrote: Tim Evans wrote: On 04/08/2013 11:24 AM, Tim wrote: Allegedly, on or about 08 April 2013, Richard Vickery sent: In the case where you have sensitive information that you don't want people looking at it, or children deleting it, how does one get back

Re: getting back from a black screen

On 04/08/2013 01:00 PM, Richard Vickery wrote: 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 0c) OK, not

Re: getting back from a black screen

On Mon, Apr 8, 2013 at 12:49 PM, Alan Gagne wrote: > On 04/08/2013 12:31 PM, Reindl Harald wrote: > >** > >* [harry at srv-rhsoft > >:~]$ lspci | grep -i > >graphic* > > AHA! Two ways to do it. How Unix! > > > And let's add a twist to f

RE:getting back from a black screen

On 04/08/2013 12:31 PM, Reindl Harald wrote: >/ />/ [harry at srv-rhsoft :~]$ lspci | grep -i graphic / AHA! Two ways to do it. How Unix! And let's add a twist to find out your drivers. [dw-agagne ~]# lspci | grep VGA 01:00.0 VGA com

Re: getting back from a black screen

On 04/08/2013 12:31 PM, Reindl Harald wrote: [harry@srv-rhsoft:~]$ lspci | grep -i graphic AHA! Two ways to do it. How Unix! -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: h

Re: getting back from a black screen

On 04/08/2013 12:29 PM, Richard Vickery wrote: I don't believe so; what's the command that prints the hardware? lspci | grep VGA However, if you have to ask, you probably aren't using the binary blob drivers, either directly from the OEM, in either the kmod or akmod package, unless it's been

Re: getting back from a black screen

Am 08.04.2013 21:29, schrieb Richard Vickery: > > > > On Mon, Apr 8, 2013 at 12:21 PM, Joe Zeff > wrote: > > On 04/08/2013 11:57 AM, Richard Vickery wrote: > > How do I find this bug in order to report it? And is it worth > reporting > since f19 wil

Re: getting back from a black screen

On Mon, Apr 8, 2013 at 12:21 PM, Joe Zeff wrote: > On 04/08/2013 11:57 AM, Richard Vickery wrote: > >> How do I find this bug in order to report it? And is it worth reporting >> since f19 will be beta soon, at which time I'll upgrade? >> >> > Before you do, one question: are you using nVidia grap

Re: getting back from a black screen

On 04/08/2013 11:57 AM, Richard Vickery wrote: How do I find this bug in order to report it? And is it worth reporting since f19 will be beta soon, at which time I'll upgrade? Before you do, one question: are you using nVidia graphics, and if so, are you using the proprietary drivers, or nouv

Re: getting back from a black screen

On Apr 8, 2013 7:18 AM, "Michael Schwendt" wrote: > > On Mon, 8 Apr 2013 06:52:04 -0700, Richard Vickery wrote: > > > > On Sun, 7 Apr 2013 19:45:43 -0700, Richard Vickery wrote: > > > > > > > Hi, > > > > > > > > It happens often enough that I leave the computer long enough for it to > > > > blacke

Re: getting back from a black screen

On 04/08/2013 07:18 AM, Michael Schwendt wrote: In other words, people in this thread have misunderstood eachother. "Locking" the screen does not refer to freezing the machine or crashing X but just to displaying a passphrase prompt after you've left the machine unattended for some time. That can

Re: getting back from a black screen

Tim Evans wrote: On 04/08/2013 11:24 AM, Tim wrote: Allegedly, on or about 08 April 2013, Richard Vickery sent: In the case where you have sensitive information that you don't want people looking at it, or children deleting it, how does one get back from this screen without rebooting and losing

Re: getting back from a black screen

On 04/08/2013 11:24 AM, Tim wrote: Allegedly, on or about 08 April 2013, Richard Vickery sent: In the case where you have sensitive information that you don't want people looking at it, or children deleting it, how does one get back from this screen without rebooting and losing ones work? As s

Re: getting back from a black screen

Allegedly, on or about 08 April 2013, Richard Vickery sent: > In the case where you have sensitive information that you don't want > people looking at it, or children deleting it, how does one get back > from this screen without rebooting and losing ones work? As soon as you go for the mouse or k

Re: getting back from a black screen

On Mon, 8 Apr 2013 06:52:04 -0700, Richard Vickery wrote: > > On Sun, 7 Apr 2013 19:45:43 -0700, Richard Vickery wrote: > > > > > Hi, > > > > > > It happens often enough that I leave the computer long enough for it to > > > blacken the screen. Is there a combination key stroke to get x back? > > >

Re: getting back from a black screen

On Apr 8, 2013 5:18 AM, "Michael Schwendt" wrote: > > On Sun, 7 Apr 2013 19:45:43 -0700, Richard Vickery wrote: > > > Hi, > > > > It happens often enough that I leave the computer long enough for it to > > blacken the screen. Is there a combination key stroke to get x back? > > Do you mean your co

  1   2   >