>No, I refer to your 3rd message in this thread, where you wrote:
OK you wont know what happened when I installed the new dconf-Editor....
This is the complete output that I got then ....:
------------------------------
[angelo_dev@zorro Downloads]$ sudo yum install dconf-editor-0.15.0-4mgc30.x86_64.rpm
[sudo] password for angelo_dev:
Loaded plugins: langpacks, refresh-packagekit
Examining dconf-editor-0.15.0-4mgc30.x86_64.rpm: dconf-editor-0.15.0-4mgc30.x86_64
Marking dconf-editor-0.15.0-4mgc30.x86_64.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package dconf-editor.x86_64 0:0.15.0-4mgc30 will be installed
--> Processing Dependency: dconf = 0.15.0-4mgc30 for package: dconf-editor-0.15.0-4mgc30.x86_64
--> Finished Dependency Resolution
Error: Package: dconf-editor-0.15.0-4mgc30.x86_64 (/dconf-editor-0.15.0-4mgc30.x86_64)
Requires: dconf = 0.15.0-4mgc30
Installed: dconf-0.18.0-2.fc20.x86_64 (@koji-override-0/$releasever)
dconf = 0.18.0-2.fc20
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
------------------------------
End.. if I still try to install dconf-editor-0.15.0-4mgc30.x86_64.rpm OK you wont know what happened when I installed the new dconf-Editor....
This is the complete output that I got then ....:
------------------------------
[angelo_dev@zorro Downloads]$ sudo yum install dconf-editor-0.15.0-4mgc30.x86_64.rpm
[sudo] password for angelo_dev:
Loaded plugins: langpacks, refresh-packagekit
Examining dconf-editor-0.15.0-4mgc30.x86_64.rpm: dconf-editor-0.15.0-4mgc30.x86_64
Marking dconf-editor-0.15.0-4mgc30.x86_64.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package dconf-editor.x86_64 0:0.15.0-4mgc30 will be installed
--> Processing Dependency: dconf = 0.15.0-4mgc30 for package: dconf-editor-0.15.0-4mgc30.x86_64
--> Finished Dependency Resolution
Error: Package: dconf-editor-0.15.0-4mgc30.x86_64 (/dconf-editor-0.15.0-4mgc30.x86_64)
Requires: dconf = 0.15.0-4mgc30
Installed: dconf-0.18.0-2.fc20.x86_64 (@koji-override-0/$releasever)
dconf = 0.18.0-2.fc20
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
------------------------------
I (always) continue to have this output..
On Wed, Oct 15, 2014 at 12:35 PM, Michael Schwendt <mschwendt@xxxxxxxxx> wrote:
On Wed, 15 Oct 2014 10:23:03 +0300, Angelo Moreschini wrote:
> I installed fedora 20 not long ago, and now I'm customizing the
> installation by adding programs not included by default in the installation.
Just don't download programs from arbitrary web sites. Prefer sticking
to official package repositories and well-known 3rd party add-on repositories.
> ....at the same time that I installed dconf-editor, I also installed "Tweak
> Tool" and "menulibre"; this fact can be relevant?
Well, if you really want to attempt at doing some trouble-shooting, start
with basic steps such as trying to reproduce the problem with a fresh user
account, without becoming superuser, with something else than GNOME Shell
(e.g. a simple window manager such as Openbox - it is fairly convenient to
install that from Fedora's repos and log in into it, too).
> > Where is the error you've mentioned in the previous mail?
>
> I'll explain what I can think about can be problematic:
No, I refer to your 3rd message in this thread, where you wrote:
| [...] have now on my computer some old API(s) that don't
| allow me to install the new package.
| The output of the program that failed the new installation suggest me:
| You could try using --skip-broken to work around the problem
| You could try running: rpm -Va --nofiles --nodigest
There, the details (the full output prior to that error message) has
not been shown. Later you could not show it anymore because you didn't
get any errors.
That's what I'm referring to. If a problem is not reproducible anymore,
it cannot be examined at all anymore.
> In the meantime, however, I continued to do tries and I found that the
> application could be affected by bugs:
>
> *Bug 975521* <https://bugzilla.redhat.com/show_bug.cgi?id=975521> - unable
> to change settings using dconf
Have you actually read through the comments of that ticket?
> *Bug 956306* <https://bugzilla.redhat.com/show_bug.cgi?id=956306> - gnome
> shell freezes when window is present from su session
Have you done anything to confirm that theory?
Does the program work if you run it as a normal user instead of via "su"?
> What I can check still on the computer to understand the problem?
Focus on a specific problem, try to trouble-shoot it as long as it is
reproducible. Gather details, find out whether somebody can reproduce it
and confirm it. Search in bugzilla, file a bug report. Don't mess with
your computer too much. Fedora 20 is not free of bugs. It may even be that
it is not reproducible with Fedora 21 (at least, here it isn't reproducible).
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org