Re: Firefox crashes when started from the panel

[Alexey Rochev]

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 in file 
../../dbus/dbus-message.c lin>
Oct 07 23:38:00 localhost.localdomain plasmashell[3571]: This is normally a bug 
in some application using the D-Bus library.
Oct 07 23:38:00 localhost.localdomain plasmashell[3571]:   D-Bus not built with 
-rdynamic so unable to print a backtrace
Oct 07 23:38:00 localhost.localdomain plasmashell[3571]: KCrash: Application 
'plasmashell' crashing...
Oct 07 23:38:00 localhost.localdomain plasmashell[3571]: KCrash: Attempting to 
start /usr/libexec/drkonqi
Oct 07 23:38:01 localhost.localdomain systemd[1766]: 
plasma-plasmashell.service: Main process exited, code=exited, status=253/n/a
Oct 07 23:38:01 localhost.localdomain systemd[1766]: 
plasma-plasmashell.service: Failed with result 'exit-code'.
Oct 07 23:38:01 localhost.localdomain systemd[1766]: 
plasma-plasmashell.service: Consumed 3.136s CPU time.
Oct 07 23:38:01 localhost.localdomain systemd[1766]: 
plasma-plasmashell.service: Scheduled restart job, restart counter is at 5.
Oct 07 23:38:01 localhost.localdomain systemd[1766]: Stopped 
plasma-plasmashell.service - KDE Plasma Workspace.
Oct 07 23:38:01 localhost.localdomain systemd[1766]: 
plasma-plasmashell.service: Consumed 3.136s CPU time.
Oct 07 23:38:01 localhost.localdomain systemd[1766]: Starting 
plasma-plasmashell.service - KDE Plasma Workspace...
Oct 07 23:38:02 localhost.localdomain systemd[1766]: Started 
plasma-plasmashell.service - KDE Plasma Workspace.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Firefox crashes when started from the panel

[Jonathan Ryshpan]

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 what happens when Firefox is
invoked. There is nothing promising in the Firefox box on the panel and
the only promising entry in the Firefox entry in the Application
Launcher is in the drop down box in 
   Application Launcher->Internet->Firefox->(Right Click)
This is "Open the Profile Manager", so I invoked this. Result another
similar crash. A log is attached; perhaps someone will find it useful.

It seems odd to me that there is no easy way to see what is supposed to
happen when a desktop item is invoked in a particular way. I would think
an entry for a Right-Click on any such item should be something like
"System Action" or whatever.


-- 
Sincerely Jonathan Ryshpan 

 There are 2 rules to success in life:
 1. Don't tell people everything you know.
 -- Dean Brown
Oct 07 09:26:00 amito plasmashell[20610]: dbus[20610]: arguments to 
dbus_message_new_method_call() were incorrect, assertion "destination == NULL 
|| _dbus_check_is_valid_bus_name (destination)" failed in file 
../../dbus/dbus-message.c line 1375.
Oct 07 09:26:00 amito plasmashell[20610]: This is normally a bug in some 
application using the D-Bus library.
Oct 07 09:26:00 amito plasmashell[20610]:   D-Bus not built with -rdynamic so 
unable to print a backtrace
Oct 07 09:26:00 amito plasmashell[20610]: KCrash: Application 'plasmashell' 
crashing...
Oct 07 09:26:00 amito plasmashell[20610]: KCrash: Attempting to start 
/usr/libexec/drkonqi
Oct 07 09:26:01 amito systemd[1455]: plasma-plasmashell.service: Main process 
exited, code=exited, status=253/n/a
Oct 07 09:26:01 amito systemd[1455]: plasma-plasmashell.service: Failed with 
result 'exit-code'.
Oct 07 09:26:01 amito systemd[1455]: plasma-plasmashell.service: Consumed 
10.000s CPU time.
Oct 07 09:26:02 amito systemd[1455]: plasma-plasmashell.service: Scheduled 
restart job, restart counter is at 9.
Oct 07 09:26:02 amito systemd[1455]: Stopped plasma-plasmashell.service - KDE 
Plasma Workspace.
Oct 07 09:26:02 amito systemd[1455]: plasma-plasmashell.service: Consumed 
10.000s CPU time.
Oct 07 09:26:02 amito systemd[1455]: Starting plasma-plasmashell.service - KDE 
Plasma Workspace...
Oct 07 09:26:02 amito systemd[1455]: Started plasma-plasmashell.service - KDE 
Plasma Workspace.
Oct 07 09:26:02 amito plasmashell[20732]: kf.plasma.quick: Applet preload 
policy set to 1
Oct 07 09:26:02 amito systemd[1455]: Starting plasma-ksystemstats.service - 
Track hardware statistics...
Oct 07 09:26:02 amito audit: BPF prog-id=130 op=LOAD
Oct 07 09:26:02 amito audit: BPF prog-id=131 op=LOAD
Oct 07 09:26:02 amito audit: BPF prog-id=132 op=LOAD
Oct 07 09:26:02 amito systemd[1]: Starting systemd-hostnamed.service - Hostname 
Service...
Oct 07 09:26:03 amito NetworkManager[1257]:   [1696695963.0090] audit: 
op="statistics" interface="enp3s0" ifindex=2 args="500" pid=20744 uid=1000 
result="success"
Oct 07 09:26:03 amito ksystemstats[20744]: kf.i18n: KLocalizedString: Using an 
empty domain, fix the code. msgid: "Temperature %1" msgid_plural: "" msgctxt: 
"@title %1 is a number"
Oct 07 09:26:03 amito ksystemstats[20744]: kf.i18n: KLocalizedString: Using an 
empty domain, fix the code. msgid: "Temperature %1" msgid_plural: "" msgctxt: 
"@title %1 is a number"
Oct 07 09:26:03 amito systemd[1455]: Started plasma-ksystemstats.service - 
Track hardware statistics.
Oct 07 09:26:03 amito systemd[1]: Started systemd-hostnamed.service - Hostname 
Service.
Oct 07 09:26:03 amito audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed 
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? 
res=success'
Oct 07 09:26:03 amito plasmashell[20732]: 
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:265:13:
 QML SelectableLabel: Binding loop detected for property "implicitWidth"
Oct 07 09:26:04 amito systemd[1455]: Started 
dbus-:1.2-org.kde.KSplash@8.service.
Oct 07 09:26:04 amito kioslave5[20766]: QObject::connect: No such slot 
DesktopProtocol::_k_slotRedirection(KIO::Job *, QUrl)
Oct 07 09:26:04 amito plasmashell[20732]: 
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:43:5:
 QML MouseArea: Cannot anchor to an item that isn't a parent or sibling.
Oct 07 09:26:05 amito plasmashell[20732]: Trying to use rootObject before 
initialization is completed, whilst using setInitializationDelayed. Forcing 
completion
Oct 07 09:26:05 amito plasmashell[20732]: 
file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:43:5:
 QML MouseArea: Cannot anchor to an item that isn't a parent or sibling.
Oct 07 09:26:05 amito plasmashell[20732]: 

Re: Firefox crashes when started from the panel

[Alex Gurenko via users]

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.

[0] https://bugs.kde.org/show_bug.cgi?id=475266
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2242454
[2] 
https://src.fedoraproject.org/rpms/firefox/c/85de885472621621af497b204a2f45f7122e8a23?branch=rawhide

---
Best regards, Alex


--- Original Message ---
On Saturday, October 7th, 2023 at 17:41, stan via users 
 wrote:


> On Sat, 07 Oct 2023 03:44:56 -0700
> Jonathan Ryshpan jonr...@pacbell.net 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 application launcher. I have attached a fragment
> > of the system log showing activity immediately before and after
> > Firefox was started (Journal.txt)
> > 
> > Any ideas how to investigate.
> > 
> > Application info:
> > firefox-118.0.1-4.fc38.x86_64
> > System info:
> > Operating System: Fedora Linux 38
> > KDE Plasma Version: 5.27.8
> > KDE Frameworks Version: 5.110.0
> > Qt Version: 5.15.10
> > Kernel Version: 6.5.5-200.fc38.x86_64 (64-bit)
> > Graphics Platform: X11
> > Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
> > Memory: 15.5 GiB of RAM
> > Graphics Processor: Mesa Intel® HD Graphics 4600
> > Manufacturer: ASUS
> 
> 
> It sounds like there isn't a problem with firefox, per se. If it
> starts fine with two out of three methods, it is the invocation that is
> causing the problem. I'm not sure what starting from the panel is, but
> can you get to the actual command being run when you do that? Then
> compare it to what you run from the console or application launcher.
> Can you alter the panel version to run with firefox --safe-mode, so
> that it starts without any add-ons. Maybe try with a different user;
> create a new user [1] and start firefox from the panel with that new
> user and a pristine /home directory. Success with the new user will
> indicate that there is something in your /home directory
> configuration that is causing the problem. Failure, a KDE panel
> problem, and probably time for a bugzilla.
> 
> 1. See man useradd for how to add a new user. You should be able to
> switch to that new user from the greeter.
> ___
> 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: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Firefox crashes when started from the panel

[stan via users]

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 application launcher. I have attached a fragment
> of the system log showing activity immediately before and after
> Firefox was started (Journal.txt)
> 
> Any ideas how to investigate.
> 
> Application info:
>firefox-118.0.1-4.fc38.x86_64
> System info:
>Operating System: Fedora Linux 38
>KDE Plasma Version: 5.27.8
>KDE Frameworks Version: 5.110.0
>Qt Version: 5.15.10
>Kernel Version: 6.5.5-200.fc38.x86_64 (64-bit)
>Graphics Platform: X11
>Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
>Memory: 15.5 GiB of RAM
>Graphics Processor: Mesa Intel® HD Graphics 4600
>Manufacturer: ASUS

It sounds like there isn't a problem with firefox, per se.  If it
starts fine with two out of three methods, it is the invocation that is
causing the problem.  I'm not sure what starting from the panel is, but
can you get to the actual command being run when you do that?  Then
compare it to what you run from the console or application launcher.
Can you alter the panel version to run with firefox --safe-mode, so
that it starts without any add-ons.  Maybe try with a different user;
create a new user [1] and start firefox from the panel with that new
user and a pristine /home directory.  Success with the new user will
indicate that there is something in your /home directory
configuration that is causing the problem.  Failure, a KDE panel
problem, and probably time for a bugzilla.

1. See  man useradd  for how to add a new user.  You should be able to
switch to that new user from the greeter.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Firefox crashes when started from the panel

[Jonathan Ryshpan]

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 activity immediately before and after Firefox was started
(Journal.txt)

Any ideas how to investigate.

Application info:
   firefox-118.0.1-4.fc38.x86_64
System info:
   Operating System: Fedora Linux 38
   KDE Plasma Version: 5.27.8
   KDE Frameworks Version: 5.110.0
   Qt Version: 5.15.10
   Kernel Version: 6.5.5-200.fc38.x86_64 (64-bit)
   Graphics Platform: X11
   Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
   Memory: 15.5 GiB of RAM
   Graphics Processor: Mesa Intel® HD Graphics 4600
   Manufacturer: ASUS

-- 
Sincerely Jonathan Ryshpan 

 Those who have put out the eyes of the people
 reproach them for their blindness. -- Milton
[jonrysh@amito ~]$ journalctl --follow
Oct 07 03:27:32 amito kinfocenter[11042]: 
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML 
MouseArea: Binding loop detected for property "width"
Oct 07 03:27:32 amito kinfocenter[11042]: 
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML 
MouseArea: Binding loop detected for property "width"
Oct 07 03:27:33 amito kinfocenter[11042]: QQmlEngine::setContextForObject(): 
Object already has a QQmlContext
Oct 07 03:27:33 amito kinfocenter[11042]: 
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML 
MouseArea: Binding loop detected for property "implicitHeight"
Oct 07 03:27:33 amito kinfocenter[11042]: 
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML 
MouseArea: Binding loop detected for property "implicitHeight"
Oct 07 03:27:33 amito systemd[1]: Created slice 
system-dbus\x2d:1.13\x2dorg.kde.kinfocenter.dmidecode.slice - Slice 
/system/dbus-:1.13-org.kde.kinfocenter.dmidecode.
Oct 07 03:27:33 amito audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=dbus-:1.13-org.kde.kinfocenter.dmidecode@0 comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 07 03:27:33 amito systemd[1]: Started 
dbus-:1.13-org.kde.kinfocenter.dmidecode@0.service.
Oct 07 03:27:43 amito systemd[1]: 
dbus-:1.13-org.kde.kinfocenter.dmidecode@0.service: Deactivated successfully.
Oct 07 03:27:43 amito audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=dbus-:1.13-org.kde.kinfocenter.dmidecode@0 comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 07 03:30:57 amito kwin_x11[1910]: kwin_core: Failed to focus 0x6e000f3 
(error 8)
Oct 07 03:31:02 amito systemd[1455]: 
app-org.kde.kinfocenter-ab348e03a6664f7495f493b025236f93.scope: Consumed 1.450s 
CPU time.
Oct 07 03:31:04 amito systemd[1455]: 
app-firefox-3fe45d1fdc6144c4b938ab0075ba0c9e.scope: Consumed 28min 48.601s CPU 
time.
Oct 07 03:31:04 amito systemd[1455]: Stopping 
cgroupify@app-firefox-3fe45d1fdc6144c4b938ab0075ba0c9e.scope.service...
Oct 07 03:31:04 amito systemd[1455]: Stopped 
cgroupify@app-firefox-3fe45d1fdc6144c4b938ab0075ba0c9e.scope.service.
Oct 07 03:31:04 amito systemd[1455]: 
cgroupify@app-firefox-3fe45d1fdc6144c4b938ab0075ba0c9e.scope.service: Consumed 
1.357s CPU time.
Oct 07 03:31:24 amito plasmashell[8515]: dbus[8515]: arguments to 
dbus_message_new_method_call() were incorrect, assertion "destination == NULL 
|| _dbus_check_is_valid_bus_name (destination)" failed in file 
../../dbus/dbus-message.c line 1375.
Oct 07 03:31:24 amito plasmashell[8515]: This is normally a bug in some 
application using the D-Bus library.
Oct 07 03:31:24 amito plasmashell[8515]:   D-Bus not built with -rdynamic so 
unable to print a backtrace
Oct 07 03:31:24 amito plasmashell[8515]: KCrash: Application 'plasmashell' 
crashing...
Oct 07 03:31:24 amito plasmashell[8515]: KCrash: Attempting to start 
/usr/libexec/drkonqi
Oct 07 03:31:24 amito systemd[1455]: plasma-ksystemstats.service: Consumed 
3.307s CPU time.
Oct 07 03:31:25 amito systemd[1455]: plasma-plasmashell.service: Main process 
exited, code=exited, status=253/n/a
Oct 07 03:31:25 amito systemd[1455]: plasma-plasmashell.service: Failed with 
result 'exit-code'.
Oct 07 03:31:25 amito systemd[1455]: plasma-plasmashell.service: Consumed 
50.844s CPU time.
Oct 07 03:31:26 amito systemd[1455]: plasma-plasmashell.service: Scheduled 
restart job, restart counter is at 7.
Oct 07 03:31:26 amito systemd[1455]: Stopped plasma-plasmashell.service - KDE 
Plasma Workspace.
Oct 07 03:31:26 amito systemd[1455]: plasma-plasmashell.service: Consumed 
50.844s CPU time.
Oct 07 03:31:26 amito systemd[1455]: Starting plasma-plasmashell.service - KDE 
Plasma Workspace...
Oct 07 03:31:26 amito systemd[1455]: Started plasma-plasmashell.service - KDE 
Plasma Workspace.
Oct 07 03:31:26 amito 

Re: Running VirtualBox Crashes Other Apps

[stan via users]

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 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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[stan via users]

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 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 the
> > system-oomd-defaults package. That way, systemd-oomd.service
> > continues to run, but it's not monitoring anything (as verified
> > with oomctl).  
> 
> So, I have it masked, and this shows from systemctl,
> systemd-oomd.service maskedinactive dead
>   systemd-oomd.service However, I don't have the
> systemd-oomd-defaults package installed so I can't say whether that
> would cause it to start while being masked or not.  Perhaps I will
> give that a try at some point.  If it is being started despite being
> masked, that is definitely a bug.  Masking is supposed to be
> inviolable.  Since systemd-oomd is part of the main systemd package,
> that would be the package to file the bug against.  It is possible
> that it is not checking the service status if the
> systemd-oomd-defaults package is installed.

I installed systemd-oomd-defaults, rebooted, and the service remained
masked.  I checked with ps and top, and it is not running.  On F37,
fully up to date.

Name: systemd
Version : 251.14
Release : 2.fc37
Architecture: x86_64
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[Barry]

> 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 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 the system-oomd-defaults
>> package. That way, systemd-oomd.service continues to run, but it's
>> not monitoring anything (as verified with oomctl).
> 
> So, I have it masked, and this shows from systemctl,
> systemd-oomd.service maskedinactive dead
> systemd-oomd.service
> However, I don't have the systemd-oomd-defaults package installed so I
> can't say whether that would cause it to start while being masked or
> not.  Perhaps I will give that a try at some point.  If it is being
> started despite being masked, that is definitely a bug.  Masking is
> supposed to be inviolable.  Since systemd-oomd is part of the main
> systemd package, that would be the package to file the bug against.  It
> is possible that it is not checking the service status if the
> systemd-oomd-defaults package is installed.

Its not a check as such.
Masking means the service is defined as /dev/null, hard to start when there is 
nothing defined.

Barry


> ___
> 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: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[stan via users]

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 reinstalled. (To check this, try
> reinstalling it.) It's better to just remove the system-oomd-defaults
> package. That way, systemd-oomd.service continues to run, but it's
> not monitoring anything (as verified with oomctl).

So, I have it masked, and this shows from systemctl,
systemd-oomd.service maskedinactive dead
systemd-oomd.service
However, I don't have the systemd-oomd-defaults package installed so I
can't say whether that would cause it to start while being masked or
not.  Perhaps I will give that a try at some point.  If it is being
started despite being masked, that is definitely a bug.  Masking is
supposed to be inviolable.  Since systemd-oomd is part of the main
systemd package, that would be the package to file the bug against.  It
is possible that it is not checking the service status if the
systemd-oomd-defaults package is installed.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[Jeffrey Walton]

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 fixed so I'm not disabling it anymore.

As far as I know, a masked service cannot be started. (A disabled
service can be manually started).

See https://www.techrepublic.com/article/masked-services-linux-how-manage/ .

Jeff
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[Andre Robatino]

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.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[Jeffrey Walton]

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 same time).

Fedora's bug reporter is at https://bugzilla.redhat.com/ .

Jeff
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[Andre Robatino]

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 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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[Samuel Sieb]

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 should 
not be touched by any install or update.

___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[Andre Robatino]

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 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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[Andre Robatino]

> 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 the system-oomd-defaults package. 
That way, systemd-oomd.service continues to run, but it's not monitoring 
anything (as verified with oomctl).
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[Patrick O'Callaghan]

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
> > > >  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 failed to restore
> > > > > about
> > > > > 2 hours' worth of work).  
> > > > 
> > > > Guessing  - OOMD is killing things to free up RAM?  
> > > 
> > > Certainly correct. In future I'll have to take corrective action
> > > --
> > > maybe buy more RAM.  From the system log:
> > 
> > I masked systemd-oomd.service because I have real swap, and when
> > something starts using too much memory, it starts using that swap
> > and
> > I notice the slowdown in the system.  Then I can do something about
> > it.
> 
> If I understand the situation correctly (which I may not} in my
> system
> this happens: All real and virtual memory is allocated (The system
> has
> 16 Gb RAM + 32 Gb Swap.), but more memory is needed, at which point
> oomd
> starts killing processes. The system often becomes quite slow, with a
> lot of disk activity, before processes start to die.
> 
> Cures might be more RAM, more swap, or cutting the system load. More
> swap is probably a bad idea, since the system already appears to be
> running slow on account of a lot of swapping.

You might try monitoring usage via oomctl to see what is actually
happening.

poc
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[Doug Herr]

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 memory is assigned to the VB clients that are 
running.




___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[Jonathan Ryshpan]

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 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).  
> > > 
> > > Guessing  - OOMD is killing things to free up RAM?  
> > 
> > Certainly correct. In future I'll have to take corrective action --
> > maybe buy more RAM.  From the system log:
> 
> I masked systemd-oomd.service because I have real swap, and when
> something starts using too much memory, it starts using that swap and
> I notice the slowdown in the system.  Then I can do something about
> it.

If I understand the situation correctly (which I may not} in my system
this happens: All real and virtual memory is allocated (The system has
16 Gb RAM + 32 Gb Swap.), but more memory is needed, at which point oomd
starts killing processes. The system often becomes quite slow, with a
lot of disk activity, before processes start to die.

Cures might be more RAM, more swap, or cutting the system load. More
swap is probably a bad idea, since the system already appears to be
running slow on account of a lot of swapping.


-- 
Sincerely Jonathan Ryshpan 

Some people want something for nothing, however much it costs.
 -- David Ryshpan
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[Tom Horsley]

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 machine, and the test was
using a address trap (where the debug registers can be set to
generate an interrupt when you reference a specific memory location),
then sometimes programs running on the host machine would get the
address trap if they referenced that memory address :-). After much
head scratching I managed to produce a test case that could trigger
the bug nearly instantly and reported the bug, which was actually
fixed.

I suppose the virtual box kernel code might have introduced such
a bug, but that's probably unlikely.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[stan via users]

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 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).  
> > 
> > Guessing  - OOMD is killing things to free up RAM?  
> 
> Certainly correct. In future I'll have to take corrective action --
> maybe buy more RAM.  From the system log:

I masked systemd-oomd.service because I have real swap, and when
something starts using too much memory, it starts using that swap and I
notice the slowdown in the system.  Then I can do something about it.

Might or might not work for your use case.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[Jonathan Ryshpan]

On Tue, 2023-04-11 at 15:46 +0930, Tim via users wrote:
> On Mon, 2023-04-10 at 17:52 -0700, Jonathan Ryshpan wrote:
> > Libreoffice attempts to restore files being worked on (but it failed
> > to restore about 2 hours' worth of work).
> 
> Some thirty-plus years ago I 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's any time my train of thought has changed, or after
> finishing a long paragraph.  Yep, my trust in technology is that poor,
> and that includes any faith in auto-recovery.

Always good advice. But I am a luck fellow. Linux has been good to me;
over 30 years of work I have lost an appreciable amount of work only
this once.


-- 
Sincerely Jonathan Ryshpan 

 Trust everyone -- But cut the cards.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[Jonathan Ryshpan]

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; Libreoffice attempts to
> > restore files being worked on (but it failed to restore about 2
> > hours' worth of work).
> 
> Guessing  - OOMD is killing things to free up RAM?

Certainly correct. In future I'll have to take corrective action --
maybe buy more RAM.  From the system log:

Apr 10 13:35:44 amito systemd-oomd[948]: Killed
/user.slice/user-1000.slice/user@1000.service/app.slice/app-
libreoffice\x2dcalc-d5d271b128784076915db377a70340bc.scope due 
to memory pressure for /user.slice/user-1000.slice/user@1000.service
being 59.60% > 50.00% for > 20s with reclaim activity
Apr 10 13:35:44 amito systemd[1440]: app-libreoffice\x2dcalc-
d5d271b128784076915db377a70340bc.scope: systemd-oomd killed 5
process(es) in this unit.
Apr 10 13:35:44 amito systemd[1440]: app-libreoffice\x2dcalc-
d5d271b128784076915db377a70340bc.scope: Consumed 4min 26.480s CPU time.
Apr 10 13:35:59 amito systemd-oomd[948]: Considered 113 cgroups for
killing, top candidates were:
Apr 10 13:35:59 amito systemd-oomd[948]: Path:
/user.slice/user-1000.slice/user@1000.service/app.slice/app-
mozilla\x2dthunderbird-c2bba51b2b8346e1bbe7647080a15d7b.
scope
Apr 10 13:35:59 amito systemd-oomd[948]: Memory Pressure
Limit: 0.00%
Apr 10 13:35:59 amito systemd-oomd[948]: Pressure:
Avg10: 0.45 Avg60: 2.44 Avg300: 1.02 Total: 1min 35s
Apr 10 13:35:59 amito systemd-oomd[948]: Current Memory
Usage: 163.0M
Apr 10 13:35:59 amito systemd-oomd[948]: Memory Min: 0B
Apr 10 13:35:59 amito systemd-oomd[948]: Memory Low: 0B
Apr 10 13:35:59 amito systemd-oomd[948]: Pgscan: 577674
Apr 10 13:35:59 amito systemd-oomd[948]: Last Pgscan:
577354


-- 
Sincerely Jonathan Ryshpan 

 Those who love truth are not too sure 
 they are right
 -- Learned Hand
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[Jonathan Ryshpan]

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 failed to restore about 2 hours' worth
> of work).
>  
> Has anyone seen anything like this? Any ideas on how to prevent it?
> Any experience with other virtual environments?
>  
> System info:
>Operating System: Fedora Linux 37
>KDE Plasma Version: 5.27.4
>KDE Frameworks Version: 5.104.0
>Qt Version: 5.15.8
>Kernel Version: 6.2.9-200.fc37.x86_64 (64-bit)
>Graphics Platform: X11
>Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
>Memory: 15.5 GiB of RAM
>Graphics Processor: Mesa Intel® HD Graphics 4600
>Manufacturer: ASUS
>Product Name: All Series 
>  
> You didn't report what version of VirtualBox you are running.

Very good point:
$ rpm -q VirtualBox
VirtualBox-7.0.6-1.fc37.x86_64


-- 
Sincerely Jonathan Ryshpan 

 In the history of the world, no one has ever 
 washed a rented car. 
 -- Lawrence Summers
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[Tim via users]

On Mon, 2023-04-10 at 17:52 -0700, Jonathan Ryshpan wrote:
> Libreoffice attempts to restore files being worked on (but it failed
> to restore about 2 hours' worth of work).

Some thirty-plus years ago I 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's any time my train of thought has changed, or after
finishing a long paragraph.  Yep, my trust in technology is that poor,
and that includes any faith in auto-recovery.
 
-- 
 
uname -rsvp
Linux 3.10.0-1160.88.1.el7.x86_64 #1 SMP Tue Mar 7 15:41:52 UTC 2023 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[Go Canes]

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 it failed to restore about 2 hours' worth of work).

Guessing  - OOMD is killing things to free up RAM?
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Running VirtualBox Crashes Other Apps

[C. Linus Hicks]

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 failed to restore about 2 hours' worth of work).
 
Has anyone seen anything like this? Any ideas on how to prevent it? Any 
experience with other virtual environments?
 
System info:
Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.9-200.fc37.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8  Intel Core i7-4790K CPU @ 4.00GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel HD Graphics 4600
Manufacturer: ASUS
Product Name: All Series
 


You didn't report what version of VirtualBox you are running.

___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Running VirtualBox Crashes Other Apps

[Jonathan Ryshpan]

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 anything like this? Any ideas on how to prevent it? Any
experience with other virtual environments?

System info:
   Operating System: Fedora Linux 37
   KDE Plasma Version: 5.27.4
   KDE Frameworks Version: 5.104.0
   Qt Version: 5.15.8
   Kernel Version: 6.2.9-200.fc37.x86_64 (64-bit)
   Graphics Platform: X11
   Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
   Memory: 15.5 GiB of RAM
   Graphics Processor: Mesa Intel® HD Graphics 4600
   Manufacturer: ASUS
   Product Name: All Series

-- 
Sincerely Jonathan Ryshpan 

 They know that it is human nature to take up
 causes whereby a man may oppress his neighbor,
 no matter how unjustly. ... Hence they have had
 no trouble in finding men who would preach the
 damnability and heresy of the new doctrine from
 the very pulpit... -- Galileo Galilei, 1615
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Fedora 35 crashes with all updates applied. How do I submit a bug report re. crashing in Gnome but probably Kernel bug.

[Grumpey]

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 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 Gnome restarts and a new user session is presented. Prior to my
> >> most recent update, this bug seemed even worse in its frequency and
> >> scope. But still, I am now continuing to potentially losing work (and
> >> basic functionality).
> >>
> >> This might be a Kernel error using shared memory between threads or
> >> processes but I really don't know. It's a guess. Anyhow, what do I
> >> need to do, to file a bug and what memory or process dumps/logs/stack
> >> traces are needed to help the developers. ie what do I type where!
> >
> > I suggest that you open a bug, describing your experiences.  The
> > maintainers of Gnome will have a much better idea of what they need to
> > diagnose or fix the bug.  If you search for bugs, you might even find
> > that this is already known (there is an already opened bugzilla), and
> > there might be a workaround.
>
> I have been seeing this as well. It seems a lot more stable after I
> downgraded gnome-shell.
>
> Michael Young

Can you check that you have,
https://bodhi.fedoraproject.org/updates/FEDORA-2022-4bfe306a05l

If you have the update and it is still occurring please chime in here,
https://bugzilla.redhat.com/show_bug.cgi?id=2110041

Joe
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 crashes with all updates applied. How do I submit a bug report re. crashing in Gnome but probably Kernel bug.

[Michael Young]

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 Gnome
session closes and it dumps me into terminal mode. If I type Ctrl-C
then Gnome restarts and a new user session is presented. Prior to my
most recent update, this bug seemed even worse in its frequency and
scope. But still, I am now continuing to potentially losing work (and
basic functionality).

This might be a Kernel error using shared memory between threads or
processes but I really don't know. It's a guess. Anyhow, what do I
need to do, to file a bug and what memory or process dumps/logs/stack
traces are needed to help the developers. ie what do I type where!


I suggest that you open a bug, describing your experiences.  The
maintainers of Gnome will have a much better idea of what they need to
diagnose or fix the bug.  If you search for bugs, you might even find
that this is already known (there is an already opened bugzilla), and
there might be a workaround.


I have been seeing this as well. It seems a lot more stable after I 
downgraded gnome-shell.


Michael Young
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 crashes with all updates applied. How do I submit a bug report re. crashing in Gnome but probably Kernel bug.

[stan via users]

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 and it dumps me into terminal mode. If I type Ctrl-C
> then Gnome restarts and a new user session is presented. Prior to my
> most recent update, this bug seemed even worse in its frequency and
> scope. But still, I am now continuing to potentially losing work (and
> basic functionality).
> 
> This might be a Kernel error using shared memory between threads or 
> processes but I really don't know. It's a guess. Anyhow, what do I
> need to do, to file a bug and what memory or process dumps/logs/stack
> traces are needed to help the developers. ie what do I type where!

I suggest that you open a bug, describing your experiences.  The
maintainers of Gnome will have a much better idea of what they need to
diagnose or fix the bug.  If you search for bugs, you might even find
that this is already known (there is an already opened bugzilla), and
there might be a workaround.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora 35 crashes with all updates applied. How do I submit a bug report re. crashing in Gnome but probably Kernel bug.

[Andrew Wood]

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 
Gnome restarts and a new user session is presented. Prior to my most 
recent update, this bug seemed even worse in its frequency and scope. 
But still, I am now continuing to potentially losing work (and basic 
functionality).


This might be a Kernel error using shared memory between threads or 
processes but I really don't know. It's a guess. Anyhow, what do I need 
to do, to file a bug and what memory or process dumps/logs/stack traces  
are needed to help the developers. ie what do I type where!


Thank-you.

Andrew, Oxford(UK)

___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: qemu crashes kernel-5.18.11-200.fc36.x86_64

[Patrick O'Callaghan]

On Wed, 2022-07-20 at 06:50 -0400, Sam Varshavchik wrote:
> Patrick O'Callaghan writes:
> 
> > On Wed, 2022-07-20 at 13:20 +1000, Eyal Lebedinsky wrote:
> > > 
> > > 
> > > On 19/07/2022 14.39, Eyal Lebedinsky wrote:
> > > > 
> > > > On 19/07/2022 07.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 from the network.
> > > > > I've
> > > > > got nothing: after a reboot there's nothing in journalctl -r
> > > > > -b -
> > > > > 1. This brings up fond memories -- ages ago I had a null
> > > > > modem
> > > > > adapter hooked up to a serial port, the kernel configured for
> > > > > a
> > > > > serial console, thusly I was able to capture OOPSes over the
> > > > > serial console, in situations like these.
> > > > > 
> > > > > But, these days, no more RS-232 ports. I dimly recall that a
> > > > > USB-
> > > > > 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 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'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).
> > > > 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 machines log to my server (which
> > > > is
> > > > the host too).
> > > > 
> > > > A special, long incantation is appended to /etc/rsyslog.conf
> > > > (on
> > > > the guest).
> > > > On the host I Provided TCP/UDP syslog reception in the same
> > > > conf
> > > > file.
> > > 
> > > I now changed the guest machine from "sound ac97" to "sound ich6"
> > > and
> > > sound now works OK.
> > > The old setup was OK for a very long time.
> > > 
> > > It is a worry when a stable setup stops working, so the OP may
> > > consider trying different
> > > guest settings.
> > 
> > IIRC ich6 has been preferred to ac97 for quite a long time now.
> 
> I had mine set to use ich9 and ich6 made no difference to me, it's
> still  
> scratchy. It looks to me more fundamental than emulated audio, the
> entire VM  
> became sluggish with the 5.18 kernel.

Regarding sound, there are some suggestions here:

https://juho.tykkala.fi/Pulseaudio-and-latency#positive-effect-on-latency

However I haven't tried the latest kernel myself so can't really
comment.

poc
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: qemu crashes kernel-5.18.11-200.fc36.x86_64

[Sam Varshavchik]

Patrick O'Callaghan writes:


On Wed, 2022-07-20 at 13:20 +1000, Eyal Lebedinsky wrote:
>
>
> On 19/07/2022 14.39, Eyal Lebedinsky wrote:
> >
> > On 19/07/2022 07.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 from the network. I've
> > > got nothing: after a reboot there's nothing in journalctl -r -b -
> > > 1. This brings up fond memories -- ages ago I had a null modem
> > > adapter hooked up to a serial port, the kernel configured for a
> > > serial console, thusly I was able to capture OOPSes over the
> > > serial console, in situations like these.
> > >
> > > But, these days, no more RS-232 ports. I dimly recall that a USB-
> > > 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 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'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).
> > 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 machines log to my server (which is
> > the host too).
> >
> > A special, long incantation is appended to /etc/rsyslog.conf (on
> > the guest).
> > On the host I Provided TCP/UDP syslog reception in the same conf
> > file.
>
> I now changed the guest machine from "sound ac97" to "sound ich6" and
> sound now works OK.
> The old setup was OK for a very long time.
>
> It is a worry when a stable setup stops working, so the OP may
> consider trying different
> guest settings.

IIRC ich6 has been preferred to ac97 for quite a long time now.


I had mine set to use ich9 and ich6 made no difference to me, it's still  
scratchy. It looks to me more fundamental than emulated audio, the entire VM  
became sluggish with the 5.18 kernel.




pgpmSXU1cYElm.pgp
Description: PGP signature
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: qemu crashes kernel-5.18.11-200.fc36.x86_64

[Patrick O'Callaghan]

On Wed, 2022-07-20 at 13:20 +1000, Eyal Lebedinsky wrote:
> 
> 
> On 19/07/2022 14.39, Eyal Lebedinsky wrote:
> > 
> > On 19/07/2022 07.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 from the network. I've
> > > got nothing: after a reboot there's nothing in journalctl -r -b -
> > > 1. This brings up fond memories -- ages ago I had a null modem
> > > adapter hooked up to a serial port, the kernel configured for a
> > > serial console, thusly I was able to capture OOPSes over the
> > > serial console, in situations like these.
> > > 
> > > But, these days, no more RS-232 ports. I dimly recall that a USB-
> > > 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 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'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).
> > 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 machines log to my server (which is
> > the host too).
> > 
> > A special, long incantation is appended to /etc/rsyslog.conf (on
> > the guest).
> > On the host I Provided TCP/UDP syslog reception in the same conf
> > file.
> 
> I now changed the guest machine from "sound ac97" to "sound ich6" and
> sound now works OK.
> The old setup was OK for a very long time.
> 
> It is a worry when a stable setup stops working, so the OP may
> consider trying different
> guest settings.

IIRC ich6 has been preferred to ac97 for quite a long time now.

You may also want to check that you're using the i440FX chipset rather
than the older one (the name of which escapes me).

poc
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: qemu crashes kernel-5.18.11-200.fc36.x86_64

[Eyal Lebedinsky]

On 19/07/2022 14.39, Eyal Lebedinsky wrote:


On 19/07/2022 07.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 from the network. I've got nothing: after a reboot 
there's nothing in journalctl -r -b -1. This brings up fond memories -- ages 
ago I had a null modem adapter hooked up to a serial port, the kernel 
configured for a serial console, thusly I was able to capture OOPSes over the 
serial console, in situations like these.

But, these days, no more RS-232 ports. I dimly recall that a USB-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 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'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). 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 machines log to my server (which is the host too).

A special, long incantation is appended to /etc/rsyslog.conf (on the guest).
On the host I Provided TCP/UDP syslog reception in the same conf file.


I now changed the guest machine from "sound ac97" to "sound ich6" and sound now 
works OK.
The old setup was OK for a very long time.

It is a worry when a stable setup stops working, so the OP may consider trying 
different
guest settings.

YMMV

--
Eyal Lebedinsky (fed...@eyal.emu.id.au)
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: qemu crashes kernel-5.18.11-200.fc36.x86_64

[Jonathan Billings]

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 bug, except that I do not have anything to 
> conclusively prove it; but this sounds very promising.

Sounds like you (or the bug you post) would benefit from setting up the kdump 
service to capture the kernel crash. 

https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes

--
Jonathan Billings___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: qemu crashes kernel-5.18.11-200.fc36.x86_64

[ToddAndMargo via users]

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 themselves
from there.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: qemu crashes kernel-5.18.11-200.fc36.x86_64

[Sam Varshavchik]

ToddAndMargo via users writes:


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 from the network. I've got nothing: after a  
reboot there's nothing in journalctl -r -b -1. This brings up fond memories  
-- ages ago I had a null modem adapter hooked up to a serial port, the  
kernel configured for a serial console, thusly I was able to capture OOPSes  
over the serial console, in situations like these.


But, these days, no more RS-232 ports. I dimly recall that a USB-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 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've got nuthin' worth putting into  
Bugzilla.


Hi Sam,

Did you try ?


Yes. It's dead 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 useful bug report.


Here's an example of a useful bug report: 2107827

That one looks like like my bug, except that I do not have anything to  
conclusively prove it; but this sounds very promising.




pgpdyXOsheg2d.pgp
Description: PGP signature
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: qemu crashes kernel-5.18.11-200.fc36.x86_64

[ToddAndMargo via users]

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 from the network. I've got 
nothing: after a reboot there's nothing in journalctl -r -b -1. This 
brings up fond memories -- ages ago I had a null modem adapter hooked up 
to a serial port, the kernel configured for a serial console, thusly I 
was able to capture OOPSes over the serial console, in situations like 
these.


But, these days, no more RS-232 ports. I dimly recall that a USB-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 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've got nuthin' 
worth putting into Bugzilla.


Hi Sam,

Did you try ?

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?

-T
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: qemu crashes kernel-5.18.11-200.fc36.x86_64

[Eyal Lebedinsky]

On 19/07/2022 07.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 from the network. I've got nothing: after a reboot 
there's nothing in journalctl -r -b -1. This brings up fond memories -- ages 
ago I had a null modem adapter hooked up to a serial port, the kernel 
configured for a serial console, thusly I was able to capture OOPSes over the 
serial console, in situations like these.

But, these days, no more RS-232 ports. I dimly recall that a USB-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 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'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). 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 machines log to my server (which is the host too).

A special, long incantation is appended to /etc/rsyslog.conf (on the guest).
On the host I Provided TCP/UDP syslog reception in the same conf file.

--
Eyal Lebedinsky (fed...@eyal.emu.id.au)
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: qemu crashes kernel-5.18.11-200.fc36.x86_64

[Tim via users]

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 2022 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

qemu crashes kernel-5.18.11-200.fc36.x86_64

[Sam Varshavchik]

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 a  
reboot there's nothing in journalctl -r -b -1. This brings up fond memories  
-- ages ago I had a null modem adapter hooked up to a serial port, the  
kernel configured for a serial console, thusly I was able to capture OOPSes  
over the serial console, in situations like these.


But, these days, no more RS-232 ports. I dimly recall that a USB-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 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've got nuthin' worth putting into  
Bugzilla.




pgpOLK_izNWTF.pgp
Description: PGP signature
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Frequent Crashes with Puddletag

[Samuel Sieb]

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().isVisible() and
h.isVisible(): numsteps = e.angleDelta().y() / 5


Python3 changed the default for division.  Python2 would always give
you an integer result from dividing integers, but Python3 will give
you a float if the numbers are not evenly divisible.  The simplest
fix would be to change the "/" to a "//" (integer division).


Good catch!  I attached to the argument 1 and got caught by the off by 1
error, the argument count starts at zero, not 1, and so was looking at
h.value() instead of numsteps.
TypeError: setValue(self, int): argument 1 has unexpected type 'float'




  h.setValue(h.value() - numsteps)   <  here
  e.accept()
  else:
  QTableView.wheelEvent(self, e)


Argument 1 is "h.value() - numsteps".  Argument 0 is the "self" 
parameter that you don't see.  It's a class method call, so the first 
argument is the instance variable.  (Referred to as "this" in several 
other languages.)

___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Frequent Crashes with Puddletag

[stan via users]

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(): numsteps = e.angleDelta().y() / 5  
> 
> Python3 changed the default for division.  Python2 would always give
> you an integer result from dividing integers, but Python3 will give
> you a float if the numbers are not evenly divisible.  The simplest
> fix would be to change the "/" to a "//" (integer division).

Good catch!  I attached to the argument 1 and got caught by the off by 1
error, the argument count starts at zero, not 1, and so was looking at
h.value() instead of numsteps.  
TypeError: setValue(self, int): argument 1 has unexpected type 'float'

> 
> >  h.setValue(h.value() - numsteps)   <  here
> >  e.accept()
> >  else:
> >  QTableView.wheelEvent(self, e)  
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Frequent Crashes with Puddletag

[Samuel Sieb]

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 for division.  Python2 would always give you 
an integer result from dividing integers, but Python3 will give you a 
float if the numbers are not evenly divisible.  The simplest fix would 
be to change the "/" to a "//" (integer division).



 h.setValue(h.value() - numsteps)   <  here
 e.accept()
 else:
 QTableView.wheelEvent(self, e)

___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Frequent Crashes with Puddletag

[Roger Heflin]

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 this language does.

C/C++ would always take int/5 == another int, but int/5.0 will be promoted
to a float, and languages without those sort of type rules may be vague
about what type numsteps is defined as and ends up as.

In c/c++ this code would work to convert the result to an int, no matter
which of the 2 values is not an int.

h.setValue((int)(h.value() - numsteps))

In some other languages it might be necessary to use a function int(
h.value() - numsteps) to convert it.




On Thu, May 26, 2022 at 8:18 AM stan via users <
users@lists.fedoraproject.org> wrote:

> 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: 3 (BadWindow),
> > sequence: 43350, resource id: 14681466, major code: 40
> > (TranslateCoords), minor code: 0 Traceback (most recent call last):
> >File "/usr/lib/python3.10/site-packages/puddlestuff/tagmodel.py",
> > line 2483, in wheelEvent
> >  h.setValue(h.value() - numsteps)
> > TypeError: setValue(self, int): argument 1 has unexpected type 'float'
> > Traceback (most recent call last):
> >File "/usr/lib/python3.10/site-packages/puddlestuff/tagmodel.py",
> > line 2483, in wheelEvent
> >  h.setValue(h.value() - numsteps)
> > TypeError: setValue(self, int): argument 1 has unexpected type 'float'
> >
> > Yes, it does appear to be the same issue that was reported on
> > Bugzilla. I have added my comment to that bug, along with the above
> > quoted output.
> >
> > Still, if anyone has any ideas, I'm all ears. I have attempted to
> > install puddletag from GIT. It installs fine, but it won't run... But
> > that is a subject for another thread. I hesitate to bring that here,
> > until I have that same issue with other Python based applications on
> > Fedora 36.
>
> 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
> h.setValue(h.value() - numsteps)   <  here
> e.accept()
> else:
> QTableView.wheelEvent(self, e)
>
> in the class
> class TagTable(QTableView):
>
> which inherits from the class QTableView in PyQt5.QtWidgets.
>
> All that is to say, if my analysis is correct, that the problem is
> probably in PyQt5.QtWidgets QTableView where the horizontalScrollBar
> function is defined.  It probably has an error in the value function,
> defaulting to a float instead of an int.  I looked for the package with
> this function to follow up, but a quick search didn't find it.  Qt5 is
> huge!  And I was in a hurry.
>
> You might put this in the bugzilla, or ask if you can move it over to
> PyQt5. python3-qt5?  qt5-???
> ___
> 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: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Frequent Crashes with Puddletag

[stan via users]

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: 3 (BadWindow),
> sequence: 43350, resource id: 14681466, major code: 40
> (TranslateCoords), minor code: 0 Traceback (most recent call last):
>    File "/usr/lib/python3.10/site-packages/puddlestuff/tagmodel.py", 
> line 2483, in wheelEvent
>      h.setValue(h.value() - numsteps)
> TypeError: setValue(self, int): argument 1 has unexpected type 'float'
> Traceback (most recent call last):
>    File "/usr/lib/python3.10/site-packages/puddlestuff/tagmodel.py", 
> line 2483, in wheelEvent
>      h.setValue(h.value() - numsteps)
> TypeError: setValue(self, int): argument 1 has unexpected type 'float'
> 
> Yes, it does appear to be the same issue that was reported on
> Bugzilla. I have added my comment to that bug, along with the above
> quoted output.
> 
> Still, if anyone has any ideas, I'm all ears. I have attempted to 
> install puddletag from GIT. It installs fine, but it won't run... But 
> that is a subject for another thread. I hesitate to bring that here, 
> until I have that same issue with other Python based applications on 
> Fedora 36.

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
h.setValue(h.value() - numsteps)   <  here
e.accept()
else:
QTableView.wheelEvent(self, e)

in the class
class TagTable(QTableView):

which inherits from the class QTableView in PyQt5.QtWidgets.

All that is to say, if my analysis is correct, that the problem is
probably in PyQt5.QtWidgets QTableView where the horizontalScrollBar
function is defined.  It probably has an error in the value function,
defaulting to a float instead of an int.  I looked for the package with
this function to follow up, but a quick search didn't find it.  Qt5 is
huge!  And I was in a hurry.

You might put this in the bugzilla, or ask if you can move it over to
PyQt5. python3-qt5?  qt5-???
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Frequent Crashes with Puddletag

[Steven P. Ulrick]

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 have thought of that first.

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: 3 (BadWindow), sequence: 43350, 
resource id: 14681466, major code: 40 (TranslateCoords), minor code: 0

Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/puddlestuff/tagmodel.py", 
line 2483, in wheelEvent

    h.setValue(h.value() - numsteps)
TypeError: setValue(self, int): argument 1 has unexpected type 'float'
Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/puddlestuff/tagmodel.py", 
line 2483, in wheelEvent

    h.setValue(h.value() - numsteps)
TypeError: setValue(self, int): argument 1 has unexpected type 'float'

Yes, it does appear to be the same issue that was reported on Bugzilla. 
I have added my comment to that bug, along with the above quoted output.


Still, if anyone has any ideas, I'm all ears. I have attempted to 
install puddletag from GIT. It installs fine, but it won't run... But 
that is a subject for another thread. I hesitate to bring that here, 
until I have that same issue with other Python based applications on 
Fedora 36.


Steven P. Ulrick
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Frequent Crashes with Puddletag

[Steven P. Ulrick]

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 have thought of that first.

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: 3 (BadWindow), sequence: 43350, 
resource id: 14681466, major code: 40 (TranslateCoords), minor code: 0

Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/puddlestuff/tagmodel.py", 
line 2483, in wheelEvent

    h.setValue(h.value() - numsteps)
TypeError: setValue(self, int): argument 1 has unexpected type 'float'
Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/puddlestuff/tagmodel.py", 
line 2483, in wheelEvent

    h.setValue(h.value() - numsteps)
TypeError: setValue(self, int): argument 1 has unexpected type 'float'

Yes, it does appear to be the same issue that was reported on Bugzilla. 
I have added my comment to that bug, along with the above quoted output.


Still, if anyone has any ideas, I'm all ears. I have attempted to 
install puddletag from GIT. It installs fine, but it won't run... But 
that is a subject for another thread. I hesitate to bring that here, 
until I have that same issue with other Python based applications on 
Fedora 36.


Steven P. Ulrick
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Frequent Crashes with Puddletag

[Roger Heflin]

On Wed, May 25, 2022 at 4:02 PM Steven P. Ulrick  wrote:

> Hello Everyone,
>
> I am running Fedora 36, fully updated as of right now...
>
> I am running version 2.1.1-1 of puddletag. That is the most recent
> version of puddletag in the official Fedora repo.
>
> I have 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 how to
> debug/troubleshoot this issue?
>
> There is one bug on the Fedora Bugzilla for puddletag:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2084341
>
> but since puddletag crashes silently, and without invoking ABRT, I have
> no idea if that report has anything to do with my issue.
>
>
>
>
>
to debug:
If you aren't starting it from the command line, then start it from the
command line in a terminal window and see if it says anything useful when
it crashes/exits.

Not triggering abrtd would seem to indicate it is exiting because of some
detected condition.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Frequent Crashes with Puddletag

[Samuel Sieb]

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 -- 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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Frequent Crashes with Puddletag

[Steven P. Ulrick]

Hello Everyone,

I am running Fedora 36, fully updated as of right now...

I am running version 2.1.1-1 of puddletag. That is the most recent 
version of puddletag in the official Fedora repo.


I have 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 how to 
debug/troubleshoot this issue?


There is one bug on the Fedora Bugzilla for puddletag:

https://bugzilla.redhat.com/show_bug.cgi?id=2084341

but since puddletag crashes silently, and without invoking ABRT, I have 
no idea if that report has anything to do with my issue.


Thank you,

Steven P. Ulrick

___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Using Fish as default shell crashes KDE

[Ben Cotton]

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 things that I cared about (certain autostart scripts, for
example), but was at least basically functional. What I've done is to
set fish as the default shell in Konsole.

I suggest filing an issue with the KDE SIG:
https://pagure.io/fedora-kde/SIG/new_issue

I imagine it's something that will need to be fixed upstream, but
they'll be the folks who can help coordinate that.

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Using Fish as default shell crashes KDE

[Lily White]

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 by 
the shell (both fish and bash), and it even thinks I need to install the 
`systemd' package. Though `systemctl' is still available.


My guess is that the booting KDE requires running something in my profiles.

Any explanations?
--
From LilyWhite with love


OpenPGP_0xEE978FA44869B163.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?

[Rogan Dawes]

> 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 the latest NVidia driver (495.46).
> 
> What is unfortunately happening, is that if my laptop goes to sleep, the TV 
> sees that the
> source disappears, and "tries to look for the laptop", repeatedly. This ends 
> up
> waking up the laptop (sometimes), until the TV eventually gives up and turns 
> itself off.
> The problem is then that the laptop no longer detects that the TV is 
> connected to the HDMI
> port, and I 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.

Just to be absolutely clear, it doesn't seem to be a requirement that the TV 
eventually gives up and turns itself off before the behaviour manifests on my 
laptop. I have caught it "searching" for a signal (although not cycling between 
inputs), but I was too late to save my laptop from going into this state where 
it no longer detects the external display. 

Also, I can unplug and replug the HDMI cable, and the TV detects that there is 
a connection (display changes from "No signal" to a blue background, but 
eventually goes back to "No signal"), but the laptop does not detect the 
external display.

Also, if I use a USB-C to HDMI adapter, it does detect the display being 
connected while in this state, but this is not a great solution because the 
laptop does not appear to like the USB-C to HDMI adapter being disconnected. 
This is what I get:

[377553.263099] usb 3-1: USB disconnect, device number 2
[377553.363447] xhci_hcd :3d:00.0: xHCI host controller not responding, 
assume dead
[377553.363451] xhci_hcd :3d:00.0: HC died; cleaning up
[377553.380937] xhci_hcd :3d:00.0: remove, state 4
[377553.380940] usb usb4: USB disconnect, device number 1
[377553.381199] xhci_hcd :3d:00.0: USB bus 4 deregistered
[377553.381346] xhci_hcd :3d:00.0: remove, state 1
[377553.381349] usb usb3: USB disconnect, device number 1
[377553.381725] xhci_hcd :3d:00.0: Host halt failed, -19
[377553.381729] xhci_hcd :3d:00.0: Host not accessible, reset failed.
[377553.381846] xhci_hcd :3d:00.0: USB bus 3 deregistered
[377553.394128] pci_bus :06: Allocating resources
[377553.394140] pcieport :06:01.0: bridge window [io  0x1000-0x0fff] to 
[bus 08-3c] add_size 1000
[377553.394143] pcieport :06:02.0: bridge window [io  0x1000-0x0fff] to 
[bus 3d] add_size 1000
[377553.394144] pcieport :06:02.0: bridge window [mem 0x0010-0x000f 
64bit pref] to [bus 3d] add_size 20 add_align 10
[377553.394146] pcieport :05:00.0: bridge window [io  0x1000-0x0fff] to 
[bus 06-3d] add_size 3000
[377553.394149] pcieport :05:00.0: BAR 13: no space for [io  size 0x3000]
[377553.394150] pcieport :05:00.0: BAR 13: failed to assign [io  size 
0x3000]
[377553.394151] pcieport :05:00.0: BAR 13: no space for [io  size 0x3000]
[377553.394152] pcieport :05:00.0: BAR 13: failed to assign [io  size 
0x3000]
[377553.394156] pcieport :06:02.0: BAR 15: no space for [mem size 
0x0020 64bit pref]
[377553.394157] pcieport :06:02.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
[377553.394158] pcieport :06:01.0: BAR 13: no space for [io  size 0x1000]
[377553.394158] pcieport :06:01.0: BAR 13: failed to assign [io  size 
0x1000]
[377553.394159] pcieport :06:02.0: BAR 13: no space for [io  size 0x1000]
[377553.394160] pcieport :06:02.0: BAR 13: failed to assign [io  size 
0x1000]
[377553.394162] pcieport :06:02.0: BAR 15: no space for [mem size 
0x0020 64bit pref]
[377553.394163] pcieport :06:02.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
[377553.394164] pcieport :06:02.0: BAR 13: no space for [io  size 0x1000]
[377553.394164] pcieport :06:02.0: BAR 13: failed to assign [io  size 
0x1000]
[377553.394165] pcieport :06:01.0: BAR 13: no space for [io  size 0x1000]
[377553.394166] pcieport :06:01.0: BAR 13: failed to assign [io  size 
0x1000]
[377558.553883] pcieport :06:00.0: can't change power state from D3cold to 
D0 (config space inaccessible)
[377558.554278] pci_bus :07: busn_res: [bus 07] is released
[377558.554418] pci_bus :08: busn_res: [bus 08-3c] is released
[377558.554530] pci_bus :3d: busn_res: [bus 3d] is released
[377558.554725] pci_bus :06: busn_res: [bus 06-3d] is released

And reconnecting it does nothing immediately, but about two to three minutes 
later, the USB-C adapter is recognised again:

[377710.601196] pci :05:00.0: [8086:15da] type 01 class 0x060400
[377710.601265] pci :05:00.0: enabling Extended Tags
[377710.601403] pci :05:00.0: supports D1 

Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?

[Rogan Dawes]

> 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
> hopefully it will revive the display!
> 
> Thanks!

Unfortunately, this didn't work. I still sit with the same problem.

Can anyone point me to some debug settings that I can enable, that will 
potentially give me some insight into what the two different graphics devices 
are seeing when this is happening?

i.e. logs that would show e.g. external monitor connected, external monitor 
disconnected events, graphics wakeup events, etc?
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?

[Rogan Dawes]

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
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?

[Rogan Dawes]

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-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?

[Rogan Dawes]

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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?

[Rogan Dawes]

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 hopefully it will revive the display!

Thanks!
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?

[Tim via users]

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 input (e.g. you rebooted, long-idle
time screen-blanked, etc), the monitor would go scanning through its
other input choices.

Unfortunately, like nearly all modern devices, it's painfully slow at
doing this (quite why anything needs 10 - 15 seconds to change inputs
escapes me, other than designed by an arse).  Then, when you tried to
do something it was probably on the wrong input, and was so slow to get
around to the input you wanted the display card had given up on the
monitor (chicken and egg problem).  Not to mention being painful to see
boot-up screens.

If you had two devices connected to the monitor, it was a real
nuisance.  It'd latch onto the always-on source, and was nearly
impossible to get it to wait for the just switched on source.

If you have any automatic input scanning options on your display,
switch them off.  And connecting your source to input one may help.
 
-- 
 
uname -rsvp
Linux 3.10.0-1160.49.1.el7.x86_64 #1 SMP Tue Nov 30 15:51:32 UTC 2021 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?

[Dave Ulrick]

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 had zero results 
in my searching.


This seems to be a long running issue with various Nvidia cards, in my 
experience. If a monitor is present and powered on at boot time 
everything is fine. If the monitor gets powered off or disconnected it 
won't ever come alive again, until the next reboot. This is not 
limited just to nvidia's drivers. In all other respects my old geforce 
gtx 285 works just fine with nouveau; this is the only defect.


Several months ago I started to experience a similar issue: screen going 
off while PC is sleeping then never coming back on until reboot.


When a sleep event occurred, syslog showed a failed attempt to suspend 
the NVIDIA device. This led me to do a Google search that led me to a 
new RPM:


xorg-x11-drv-nvidia-power

It installed several service unit files:

/usr/lib/systemd/system/nvidia-fallback.service
/usr/lib/systemd/system/nvidia-hibernate.service
/usr/lib/systemd/system/nvidia-resume.service
/usr/lib/systemd/system/nvidia-suspend.service

I don't recall whether I had to manually enable any of these services, 
but I eventually managed to restore proper NVIDIA behavior for power events.


Dave
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?

[Patrick O'Callaghan]

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 a rather difficult thing to google, I have had zero results
> > in my  
> > searching.
> 
> This seems to be a long running issue with various Nvidia cards, in
> my  
> experience. If a monitor is present and powered on at boot time
> everything is  
> fine. If the monitor gets powered off or disconnected it won't ever
> come  
> alive again, until the next reboot. This is not limited just to
> nvidia's  
> drivers. In all other respects my old geforce gtx 285 works just fine
> with  
> nouveau; this is the only defect.

I have a single monitor connected via a KVM switch to two video
outputs, the onboard Intel and an NVidia GPU card. I use this setup for
VMs with GPU passthrough. The first switch I tried had exactly this
problem, i.e. if I switched away from the NVidia and then back again it
would remain off. I ended up getting a different model KVM switch that
maintains each of its connections "live" so the problem doesn't occur.
Possibly this is something the OP could consider.

poc
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?

[Sam Varshavchik]

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 seems to be a long running issue with various Nvidia cards, in my  
experience. If a monitor is present and powered on at boot time everything is  
fine. If the monitor gets powered off or disconnected it won't ever come  
alive again, until the next reboot. This is not limited just to nvidia's  
drivers. In all other respects my old geforce gtx 285 works just fine with  
nouveau; this is the only defect.




pgpULLmv9HY0_.pgp
Description: PGP signature
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?

[Jon LaBadie]

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 disconnecting 
and reconnecting the HDMI cable does not have the same effect.

I can perhaps look at interposing a breakout board on the HDMI cable, and using 
a logic analyser on certain pins (i.e. those that carry the DDC protocol used 
to enumerate the display modes supported by the connected display). That might 
allow me to see that the laptop is or isn't recognising that the display is 
connected and performing the DDC interrogation. But I imagine this would also 
be possible by enabling verbose logging too, which would probably be a lot 
easier in the short term.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

End of included message <<<


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.
Note, the computer does not go to suspend or hibernate ever.  After
a time, the blank monitor does not come back if I key press or mouse
move.  Yet I can here the computer has been stimulated.

Sometimes if I power cycle the monitor it comes back though most
often not.

Rebooting of course awakens the monitor.

Also, I've found if I ssh in remotely and log out my console
session, when the display manager presents its login screen,
the monitor awakens.

Jon

--
Jon H. LaBadie  jo...@jgcomp.com
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?

[Rogan Dawes]

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 effect.

I can perhaps look at interposing a breakout board on the HDMI cable, and using 
a logic analyser on certain pins (i.e. those that carry the DDC protocol used 
to enumerate the display modes supported by the connected display). That might 
allow me to see that the laptop is or isn't recognising that the display is 
connected and performing the DDC interrogation. But I imagine this would also 
be possible by enabling verbose logging too, which would probably be a lot 
easier in the short term.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?

[stan via users]

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)" graphics subsystem. As far as I can make out,
> I am using the latest NVidia driver (495.46).
> 
> What is unfortunately happening, is that if my laptop goes to sleep,
> the TV sees that the source disappears, and "tries to look for the
> laptop", repeatedly. This ends up waking up the laptop (sometimes),
> until the TV eventually gives up and turns itself off. The problem is
> then that the laptop no longer detects that the TV is connected to
> the HDMI port, and I 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.

When you say 'turns itself off', does it actually fully power down?
Have you tried powering down the TV, waiting 10 or 15 seconds, and then
powering back up?  It should look for a source again, and if the laptop
is not sleeping, it should find it, and everything should just work.

Another thought.  Have you tried reloading the video driver when you
take the laptop out of sleep?  It should look for outputs, and if the
TV is only in suspend, it might respond to status queries.  Seems
doubtful, because if the laptop was aware there was a connection when
it went to sleep, it probably tries sending output to the TV when it
wakes.  And that isn't waking the TV.

> This is a rather difficult thing to google, I have had zero results
> in my searching.
> 
> I also tried looking for any logs that would indicate what went
> wrong, but I found nothing in the syslog, etc.

I don't think anything went wrong.  There is just a procedural mismatch
between the TV and the laptop.  Once the TV turns itself off because
there is no input, it seems to be unavailable for being turned on.
What is the startup sequence like?  Do you start the laptop and then
turn the TV on?  Or could it be that they are turned on simultaneously,
and the TV is still looking for a source when the laptop finishes
booting, and thus finds one?

> Can anyone give me pointers on how I can start debugging this? I am
> fairly technical, so can certainly follow instructions. I'm guessing
> I need to enable verbose logging for the driver so it can report when
> new displays are connected or disconnected, as well as any actions
> around those events?

No experience whatsoever with this, but that sounds reasonable.  From
the symptoms though, I don't think this is a driver issue.  I think the
TV is set up to ignore attempts to connect once it doesn't find a
source, and that it only looks for sources at power up.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Samsung Smart TV "crashes" NVidia driver, can't detect TV any more?

[Rogan Dawes]

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 the latest NVidia 
driver (495.46).

What is unfortunately happening, is that if my laptop goes to sleep, the TV 
sees that the source disappears, and "tries to look for the laptop", 
repeatedly. This ends up waking up the laptop (sometimes), until the TV 
eventually gives up and turns itself off. The problem is then that the laptop 
no longer detects that the TV is connected to the HDMI port, and I 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.

I also tried looking for any logs that would indicate what went wrong, but I 
found nothing in the syslog, etc.

Can anyone give me pointers on how I can start debugging this? I am fairly 
technical, so can certainly follow instructions. I'm guessing I need to enable 
verbose logging for the driver so it can report when new displays are connected 
or disconnected, as well as any actions around those events?

Thanks

Rogan
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Issues (hard crashes) with Google's Chrome...

[George N. White III]

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 log full of things , with:
> -> $ google-chrome --enable-logging --v=1
> of which most worrying are:
> ...
> [149778:149778:0100/00.007110:ERROR:external_vk_image_skia_representation.cc(151)]
>
> BeginAccess failed
> [149778:149778:0100/00.045833:FATAL:external_vk_image_gl_representation.cc(79)]
>
> Unable to create an ExternalSemaphore in
> ExternalVkImageGLRepresentation for synchronization with Vulkan
>

This implicates "vulcan", which AMD claims to support.  You should look for
other "amdgpu"
versions.   Report the issue at
https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/

Wayland is said to work better than Xorg with amdgpu, but laptop hybrid
graphics are problematic
(every vendor does it differently).

-- 
George N. White III
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Issues (hard crashes) with Google's Chrome...

[lejeczek via users]

.. 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:
...
[149778:149778:0100/00.007110:ERROR:external_vk_image_skia_representation.cc(151)] 
BeginAccess failed
[149778:149778:0100/00.045833:FATAL:external_vk_image_gl_representation.cc(79)] 
Unable to create an ExternalSemaphore in 
ExternalVkImageGLRepresentation for synchronization with Vulkan
[150084:1:1005/102829.364500:ERROR:command_buffer_proxy_impl.cc(328)] 
GPU state invalid after WaitForGetOffsetInRange.
[150234:1:1005/102829.382907:ERROR:command_buffer_proxy_impl.cc(125)] 
ContextResult::kTransientFailure: Failed to send 
GpuControl.CreateCommandBuffer.
[149735:149735:1005/102829.393012:ERROR:gpu_process_host.cc(956)] 
GPU process exited unexpectedly: exit_code=133
[150295:150295:1005/102829.529107:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process 
gpu-process.
[150295:150295:1005/102829.531704:ERROR:vulkan_device_queue.cc(217)] 
Vulkan: AMD RADV RENOIR (ACO)
amdgpu: The CS has been rejected, see dmesg for more 
information (-22).
[150295:150295:1005/102913.650278:ERROR:gles2_cmd_decoder_passthrough.cc(1547)] 
GLES2DecoderPassthroughImpl: Context reset detected after 
MakeCurrent.
[150295:150295:1005/102913.650922:ERROR:gpu_service_impl.cc(945)] 
Exiting GPU process because some drivers can't recover from 
errors. GPU process will restart shortly.
[150084:1:1005/102913.664169:ERROR:command_buffer_proxy_impl.cc(328)] 
GPU state invalid after WaitForGetOffsetInRange.
[149735:149735:1005/102913.668666:ERROR:command_buffer_proxy_impl.cc(328)] 
GPU state invalid after WaitForGetOffsetInRange.
[149735:149735:1005/102913.679697:ERROR:gpu_process_host.cc(956)] 
GPU process exited unexpectedly: exit_code=8704
[150569:150569:1005/102913.785831:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process 
gpu-process.
[150569:150569:1005/102913.787253:ERROR:vulkan_device_queue.cc(217)] 
Vulkan: AMD RADV RENOIR (ACO)

..

and 'dmesg'
...
[Oct 5 10:29] [drm:amdgpu_syncobj_lookup_and_add_to_sync 
[amdgpu]] *ERROR* syncobj 1834 failed to find fence @ 0 (-22)!
[  +0.000130] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed 
in the dependencies handling -22!



All that tempts me to report a 'bug' but since there is no 
'Chrome' in Bugzilla I thought I'd ask around here for 
thoughts & opinions.


Google's map is in my case the most evident place where 
Chrome struggles horribly, since the issues arose (I've 
reset Chrome's settings to defaults too)
I think that system coming back from 'sleep' might have a 
role in this - after reboot and until sleep I think Chrome 
runs fine but cannot say I 'programmatically' verified this.
Right now I'm on 5.14.9-200.fc34.x86_64 and 
google-chrome-stable-94.0.4606.71-1.x86_64 and in case 
hardware matters, which it most likely does - I'm on Lenovo 
e14 gen2 with AMD's 4500U.


many thanks, L.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Xorg crashes in KVM

[Ed Greshko]

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 started Xfce with xfwm4 and using firefox played a live-stream of 
Taiwan News on YouTube
and the audio/video sync was good fine. I also stream a John Oliver Last Week 
Tonight segment and it
was also good. The video was 16 minutes long and lips/audio were 99% fine.  A 
little blip here and there
but is recovered.   Surprised the heck out of me.  :-)

--
Remind me to ignore comments which aren't germane to the thread.

___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Xorg crashes in KVM

[Ed Greshko]

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 comments which aren't germane to the thread.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Xorg crashes in KVM

[Ed Greshko]

On 11/07/2021 18:22, Eyal Lebedinsky wrote:



On 11/07/2021 20.18, Ed Greshko wrote:

On 11/07/2021 18:17, Eyal Lebedinsky wrote:



On 11/07/2021 20.14, Ed Greshko wrote:

On 11/07/2021 16:19, Eyal Lebedinsky wrote:



On 11/07/2021 10.22, Ed Greshko wrote:

On 10/07/2021 19:09, Eyal Lebedinsky wrote:


On 10/07/2021 10.56, Ed Greshko 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 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 QXL for comparo but LXD could not 
start,
X repeatedly terminated with
[    43.747] resizing primary to 3840x2160
[    43.747] primary is 0x5640e09faa30
[    43.747] (EE) qxl(0): failed to set mode: Cannot allocate memory(EE)
I will deal with this later.



Is your host running low on memory?


I do not think so. I changed back to QXL and LXDM failed in a loop, at that 
point
I did this on the host:

$ free
   total    used    free  shared buff/cache   available
Mem:    32734592 3232096 7343812  246400 22158684    28782264
Swap:   16777212 1064704    15712508

The guest is configured with 8GB memory.

[later] I had a very vague memory that I needed to fiddle with the domain xml 
file.
I restored /etc/libvirt/qemu/e4.xml from backup and compared and sure it was 
different.

I used
$ sudo virsh edit e4
and set the  stanza to say

where it originally said

Now lxdm starts OK.

Audio sync still bad. Video barely keeps up. Probably similar to virtio mode.

I will run this way until I get an Xorg crash, then switch to virtio to see if 
it is better.



OK   I forgot to ask.  This is F34 installed from what Live Image?


This system was installed too many years ago to remember and upgraded every 
year.



I see.  What desktop and display manager?


xfce4 xfwm4



Oh, I can't seem to find xfwm4 display manager available for F34.

What is the outupt of

systemctl status display-manager


--
Remind me to ignore comments which aren't germane to the thread.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Xorg crashes in KVM

[Eyal Lebedinsky]

On 11/07/2021 20.18, Ed Greshko wrote:

On 11/07/2021 18:17, Eyal Lebedinsky wrote:



On 11/07/2021 20.14, Ed Greshko wrote:

On 11/07/2021 16:19, Eyal Lebedinsky wrote:



On 11/07/2021 10.22, Ed Greshko wrote:

On 10/07/2021 19:09, Eyal Lebedinsky wrote:


On 10/07/2021 10.56, Ed Greshko 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 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 QXL for comparo but LXD could not 
start,
X repeatedly terminated with
[    43.747] resizing primary to 3840x2160
[    43.747] primary is 0x5640e09faa30
[    43.747] (EE) qxl(0): failed to set mode: Cannot allocate memory(EE)
I will deal with this later.



Is your host running low on memory?


I do not think so. I changed back to QXL and LXDM failed in a loop, at that 
point
I did this on the host:

$ free
   total    used    free  shared buff/cache   available
Mem:    32734592 3232096 7343812  246400 22158684    28782264
Swap:   16777212 1064704    15712508

The guest is configured with 8GB memory.

[later] I had a very vague memory that I needed to fiddle with the domain xml 
file.
I restored /etc/libvirt/qemu/e4.xml from backup and compared and sure it was 
different.

I used
$ sudo virsh edit e4
and set the  stanza to say

where it originally said

Now lxdm starts OK.

Audio sync still bad. Video barely keeps up. Probably similar to virtio mode.

I will run this way until I get an Xorg crash, then switch to virtio to see if 
it is better.



OK   I forgot to ask.  This is F34 installed from what Live Image?


This system was installed too many years ago to remember and upgraded every 
year.



I see.  What desktop and display manager?


xfce4 xfwm4

--
Eyal Lebedinsky (fed...@eyal.emu.id.au)
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Xorg crashes in KVM

[Ed Greshko]

On 11/07/2021 18:17, Eyal Lebedinsky wrote:



On 11/07/2021 20.14, Ed Greshko wrote:

On 11/07/2021 16:19, Eyal Lebedinsky wrote:



On 11/07/2021 10.22, Ed Greshko wrote:

On 10/07/2021 19:09, Eyal Lebedinsky wrote:


On 10/07/2021 10.56, Ed Greshko 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 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 QXL for comparo but LXD could not 
start,
X repeatedly terminated with
[    43.747] resizing primary to 3840x2160
[    43.747] primary is 0x5640e09faa30
[    43.747] (EE) qxl(0): failed to set mode: Cannot allocate memory(EE)
I will deal with this later.



Is your host running low on memory?


I do not think so. I changed back to QXL and LXDM failed in a loop, at that 
point
I did this on the host:

$ free
   total    used    free  shared buff/cache   available
Mem:    32734592 3232096 7343812  246400 22158684    28782264
Swap:   16777212 1064704    15712508

The guest is configured with 8GB memory.

[later] I had a very vague memory that I needed to fiddle with the domain xml 
file.
I restored /etc/libvirt/qemu/e4.xml from backup and compared and sure it was 
different.

I used
$ sudo virsh edit e4
and set the  stanza to say

where it originally said

Now lxdm starts OK.

Audio sync still bad. Video barely keeps up. Probably similar to virtio mode.

I will run this way until I get an Xorg crash, then switch to virtio to see if 
it is better.



OK   I forgot to ask.  This is F34 installed from what Live Image?


This system was installed too many years ago to remember and upgraded every 
year.



I see.  What desktop and display manager?

--
Remind me to ignore comments which aren't germane to the thread.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Xorg crashes in KVM

[Eyal Lebedinsky]

On 11/07/2021 20.14, Ed Greshko wrote:

On 11/07/2021 16:19, Eyal Lebedinsky wrote:



On 11/07/2021 10.22, Ed Greshko wrote:

On 10/07/2021 19:09, Eyal Lebedinsky wrote:


On 10/07/2021 10.56, Ed Greshko 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 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 QXL for comparo but LXD could not 
start,
X repeatedly terminated with
[    43.747] resizing primary to 3840x2160
[    43.747] primary is 0x5640e09faa30
[    43.747] (EE) qxl(0): failed to set mode: Cannot allocate memory(EE)
I will deal with this later.



Is your host running low on memory?


I do not think so. I changed back to QXL and LXDM failed in a loop, at that 
point
I did this on the host:

$ free
   total    used    free  shared buff/cache   available
Mem:    32734592 3232096 7343812  246400 22158684    28782264
Swap:   16777212 1064704    15712508

The guest is configured with 8GB memory.

[later] I had a very vague memory that I needed to fiddle with the domain xml 
file.
I restored /etc/libvirt/qemu/e4.xml from backup and compared and sure it was 
different.

I used
$ sudo virsh edit e4
and set the  stanza to say

where it originally said

Now lxdm starts OK.

Audio sync still bad. Video barely keeps up. Probably similar to virtio mode.

I will run this way until I get an Xorg crash, then switch to virtio to see if 
it is better.



OK   I forgot to ask.  This is F34 installed from what Live Image?


This system was installed too many years ago to remember and upgraded every 
year.


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.


--
Eyal Lebedinsky (fed...@eyal.emu.id.au)
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Xorg crashes in KVM

[Ed Greshko]

On 11/07/2021 16:19, Eyal Lebedinsky wrote:



On 11/07/2021 10.22, Ed Greshko wrote:

On 10/07/2021 19:09, Eyal Lebedinsky wrote:


On 10/07/2021 10.56, Ed Greshko 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 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 QXL for comparo but LXD could not 
start,
X repeatedly terminated with
[    43.747] resizing primary to 3840x2160
[    43.747] primary is 0x5640e09faa30
[    43.747] (EE) qxl(0): failed to set mode: Cannot allocate memory(EE)
I will deal with this later.



Is your host running low on memory?


I do not think so. I changed back to QXL and LXDM failed in a loop, at that 
point
I did this on the host:

$ free
   total    used    free  shared buff/cache   available
Mem:    32734592 3232096 7343812  246400 22158684    28782264
Swap:   16777212 1064704    15712508

The guest is configured with 8GB memory.

[later] I had a very vague memory that I needed to fiddle with the domain xml 
file.
I restored /etc/libvirt/qemu/e4.xml from backup and compared and sure it was 
different.

I used
$ sudo virsh edit e4
and set the  stanza to say

where it originally said

Now lxdm starts OK.

Audio sync still bad. Video barely keeps up. Probably similar to virtio mode.

I will run this way until I get an Xorg crash, then switch to virtio to see if 
it is better.



OK   I forgot to ask.  This is F34 installed from what Live Image?

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.


--
Remind me to ignore comments which aren't germane to the thread.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Xorg crashes in KVM

[Eyal Lebedinsky]

On 11/07/2021 10.22, Ed Greshko wrote:

On 10/07/2021 19:09, Eyal Lebedinsky wrote:


On 10/07/2021 10.56, Ed Greshko 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 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 QXL for comparo but LXD could not 
start,
X repeatedly terminated with
[    43.747] resizing primary to 3840x2160
[    43.747] primary is 0x5640e09faa30
[    43.747] (EE) qxl(0): failed to set mode: Cannot allocate memory(EE)
I will deal with this later.



Is your host running low on memory?


I do not think so. I changed back to QXL and LXDM failed in a loop, at that 
point
I did this on the host:

$ free
   totalusedfree  shared  buff/cache   available
Mem:32734592 3232096 7343812  2464002215868428782264
Swap:   16777212 106470415712508

The guest is configured with 8GB memory.

[later] I had a very vague memory that I needed to fiddle with the domain xml 
file.
I restored /etc/libvirt/qemu/e4.xml from backup and compared and sure it was 
different.

I used
$ sudo virsh edit e4
and set the  stanza to say

where it originally said

Now lxdm starts OK.

Audio sync still bad. Video barely keeps up. Probably similar to virtio mode.

I will run this way until I get an Xorg crash, then switch to virtio to see if 
it is better.

--
Eyal Lebedinsky (fed...@eyal.emu.id.au)
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Xorg crashes in KVM

[Ed Greshko]

On 10/07/2021 19:09, Eyal Lebedinsky wrote:


On 10/07/2021 10.56, Ed Greshko 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 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 QXL for comparo but LXD could not 
start,
X repeatedly terminated with
[    43.747] resizing primary to 3840x2160
[    43.747] primary is 0x5640e09faa30
[    43.747] (EE) qxl(0): failed to set mode: Cannot allocate memory(EE)
I will deal with this later.



Is your host running low on memory?

--
Remind me to ignore comments which aren't germane to the thread.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Xorg crashes in KVM

[Eyal Lebedinsky]

On 10/07/2021 10.56, Ed Greshko 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 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 QXL for comparo but LXD could not 
start,
X repeatedly terminated with
[43.747] resizing primary to 3840x2160
[43.747] primary is 0x5640e09faa30
[43.747] (EE) qxl(0): failed to set mode: Cannot allocate memory(EE)
I will deal with this later.

--
Eyal Lebedinsky (fed...@eyal.emu.id.au)
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Xorg crashes in KVM

[Ed Greshko]

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 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?

--
Remind me to ignore comments which aren't germane to the thread.
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Xorg crashes in KVM

[Eyal Lebedinsky]

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 precede the crash ###
Jul  9 16:28:47 e4 kernel: f 4026531864#104645: failed to wait on release 24 
after spincount 301
Jul  9 16:28:47 e4 kernel: [TTM] Buffer eviction failed
Jul  9 16:28:47 e4 kernel: qxl :00:01.0: object_init failed for (458752, 
0x0001)
Jul  9 16:28:47 e4 kernel: [drm:qxl_gem_object_create [qxl]] *ERROR* Failed to 
allocate GEM object (454760, 1, 4096, -12)
Jul  9 16:28:47 e4 kernel: [drm:qxl_alloc_ioctl [qxl]] *ERROR* qxl_alloc_ioctl: 
failed to create gem ret=-12
Jul  9 16:28:47 e4 kernel: kauditd_printk_skb: 16 callbacks suppressed
Jul  9 16:28:47 e4 kernel: audit: type=1701 audit(1625812127.806:325): auid=4294967295 uid=0 gid=0 
ses=4294967295 subj=kernel pid=1035 comm="Xorg" exe="/usr/libexec/Xorg" sig=6 
res=1
Jul  9 16:28:47 e4 audit[1035]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel 
pid=1035 comm="Xorg" exe="/usr/libexec/Xorg" sig=6 res=1
Jul  9 16:28:48 e4 systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Jul  9 16:28:48 e4 audit: BPF prog-id=49 op=LOAD
Jul  9 16:28:48 e4 kernel: audit: type=1334 audit(1625812128.526:326): 
prog-id=49 op=LOAD
Jul  9 16:28:48 e4 audit: BPF prog-id=50 op=LOAD
Jul  9 16:28:48 e4 audit: BPF prog-id=51 op=LOAD
Jul  9 16:28:48 e4 kernel: audit: type=1334 audit(1625812128.528:327): 
prog-id=50 op=LOAD
Jul  9 16:28:48 e4 kernel: audit: type=1334 audit(1625812128.528:328): 
prog-id=51 op=LOAD
Jul  9 16:28:48 e4 systemd[1]: Started Process Core Dump (PID 134753/UID 0).
Jul  9 16:28:48 e4 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel 
msg='unit=systemd-coredump@0-134753-0 comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul  9 16:28:48 e4 kernel: audit: type=1130 audit(1625812128.593:329): pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=kernel msg='unit=systemd-coredump@0-134753-0 comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul  9 16:28:52 e4 systemd-coredump[134754]: Process 1035 (Xorg) of user 0 
dumped core.

Stack trace of thread 1035:
#0  0x7f3c01fda2a2 n/a (libc.so.6 + 0x3d2a2)
#1  0x7f3c01fc38a4 n/a (libc.so.6 + 0x268a4)
#2  0x5595780f7170 OsAbort (Xorg + 0x1ba170)
#3  0x5595780ff446 FatalError (Xorg + 0x1c2446)
#4  0x5595780f5d3a OsSigHandler (Xorg + 0x1b8d3a)
#5  0x7f3c0217fa20 __restore_rt (libpthread.so.0 + 0x13a20)
#6  0x7f3c01716a35 qxl_image_create (qxl_drv.so + 0x8a35)
#7  0x7f3c01716e66 qxl_surface_put_image_for_reals (qxl_drv.so + 0x8e66)
#8  0x7f3c01723350 uxa_copy_n_to_n (qxl_drv.so + 0x15350)
#9  0x5595780d475b miCopyRegion (Xorg + 0x19775b)
#10 0x5595780d735c miDoCopy (Xorg + 0x19a35c)
#11 0x7f3c01723552 uxa_copy_area (qxl_drv.so + 0x15552)
#12 0x5595780831e9 damageCopyArea (Xorg + 0x1461e9)
#13 0x559577f964af ProcCopyArea (Xorg + 0x594af)
#14 0x559577f862d7 main (Xorg + 0x492d7)
#15 0x7f3c01fc4b75 n/a (libc.so.6 + 0x27b75)
#16 0x559577f8667e _start (Xorg + 0x4967e)

Stack trace of thread 1038:
#0  0x7f3c02181a8a __futex_abstimed_wait_common64 (libpthread.so.0 + 
0x15a8a)
#1  0x7f3c0217b2c0 pthread_cond_wait (libpthread.so.0 + 0xf2c0)
#2  0x7f3bfc296c43 thread_function (swrast_dri.so + 0x7b8c43)
#3  0x7f3bfc29653b impl_thrd_routine (swrast_dri.so + 0x7b853b)
#4  0x7f3c02175299 start_thread (libpthread.so.0 + 0x9299)
#5  0x7f3c0209d353 n/a (libc.so.6 + 0x100353)

Stack trace of thread 1040:
#0  0x7f3c02181a8a __futex_abstimed_wait_common64 (libpthread.so.0 + 
0x15a8a)
#1  0x7f3c0217b2c0 pthread_cond_wait (libpthread.so.0 + 0xf2c0)
#2  0x7f3bfc293edb lp_cs_tpool_worker (swrast_dri.so + 0x7b5edb)
#3  0x7f3bfc293e5b impl_thrd_routine (swrast_dri.so + 0x7b5e5b)
#4  0x7f3c02175299 start_thread (libpthread.so.0 + 0x9299)
#5  0x7f3c0209d353 n/a (libc.so.6 + 0x100353)

Stack trace of thread 1042:
#0  0x7f3c02181a8a __futex_abstimed_wait_common64 (libpthread.so.0 + 
0x15a8a)
#1  0x7f3c0217b2c0 pthread_cond_wait (libpthread.so.0 + 0xf2c0)
#2  0x7f3bfbc960db util_queue_thread_func (swrast_dri.so + 0x1b80db)
#3  0x7f3bfbc95b9b impl_thrd_routine (swrast_dri.so + 0x1b7b9b)
#4  0x7f3c02175299 start_thread (libpthread.so.0 + 0x9299)
#5  0x7f3c0209d353 n/a (libc.so.6 + 0x100353)

Stack trace of thread 1044:
#0  0x7f3c02181a8a __futex_abstimed_wait_common64 (libpthread.so.0 + 
0x15a8a)
#1  0x7f3c0217b2c0 pthread_cond_wait (libpthread.so.0 + 0xf2c0)
#2  0x7f3bfbc960db util_queue_thread_func (swrast_dri.so + 0x1b80db)
#3  0x7f3bfbc95b9b impl_thrd_routine (swrast_dri.so + 0x1b7b9b)
#4  0x7f3c02175299 start_thread (libpthread.so.0 + 0x9299)
#5  

Re: Random crashes/reboots under F32

[Łukasz Posadowski]

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 "random crashes" doesn't
> bring up anything particularly helpful.
> 
> Tips? Suggestions?

As George wrote, You can check all past reboots and shutdowns with
'last -x'. It is easier to browse the logs knowing the exact time.

-- 
Łukasz Posadowski
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Random crashes/reboots under F32

[George N. White III]

On Fri, 19 Jun 2020 at 10:43, Justin Moore  wrote:

> About four weeks ago I upgraded from F30 to F32. I've been using this same
> hardware for a few years now, and it worked fine* under multiple versions
> of Fedora.
>

> However since I upgraded to F32 I've been finding my system randomly
> rebooting about every 8-14 days. I'll just come back to it and it'll be
> sitting at the encrypted partition unlock screen. When I check system logs
> (journalctl -b [bootID] -r) there's no indication that something went
> horribly wrong. No error messages, no nothing. It's just fine until I'm
> staring at a reboot screen.
>

Start keeping a log.   For years I was going in to work 7 days a week to
babysit an unreliable system used to capture "irreplacable" data.   From
the logs I determined that the system never failed 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" or "random crashes" doesn't bring up anything
> particularly helpful.
>
> Tips? Suggestions?
>

"last" should show if you had an orderly shutdown or a crash.

There is a good reason that linux distros include a memory test -- use it.
Sometimes reseating memory cards is enough to get past a test failure.

After memory common old PC random crashes are due to bad cables,
connectors, or power supplies.   Particularly if you live in a hot, humid,
area (or take your PC to sea) you may find green corrosion on some
connections.   You can buy "contact enhancer" that is really helpful for
seagoing or ocean adjacent gear.   At my work we generally had a stack of
old PC's "all made out of ticky tacky. And they all look just the same…",
so I could swap cables and power supplies to keep a few running.   Before
retiring I managed a 7x24 industrial PC used to control a satellite dish.
Twice the system started having random crashes.  Inspection of the system
board revealed bulging capacitors.
<https://en.wikipedia.org/wiki/Capacitor_plague>   I bought a new MB and
replaced the bad capacitors on the original.   Then the new MB failed the
same way, so when I retired it was running on the repaired board.  That MB
supported a range of CPU clock speeds.  Normally I run 7x24 systems at the
lowest clock speed for longevity, but we were using time consuming software
decryption so the system used the fastest available CPU.


-- 
George N. White III
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Random crashes/reboots under F32

[Richard Shaw]

On Fri, Jun 19, 2020 at 8:43 AM Justin Moore 
wrote:

> About four weeks ago I upgraded from F30 to F32. I've been using this same
> hardware for a few years now, and it worked fine* under multiple versions
> of Fedora.
>
> However since I upgraded to F32 I've been finding my system randomly
> rebooting about every 8-14 days. I'll just come back to it and it'll be
> sitting at the encrypted partition unlock screen. When I check system logs
> (journalctl -b [bootID] -r) there's no indication that something went
> horribly wrong. No 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" and "random reboots" or "random crashes" doesn't bring up anything
> particularly helpful.
>
> Tips? Suggestions?
>

Purely a SWAG but newer kernels may either have a bug, or may be exposing a
problem which a previous kernel ignored or didn't trigger. For random stuff
like this I would look to see if there's a firmware update for your BIOS.

Thanks,
Richard
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Random crashes/reboots under F32

[Justin Moore]

About four weeks ago I upgraded from F30 to F32. I've been using this same
hardware for a few years now, and it worked fine* under multiple versions
of Fedora.

However since I upgraded to F32 I've been finding my system randomly
rebooting about every 8-14 days. I'll just come back to it and it'll be
sitting at the encrypted partition unlock screen. When I check system logs
(journalctl -b [bootID] -r) there's no indication that something went
horribly wrong. No 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" and "random reboots" or "random crashes" doesn't bring up anything
particularly helpful.

Tips? Suggestions?

Thanks in advance.
-justin

*Standard disclaimer about things like systemd and journalctl being an
absolute dumpster fire
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Pycharm repository package crashes on me

[Samuel Sieb]

On 6/1/20 1:20 PM, Anil Felipe Duggirala wrote:
I am new to Fedora, and am happy about it. I installed Fedora 32 and was 
offered to "install" third party repositories by the Software 
application. There is one repository included in this list, which 
contains the Pycharm IDE software. I have 2 questions:


1. What can you gain from installing from this repository? Considering 
this is a Java app, it basically requires its own customized JRE. And 
installing and running it (using the author's package) is as easy as 
unpacking an archive.


It can be installed system-wide.  All the files are managed by the 
package manager which lets you cleanly upgrade or remove it later.


2. As a follow up to the first question. What makes this particular 
repository special in being included in this list?


I'm curious about that as well.

I am complaining because I installed the app using this repository and 
it was crashing, requiring a hard reboot. Running or "installing" this 


That seems unlikely.  Can you provide more details?

app using the directly downloaded package works better. And installing 
using the repository could (probably does) make changes to your system 
Java installation.


No, that would be another benefit of using the Fedora packaging.  It 
will be setup to not mess up any other part of the Fedora installation.

___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Pycharm repository package crashes on me

[Anil Felipe Duggirala]

hello,

I am new to Fedora, and am happy about it. I installed Fedora 32 and was 
offered to "install" third party repositories by the Software 
application. There is one repository included in this list, which 
contains the Pycharm IDE software. I have 2 questions:


1. What can you gain from installing from this repository? Considering 
this is a Java app, it basically requires its own customized JRE. And 
installing and running it (using the author's package) is as easy as 
unpacking an archive.


2. As a follow up to the first question. What makes this particular 
repository special in being included in this list?


I am complaining because I installed the app using this repository and 
it was crashing, requiring a hard reboot. Running or "installing" this 
app using the directly downloaded package works better. And installing 
using the repository could (probably does) make changes to your system 
Java installation.


thank you,,

Anil
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: fedora 32 live DVD crashes

[George N. White III]

On Mon, 1 Jun 2020 at 01:23, Michael Hennebry <
henne...@web.cs.ndsu.nodak.edu> wrote:

> On Fri, 29 May 2020, George N. White III wrote:
>
> > Have you tried the vga= kernel boot parameter?   For Xwindows it would be
> > good to get something other than VESA running, either i915 or by adding a
> > graphics card.
>
> I have now.
> No go.
>
> > I had a look at the dmesg log on an old system with Nvidia card.   It was
> > set to display
> > the startup messages, which were initially at low res then switched to
> the
> > resolution of
> > the monitor.  The switch appears to occur when dmesg reports that nouveau
> > has started.
> > Have you looked in dmesg for any indication of why it doesn't load the
> i915
> > driver?
>
> It does load the i915 driver.
> [   60.044675] pci :00:00.0: detected 8192K stolen memory
> [   60.054985] checking generic (e000 7f) vs hw (f010 8)
> [   60.054987] checking generic (e000 7f) vs hw (e000 1000)
> [   60.054988] fb0: switching to inteldrmfb from VESA VGA
> [   60.065317] Console: switching to colour dummy device 80x25
> [   60.065381] i915 :00:02.0: vgaarb: deactivate vga console
> [   60.066924] [drm] ACPI BIOS requests an excessive sleep of 4022337523
> ms, using 1500 ms instead
> [   60.066933] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> [   60.066936] [drm] Driver supports precise vblank timestamp query.
> [   60.067241] i915 :00:02.0: vgaarb: changed VGA decodes:
> olddecodes=io+mem,decodes=io+mem:owns=io+mem
> [   60.084775] [drm] Initialized overlay support.
> [   60.086225] [drm] Initialized i915 1.6.0 20200114 for :00:02.0 on
> minor 0
> [   60.086456] ACPI: Video Device [GFX0] (multi-head: no  rom: yes  post:
> no)
> [   60.086568] input: Video Bus as
> /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12
> [   60.118670] fbcon: i915drmfb (fb0) is primary device
>

But the snippet from Xorg.0.log had:


[   109.570] (EE) Unable to find a valid framebuffer device
[   109.571] (EE) open /dev/fb0: No such file or directory
[   109.571] (EE) Screen 0 deleted because of no matching config section.



> [   60.163409] Console: switching to colour frame buffer device 180x56
> [   60.183707] i915 :00:02.0: fb0: i915drmfb frame buffer device
>

If you edit the options in the boot command line to remove what ever "rhgb
quiet" has morphed to you should see the first few lines in low res. and
then the 180x56 text output.   Have a look at
https://wiki.ubuntu.com/X/Troubleshooting/BlankScreen


> Is this bit from dmesg relevant?
> [0.676375] PCI: Using host bridge windows from ACPI; if necessary, use
> "pci=nocrs" and report a bug
> [0.677023] ACPI: Enabled 11 GPEs in block 00 to 3F
> [0.685546] ACPI: PCI Root Bridge [PCI0] (domain  [bus 00-ff])
> [0.68] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM
> ClockPM Segments MSI HPX-Type3]
> [0.685562] ACPI BIOS Error (bug): \_SB.PCI0._OSC: Excess arguments -
> ASL declared 5, ACPI requires 4 (20200110/nsarguments-160)
> [0.685616] ACPI BIOS Error (bug): Failure creating named object
> [\_SB.PCI0._OSC.CAPD], AE_ALREADY_EXISTS (20200110/dsfield-181)
> [0.685625] ACPI Error: Aborting method \_SB.PCI0._OSC due to previous
> error (AE_ALREADY_EXISTS) (20200110/psparse-529)
>

https://bugzilla.kernel.org/show_bug.cgi?id=198003  I've seen this before,
probably on boxes similar to yours.
https://access.redhat.com/solutions/58790 explains workarounds and
their consequences, also useful is
https://www.kernel.org/doc/html/v5.6/admin-guide/kernel-parameters.html


I'm calling it a night.
> Frustration is exhausting.
>

I was lucky that I didn't really need X11 to work on the similar boxes
(they ran lightweight batch processing
in a machine room and also managed the UPS's via serial ports).   Some
people actually repair the buggy BIOS:
https://forums.freebsd.org/threads/acpi-error-excess-arguments-asl-declared-5-acpi-requires-4.71283/
.


--
George N. White III
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: fedora 32 live DVD crashes

[Michael Hennebry]

On Fri, 29 May 2020, George N. White III wrote:


Have you tried the vga= kernel boot parameter?   For Xwindows it would be
good to get something other than VESA running, either i915 or by adding a
graphics card.


I have now.
No go.


I had a look at the dmesg log on an old system with Nvidia card.   It was
set to display
the startup messages, which were initially at low res then switched to the
resolution of
the monitor.  The switch appears to occur when dmesg reports that nouveau
has started.
Have you looked in dmesg for any indication of why it doesn't load the i915
driver?


It does load the i915 driver.
[   60.044675] pci :00:00.0: detected 8192K stolen memory
[   60.054985] checking generic (e000 7f) vs hw (f010 8)
[   60.054987] checking generic (e000 7f) vs hw (e000 1000)
[   60.054988] fb0: switching to inteldrmfb from VESA VGA
[   60.065317] Console: switching to colour dummy device 80x25
[   60.065381] i915 :00:02.0: vgaarb: deactivate vga console
[   60.066924] [drm] ACPI BIOS requests an excessive sleep of 4022337523 ms, 
using 1500 ms instead
[   60.066933] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   60.066936] [drm] Driver supports precise vblank timestamp query.
[   60.067241] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   60.084775] [drm] Initialized overlay support.
[   60.086225] [drm] Initialized i915 1.6.0 20200114 for :00:02.0 on minor 0
[   60.086456] ACPI: Video Device [GFX0] (multi-head: no  rom: yes  post: no)
[   60.086568] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12
[   60.118670] fbcon: i915drmfb (fb0) is primary device
[   60.163409] Console: switching to colour frame buffer device 180x56
[   60.183707] i915 :00:02.0: fb0: i915drmfb frame buffer device


Is this bit from dmesg relevant?
[0.676375] PCI: Using host bridge windows from ACPI; if necessary, use 
"pci=nocrs" and report a bug
[0.677023] ACPI: Enabled 11 GPEs in block 00 to 3F
[0.685546] ACPI: PCI Root Bridge [PCI0] (domain  [bus 00-ff])
[0.68] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM 
Segments MSI HPX-Type3]
[0.685562] ACPI BIOS Error (bug): \_SB.PCI0._OSC: Excess arguments - ASL 
declared 5, ACPI requires 4 (20200110/nsarguments-160)
[0.685616] ACPI BIOS Error (bug): Failure creating named object 
[\_SB.PCI0._OSC.CAPD], AE_ALREADY_EXISTS (20200110/dsfield-181)
[0.685625] ACPI Error: Aborting method \_SB.PCI0._OSC due to previous error 
(AE_ALREADY_EXISTS) (20200110/psparse-529)


I'm calling it a night.
Frustration is exhausting.

--
Michael   henne...@web.cs.ndsu.nodak.edu
"Even if it could be powered by Elon Musk's ego, ..."  --- I. Forget
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: fedora 32 live DVD crashes

[Michael Hennebry]

On Fri, 29 May 2020, George N. White III wrote:


Have you tried the vga= kernel boot parameter?   For Xwindows it would be
good to get something other than VESA running, either i915 or by adding a
graphics card.


I'll try that next,
though the problem seems to be that a power that be
seems to think I only have a 640x480 screen.
Vesa finds larger modes.


I had a look at the dmesg log on an old system with Nvidia card.   It was
set to display
the startup messages, which were initially at low res then switched to the
resolution of
the monitor.  The switch appears to occur when dmesg reports that nouveau
has started.
Have you looked in dmesg for any indication of why it doesn't load the i915
driver?


I'll try.



https://www.kernel.org/doc/html/latest/gpu/i915.html says: "The drm/i915
driver supports all (with the exception of some very early models)
integrated GFX chipsets with both Intel display and rendering blocks."   It
is possible that your system is one of those "very early models", or that
the kernel developers removed support for some not quite as early models.
The driver also needs a .bin
firmware file.  I have had problems with other hardware when upstream
omitted the firmware files
needed by old hardware.


I have the latest and greatest firmware.

--
Michael   henne...@web.cs.ndsu.nodak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
 --  someeecards
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: fedora 32 live DVD crashes

[George N. White III]

On Fri, 29 May 2020 at 10:56, Michael Hennebry <
henne...@web.cs.ndsu.nodak.edu> wrote:

> For whatever reason,
> the persistent overlay does not work for me.
>
> I can get to runlevel 3 with or without nomodeset.
> With nomodeset,
> telinit 5
> brings me to 640x480 .
> Without nomodeset, it fails:
> the oh no screen rears its ugly head.
>
> Is there something I can do at runlevel 3
> to get a mode other than 640x480 ?
>

Have you tried the vga= kernel boot parameter?   For Xwindows it would be
good to get something other than VESA running, either i915 or by adding a
graphics card.

>
> Is there something that will change xrandr's
> idea of the screen size?
>

I had a look at the dmesg log on an old system with Nvidia card.   It was
set to display
the startup messages, which were initially at low res then switched to the
resolution of
the monitor.  The switch appears to occur when dmesg reports that nouveau
has started.
Have you looked in dmesg for any indication of why it doesn't load the i915
driver?

https://www.kernel.org/doc/html/latest/gpu/i915.html says: "The drm/i915
driver supports all (with the exception of some very early models)
integrated GFX chipsets with both Intel display and rendering blocks."   It
is possible that your system is one of those "very early models", or that
the kernel developers removed support for some not quite as early models.
 The driver also needs a .bin
firmware file.  I have had problems with other hardware when upstream
omitted the firmware files
needed by old hardware.

-- 
George N. White III
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: fedora 32 live DVD crashes

[Michael Hennebry]

For whatever reason,
the persistent overlay does not work for me.

I can get to runlevel 3 with or without nomodeset.
With nomodeset,
telinit 5
brings me to 640x480 .
Without nomodeset, it fails:
the oh no screen rears its ugly head.

Is there something I can do at runlevel 3
to get a mode other than 640x480 ?

Is there something that will change xrandr's
idea of the screen size?

--
Michael   henne...@web.cs.ndsu.nodak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
 --  someeecards
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: fedora 32 live DVD crashes

[Michael Hennebry]

On Thu, 28 May 2020, Michael Hennebry wrote:


On Thu, 28 May 2020, Samuel Sieb wrote:

I don't recall you mentioning which live image you're using.  Assuming it's 
workstation, edit /etc/gdm/custom.conf and uncomment the line with 
"WaylandEnable=false".  Then reboot and see what happens.


'Twas only in the first post:
On Sun, 24 May 2020, Michael Hennebry wrote:


I've trying to run Fedora-Workstation-Live-x86_64-32-1.6.iso
on my HP Compac dc5800 Small Form Factor.


Alas when I boot, I get the message
Unable to find persistent overlay; using temporary one.


I tried booting to runlevel 3,
editing custom.conf and telinit 5 .
Without nomodeset , it gave me the Oh no ssscreen.

--
Michael   henne...@web.cs.ndsu.nodak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
 --  someeecards
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: fedora 32 live DVD crashes

[Michael Hennebry]

On Thu, 28 May 2020, Samuel Sieb wrote:

I don't recall you mentioning which live image you're using.  Assuming it's 
workstation, edit /etc/gdm/custom.conf and uncomment the line with 
"WaylandEnable=false".  Then reboot and see what happens.


'Twas only in the first post:
On Sun, 24 May 2020, Michael Hennebry wrote:


I've trying to run Fedora-Workstation-Live-x86_64-32-1.6.iso
on my HP Compac dc5800 Small Form Factor.


Alas when I boot, I get the message
Unable to find persistent overlay; using temporary one.

I'd used the following command and had gotten the ok:
[root@localhost-live ~]# livecd-iso-to-disk --format --msdos --overlay-size-mb 
1024 *.iso /dev/sdc

Grrr.

--
Michael   henne...@web.cs.ndsu.nodak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
 --  someeecards
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: fedora 32 live DVD crashes

[Samuel Sieb]

On 5/28/20 1:16 PM, Michael Hennebry wrote:

On Tue, 26 May 2020, Samuel Sieb wrote:

livecd-iso-to-disk --format --msdos --overlay-size-mb 1024 
Fedora-Workstation-Live-x86_64-32-1.2.iso /dev/sdd


Replace the sdd with your USB drive, this will completely wipe the 
drive. Put the name of whatever iso image you're using instead of the 
workstation one. The 1024 makes a 1GB overlay.  When you boot that 
drive, any changes you make will be persistent.  You can install 
packages, change configs, whatever you want, up to 1GB of changes. 
There's also an option to create a home partition as well, optionally 
encrypted, but you don't need that right now. For now, the /home 
directory will be part of the overlay.


Done that.
I suppose now I need to boot and
figure out the changes I need to make.


I don't recall you mentioning which live image you're using.  Assuming 
it's workstation, edit /etc/gdm/custom.conf and uncomment the line with 
"WaylandEnable=false".  Then reboot and see what happens.

___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: fedora 32 live DVD crashes

[Michael Hennebry]

On Tue, 26 May 2020, Samuel Sieb wrote:

livecd-iso-to-disk --format --msdos --overlay-size-mb 1024 
Fedora-Workstation-Live-x86_64-32-1.2.iso /dev/sdd


Replace the sdd with your USB drive, this will completely wipe the drive. 
Put the name of whatever iso image you're using instead of the workstation 
one. The 1024 makes a 1GB overlay.  When you boot that drive, any changes you 
make will be persistent.  You can install packages, change configs, whatever 
you want, up to 1GB of changes. There's also an option to create a home 
partition as well, optionally encrypted, but you don't need that right now. 
For now, the /home directory will be part of the overlay.


Done that.
I suppose now I need to boot and
figure out the changes I need to make.

--
Michael   henne...@web.cs.ndsu.nodak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
 --  someeecards
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: fedora 32 live DVD crashes

[Michael Hennebry]

On Wed, 27 May 2020, George N. White III wrote:


https://www.systutorials.com/configuration-of-linux-kernel-video-mode/
has an incantation (from 2015) to display available video modes.


Got it.
vbeinfo notices several resolutions at at least two resolutions each:
1920 x 1440 at 8 or 16 bits
1600 x 1200, 1280 x 1024, 1024 x 768 and 640 x 480 at 8, 16 or 32 bits
It claims that 1440 x 900 is the preferred mode,
but gives no mode number.
Note that the first three modes are larger than 1140 x 900.

--
Michael   henne...@web.cs.ndsu.nodak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
 --  someeecards
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: fedora 32 live DVD crashes

[Michael Hennebry]

I now have live-cd-tools.
They and the tutorial website will have to wait until tomorrow.

--
Michael   henne...@web.cs.ndsu.nodak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
 --  someeecards
___
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: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org