F33->F34: paps output has changed
by Max Pyziur
Greetings,
Thank you to the Fedora team for the F34 roll-out; upgrades were seamless:
seemingly a trend not an anomoly.
I'm a paps users (paps is a PostScript converter from plain text file
using Pango), having at one time used enscript.
My general CLI invocation has been:
paps --columns=3 --landscape --paper=letter --font="Arial 6" /tmp/x3 | lpr -P lp3
This is generally sent to an HP53xx printer. /tmp/x3 is just a temporary
text file copied from somewhere else.
With the F34 upgrade, the output is a little uneven in print quality as
far as the fonts are concerned.
I've tried changing the "Arial 6" to "Serif 6", then to "Sans 6"
The last seems to be satifactory. The goal here is to print text files of
from a variety of sources: code, essays, articles, etc., in a compact
space to read. Not so much to print publication-quality stuff.
I would be interested in suggestions from other paps users on their
preferred
Much thanks,
Max Pyziur
pyz(a)brama.com
2 years, 11 months
A problem with wine and fedora 34
by Francisco Tissera
Hello everyone,
Just recently I have installed wine on Fedora 34, with gnome 40, and all
the defaults, but when ever I install an application and try to start
it, this happens:
Application could not be started, or no application associated with the
specified file. ShellExecuteEx failed: File not found.
Anyone have any clew as to how to fix it?
Thank you for any answer.
Best regards.
Francisco.
2 years, 11 months
Re: Upgrading 33 to 34. Small problems
by Frank
On 2021-05-01 3:08 p.m., Matti Pulkkinen wrote:
> la, 2021-05-01 kello 14:52 -0400, Frank kirjoitti:
>> Upgraded Fedora 33 to 34 yesterday following the Fedora
>> recommendations.
>>
>> It went well but today I noticed two small problems.
>>
>> Every once in a while sound stops working...pulse audio show no
>> devices
>> at all.
> Was this after suspending or hibernating the computer, by any chance?
> I've seen what you're describing too, once, and it was after waking up
> from suspend mode.
>
>
No. It happens without suspending or hibernating, while I am in the
desktop (Mate) .
Sometimes logging in and out doesn't work and I'll have to reboot.
2 years, 11 months
Upgrading 33 to 34. Small problems
by Frank
Upgraded Fedora 33 to 34 yesterday following the Fedora recommendations.
It went well but today I noticed two small problems.
Every once in a while sound stops working...pulse audio show no devices
at all. I know
pipewire is the default now so I have no idea how to resolve this
intermittent problem. It seems
when sound stops working, logging out and back in solves the problem.
The other problem is xscreen-saver has stopped working. I suspect it's been
integrated into systemd as there are a bunch of config files which
didn't exist before.
[frank@localhost ~]$ inxi -A
Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio
driver: snd_hda_intel
Sound Server-1: ALSA v: k5.11.16-300.fc34.x86_64 running: yes
Sound Server-2: PipeWire v: 0.3.26 running: yes
[frank@localhost ~]$ ls /etc/xscreensaver/
XScreenSaver.ad
XScreenSaver.ad.hacks
XScreenSaver.ad.header
XScreenSaver.ad.tail
I had xscreensaver setup to use GLslideshow, now all I get is a blank
screen.
Any ideas ?
Thanks
2 years, 11 months
btrfs
by Patrick Dupre
Hello,
With fedora32, I created a btrfs partition with gparted
fdisk see it as of type 83, ie. like a ext4 partition.
Is it normal?
btrfs filesystem show
can show it
Can I format the partition with an option of mke2fs ?
Thanks
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988 | | Room# D114A
===========================================================================
2 years, 11 months
Using the logs to detect a problem with webcam on OBS-Studio
by Paul Smith
Dear All,
After having upgraded from F33 to F34, my webcam was still detected by
OBS-Studio. However, it did not display any image -- only a black
rectangle.
It took me a lot of time to find out the cause: The resolution of my
webcam on OBS-Studio was configured as
"Leave unchanged"
and it should be
"1280x720".
So my question is: Could this problem have been spotted in some logs?
Thanks in advance,
Paul
2 years, 11 months
btrfs system slow down with 100GB file
by Richard Shaw
I'm getting significant iowait while writing to a 100GB file. I have
already made it nocow by copying it to another directory, marking the
director nocow (+C) and using cat <oldfile> <newfile> to re-create it from
scratch.
I was under the impression that this should fix the problem.
On a tangent, it took about 30 minutes to delete the old file... My system
is a Ryzen 5 3600 w/ 16GB or memory but it is a spinning disk. I use an
NVME for the system and the spinning disk for /home.
Currently I'm getting random GUI freezes due to the iowait problem and my
HDD indicator light basically stays on solid for over an hour now.
Any tips?
Thanks,
Richard
2 years, 11 months
Fwd: Re: (SOLVED) Problems upgrading to Fedora 34 openjfx and
openjfz8 conflict
by Feoli, Dr. Enrique
To whoever meets openjfx and openjfz8 conflict while upgrading
from F33 to F44
By suuport received from Ed Greshko the following will solve the
conflict
do
sudo dnf erase openjfx
sudo dnf erase opnjfx8
then download an install F34
system-upgrade download --refresh --releasever=34 --allowerasing
After upgrade reinstall openjfx8 (you will not be able to install both
packages in parallel on F34)
sudo dng install openjfx8
That will solve it.
Enrique
--- Mensaje original ---
ASUNTO: Re: Problems upgrading to Fedora 34
De: "Feoli, Dr. Enrique"
Para: "Community support for Fedora users"
Fecha: 30-04-2021 14:48
Thnak you so much Ed for the guidance. I was able to download the
Fedora 34 distribution, removed the openjfix and openjfx8 packages,
plus the two files that appear in the error message
Error: Transaction test error:
file /usr/lib/.build-id/c7/dcd663e38adaac7a2d8d137c46f337ab5543cf
from install of openjfx-3:11.0.9.2-4.fc34.x86_64 conflicts with file
from package openjfx8-8.0.202-26.b07.fc34.x86_64
file /usr/lib/.build-id/e6/010f9c606facd1495fb823e9e767752537712b
from install of openjfx-3:11.0.9.2-4.fc34.x86_64 conflicts with file
from package openjfx8-8.0.202-26.b07.fc34.x86_64
However, when the command to instal is given the above error appears
repatedly, even after rebooting. Is there some kind of chace to clear?
Enrique
A las Jueves, 29-04-2021 en 20:14 Ed Greshko escribió:
On 30/04/2021 09:08, Feoli, Dr. Enrique via users wrote:
> I am unfamiliar on how to communicate in th users lists. I hope not
to be breaking Code of Conduct by sending this emal.
This is the way....
>
> I have found Fedora a great working tool and need to upgrade from
Fedora 33 to Fedora 34. But the download in the Software app is giving
the following error:
> Error running transaction:
file/usr/.build-id/c7/-dcd663e38adaac7a2d6d137c46f337ab5543cf
conflicts between attempted installs of
openjfx8-80.202-26.b07.fc34x86_64 and openjfx-3:11.0.9.2-4.fc34x86_64
>
> Would anyone help in fixing this problem?
I'm not familiar with openjfx or openjf8 and I've not see this sort of
error before.
There are several things you can try.
system-upgrade download --refresh --releasever=34 --allowerasing
or
system-upgrade --exclude=openjfx --exclude= openjfx8 --refresh
--releasever=34
then upgrade them after the system upgrade has completed.
or
You can remove/erase those two packages, do the upgrade, and then add
them back after the
upgrade is complete.
--
Remind me to ignore comments which aren't germane to the thread.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)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
2 years, 11 months
Logitech webcam works in cheese and mplayer -- not zoom under
Firefox nor Chrome
by John W. Himpel
I am running a fully updated F34 on x86_64 hardware. I have a Logitech QuickCam Pro 9000 web cam (webcam +
microphone). I can view the video stream with cheese. I can view the video stream with mplayer. When I start zoom, I
can get no video.
zoom version 5.6.16888.0424-1
heese version 2:3.38.0-3.fc34
mplayer version 1.4.1-0.1.20210313svn.fc34
firefox-wayland version 88.0-5.fc34
google-chrome-stable 90.0.4430.93-1
Journalctl output while plugging in usb cable:
Apr 30 20:45:48 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792] (EE) event3 - Das Keyboard Das Keyboard P13: client
bug: event processing lagging behind by 25ms, your system is too slow
Apr 30 20:45:56 dubby.jlhimpel.net postfix/smtpd[18967]: connect from unknown[212.70.149.55]
Apr 30 20:45:58 dubby.jlhimpel.net audit[20327]: NETFILTER_CFG table=filter family=2 entries=30 op=xt_replace pid=20327
subj=system_u:system_r:iptables_t:s0 comm="iptables"
Apr 30 20:46:01 dubby.jlhimpel.net kernel: usb 1-11: new high-speed USB device number 7 using xhci_hcd
Apr 30 20:46:01 dubby.jlhimpel.net kernel: usb 1-11: New USB device found, idVendor=046d, idProduct=0990, bcdDevice=
0.05
Apr 30 20:46:01 dubby.jlhimpel.net kernel: usb 1-11: New USB device strings: Mfr=0, Product=0, SerialNumber=2
Apr 30 20:46:01 dubby.jlhimpel.net kernel: usb 1-11: SerialNumber: D4C0E1E4
Apr 30 20:46:01 dubby.jlhimpel.net kernel: uvcvideo: Found UVC 1.00 device <unnamed> (046d:0990)
Apr 30 20:46:01 dubby.jlhimpel.net kernel: input: UVC Camera (046d:0990) as /devices/pci0000:00/0000:00:14.0/usb1/1-
11/1-11:1.0/input/input33
Apr 30 20:46:01 dubby.jlhimpel.net kernel: usb 1-11: Warning! Unlikely big volume range (=3072), cval->res is probably
wrong.
Apr 30 20:46:01 dubby.jlhimpel.net kernel: usb 1-11: [5] FU [Mic Capture Volume] ch = 1, val = 4608/7680/1
Apr 30 20:46:01 dubby.jlhimpel.net mtp-probe[20330]: checking bus 1, device 7:
"/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11"
Apr 30 20:46:01 dubby.jlhimpel.net mtp-probe[20330]: bus: 1, device: 7 was not an MTP device
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (II) config/udev: Adding input device UVC Camera
(046d:0990) (/dev/input/event21)
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (**) UVC Camera (046d:0990): Applying InputClass
"evdev keyboard catchall"
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (**) UVC Camera (046d:0990): Applying InputClass
"libinput keyboard catchall"
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (**) UVC Camera (046d:0990): Applying InputClass
"system-keyboard"
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (II) Using input driver 'libinput' for 'UVC Camera
(046d:0990)'
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (II) systemd-logind: got fd for /dev/input/event21
13:85 fd 73 paused 0
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (**) UVC Camera (046d:0990): always reports core
events
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (**) Option "Device" "/dev/input/event21"
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (**) Option "_source" "server/udev"
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (II) event21 - UVC Camera (046d:0990): is tagged by
udev as: Keyboard
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (II) event21 - UVC Camera (046d:0990): device is a
keyboard
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (II) event21 - UVC Camera (046d:0990): device
removed
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (**) Option "config_info"
"udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11:1.0/input/input33/event21"
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (II) XINPUT: Adding extended input device "UVC
Camera (046d:0990)" (type: KEYBOARD, id 18)
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (**) Option "xkb_layout" "us"
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (II) event21 - UVC Camera (046d:0990): is tagged by
udev as: Keyboard
Apr 30 20:46:01 dubby.jlhimpel.net /usr/libexec/gdm-x-session[1792]: (II) event21 - UVC Camera (046d:0990): device is a
keyboard
Apr 30 20:46:02 dubby.jlhimpel.net /usr/libexec/gdm-x-session[20351]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Apr 30 20:46:02 dubby.jlhimpel.net /usr/libexec/gdm-x-session[20351]: > Warning: Could not resolve keysym
XF86FullScreen
Apr 30 20:46:02 dubby.jlhimpel.net /usr/libexec/gdm-x-session[20351]: Errors from xkbcomp are not fatal to the X server
Apr 30 20:46:02 dubby.jlhimpel.net mtp-probe[20358]: checking bus 1, device 7:
"/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11"
Apr 30 20:46:02 dubby.jlhimpel.net mtp-probe[20358]: bus: 1, device: 7 was not an MTP device
lsusb output:
Bus 004 Device 003: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 004 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 004: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 003 Device 003: ID 24f0:0105 Metadot Das Keyboard 4
Bus 003 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications
Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 001 Device 007: ID 046d:0990 Logitech, Inc. QuickCam Pro 9000
Bus 001 Device 002: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Any suggestions are greatly appreciated.
2 years, 11 months
Problems upgrading to Fedora 34
by Feoli, Dr. Enrique
Hello,
I am unfamiliar on how to communicate in th users lists. I hope not to be breaking Code of Conduct by sending this emal.
I have found Fedora a great working tool and need to upgrade from Fedora 33 to Fedora 34. But the download in the Software app is giving the following error:
Error running transaction: file/usr/.build-id/c7/-dcd663e38adaac7a2d6d137c46f337ab5543cf conflicts between attempted installs of openjfx8-80.202-26.b07.fc34x86_64 and openjfx-3:11.0.9.2-4.fc34x86_64
Would anyone help in fixing this problem?
Thanks and regards
Enrique Feoli
2 years, 11 months
