x11 and the mouse
by ToddAndMargo
Hi All,
Fedroa 29, x64
Xfce 4.13
Is there an X11 (not Xfce's settings) setting out there
somewhere for how the mouse behaves?
Many thanks,
-T
5 years
f29 iso customization : value of inst.stage2 and iso re-packaging
by Adrian Sevcenco
Hi! I would like to customize the iso net-install of f29
by pointing the inst.stage2 to a local http location but i do not find
a reliable point of information ...
looking over
https://docs.fedoraproject.org/en-US/fedora/f29/install-guide/advanced/Bo...
i see :
"This option expects a path to a directory containing a valid .treeinfo
file; the location of the runtime image will be read from this file if
found. If a .treeinfo file is not available, Anaconda will try to load
the image from LiveOS/squashfs.img."
but the f29 net-install image does not have .treeinfo file, not LiveOS
directory nor squashfs.img (it have an install.img)
So, how can i point inst.stage2 to a location containing install.img?
Also, i fail to find a method to repackage back the iso..
Any idea if the el7 method (with mkisofs) would work the same ?
Thank you!
Adrian
5 years
clean-up after upgrade.
by home user
Good afternoon,
A short while ago, I upgraded from f28 to f29. One post-upgrade step suggested by the upgrade instructions is:
-----
bash.3[~]: dnf list extras
Last metadata expiration check: 0:32:03 ago on Thu 18 Apr 2019 02:01:12 PM MDT.
Extra Packages
clutter-gst.x86_64 1.6.0-20.fc28 @fedora
clutter-gst2.x86_64 2.0.18-5.fc28 @fedora
compat-libicu57.x86_64 57.1-2.fc28 @fedora
eclipse-emf-query.noarch 1.10.0-5.fc28 @fedora
eclipse-emf-validation.noarch 1.10.0-5.fc28 @fedora
eclipse-fedorapackager.noarch 0.6.0-4.fc28 @fedora
eclipse-mdt-ocl.noarch 6.2.1-4.fc28 @fedora
eclipse-mdt-uml2.noarch 5.2.3-3.fc28 @fedora
gegl.x86_64 0.2.0-38.fc28 @fedora
java-9-openjdk.x86_64 1:9.0.4.11-6.fc28 @fedora
java-9-openjdk-headless.x86_64 1:9.0.4.11-6.fc28 @fedora
kernel.x86_64 5.0.6-100.fc28 @updates
kernel.x86_64 5.0.7-100.fc28 @updates
kernel-core.x86_64 5.0.6-100.fc28 @updates
kernel-core.x86_64 5.0.7-100.fc28 @updates
kernel-debug-devel.x86_64 5.0.6-100.fc28 @updates
kernel-debug-devel.x86_64 5.0.7-100.fc28 @updates
kernel-devel.x86_64 5.0.6-100.fc28 @updates
kernel-devel.x86_64 5.0.7-100.fc28 @updates
kernel-modules.x86_64 5.0.6-100.fc28 @updates
kernel-modules.x86_64 5.0.7-100.fc28 @updates
kmod-nvidia-5.0.6-100.fc28.x86_64.x86_64 3:418.56-1.fc28 @@commandline
kmod-nvidia-5.0.7-100.fc28.x86_64.x86_64 3:418.56-1.fc28 @@commandline
kmod-nvidia-5.0.7-200.fc29.x86_64.x86_64 3:418.56-1.fc29 @@commandline
libXevie.x86_64 1.0.3-14.fc27 @fedora
libgit2.x86_64 0.27.8-1.fc29 @updates
lucene4.noarch 4.10.4-12.fc28 @fedora
mozjs24.x86_64 24.2.0-11.fc26 @@commandline
python2-pygpgme.x86_64 0.3-26.fc28 @fedora
bash.4[~]:
-----
My grub menu does include the last 2 patches. In the above output, I see kmod-nvidia and kernel entries. Is is safe for me to the
"dnf remove $dnf repoquery --extras --exclude=kernel,kernel-\*)
as suggested by the upgrade instructions?
Thank-you,
Bill.
5 years
Re: Problems with plank settings app
by Frank McCormick
On 2019-04-20 4:08 p.m., Samuel Sieb wrote:
> On 4/20/19 9:49 AM, Frank McCormick wrote:
>> In installed the dock plank on my Fedora 29 installation this
>> morning, then found
>>
>> a python-based plank settings app.
>
> Where did you find it? You will need to file a bug there.
That I have done.
>
>> I suspect it's related to Apples threat to Plank developers over use
>> of the icon zoom property
>>
>> which the fruit company has apparently patented ?? Plank is reported
>> to have removed the zoom option,
>
> This is why software patents need to be eliminated:
> http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PALL&...
>
> (Patent number 7,434,177)
>
>> Is there a work around? I don't particularly care about the zoom
>> function eye-candy but
>>
>> it would be nice to be able to use the settings app.
>
> Until upstream fixes the app, you can either edit the python code to
> remove that part or modify the schema file to include that setting.
> _______________________________________________
I edited the schema file, which I then recompiled and it now works.
No actual zoom as I suspect
the authors pulled that part of the code.
Thanks
Frank
5 years
What is a "CHESEN"?
by ToddAndMargo
$ xinput --list --short | grep -i chesen
⎜ ↳ CHESEN PS2 to USB Converter Mouse id=17 [slave pointer (2)]
↳ CHESEN PS2 to USB Converter id=16 [slave keyboard (3)]
↳ CHESEN PS2 to USB Converter System Control id=18 [slave keyboard
(3)]
↳ CHESEN PS2 to USB Converter Consumer Control id=19 [slave
keyboard (3)]
5 years
Problems with plank settings app
by Frank McCormick
In installed the dock plank on my Fedora 29 installation this morning,
then found
a python-based plank settings app.
However it does not work with Fedora's version of plank (0.11.4).
The settings app gives this error:
(planksetting.py:6935): GLib-GIO-ERROR **: 12:41:28.299: Settings schema
'net.launchpad.plank.dock.settings' does not contain a key named
'zoom-enabled'
/usr/bin/planksetting14: line 1: 6935 Trace/breakpoint trap (core
dumped) python3 /usr/share/planksetting/planksetting.py
I suspect it's related to Apples threat to Plank developers over use of
the icon zoom property
which the fruit company has apparently patented ?? Plank is reported to
have removed the zoom option,
Is there a work around? I don't particularly care about the zoom
function eye-candy but
it would be nice to be able to use the settings app.
Thanks
5 years
Feature request : Vivaldi
by Beartooth
I tried installing Vivaldi from its own site, used it a few
weeks, and liked it immensely. Then I happened to discover that it was
not available via dnf. With copious bad memories of dependency hells, and
despite great reluctance, I gave it up. I still miss it. Couldn't it be
added to one or another of the Fedora repos??
--
Beartooth Staffwright, Not Quite Clueless Power User
Remember I know little (precious little!) of where up is.
5 years
why dnf wants to reinstall to same version ?
by sean darcy
FC29. I have a server for video encoding. I use x264, which I keep
updated to the most recent git packaaged in an rpm.
rpm -q x264-libs
x264-libs-0.157-0.20190331.fc29.x86_64
I then rebuild all the packages that depend on x264, including
avidemux-libs. I just rebuild on my machine, without chaging the
version, since the version hasn't changed, it's just linked to the new
x264 version.
rpm -q avidemux-libs
avidemux-libs-2.7.3-1.fc29.x86_64
But dnf want to replace my rebuild version, with the version for the repo:
dnf upgrade --refresh
..............
Problem 1: package avidemux-libs-2.7.3-1.fc29.x86_64 requires
libx264.so.155()(64bit), but none of the providers can be installed
- cannot install both
x264-libs-0.155-2.20180806git0a84d98.fc29.x86_64 and
x264-libs-0.157-0.20190331.fc29.x86_64
I don't want to bump the avidemux-libs version, since I want to know
when a new one is available. I don't want to keep adding "-x avidemux.."
Why does dnf want to replace the installed package ? How does it even
know it's not the same package as the repo ?
sean
5 years
Feature request: pre-tweaking
by Beartooth
Whenever I do a fresh install (preferably a net install or one
from a live medium -- they're smaller), as soon as I reboot into it and
update it, I launch dnfdragora and go through, first, all the apps I know
I don't need, or hope I won't. (When in doubt, I hit Apply often and read
through the resulting list with great care.)
That done, I start over, this time looking for things I know or
hope I will want. By the time I've done both, I've pretty well killed a
day, often two.
And then I still have to do the other half: arranging panels,
icons, and the like into places where my fingers can find them, without
taking what's left of my mind off what it's doing.
As an old retired fart blissfully unconcerned with production of
anything, I can afford all this; but it's gawdawful tedious. If there's a
better way that a non-technoid can use, somebody please clue me in!
If I could have my druthers, I'd like some snapshot that would
record my tweaks shortly before a fresh install, and write them to a
temporary external medium. Then after the fresh install, it would check
as best it could, show me the changes, and offer to carry them out.
I realize such a tool could never be perfect. There will always
be new releases of one standby or another, and other bigger changes that
give the May or November release of Fedora good reason for taking a new
number. Nevertheless, there are also mature apps, such as mailers and
list servers, that some of us want and some of us don't, which change
only slowly. There are terminal tabs, font sizes, locations of launchers,
and so forth and so on. The tool I'm wish-dreaming of would seize *my*
tweaks and carry them over to feed into the new install.
All this or something like it happens now with an upgrade, and
may the developers be blessed above all nations for making it the
preferred way! But sometimes for instance I replace a machine ....
--
Beartooth Staffwright, Historian of Tongues
Squirreler, Double Retiree, Linux Evangelist
5 years
