Dunno when and why this started recently, but I'm hit hard by segfaults
taking down GNOME Shell.
Bugzilla knows tons of duplicate bug reports about it, dating back to
OsLookupColor(): Segmentation fault at address 0x...
Has anyone seen this earlier and knows a workaround perhaps?
F30 isn't usable anymore due to those crashes.
After I connected the new scanner to the USB port and ran 'xsane', it
showed 'no devices available'. But if I run 'lsusb' it is getting this
Bus 001 Device 005: ID 04a9:12fe Canon, Inc
I downloaded the driver from this link:
And the driver scangearmp2-3.70-1.x86_64.rpm was installed.
But still 'xsane' is not finding it but 'lsusb' is showing it.
Can I do anything here? Thanks in advance.
I was trying to install the InventorLoader addon for FreeCAD and it
requires three python modules to install.
xlrd, xlwt and xlutils
xlrd and xlwt are available through DNF, xlutils isn't.
I saw it mentioned in an old bug report but nothing more.
I would like to request that this package be added.
I installed the ccache package on F30. Doing a rpm -ql on the
package show a long list of files that are part of the package, but if I do
ls -l /usr/lib64/ccache/
-rwxr-xr-x. 1 root root 193392 Jan 31 07:23 cc
-rwxr-xr-x. 1 root root 193392 Jan 31 07:23 gcc
-rwxr-xr-x. 1 root root 193392 Jan 31 07:23 x86_64-redhat-linux-gcc
where are all the other files, e.g. /usr/lib64/ccache/c++?
Today while working on one of my client i realized that it is possible to delete one self by the user who is logged in using
->ipa user-del 'user' command
I found out that it can be avoided by adding a function for protecting deletion of any logged in user in the user.py file under the claa user_del
However i could not find out any way to get the details of any or all the logged in user.
Can anyone tell me how to deal with this??
Hello, reported some time ago about an issue with Vagrant in F30 with
the topic above.
Didn't have the original email left (since no-one answered), so will
post an update.
The latest (2.2.5) version of Vagrant released by Hashicorp, which is
not yet available from Fedora, fixed the issue. I used the CentOS
package to update the installed one.
Just a FYI in case you run into similar issues.
Writing a new message always starts the format in "Pararaph" mode
instead of "Body Text"
And this leads to the messages being double spaced.
How can I change it so it will default to Body Text every time?
(f29; gnome; Firefox 68.0; all patched late this morning)
While trying to sign on to a financial institution's web site, when I
start to enter the password, the cpu suddenly gets extremely busy and
stays that way. I had to hit the power button. Upon booting up again,
I launched ksysguard, and then re-tried the login. Again I saw the cpu
essentially max out. I had to hit the power button. Upon booting up, I
launched "top" in a terminal, and then retried the login. Again the cpu
essentially maxed out. "top" showed that gnome was the cpu hog.
I again hit the power button and booted up. This time I logged in to a
plasma session. I was able to log in and do what I had to do with no
This one is really strange. How do I determine what the problem is?
This problem did not occur before today's "dnf upgrade". The last
patching before today was last Thursday.
I am working on my non-working wifi now. The last critical item (I hope).
Just installing the broadcom-wl rpm got the card recognized, and I am
seeing SSIDs, but cannot connect. Perhaps some setting needed.
So I figure to start I need to know what card F30 thinks I have. Win10's
driver for this unit is BCMWL63a.
I can't find my old notes on how to list information about the card itself.