NetBeans problem - related to Flatpak?
by Matti Pulkkinen
Hello!
I've run into a problem with NetBeans and Maven. Maven will start
downloading and processing its central repository index, and the
process will fail with a message saying the device ran out of space.
I've monitored resources while this is going on, and my computer runs
out of neither RAM nor storage space while this is happening.
Now I know this isn't a Fedora package (it's from Flathub; NetBeans
isn't available in Fedora) so I'm not asking for support here
necessarily. I'm just wondering whether this issue could be caused by
Flatpak. Does Flatpak somehow space-constrain applications? This would
be nice to know before I go trying to report the issue to Apache
because the Flatpak is not officially distributed or supported by
Apache.
--
Terveisin / Regards,
Matti Pulkkinen
3 years, 2 months
Bad JSON format for 'lshw'
by Digimer
I tried to submit this as a ticket to
https://ezix.org/project/newticket#ticket but it wouldn't accept the
captcha test. Posting here in case I can get to the 'lshw' dev (or
package maintainer) through Fedora. This is tested on Fedora 33 (and
CentOS Stream 8, fwiw).
I'm working on a program to process lshw data, and the XML data is fine,
but the JSON output format is invalid.
Example in XML;
# lshw -class disk -class storage -xml
====
<?xml version="1.0" standalone="yes" ?>
<!-- generated by lshw-B.02.19.2 -->
<!-- GCC 10.2.1 20200723 (Red Hat 10.2.1-1) -->
<!-- Linux 5.10.21-200.fc33.x86_64 #1 SMP Mon Mar 8 00:24:40 UTC 2021
x86_64 -->
<!-- GNU libc 2 (glibc 2.32) -->
<list>
<node id="nvme" claimed="true" class="storage" handle="PCI:0000:55:00.0">
<description>NVMe device</description>
<product>INTEL SSDPEKNW020T9</product>
<vendor>Intel Corporation</vendor>
<physid>0</physid>
<subproduct>Intel Corporation</subproduct>
<subvendor>Intel Corporation</subvendor>
<businfo>pci@0000:55:00.0</businfo>
<logicalname>/dev/nvme0</logicalname>
<version>001C</version>
<serial>xxxxx</serial>
<width units="bits">64</width>
<clock units="Hz">33000000</clock>
<configuration>
<setting id="driver" value="nvme" />
<setting id="latency" value="0" />
<setting id="nqn"
value="nqn.2010-01.com.intel:nvm-subsystem-sn-btnr00161vch2p0c" />
<setting id="state" value="live" />
</configuration>
<capabilities>
<capability id="nvme" />
<capability id="pm" >Power Management</capability>
<capability id="msi" >Message Signalled Interrupts</capability>
<capability id="pciexpress" >PCI Express</capability>
<capability id="msix" >MSI-X</capability>
<capability id="nvm_express" />
<capability id="bus_master" >bus mastering</capability>
<capability id="cap_list" >PCI capabilities listing</capability>
</capabilities>
<resources>
<resource type="irq" value="16" />
<resource type="memory" value="ae100000-ae103fff" />
</resources>
<hints>
<hint name="icon" value="disc" />
<hint name="pci.class" value="0x108" />
<hint name="pci.device" value="0xFAF0" />
<hint name="pci.subdevice" value="0x390E" />
<hint name="pci.subvendor" value="0x8086" />
<hint name="pci.vendor" value="0x8086" />
</hints>
<node id="namespace" claimed="true" class="disk"
handle="GUID:766cd8a2-26c2-4983-9f02-60817e74f3a5">
<description>NVMe disk</description>
<physid>1</physid>
<businfo>nvme@0:1</businfo>
<logicalname>/dev/nvme0n1</logicalname>
<size units="bytes">2048408248320</size>
<configuration>
<setting id="guid" value="766cd8a2-26c2-4983-9f02-60817e74f3a5" />
<setting id="logicalsectorsize" value="512" />
<setting id="sectorsize" value="512" />
<setting id="wwid" value="eui.0000000001000000e4d25c2316cf5101" />
</configuration>
<capabilities>
<capability id="gpt-1.00" >GUID Partition Table version
1.00</capability>
<capability id="partitioned" >Partitioned disk</capability>
<capability id="partitioned:gpt" >GUID partition table</capability>
</capabilities>
<hints>
<hint name="guid" value="766cd8a2-26c2-4983-9f02-60817e74f3a5" />
<hint name="icon" value="disc" />
<hint name="partitions" value="0x80" />
</hints>
</node>
</node>
</list>
====
Same in JSON;
# lshw -class disk -class storage -json
====
{
"id" : "nvme",
"class" : "storage",
"claimed" : true,
"handle" : "PCI:0000:55:00.0",
"description" : "NVMe device",
"product" : "INTEL SSDPEKNW020T9",
"vendor" : "Intel Corporation",
"physid" : "0",
"businfo" : "pci@0000:55:00.0",
"logicalname" : "/dev/nvme0",
"version" : "001C",
"serial" : "BTNR00161VCH2P0C",
"width" : 64,
"clock" : 33000000,
"configuration" : {
"driver" : "nvme",
"latency" : "0",
"nqn" : "nqn.2010-01.com.intel:nvm-subsystem-sn-btnr00161vch2p0c",
"state" : "live"
},
"capabilities" : {
"nvme" : true,
"pm" : "Power Management",
"msi" : "Message Signalled Interrupts",
"pciexpress" : "PCI Express",
"msix" : "MSI-X",
"nvm_express" : true,
"bus_master" : "bus mastering",
"cap_list" : "PCI capabilities listing"
},
"children" : [
{
"id" : "namespace",
"class" : "disk",
"claimed" : true,
"handle" : "GUID:766cd8a2-26c2-4983-9f02-60817e74f3a5",
"description" : "NVMe disk",
"physid" : "1",
"businfo" : "nvme@0:1",
"logicalname" : "/dev/nvme0n1",
"units" : "bytes",
"size" : 2048408248320,
"configuration" : {
"guid" : "766cd8a2-26c2-4983-9f02-60817e74f3a5",
"logicalsectorsize" : "512",
"sectorsize" : "512",
"wwid" : "eui.0000000001000000e4d25c2316cf5101"
},
"capabilities" : {
"gpt-1.00" : "GUID Partition Table version 1.00",
"partitioned" : "Partitioned disk",
"partitioned:gpt" : "GUID partition table"
},
"children" : [
]
}
]
====
--
Digimer
Papers and Projects: https://alteeve.com/w/
"I am, somehow, less interested in the weight and convolutions of
Einstein’s brain than in the near certainty that people of equal talent
have lived and died in cotton fields and sweatshops." - Stephen Jay Gould
3 years, 2 months
speed of dd
by Tim
When I do something like:
dd if='fedora.iso' of=/dev/sdb status=progress
I only get around 6 megabytes per second on a USB 2 Sandisk Cruzer
Blade flashdrive (store bought, not fleabay) plugged directly into a
motherboard's USB 3 port - one that's not sharing its host with any
other ports in use.
Surely it should be going a lot faster?
When plugged in, dmesg shows this for the drive:
[337595.365826] usb 1-4: new high-speed USB device number 24 using xhci_hcd
[337595.489415] usb 1-4: New USB device found, idVendor=0781, idProduct=5567, bcdDevice= 1.00
[337595.489426] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[337595.489433] usb 1-4: Product: Cruzer Blade
[337595.489439] usb 1-4: Manufacturer: SanDisk
[337595.489445] usb 1-4: SerialNumber: 00007014102520061826
[337595.557718] usb-storage 1-4:1.0: USB Mass Storage device detected
[337595.557933] scsi host6: usb-storage 1-4:1.0
[337595.557995] usbcore: registered new interface driver usb-storage
[337595.560673] usbcore: registered new interface driver uas
[337596.561807] scsi 6:0:0:0: Direct-Access SanDisk Cruzer Blade 1.00 PQ: 0 ANSI: 6
[337596.562686] sd 6:0:0:0: Attached scsi generic sg2 type 0
[337596.563276] sd 6:0:0:0: [sdb] 60088320 512-byte logical blocks: (30.7 GB/28.6 GiB)
[337596.564047] sd 6:0:0:0: [sdb] Write Protect is off
[337596.564057] sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00
[337596.564305] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[337596.584964] sdb: sdb1
[337596.586991] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[337609.674186] usb 1-11: USB disconnect, device number 19
--
uname -rsvp
Linux 3.10.0-1160.15.2.el7.x86_64 #1 SMP Wed Feb 3 15:06:38 UTC 2021 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
3 years, 2 months
Configuring a Fedora 33 system as NAS
by Robert McBroom
After a painful experience of the lack of support of a Seagate Goflex
Home never updated from smb1, and finding the inadequacies of a WD
MyCloudUltra2, I'm ready to tackle configuring an older Dell system as
the NAS for my network. What do I need to configure besides NFS and smb
servers?
3 years, 2 months
konqueror fails
by Michael Hennebry
I recently installed konqueror on F33 with gnome.
Gnome seems to not know of it.
The problem seems to be:
kf.service.services: The desktop entry file
"/usr/share/applications/org.gnome.ChromeGnomeShell.desktop" has Type="Application" but no Exec line
a message I get starting it from the command line.
There are other errors, e.g. QWaylandGLContext: failed to create EGLContext, error=3009
Eventually konqueror aborts.
ps a
includes
358792 tty3 Ssl+ 0:00 /usr/libexec/gdm-wayland-session /usr/bin/gnome-ses
so I infer I am running wayland.
How do I run konqueror?
I also have to run brasero from the command line, bit it works.
--
Michael hennebry(a)web.cs.ndsu.NoDak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
-- someeecards
3 years, 2 months
Can't burn a CentOS 7.9 DVD
by Robert G. (Doc) Savage
Is the CentOS-7-x86_64-DVD-2009.iso really too big to burn on a DVD-R?
Brasero under Centos 7.9 and Fedora 33 both say a 4.7GB blank disk
isn't big enough.
--Doc Savage
Fairview Heights, IL
3 years, 2 months
A question about Wine in fedora
by Francisco Tissera
Hello everyone,
I am having this problem where, when I try to launch a Windows
application with Wine, this happens.
Xlib: extension "NV-GLX" missing on display ":1".
Xlib: extension "NV-GLX" missing on display ":1".
MESA-INTEL: warning: Performance support disabled, consider sysctl
dev.i915.perf
_stream_paranoid=0
What is this? has anyone experienced this before? if so, how do I fix it?
Thank you for any answers.
Best regards.
Francisco.
3 years, 2 months
dnf dkms interaction
by Robert McBroom
When updating the kernel, dnf tries to use dkms to add my NVIDIA
drivers, For some reason it tries to use 390.129 instead of the current
390.141 driver. The manual install works.
/var/lib/dkms/nvidia:
total used in directory 20 available 57.5 GiB
drwxr-xr-x. 5 root root 4096 Mar 12 23:44 .
drwxr-xr-x. 6 root root 4096 Dec 18 01:36 ..
drwxr-xr-x. 5 root root 4096 Jan 29 2020 390.129
drwxr-xr-x. 3 root root 4096 Mar 12 23:44 390.141
drwxr-xr-x. 5 root root 4096 Nov 1 2019 390.77
lrwxrwxrwx. 1 root root 38 Mar 12 23:44
kernel-5.10.22-200.fc33.x86_64-x86_64 ->
390.141/5.10.22-200.fc33.x86_64/x86_64
lrwxrwxrwx. 1 root root 37 Oct 17 2019
kernel-5.2.18-100.fc29.x86_64-x86_64 ->
390.129/5.2.18-100.fc29.x86_64/x86_64
lrwxrwxrwx. 1 root root 37 Nov 22 2019
kernel-5.3.11-300.fc31.x86_64-x86_64 ->
390.129/5.3.11-300.fc31.x86_64/x86_64
Is it looking for just one entry here? Perhaps the installer is not
cleaning the directory.
Thoughts?
3 years, 2 months
