Update on my original post. Thanks to Matthew Dash to Dock is working
great.
I also fixed a problem with Gnome freezing. I tried negativo Nvidia repo.
Unfortunately my graphics card was too old for the repo. However,
installing new repo required removing all of the fusion nvidia rpms. I did
find
John Mellor writes:
Turning off rhgb and quiet at boot results in the unquiet shutdown, but no
more enlightenment. The screen output looks ok.
Doing a "systemctl poweroff" causes the same hang as the normal poweroff
from CLI or from GUI.
I have not yet tried the suggestion to relabel
>
> When the system hangs, I have no keyboard or usable screen to debug
> with, as
> the system is almost all shutdown.
>
1)
is a second box and a null modem cable available to setup an serial console ?
currently I don't know/I'm unsure how to setup a serial console nowadays (did
that
On 11/10/19 10:17 AM, John Mellor wrote:
Turning off rhgb and quiet at boot results in the unquiet shutdown, but
no more enlightenment. The screen output looks ok.
Would you be able to type out what the last line on the screen is?
Doing a "systemctl poweroff" causes the same hang as the
On Sun, 10 Nov 2019 17:37:13 -
Cătălin George Feștilă wrote:
> any idea?
Two things.
Is there any message from alsa during boot? Look in
journalctl -b
to see the last boot.
Run the script you find here,
https://gist.github.com/craftyjon/902247
and run it as
bash alsa-info.sh
Paste the
On Sun, 10 Nov 2019 13:17:33 -0500
John Mellor wrote:
> I'm starting to suspect a broken ACPI change in the newer kernel, but
> I'm stuck...
Sure looks like it is a bug. Try installing the -debug kernel? At the
least it should give you more messages. You should probably open a
bugzilla
Samuel Sieb wrote:
> On 11/10/19 7:58 AM, SternData wrote:
>> Is there a problem in the backtrace server?
>
> Yes. There was a thread about that on a different list. I think it's
> running RHEL and as you can see in the output, the rpm on it doesn't support
> the new compression format zstd.
the sound device was gone ...
the pavucontrol tool shows an input sound play but on virtual output, Dummy
Output ...
I don't see anything with the hardware with this tool.
The arecord don't see anything:
$ arecord -l
arecord: device_list:272: no soundcards found...
The output of lspci
On 11/10/19 7:58 AM, SternData wrote:
Is there a problem in the backtrace server?
Yes. There was a thread about that on a different list. I think it's
running RHEL and as you can see in the output, the rpm on it doesn't
support the new compression format zstd.
On 2019-11-09 11:34 a.m., Tom Horsley wrote:
On Sat, 09 Nov 2019 11:00:42 -0500
john.mel...@gmail.com wrote:
I guess its possible that something is not completing its shutdown
step, but it does not appear to be logging that omission. Any idea how
to isolate which is the faulty daemon?
If you
the sound device was gone ...
the pavucontrol tool shows an input sound play but on virtual output, Dummy
Output ...
I don't see anything with the hardware with this tool.
The arecord don't see anything:
$ arecord -l
arecord: device_list:272: no soundcards found...
The output of lspci
Is there a problem in the backtrace server?
--- Running report_uReport ---
('report_uReport' completed successfully)
--- Running analyze_CCpp ---
Ok to upload core dump? (It may contain sensitive data). If your answer
is 'No', a stack trace will be generated locally. (It may download a
huge
On Sun, 10 Nov 2019 07:57:52 +0100
antonio montagnani wrote:
> I made a test switching from Gnome wayland to Gnome classic ans
> urprise it works as expected. So, I am going to file for a bug
> (component to blame is wayland I suppose)
That explains why I didn't see it, I run X.
s/inside/insight/
___
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/project/code-of-conduct/
List Guidelines:
agreed.
more inside in the log files needed.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
On 11/9/19 4:24 AM, Ed Greshko wrote:
They are indeed a good place to start, but they
only work under ideal conditions.
No, the upgrade plugin and the procedures are designed to work under "normal"
or "ordinary" conditions.
Hi Ed,
To me that sounds like a distinction without a difference.
On 11/2/19 1:12 AM, Roger Heflin wrote:
they are now putting an early cpio in the intramfs that includes
intel/amd firmware that will load before linux.
If you want to use cpio to see the 2nd part you will have to use a dd
if=initnam bs=512 skip= | zcat | cpio cmd
More easily,
17 matches
Mail list logo
