RIP Fedora?
by Phil Neck
Okay ... now I have your attention ...
A funny thing happened to me the other day ...
I tried upgrading a Fedora 22 VM which was running on about 30 different
VMware architectures to Fedora 23. All but a couple worked perfectly but a
couple (Both Dell servers) didn't. On these I can only describe what I was
seeing as '64-bitty' problems ... checksums failing ... that kind of thing.
I then had the idea of trying to build the machine 'from scratch' using a
Fedora 25 CD image. Similar results ... the machines the original 22-23
convertion worked on went fine, but the other two ... no dice. They
wouldn't even load beyond initial kernel boot and into install screen.
I thought best to start at the bottom and work up, so spoke to Dell ...
they had no reports of problems with their machines and VMware (yeah ... I
know ... they never do ... but)
Then spoke to VMWare to be told:
=========================
"My name is gfdgfdgfdg and I will be working with you to resolve your issue
for Support Request 7657576576576.
I understand from your case description that Fedora 25 64 bit VM won't
boot.
Please find the list of the supported OS on the ESXi host. Fedora is not
supported on ESXi but rather on Workstation and Fusion.
https://partnerweb.vmware.com/comp_guide2/pdf/VMware_GOS_Compatibility_Gu...
If you are using Workstation or Fusion, please raise a case with the
concerned team to assist you however its not supported as a guest OS on
ESXi.
Let me know if you have any questions or if we are good to close the case
for now.
==========================
I appreciate that this note is low on technical facts (by design). because
I'm not really as as interested in the technical minucia of the problem, as
the more general situation. Can anyone explain what changed between FC22
and FC23? What caused VMware to drop support? Is there any practical way
around this?
I have hundreds of Fedora based VMs out there running versions from
'stoneage' to the latest, all working fine EXCEPT those on the two machines
mentioned.
I have a heck of a decision to make in the in the next few days, but it
sounds like its going to be RIP Fedora :(
Any insight most gratefully appreciated
Thanks
Phil.
7 years, 4 months
Display setting problem with 4k monitor
by Massimo Canonico
Hi all,
I've bought a new laptop (Dell xps 13.3) and the monitor resolution is
3200x1800. Now the problem is that I cannot use this laptop with my
external monitor which I use as an extended monitor. The external
monitor could reach 1280x1024. So when I try to move a window from the
laptop monitor to the external monitor, it appears too big.
I haven't this problem with my previous dell xps and what it is more
important, if I run an Ubuntu live distro, I can see various setting to
manage displays such as "windows scaling" where I can adjust the windows
sizes.
So,
- why fedora does not provide the same setting as Ubuntu? Ubuntu
proposes many different resolutions and specific window scaling for the
two monitors.
- is there something that I can do in fedora?
I really do no want switch to Ubuntu after more than 20 years with fedora.
After my signature the xrandr output.
Thanks,
Massimo
Screen 0: minimum 320 x 200, current 4480 x 1800, maximum 8192 x 8192
eDP-1 connected primary 3200x1800+0+0 (normal left inverted right x axis
y axis) 294mm x 165mm
3200x1800 59.98*+ 47.99
2048x1536 60.00
1920x1440 60.00
1856x1392 60.01
1792x1344 60.01
1600x1200 60.00
1400x1050 59.98
1280x1024 60.02
1280x960 60.00
1024x768 60.04 60.00
960x720 60.00
928x696 60.05
896x672 60.01
800x600 60.00 60.32 56.25
700x525 59.98
640x512 60.02
640x480 60.00 59.94
512x384 60.00
400x300 60.32 56.34
320x240 60.05
DP-1 connected 1280x1024+3200+0 (normal left inverted right x axis y
axis) 338mm x 270mm
1280x1024 60.02*+ 75.02
1152x864 75.00
1024x768 75.03 60.00
832x624 74.55
800x600 75.00 60.32
640x480 75.00 59.94
720x400 70.08
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)
7 years, 4 months
Re: DNF install of tesseract fails w call to old lib,> dependency
by R. G. Newbury
On 01/23/2017 09:47 PM, Greshko <ed.greshko(a)greshko.com>
>> On 01/24/17 06:43, R. G. Newbury wrote:
>> I used tesseract in an ocr script on F24 last year. Worked well
>> Did a new install of F25, including a dnf install of tesseract, ( and leptonica and
>> leptonica-devel which are actually dependencies)
>>
>> tesseract fails, calling for liblept.so.3
>> I did a dnf upgrade of all three, just to be sure, but
> I have a new install of F25 in a VM (KDE). I did not have to install tesseract as it was
> already installed.
PEBKAC!
I think I had my rpmfusion.repo turned off, so no match found. I then
tried installing from sourceforge, which installed to /usr/local/bin.
And which was apparently an older version???
Of course, /usr/local/bin is ahead of /usr/bin, so the dnf re-install
did nothing visible!
Delete and re-install fixed things..
Thanks! It was the 'ldd /usr/bin/tesseract' which triggered a search.
Geoff
7 years, 4 months
gnome-shell, wayland problem with gnome-ssh-askpass
by Brian Millett
Hello,
My system:
description: Laptop
product: Inspiron 13-5368 (073B)
vendor: Dell Inc.
width: 64 bits
capabilities: smbios-2.8 dmi-2.8 smp vsyscall32
configuration: boot=normal chassis=docking sku=073B uuid=44454C4C-
5700-1035-8043-B6C04F564232
*-core
description: Motherboard
vendor: Dell Inc.
physical id: 0
version: A00
Linux 4.9.3-200.fc25.x86_64 #1 SMP Fri Jan 13 01:01:13 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
I running gnome3 NO X11 and I have setup keychain to run at launch of a
terminal for the ssh agent. Have set the variable:
GPG_TTY=/usr/libexec/openssh/gnome-ssh-askpass
I have also used gnome-tweak-tool to have the gnome-terminal autostart,
as well as nautilus.
PROBLEM:
When I login, the screen is blank. Nothing shows, the mouse is frozen,
nothing. However, if I type my passphrase for my ssh key (assuming
that the asskpass window is active) then after entering the return key,
the desktop become responsive and finishes logging me in.
When I set the desktop to be Gnome - X11, then the askpass window
displays and all is good.
When the desktop is set to Gnome (wayland), then the askpass windows
does not display, but it is waiting for keyboard entry.
Reading it looks like the DISPLAY is not yet set.
Is there a way (other than not autostarting the terminal) to delay the
askpass dialog till a DISPLAY is set? Or any other ideas?
Thanks.
--
Brian Millett
"Beep. Beep."
-- [ Garibaldi (to G'Kar), "The Gathering"]
7 years, 4 months
sagemath and perl
by Patrick Dupre
Hello,
Trying to update perl (to 4:5.22.3-367.fc24) I get:
Skipping packages with broken dependencies:
because
sagemath-6.8-14.fc24.x86_64
How can I avoid the issue?
by Recompiling sagemath? after the update?
Thank.
Regards.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
7 years, 4 months
alt+tab program groups
by Philippe LeCavalier
Anyone else loose grouping by programs after upgrading? Where do I find the
setting for that?
--
Regards,
Phil
7 years, 4 months
DNF install of tesseract fails w call to old lib dependency
by R. G. Newbury
I used tesseract in an ocr script on F24 last year. Worked well
Did a new install of F25, including a dnf install of tesseract, ( and
leptonica and leptonica-devel which are actually dependencies)
tesseract fails, calling for liblept.so.3
I did a dnf upgrade of all three, just to be sure, but
# tesseract
tesseract: error while loading shared libraries: liblept.so.3: cannot
open shared object file: No such file or directory
# cd /usr/lib64
# ls -al liblept*
lrwxrwxrwx 1 root root 16 Jan 3 06:08 liblept.so -> liblept.so.5.0.1
lrwxrwxrwx 1 root root 16 Jan 3 06:08 liblept.so.5 -> liblept.so.5.0.1
-rwxr-xr-x 1 root root 2552880 Jan 3 06:08 liblept.so.5.0.1
# ln -s liblept.so.5.0.1 liblept.so.3
# ls -al liblept*
lrwxrwxrwx 1 root root 16 Jan 3 06:08 liblept.so -> liblept.so.5.0.1
lrwxrwxrwx 1 root root 16 Jan 23 17:25 liblept.so.3 -> liblept.so.5.0.1
lrwxrwxrwx 1 root root 16 Jan 3 06:08 liblept.so.5 -> liblept.so.5.0.1
-rwxr-xr-x 1 root root 2552880 Jan 3 06:08 liblept.so.5.0.1
# tesseract
Segmentation fault (core dumped)
Creating a linked version of liblept.so.3 cause a seg fault!
Interestingly, I get the same 'missing liblept.so.3' error on f23, but
creating the linked version (against liblept.so.4.0.3 works.
tesseract is: 3.04.01-2.fc25
leptonica is: 1.74.1-1.fc25
(On the F23 laptop those are 3.02.02 and 1.72 respectively.
Anyone have any ideas on what/why this fails, and how to fix it?
Geoff
7 years, 4 months
Wifi - wrong speed reported
by Winfried de Heiden
Hi all,
Using Fedora 25 on my laptop I found out it supports 5ghz. Great, some
more speed, since the 2.4ghz band is a bit crowded in my
neighboorhood....
However, both NetworkManager an iwconfig report only a poor 6m...:
wconfig wlp3s0
wlp3s0 IEEE 802.11 ESSID:"<very secret>"
Mode:Managed Frequency:5.26 GHz Access Point:
<xx:xx:xx:xx:xx:xx>
Bit Rate=6 Mb/s Tx-Power=20 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
Link Quality=65/70 Signal level=-45 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Can't be that bad.... Luckily, my (Fritz) access point reports a
healthy 650 Mb. Also, downloading a large file goes easily 2x faster
from what you would expect from reported transfer rate.
I noticed this behaviour before, reporting only 1 MB on an older
laptop.
What's happening here? I look a bit like large number (>100 Mb) is cut
of to only the first digit. Anyone seen this before? How to handle?
Some details about my wireless nic:
03:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
Network Adapter (rev 32)
Subsystem: Bigfoot Networks, Inc. Device 1535
Flags: bus master, fast devsel, latency 0, IRQ 129
Memory at df200000 (64-bit, non-prefetchable) [size=2M]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Virtual Channel
Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-
00
Capabilities: [178] Latency Tolerance Reporting
Capabilities: [180] L1 PM Substates
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
Winfried
7 years, 4 months
Wifi - wrong speed reported
by Winfried de Heiden
Hi all,
Using Fedora 25 on my laptop I found out it supports 5ghz. Great, some
more speed, since the 2.4ghz band is a bit crowded in my
neighboorhood....
However, both NetworkManager an iwconfig report only a poor 6m...:
wconfig wlp3s0
wlp3s0 IEEE 802.11 ESSID:"<very secret>"
Mode:Managed Frequency:5.26 GHz Access Point:
<xx:xx:xx:xx:xx:xx>
Bit Rate=6 Mb/s Tx-Power=20 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
Link Quality=65/70 Signal level=-45 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Can't be that bad.... Luckily, my (Fritz) access point reports a
healthy 650 Mb. Also, downloading a large file goes easily 2x faster
from what you would expect from reported transfer rate.
I noticed this behaviour before, reporting only 1 MB on an older
laptop.
What's happening here? I look a bit like large number (>100 Mb) is cut
of to only the first digit. Anyone seen this before? How to handle?
Some details about my wireless nic:
03:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
Network Adapter (rev 32)
Subsystem: Bigfoot Networks, Inc. Device 1535
Flags: bus master, fast devsel, latency 0, IRQ 129
Memory at df200000 (64-bit, non-prefetchable) [size=2M]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Virtual Channel
Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-
00
Capabilities: [178] Latency Tolerance Reporting
Capabilities: [180] L1 PM Substates
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
Winfried
7 years, 4 months
