Installing MS Edge Browser

2024-07-26 Thread Jonathan Ryshpan
I am trying to install the MS Edge Browser (to access a web site that
doesn't work properly under Firefox or Chrome of the KDE native
browser). The installation fails when I attempt to install the repo, as
follows:
   # curl -v https://packages.microsoft.com/keys/ -oedgeKeys
   # vi edgeKeys
   # rpm --import edgeKeys
   error: edgeKeys-ed: key 1 not an armored public key.

The "vi" step is to get a line-feed at the end of the key; I have read
that a missing line-feed can cause this problem. The same problem
happens without the "vi".

Does anyone know how to install the MS Edge repo, or to install Edge in
some other way?

System is:
   Operating System: Fedora Linux 39
   KDE Plasma Version: 5.27.11
   KDE Frameworks Version: 5.115.0
   Qt Version: 5.15.13
   Kernel Version: 6.9.10-100.fc39.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 

 Three percent exceeds 2 percent by 50 percent, 
 not by 1 percent.
 --Edward Denison
-- 
___
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: Can't log in to graphical workstation

2023-11-15 Thread Jonathan Ryshpan
On Wed, 2023-11-15 at 22:26 +1000, Michael D. Setzer II wrote:
> Now I understand, it is the local graphic login that is not working?
> 1. Did you install the server install on tis machine or the
> workstation one?
> Think the server installation doesn't install the gui by default. 
> Did that once to see what it did, and without the gui it was not
> usefull.
> 2. In you login to a terminal window. run systemctl status gdm and see
> what it reports.

Since I run kde, the display manager is actually sddm, and systemctl
gives very interesting info. Some research shows that a package is
missing, namely plasma-workspace-x11. Installing it cures things. The
problem actually arose in Fedora 38 (I have no idea how.); I upgraded to
Fedora 39 to see if this would cure the problem, but since plasma-
workspace-x11 was missing from 38, it stayed missing in 39.

$ systemctl status sddm.service  
● sddm.service - Simple Desktop Display Manager
Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled;
preset: enabled)
   Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Wed 2023-11-15 03:09:44 PST; 8h ago
  Docs: man:sddm(1)
man:sddm.conf(5)
  Main PID: 1125 (sddm)
 Tasks: 2 (limit: 9302)
Memory: 20.1M
   CPU: 71ms
CGroup: /system.slice/sddm.service
└─1125 /usr/bin/sddm


Nov 15 03:09:44 OaklandWeather.localdomain systemd[1]: Started
sddm.service - Simple Desktop Display Manager.
Nov 15 03:09:45 OaklandWeather.localdomain sddm[1125]: Unable to find
autologin session entry "plasma"

Nov 15 03:09:45 OaklandWeather.localdomain sddm[1125]: Autologin failed!

Nov 15 03:09:45 OaklandWeather.localdomain sddm[1125]: The configured
theme "01-breeze-fedora" doesn't exist, using the embedded theme instead

Nov 15 03:09:45 OaklandWeather.localdomain sddm-helper[1164]:
pam_unix(sddm-greeter:session): session opened for user sddm(uid=988) by
(uid=0)
Nov 15 10:46:36 OaklandWeather.localdomain sddm[1125]: Invalid session
""

-- 
Many Thanks - 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: Can't log in to graphical workstation

2023-11-15 Thread Jonathan Ryshpan
On Wed, 2023-11-15 at 10:17 +, Barry wrote:
> > On 15 Nov 2023, at 09:03, Jonathan Ryshpan 
> > wrote:
> > I can no longer log in to the machine remotely via ssh
> 
> Over time the security of ssh is improved as cryptography research
> recommends.
> If are using an old version of ssh to connect that may be the problem.
> If you have a weak ssh key that may the be the problem.

This got better after a while for no apparent reason. I suspect that the
dns server for my local net did not recognize the upgraded machine for a
while, but then started to when something timed out. Ssh is working, and
also the machine (a server) is now visible. Thanks for your help.

-- 
Sincerely Jonathan Ryshpan 

 Procrastinators do it later.
___
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: Can't log in to graphical workstation

2023-11-15 Thread Jonathan Ryshpan
On Wed, 2023-11-15 at 20:15 +1000, Michael D. Setzer II wrote:
> Note sure what graphic login you are referring to?
> I have used tigervnc up to Fedora 38, but found that there are 
> issues with 39, so have switch to TurboVNC.
The "graphic login" is the plain ordinary login screen that appears when
the computer starts up.


-- 
Sincerely Jonathan Ryshpan 

 Those who have put out the eyes of the people
 reproach them for their blindness. -- Milton
___
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


Can't log in to graphical workstation

2023-11-15 Thread Jonathan Ryshpan
I am not able to log in as a graphical user on one of my workstations.
The login screen works normally, except that:
 * The "Session" box is empty
 * The "Layout" box reads "??zz" (?? is blue)
When I type my password and hit return, nothing happens.
I can run a terminal session (CTRL+ALT F2) OK, but $startx fails.

This started to happen on Fedora 38. I (foolishly) upgraded to Fedora
39, which only made things worse: I can no longer log in to the machine
remotely via ssh. Currently running Fedora 39 with all upgrades
installed.

Any ideas on what's going on or how to investigate?

-- 
Sincerely Jonathan Ryshpan  The most perilous
moment for a bad government is when it seeks to mend its ways.” --Alexis
de Tocqueville
___
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


Web page doesn't display (Trouble with javascript?)

2023-11-06 Thread Jonathan Ryshpan
Can anyone display this page:
   https://eclipse.gsfc.nasa.gov/SEgoogle/SEgoogle2001/SE2024Apr08Tgoogle.html
The text claims the page contains a map of the April 2024 eclipse, but
no such thing appears on the screen.

System Info:
   Firefox 119.0 (64-bit)
   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.9-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 

 I've learned that you can tell a lot about 
 a person by the way they handle these three 
 things:
 a rainy day, 
 lost luggage, 
 and tangled Christmas tree lights.
 --Maya Angelou
___
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

2023-10-07 Thread 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.system

Firefox crashes when started from the panel

2023-10-07 Thread 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 system

System upgrade verification

2023-05-17 Thread Jonathan Ryshpan
To upgrade from Fedora-37 to Fedora-38 the instructions
(https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/) sa
y:
   ...
   5. When the new GPG key is imported, you are asked to verify the key’s
   fingerprint. Refer to https://getfedora.org/security to do so.
Which  never happened. I have continued with the upgrade. Is this safe?

-- 
Sincerely Jonathan Ryshpan 

 Procrastinators do it later.
___
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: Messages held for moderation.

2023-05-04 Thread Jonathan Ryshpan
On Thu, 2023-05-04 at 17:42 -0400, Todd Zullinger wrote:
> Jonathan Ryshpan wrote:
> > I have two messages held for moderation, each reported with the
> > following message. One of them is 53,454 bytes, the other is  44,018
> > bytes. What's going on?
> > 
> > I would not normally trouble the list about this, but they have been
> > pending for two days and there seems to be no way to reach the
> > moderator.
> 
> Sorry for the delay.
> 
> If we could, we'd probably have the list reject instead of
> hold, as there's generally not much chance we will approve
> large messages.  But that's not something we can configure
> at the list admin level in mailman (AFAIK).
> 
> It's better to trim the output than wait for the messages to
> be approved or rejected.
> 
> The list owners / moderators can be reached via the
> ${list}-ow...@lists.fedoraproject.org.  The list info page
> does include this information.

I see; the headers to your last message amount to about 10 Kbytes. But I
would have expected that even with headers, a message of about 44 Kbytes
would be under 60 Kbytes. I already trimmed the text size down from
about 53 Kbytes to abpit 44 Kbytes.

I guess a message of more than about 30 Kbytes of text should not be
expected to go through. In the future I will save long files to Google
Docs and send a link. Bother!


-- 
Sincerely Jonathan Ryshpan 

Never attribute to malice that which is adequately explained by
stupidity.
 -- Hanlon's razor
___
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


Messages held for moderation.

2023-05-04 Thread Jonathan Ryshpan
I have two messages held for moderation, each reported with the
following message. One of them is 53,454 bytes, the other is  44,018
bytes. What's going on?

I would not normally trouble the list about this, but they have been
pending for two days and there seems to be no way to reach the
moderator.

 Forwarded Message 
From: users-boun...@lists.fedoraproject.org
To: jonr...@pacbell.net
Subject: Your message to users@lists.fedoraproject.org awaits moderator
approval
Date: 05/02/2023 12:08:56 PM

Your mail to 'users@lists.fedoraproject.org' with the subject
    Re: Systemd Unit Fails at Boot, but Succeeds when Started from the
Console
Is being held until the list moderator can review it for approval.
The message is being held because:
    The message is larger than the 60 KB maximum size

Either the message will get posted to the list, or you will receive 
notification of the moderator's decision.

-- 
Sincerely Jonathan Ryshpan 

 Necessity is the excuse for every infringement of 
 human freedom. It is the argument of the tyrant 
 and the creed of the slave. -- Wm. Pitt the Elder
___
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: How to get system info

2023-05-03 Thread Jonathan Ryshpan
On Wed, 2023-05-03 at 13:50 -0300, George N. White III wrote:
> Is there some way to get this info from the console, for machines
> running remotely, typically connected via ssh? I am tired of running
> to a remote machine to run kinfocenter on it.
...
> % neofetch --off --color_blocks off @


Very nice.

-- 
Thanks - Jonathan Ryshpan 

 The Website you seek
 Cannot be located, but
 Countless more exist.
___
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


How to get system info

2023-05-03 Thread Jonathan Ryshpan
I get the system info shown at the bottom of this message by running
   kinfocenter -> Copy to Clipboard
Is there some way to get this info from the console, for machines
running remotely, typically connected via ssh? I am tired of running to
a remote machine to run kinfocenter on it.

System Info:
   Operating System: Fedora Linux 37
   KDE Plasma Version: 5.27.4
   KDE Frameworks Version: 5.105.0
   Qt Version: 5.15.9
   Kernel Version: 6.2.13-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 

 Though a program be but three lines long,
 someday it will have to be maintained.
 -- The Tao of Programming
___
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: Systemd Unit Fails at Boot, but Succeeds when Started from the Console

2023-05-01 Thread Jonathan Ryshpan
On Sun, 2023-04-30 at 16:41 -0500, Chris Adams wrote:
> Once upon a time, Jonathan Ryshpan  said:
> > This unit 
> >    $ cat /etc/systemd/system/noip-duc.service  
> >    [Unit]
> >    Description=No-IP Dynamic Update Client
> >    After=network.target auditd.service
> 
> This should probably be network-online.target.
> 
> > always fails at boot time with the message status=2/INVALIDARGUMENT
> 
> That's the exit code from the program.  It is probably the return code
> from a system call made within the program, not in response to some  
>  command-line argument.  But if the program runs before the network is
> up and doesn't handle waiting, that's the most likely culprit.

A very plausible theory. I was sure this would fix the problem; but it
is not so. I edited /etc/systemd/system/noip-duc.service as you
recommend.
   The file noip-duc.service has been edited to change  
      After=network.target auditd.service
   to
      After=network-online.target auditd.service

And the problem remains. Further advice would be welcome.

-- 
Sincerely Jonathan Ryshpan 

 Common sense is the collection of prejudices
 acquired by the age of eighteen. -- Einstein
___
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


Systemd Unit Fails at Boot, but Succeeds when Started from the Console

2023-04-30 Thread Jonathan Ryshpan
This unit 
   $ cat /etc/systemd/system/noip-duc.service  
   [Unit]
   Description=No-IP Dynamic Update Client
   After=network.target auditd.service
   
   [Service]
   EnvironmentFile=/etc/sysconfig/noip-duc
   ExecStart=/usr/local/bin/noip-duc
   Restart=on-failure
   Type=simple
   
   [Install]
   WantedBy=multi-user.target
always fails at boot time with the message status=2/INVALIDARGUMENT

Here is an extract from the system log (a fuller extract is attached):
   Mar 18 07:57:56 OaklandWeather.localdomain systemd[1]: Started noip-
   duc.service - No-IP Dynamic Update Client.
   Mar 18 07:57:58 OaklandWeather.localdomain systemd[1]: noip-duc.service:
   Main process exited, code=exited, status=2/INVALIDARGUMENT
   Mar 18 07:57:58 OaklandWeather.localdomain systemd[1]: noip-duc.service:
   Failed with result 'exit-code'.
   Mar 18 07:57:58 OaklandWeather.localdomain systemd[1]: noip-duc.service:
   Scheduled restart job, restart counter is at 1.
   Mar 18 07:57:58 OaklandWeather.localdomain systemd[1]: Stopped noip-
   duc.service - No-IP Dynamic Update Client.
   Mar 18 07:57:58 OaklandWeather.localdomain systemd[1]: Started noip-
   duc.service - No-IP Dynamic Update Client.
   Mar 18 07:57:58 OaklandWeather.localdomain systemd[1]: noip-duc.service:
   Main process exited, code=exited, status=2/INVALIDARGUMENT
   Mar 18 07:57:58 OaklandWeather.localdomain systemd[1]: noip-duc.service:
   Failed with result 'exit-code'.
   Mar 18 07:57:58 OaklandWeather.localdomain systemd[1]: noip-duc.service:
   Scheduled restart job, restart counter is at 2.
   
However if the unit is started from the console after the boot process
is complete:
   $ systemctrl start noip-duc.service
it succeeds.
How can I find out what the argument is with which systemd is invoking
noip-duc, so I can understand why it is invalid at boot time but valid
when the unit is started afterwards from the console? I would simply
recompile it to output this, but noip-duc is written in the rust
programming language, which I to lazy to learn for this one application.

-- 
Sincerely Jonathan Ryshpan 

 We dance around in a ring and suppose
 But the secret sits in the center and knows.
 - Robert Frost
Mar 18 07:57:56 OaklandWeather.localdomain audit[1]: SERVICE_START pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=noip-duc comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? 
addr=? terminal=? res=success'
Mar 18 07:57:58 OaklandWeather.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=noip-duc comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? 
addr=? terminal=? res=failed'
Mar 18 07:57:58 OaklandWeather.localdomain audit[1]: SERVICE_START pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=noip-duc comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? 
addr=? terminal=? res=success'
Mar 18 07:57:58 OaklandWeather.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=noip-duc comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? 
addr=? terminal=? res=success'
Mar 18 07:57:58 OaklandWeather.localdomain audit[1]: SERVICE_START pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=noip-duc comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? 
addr=? terminal=? res=success'
Mar 18 07:57:58 OaklandWeather.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=noip-duc comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? 
addr=? terminal=? res=failed'
Mar 18 07:57:58 OaklandWeather.localdomain audit[1]: SERVICE_START pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=noip-duc comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? 
addr=? terminal=? res=success'
Mar 18 07:57:58 OaklandWeather.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=noip-duc comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? 
addr=? terminal=? res=success'
Mar 18 07:57:58 OaklandWeather.localdomain audit[1]: SERVICE_START pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=noip-duc comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? 
addr=? terminal=? res=success'
Mar 18 07:57:58 OaklandWeather.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 
msg='unit=noip-duc comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? 
addr=? terminal=? res=failed'
Mar 18 07:57:58 OaklandWeather.localdomain audit[1]: SERVICE_START p

Re: Running VirtualBox Crashes Other Apps

2023-04-11 Thread 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

2023-04-11 Thread 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

2023-04-11 Thread 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

2023-04-11 Thread 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


Running VirtualBox Crashes Other Apps

2023-04-10 Thread 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: UEFI Upgrade Fails

2023-04-08 Thread Jonathan Ryshpan
On Sat, 2023-04-08 at 20:03 -0700, Samuel Sieb wrote:
> > > > It looks like there is a new version of the UEFI boot system,
> > > > which 
> > > > can't be installed because of signature issues. Is this correct?
> > > > Is 
> > > > it anything to worry about? Can anything be done to fix the
> > > > issue? Is 
> > > > the issue likely to be fixed upstream?
> > > 
> > > I don't use Discover. I use fwupdmgr directly. I have not seen
> > > fwupdmgr refuse to update a component (sans no UEFI). Here's the
> > > relevant piece of the script I run daily:
> > > 
> > > if command -v fwupdmgr >/dev/null 2>&1 ; then
> > >     if fwupdmgr get-devices 2>&1 | grep -q -c 'UEFI ESRT device' ;
> > > then
> > >     echo "Updating firmware"
> > >     fwupdmgr refresh --force 1>/dev/null && \
> > >     fwupdmgr update 1>/dev/null
> > >     fi
> > > fi
> > > 
> > > I also noticed the db was updated today.
> > 
> > Very interesting. After running by hand the parts of your script
> > that 
> > test whether an update is necessary (It is.), I ran the actual
> > update 
> > and got the following output. As you see, I replied "n"; would it be
> > dangerous to try "Y"?
> 
> That sounds quite safe.  Do you even use any software from those 
> companies?  (Things that boot directly.)
One of them may be the author my system's firmware. I don't know who
wrote it.

> > BTW: I've been seeing the error message for about a week.
> 
> 
> What error message?

The following message. I should have written "warning" rather than
"error".

$ fwupdmgr update 
Devices with no available firmware updates:  
• System Firmware 
• WDC WD2005FBYZ-01YCBB2 
• WDC WD20EFRX-68EUZN0 
╔═══
═══╗ 
║ Upgrade UEFI dbx from 217 to 220?
   ║ 
╠═══
═══╣ 
║ Insecure versions of software from Trend Micro, vmware, CPSD,
Eurosoft, and  ║ 
║ New Horizon Datasys Inc were added to the list of forbidden signatures
due   ║ 
║ to discovered security problems. This updates the dbx to the latest
release  ║ 
║ from Microsoft.
 ║ 
║

 ║ 
║ Before installing the update, fwupd will check for any affected
executables  ║ 
║ in the ESP and will refuse to update if it finds any boot binaries
signed    ║ 
║ with any of the forbidden signatures.
   ║ 
║

 ║ 
╚═══
═══╝ 
Perform operation? [Y|n]: n 
Request canceled


-- 
Sincerely Jonathan Ryshpan 

 The Website you seek
 Cannot be located, but
 Countless more exist.
___
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: UEFI Upgrade Fails

2023-04-08 Thread Jonathan Ryshpan
On Sat, 2023-04-08 at 21:32 -0400, Jeffrey Walton wrote:
> On Sat, Apr 8, 2023 at 9:08 PM Jonathan Ryshpan 
> wrote:
> > 
> > Discover, which I use for upgrades, reports problems with UEFI.
> > There is an update, which Discover refuses to install. Discover
> > reports this message:
> > 
> > UEFI DBX : Version 217 : Released on 4/8/23
> > 
> > UEFI Secure Boot Forbidden Signature Database
> > 
> > Insecure versions of software from Trend Micro, vmware, CPSD,
> > Eurosoft, and New Horizon Datasys Inc were added to the list of
> > forbidden signatures due to discovered security problems. This
> > updates the dbx to the latest release from Microsoft.
> > Before installing the update, fwupd will check for any affected
> > executables in the ESP and will refuse to update if it finds any
> > boot binaries signed with any of the forbidden signatures.
> > ...
> > 
> > It looks like there is a new version of the UEFI boot system, which
> > can't be installed because of signature issues. Is this correct? Is
> > it anything to worry about? Can anything be done to fix the issue?
> > Is the issue likely to be fixed upstream?
> 
> I don't use Discover. I use fwupdmgr directly. I have not seen
> fwupdmgr refuse to update a component (sans no UEFI). Here's the
> relevant piece of the script I run daily:
> 
> if command -v fwupdmgr >/dev/null 2>&1 ; then
>     if fwupdmgr get-devices 2>&1 | grep -q -c 'UEFI ESRT device' ;
> then
>     echo "Updating firmware"
>     fwupdmgr refresh --force 1>/dev/null && \
>     fwupdmgr update 1>/dev/null
>     fi
> fi
> 
> I also noticed the db was updated today.

Very interesting. After running by hand the parts of your script that
test whether an update is necessary (It is.), I ran the actual update
and got the following output. As you see, I replied "n"; would it be
dangerous to try "Y"?

BTW: I've been seeing the error message for about a week.

$ fwupdmgr update
Devices with no available firmware updates:  
• System Firmware
• WDC WD2005FBYZ-01YCBB2
• WDC WD20EFRX-68EUZN0
╔═══
═══╗
║ Upgrade UEFI dbx from 217 to 220?
   ║
╠═══
═══╣
║ Insecure versions of software from Trend Micro, vmware, CPSD,
Eurosoft, and  ║
║ New Horizon Datasys Inc were added to the list of forbidden signatures
due   ║
║ to discovered security problems. This updates the dbx to the latest
release  ║
║ from Microsoft.
 ║
║

 ║
║ Before installing the update, fwupd will check for any affected
executables  ║
║ in the ESP and will refuse to update if it finds any boot binaries
signed    ║
║ with any of the forbidden signatures.
       ║
║

 ║
╚═══
═══╝
Perform operation? [Y|n]: n
Request canceled



-- 
Sincerely Jonathan Ryshpan 

 Ever wonder why the SAME PEOPLE make up ALL the 
 conspiracy theories?
___
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


UEFI Upgrade Fails

2023-04-08 Thread Jonathan Ryshpan
Discover, which I use for upgrades, reports problems with UEFI. There is
an update, which Discover refuses to install. Discover reports this
message:

   UEFI DBX : Version 217 : Released on 4/8/23
   
   UEFI Secure Boot Forbidden Signature Database
   
   Insecure versions of software from Trend Micro, vmware, CPSD, Eurosoft,
   and New Horizon Datasys Inc were added to the list of forbidden
   signatures due to discovered security problems. This updates the dbx to
   the latest release from Microsoft.
   Before installing the update, fwupd will check for any affected
   executables in the ESP and will refuse to update if it finds any boot
   binaries signed with any of the forbidden signatures.
   ...

It looks like there is a new version of the UEFI boot system, which
can't be installed because of signature issues. Is this correct? Is it
anything to worry about? Can anything be done to fix the issue? Is the
issue likely to be fixed upstream?

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 

 Common sense is the collection of prejudices
 acquired by the age of eighteen. -- Einstein
___
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: Start Screen Saver but Don't Lock Screen

2023-02-23 Thread Jonathan Ryshpan
On Wed, 2023-02-22 at 23:20 -0800, Jonathan Ryshpan wrote:
> How can I set my system up to start a screen saver after (say) 20
> minutes, but never lock the screen.

On Thu, 2023-02-23 at 00:34 -0700, Joe Zeff wrote:
> On the bottom left of the Display Modes tab of Xscreensaver
> Preferences, there's a check box labeled Lock Screen After.  If it's
> checked,uncheck it.  If you're not  using Xscreensaver, you should
> have said so.
I am running the standard screen-lock/screen-saver function that comes
with KDE. Maybe it would be better to install xscreensaver, however the
KDE standard controls are integrated with the rest of the KDE system,
which seems to argue for keeping things as they are.

On Thu, 2023-02-23 at 18:56 +1030, Tim via users wrote:
> My guess would be to look at the screen locking preferences, rather
> than the screensaver choices.  Related, but separate actions.

The only controls that I can find which KDE provides for screen locking
or saving are in: 
Start->System Settings->Workspace Behavior->Screen Lockingan image of 
which is attached. There seems to be nothing for screen
saving as such. I had thought that doing this would be extremely easy,
but it seems not to be so.

-- 
Sincerely Jonathan Ryshpan 

 The Website you seek
 Cannot be located, but
 Countless more exist.
___
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


Start Screen Saver but Don't Lock Screen

2023-02-22 Thread Jonathan Ryshpan
How can I set my system up to start a screen saver after (say) 20
minutes, but never lock the screen?

System info:
  Operating System: Fedora Linux 37
  KDE Plasma Version: 5.26.5
  KDE Frameworks Version: 5.103.0
  Qt Version: 5.15.8
  Kernel Version: 6.1.11-200.fc37.x86_64 (64-bit)
  Graphics Platform: Wayland
  Processors: 2 × Intel® Pentium® CPU G2030 @ 3.00GHz
  Memory: 7.6 GiB of RAM
  Graphics Processor: Mesa Intel® HD Graphics 2500
  Manufacturer: Dell Inc.
  Product Name: Inspiron 660s
  

-- 
Thanks - Jonathan Ryshpan 

 Ring the bells that still can ring
 Forget your perfect offering
 There is a crack ... in everything
 That's how the light gets in.
 -- Leonard Cohen - Anthem
___
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: /run/media

2022-12-27 Thread Jonathan Ryshpan
On Tue, 2022-12-27 at 13:53 -0800, Samuel Sieb wrote:

> On 12/27/22 13:35, Amadeus WM via users wrote:
> > 
> > > You could check the "don't prompt or run programs" checkbox, but
> > > that
> > > will apply to all devices.  You might be able to create a udev
> > > rule to
> > > isolate that specific device.
> > 
> > That's right, and I didn't mention this in the original post. I
> > would only
> > want to not mount that one specific drive. Other usb thumbdrives and
> > such
> > should be auto mounted to /run/media. Is it even possible?
> 
> It looks like if you add it to /etc/fstab, then Gnome auto-mounting 
> won't touch it.

Almost surely true. I had exactly the same problem with a USB mounted
hard drive. I put an entry for it into /etc/fstab and have had no
problems..

$ cat /etc/fstab
...
LABEL=Rosewill /srv/Rosewill/ ext4 nofail,defaults 

-- 
Sincerely Jonathan Ryshpan 

 The mind is not a vessel to be filled; it is 
 a fire to be kindled. -- Plutarch 
___
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: Lost NFS Export

2022-12-24 Thread Jonathan Ryshpan
On Tue, 2022-11-08 at 08:12 -0800, Doug Herr wrote:
> On Mon, Nov 7, 2022, at 9:08 AM, Jonathan Ryshpan wrote:
> > The machine *OaklandWeather* is set up to export some directories to
> > the machine *amito*. But when OaklandWeather is restarted the export
> > is 
> > lost. Running "# exportfs -a" restores the export and the desired
> > files 
> > can be seen by amito.
> > 
> > Some Details:
> > root@OaklandWeather# cat /etc/exports
> > # /etc/exportfs created by Jon : Fri 2021-11-05 02:33:51 PM PDT 
> > # edited by Jon : Tue Nov 16 10:30:08 AM PST 2021
> > # / amito(rw,no_subtree_check,no_root_squash)
> > / amito(rw)
> > /home amito(rw)
> > 
> > The problem seems to happen because nfs is started before amito can
> > be 
> > resolved:
> 
> Do you have "NetworkManager-wait-online.service" enabled?
> Not sure if this would fix it, but it *seems* like it should.

I believe that I do. Here is the result of a query:
$  systemctl status NetworkManager-wait-online.service
● NetworkManager-wait-online.service - Network Manager Wait Online
Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-
online.service; enabled; preset: enabled)
Active: active (exited) since Wed 2022-12-21 08:25:36 PST; 2 days
ago
  Docs: man:nm-online(1)
   Process: 1278 ExecStart=/usr/bin/nm-online -s -q (code=exited,
status=0/SUCCESS)
  Main PID: 1278 (code=exited, status=0/SUCCESS)
   CPU: 45ms


BTW: I have adopted the suggestion of Tom Horsley to put "amito" in
/etc/hosts, which seems to work well. However this could fail if my dns
server changes amito's IP address -- unlikely but possible. I apologize
for the late reply.
-- 
Sincerely Jonathan Ryshpan 

 The object of computation is not numbers
 but understanding. -- Hamming
___
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


Lost NFS Export

2022-11-07 Thread Jonathan Ryshpan
The machine OaklandWeather is set up to export some directories to the
machine amito. But when OaklandWeather is restarted the export is lost.
Running "# exportfs -a" restores the export and the desired files can be
seen by amito.

Some Details:
   root@OaklandWeather# cat /etc/exports
   # /etc/exportfs created by Jon : Fri 2021-11-05 02:33:51 PM PDT 
   # edited by Jon : Tue Nov 16 10:30:08 AM PST 2021
   # / amito(rw,no_subtree_check,no_root_squash)
   / amito(rw)
   /home amito(rw)
   
The problem seems to happen because nfs is started before amito can be
resolved:
   Nov 07 07:37:42 OaklandWeather.localdomain systemd[1]: Starting nfs-
   server.service - NFS server and services...
   Nov 07 07:37:42 OaklandWeather.localdomain exportfs[1074]: exportfs:
   Failed to resolve amito
   
When OaklandWeather is running, amito can be resolved without
difficulty:
   [jonrysh@oaklandweather ~]$ ping amito
   PING amito(fe80::eaa3:138b:df4f:7e60%enp4s0) 56 data bytes
   64 bytes from fe80::eaa3:138b:df4f:7e60%enp4s0: icmp_seq=1 ttl=64
   time=0.739 ms
   
System Info
   Operating System: Fedora Linux 36
   KDE Plasma Version: 5.25.5
   KDE Frameworks Version: 5.99.0
   Qt Version: 5.15.6
   Kernel Version: 6.0.5-200.fc36.x86_64 (64-bit)
   Graphics Platform: Wayland
   Processors: 2 × Intel® Pentium® CPU G2030 @ 3.00GHz
   Memory: 7.6 GiB of RAM
   Graphics Processor: Mesa Intel® HD Graphics 2500
   Manufacturer: Dell Inc.
   Product Name: Inspiron 660s

-- 
Sincerely Jonathan Ryshpan 

 The Website you seek
 Cannot be located, but
 Countless more exist.
___
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: Duplex Printer Problem

2022-09-07 Thread Jonathan Ryshpan
On Wed, 2022-09-07 at 08:32 -0300, George N. White III wrote:
> On Tue, Sep 6, 2022 at 11:46 PM Jonathan Ryshpan 
> wrote:
> > > For USB, see https://github.com/OpenPrinting/ipp-usb.  The
> > > "Issues" section has
> > > examples of troubleshooting on linux:
> > 
> > So there are, but none of them seems to have much to do with my
> > situation.
> 
> 
> The problems/printer models aren't the same, but some of the
> troubleshooting methods
> could help pin down the problem.  One reason troubleshooting IPP-USB
> is hard (quoting the README):
> Unfortunately, the naive implementation, which simply relays a TCP
> connection to USB, does not work. It happens because closing the TCP
> connection on the client side has a useful side effect of discarding
> all data sent to this connection from the server side, but it does not
> happen with USB connections. In the case of USB, all data not received
> by the client will remain in the USB buffers, and the next time the
> client connects to the device, it will receive unexpected data, left
> from the previous abnormally completed request.
> Actually, it is an obvious flaw in the IPP-over-USB standard, but we
> have to live with it.
> The easy workaround would be to switch to a network connection.  
> Opening an issue on the ipp-usb
> github site takes effort, but could be a useful contribution to the
> community.

This implies that cups needs to communicate with the printer to find out
something (say whether the printer has duplex capability), but can't
because of communication issues which would be solved if IPP-USB were
working properly. A test would be to change the connection to the
printer from USB to TCP/IP, i.e. I should disconnect USB, attach
Ethernet on the printer, set up the printer for Ethernet and see what
happens. Is all this correct?

I suspect that ipp-usb is not going to help because the HP m255dw
printer doesn't seem to be supported:
   # ipp-usb check
   Configuration files: OK
   No IPP over USB devices found

-- 
Sincerely Jonathan Ryshpan 

 Today's thought: 
 I can please only one person per day. Today is not 
 your day. Tomorrow isn't looking good either.
___
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: Duplex Printer Problem

2022-09-06 Thread Jonathan Ryshpan
Thanks very much.
On Tue, 2022-09-06 at 08:07 -0300, George N. White III wrote:
> HP "specs" say it has USB as well as wired or wireless network
> printing and that it
> supports Apple Airprint.  
> 
> Which communications interface are are you using?

USB.

> Airprint comes from IPP, which is the current "driverless" network
> protocol used by
> CUPS (from when CUPS was an Apple project).  There are drivers that
> make USB 
> look like IPP, but I assume those are printer-specific.  Airprint may
> diverge from IPP
> in the future, but HP's specs say this model works with older macOS
> versions, so 
> should support CUPS driverless printing  for ethernet and wifi.
> 
> For USB, see https://github.com/OpenPrinting/ipp-usb.  The "Issues"
> section has
> examples of troubleshooting on linux:
So there are, but none of them seems to have much to do with my
situation.

-- 
Sincerely Jonathan Ryshpan 

 If thousands of volunteers can make an operating system
 that doesn't crash, thousands of highly paid engineers
 should be able to do it, too. Then why don't they?
 -- Al Fasoldt
___
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: Duplex Printer Problem

2022-09-06 Thread Jonathan Ryshpan
On Tue, 2022-09-06 at 12:36 +0200, Klaus-Peter Schrage wrote:
> FWIW, hp-check gives me just the same errors about missing
> dependencies
> (some details in the log are different because my device HP Color
> LaserJet MFP M277dw includes scanning). So these messages are probably
> useless in your case - as far as I understand it, those dependencies
> are
> essential if you want to BUILD the hp libraries.
This looks very reasonable, except for the message
>  error: 'cups' package is missing or 'cups' service is not running.
Cups certainly seems to be running on my system
   $ systemctl status cups.service  
   ● cups.service - CUPS Scheduler
   Loaded: loaded (/usr/lib/systemd/system/cups.service; disabled;
   vendor preset: disabled)
   Active: active (running) since Tue 2022-09-06 19:08:56 PDT; 15min
   ago
Very mysterious...

> Interesting enough, hp-toolbox tells me that no hp devices can be
> found,
> although I definitely can use my printer/scanner. I found that my
> printer uses "driverless printing" through "IPP Everywhere". So you
> might investigate further in this direction:
> https://docs.fedoraproject.org/en-US/quick-docs/cups-useful-tricks/

hp-toolbox finds my printer without any trouble, not in the console
message but in the GUI.

It's not clear what cups-useful-tricks is about; there seems to be
unstated context. In any case the HP-M255dw is not capable of driverless
operation:

   $ sudo lsusb -v
   ...
   Bus 003 Device 004: ID 03f0:0a70 HP, Inc HP ColorLaserJet M255-M256
   Device Descriptor:
   ...
        bInterfaceClass 7 Printer
    bInterfaceSubClass  1 Printer
    bInterfaceProtocol  2 Bidirectional

The web page indicates that bInterfaceProtocol must be 4 for the printer
to be capable of driverless operation. So it looks like the document is
not relevant to my situation. However I did install ipp-usb (and
reboot), however without any apparent result.

-- 
Sincerely Jonathan Ryshpan 

 Procrastinators do it later.
___
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: Duplex Printer Problem

2022-09-05 Thread Jonathan Ryshpan
On Tue, 2022-08-30 at 07:14 -0700, Jonathan Ryshpan wrote:
> Whenever I try to print from Okular, a box with this message appears:
>There are conflicts in duplex settings. Do you want to fix them?
> And printing is in fact funky: the options for double sided printing:
>Okular->Print->Options
> are strange. The option "Long Side Printing" is selected (though
> greyed out); the option "Off" is selectable, but if selected, no other
> option can be selected afterward. Firefox doesn't allow control of
> duplex printing using its native print dialog, but duplex can be
> controlled using the system dialog.
> 
> Does anyone know what's going on or how to fix it.
> 
> Printer:
>HP Color Laserjet M255dw
> 
> Cups Version:
>cups-2.4.2-4.fc36.x86_64
> 
> System Info:
>Operating System: Fedora Linux 36
>KDE Plasma Version: 5.25.4
>KDE Frameworks Version: 5.97.0
>Qt Version: 5.15.5
>Kernel Version: 5.19.4-200.fc36.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

I tried running 
 $ hp-check --run
which appears to be largely undocumented, and which produced the
following errors. The list looks very strange. Does anyone know what's
going on? The entire output is attached as hp-check.log .
   
   ---
   | SUMMARY |
   ---
   
   Missing Required Dependencies
   -
   error: 'cups' package is missing or 'cups' service is not running.
   error: 'libjpeg-devel' package is missing/incompatible  
   error: 'cups-devel' package is missing/incompatible  
   error: 'cups-devel' package is missing/incompatible  
   error: 'libusb1-devel' package is missing/incompatible  
   error: 'sane-backends-devel' package is missing/incompatible  
   error: 'avahi-devel' package is missing/incompatible  
   error: 'net-snmp-devel' package is missing/incompatible  
   error: 'python3-devel' package is missing/incompatible  
   error: 'libtool' package is missing/incompatible  
   error: 'rpm-build' package is missing/incompatible  
   
   Missing Optional Dependencies
   -
   error: 'polkit' package is missing/incompatible  
   error: 'polkit-gnome' package is missing/incompatible  
   error: 'PKG_FROM_PIP:notify2' package is missing/incompatible  
   
   Total Errors: 12
   Total Warnings: 0
   

-- 
Sincerely Jonathan Ryshpan 

 The time you enjoy wasting is not wasted time.
 --Bertrand Russell
hp-check[44389]: info: :
hp-check[44389]: info: :[01mHP Linux Imaging and Printing System (ver. 3.22.6)[0m
hp-check[44389]: info: :[01mDependency/Version Check Utility ver. 15.1[0m
hp-check[44389]: info: :
hp-check[44389]: info: :Copyright (c) 2001-18 HP Development Company, LP
hp-check[44389]: info: :This software comes with ABSOLUTELY NO WARRANTY.
hp-check[44389]: info: :This is free software, and you are welcome to distribute it
hp-check[44389]: info: :under certain conditions. See COPYING file for more details.
hp-check[44389]: info: :
hp-check[44389]: info: :[01mNote: hp-check can be run in three modes:[0m
hp-check[44389]: info: :1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are  
hp-check[44389]: info: :installed to successfully compile HPLIP.   
hp-check[44389]: info: :2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper  
hp-check[44389]: info: :dependencies installed to successfully run.
hp-check[44389]: info: :3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). 
hp-check[44389]: info: :
hp-check[44389]: info: :Check types:   
hp-check[44389]: info: :a. EXTERNALDEP - External Dependencies 
hp-check[44389]: info: :b. GENERALDEP - General Dependencies (required both at compile and run time)   
hp-check[44389]: info: :c. COMPILEDEP - Compile time Dependencies 

Duplex Printer Problem

2022-08-30 Thread Jonathan Ryshpan
Whenever I try to print from Okular, a box with this message appears:
   There are conflicts in duplex settings. Do you want to fix them?
And printing is in fact funky: the options for double sided printing:
   Okular->Print->Options
are strange. The option "Long Side Printing" is selected (though greyed
out); the option "Off" is selectable, but if selected, no other option
can be selected afterward. Firefox doesn't allow control of duplex
printing using its native print dialog, but duplex can be controlled
using the system dialog.

Does anyone know what's going on or how to fix it.

Printer:
   HP Color Laserjet M255dw

Cups Version:
   cups-2.4.2-4.fc36.x86_64

System Info:
   Operating System: Fedora Linux 36
   KDE Plasma Version: 5.25.4
   KDE Frameworks Version: 5.97.0
   Qt Version: 5.15.5
   Kernel Version: 5.19.4-200.fc36.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 

 Three percent exceeds 2 percent by 50 percent, 
 not by 1 percent.
 --Edward Denison
___
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: Missing Libraries

2022-08-27 Thread Jonathan Ryshpan
On Sat, 2022-08-27 at 15:32 -0700, Samuel Sieb wrote:
> On 8/27/22 15:14, Jonathan Ryshpan wrote:
> > I'm trying to build an application for KDE, kpeoplevcard, available
> > from 
> > github. The compilation goes OK, but ld produces a large number of 
> > undefined references, so it looks like I should install some
> > libraries. 
> > What's the easiest way to find out which libraries to install?
> 
> That's very odd that it would compile and fail to link.  To have the 
> headers, you need the devel package and that will require the library 
> package.  Did you run a configure step of some sort?  That should
> detect 
> any missing libraries.
> 
> It can be difficult to go from a link error to the required library. 
> Can you show an example?

The program is on github and can be downloaded by:
   git clone https://invent.kde.org/pim/kpeoplevcard.git

The output of the build process is attached as all.


-- 
Sincerely Jonathan Ryshpan 

 If thousands of volunteers can make an operating system
 that doesn't crash, thousands of highly paid engineers
 should be able to do it, too. Then why don't they?
 -- Al Fasoldt
[ 11%] Automatic MOC for target KPeopleVCard
[ 11%] Built target KPeopleVCard_autogen
[ 22%] Building CXX object 
src/CMakeFiles/KPeopleVCard.dir/KPeopleVCard_autogen/mocs_compilation.cpp.o
[ 33%] Building CXX object src/CMakeFiles/KPeopleVCard.dir/kpeoplevcard.cpp.o
[ 44%] Linking CXX shared module ../bin/kpeople/datasource/KPeopleVCard.so
/usr/bin/ld: 
CMakeFiles/KPeopleVCard.dir/KPeopleVCard_autogen/mocs_compilation.cpp.o:(.data.rel.ro._ZTI12KPeopleVCard[_ZTI12KPeopleVCard]+0x0):
 undefined reference to `vtable for __cxxabiv1::__si_class_type_info'
/usr/bin/ld: CMakeFiles/KPeopleVCard.dir/kpeoplevcard.cpp.o: in function 
`(anonymous namespace)::Q_QGS_vcardsLocation::innerFunction()':
kpeoplevcard.cpp:(.text+0x100): undefined reference to `__cxa_guard_acquire'
/usr/bin/ld: kpeoplevcard.cpp:(.text+0x14a): undefined reference to 
`__cxa_guard_release'
/usr/bin/ld: CMakeFiles/KPeopleVCard.dir/kpeoplevcard.cpp.o: in function 
`(anonymous namespace)::Q_QGS_vcardsWriteLocation::innerFunction()':
kpeoplevcard.cpp:(.text+0x258): undefined reference to `__cxa_guard_acquire'
/usr/bin/ld: kpeoplevcard.cpp:(.text+0x2a2): undefined reference to 
`__cxa_guard_release'
/usr/bin/ld: CMakeFiles/KPeopleVCard.dir/kpeoplevcard.cpp.o: in function 
`KPeopleVCard::KPeopleVCard()':
kpeoplevcard.cpp:(.text+0x857): undefined reference to `operator new(unsigned 
long)'
/usr/bin/ld: CMakeFiles/KPeopleVCard.dir/kpeoplevcard.cpp.o: in function 
`KPeopleVCard::~KPeopleVCard()':
kpeoplevcard.cpp:(.text+0xa9f): undefined reference to `operator delete(void*, 
unsigned long)'
/usr/bin/ld: CMakeFiles/KPeopleVCard.dir/kpeoplevcard.cpp.o: in function 
`KPeopleVCard::processVCard(QString const&)':
kpeoplevcard.cpp:(.text+0x1079): undefined reference to `operator new(unsigned 
long)'
/usr/bin/ld: CMakeFiles/KPeopleVCard.dir/kpeoplevcard.cpp.o: in function 
`VCardDataSource::~VCardDataSource()':
kpeoplevcard.cpp:(.text+0x12ed): undefined reference to `operator delete(void*, 
unsigned long)'
/usr/bin/ld: CMakeFiles/KPeopleVCard.dir/kpeoplevcard.cpp.o: in function 
`VCardDataSource::createAllContactsMonitor()':
kpeoplevcard.cpp:(.text+0x136d): undefined reference to `operator new(unsigned 
long)'
/usr/bin/ld: CMakeFiles/KPeopleVCard.dir/kpeoplevcard.cpp.o: in function 
`VCardDataSourceFactory::~VCardDataSourceFactory()':
kpeoplevcard.cpp:(.text+0x140b): undefined reference to `operator delete(void*, 
unsigned long)'
/usr/bin/ld: CMakeFiles/KPeopleVCard.dir/kpeoplevcard.cpp.o: in function 
`qt_plugin_instance':
kpeoplevcard.cpp:(.text+0x1549): undefined reference to `__cxa_guard_acquire'
/usr/bin/ld: kpeoplevcard.cpp:(.text+0x1593): undefined reference to 
`__cxa_guard_release'
/usr/bin/ld: kpeoplevcard.cpp:(.text+0x15b6): undefined reference to `operator 
new(unsigned long)'
/usr/bin/ld: CMakeFiles/KPeopleVCard.dir/kpeoplevcard.cpp.o: in function 
`std::enable_if::ArgumentCount==(-1), QMetaObject::Connection>::type 
QObject::connect(QtPrivate::FunctionPointer::Object const*, void (KDirWatch::*)(QString const&), QObject const*, 
KPeopleVCard::KPeopleVCard()::{lambda(QString const&)#1}, Qt::ConnectionType)':
kpeoplevcard.cpp:(.text+0x16da): undefined reference to `operator new(unsigned 
long)'
/usr/bin/ld: CMakeFiles/KPeopleVCard.dir/kpeoplevcard.cpp.o: in function 
`std::enable_if::ArgumentCount==(-1), QMetaObject::Connection>::type 
QObject::connect(QtPrivate::FunctionPointer::Object const*, void (KDirWatch::*)(QString const&), QObject const*, 
KPeopleVCard::KPeopleVCard()::{lambda(QString const&)#2}, Qt::ConnectionType)':
kpeoplevcard.cpp:(.text+0x178f): undefined reference to `operator new(unsigned 
long)'
/usr/bin/ld: CMakeFiles/KPeopleVCard.dir/kpeoplevcard.cpp.o: in function 
`QtPrivate::QFunctorSlotObject, void>::impl(int, 
QtPrivate::QS

Missing Libraries

2022-08-27 Thread Jonathan Ryshpan
I'm trying to build an application for KDE, kpeoplevcard, available from
github. The compilation goes OK, but ld produces a large number of
undefined references, so it looks like I should install some libraries.
What's the easiest way to find out which libraries to install?

The System is:
   Operating System: Fedora Linux 36
   KDE Plasma Version: 5.25.4
   KDE Frameworks Version: 5.97.0
   Qt Version: 5.15.5
   Kernel Version: 5.18.19-200.fc36.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 

 Those who would give up essential liberty to 
 purchase a little temporary safety deserve 
 neither liberty nor safety.
 -- Benjamin Franklin
___
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


The Mystery of Fedora Sound

2022-08-12 Thread Jonathan Ryshpan
Can anyone point me to information about the Fedora/KDE audio system?
I'm running (I think) Pipewire and Pipewire-pulse, which usually serve
me well, but sometimes don't; and I have no idea how sound works on my
system. For example headphones plugged directly into an audio port work
on some configurations and not on others. 

Here's a screen shot of the audio control applet:

 
 * What defines the names?
- "Audioengine 2+" :  Which are a pair of USB connected speakers
- "Build-in Audio Pro" :  Which are my headphones
 * Why does Built-in Audio Pro appear twice?
 * What's the difference between "Built-in Audio Pro 1" and "Built-in
   Audio Pro 2"?
 * What are the "Profiles"?
 * What is the function of the circles with dots, which look like radio
   buttons, but can't be because two of them are selected.
 * ...

System Info:
 * Operating System: Fedora Linux 36
 * KDE Plasma Version: 5.25.4
 * KDE Frameworks Version: 5.96.0
 * Qt Version: 5.15.5
 * Kernel Version: 5.18.16-200.fc36.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

-- 
Many Thanks - Jonathan Ryshpan  If one foot is on
fire and the other is frozen to the floor on the average you are doing
OK.
___
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-36: Null Names for a Virtual Desktop Locks up the System

2022-06-15 Thread Jonathan Ryshpan
On Wed, 2022-06-15 at 21:44 +0100, Barry wrote:
> You can file bugs here https://bugzilla.redhat.com/ you will need an
> account.
> Choose file a bug, then choose fedora and the rest should be obvious.

Will do.

-- 
Many Thanks - Jonathan Ryshpan 

 Do you ever feel thankful that you know me and have
 access to my dementia? Explain and be prepared to 
 discuss in class.
___
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-36: Null Names for a Virtual Desktop Locks up the System

2022-06-15 Thread Jonathan Ryshpan
Here's what I did:
 * Invoked System Settings -> Workspace Behavior -> Virtual Desktops
 * Set the name of a desktop to null using the pen and backspace key
 * Hit Apply
The system is now well and truly locked up; the best way out seems to
be a reboot.

System is:
   Operating System: Fedora Linux 36
   KDE Plasma Version: 5.24.5
   KDE Frameworks Version: 5.93.0
   Qt Version: 5.15.3
   Kernel Version: 5.17.13-300.fc36.x86_64 (64-bit)
   Graphics Platform: X11
   Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
   Memory: 15.4 GiB of RAM
   Graphics Processor: Mesa Intel® HD Graphics 4600

-- 
Sincerely Jonathan Ryshpan  For I am a Bear of
Very Little Brain, and long words bother me. -- Winnie the Pooh
___
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


Problems upgrading f35->f36 : At this point I can't get there from here

2022-06-13 Thread Jonathan Ryshpan
I have just upgraded from Fedora-35 to Fedora-36 using dnf system-
upgrade. The upgrade appeared to go without problems, but the system
has been extremely slow  since the upgrade -- programs take a long time
to start or respond, delays in typing, etc. There seems to be a great
deal of CPU and disk activity for no apparent reason

===> Does anyone have a suggestion of how to investigate?

For lack of a better idea, I decided to reinstall my system: I built
installation media using  Fedora Media Writer and started a re-
installation process. However the Fedora installer for KDE thinks my
system is BIOS based, while in fact it is UEFI based; so it wants me to
create a biosboot partition at sector 0 of the drive.

===> Does anyone have a suggestion of how to investigate?

System Info is:
   Operating System: Fedora Linux 36
   KDE Plasma Version: 5.24.5
   KDE Frameworks Version: 5.93.0
   Qt Version: 5.15.3
   Kernel Version: 5.17.13-300.fc36.x86_64 (64-bit)
   Graphics Platform: X11
   Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
   Memory: 15.4 GiB of RAM
   Graphics Processor: Mesa Intel® HD Graphics 4600

The BIOS is:
 American Megatrends Version 2.16.1240, Copyright 2015

-- 
Thanks for your help - Jonathan Ryshpan 

 I'm not a vegetarian because I love animals.
 I'm a vegetarian because I hate plants.
___
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: Flakey Bluetooth Devices

2022-02-21 Thread Jonathan Ryshpan
On Wed, 2022-02-09 at 13:48 -0500, Tom Horsley wrote:
> On Wed, 09 Feb 2022 10:32:30 -0800 Jonathan Ryshpan wrote:
> There are two bluetooth devices paired with my main computer.  The
> connection is via this dongle:
>$ lsusb
>...
>Bus 003 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
> Dongle (HCI mode)
> Two devices are paired:
>$ bluetoothctl paired-devices
>Device C0:15:DA:B9:77:39 Bluetooth Ergonomic Mouse
>Device 3B:0C:40:C7:35:16 TEWELL T-1
> Both have problems:
> 
> I've never had any bluetooth device reliably connecting to anything
> (linux, windows, my car's audio, you name it). I've always suspected
> that "flakey" was mandated in the bluetooth standard.

A lucky Google hit has led me to a cure, which is to create
/etc/udev/rules.d/50-usb_power_save.rules. This disables power saving
to the bluetooth dongle. Read:
   
https://askubuntu.com/questions/1303731/how-to-change-bluetooth-timeout-settings-for-bluetooth-mouse
to find the magic and also links to explanations.

-- 
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Flakey Bluetooth Devices

2022-02-09 Thread Jonathan Ryshpan
There are two bluetooth devices paired with my main computer.  The
connection is via this dongle:
   $ lsusb
   ...
   Bus 003 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
Two devices are paired:
   $ bluetoothctl paired-devices
   Device C0:15:DA:B9:77:39 Bluetooth Ergonomic Mouse
   Device 3B:0C:40:C7:35:16 TEWELL T-1
Both have problems:

The MS Ergonomic Mouse often doesn't connect when the system starts.
 Sometimes it's possible to get it to connect by running
   $ bluetoothctl connect C0:15:DA:B9:77:39
but generally the only way to get the it to connect is by running:
   $ sudo pkill bluetoothd
which kills the bluetooth daemon; another instance is automatically
restarted, which recognizes the mouse.
Also, the mouse often falls asleep; it's possible to wake it by moving
it around, but it would be nicer is it stayed awake.

$ bluetoothctl info C0:15:DA:B9:77:39
Device C0:15:DA:B9:77:39 (random)
Name: Bluetooth Ergonomic Mouse
Alias: Bluetooth Ergonomic Mouse
Appearance: 0x03c2
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: yes
LegacyPairing: no
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: Device Information(180a--1000-8000-00805f9b34fb)
UUID: Battery Service   (180f--1000-8000-00805f9b34fb)
UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
UUID: Vendor specific   (7a440b82-7fc2-45bd-83e6-d6d78c5669d1)
Modalias: usb:v045Ep0834d0124
Battery Percentage: 0x64 (100)

The TEWELL internet radio often cuts off the first part of sentences
when listening to voice.  I can post a recording if anyone wants to
hear.

   $ bluetoothctl info 3B:0C:40:C7:35:16
   Device 3B:0C:40:C7:35:16 (public)
      Name: TEWELL T-1
      Alias: TEWELL T-1
      Class: 0x00340404
      Icon: audio-headset
      Paired: yes
      Trusted: yes
      Blocked: no
      Connected: yes
      LegacyPairing: no
      UUID: Audio Sink    (110b--1000-8000-
   00805f9b34fb)
      UUID: A/V Remote Control Target (110c--1000-8000-
   00805f9b34fb)
      UUID: Advanced Audio Distribu.. (110d--1000-8000-
   00805f9b34fb)
      UUID: A/V Remote Control    (110e--1000-8000-
   00805f9b34fb)
      UUID: PnP Information   (1200--1000-8000-
   00805f9b34fb)
      Modalias: bluetooth:v05D6p000Ad0240

System Info:

   Operating System: Fedora Linux 35
   KDE Plasma Version: 5.23.5
   KDE Frameworks Version: 5.90.0
   Qt Version: 5.15.2
   Kernel Version: 5.16.5-200.fc35.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
-- 
Sincerely Jonathan Ryshpan 

 All the world's a stage and most of us are 
 desperately unrehearsed. -- Sean O'Casey
___
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: Artifacts running konsole under Fedora-35

2022-01-06 Thread Jonathan Ryshpan
On Thu, 2022-01-06 at 09:40 -0400, George N. White III wrote:
> On Wed, 5 Jan 2022 at 06:54, Jonathan Ryshpan 
> wrote:
> > On Wed, 2022-01-05 at 01:19 -0800, Samuel Sieb wrote:
> > > On 1/5/22 01:00, Jonathan Ryshpan wrote:
> > > > Wayland is very flaky, crashes of various kinds, sometimes
> > > > killing individual apps, sometimes an entire session.  I can't
> > > > reproduce the crashes reliably; they happen when they happen.
> > > > The only thing that may be relevant is that I am running
> > > > Firefox with many (probably too many) 
> > > > windows and tabs.
> > > 
> > > It's probably not Wayland.  When it happens, check the journal. 
> > > It's likely the OOM killer.
> > BTW: KDE is now better.  No artifacts running X11, after nothing
> > but investigating and replying to your email.  Go figure...
> 
> 
> Intel is no longer supporting cards that old.
A case of "planned obsolescence".  My system is more than adequate for
everything I need it to do: web surfing, email, videos, sys admin, a
little development, etc. and nonetheless the CPU is no longer under
supported.  Oh well...

> https://wiki.archlinux.org/title/intel_graphics as usual, lots of
> good detail
> 
> I have a similar vintage system that is mainly used for data
> transfers from firewire and old memory card formats, so I may not
> encounter edge cases with graphics using a low-end (small fan) nvidia
> card and nouveau.  There are probably lots of old graphics cards
> gathering dust -- you could try ebay or a local computer users group.

Thanks very much.  It was hardware trouble and has been cured by the
advice about "Tearing" in Archlinux.

-- 
Sincerely Jonathan Ryshpan 

 Outside of a dog, a man's best friend is a book. 
 Inside a dog, it's too dark to read. -- Groucho Marx
___
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: Artifacts running konsole under Fedora-35

2022-01-05 Thread Jonathan Ryshpan
On Wed, 2022-01-05 at 01:19 -0800, Samuel Sieb wrote:
> On 1/5/22 01:00, Jonathan Ryshpan wrote:
> > Wayland is very flaky, crashes of various kinds, sometimes killing 
> > individual apps, sometimes an entire session.  I can't reproduce
> > the 
> > crashes reliably; they happen when they happen. The only thing that
> > may 
> > be relevant is that I am running Firefox with many (probably too
> > many) 
> > windows and tabs.
> 
> It's probably not Wayland.  When it happens, check the journal.  It's
> likely the OOM killer.

BTW: KDE is now better.  No artifacts running X11, after nothing but
investigating and replying to your email.  Go figure...


-- 
Sincerely Jonathan Ryshpan 

 If thousands of volunteers can make an operating system
 that doesn't crash, thousands of highly paid engineers
 should be able to do it, too. Then why don't they?
 -- Al Fasoldt
___
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: Artifacts running konsole under Fedora-35

2022-01-05 Thread Jonathan Ryshpan
On Wed, 2022-01-05 at 01:19 -0800, Samuel Sieb wrote:
> On 1/5/22 01:00, Jonathan Ryshpan wrote:
> > Wayland is very flaky, crashes of various kinds, sometimes killing 
> > individual apps, sometimes an entire session.  I can't reproduce
> > the 
> > crashes reliably; they happen when they happen. The only thing that
> > may 
> > be relevant is that I am running Firefox with many (probably too
> > many) 
> > windows and tabs.
> 
> It's probably not Wayland.  When it happens, check the journal.  It's
> likely the OOM killer.

Possible though not likely.  I just started firefox and ksysguardm
still running X11 and gnome-terminal.  The situation is:
 Memory 5.9 GiB / 15.5 GiB Swap 0 B / 32.0
GiB


Also looked for action from OOM (F35 was installed on 2022-01-02 about
19:30):
   $ journalctl --since 2022-01-01 | grep -i 'killed process'
   $ 

On the other hand:
   $ journalctl --since yesterday | grep -i wayland
   Jan 04 05:39:45 amito org_kde_powerdevil[79877]: The Wayland connection
   broke. Did the Wayland compositor die?
   Jan 04 05:39:45 amito polkit-kde-authentication-agent-1[79876]: The
   Wayland connection broke. Did the Wayland compositor die?
   Jan 04 05:39:45 amito kactivitymanagerd[79883]: The Wayland connection
   broke. Did the Wayland compositor die?
   Jan 04 05:39:45 amito kded5[79965]: The Wayland connection broke. Did
   the Wayland compositor die?
   Jan 04 05:39:45 amito kdeconnectd[79956]: The Wayland connection broke.
   Did the Wayland compositor die?
   Jan 04 05:39:45 amito unknown[79959]: Lost connection to Wayland
   compositor.
   Jan 04 05:39:45 amito xdg-desktop-portal-kde[80214]: The Wayland
   connection broke. Did the Wayland compositor die?
   Jan 04 05:39:45 amito konsole[80928]: The Wayland connection broke. Did
   the Wayland compositor die?
   Jan 04 05:39:45 amito unknown[87054]: Lost connection to Wayland
   compositor.
   Jan 04 05:39:45 amito baloorunner[88772]: The Wayland connection broke.
   Did the Wayland compositor die?
   Jan 04 05:39:45 amito kwalletd5[99930]: The Wayland connection broke.
   Did the Wayland compositor die?
   Jan 04 05:39:45 amito akonadi_kalarm_resource[80438]: The Wayland
   connection broke. Did the Wayland compositor die?
   Jan 04 05:39:45 amito akonadi_kalarm_resource[80427]: The Wayland
   connection broke. Did the Wayland compositor die?
   Jan 04 05:39:45 amito akonadi_kalarm_resource[80439]: The Wayland
   connection broke. Did the Wayland compositor die?
   Jan 04 05:39:45 amito akonadi_archivemail_agent[80419]: The Wayland
   connection broke. Did the Wayland compositor die?
   Jan 04 05:39:45 amito kgpg[80023]: The Wayland connection broke. Did
   the Wayland compositor die?
   ...

-- 
Many Thanks - Jonathan Ryshpan 

 We are sorry, but the number you have dialed is
 imaginary. Please rotate your phone 90 degrees
 and try again.
___
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: Artifacts running konsole under Fedora-35

2022-01-05 Thread Jonathan Ryshpan
On Wed, 2022-01-05 at 01:00 -0800, Jonathan Ryshpan wrote:
> X11 messes up konsole, the KDE terminal emulator.  When typing onto
> the screen, not displaying text generated by an application, the test
> appears slowly and with many strange artifacts. It looks like the
> text appears on one interlace and then gradually gets better; the
> text takes about 500 msec to recover; the same thing happens with
> window decorations when I mouse over them. I have attempted to record
> screen behavior using simplescreenrecorder, but when I start it, the
> problem goes away.

The highlighted text is actually not true.  The problem occurs with
many KDE applications, e.g. kpat and simplescreenrecorder.  Starting
simplescreenrecorder does make the artifacts stop.

-- 
Many Thanks - Jonathan Ryshpan 

 Anyone can do any amount of work, provided 
 it isn't the work he is supposed to be doing.
 --Robert Benchley
___
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


Artifacts running konsole under Fedora-35

2022-01-05 Thread Jonathan Ryshpan
I've just upgraded from F34 to F35 and have troubles with KDE vs
Wayland and X11.  

Wayland is very flaky, crashes of various kinds, sometimes killing
individual apps, sometimes an entire session.  I can't reproduce the
crashes reliably; they happen when they happen. The only thing that may
be relevant is that I am running Firefox with many (probably too many)
windows and tabs.

X11 messes up konsole, the KDE terminal emulator.  When typing onto the
screen, not displaying text generated by an application, the test
appears slowly and with many strange artifacts. It looks like the text
appears on one interlace and then gradually gets better; the text takes
about 500 msec to recover; the same thing happens with window
decorations when I mouse over them. I have attempted to record screen
behavior using simplescreenrecorder, but when I start it, the problem
goes away.

Right now I'm using X11 with gnome-terminal, which doesn't show the
problem.

System is:
   Operating System: Fedora Linux 35
   KDE Plasma Version: 5.23.4
   KDE Frameworks Version: 5.89.0
   Qt Version: 5.15.2
   Kernel Version: 5.15.12-200.fc35.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

-- 
All Suggestions Welcome - Jonathan Ryshpan 

 What is love? 'tis not hereafter; 
 Present mirth hath present laughter. 
 What's to come is still unsure: 
 In delay there lies no plenty,
 Then come kiss me, sweet and twenty. 
 Youth's a stuff will not endure." 
 -- Shakespeare's Twelfth Night
___
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: Dnf MutableMapping

2022-01-03 Thread Jonathan Ryshpan
On Sun, 2022-01-02 at 22:48 -0800, Samuel Sieb wrote:
> On 1/2/22 21:58, Jonathan Ryshpan wrote:
> > Whenever I run dnf these messages appear.  Dnf appears to run
> > correctly, but it would be nice to know what the messages mean, and
> > if they don't 
> > indicate anything harmful, how to make them go away
> > $ sudo dnf upgrade --refresh
> > Failed loading plugin "product-id": module 'collections' has no
> > attribute 'MutableMapping'
> > Failed loading plugin "subscription-manager": module 'collections'
> > has no attribute 'MutableMapping'
> > Failed loading plugin "upload-profile": module 'collections' has no
> > attribute 'MutableMapping'
> 
> Is this on Fedora?  Those are RHEL plugins.

Definitely.  Here is the system configuration:
   Operating System: Fedora Linux 35
   KDE Plasma Version: 5.23.4
   KDE Frameworks Version: 5.89.0
   Qt Version: 5.15.2
   Kernel Version: 5.15.12-200.fc35.x86_64 (64-bit)
   Graphics Platform: Wayland
   Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
   Memory: 15.5 GiB of RAM
   Graphics Processor: Mesa Intel® HD Graphics 4600

-- 
Sincerely Jonathan Ryshpan 

 The Website you seek
 Cannot be located, but
 Countless more exist.
___
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


Dnf MutableMapping

2022-01-02 Thread Jonathan Ryshpan
Whenever I run dnf these messages appear.  Dnf appears to run
correctly, but it would be nice to know what the messages mean, and if
they don't indicate anything harmful, how to make them go away
   $ sudo dnf upgrade --refresh          
   Failed loading plugin "product-id": module 'collections' has no
   attribute 'MutableMapping'
   Failed loading plugin "subscription-manager": module 'collections' has
   no attribute 'MutableMapping'
   Failed loading plugin "upload-profile": module 'collections' has no
   attribute 'MutableMapping'
   ...

-- 
Many Thanks - Jonathan Ryshpan 

 Do you ever feel thankful that you know me and have
 access to my dementia? Explain and be prepared to 
 discuss in class.
___
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: OT: Linux kernel version in fiber modem

2021-12-28 Thread Jonathan Ryshpan
On Sat, 2021-12-25 at 03:15 -0800, Jonathan Ryshpan wrote:
> On a whim I opened up the:
>Legal Disclaimer Open Source Licenses
> in the management page for my fiber modem (ATT installed 2021/03/30)
> and discovered that the kernel is rather old:

Since this seems to have produced a modest amount of interest, I'm
posting a little more of this license file; the whole file is about 0.5
Mbytes, which seems a little long.

The modem was provided to me by ATT when they installed fiber service;
I haven't checked but I suspect that it's the only device that ATT
supports and very likely the only one that works on the ATT network.
This very long list of open source software very likely contains more
vulnerabilities.

- ATT License File Starts  
- 

# BGW320 version 1.0 OPEN SOURCE SOFTWARE INFORMATION

For instructions on how to obtain a copy of any open source code being
made publicly available by AT 
related to open source software used in the BGW320 gateway, you may
send your request in writing to:

AVP, RG Software
Open Source Request
AT
2230 E Imperial HWY
El Segundo CA 90245

This document contains additional information regarding open source
software licenses, acknowledgments 
and required copyright notices for open source packages used in the
BGW320 device.

radvd - Version 2.18
libssl - Version 1.1.1k
motopia - ssl_api.c
openssl - Version 1.1.1k
dropbear - Version 2013.62
portmap - Version 6.0
tcp_wrappers - Version 7.6
libtecla - Version 1.6.2
pcre - Version 8.32
dhrystone - Version 2.2
flex - Version 2.5.4
aiccu - Version 20070115
motopia - list.h
mcproxy - mcp_util.c
miniupnpd
voip resolver - resolverapi.h
voip resolver - resolverapi.c
portmap - Version 5beta
SpryAssets
lua - Version 5.4.0
expat - Version 2.1.0
public include - pcp.h
cms_util - pcp.c
dhcp-isc - Version 4.1-ESV-R8
dhcpcd
motopia - md5.h
motopia - list.c
motopia - md5.c
muhttpd - Version 1.1.5
smartdb system - broadcom.c
voip SIP - sha1.c
voip SIP - sha1.h
dhcp - Version 4.1-ESV-R3
mini_httpd - Version 1.19
dhcpcd - ifaddrs.c
ez-ipupdate - md5.c
libmnl - Version 1.0.3
dhcpv6
dhcpv6 - ifaddrs.c
public include - cms_lzw.h
cms_util - base64decode.c
cms_util - base64encode.c
cms_util - lzw_decode.c
voip resolver - resolverprivate.c
widedhcpv6 - Version 20080615
widedhcpv6 - ifaddrs.c
uClibc - Version 0.9.28.3
arptables - Version 0.0.3-4
inetd - inetd.c
kernel - include
motopia-arm
netfilter
zl880 - arris_lt.c
bcmdriver include - adsldrv.h
bcmdriver include - AdslMibDef.h
bcmdriver include - atmapidrv.h
bcmdriver include - bcmadsl.h
bcmdriver include - bcmatmapi.h
bcmdriver include - bcmxdsl.h
bcmdriver include - DiagDef.h
bcmdriver include - VdslInfoDef.h
bdmf
dpi
pcmshim
rdpa_drv
rdpa_gpl
rdpa_mw
opensource include - bcmspucfg.h
opensource include - bcmspudrv.h
opensource include - bcmtypes.h
opensource include - board.h
bcmdrivers - enet
bcmdrivers - wfd
bcmdrivers - xtmrt
linux kernel - Version 3.4.11
bridge-utils - Version 1.2
busybox - Version 1.30.1
conntrack-tools - Version 1.4.1
dnsmasq - Version 2.85
dproxy-nexgen - Version 0.5
ebtables
ez-ipupdate - Version 3.0.11b7
ftpd - Version 1.0.24
haserl - Version 0.9.35
iproute2
iptables - Version 1.4.16.3
mtd-util - flash_eraseall.c
mtd - Version 1.5.0
ntfs-3g - Version 2014.3.15
ntpclient - Version 2010_356
rp-pppoe - Version 3.11
sysstat - Version 9.0.3
urlfilterd - Version 1.0.1
libnetfilter_conntrack - Version 1.0.3
libnetfilter_cthelper - Version 1.0.0
libnetfilter_cttimeout - Version 1.0.0
libnetfilter_queue - Version 1.0.2
libnfnetlink - Version 1.0.1
bcm_boot_launcher.c
bdmf_shell
memaccess.c
ppp - Version 2.3.11
psictl.c
scratchpadctl.c
send_cms_msg.c
simcard
public - include
cms_boardctl
cms_msg
cms_util
motopia
portmirror
prioritytag
udev - Version 136
bridge-utils - Version 1.0.6
iproute2 - Version 2.6.35
mtd - Version 20050122.orig
ntpclient - Version 2010_365
wireless_tools - Version 29
wpa_supplicant - Version 1.1
hostapd
compat.h
bootcfg.ko
pm_interval.ko
emaclib.ko
wlan.ko
wlan_ccmp.ko
wlan_scan_ap.ko
wlan_scan_sta.ko
wlan_tkip.ko
wlan_xauth.ko
xt_mark.ko
queue.h
linux kernel - Version 2.6.35.12
U-Boot - Version 2009.06
PHP - Version 5.0.5
zlib - Version 1.2.11
zlib - Version 1.2.3
dhcpcd - ifaddrs.h
dhcpv6 - ifaddrs.h
radvd - ifaddrs.h
mocana - parseasn1.c
smartdb system - etc53xx.h
widedhcpv6 - ifaddrs.h - Version 1.1.1.1
popt - Version 1.16
Process Control Daemon (PCD) - Version 1.1.6
syslog-ng - Version 3.8.1
eventlog - Version 0.2.12
glib - Version 2.40.0
logrotate - Version 3.11.0
libffi - Version 3.2.1
libuuid - Version 1.0.3
md5.js - Version 2.2
safeclib - Version 10052013
Argon2 - Version 1.3
curl - Version 7.70.0
ncurses - Version 6.1
mtr - Version 0.93
dbus - Version 1.10.8
systemd - Version 243
libfuse - Version 3.10.2
libattr - Version 2.4.48
util-linux - Version 2.36

-  ATT Licen

OT: Linux kernel version in fiber modem

2021-12-25 Thread Jonathan Ryshpan
On a whim I opened up the:
   Legal Disclaimer Open Source Licenses
in the management page for my fiber modem (ATT installed 2021/03/30)
and discovered that the kernel is rather old:
   linux kernel - Version 3.4.11
There are about 163 other open source components, probably most of
similar ages.

Is this a security problem?

-- 
Sincerely Jonathan Ryshpan 

 The above message, which does not represent 
 the opinion of the Berkeley Linux Team, is sold 
 by weight, not by volume. 
 Some settling of the contents may have occurred
 during shipment.
___
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: Webcam not recognized

2021-12-23 Thread Jonathan Ryshpan
On Thu, 2021-12-23 at 18:32 -0500, Tom Horsley wrote:
> On Thu, 23 Dec 2021 15:10:38 -0800
> Jonathan Ryshpan wrote:
> 
> > I have an HD Pro Webcam C920 which has stopped working on my main
> > system
> 
> I have a system at home in which almost all the USB ports stopped
> working, so maybe it isn't the camera. You might want to try every
> USB port and see if one works.

A very good suggestion.  I switched the camera with a bluetooth dongle:
the dongle works on both ports but the camera only works on one.  Go
figure...


-- 
Sincerely Jonathan Ryshpan 

 Vegetarians eat vegetables -- Beware of humanitarians.
___
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


Webcam not recognized

2021-12-23 Thread Jonathan Ryshpan
I have an HD Pro Webcam C920 which has stopped working on my main
system (amito), which doesn't recognize it and disconnects.  I have
another system (oaklandweather), which does recognize it and remains
connected.  Attached are the relevant extracts from the two system
logs, starting at the time the camera was plugged into a USB socket;
 each extract is preceded by system info.  Can anyone tell me what is
going on and how to get  the camera working?

The most important difference between the two systems is that amito
runs X11 but oaklandweather runs Wayland.  Otherwise they look very
 similar, except for the hardware.

-- 
Many Thanks - Jonathan Ryshpan 

 This sentence have three erors.
THIS DOESN'T WORK
Operating System: Fedora 34
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.15.10-100.fc34.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 DRI Intel® HD Graphics 4600

Dec 23 14:28:09 amito kernel: usb 3-5: new high-speed USB device number 27 
using xhci_hcd
Dec 23 14:28:12 amito kernel: usb 3-5: New USB device found, idVendor=046d, 
idProduct=082d, bcdDevice= 0.11
Dec 23 14:28:12 amito kernel: usb 3-5: New USB device strings: Mfr=0, 
Product=2, SerialNumber=1
Dec 23 14:28:12 amito kernel: usb 3-5: Product: HD Pro Webcam C920
Dec 23 14:28:12 amito kernel: usb 3-5: SerialNumber: 0A6F9F5F
Dec 23 14:28:12 amito kernel: usb 3-5: Found UVC 1.00 device HD Pro Webcam C920 
(046d:082d)
Dec 23 14:28:12 amito kernel: input: HD Pro Webcam C920 as 
/devices/pci:00/:00:14.0/usb3/3-5/3-5:1.0/input/input99
Dec 23 14:28:12 amito mtp-probe[1]: checking bus 3, device 27: 
"/sys/devices/pci:00/:00:14.0/usb3/3-5"
Dec 23 14:28:12 amito mtp-probe[1]: bus: 3, device: 27 was not an MTP device
Dec 23 14:28:12 amito mtp-probe[55591]: checking bus 3, device 27: 
"/sys/devices/pci:00/:00:14.0/usb3/3-5"
Dec 23 14:28:12 amito mtp-probe[55591]: bus: 3, device: 27 was not an MTP device
Dec 23 14:28:12 amito kdeconnectd[2925]: org.kde.pulseaudio: No object for name 
"alsa_output.pci-_00_1b.0.analog-stereo.monitor"
Dec 23 14:28:12 amito plasmashell[2778]: org.kde.plasma.pulseaudio: No object 
for name "alsa_output.pci-_00_1b.0.analog-stereo.monitor"
Dec 23 14:28:14 amito kernel: usb 3-5: USB disconnect, device number 27
Dec 23 14:28:14 amito kdeconnectd[2925]: org.kde.pulseaudio: No object for name 
"alsa_input.usb-046d_HD_Pro_Webcam_C920_0A6F9F5F-02.analog-stereo"
Dec 23 14:28:14 amito kdeconnectd[2925]: org.kde.pulseaudio: No object for name 
"alsa_output.pci-_00_1b.0.analog-stereo.monitor"
Dec 23 14:28:14 amito plasmashell[2778]: org.kde.plasma.pulseaudio: No object 
for name "alsa_input.usb-046d_HD_Pro_Webcam_C920_0A6F9F5F-02.analog-stereo"
Dec 23 14:28:14 amito plasmashell[2778]: org.kde.plasma.pulseaudio: No object 
for name "alsa_output.pci-_00_1b.0.analog-stereo.monitor"

THIS DOES WORK
Operating System: Fedora 34
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.15.10-100.fc34.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 2 × Intel® Pentium® CPU G2030 @ 3.00GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 2500

Dec 23 14:16:59 OaklandWeather.localdomain kernel: usb 1-1.3: new high-speed 
USB device number 6 using ehci-pci
Dec 23 14:17:01 OaklandWeather.localdomain kernel: usb 1-1.3: New USB device 
found, idVendor=046d, idProduct=082d, bcdDevice= 0.11
Dec 23 14:17:01 OaklandWeather.localdomain kernel: usb 1-1.3: New USB device 
strings: Mfr=0, Product=2, SerialNumber=1
Dec 23 14:17:01 OaklandWeather.localdomain kernel: usb 1-1.3: Product: HD Pro 
Webcam C920
Dec 23 14:17:01 OaklandWeather.localdomain kernel: usb 1-1.3: SerialNumber: 
0A6F9F5F
Dec 23 14:17:01 OaklandWeather.localdomain mtp-probe[49306]: checking bus 1, 
device 6: "/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3"
Dec 23 14:17:01 OaklandWeather.localdomain mtp-probe[49306]: bus: 1, device: 6 
was not an MTP device
Dec 23 14:17:01 OaklandWeather.localdomain kernel: mc: Linux media interface: 
v0.10
Dec 23 14:17:01 OaklandWeather.localdomain kernel: videodev: Linux video 
capture interface: v2.00
Dec 23 14:17:01 OaklandWeather.localdomain kernel: usb 1-1.3: Found UVC 1.00 
device HD Pro Webcam C920 (046d:082d)
Dec 23 14:17:01 OaklandWeather.localdomain kernel: input: HD Pro Webcam C920 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input29
Dec 23 14:17:01 OaklandWeather.localdomain kernel: usbcore: registered new 
interface driver uvcvideo
Dec 23 14:17:01 OaklandWeather.localdomain kernel: usbcore: registered new 
interface driver snd-usb-audio
Dec 23 14:17:01 OaklandWeather.localdomain mtp-probe[49329]: checking bus 1, 
device 6: "/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3&

Re: stream TO airplay/sonos

2021-12-02 Thread Jonathan Ryshpan
On Mon, 2021-11-22 at 16:06 -0600, SternData wrote:
> I see a bunch of tools that let my desktop act as an airplay
> receiver, but I'm having no google-fun finding a tool that lets use
> my Sonos system as speakers for the desktop.
I've used Noson (available in the Fedora-34 repos) successfully.  The
biggest problem is the delay, about 10 seconds, which has made it
mostly unusable for me.  Start Noson and enable Pulse Audio, then Noson
appears as a device in (say) the Pulse Audio list of Output Devices.


-- 
Sincerely Jonathan Ryshpan 

 All music is folk music. I ain't never heard no 
 horse sing a song. -- Louis Armstrong
___
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: Problems with USB AudioEngine Speakers [another couple of data points]

2021-10-17 Thread Jonathan Ryshpan
On Sun, 2021-10-17 at 19:50 +0800, Ed Greshko wrote:
> On 17/10/2021 18:37, Tim via users wrote:
> > On Sun, 2021-10-17 at 12:58 +0800, Ed Greshko wrote:
> > > The Fedora system produces sound with, hard to describe, some
> > > "stuttering".  So, it gives the impression of clicks, but there
> > > aren't any.
> > I wonder if that's a buffering or a sample rate conversion issue. 
> > For instance, if one piece of the puzzle decides it's going to
> > convert 44.1 to 48 kHz samples (though it could have just passed it
> > through, as-is) it might introduce noticeable distortions.
> 
> OK, I've "fixed" the problem.
> 
> I'm using KDE and I went to System Settings-->Hardware-->Audio--
> >Configure and for the profile for the Bluetooth speaker output I
> picked 
>High Fidelity Playback (A2DP Sink, codec ACC) 
> and now everything is great!

Interesting.  The choices on my system are much less informative.  For
AudioEngine 2+
Device Profile:
 * Off
 * Analog Stereo Output
 * Digital Stereo (E958) Output <===
 * Pro Audio
Speaker Placement and Testing
 * AudioEngine 2+  Digital Stereo (E958) <===
 * Build in Audio Analog Stereo
Right now the marked choices are active, the sound is good, and the
connection hasn't been dropped for the last day.

Does anyone know what these choices mean?  In particular, what is
"Digital Stereo (E958)"?

-- 
Thanks - Jonathan Ryshpan  Oderint dum metuant. --
Lucius Accius
___
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: Problems with USB AudioEngine Speakers [another couple of data points]

2021-10-17 Thread Jonathan Ryshpan
On Sun, 2021-10-17 at 07:46 +0800, Ed Greshko wrote:
> Sound quality from the Samsung is better than from Fedora.  When I
> have time I'll try to determine why that is so.
> I'm sorta suspecting pipewire.  But I have to find the instructions
> for switching between pipewire and pulseaudio.

I had to do this a couple of times while investigating the AudioEngine
speakers.  Here's what worked for my system:

To change from pulseaudio to pipewire:
dnf swap --allowerasing pulseaudio pipewire-pulseaudio
To change from pipewire to pulseaudio:
dnf swap --allowerasing pipewire-pulseaudio pulseaudio

-- 
All my best wishes - Jonathan Ryshpan 

 May the source be with you...
___
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: Problems with USB AudioEngine Speakers [another couple of data points]

2021-10-16 Thread Jonathan Ryshpan
On Sun, 2021-10-10 at 08:38 +0800, Ed Greshko wrote:
> On 10/10/2021 07:48, Jonathan Ryshpan wrote:
> 
> > 
> > On Sat, 2021-10-09 at 06:40 +0800, Ed Greshko wrote:
> > 
> > > What results do you get if you boot your system with the USB
> > > speakers disconnected and the connect them once the system is
> > > fully booted?
> > I was listening to some audio when the sound stopped;  AudioEngine
> > had disappeared from the list of output devices.  A log extract is
> > attached  (Audio-Crash.txt).  
> > 
> > There may be a problem with the cable.  The speakers are attached
> > to the computer with a USB extender cable, which may not give as
> > good a connection as is needed.  So I moved things around and
> > connected the speakers without the extender; we'll see if things
> > get better.  A log extract is attached (Audio-Restore-
> > ShortCable.txt).
> 
> Oh, I never did have much luck with USB extender cables.  FWIW, I
> don't use USB devices all that much.  Other than
> dongles I only have an HDMI capture device hooked to USB.
> 
> With speakers, I use Bluetooth.  I find them more versatile. 
Everything is working now.  A new USB cable long enough to reach from
the speakers to the computer without an extension has made USB
reliable.  And a new Bluetooth dongle from tp-link has made Bluetooth
reliable.  And there have been some upgrades to pipewire, which may
have affected things. The sound using USB seems slightly superior to
that using Bluetooth.


-- 
Sincerely Jonathan Ryshpan 

 All the world's a stage and most of us are 
 desperately unrehearsed. -- Sean O'Casey
___
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: Problems with USB AudioEngine Speakers [Bluetooth]

2021-10-12 Thread Jonathan Ryshpan
On Sun, 2021-10-10 at 08:38 +0800, Ed Greshko wrote:
> On 10/10/2021 07:48, Jonathan Ryshpan wrote:
> > 
> > On Sat, 2021-10-09 at 06:40 +0800, Ed Greshko wrote:
> > > What results do you get if you boot your system with the USB
> > > speakers disconnected and the connect them once the system is
> > > fully booted?
> > I was listening to some audio when the sound stopped;  AudioEngine
> > had disappeared from the list of output devices.  A log extract is
> > attached  (Audio-Crash.txt).  
> > 
> > There may be a problem with the cable.  The speakers are attached
> > to the computer with a USB extender cable, which may not give as
> > good a connection as is needed.  So I moved things around and
> > connected the speakers without the extender; we'll see if things
> > get better.  A log extract is attached (Audio-Restore-
> > ShortCable.txt).
> 
> Oh, I never did have much luck with USB extender cables.  FWIW, I
> don't use USB devices all that much.  Other than
> dongles I only have an HDMI capture device hooked to USB.
> 
> With speakers, I use Bluetooth.  I find them more versatile. 

I have changed the connection to Bluetooth, which worked well for a
while, except that sound quality may be a little less good.  However
the connection is still flaky: 
After plugging in another sound device via USB, Bluetooth disconnects
from the speakers, producing the log message:
   Oct 10 08:14:28 amito bluetoothd[15557]:
   profiles/audio/avdtp.c:avdtp_connect_cb() connect to AC:A9:B4:00:06:2E:
   Connection refused (111)
Does anyone know what this means?  The connection also drops fairly
frequently for no apparent reason.  The only way to reconnect is to
either remove and reinsert the Bluetooth adapter or to reboot the
system.

The Bluetooth adapter, an old Belkin USB dongle, produces this log
message when recognized:
   Oct 09 22:01:10 amito udisksd[2157]: Mounted /dev/sr0 at
   /run/media/jonrysh/我的光碟 on behalf of uid 1000
Definitely made in China.

I would like to try a different adapter (dongle).  Can anyone recommend
one?  There are a lot of choices, and the ones recommended (for M$
Windows) may not be the best for Linux.

-- 
Many Thanks - Jonathan Ryshpan 

 Bother' said Pooh as the Borg assimilated 
 Piglet -- Simon Robinson
___
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: Problems with USB AudioEngine Speakers [another couple of data points]

2021-10-09 Thread Jonathan Ryshpan
On Sat, 2021-10-09 at 06:40 +0800, Ed Greshko wrote:
> What results do you get if you boot your system with the USB speakers
> disconnected and the connect them once the system is fully booted?
I was listening to some audio when the sound stopped;  AudioEngine had
disappeared from the list of output devices.  A log extract is attached
 (Audio-Crash.txt).  

There may be a problem with the cable.  The speakers are attached to
the computer with a USB extender cable, which may not give as good a
connection as is needed.  So I moved things around and connected the
speakers without the extender; we'll see if things get better.  A log
extract is attached (Audio-Restore-ShortCable.txt).

-- 
Sincerely Jonathan Ryshpan 

 We've heard that a million monkeys at a million keyboards
 could produce the Complete Works of Shakespeare; 
 now, thanks to the Internet, we know this is not true.
 --Robert Wilensky, University of California
Oct 09 15:46:00 amito kernel: usb 3-14.1: USB disconnect, device number 9
Oct 09 15:46:00 amito pulseaudio[2569]: Got POLLNVAL from ALSA
Oct 09 15:46:00 amito pulseaudio[2569]: Error opening PCM device front:2: No 
such file or directory
Oct 09 15:46:00 amito kernel: usb 3-14: reset full-speed USB device number 8 
using xhci_hcd
Oct 09 15:46:00 amito plasmashell[2697]: org.kde.plasma.pulseaudio: No object 
for name 
"alsa_output.usb-Audioengine_LLC_Audioengine_2__AE202010001A2002-00.analog-stereo"
Oct 09 15:46:00 amito plasmashell[2697]: org.kde.plasma.pulseaudio: No object 
for name 
"alsa_output.usb-Audioengine_LLC_Audioengine_2__AE202010001A2002-00.analog-stereo.monitor"
Oct 09 15:46:00 amito plasmashell[2697]: org.kde.plasma.pulseaudio: No object 
for name "alsa_output.pci-_00_1b.0.analog-stereo.monitor"
Oct 09 15:46:00 amito systemsettings5[11781]: org.kde.plasma.pulseaudio: No 
object for name 
"alsa_output.usb-Audioengine_LLC_Audioengine_2__AE202010001A2002-00.analog-stereo"
Oct 09 15:46:00 amito systemsettings5[11781]: org.kde.plasma.pulseaudio: No 
object for name 
"alsa_output.usb-Audioengine_LLC_Audioengine_2__AE202010001A2002-00.analog-stereo.monitor"
Oct 09 15:46:00 amito systemsettings5[11781]: org.kde.plasma.pulseaudio: No 
object for name "alsa_output.pci-_00_1b.0.analog-stereo.monitor"
Oct 09 15:46:00 amito kernel: usb 3-14.1: new full-speed USB device number 15 
using xhci_hcd
Oct 09 15:46:00 amito kernel: usb 3-14.1: New USB device found, idVendor=0a12, 
idProduct=4007, bcdDevice=14.86
Oct 09 15:46:00 amito kernel: usb 3-14.1: New USB device strings: Mfr=1, 
Product=2, SerialNumber=3
Oct 09 15:46:00 amito kernel: usb 3-14.1: Product: Audioengine 2+
Oct 09 15:46:00 amito kernel: usb 3-14.1: Manufacturer: Audioengine LLC
Oct 09 15:46:00 amito kernel: usb 3-14.1: SerialNumber: AE202010001A2002
Oct 09 15:46:00 amito kernel: usb 3-14.1: can't set config #1, error -71
Oct 09 15:46:00 amito upowerd[2666]: treating change event as add on 
/sys/devices/pci:00/:00:14.0/usb3/3-14
Oct 09 15:46:00 amito upowerd[2666]: treating change event as add on 
/sys/devices/pci:00/:00:14.0/usb3/3-14
Oct 09 15:46:00 amito mtp-probe[11911]: checking bus 3, device 15: 
"/sys/devices/pci:00/:00:14.0/usb3/3-14/3-14.1"
Oct 09 15:46:00 amito mtp-probe[11911]: bus: 3, device: 15 was not an MTP device
Oct 09 15:46:00 amito mtp-probe[11924]: checking bus 3, device 15: 
"/sys/devices/pci:00/:00:14.0/usb3/3-14/3-14.1"
Oct 09 15:46:00 amito mtp-probe[11924]: bus: 3, device: 15 was not an MTP device
Oct 09 16:30:16 amito kernel: usb 3-6: new full-speed USB device number 18 
using xhci_hcd
Oct 09 16:30:16 amito kernel: usb 3-6: New USB device found, idVendor=0a12, 
idProduct=4010, bcdDevice=15.49
Oct 09 16:30:16 amito kernel: usb 3-6: New USB device strings: Mfr=0, 
Product=0, SerialNumber=0
Oct 09 16:30:16 amito kernel: hub 3-6:1.0: USB hub found
Oct 09 16:30:16 amito kernel: hub 3-6:1.0: 4 ports detected
Oct 09 16:30:16 amito upowerd[2666]: treating change event as add on 
/sys/devices/pci:00/:00:14.0/usb3/3-6
Oct 09 16:30:16 amito systemsettings5[11781]: 
file:///usr/share/kpackage/kcms/kcm_pulseaudio/contents/ui/StreamListItem.qml:22:
 TypeError: Cannot read property 'width' of null
Oct 09 16:30:16 amito kernel: usb 3-6.1: new full-speed USB device number 19 
using xhci_hcd
Oct 09 16:30:16 amito kernel: usb 3-6.1: New USB device found, idVendor=0a12, 
idProduct=4007, bcdDevice=14.86
Oct 09 16:30:16 amito kernel: usb 3-6.1: New USB device strings: Mfr=1, 
Product=2, SerialNumber=3
Oct 09 16:30:16 amito kernel: usb 3-6.1: Product: Audioengine 2+
Oct 09 16:30:16 amito kernel: usb 3-6.1: Manufacturer: Audioengine LLC
Oct 09 16:30:16 amito kernel: usb 3-6.1: SerialNumber: AE202010001A2002
Oct 09 16:30:16 amito kernel: usb 3-6.1: 1:1: cannot set freq 48000 to ep 0x3
Oct 09 16:30:16 amito kernel: hid-generic 0003:0A12:4007.000B: 
hiddev97,hidraw2: USB HID v1.11 Device [Audioengi

Re: Problems with USB AudioEngine Speakers

2021-10-09 Thread Jonathan Ryshpan
On Sat, 2021-10-09 at 06:40 +0800, Ed Greshko wrote:
> What results do you get if you boot your system with the USB speakers
> disconnected and the connect them once the system is fully booted?

Here are two extracts of a boot log:
 * plugAfterBoot.txt: System boot followed by connecting USB speakers
    (speakers visible in pavucontrol)
 * unplugPlug.txt:   Disconnecting USB speakers followed by connecting
   them (speakers visible in pavucontrol)

I'm a little surprised that the system sees the speakers after
reporting so many errors.

-- 
Sincerely Jonathan Ryshpan  In a World Without
Fences, Who Needs Gates? Linux - http://www.linux.org
Oct 09 09:49:06 amito kernel: usb 3-14: new full-speed USB device number 6 
using xhci_hcd
Oct 09 09:49:06 amito kernel: usb 3-14: New USB device found, idVendor=0a12, 
idProduct=4010, bcdDevice=15.49
Oct 09 09:49:06 amito kernel: usb 3-14: New USB device strings: Mfr=0, 
Product=0, SerialNumber=0
Oct 09 09:49:06 amito kernel: hub 3-14:1.0: USB hub found
Oct 09 09:49:06 amito kernel: hub 3-14:1.0: 4 ports detected
Oct 09 09:49:06 amito upowerd[2666]: treating change event as add on 
/sys/devices/pci:00/:00:14.0/usb3/3-14
Oct 09 09:49:06 amito kernel: usb 3-14.1: new full-speed USB device number 7 
using xhci_hcd
Oct 09 09:49:06 amito kernel: usb 3-14.1: New USB device found, idVendor=0a12, 
idProduct=4007, bcdDevice=14.86
Oct 09 09:49:06 amito kernel: usb 3-14.1: New USB device strings: Mfr=1, 
Product=2, SerialNumber=3
Oct 09 09:49:06 amito kernel: usb 3-14.1: Product: Audioengine 2+
Oct 09 09:49:06 amito kernel: usb 3-14.1: Manufacturer: Audioengine LLC
Oct 09 09:49:06 amito kernel: usb 3-14.1: SerialNumber: AE202010001A2002
Oct 09 09:49:06 amito kernel: hid-generic 0003:0A12:4007.0006: 
hiddev97,hidraw2: USB HID v1.11 Device [Audioengine LLC Audioengine 2+] on 
usb-:00:14.0-14.1/input2
Oct 09 09:49:06 amito mtp-probe[4005]: checking bus 3, device 7: 
"/sys/devices/pci:00/:00:14.0/usb3/3-14/3-14.1"
Oct 09 09:49:06 amito mtp-probe[4005]: bus: 3, device: 7 was not an MTP device
Oct 09 09:49:07 amito kernel: mc: Linux media interface: v0.10
Oct 09 09:49:07 amito kernel: usb 3-14.1: 1:1: cannot set freq 48000 to ep 0x3
Oct 09 09:49:07 amito kernel: usbcore: registered new interface driver 
snd-usb-audio
Oct 09 09:49:07 amito mtp-probe[4035]: checking bus 3, device 7: 
"/sys/devices/pci:00/:00:14.0/usb3/3-14/3-14.1"
Oct 09 09:49:07 amito mtp-probe[4035]: bus: 3, device: 7 was not an MTP device
Oct 09 09:49:07 amito systemd[2560]: Reached target Sound Card.
Oct 09 09:49:07 amito kernel: usb 3-14.1: 1:1: cannot get freq at ep 0x3
Oct 09 09:49:07 amito systemd[2560]: Starting Mark boot as successful...
Oct 09 09:49:07 amito systemd[2560]: Finished Mark boot as successful.
Oct 09 09:49:07 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to ep 0x3
Oct 09 09:49:07 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to ep 0x3
Oct 09 09:49:07 amito kernel: usb 3-14.1: 1:1: cannot set freq 48000 to ep 0x3
Oct 09 09:49:07 amito kernel: usb 3-14.1: 1:1: cannot set freq 48000 to ep 0x3
Oct 09 09:49:07 amito kernel: usb 3-14.1: 1:1: cannot set freq 48000 to ep 0x3
Oct 09 09:49:07 amito kernel: usb 3-14.1: 1:1: cannot set freq 48000 to ep 0x3
Oct 09 09:49:07 amito kernel: usb 3-14.1: 1:1: cannot set freq 48000 to ep 0x3
Oct 09 09:49:07 amito kernel: usb 3-14.1: 1:1: cannot get freq at ep 0x3
Oct 09 09:49:07 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to ep 0x3
Oct 09 09:49:07 amito rtkit-daemon[2154]: Supervising 7 threads of 4 processes 
of 1 users.
Oct 09 09:49:07 amito rtkit-daemon[2154]: Successfully made thread 4045 of 
process 2569 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
Oct 09 09:49:07 amito rtkit-daemon[2154]: Supervising 8 threads of 4 processes 
of 1 users.
Oct 09 09:49:07 amito plasmashell[2697]: org.kde.plasma.pulseaudio: No object 
for name "alsa_output.pci-_00_1b.0.analog-stereo.monitor"
Oct 09 09:49:07 amito plasmashell[2697]: org.kde.plasma.pulseaudio: No object 
for name 
"alsa_output.usb-Audioengine_LLC_Audioengine_2__AE202010001A2002-00.analog-stereo.monitor"
Oct 09 09:56:19 amito kernel: usb 3-14: USB disconnect, device number 6
Oct 09 09:56:19 amito kernel: usb 3-14.1: USB disconnect, device number 7
Oct 09 09:56:19 amito plasmashell[2697]: org.kde.plasma.pulseaudio: No object 
for name 
"alsa_output.usb-Audioengine_LLC_Audioengine_2__AE202010001A2002-00.analog-stereo"
Oct 09 09:56:19 amito plasmashell[2697]: org.kde.plasma.pulseaudio: No object 
for name 
"alsa_output.usb-Audioengine_LLC_Audioengine_2__AE202010001A2002-00.analog-stereo.monitor"
Oct 09 09:56:19 amito plasmashell[2697]: org.kde.plasma.pulseaudio: No object 
for name "alsa_output.pci-_00_1b.0.analog-stereo.monitor"
Oct 09 09:56:34 amito kernel: usb 3-14: new full-speed USB device number 8 
using xhci_hcd
Oct 09 09:56:34 amito kernel: usb 3-14: New USB device 

Re: Problems with USB AudioEngine Speakers

2021-10-08 Thread Jonathan Ryshpan
On Thu, 2021-10-07 at 18:55 -0700, Jonathan Ryshpan wrote:
> The stock Fedora-34 with pipewire allows some audio output from the
> speakers but with problems.  However the system with pipewire was so
> unstable that I was unable to investigate:
>  * device names changed
>  * audio configuration changed in unexpected ways, for unknown reasons
>  * system locked up (probably KDE Plasma lockup)
>  * audio went from one device to another and back every second or so
>  * ...
> 
> So I reverted to pulseaudio.  The audio is now stable, but the
> speakers are not recognized.  Here are suspicious sections of the
> starts of the journals for the two setups:

Today's upgrade has mostly but not completely cured the problem, at
least for pulseaudio.  The speakers started working as soon as the
upgrade had taken effect, even before a reboot.  I don't see what
upgraded package could have caused the device to appear; the record of
the upgrade is attached (dnf-upgrade-1021-10-08.txt).  Unfortunately,
the computer audio system does not always recognize the Audioengine-2+
speakers. Maybe there is some kind of race condition.

Here are extracts from system journals showing two different boot
sequences, one that works and one that doesn't:

A boot that works:
Oct 08 14:06:08 amito kernel: usb 3-14.1: New USB device found,
idVendor=0a12, idProduct=4007, bcdDevice=14.86 
Oct 08 14:06:08 amito kernel: usb 3-14.1: New USB device strings:
Mfr=1, Product=2, SerialNumber=3 
Oct 08 14:06:08 amito kernel: usb 3-14.1: Product: Audioengine 2+ 
Oct 08 14:06:08 amito kernel: usb 3-14.1: Manufacturer: Audioengine
LLC 
Oct 08 14:06:08 amito kernel: usb 3-14.1: SerialNumber:
AE202010001A2002 
Oct 08 14:06:08 amito kernel: hid-generic 0003:0A12:4007.0006:
hiddev97,hidraw3: USB HID v1.11 Device [Audioengine LLC Audioengine 2+]
on usb-:00:14.0-14.1/input2

The boot just before the one above, which doesn't work:
Oct 08 14:00:31 amito kernel: usb 3-14.1: new full-speed USB device
number 8 using xhci_hcd 
Oct 08 14:00:31 amito kernel: usb 3-14.1: New USB device found,
idVendor=0a12, idProduct=4007, bcdDevice=14.86 
Oct 08 14:00:31 amito kernel: usb 3-14.1: New USB device strings:
Mfr=1, Product=2, SerialNumber=3 
Oct 08 14:00:31 amito kernel: usb 3-14.1: Product: Audioengine 2+ 
Oct 08 14:00:31 amito kernel: usb 3-14.1: Manufacturer: Audioengine LLC
Oct 08 14:00:31 amito kernel: usb 3-14.1: can't set config #1, error -
71

-- 
Sincerely Jonathan Ryshpan  Better to light a
single candle than to curse the darkness.
Transaction ID : 1075
Begin time : Fri 08 Oct 2021 07:31:29 AM PDT
Begin rpmdb: 3691:42313e892d2a353cd001b817a995289d7e64560d
End time   : Fri 08 Oct 2021 07:32:23 AM PDT (54 seconds)
End rpmdb  : 3691:2a70deb0ecd448b6fb84f078f3470266703d964b
User   : Jonathan Ryshpan 
Return-Code: Success
Releasever : 34
Command Line   : upgrade --refresh
Comment: 
Packages Altered:
Upgrade  autocorr-en-1:7.1.6.2-2.fc34.noarch   @updates
Upgraded autocorr-en-1:7.1.6.2-1.fc34.noarch   @@System
Upgrade  gjs-1.68.4-3.fc34.x86_64  @updates
Upgraded gjs-1.68.4-2.fc34.x86_64  @@System
Upgrade  libdb-5.3.28-49.fc34.x86_64   @updates
Upgraded libdb-5.3.28-46.fc34.x86_64   @@System
Upgrade  libdb-utils-5.3.28-49.fc34.x86_64 @updates
Upgraded libdb-utils-5.3.28-46.fc34.x86_64 @@System
Upgrade  libreoffice-base-1:7.1.6.2-2.fc34.x86_64  @updates
Upgraded libreoffice-base-1:7.1.6.2-1.fc34.x86_64  @@System
Upgrade  libreoffice-calc-1:7.1.6.2-2.fc34.x86_64  @updates
Upgraded libreoffice-calc-1:7.1.6.2-1.fc34.x86_64  @@System
Upgrade  libreoffice-core-1:7.1.6.2-2.fc34.x86_64  @updates
Upgraded libreoffice-core-1:7.1.6.2-1.fc34.x86_64  @@System
Upgrade  libreoffice-data-1:7.1.6.2-2.fc34.noarch  @updates
Upgraded libreoffice-data-1:7.1.6.2-1.fc34.noarch  @@System
Upgrade  libreoffice-draw-1:7.1.6.2-2.fc34.x86_64  @updates
Upgraded libreoffice-draw-1:7.1.6.2-1.fc34.x86_64  @@System
Upgrade  libreoffice-graphicfilter-1:7.1.6.2-2.fc34.x86_64 @updates
Upgraded libreoffice-graphicfilter-1:7.1.6.2-1.fc34.x86_64 @@System
Upgrade  libreoffice-gtk3-1:7.1.6.2-2.fc34.x86_64  @updates
Upgraded libreoffice-gtk3-1:7.1.6.2-1.fc34.x86_64  @@System
Upgrade  libreoffice-help-en-1:7.1.6.2-2.fc34.x86_64   @updates
Upgraded libreoffice-help-en-1:7.1.6.2-1.fc34.x86_64   @@System
Upgrade  libreoffice-impress-1:7.1.6.2-2.fc34.x86_64   @updates
Upgraded libreof

Problems with USB AudioEngine Speakers

2021-10-07 Thread Jonathan Ryshpan
I have just installed a pair of AudioEngine speakers and have many
problems:

The stock Fedora-34 with pipewire allows some audio output from the
speakers but with problems.  However the system with pipewire was so
unstable that I was unable to investigate:
 * device names changed
 * audio configuration changed in unexpected ways, for unknown reasons
 * system locked up (probably KDE Plasma lockup)
 * audio went from one device to another and back every second or so
 * ...

So I reverted to pulseaudio.  The audio is now stable, but the speakers
are not recognized.  Here are suspicious sections of the starts of the
journals for the two setups:

With pipewire:
...
Oct 07 15:50:10 amito kernel: usb 3-14: reset full-speed USB device
number 6 using xhci_hcd
Oct 07 15:50:11 amito kernel: usb 3-14.1: new full-speed USB device
number 9 using xhci_hcd
Oct 07 15:50:11 amito kernel: usb 3-14.1: New USB device found,
idVendor=0a12, idProduct=4007, bcdDevice=14.86
Oct 07 15:50:11 amito kernel: usb 3-14.1: New USB device strings:
Mfr=1, Product=2, SerialNumber=3
Oct 07 15:50:11 amito kernel: usb 3-14.1: Product: Audioengine 2+
Oct 07 15:50:11 amito kernel: usb 3-14.1: Manufacturer: Audioengine LLC
Oct 07 15:50:11 amito kernel: usb 3-14.1: SerialNumber:
AE202010001A2002
Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 48000 to
ep 0x3
Oct 07 15:50:11 amito kernel: hid-generic 0003:0A12:4007.0007:
hiddev97,hidraw3: USB HID v1.11 Device [Audioengine LLC Audioengine 2+]
on usb-:00:14.0-14.1/input2
Oct 07 15:50:11 amito upowerd[2720]: treating change event as add on
/sys/devices/pci:00/:00:14.0/usb3/3-14
Oct 07 15:50:11 amito upowerd[2720]: treating change event as add on
/sys/devices/pci:00/:00:14.0/usb3/3-14
Oct 07 15:50:11 amito mtp-probe[6841]: checking bus 3, device 9:
"/sys/devices/pci:00/:00:14.0/usb3/3-14/3-14.1"
Oct 07 15:50:11 amito mtp-probe[6841]: bus: 3, device: 9 was not an MTP
device
Oct 07 15:50:11 amito plasmashell[4490]: UdevQt: unhandled device
action "bind"
Oct 07 15:50:11 amito plasmashell[4490]: UdevQt: unhandled device
action "bind"
Oct 07 15:50:11 amito plasmashell[4490]: UdevQt: unhandled device
action "bind"
Oct 07 15:50:11 amito mtp-probe[6869]: checking bus 3, device 9:
"/sys/devices/pci:00/:00:14.0/usb3/3-14/3-14.1"
Oct 07 15:50:11 amito mtp-probe[6869]: bus: 3, device: 9 was not an MTP
device
Oct 07 15:50:11 amito plasmashell[4490]: UdevQt: unhandled device
action "bind"
Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to
ep 0x3
Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to
ep 0x3
Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to
ep 0x3
Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to
ep 0x3
Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to
ep 0x3
Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to
ep 0x3
Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to
ep 0x3
...

Using pulseaudio:
...
Oct 07 17:45:46 amito kernel: usb 3-14.1: New USB device found,
idVendor=0a12, idProduct=4007, bcdDevice=14.86
Oct 07 17:45:46 amito kernel: usb 3-14.1: New USB device strings:
Mfr=1, Product=2, SerialNumber=3
Oct 07 17:45:46 amito kernel: usb 3-14.1: Product: Audioengine 2+
Oct 07 17:45:46 amito kernel: hid-generic 0003:046D:400A.0005:
input,hidraw2: USB HID v1.11 Mouse [Logitech Wireless Device PID:400a]
on usb-:00:14.0-13/input2:1
Oct 07 17:45:46 amito kernel: hub 3-14:1.0: hub_ext_port_status failed
(err = -71)
Oct 07 17:45:46 amito kernel: input: Logitech M325 as
/devices/pci:00/:00:14.0/usb3/3-13/3-
13:1.2/0003:046D:C52B.0004/0003:046D:400A.0005/input/input13
...
Oct 07 17:45:46 amito kernel: usb 3-14.1: New USB device found,
idVendor=0a12, idProduct=4007, bcdDevice=14.86
Oct 07 17:45:46 amito kernel: usb 3-14.1: New USB device strings:
Mfr=1, Product=2, SerialNumber=3
Oct 07 17:45:46 amito kernel: usb 3-14.1: Product: Audioengine 2+
Oct 07 17:45:46 amito kernel: usb 3-14.1: Manufacturer: Audioengine LLC
Oct 07 17:45:46 amito kernel: usb 3-14.1: can't set config #1, error -
71
...

It would help to know what the various errors mean.

System is Fedora-34 with all updates installed, in detail:
Operating System: Fedora 34
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.14.9-200.fc34.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 DRI Intel® HD Graphics 4600

-- 
Sincerely Jonathan Ryshpan  If God lived on earth,
people would break all his windows.
___
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

Re: Entitlement Server?

2021-08-12 Thread Jonathan Ryshpan
On Thu, 2021-08-12 at 00:00 -0700, Samuel Sieb wrote:
> On 8/11/21 11:41 PM, Jonathan Ryshpan wrote:
> > On Thu, 2021-08-12 at 10:36 +0800, Ed Greshko wrote:
> > > Your VBox VM's, what type of disk image are you using?
> > 
> > There appear to be two kinds:
> > $ file *
> > Win-10.vbox:   XML 1.0 document, ASCII text
> > Win-10.vdi:    VirtualBox Disk Image, major 1, minor 1 (<<< Oracle VM 
> > VirtualBox Disk Image >>>), 107374182400 bytes
> 
> The first is the virtual machine config, the second is the disk image.

I suspected as much.  But are they compatible with qemu (which I
suspect they aren't)?

-- 
Sincerely Jonathan Ryshpan 

Institutionalised language ... shakes the very
foundations of freedom and democracy.  It is the 
language of death...
-- Adonis
___
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: Entitlement Server?

2021-08-12 Thread Jonathan Ryshpan
sOn Thu, 2021-08-12 at 10:36 +0800, Ed Greshko wrote:
> On 12/08/2021 08:49, Jonathan Ryshpan wrote:
> > Sounds like a good idea but ... how compatible are qemu snapshot
> > file
> > with virtualbox's .vbox files?  I have only a small
> > amount
> > of stuff in my VirtualBox Windows machine, but it's valuable:
> > mostly
> > tax programs and data going back about 10 years.
> > 
> > Also, I have found that Oracle keeps its repos up to date better
> > than
> > the Fedora ones.
> 
> You can certainly disable the repo to test if the Entitlement Server
> message goes away.
> 
> Your VBox VM's, what type of disk image are you using?

There appear to be two kinds:
$ file *
Win-10.vbox:   XML 1.0 document, ASCII text
Win-10.vdi:    VirtualBox Disk Image, major 1, minor 1 (<<< Oracle VM
VirtualBox Disk Image >>>), 107374182400 bytes

-- 
Thanks - Jonathan Ryshpan 

 May the source be with you...
___
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: Entitlement Server?

2021-08-11 Thread Jonathan Ryshpan
On Thu, 2021-08-12 at 06:57 +0800, Ed Greshko wrote:
> On 11/08/2021 23:16, Jonathan Ryshpan wrote:
> > On Wed, 2021-08-11 at 11:49 +0800, Ed Greshko wrote:
> > > On 11/08/2021 08:57, Jonathan Ryshpan wrote:
> > > > At the latest upgrade the following strange message appeared.   What is 
> > > > it about?   Do need to take any action?
> > > > $ sudo dnf upgrade
> > > > [sudo] password for jonrysh:
> > > > Updating Subscription Management repositories.
> > > > Unable to read consumer identity
> > > > 
> > > > This system is not registered with an entitlement server. You can use 
> > > > subscription-manager to register.
> > > 
> > > Sounds like you have a non-fedora repo enabled for which a subscription 
> > > is needed.
> > > 
> > > Output of
> > > dnf repolist --enabled
> > 
> > Your wish is my command:
> > 
> > $ sudo dnf repolist --enabled
> > [sudo] password for jonrysh:
> > Updating Subscription Management repositories.
> > Unable to read consumer identity
> > This system is not registered with an entitlement server. You can use 
> > subscription-manager to register.
> > repo id  repo name
> > copr:copr.fedorainfracloud.org:cygn:pulseaudio-dlna  Copr repo for 
> > pulseaudio-dlna owned by cygn
> > fedora   Fedora 34 - x86_64
> > fedora-cisco-openh264    Fedora 34 openh264 
> > (From Cisco) - x86_64
> > fedora-modular   Fedora Modular 34 
> > - x86_64
> > gh-cli   packages for the 
> > GitHub CLI
> > google-chrome    google-chrome
> > google-earth-pro google-earth-pro
> > rpmfusion-free   RPM Fusion for 
> > Fedora 34 - Free
> > rpmfusion-free-updates   RPM Fusion for 
> > Fedora 34 - Free - Updates
> > rpmfusion-nonfree    RPM Fusion for 
> > Fedora 34 - Nonfree
> > rpmfusion-nonfree-updates    RPM Fusion for 
> > Fedora 34 - Nonfree - Updates
> > skype-stable skype (stable)
> > updates  Fedora 34 - x86_64 
> > - Updates
> > updates-modular  Fedora Modular 34 
> > - x86_64 - Updates
> > virtualbox   Fedora 34 - x86_64 
> > - VirtualBox
> 
> Suggest you first try disabling the Oracle repo "virtualbox".
> 
> I don't use virtualbox much since qemu VM's work great.  And, I don't know 
> why you'd want the Oracle repo and
> the Fedora VirtualBox repo both enabled.

Sounds like a good idea but ... how compatible are qemu snapshot file
with virtualbox's .vbox files?  I have only a small amount
of stuff in my VirtualBox Windows machine, but it's valuable: mostly
tax programs and data going back about 10 years.

Also, I have found that Oracle keeps its repos up to date better than
the Fedora ones.

-- 
Sincerely Jonathan Ryshpan 

"Do I contradict myself?  
Very well, I contradict myself, 
(I am large, I contain multitudes.)" 
-- Walt Whitman
___
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: Entitlement Server?

2021-08-11 Thread Jonathan Ryshpan
On Wed, 2021-08-11 at 11:49 +0800, Ed Greshko wrote:
> On 11/08/2021 08:57, Jonathan Ryshpan wrote:
> > At the latest upgrade the following strange message appeared.  
> > What is it about?   Do need to take any action?
> > $ sudo dnf upgrade
> > [sudo] password for jonrysh:
> > Updating Subscription Management repositories.
> > Unable to read consumer identity
> > 
> > This system is not registered with an entitlement server. You can
> > use subscription-manager to register.
> 
> Sounds like you have a non-fedora repo enabled for which a
> subscription is needed.
> 
> Output of
> dnf repolist --enabled

Your wish is my command:

$ sudo dnf repolist --enabled
[sudo] password for jonrysh: 
Updating Subscription Management repositories.
Unable to read consumer identity

This system is not registered with an entitlement server. You can use
subscription-manager to register.

repo id repo name
copr:copr.fedorainfracloud.org:cygn:pulseaudio-dlna Copr repo for
pulseaudio-dlna owned by cygn
fedora Fedora 34 - x86_64
fedora-cisco-openh264 Fedora 34 openh264 (From Cisco) - x86_64
fedora-modular Fedora Modular 34 - x86_64
gh-cli packages for the GitHub CLI
google-chrome google-chrome
google-earth-pro google-earth-pro
rpmfusion-free RPM Fusion for Fedora 34 - Free
rpmfusion-free-updates RPM Fusion for Fedora 34 - Free - Updates
rpmfusion-nonfree RPM Fusion for Fedora 34 - Nonfree
rpmfusion-nonfree-updates RPM Fusion for Fedora 34 - Nonfree - Updates
skype-stable skype (stable)
updates Fedora 34 - x86_64 - Updates
updates-modular Fedora Modular 34 - x86_64 - Updates
virtualbox Fedora 34 - x86_64 - VirtualBox

- 
Sincerely Jonathan Ryshpan 

 For I am a Bear of Very Little Brain, and 
 long words bother me. -- Winnie the Pooh
___
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


Entitlement Server?

2021-08-10 Thread Jonathan Ryshpan
At the latest upgrade the following strange message appeared.   What is
it about?   Do need to take any action?
$ sudo dnf upgrade
[sudo] password for jonrysh:  
Updating Subscription Management repositories.
Unable to read consumer identity

This system is not registered with an entitlement server. You can use
subscription-manager to register.
   
-- 
Sincerely Jonathan Ryshpan 

 "He who receives an idea from me, receives instructions
 himself without lessening mine; as he who lights his
 taper at mine, receives light without darkening me."
 -- Thomas Jefferson on Copyright
___
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: Audio output device changes unbidden under f34

2021-07-25 Thread Jonathan Ryshpan
On Sun, 2021-07-25 at 16:32 +0930, Tim via users wrote:
> On Sat, 2021-07-24 at 13:01 -0700, Jonathan Ryshpan wrote:
> > When I queue up a number of podcasts to play in rhythmbox, the output
> > device often changes when the second podcast starts, from a device
> > connected via a USB port to the built in audio.
> 
> Just to be thorough:  Can you plug it into another USB port?
> 
> If the connector is a bit loose, the device could be intermittently
> interrupted and resetting.  Perhaps sometimes it recovers, sometimes it 
> doesn't.

A very good point.  I'll try different ports over the next few days.

But service should continue to my desired (USB) device since it's
selected as the default in the KDE Plasma Audio Volume applet, using
   Applet->Device->Digital Output->Play all audio via this device
Digital Output is the desired device.

-- 
Thanks - Jonathan Ryshpan 

The above message, which does not represent 
the opinion of the Berkeley Linux Team, is sold 
by weight, not by volume.  
Some settling of the contents may have occurred
during shipment.
___
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


Audio output device changes unbidden under f34

2021-07-24 Thread Jonathan Ryshpan
When I queue up a number of podcasts to play in rhythmbox, the output
device often changes when the second podcast starts, from a device
connected via a USB port to the built in audio.  This happens when I
use either the PulseAudio Volume Control application or the KDE Plasma
Audio Volume applet.  I don't remember it happening under Fedora-33.

System
 * KDE Frameworks 5.83.0
 * Fedora-34 with all updates installed

-- 
Thanks for your help Jonathan Ryshpan  Dance, as
if nobody's watching, Love, as if you've never been hurt, Sing, as if
no one can hear you, Work, as if you don't need the money, Live, as if
heaven is on earth. -- Rumi
___
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: D-Bus notification failed: Transport endpoint is not connected [was System always "Resumes from hibernation" on startup]

2021-07-11 Thread Jonathan Ryshpan
On Fri, 2021-07-09 at 08:18 -0700, Jonathan Ryshpan wrote:
> On Thu, 2021-07-01 at 08:25 -0600, Greg Woods wrote:
> > I would bet that if you "cat /proc/cmdline" you will see a resume=
> > parameter, but even if not this may be the default. At any rate, it
> > doesn't look like your resume attempt is the reason for the delay,
> > as the delay has already occurred when the resume is attempted:
> > 
> > Jun 30 12:19:40 amito kernel: Console: switching to colour frame
> > buffer device 240x75
> >         
> > Jun 30 12:21:08 amito dracut-initqueue[526]: WARNING: D-Bus
> > notification failed: Transport endpoint is not connected
> > 
> > Note that delay has already occurred at this point.
> > 
> > Jun 30 12:21:08 amito systemd[1]: Found device /dev/mapper/fedora-
> > swap.
> > Jun 30 12:21:08 amito systemd[1]: Starting Resume from hibernation
> > using device /dev/mapper/fedora-swap...
> > Jun 30 12:21:08 amito systemd-hibernate-resume[547]: Could not
> > resume from '/dev/mapper/fedora-swap' (253:1).
> > 
> > ...and the resume failure is a second or less after the attempted
> > resume starts.
> > 
> > On Thu, Jul 1, 2021 at 8:14 AM Jonathan Ryshpan
> >  wrote:
> > > ...
> > > System configuration"  
> > >    Operating System: Fedora 34
> > >    KDE Plasma Version: 5.22.2
> > >    KDE Frameworks Version: 5.83.0
> > >    Qt Version: 5.15.2
> > >    Kernel Version: 5.12.13-300.fc34.x86_64 (64-bit)
> > >    Graphics Platform: Wayland
> > >    Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
> > >    Memory: 15.5 GiB of RAM
> > >    Graphics Processor: Mesa DRI Intel® HD Graphics 4600
> 
> GW is correct.  I recreated the swap partition ($ swapoff -a; $
> mkswap; $ swapon -a) and the problem persisted.  Then I examined the
> full system log, which goes back to Thu 2020-07-09.  There a large
> number of entries like 
>Starting Resume from hibernation using device /dev/mapper/fedora-
>swap...
> none of which is associated with a delay
> 
> However there are no entries like
>WARNING: D-Bus notification failed: Transport endpoint is not
>connected
> until 2021-06-30, about a year.  After the first one appears, there
> is one following each reboot, and each is associated with a delay,
> generally, but not always, about 1 minute 28 seconds.
> 
> The system was upgraded from Fedora-33 to Fedora-34 on 2021-05-25, so
> there may be some connection.  I don't see anything on the web about
> this kind of error.  Can anyone enlighten me.

This is a known bug.
 See: https://bugzilla.redhat.com/show_bug.cgi?id=1976653

-- 
Sincerely Jonathan Ryshpan 

 Power tends to corrupt. Absolute power tends to
 corrupt absolutely. -- Lord Acton
___
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


D-Bus notification failed: Transport endpoint is not connected [was System always "Resumes from hibernation" on startup]

2021-07-09 Thread Jonathan Ryshpan
On Thu, 2021-07-01 at 08:25 -0600, Greg Woods wrote:
> I would bet that if you "cat /proc/cmdline" you will see a resume=
> parameter, but even if not this may be the default. At any rate, it
> doesn't look like your resume attempt is the reason for the delay, as
> the delay has already occurred when the resume is attempted:
> 
> Jun 30 12:19:40 amito kernel: Console: switching to colour frame
> buffer device 240x75
>         
> Jun 30 12:21:08 amito dracut-initqueue[526]: WARNING: D-Bus
> notification failed: Transport endpoint is not connected
> 
> Note that delay has already occurred at this point.
> 
> Jun 30 12:21:08 amito systemd[1]: Found device /dev/mapper/fedora-
> swap.
> Jun 30 12:21:08 amito systemd[1]: Starting Resume from hibernation
> using device /dev/mapper/fedora-swap...
> Jun 30 12:21:08 amito systemd-hibernate-resume[547]: Could not resume
> from '/dev/mapper/fedora-swap' (253:1).
> 
> ...and the resume failure is a second or less after the attempted
> resume starts.
> 
> On Thu, Jul 1, 2021 at 8:14 AM Jonathan Ryshpan 
> wrote:
> > ...
> > System configuration"  
> >    Operating System: Fedora 34
> >    KDE Plasma Version: 5.22.2
> >    KDE Frameworks Version: 5.83.0
> >    Qt Version: 5.15.2
> >    Kernel Version: 5.12.13-300.fc34.x86_64 (64-bit)
> >    Graphics Platform: Wayland
> >    Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
> >    Memory: 15.5 GiB of RAM
> >    Graphics Processor: Mesa DRI Intel® HD Graphics 4600

GW is correct.  I recreated the swap partition ($ swapoff -a; $ mkswap;
$ swapon -a) and the problem persisted.  Then I examined the full
system log, which goes back to Thu 2020-07-09.  There a large number of
entries like 
   Starting Resume from hibernation using device /dev/mapper/fedora-
   swap...
none of which is associated with a delay

However there are no entries like
   WARNING: D-Bus notification failed: Transport endpoint is not connected
until 2021-06-30, about a year.  After the first one appears, there is
one following each reboot, and each is associated with a delay,
generally, but not always, about 1 minute 28 seconds.

The system was upgraded from Fedora-33 to Fedora-34 on 2021-05-25, so
there may be some connection.  I don't see anything on the web about
this kind of error.  Can anyone enlighten me.

-- 
Thanks - jon 

 Rich or poor, it's good to have money.
___
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: System always "Resumes from hibernation" on startup

2021-07-08 Thread Jonathan Ryshpan
On Thu, 2021-07-01 at 08:25 -0600, Greg Woods wrote:
> I would bet that if you "cat /proc/cmdline" you will see a resume=
> parameter, but even if not this may be the default. At any rate, it
> doesn't look like your resume attempt is the reason for the delay, as
> the delay has already occurred when the resume is attempted:
> 
> Jun 30 12:19:40 amito kernel: Console: switching to colour frame
> buffer device 240x75
>         
> Jun 30 12:21:08 amito dracut-initqueue[526]: WARNING: D-Bus
> notification failed: Transport endpoint is not connected
> 
> Note that delay has already occurred at this point.
> 
> Jun 30 12:21:08 amito systemd[1]: Found device /dev/mapper/fedora-
> swap.
> Jun 30 12:21:08 amito systemd[1]: Starting Resume from hibernation
> using device /dev/mapper/fedora-swap...
> Jun 30 12:21:08 amito systemd-hibernate-resume[547]: Could not resume
> from '/dev/mapper/fedora-swap' (253:1).
> 
> ...and the resume failure is a second or less after the attempted
> resume starts.
> 
> On Thu, Jul 1, 2021 at 8:14 AM Jonathan Ryshpan 
> wrote:
> > ...
> > System configuration"  
> >    Operating System: Fedora 34
> >    KDE Plasma Version: 5.22.2
> >    KDE Frameworks Version: 5.83.0
> >    Qt Version: 5.15.2
> >    Kernel Version: 5.12.13-300.fc34.x86_64 (64-bit)
> >    Graphics Platform: Wayland
> >    Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
> >    Memory: 15.5 GiB of RAM
> >    Graphics Processor: Mesa DRI Intel® HD Graphics 4600

GW is correct.  I recreated the swap partition ($ swapoff -a; $ mkswap;
$ swapon -a) and the problem persisted.  Then I examined the full
system log, which goes back to Thu 2020-07-09.  There a large number of
entries like 
   Starting Resume from hibernation using device /dev/mapper/fedora-
   swap...
none of which is associated with a delay

However there are no entries like
   WARNING: D-Bus notification failed: Transport endpoint is not connected
until 2021-06-30, about a year.  After the first one appears, there is
one following each reboot, and each is associated with a delay,
generally, but not always, about 1 minute 28 seconds.

The system was upgraded from Fedora-33 to Fedora-34 on 2021-05-25, so
there may be some connection.  I don't see anything on the web about
this kind of error.  Can anyone enlighten me.

-- 
Sincerely Jonathan Ryshpan 

 "Never try to teach a pig to sing.
 It wastes time and annoys the pig."
___
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: System always "Resumes from hibernation" on startup

2021-07-01 Thread Jonathan Ryshpan
On Thu, 2021-07-01 at 07:26 -0700, stan via users wrote:
> On Thu, 01 Jul 2021 07:13:38 -0700
> Jonathan Ryshpan  wrote:
> 
> > The system always tries to restore from hibernation on startup; this
> > causes about a 1-1/2 minute delay.  I see no reason for this, since
> > the system is halted by "(Start)->Shut Do..."  Here is an extract
> > from the system log with inserted comments.
> 
> A long time ago I remember having a problem like this, and it was
> because the kernel had a resume on the command line, telling it to try
> an ancient hibernation on a swap partition.  When I removed that, it
> went away.  You could interrupt the boot and look at the kernel command
> line, and if it is there remove it before booting to see if that is the
> cause.

Interesting!  Did you remove the "resume=/..." from the command line,
or the ancient hibernation from the swap partition?  If the
hibernation, how did you remove it?

-- 
Many Thanks - Jonathan Ryshpan 

Honesty may not be the best policy, 
but it is worth trying once in a while.
--Richard Nixon
___
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


System always "Resumes from hibernation" on startup

2021-07-01 Thread Jonathan Ryshpan
The system always tries to restore from hibernation on startup; this
causes about a 1-1/2 minute delay.  I see no reason for this, since the
system is halted by "(Start)->Shut Do..."  Here is an extract from the
system log with inserted comments.

Jun 30 12:19:38 amito dracut-initqueue[523]: inactive  
'/dev/fedora/windows' [400.00 GiB] inherit
Jun 30 12:19:38 amito dracut-initqueue[523]: inactive  
'/dev/fedora/root' [100.00 GiB] inherit
Jun 30 12:19:38 amito dracut-initqueue[523]: inactive  
'/dev/fedora/swap' [24.00 GiB] inherit
Jun 30 12:19:38 amito dracut-initqueue[523]: inactive  
'/dev/fedora/home' [<1.31 TiB] inherit
Jun 30 12:19:38 amito systemd[1]: Found device /dev/mapper/fedora-root.

Jun 30 12:19:38 amito systemd[1]: Reached target Initrd Root Device.
Jun 30 12:19:40 amito kernel: fbcon: Taking over console
Jun 30 12:19:40 amito kernel: Console: switching to colour frame buffer device 
240x75

Jun 30 12:21:08 amito dracut-initqueue[526]: WARNING: D-Bus notification 
failed: Transport endpoint is not connected
Jun 30 12:21:08 amito systemd[1]: Found device /dev/mapper/fedora-swap.
Jun 30 12:21:08 amito systemd[1]: Starting Resume from hibernation using device 
/dev/mapper/fedora-swap...
Jun 30 12:21:08 amito systemd-hibernate-resume[547]: Could not resume from 
'/dev/mapper/fedora-swap' (253:1).
Jun 30 12:21:08 amito systemd[1]: 
systemd-hibernate-resume@dev-mapper-fedora\x2dswap.service: Deactivated 
successfully.
Jun 30 12:21:08 amito systemd[1]: Finished Resume from hibernation using device 
/dev/mapper/fedora-swap.
Jun 30 12:21:08 amito kernel: PM: Image not found (code -22)
Jun 30 12:21:08 amito kernel: kauditd_printk_skb: 7 callbacks suppressed

System configuration"  
   Operating System: Fedora 34
   KDE Plasma Version: 5.22.2
   KDE Frameworks Version: 5.83.0
   Qt Version: 5.15.2
   Kernel Version: 5.12.13-300.fc34.x86_64 (64-bit)
   Graphics Platform: Wayland
   Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
   Memory: 15.5 GiB of RAM
   Graphics Processor: Mesa DRI Intel® HD Graphics 4600

-- 
Sincerely Jonathan Ryshpan 

But what are all these mysteries to me,
 2  Whose thoughts are full of indices and surds.
X  +  7 X  +  53
= 11 / 3.
-- Lewis Carrol
___
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: slow startup process and dmesg times

2021-06-30 Thread Jonathan Ryshpan
On Sun, 2021-06-27 at 15:37 -0500, Anil F Duggirala wrote:
> I am looking at output from dmesg on my laptop and there appears to be a 
> time when a process takes longer than what might be expected and I think 
> this may be reducing my startup speed.

I neglected to put the system configuration in my last message.  
Here it is:
   Operating System: Fedora 34
   KDE Plasma Version: 5.22.2
   KDE Frameworks Version: 5.83.0
   Qt Version: 5.15.2
   Kernel Version: 5.12.13-300.fc34.x86_64 (64-bit)
   Graphics Platform: Wayland
   Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
   Memory: 15.5 GiB of RAM
   Graphics Processor: Mesa DRI Intel® HD Graphics 4600

-- 
Sincerely Jonathan Ryshpan 

Better trouble a tiger in his lair than a sage among
his books.  For to you kingdoms and their armies are
mighty and enduring, but to him they are but toys of
the moment to be overturned by the flick of a finger.
___
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: slow startup process and dmesg times

2021-06-30 Thread Jonathan Ryshpan
On Sun, 2021-06-27 at 15:37 -0500, Anil F Duggirala wrote:
> I am looking at output from dmesg on my laptop and there appears to be a 
> time when a process takes longer than what might be expected and I think 
> this may be reducing my startup speed.

I have a similar problem, which seems to be caused by the system trying
to restore the system from hibernation, which I never (intended to)
invoke. The system was stopped by (Start)->Shut Do...  I have appended
a relevant extract from the system log; note the inserted comments.

Jun 30 12:19:38 amito dracut-initqueue[523]: inactive  
'/dev/fedora/windows' [400.00 GiB] inherit
Jun 30 12:19:38 amito dracut-initqueue[523]: inactive  
'/dev/fedora/root' [100.00 GiB] inherit
Jun 30 12:19:38 amito dracut-initqueue[523]: inactive  
'/dev/fedora/swap' [24.00 GiB] inherit
Jun 30 12:19:38 amito dracut-initqueue[523]: inactive  
'/dev/fedora/home' [<1.31 TiB] inherit
Jun 30 12:19:38 amito systemd[1]: Found device /dev/mapper/fedora-root.

Jun 30 12:19:38 amito systemd[1]: Reached target Initrd Root Device.
Jun 30 12:19:40 amito kernel: fbcon: Taking over console
Jun 30 12:19:40 amito kernel: Console: switching to colour frame buffer device 
240x75

Jun 30 12:21:08 amito dracut-initqueue[526]: WARNING: D-Bus notification 
failed: Transport endpoint is not connected
Jun 30 12:21:08 amito systemd[1]: Found device /dev/mapper/fedora-swap.
Jun 30 12:21:08 amito systemd[1]: Starting Resume from hibernation using device 
/dev/mapper/fedora-swap...
Jun 30 12:21:08 amito systemd-hibernate-resume[547]: Could not resume from 
'/dev/mapper/fedora-swap' (253:1).
Jun 30 12:21:08 amito systemd[1]: 
systemd-hibernate-resume@dev-mapper-fedora\x2dswap.service: Deactivated 
successfully.
Jun 30 12:21:08 amito systemd[1]: Finished Resume from hibernation using device 
/dev/mapper/fedora-swap.
Jun 30 12:21:08 amito kernel: PM: Image not found (code -22)
Jun 30 12:21:08 amito kernel: kauditd_printk_skb: 7 callbacks suppressed

-- 
Sincerely Jonathan Ryshpan 

"...whose songs and tunes have we been playing?"
"They belong to anyone who wants to sing, play, or 
 dance to them"  -- Quoted by Graham Witt
___
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-34 breaks KDE pager

2021-06-25 Thread Jonathan Ryshpan
In versions up to Fedora-34, dragging a window icon in the pager from
one desktop to another used to move the related window from that
desktop to the other.  This no longer works.  Has the function been
removed or is there some option that needs to be set (or whatever)?

Platform: Fedora-34
KDE Plasma: 5.22.2
KDE Framework: 5.83.0
Graphics: Wayland

-- 
Thanks Jonathan Ryshpan 

 The world is so full of a number of things
 That we should all be as happy as kings.
 -- Robert Lewis Stevenson
___
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: Verifying Fedora-34

2021-06-25 Thread Jonathan Ryshpan
On Fri, 2021-06-25 at 22:25 -0400, Todd Zullinger wrote:
> Jonathan Ryshpan wrote:
> > While verifying my download of Fedora-34, I encounter this message:
> >    $ gpg --verify-files *-CHECKSUM 
> > gpg: Signature made Fri 23 Apr 2021 12:36:44 PM PDT
> > gpg:    using RSA key
> > 8C5BA6990BDB26E19F2A1A801161AE6945719A39
> > gpg: Good signature from "Fedora (34)
> > " [unknown]
> > gpg: WARNING: This key is not certified with a trusted signature!
> > gpg:  There is no indication that the signature belongs to
> > the owner.
> > Primary key fingerprint: 8C5B A699 0BDB 26E1 9F2A  1A80 1161 AE69
> > 4571 9A39
> > I surmise this means that my computer's list of trusted signatures
> > needs to be brought up to date (actually it may not even exist).
> >  How
> > can this be done?  A link to info would suffice.
> 
> There's nothing wrong with that output.  The warning is
> simply telling you that the Fedora key isn't signed by a key
> you've marked as trusted.
> 
> As an aside, we (the royal we, as in folks in the Fedora
> community who maintain the website) should change the
> verification step to recommend gpgv rather than the gpg
> command.  It would require making the fedora.gpg a
> de-armored file, but then it the instructions would be
> simpler.

Just as I thought.   So...

How do I mark a key as trusted?  What precautions are needed to be sure
that the key should actually be trusted?


-- 
Thanks - Jonathan Ryshpan 

 Those who have put out the eyes of the people
 reproach them for their blindness. -- Milton
___
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


Verifying Fedora-34

2021-06-25 Thread Jonathan Ryshpan
While verifying my download of Fedora-34, I encounter this message:
   $ gpg --verify-files *-CHECKSUM 
gpg: Signature made Fri 23 Apr 2021 12:36:44 PM PDT
gpg:    using RSA key
8C5BA6990BDB26E19F2A1A801161AE6945719A39
gpg: Good signature from "Fedora (34)
" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the
owner.
Primary key fingerprint: 8C5B A699 0BDB 26E1 9F2A  1A80 1161 AE69 4571
9A39
I surmise this means that my computer's list of trusted signatures
needs to be brought up to date (actually it may not even exist).  How
can this be done?  A link to info would suffice.

-- 
Thanks - jon 

 "Never try to teach a pig to sing.
 It wastes time and annoys the pig."
___
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


Trouble with firewalld

2021-04-11 Thread Jonathan Ryshpan
Looking through the system logs (journalctl --boot), I stumbled on the
following error messages from firewalld; it looks like the function
iptables-restore is called fairly frequently, generally after the
system wakes up from sleep, and never succeeds.  The intervening lines
vary.

Is this something to worry about?

Apr 09 07:16:49 amito firewalld[926]: ERROR: '/usr/sbin/iptables-
restore -w -n' failed: iptables-restore: line 9 failed
Apr 09 07:16:46 amito systemd[1]: Started Hostname Service.
Apr 09 07:16:49 amito firewalld[926]: ERROR: '/usr/sbin/ip6tables-
restore -w -n' failed: ip6tables-restore: line 9 failed
Apr 09 07:16:46 amito NetworkManager[1020]:   [1617977806.4768]
hostname: hostname: using hostnamed
Apr 09 07:16:49 amito firewalld[926]: ERROR: COMMAND_FAILED:
'/usr/sbin/ip6tables-restore -w -n' failed: ip6tables-restore: line 9
failed

-- 
Sincerely Jonathan 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 on the list, report it: 
https://pagure.io/fedora-infrastructure


What is the "compositor"?

2021-03-06 Thread Jonathan Ryshpan
What is the function of the "compositor"?  In KDE, controls for it are
available at:
   System Settings -> Display and Monitor -> Compositor
There's no useful documentation that I can find in System Settings or
on the web; it seems to have something to do with visual effects:
transparency, shadowing, and possibly others.  Any info would be
interesting.

Thanks - jon

___
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: capture system audio?

2021-02-23 Thread Jonathan Ryshpan
On Tue, 2021-02-23 at 13:09 -0500, Tom Horsley wrote:
> I'm playing a video in firefox and want to capture the audio.
> 
> There are a maze of web pages about audio capture, all different.
> None of the ones I've tried work. They all give the impression they
> are capturing audio, but the resulting audio files are nothing
> but silence.
> 
> Has anyone successfully captured audio from firefox on fedora 33?

Assuming you run PulseAudio, the tools that you want are Pavucontrol
and Audacity.  Pavucontrol controls the paths through which sound moves
in the PulseAudio system.  Audacity records it.  Both are pretty
intuitive.  When you start Firefox it will show up as a source in
Pavucontrol, similarly Audacity will show up as a sink. 

jon


___
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: Weird graphics errors with recent kernels

2021-02-23 Thread Jonathan Ryshpan
On Mon, 2021-02-22 at 16:55 +, Patrick O'Callaghan wrote:
> On Mon, 2021-02-22 at 08:28 -0800, Jonathan Ryshpan wrote:
> > On Sat, 2021-02-20 at 11:41 +, Patrick O'Callaghan wrote:
> > > The last 2 or 3 kernel updates seem to have triggered a
> > > regression in the i915 (internal Intel GPU) driver. I get damaged
> > > screen updates, very noticeable tearing on videos and occasional
> > > freezes in the DE
> > 
> > I may have a similar problem.  See my thread "Strange Artifacts in
> > the Panel"; the problem seems to affect the whole KDE Plasma
> > subsystem, but not other functions.
> 
> See the BZ report at
> https://bugzilla.redhat.com/show_bug.cgi?id=1931065
> A modified kernel seems to be working so far.

It works for me too.  Now I have to decide whether to install my new
CPU, scheduled to arrive this week, or return 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: Weird graphics errors with recent kernels

2021-02-22 Thread Jonathan Ryshpan
On Sat, 2021-02-20 at 11:41 +, Patrick O'Callaghan wrote:
> The last 2 or 3 kernel updates seem to have triggered a regression in
> the i915 (internal Intel GPU) driver. I get damaged screen updates,
> very noticeable tearing on videos and occasional freezes in the DE

I may have a similar problem.  See my thread "Strange Artifacts in the
Panel"; the problem seems to affect the whole KDE Plasma subsystem, but
not other functions.

___
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: Strange Artifacts on the Panel

2021-02-22 Thread Jonathan Ryshpan
On Thu, 2021-01-28 at 09:53 -0800, Jonathan Ryshpan wrote:
> On Thu, 2021-01-28 at 07:49 -0800, Jonathan Ryshpan wrote:
> > I've been seeing strange things on my panel for about a week or
> > two.  They are triangles or lines extending horizontally from a
> > region of some color, narrowing to a point.  They last generally
> > for up to about 30 seconds.  Attached is a picture of such an
> > artifact (PanelArtifact.jpg), taken with my cell phone.  Note the
> > black stripe just above "System Information".  Has anyone seen
> > anything like this
> > 
> > System: Fedora-32 all updates installed
> > Processor:  4 x Intel i5 4460 CPU at 3.2 GHz
> > Memory:  15.5 GiB RAM
> > Video System: Xorg (not Wayland)
> > Graphics: Mesa DRI Intel HD Graphics 4600
> > KDE Plasma: 5.20.5
> > KDE Framework: 5.78.0
> 
> Could it be a hardware issue?  It has an intermittent quality that
> looks like hardware trouble; but then why would the artifacts happen
> only in the panel?

Continuing: It does look like a hardware issue that affects only KDE
Plasma.  I see these things intermittently and only in plasma, i.e. the
desktop, the panel, and the start menu.  They have become more
pronounced, often flickering between this (normal)

and this (black panel, etc)

I'm planning to replace the CPU intel i5-4460 with an intel i7-4790.
 Let's see it it makes a difference.


___
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


Verifying a Fedora-33 Image

2021-02-11 Thread Jonathan Ryshpan
I have downloaded the Fedora-33 KDE spin and am attempting to verify
it.  Following the instructions (appended below for convenience) I
have:
 * Imported the keys using curl (where do they go?) and
 * Verified the CHECKSUM file using gpg

The verification fails with this message:
$ gpg --verify-files *-CHECKSUM
gpg: Signature made Fri 23 Oct 2020 08:09:07 AM PDT
gpg:    using RSA key
963A2BEB02009608FE67EA4249FD77499570FF31
gpg: Good signature from "Fedora (33)
" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the
owner.
Primary key fingerprint: 963A 2BEB 0200 9608 FE67  EA42 49FD 7749 9570
FF31
This doesn't look good.  How can I verify the CHECKSUM file?

Verification instructions
from https://spins.fedoraproject.org/en/verify follow:
   Next, import Fedora's GPG key(s):
   $ curl https://getfedora.org/static/fedora.gpg | gpg --import
   You can verify the details of the GPG key(s) here.
   Now, verify that the CHECKSUM file is valid:
   $ gpg --verify-files *-CHECKSUM
   The CHECKSUM file should have a good signature from one of the
   following keys:
- 12C944D0 - Fedora 32
- 3C3359C4 - Fedora 31
- CFC659B9 - Fedora 30
- DBBDCF7C - IOT 2019
   Finally, now that the CHECKSUM file has been verified, check that the
   image's checksum matches:
   $ sha256sum -c *-CHECKSUM
   If the output states that the file is valid, then it's ready to use!
   
___
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: Strange Artifacts on the Panel

2021-01-28 Thread Jonathan Ryshpan
On Thu, 2021-01-28 at 07:49 -0800, Jonathan Ryshpan wrote:
> I've been seeing strange things on my panel for about a week or two.
>  They are triangles or lines extending horizontally from a region of
> some color, narrowing to a point.  They last generally for up to
> about 30 seconds.  Attached is a picture of such an artifact
> (PanelArtifact.jpg), taken with my cell phone.  Note the black stripe
> just above "System Information".  Has anyone seen anything like this
> 
> System: Fedora-32 all updates installed
> Processor:  4 x Intel i5 4460 CPU at 3.2 GHz
> Memory:  15.5 GiB RAM
> Video System: Xorg (not Wayland)
> Graphics: Mesa DRI Intel HD Graphics 4600
> KDE Plasma: 5.20.5
> KDE Framework: 5.78.0

Could it be a hardware issue?  It has an intermittent quality that
looks like hardware trouble; but then why would the artifacts happen
only in the panel?

___
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: Strange Artifacts on the Panel

2021-01-28 Thread Jonathan Ryshpan
On Thu, 2021-01-28 at 08:57 -0800, Doug H. wrote:
> On Thu, Jan 28, 2021, at 7:49 AM, Jonathan Ryshpan wrote:
> > I've been seeing strange things on my panel for about a week or
> > two.  
> > They are triangles or lines extending horizontally from a region of
> > some color, narrowing to a point.  They last generally for up to
> > about 
> > 30 seconds.  Attached is a picture of such an artifact 
> > (PanelArtifact.jpg), taken with my cell phone.  Note the black
> > stripe 
> > just above "System Information".  Has anyone seen anything like
> > this
> 
> It sort of looks like it would be coming from whatever icon is to the
> left of the clipboard icon. When this stops happening, is there
> another icon there?

There is another icon there, the kalarm icon.  But I don't think this
has anything to do with the issue.  Artifacts appear all over the
panel: they appear to be extended from any icon on the panel and seem
to have something to do with the cursor.  I had thought it had
something to so with overloading the system; I frequently run Firefox
with many windows and tabs; but the artifacts appear whether or not
Firefox is 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


Strange Artifacts on the Panel

2021-01-28 Thread Jonathan Ryshpan
I've been seeing strange things on my panel for about a week or two.
 They are triangles or lines extending horizontally from a region of
some color, narrowing to a point.  They last generally for up to about
30 seconds.  Attached is a picture of such an artifact
(PanelArtifact.jpg), taken with my cell phone.  Note the black stripe
just above "System Information".  Has anyone seen anything like this

System: Fedora-32 all updates installed
Processor:  4 x Intel i5 4460 CPU at 3.2 GHz
Memory:  15.5 GiB RAM
Video System: Xorg (not Wayland)
Graphics: Mesa DRI Intel HD Graphics 4600
KDE Plasma: 5.20.5
KDE Framework: 5.78.0


___
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


Security Software Hack vs. Fedora

2020-12-17 Thread Jonathan Ryshpan
I read that there has been a major security hack of at least two
companies, FireEye and SolarWinds,  which supply security software to
the US Government and to major corporations.
 (see: 
https://www.nytimes.com/2020/12/16/opinion/fireeye-solarwinds-russia-hack.html
 ).  Does this have any effect on Fedora?

BTW/OT: One of the comments reads "...President Carter [said] that to
this day, if he wants to send a secure message, he hand-writes letters
to foreign leaders to avoid surveillance."
___
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


KDE System Monitor Widget Problem after upgrade to Fedora-33

2020-11-21 Thread Jonathan Ryshpan
Th KDE System Monitor Widget does not display Network Speed.  There is
a box on the panel where the network load would normally be shown.  
Relevant Sensors are: 
   "Download Rate" and "Upload Rate".
System is 
 * Fedora-33 (as of this afternoon)
 * System Monitor Sensor 1.0
 * KDE Frameworks 5.75.0
* Qt 5.15.1 (built against 5.15.1)
* The xcb windowing system
CPU load appears to be working properly.
___
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


Cantarell font prints blank (OT)

2020-07-15 Thread Jonathan Ryshpan
I have an HP M402dn printer which has started printing the Cantarell
font as blanks; a page using the Cantarell font prints as a perfectly
blank page.  The printer has no problem with (eg) the Liberation Sans
font.  I believe the problem started recently, possibly with my upgrade
from Fedora-31 to Fedora-32 on about May 17.  Questions:
 * How can I find out what fonts my printer supports?
 * How can I install fonts into the printer?

Thanks in advance - jon

___
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: X server crashes when system is busy but server is idle

2020-05-24 Thread Jonathan Ryshpan
On Sun, 2020-05-24 at 11:30 -0500, Roger Heflin wrote:
> On Sun, May 24, 2020 at 10:13 AM Jonathan Ryshpan <
> jonr...@pacbell.net
> > wrote:
> 
> > On Sun, 2020-05-24 at 01:00 -0700, Samuel Sieb wrote:
> > > On 5/23/20 11:24 PM, Jonathan Ryshpan wrote:
> > > > A number of times lately my system has partially locked up. When this
> > > > happens, the system is playing an audio file (usually using rhythmbox)
> > > > but is otherwise idle.

> How much ram do you have and when you switch to console mode is it
> fast or does it take several seconds or more?

RAM 16 GB.  Switch to console mode is pretty quick.

BTW: Top posting good; bottom posting good; mixed top and bottom
posting bad.

jon
___
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: X server crashes when system is busy but server is idle

2020-05-24 Thread Jonathan Ryshpan
On Sun, 2020-05-24 at 01:00 -0700, Samuel Sieb wrote:
> On 5/23/20 11:24 PM, Jonathan Ryshpan wrote:> 
> > A number of times lately my system has partially locked up. When this 
> > happens, the system is playing an audio file (usually using rhythmbox) 
> > but is otherwise idle. Audio continues but the screen is inactive: 
> > generally it is dark but sometimes it shows a screen saver (sometimes a 
> > clock that never changes); sometimes the cursor follows the mouse; 
> > usually no cursor is visible. It's possible to get into console mode by 
> > pressing CTRL/ALT/F2 but I haven't been able to get the graphical system 
> > back without rebooting. I first saw this under Fedora-31 and have been 
> > waiting for Fedora-32 before reporting it. Nothing in the log stands out.
> 
> > Any theories? Anything I should look for?
> 
> If you run top in the console is anything running?

Good question.  I'll run top the next time it happens.

> It only happens when playing audio?  How long does the audio keep playing?
The audio runs indefinitely.

> Which desktop are you running?
KDE Frameworks 5.68.0
Qt 5.13.2 (built against 5.13.2)
The xcb windowing system
___
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: X server crashes when system is busy but server is idle

2020-05-24 Thread Jonathan Ryshpan
On Sun, 2020-05-24 at 19:54 +0930, Tim via users wrote:
> On Sat, 2020-05-23 at 23:24 -0700, Jonathan Ryshpan wrote:> 
> > A number of times lately my system has partially locked up. When this
> > happens, the system is playing an audio file (usually using
> > rhythmbox) but is otherwise idle. Audio continues but the screen is
> > inactive: generally it is dark but sometimes it shows a screen saver
> > (sometimes a clock that never changes); sometimes the cursor follows
> > the mouse; usually no cursor is visible
> 
> You may have a crashing screensaver, you've described that situation to
> a tee.  The usual approach was to try disabling some screensavers; or
> turning off the choose random option, and only using one that you've
> never seen crash.

It's the most plain vanilla screensaver for KDE; there's not even an
entry for Screensaver in System Settings.  It's dark blue with a
digital clock at the top, then a place for a picture of m, then a box
to enter a password.
___
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


X server crashes when system is busy but server is idle

2020-05-24 Thread Jonathan Ryshpan
A number of times lately my system has partially locked up.  When this
happens, the system is playing an audio file (usually using rhythmbox)
but is otherwise idle.  Audio continues but the screen is inactive: generally 
it is dark but sometimes it shows a screen saver (sometimes a clock that never 
changes); sometimes the cursor follows the mouse; usually no cursor is visible. 
 It's possible to get into console mode by pressing CTRL/ALT/F2 but I haven't 
been able to get the graphical system back without rebooting.   I first saw 
this under Fedora-31 and have been waiting for Fedora-32 before reporting it.  
Nothing in the log stands out.

Any theories?  Anything I should look for?

System is Fedora-31 and Fedora-32
Server is:  /usr/libexec/Xorg
CPU model is: Intel(R) Core(TM) i5-4460  CPU @ 3.20GHz
Graphics controller is:  Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor Integrated Graphics Controller (rev 06)
___
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


Upgrade f31->f32 Problems with ktp/telepathy

2020-05-13 Thread Jonathan Ryshpan
Upgrading from f31 to f32 I get these errors:
$ sudo dnf system-upgrade download --refresh --skip-broken --
releasever=32Before you continue ensure that your system is fully
upgraded by running "dnf --refresh upgrade". Do you want to continue
[y/N]: yFedora Modular 32 - x86_64 ..Errors during downloading
metadata for repository 'virtualbox':  - Status code: 404 for 
http://download.virtualbox.org/virtualbox/rpm/fedora/32/x86_64/repodata/repomd.xml
(IP: 104.123.204.100)Error: Failed to download metadata for repo
'virtualbox': Cannot download repomd.xml: Cannot download
repodata/repomd.xml: All mirrors were triedIgnoring repositories:
virtualboxModular dependency problem:
 Problem: conflicting requests  - nothing provides module(platform:f31)
needed by module gimp:2.10:3120191106095052:f636be4b-
0.x86_64Error:  Problem: package ktp-common-internals-19.12.2-
1.fc32.x86_64 requires libtelepathy-qt5-service.so.0()(64bit), but none
of the providers can be installed  - problem with installed package
ktp-common-internals-19.12.1-1.fc31.x86_64  - telepathy-qt5-0.9.7-
9.fc31.x86_64 does not belong to a distupgrade repository  - ktp-
common-internals-19.12.1-1.fc31.x86_64 does not belong to a distupgrade
repository
The problems with virtualbox and gimp look fairly simple; the apps can
simply be removed from my system and then reinstalled later.  But
telepathy looks like a mess; there are a large number of rpms related
to it, namely the following list.  I don't use telepathy and would be
happy to see it go, but I am nervous about removing so many rpms for
fear that there may be other dependencies, so that removing them might
damage my system.  Can anyone advise me?Here is the list:ktp-desktop-
applets-19.12.1-1.fc31.x86_64ktp-auth-handler-19.12.1-1.fc31.x86_64ktp-
send-file-19.12.1-1.fc31.x86_64ktp-accounts-kcm-19.12.1-
1.fc31.x86_64ktp-approver-19.12.1-1.fc31.x86_64ktp-contact-runner-
19.12.1-1.fc31.x86_64ktp-contact-list-19.12.1-1.fc31.x86_64ktp-
filetransfer-handler-19.12.1-1.fc31.x86_64ktp-common-internals-19.12.1-
1.fc31.x86_64ktp-kded-integration-module-19.12.1-
1.fc31.x86_64telepathy-haze-0.8.0-3.fc22.x86_64telepathy-glib-0.24.1-
14.fc31.x86_64telepathy-accounts-signon-2.0-3.fc31.x86_64telepathy-
logger-0.8.2-9.fc31.x86_64telepathy-filesystem-0.0.2-
15.fc31.noarchtelepathy-logger-qt-17.08.0-7.fc31.x86_64telepathy-
gabble-0.18.4-7.fc29.x86_64telepathy-rakia-0.8.0-
13.fc31.x86_64telepathy-qt5-0.9.7-9.fc31.x86_64telepathy-mission-
control-5.16.4-9.fc31.x86_64telepathy-salut-0.8.1-15.fc29.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


ICE Connection rejected!

2019-12-21 Thread Jonathan Ryshpan
Has anyone seen a message like the following, which I started getting
when I upgraded from F30 to F31. It comes from dolphin when attempting
to view some (but not all) files in my Trash folder and also from
ksensors .  The problem has been reported on some other forums, e.g. 
https://forums.fedoraforum.org/showthread.php?322688-ICEauthority-problem-after-30-gt-31-upgrade=1828892#post1828892
but there doesn't seem to be any clear analysis or a solution.  

Any ideas?  If I file a bug, where should it go?

$ ksensors ICE Connection rejected!


DCOPClient::attachInternal. Attach failed Authentication Rejected,
reason : None of the authentication protocols specified are supported
and host-based authentication failed
ICE Connection rejected!

Thanks - jon


___
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: What cron entry generates mlocate.db ?

2019-12-09 Thread Jonathan Ryshpan
It looks like mlocate.db is updated on command of systemd.  

I want to have updatedb create two databases, one indexing my backup
device (/srv/UpdateDevice), which is a removable filesystem containing
a complete backup of (the rest of) my system, and the other
indexing  the complete system, including the backup device.  If
mlocate.db were created via a cron command this would be easy.  Since
actually the command comes from systemd, which I'm not familiar with,
it's not so easy.  Any hints?

Thanks - jon

On Mon, 2019-12-09 at 16:51 +, Patrick O'Callaghan wrote:
> On Mon, 2019-12-09 at 08:43 -0800, Jonathan Ryshpan wrote:
> > I would have thought it's in /etc/cron.daily, but I can't find it.
> > Where is it?
> 
> $ man locatelocate reads one or more databases prepared by
> updatedb(8) ...
> $ man updatedb...updatedb is usually run daily by cron(8) to update
> the default database
> $ sudo find /etc|grep
> updatedb/etc/updatedb.conf/etc/systemd/system/timers.target.wants/mlo
> cate-updatedb.timer


___
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


What cron entry generates mlocate.db ?

2019-12-09 Thread Jonathan Ryshpan
I would have thought it's in /etc/cron.daily, but I can't find it. 
Where is it?

Thanks - jon

___
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


OT: (Real) penguins at work

2019-09-20 Thread Jonathan Ryshpan
Enjoy this cute video for some comic relief in your day
   https://www.youtube.com/watch?v=d1JmOEWzOHQ

___
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


  1   2   3   4   5   >