On Tue, Apr 1, 2025 at 9:05 AM Robert Moskowitz wrote:
>
> I am at a meeting and resumed on battery. The system started up and
> pretty much shut right off.
>
> On reboot I saw a message which I found be grepping /var/log/message
>
> Apr 1 08:45:51 LX140e-3 kernel: ACPI: \_SB_.PCI0.LPC0.EC__.HKE
And I am having no apparent issue operating on battery.
I AM going to have to find a plug soon. And will suspend, then resume
while being plugged in.
On 4/1/25 9:04 AM, Robert Moskowitz wrote:
I am at a meeting and resumed on battery. The system started up and
pretty much shut right off.
ARGH! Work. But not while I am at this meeting...
On 4/1/25 11:50 AM, Roger Heflin wrote:
There is no resume when something crashes because nothing ever got
saved to resume.
And I would not assume that the last message/"error" on your screen
has anything to do with the crash. T
There is no resume when something crashes because nothing ever got
saved to resume.
And I would not assume that the last message/"error" on your screen
has anything to do with the crash. The message/"error" in question
may actually happen on EVERY boot and when it crashes
On 4/1/25 11:10 AM, Germano Massullo wrote:
Il 01/04/25 16:22, Robert Moskowitz ha scritto:
https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x140e/downloads/ds038561-bios-update-utility-bootable-cd-for-windows-10-81-8-64-bit-7-32-bit-64-bit-thi
On 4/1/25 11:03 AM, Jeffrey Walton wrote:
On Tue, Apr 1, 2025 at 11:01 AM Robert Moskowitz wrote:
On 4/1/25 10:46 AM, Jeffrey Walton wrote:
On Tue, Apr 1, 2025 at 10:23 AM Robert Moskowitz wrote:
How can I find out my firmware ver without rebooting into setup? Is
there some Linux tool to
Il 01/04/25 16:22, Robert Moskowitz ha scritto:
https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x140e/downloads/ds038561-bios-update-utility-bootable-cd-for-windows-10-81-8-64-bit-7-32-bit-64-bit-thinkpad-x140e?category=BIOS%2FUEFI
[...]
But
On Tue, Apr 1, 2025 at 11:01 AM Robert Moskowitz wrote:
>
> On 4/1/25 10:46 AM, Jeffrey Walton wrote:
> > On Tue, Apr 1, 2025 at 10:23 AM Robert Moskowitz
> > wrote:
> >> How can I find out my firmware ver without rebooting into setup? Is
> >> there some Linux tool to report this?
> > dmidecode
On 4/1/25 10:46 AM, Jeffrey Walton wrote:
On Tue, Apr 1, 2025 at 10:23 AM Robert Moskowitz wrote:
How can I find out my firmware ver without rebooting into setup? Is
there some Linux tool to report this?
dmidecode
BIOS Information
Vendor: LENOVO
Version: GSET74WW (2.19 )
Relea
On Tue, Apr 1, 2025 at 10:23 AM Robert Moskowitz wrote:
>
> How can I find out my firmware ver without rebooting into setup? Is
> there some Linux tool to report this?
dmidecode
> It looks like from
>
> https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/t
How can I find out my firmware ver without rebooting into setup? Is
there some Linux tool to report this?
It looks like from
https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x140e/downloads/ds038561-bios-update-utility-bootable-cd-for-windows-
I have had this box for a lot of years (back to F32?). I really should
see what the firmware levels are now...
On 4/1/25 9:53 AM, Jeffrey Walton wrote:
On Tue, Apr 1, 2025 at 9:05 AM Robert Moskowitz wrote:
I am at a meeting and resumed on battery. The system started up and
pretty much shut
I am at a meeting and resumed on battery. The system started up and
pretty much shut right off.
On reboot I saw a message which I found be grepping /var/log/message
Apr 1 08:45:51 LX140e-3 kernel: ACPI: \_SB_.PCI0.LPC0.EC__.HKEY: BCTG
evaluated
but flagged as error
Apr 1 08:45:51 LX140e-3
I have the same issue after updating today. This is what appears in system log:
Oct 07 23:38:00 localhost.localdomain plasmashell[3571]: dbus[3571]: arguments
to dbus_message_new_method_call() were incorrect, assertion "destination ==
NULL || _dbus_check_is_valid_bus_name (destination)" failed i
On Sat, 2023-10-07 at 15:47 +, Alex Gurenko via users wrote:
> There is been a lot of discussion already that resulted in several BZs
> [0][1] opened and worked on. Generally caused by relatively recent
> change [2].
So a fix ls likely to appear soon.
I thought it would be interesting to see
There is been a lot of discussion already that resulted in several BZs [0][1]
opened and worked on. Generally caused by relatively recent change [2].
Quick workaround is to comment out or remove this line:
`DBusActivatable=true`
from
`/usr/share/applications/firefox.desktop`
I hope that helps
On Sat, 07 Oct 2023 03:44:56 -0700
Jonathan Ryshpan wrote:
> After the latest upgrade to Fedora, when Firefox is started from the
> panel, the screen goes dark, and then refreshes itself; Firefox does
> not start. Firefox appears to start perfectly when run from the
> console or from the applicat
After the latest upgrade to Fedora, when Firefox is started from the
panel, the screen goes dark, and then refreshes itself; Firefox does not
start. Firefox appears to start perfectly when run from the console or
from the application launcher. I have attached a fragment of the system
log showing ac
On Sun, 16 Apr 2023 16:45:09 +0100
Barry wrote:
> Its not a check as such.
> Masking means the service is defined as /dev/null, hard to start when
> there is nothing defined.
True that. :-)
___
users mailing list -- users@lists.fedoraproject.org
To un
On Sun, 16 Apr 2023 07:38:56 -0700
stan wrote:
> On Sat, 15 Apr 2023 04:59:48 -
> "Andre Robatino" wrote:
>
> > > On Tue, 11 Apr 2023 00:59:59 -0700
> > > Jonathan Ryshpan > >
> > >
> > > I masked systemd-oomd.service because I have real swap,
> >
> > Masking it is unreliable becaus
> On 16 Apr 2023, at 15:39, stan via users
> wrote:
>
> On Sat, 15 Apr 2023 04:59:48 -
> "Andre Robatino" wrote:
>
>>> On Tue, 11 Apr 2023 00:59:59 -0700
>>> Jonathan Ryshpan >>
>>>
>>> I masked systemd-oomd.service because I have real swap,
>>
>> Masking it is unreliable because i
On Sat, 15 Apr 2023 04:59:48 -
"Andre Robatino" wrote:
> > On Tue, 11 Apr 2023 00:59:59 -0700
> > Jonathan Ryshpan >
> >
> > I masked systemd-oomd.service because I have real swap,
>
> Masking it is unreliable because it might start running again if
> system-oomd-defaults is updated or
On Sat, Apr 15, 2023 at 3:48 PM Andre Robatino
wrote:
>
> I don't know enough about systemd to think that's even a bug - I had assumed
> it was normal behavior. In any case the bug that was forcing me to disable
> the OOM killer ( https://bugzilla.redhat.com/show_bug.cgi?id=2177722 ) has
> been
I don't know enough about systemd to think that's even a bug - I had assumed it
was normal behavior. In any case the bug that was forcing me to disable the OOM
killer ( https://bugzilla.redhat.com/show_bug.cgi?id=2177722 ) has been fixed
so I'm not disabling it anymore.
_
On Sat, Apr 15, 2023 at 1:05 PM Andre Robatino
wrote:
>
> On F37, masking was the first thing I tried. Then after a systemd update, I
> noticed it was running again, even though it was still masked (verified by
> "systemctl status systemd-oomd" which showed it both running and masked at
> the s
On F37, masking was the first thing I tried. Then after a systemd update, I
noticed it was running again, even though it was still masked (verified by
"systemctl status systemd-oomd" which showed it both running and masked at the
same time).
___
users
On 4/14/23 22:06, Andre Robatino wrote:
I just tried masking/reinstalling just now and it didn't restart. I experienced
it before with a systemd update so it might require that. But masking is
definitely not 100% effective.
Masking should be 100% effective. It changes files in /etc which sho
I just tried masking/reinstalling just now and it didn't restart. I experienced
it before with a systemd update so it might require that. But masking is
definitely not 100% effective.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscrib
> On Tue, 11 Apr 2023 00:59:59 -0700
> Jonathan Ryshpan
>
> I masked systemd-oomd.service because I have real swap,
Masking it is unreliable because it might start running again if
system-oomd-defaults is updated or reinstalled. (To check this, try
reinstalling it.) It's better to just remove
On Tue, 2023-04-11 at 09:49 -0700, Jonathan Ryshpan wrote:
> On Tue, 2023-04-11 at 08:30 -0700, stan via users wrote:
> > On Tue, 11 Apr 2023 00:59:59 -0700
> > Jonathan Ryshpan wrote:
> > > On Mon, 2023-04-10 at 22:21 -0400, Go Canes wrote:
> > > > On Mon, Apr 10, 2023 at 8:53 PM Jonathan Ryshpan
On Mon, Apr 10, 2023, at 5:52 PM, Jonathan Ryshpan wrote:
> Starting Oracle's VirtualBox has started to crash other apps, in
> particular Thunderbird, Firefox, and Libreoffice;
[snip]
I assume it is not just starting the VirtualBox Manager that is doing this.
It might help to know how much memor
On Tue, 2023-04-11 at 08:30 -0700, stan via users wrote:
> On Tue, 11 Apr 2023 00:59:59 -0700
> Jonathan Ryshpan wrote:
> > On Mon, 2023-04-10 at 22:21 -0400, Go Canes wrote:
> > > On Mon, Apr 10, 2023 at 8:53 PM Jonathan Ryshpan
> > > wrote:
> > > > Starting Oracle's VirtualBox has started to
This is unlikely to be the problem, but it is a fun story:
Many years ago there was a bug in the KVM kernel code that failed to
correctly context switch all the registers in virtual machines.
In this case, the somewhat obscure debug registers. So if I was
running debugger tests inside a virtual ma
On Tue, 11 Apr 2023 00:59:59 -0700
Jonathan Ryshpan wrote:
> On Mon, 2023-04-10 at 22:21 -0400, Go Canes wrote:
> > On Mon, Apr 10, 2023 at 8:53 PM Jonathan Ryshpan
> > wrote:
> > > Starting Oracle's VirtualBox has started to crash other apps, in
> > > particular Thunderbird, Firefox, and Libr
learnt to regularly press "CTRL S" to
> save the current status of whatever I was working on, because crashes,
> power outages, cats, and nearby twits with a bad sense of humour can
> so easily wreck a lot of hard work in a fraction of a second.
>
> These days, that&#
On Mon, 2023-04-10 at 22:21 -0400, Go Canes wrote:
> On Mon, Apr 10, 2023 at 8:53 PM Jonathan Ryshpan
> wrote:
> > Starting Oracle's VirtualBox has started to crash other apps, in
> > particular Thunderbird, Firefox, and Libreoffice; but not the
> > console. Firefox and Thunderbird just stop; Libr
On Tue, 2023-04-11 at 01:15 +, C. Linus Hicks wrote:
> Starting Oracle's VirtualBox has started to crash other apps, in
> particular Thunderbird, Firefox, and Libreoffice; but not the console.
> Firefox and Thunderbird just stop; Libreoffice attempts to restore
> files being worked on (but it f
ever I was working on, because crashes, power
outages, cats, and nearby twits with a bad sense of humour can so
easily wreck a lot of hard work in a fraction of a second.
These days, that's any time my train of thought has changed, or after
finishing a long paragraph. Yep, my trust in technol
On Mon, Apr 10, 2023 at 8:53 PM Jonathan Ryshpan wrote:
> Starting Oracle's VirtualBox has started to crash other apps, in particular
> Thunderbird, Firefox, and Libreoffice; but not the console. Firefox and
> Thunderbird just stop; Libreoffice attempts to restore files being worked on
> (but i
Subject: Running VirtualBox Crashes Other Apps
Starting Oracle's VirtualBox has started to crash other apps, in particular
Thunderbird, Firefox, and Libreoffice; but not the console. Firefox and
Thunderbird just stop; Libreoffice attempts to restore files being worked on
(but it fail
Starting Oracle's VirtualBox has started to crash other apps, in
particular Thunderbird, Firefox, and Libreoffice; but not the console.
Firefox and Thunderbird just stop; Libreoffice attempts to restore files
being worked on (but it failed to restore about 2 hours' worth of work).
Has anyone seen
On Sun, Jul 31, 2022 at 3:42 PM Michael Young wrote:
>
> On Sun, 31 Jul 2022, stan wrote:
>
> > On Sun, 31 Jul 2022 12:44:24 +0100
> > Andrew Wood wrote:
> >
> >> I have Fedora set up with Fedora 35 (workstation edition) using Gnome
> >> 41.6.
> >>
> >> I notice a (annoying!) bug which occurs whe
On Sun, 31 Jul 2022, stan wrote:
On Sun, 31 Jul 2022 12:44:24 +0100
Andrew Wood wrote:
I have Fedora set up with Fedora 35 (workstation edition) using Gnome
41.6.
I notice a (annoying!) bug which occurs when I try and cut and paste
from one window to another. What seems to happen is that the
On Sun, 31 Jul 2022 12:44:24 +0100
Andrew Wood wrote:
> I have Fedora set up with Fedora 35 (workstation edition) using Gnome
> 41.6.
>
> I notice a (annoying!) bug which occurs when I try and cut and paste
> from one window to another. What seems to happen is that the Gnome
> session closes
Hello,
I have Fedora set up with Fedora 35 (workstation edition) using Gnome 41.6.
I notice a (annoying!) bug which occurs when I try and cut and paste
from one window to another. What seems to happen is that the Gnome
session closes and it dumps me into terminal mode. If I type Ctrl-C then
G
> > serial option is possible; but I don't have any of that in
> > > > > any
> > > > > case.
> > > > >
> > > > > Anyway, reverting to 5.18.9 made this VM happy, and my VMs on
> > > > > another hardware, also run
; > Anyway, reverting to 5.18.9 made this VM happy, and my VMs on
> > > another hardware, also running the same kernel, are also fine.
> > > But, 5.18.11 gets reliably clusterfarked by qemu on at least on
> > > some hardware combinations. I wish I had more useful da
5.18.9 made this VM happy, and my VMs on
> > > another hardware, also running the same kernel, are also fine.
> > > But, 5.18.11 gets reliably clusterfarked by qemu on at least on
> > > some hardware combinations. I wish I had more useful data points,
> > > but I
.fc36.x86_64 on the host and on the guest (KVM). No crashes so
far.
However, sound is now broken, highly distorted, so maybe there is something bad
with this kernel?
You bay want to set rsyslog to log to the host, hoping to catch messages that
did not make it to
the guests fs. I have all my mach
On Jul 19, 2022, at 17:52, Sam Varshavchik wrote:
> No, there's nothing worthwhile to report. "Crashes with Qemu on some
> hardware" isn't a very useful bug report.
>
> Here's an example of a useful bug report: 2107827
>
> That one looks like like my
On 7/19/22 14:50, Sam Varshavchik wrote:
No, there's nothing worthwhile to report. "Crashes with Qemu on some
hardware" isn't a very useful bug report.
Post all you version numbers and post your XML file.
They should be able to reproduce for t
as a doornail.
Fortunately, it is not happening to me, but I
am still running 5.18.10-200.fc36.x86_64.
I am getting paranoid about upgrading my kernel.
Did you report it to Bugzilla?
No, there's nothing worthwhile to report. "Crashes with Qemu on some
hardware" isn't a very u
On 7/18/22 14:42, Sam Varshavchik wrote:
Am I the only one lucky enough to have kernel-5.18.11-200.fc36.x86_64
crash reliably, on particular hardware, after starting a VM in
virt-manager?
At least I think it's a crash. One second after a VM start it's
brick-city. Display frozen, no response f
e also fine. But, 5.18.11 gets reliably
clusterfarked by qemu on at least on some hardware combinations. I wish I had
more useful data points, but I've got nuthin' worth putting into Bugzilla.
Just a data point for you.
I run 5.18.11-200.fc36.x86_64 on the host and on the guest (KVM).
On Mon, 2022-07-18 at 17:42 -0400, Sam Varshavchik wrote:
> But, these days, no more RS-232 ports.
If it's not a laptop, there may still be one. But just on a header
that needs a flylead to an external connector.
--
uname -rsvp
Linux 3.10.0-1160.71.1.el7.x86_64 #1 SMP Tue Jun 28 15:37:28 UTC
Am I the only one lucky enough to have kernel-5.18.11-200.fc36.x86_64 crash
reliably, on particular hardware, after starting a VM in virt-manager?
At least I think it's a crash. One second after a VM start it's brick-city.
Display frozen, no response from the network. I've got nothing: after
On 5/27/22 06:03, stan via users wrote:
On Thu, 26 May 2022 14:29:31 -0700
Samuel Sieb wrote:
On 5/26/22 06:18, stan via users wrote:
So, the problem is in this function,
def wheelEvent(self, e):
h = self.horizontalScrollBar()
if not self.verticalScrollBar().isVisib
On Thu, 26 May 2022 14:29:31 -0700
Samuel Sieb wrote:
> On 5/26/22 06:18, stan via users wrote:
> > So, the problem is in this function,
> >
> > def wheelEvent(self, e):
> > h = self.horizontalScrollBar()
> > if not self.verticalScrollBar().isVisible() and
> > h.isVisible(
On 5/26/22 06:18, stan via users wrote:
So, the problem is in this function,
def wheelEvent(self, e):
h = self.horizontalScrollBar()
if not self.verticalScrollBar().isVisible() and h.isVisible():
numsteps = e.angleDelta().y() / 5
Python3 changed the default
I would hope since value/setValue are forward/reverse functions that they
are consistent (both int). But you never know.
On the other hand numsteps is not defined as int or a float, and I don't
know what that means in this language but int/5 can be whole number or a
float and I don't know what th
On Wed, 25 May 2022 20:20:37 -0500
"Steven P. Ulrick" wrote:
> Anyway, here is the output from the terminal:
>
> qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence:
> 20209, resource id: 14681426, major code: 40 (TranslateCoords), minor
> code: 0 qt.qpa.xcb: QXcbConnection: XCB error
On 5/25/22 16:29, Samuel Sieb wrote:
On 5/25/22 14:00, Steven P. Ulrick wrote:
but since puddletag crashes silently, and without invoking ABRT, I
have no idea if that report has anything to do with my issue.
Do you see any messages if you run it from a terminal?
Boy, I feel silly. Should
On 5/25/22 16:29, Samuel Sieb wrote:
On 5/25/22 14:00, Steven P. Ulrick wrote:
but since puddletag crashes silently, and without invoking ABRT, I
have no idea if that report has anything to do with my issue.
Do you see any messages if you run it from a terminal?
Boy, I feel silly. Should
e had puddletag crash on multiple occasions since I started running
> this version under Fedora 36. I have not been able to narrow down
> anything that I am doing when the crashes occur that would help narrow
> things down.
>
> Anybody else having issues like this? If not, any advice on
On 5/25/22 14:00, Steven P. Ulrick wrote:
but since puddletag crashes silently, and without invoking ABRT, I have
no idea if that report has anything to do with my issue.
Do you see any messages if you run it from a terminal?
___
users mailing list
. I have not been able to narrow down
anything that I am doing when the crashes occur that would help narrow
things down.
Anybody else having issues like this? If not, any advice on how to
debug/troubleshoot this issue?
There is one bug on the Fedora Bugzilla for puddletag:
https
On Wed, May 11, 2022 at 9:57 AM Lily White wrote:
>
> My guess is that the booting KDE requires running something in my profiles.
>
> Any explanations?
That's a reasonable explanation. The last time I tried setting my
shell to fish (which was a few releases ago now), I recall that it
broke some t
When I use fish as the default shell (via chsh). After a system reboot,
The KDE login screen would show up, but after logging in, it displays
only a blank screen.
I quit X to look at the logs and saw core dumps left and right.
Moreover, some commands like `reboot' and even `init' are not found
> Hi folks,
>
> I have a 43" Samsung Smart TV that I am using as a monitor with a ThinkPad
> P51,
> running Fedora 35 Workstation Edition. This laptop has a "NVIDIA Corporation
> GM206GLM
> [Quadro M2200 Mobile] / Mesa Intel® HD Graphics 630 (KBL GT2)" graphics
> subsystem. As
> far as I can ma
> Wow! That is awesome! Hopefully this will give me some pointers in the right
> direction (if
> it doesn't "just work"(tm)).
>
> From reading the script at /usr/bin/nvidia-sleep.sh, it seems that when it
> happens, I can
> try to change to a console VT, suspend and awaken the driver, then chang
I can attach the TV to my laptop long after boot, with no issues. However, once
this sleep behaviour has triggered, I can disconnect and reconnect as many
times as I like without resuscitating it.
___
users mailing list -- users@lists.fedoraproject.org
If I don't find a software solution, I'm going with a smart power switch that
will power the TV off whenever the laptop screen blanks. Taking no prisoners!
:-)
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users
That is excellent! Thanks for the pointer to this.
___
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-co
Wow! That is awesome! Hopefully this will give me some pointers in the right
direction (if it doesn't "just work"(tm)).
From reading the script at /usr/bin/nvidia-sleep.sh, it seems that when it
happens, I can try to change to a console VT, suspend and awaken the driver,
then change back, and h
On Tue, 2022-01-18 at 12:33 -0500, Jon LaBadie wrote:
> I have a similar problem with a Dell 35 inch monitor. If my desktop
> is idle long enough and I have no screensaver, the screen goes blank.
I, too, had similar issues. In my case, one of those multi-input
monitors. If it doesn't see an inp
On 1/18/22 5:40 PM, Sam Varshavchik wrote:
Rogan Dawes writes:
have to reboot to allow the laptop to detect the screen again. Xrandr
does not detect the display if run manually, and the Settings app
Displays page also doesn't show the TV.
This is a rather difficult thing to google, I have ha
On Tue, 2022-01-18 at 18:40 -0500, Sam Varshavchik wrote:
> Rogan Dawes writes:
>
> > have to reboot to allow the laptop to detect the screen again.
> > Xrandr does
> > not detect the display if run manually, and the Settings app
> > Displays page
> > also doesn't show the TV.
> >
> > This is
Rogan Dawes writes:
have to reboot to allow the laptop to detect the screen again. Xrandr does
not detect the display if run manually, and the Settings app Displays page
also doesn't show the TV.
This is a rather difficult thing to google, I have had zero results in my
searching.
This s
On Tue, Jan 18, 2022 at 04:02:41PM -, Rogan Dawes wrote:
I don't believe that this is a TV issue (other than its behaviour on input loss
triggering the resulting behaviour on the laptop). This is because if I reboot
the laptop, the TV is quite happy to recognise it again, while disconnectin
I don't believe that this is a TV issue (other than its behaviour on input loss
triggering the resulting behaviour on the laptop). This is because if I reboot
the laptop, the TV is quite happy to recognise it again, while disconnecting
and reconnecting the HDMI cable does not have the same effec
On Tue, 18 Jan 2022 14:55:11 -
"Rogan Dawes" wrote:
> I have a 43" Samsung Smart TV that I am using as a monitor with a
> ThinkPad P51, running Fedora 35 Workstation Edition. This laptop has
> a "NVIDIA Corporation GM206GLM [Quadro M2200 Mobile] / Mesa Intel® HD
> Graphics 630 (KBL GT2)" grap
Hi folks,
I have a 43" Samsung Smart TV that I am using as a monitor with a ThinkPad P51,
running Fedora 35 Workstation Edition. This laptop has a "NVIDIA Corporation
GM206GLM [Quadro M2200 Mobile] / Mesa Intel® HD Graphics 630 (KBL GT2)"
graphics subsystem. As far as I can make out, I am using
On Tue, 5 Oct 2021 at 06:53, lejeczek via users <
users@lists.fedoraproject.org> wrote:
> .. or is it Mesa and/or 'amdgpu'?
>
> Hi guys.
>
> Lately, I'd say for ~1 month, my Chrome has been really
> misbehaving even to the point when becomes unresponsive and
> I have to kill it.
> Chrome shows lo
.. or is it Mesa and/or 'amdgpu'?
Hi guys.
Lately, I'd say for ~1 month, my Chrome has been really
misbehaving even to the point when becomes unresponsive and
I have to kill it.
Chrome shows log full of things , with:
-> $ google-chrome --enable-logging --v=1
of which most worrying are:
...
[
On 11/07/2021 18:14, Ed Greshko wrote:
I don't use VM's with audio. I don't know if it is my slow HW or what, but I
never got it to work well with
pulseaudio and I've not even given pipewire a try with VM's. I had the same
disappointing issues using
VirtualBox as well.
FWIW, I just starte
On 11/07/2021 18:51, Ed Greshko wrote:
Oh, I can't seem to find xfwm4 display manager available for F34.
What is the outupt of
systemctl status display-manager
Never mind
If one logs in from multi-user mode and does startxfce you get that window
manager.
--
Remind me to ignore comment
kernels.
I've not seen any crashes on my VM. Host is F34 and multiple guests, including
F34 guests.
As a test, have you tried changing your guest video from QXL to Virtio?
Worth a try. I am now running with Virtio video. Audio sync is a bit out...
Interestingly: I tried to change back t
wrote:
On 10/07/2021 08:44, Eyal Lebedinsky wrote:
Recently I started having Xorg crash while using firefox.
This is f34 in a libvirt kvm, host (also f34) uses internal i915 video.
Kernel is 5.12.14-300.fc34.x86_64 but saw this with earlier 5.12.12/13 kernels.
I've not seen any crashes on
wrote:
Recently I started having Xorg crash while using firefox.
This is f34 in a libvirt kvm, host (also f34) uses internal i915 video.
Kernel is 5.12.14-300.fc34.x86_64 but saw this with earlier 5.12.12/13 kernels.
I've not seen any crashes on my VM. Host is F34 and multiple guests, incl
while using firefox.
This is f34 in a libvirt kvm, host (also f34) uses internal i915 video.
Kernel is 5.12.14-300.fc34.x86_64 but saw this with earlier 5.12.12/13 kernels.
I've not seen any crashes on my VM. Host is F34 and multiple guests, including
F34 guests.
As a test, have you
libvirt kvm, host (also f34) uses internal i915 video.
Kernel is 5.12.14-300.fc34.x86_64 but saw this with earlier 5.12.12/13 kernels.
I've not seen any crashes on my VM. Host is F34 and multiple guests, including
F34 guests.
As a test, have you tried changing your guest video from QXL to V
video.
Kernel is 5.12.14-300.fc34.x86_64 but saw this with earlier 5.12.12/13 kernels.
I've not seen any crashes on my VM. Host is F34 and multiple guests, including
F34 guests.
As a test, have you tried changing your guest video from QXL to Virtio?
Worth a try. I am now running with V
but saw this with earlier 5.12.12/13 kernels.
I've not seen any crashes on my VM. Host is F34 and multiple guests, including
F34 guests.
As a test, have you tried changing your guest video from QXL to Virtio?
Worth a try. I am now running with Virtio video. Audio sync is a bi
.
I've not seen any crashes on my VM. Host is F34 and multiple guests, including
F34 guests.
As a test, have you tried changing your guest video from QXL to Virtio?
Worth a try. I am now running with Virtio video. Audio sync is a bit out...
Interestingly: I tried to change back to QX
On 10/07/2021 08:44, Eyal Lebedinsky wrote:
Recently I started having Xorg crash while using firefox.
This is f34 in a libvirt kvm, host (also f34) uses internal i915 video.
Kernel is 5.12.14-300.fc34.x86_64 but saw this with earlier 5.12.12/13 kernels.
I've not seen any crashes on
Recently I started having Xorg crash while using firefox.
This is f34 in a libvirt kvm, host (also f34) uses internal i915 video.
Kernel is 5.12.14-300.fc34.x86_64 but saw this with earlier 5.12.12/13 kernels.
an example crash:
=
### note: many repeats of the following line preced
Fri, 19 Jun 2020 09:43:12 -0400
Justin Moore :
> It hasn't (yet) happened while I've been sitting at the computer so I
> can't tell if it's a clean shutdown or a hard reboot. Googling for
> "fedora" or "F32" and "random reboots" or "
ed on Sunday, so I went
from a 7-day work week to 6 days.
>
> It hasn't (yet) happened while I've been sitting at the computer so I
> can't tell if it's a clean shutdown or a hard reboot. Googling for "fedora"
> or "F32" and "random reboots&qu
error messages, no nothing. It's just fine until I'm
> staring at a reboot screen.
>
> It hasn't (yet) happened while I've been sitting at the computer so I
> can't tell if it's a clean shutdown or a hard reboot. Googling for "fedora"
> or "F32&q
t (yet) happened while I've been sitting at the computer so I can't
tell if it's a clean shutdown or a hard reboot. Googling for "fedora" or
"F32" and "random reboots" or "random crashes" doesn't bring up anything
particularly helpful.
1 - 100 of 707 matches
Mail list logo
