Workaround for openjdk misconfiguration?
by Scott Beamer
Greetings all,
When updating openjdk and openjdk-devel the following happens...
[...]
Cleanup : 1:java-1.7.0-openjdk-
devel-1.7.0.60-2.4.2.4.fc19.x86_64 21/29
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.2.4.fc19.x86_64/bin/javac
has not been configured as an alternative for javac
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.2.4.fc19.x86_64 has not been
configured as an alternative for java_sdk_openjdk
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.2.4.fc19.x86_64 has not been
configured as an alternative for java_sdk_1.7.0
[...]
Cleanup : 1:java-1.7.0-
openjdk-1.7.0.60-2.4.2.4.fc19.x86_64 27/29
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.2.4.fc19.x86_64/jre/bin/java
has not been configured as an alternative for java
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.2.4.fc19.x86_64/jre has not
been configured as an alternative for jre_openjdk
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.2.4.fc19.x86_64/jre has not
been configured as an alternative for jre_1.7.0
[...]
A bug report has been filed: https://bugzilla.redhat.com/show_bug.cgi?
id=991762
In the meantime, what is the workaround for this?
Thanks.
Scott
10 years, 6 months
Re: encription
by Patrick Dupre
> >> Hello,
> >>
> >> I encripted one partition of a usb key.
> >> When I plug it, it used to ask me about the paraphase, but after I
> >> entered one time, the partition is mounted. Then, I can eject the
> >> key, and replug it,
> >> but it does not ask me anymore the paraphrase, mounting the partition
> >> automatically.
> >> I would like that it ask me the paraphrase every time that the key
> >> in replugged.
> >> How can I get this behavior?
> >
> > Did you actually eject or dismount the USB device (via the umount or
> > eject commands or desktop options) or did you simply unplug it? If you
> > unmounted or ejected it, I'd imagine you'd be asked for the passphrase
> > the next time you mounted it. If it doesn't ask, then yeah, we have an
> > issue--nothing having to do with that device should be cached.
> >
> > If all you did was unplug it, then the filesystem was never closed, the
> > system never saw it as unmounted and the current mount is still valid.
> > If that is the case, you're lucky it wasn't corrupted (you must have
> > waited long enough between write operations for changes to be flushed
> > to the device).
> > ----------------------------------------------------------------------
> > - Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
> > - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
> > - -
> > - "Microsoft is a cross between The Borg and the Ferengi. -
> > - Unfortunately they use Borg to do their marketing and Ferengi to -
> > - do their programming." -- Simon Slavin -
> > ----------------------------------------------------------------------
> did you check if the gnome key ring program is keeping the password
How can I chek this?
so
> that it will not prompt you. Generally, when you put the password, there
> is a check on save the password.
> This is my experience encfs
> --
> Joseph Loo
> jloo(a)acm.org
>
> --
> users mailing list
> users(a)lists.fedoraproject.org
> 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
===========================================================================
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
===========================================================================
10 years, 6 months
yum grouplist does not show all groups
by Özgür
Hi,
The command
yum grouplist
does not show all available groups in Fedora 19. I had the same problem
before in CentOS and other versions of Fedora. As an example, I can
install
yum groupinstall "Development Libraries"
but yum grouplist does not show such a group. Is that a bug, or am I doing
something wrong?
Regards, Ozgur
10 years, 6 months
Update Dependancies broken for the past few days.
by Scott Beamer
Greetings all,
I'm running KDE on Fedora 19 X64
For the past 2-3 days I've had problems updating a number of packages
because of failed dependencies.
For a while I figured it was a problem that would resolve itself once
the mirrors were updated, but so far, the problem persists.
II've done 'yum clean all' numerous times to no avail.
Is this a problem on my end or Fedora's end?
Here is the the output of 'yum update':
$ sudo yum update
Loaded plugins: langpacks, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package kcm_colors.x86_64 0:4.10.5-3.fc19 will be updated
---> Package kcm_colors.x86_64 0:4.11.1-2.fc19 will be an update
---> Package kde-workspace.x86_64 0:4.10.5-3.fc19 will be updated
---> Package kde-workspace.x86_64 0:4.11.1-2.fc19 will be an update
--> Processing Dependency: libxcb-keysyms.so.1()(64bit) for package:
kde-workspace-4.11.1-2.fc19.x86_64
--> Processing Dependency: libxcb-image.so.0()(64bit) for package:
kde-workspace-4.11.1-2.fc19.x86_64
---> Package kde-workspace-libs.x86_64 0:4.10.5-3.fc19 will be updated
--> Processing Dependency: libsolidcontrol.so.4()(64bit) for package:
contour-0.3-2.fc19.x86_64
--> Processing Dependency: libsolidcontrolifaces.so.4()(64bit) for
package: contour-0.3-2.fc19.x86_64
---> Package kde-workspace-libs.x86_64 0:4.11.1-2.fc19 will be an update
---> Package kdeartwork.x86_64 0:4.10.5-1.fc19 will be updated
---> Package kdeartwork.x86_64 0:4.11.1-1.fc19 will be an update
---> Package kdeartwork-kxs.x86_64 0:4.10.5-1.fc19 will be updated
---> Package kdeartwork-kxs.x86_64 0:4.11.1-1.fc19 will be an update
---> Package kdeartwork-screensavers.x86_64 0:4.10.5-1.fc19 will be updated
---> Package kdeartwork-screensavers.x86_64 0:4.11.1-1.fc19 will be an update
---> Package kdm.x86_64 0:4.10.5-3.fc19 will be updated
---> Package kdm.x86_64 0:4.11.1-2.fc19 will be an update
---> Package kgreeter-plugins.x86_64 0:4.10.5-3.fc19 will be updated
---> Package kgreeter-plugins.x86_64 0:4.11.1-2.fc19 will be an update
---> Package konsole.x86_64 0:4.10.5-1.fc19 will be updated
---> Package konsole.x86_64 0:4.11.1-1.fc19 will be an update
---> Package konsole-part.x86_64 0:4.10.5-1.fc19 will be updated
---> Package konsole-part.x86_64 0:4.11.1-1.fc19 will be an update
---> Package libkworkspace.x86_64 0:4.10.5-3.fc19 will be updated
---> Package libkworkspace.x86_64 0:4.11.1-2.fc19 will be an update
---> Package mesa-libwayland-egl.x86_64 0:9.2-1.20130902.fc19 will be updated
---> Package mesa-libwayland-egl.x86_64 0:9.2-1.20130919.fc19 will be an update
---> Package plasma-scriptengine-python.x86_64 0:4.10.5-3.fc19 will be updated
---> Package plasma-scriptengine-python.x86_64 0:4.11.1-2.fc19 will be an update
--> Running transaction check
---> Package kde-workspace-libs.x86_64 0:4.10.5-3.fc19 will be updated
--> Processing Dependency: libsolidcontrol.so.4()(64bit) for package:
contour-0.3-2.fc19.x86_64
--> Processing Dependency: libsolidcontrolifaces.so.4()(64bit) for
package: contour-0.3-2.fc19.x86_64
---> Package xcb-util-image.x86_64 0:0.3.9-2.fc19 will be installed
---> Package xcb-util-keysyms.x86_64 0:0.3.9-2.fc19 will be installed
--> Finished Dependency Resolution
Error: Package: contour-0.3-2.fc19.x86_64 (@fedora)
Requires: libsolidcontrolifaces.so.4()(64bit)
Removing: kde-workspace-libs-4.10.5-3.fc19.x86_64 (@updates)
libsolidcontrolifaces.so.4()(64bit)
Updated By: kde-workspace-libs-4.11.1-2.fc19.x86_64 (updates)
Not found
Available: kde-workspace-libs-4.10.4-1.fc19.x86_64 (fedora)
libsolidcontrolifaces.so.4()(64bit)
Error: Package: contour-0.3-2.fc19.x86_64 (@fedora)
Requires: libsolidcontrol.so.4()(64bit)
Removing: kde-workspace-libs-4.10.5-3.fc19.x86_64 (@updates)
libsolidcontrol.so.4()(64bit)
Updated By: kde-workspace-libs-4.11.1-2.fc19.x86_64 (updates)
Not found
Available: kde-workspace-libs-4.10.4-1.fc19.x86_64 (fedora)
libsolidcontrol.so.4()(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Thanks.
Scott
10 years, 6 months
FC18 - Libreoffice keeps crashing
by Paul Erickson
For some reason whenever I try to configure Libreoffice, for instance to
change the default language setting, or try to change the font in a
document, Libreoffice keeps crashing. I get the following error message:
Xlib: extension "RANDR" missing on display ":0.0".
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve
property `GtkOptionMenu::indicator-size' of type `GtkRequisition' from
rc file value "0" of type `glong'
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve
property `GtkOptionMenu::indicator-spacing' of type `GtkBorder' from rc
file value "0" of type `glong'
I have tried uninstalling and reinstalling without success.
Has anyone else encountered this, and if so, how have you resolved it?
--
----------------------------------------------------------------
cheers, Paul - VA7NT - email: va7nt(a)telus.net
"Those who hear not the music, think the dancers mad."
"Tolerance becomes a crime when applied to evil." - Thomas Mann
"That state which separates it's warriors from it's scholars will have
it's thinking done by cowards and fighting done by fools"
- Thucydides - The Pelopenisia
"The Malice of the wicked is reinforced by the weakness of the virtuous."
- Churchill
10 years, 6 months
Reboot hangs from Cinnamon
by Frank McCormick
I have several desktops installed on my 19 install, including Cinnamon
and Mate.
I noticed this morning for the first time that a reboot from Cinnamon hangs.
I end up with a blank screen and one line at the time which as I recall
mentions
reboot and some numbers.
Does anyone have a clue as to what is wrong? Mate reboots fine as does
XFCE.
Cheers
10 years, 6 months
Problems booting Fedora 19 with UEFI
by Edward Quick
Hi,
I recently purchased a Dell Inspiron 5721 which came with Windows 8. I
would like to dual boot this with Fedora but am having problems running
the Fedora Install. I have Fedora-19-x86_64-DVD.iso on usb, and whenever
I boot with UEFI (secure on or off), the
boot process hangs at the line, Reached target Basic System:
[ 12.650116] localhost systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ 12.650553] localhost systemd[1]: Starting Paths.
[ 12.650962] localhost systemd[1]: Reached target Paths.
[ 12.651376] localhost systemd[1]: Starting Basic System.
[ 12.651829] localhost systemd[1]: Reached target Basic System.
And then bails out after a few minutes and starts up the Dracut Emergency Shell:
[ 35.729286] localhost multipathd[108]: sdc: add path (uevent)
[ 35.915042] localhost multipathd[108]: sdc: update path write_protect to '0' (uevent)
[ 36.008982] localhost multipathd[108]: sdc: update path write_protect to '1' (uevent)
[ 197.571596] localhost dracut-initqueue[395]: Warning: Could not boot.
[ 197.574126] localhost dracut-initqueue[395]: Warning: /dev/root does not exist
[ 197.578383] localhost systemd[1]: Starting Dracut Emergency Shell...
I have pasted the full sosreport.txt at http://pastebin.com/4stUgUDN
Please note that if I install in basic graphics mode, I still get the
same result. The only way I can get the install to work, is if I boot in
legacy mode. Unfortunately after doing this, I can no longer boot up
Windows.
If anyone knows how to fix this, I'd be really grateful for some help :-)
Many thanks,
Ed
10 years, 6 months
readline (in c)
by Patrick Dupre
Hello,
It is probably not the right list to post my question, just in case!
I would like to catch the ESC or ctl C key when using readline.
Is it possible?
Thank
===========================================================================
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
===========================================================================
10 years, 6 months
F18: Problem with Abort
by Dan Thurman
I did a ps command and found the following:
root 622 1 0 10:52 ? 00:00:00 /usr/bin/abrt-watch-log
-F BUG: WARNING: at INFO: possible recursive locking detected ernel BUG
at list_del corruption list_add corruption do_IRQ: stack overflow: ear
stack overflow (cur: eneral protection fault nable to handle kernel
ouble fault: RTNL: assertion failed eek! page_mapcount(page) went
negative! adness at NETDEV WATCHDOG ysctl table check failed : nobody
cared IRQ handler type mismatch Machine Check Exception divide error:
bounds: coprocessor segment overrun: invalid TSS: segment not present:
invalid opcode: alignment check: stack segment: fpu exception: simd
exception: iret exception: /var/log/messages -- /usr/bin/abrt-dump-oops -xD
So what do I need to do?
10 years, 6 months