lost the meta key in gnome-terminal after 32 -> 33 upgrade
by Denis Shaposhnikov
Hi!
After upgrade my Fedora from 32 to 33 I found Meta key in the
gnome-terminal works strange. Looks like now the gnome-terminal
recognizes Alt key as Meta key. Everywhere in the system Win key is
the Meta key and in the gnome-terminal only Alt key is the Meta key. I
see it because before Win+Backspace deleted the whole word, but now it
deletes just one symbol and Alt+Backspace deletes the whole word. Does
anybody know how to return it to previous behavior?
3 years, 5 months
HTML/PDF -
by Bob Goodwin
What is the best way to convert an HTML file to PDF. I have a two page
report in HTML form that I want to change to PDF. I can scan a printed
copy but I would like to convert the HTML file I received to PDF.
LibreOffice reformat it into a four page document, I would prefer to
keep the original two page style.
Bob
--
Bob Goodwin - Zuni, Virginia, USA
FEDORA-32/64bit LINUX XFCE Fastmail POP3
3 years, 5 months
'smbclient' Crashing on Fedora 33
by Tim Evans
Have been working this on the BackupPC users mailing list, but it's
looking more like a general problem in F33's Samba utility, 'smbclient.'
BackupPC is a backup server package that uses Samba, rsync, and other
protocols to backup clients, including Windows PC's. Basically, it runs
a command like this for a SMB backup of a PC:
/usr/bin/smbclient \\\\new-pelican\\C\$ -U backup -E -d 2 -c tarmode\
full -Tc -
Output is piped to BackupPC utilities that unpack and index the backup,
and do other housekeeping
My backups have consistently failed since my upgrade to F33 (were
working without problems for years before, and most recently on F32).
Looking closely, it appears 'smbclient' is crashing after passing
exactly 47 files. (BackupPC then quits after data stops coming in.)
I've run this command at the command-line; it runs for a few seconds
then reports a core dump. Gnome shell then prompted me to file a
bugzilla, which I have done.
https://bugzilla.redhat.com/show_bug.cgi?id=1900232 "[abrt]
samba-client: remove_do_list_queue_head(): smbclient killed by SIGSEGV")
Anybody have further suggestions, please?
--
Tim Evans |5 Chestnut Court
443-394-3864 |Owings Mills, MD 21117
3 years, 5 months
f33 :: where should i fill bug against dnf-dragora?
by Adrian Sevcenco
Hi! Is there a specific place where can i fill a bug for dnf-dragora?
It is maddening that weird sorting where i have (descending order):
9994.2k 999.7k 998.5k 996.6k 994.9k 9928.2k ...
is this alphabetical sorting or what?
Thanks!
Adrian
3 years, 5 months
Waterfox?
by ToddAndMargo
Hi All,
Anyone have an experience with Waterfox?
https://www.waterfox.net
and do you like it?
Also, any sign of RPM support for it out
there anywhere?
Many thanks,
-T
3 years, 5 months
KDE System Monitor Widget Problem after upgrade to Fedora-33
by 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.
3 years, 5 months
Post F32->F33 upgrade rsync w ssh fails
by Max Pyziur
Greetings,
Even though I had done the F33 upgrade sometime ago, I am only now seeing
that it appears to have affected my rsync backups. When my CentOS server
issues the rsync backup the following error appears:
no hostkey alg
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: unexplained error (code 255) at io.c(600) [receiver=3.0.6]
Any suggestions on how to resolve this? I've done some Googling; it seems
that crypto policies have been upgraded; general suggestion is to
regenerate keys; but so far I'm having no success restoring the rsync
process.
Much thanks as always,
Max
pyz(a)brama.com
3 years, 5 months
Re: Audio Disc Burning software recommendation
by Sreyan Chakravarty
On Fri, Nov 20, 2020 at 4:31 PM Frank Elsner <frank.elsner(a)mailbox.org>
wrote:
> If it carrys an ISO9660 file system simpy mount it and play with any
> player.
>
No that's not what I meant by reading.
I meant before you actually write to a disc, you have to have the data from
your original disc somewhere right ?
What would you use to record that from the original disc ? That's what I
meant.
Sorry for the confusion.
3 years, 5 months
How use thin snapshots with a non-thin root filesystem ?
by Sreyan Chakravarty
I am looking into thin snapshots since the older COW snapshots delay my
boot enormously.
My normal root fs is on a normal "non-thin" volume.
So to make a snapshot I have boot into a live cd environment then set my
root fs volume to read-only and then set it to inactive.
Commands:
sudo lvchange -pr vgfedora/fedora
sudo lvchange -an vgfedora/fedora
Now I create the thin snapshot using lvcreate, after that I need to restore
my root LVS to its original state:
sudo lvchange -ay vgfedora/fedora
sudo lvchange -prw vgfedora/fedora
This fails with:
Command on LV vgfedora/fedora uses options that are invalid
with LV parameters: lv_is_external_origin.
I mean what is the point of creating a thin snapshot if I can't change my
original volume ?
What am I doing wrong?
--
Regards,
Sreyan Chakravarty
3 years, 5 months
Fwd: Unusually long boot times with LVM Snapshots
by Sreyan Chakravarty
On Fri, Nov 20, 2020 at 12:38 PM Samuel Sieb <samuel(a)sieb.net> wrote:
>
> Edit /etc/lvm/lvm.conf, find the line in the "log {" section that has
> "verbose = 0" and change it to "verbose = 1". Then run "dracut -f".
> Reboot and at the grub menu, edit the boot entry, remove the "quiet
> rhgb" parameters from the linux command line, then boot it. See what
> it's doing doing that time. After it's booted, you can also check
> "dmesg" and possible the "journalct -b" for information.
>
I have set
verbose = 1
and
level =7
the highest level, in the "log {" section of /etc/lvm/lvm.conf
But I have seen no change in boot logs. Let me know if I am doing anything
wrong.
I am checking the boot logs via :
journalctl -b
Also no change in the dmesg output.
Nevertheless, the think I have found the problem:
Nov 20 21:14:15 dracut-initqueue[902]: Scanning devices dm-0 for LVM
logical volumes vgfedora/fedora
Nov 20 21:14:16 dracut-initqueue[927]: inactive Original
'/dev/vgfedora/fedora' [700.00 GiB] inherit
Nov 20 21:14:16 dracut-initqueue[927]: inactive Snapshot
'/dev/vgfedora/pre_kde_Nov_9' [70.00 GiB] inherit
Nov 20 21:17:27 systemd[1]: Found device /dev/mapper/vgfedora-fedora.
Nov 20 21:17:27 systemd[1]: Found device
/dev/disk/by-uuid/03aef3ba-dca1-4cba-a3f5-36c5c0fe948e.
Nov 20 21:17:27 systemd[1]: Reached target Initrd Root Device.
As you can see there is a 3 minute delay to load or find the snapshot.
The question is what do I do now ?
This is my entire boot log below:
https://pastebin.com/raw/275JPvZB
--
Regards,
Sreyan Chakravarty
3 years, 5 months
