Hi.
With 12.3, bash completion generally work(s/ed) for me. However, in 13.2,
it does not, unless I modify /usr/share/bash-completion/bash_completion
at line 1741 to include `sudo` specifically, AND source it again for
each xterm window I open... The file has, at least in theory, been sourced
from the chain
/etc/bash.bashrc
/etc/profile.d/bash_completion.sh
/usr/share/bash-completion/bash_completion
However, I still have to explicitly source it again in the newly-opened
xterm to get `sudo` commands to tab-complete (e.g. `sudo ls <TAB>..`)
12.3 seems to have had the pattern:
/etc/bash.bashrc
/etc/profile.d/complete.bash
Re-jiggering /etc/bash.bashrc to prefer /etc/profile.d/complete.bash
over /etc/profile.d/bash_completion.sh on 13.2 doesn't seem to help.
The only difference I see between the 12.3 and 13.2 versions of
complete.bash is the inclusion of the block starting with
if ! type -t _completion_loader &> /dev/null ; then
_completion_loader ()
Any explanations?
Suggestions on getting back sudo <CMD> <TAB>... completion?
TIA,
Michael
--
Michael Fischer
michael(a)visv.net
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
I would like to be able to use excel in wine and I have almost got it
working. Sor far I have followed these steps:
step 1 deleted ~/.wine
step 2 run command (to make my wine prefix 32-bit not 64)
WINEARCH=win32 winecfg
step 3 follow instructions here
https://www.liberiangeek.net/2012/06/how-to-install-microsoft-office-suite-…
step 4 excel installed (32-bit version) with no errors so did the
dotnet20 and msxml and corefonts pacakages. When excel is opened I get
the error: Not enough memory to run Microsoft Excel. lease close other
applications and try again
This install works fine on windows so it is not my disc
I have tried on my laptop which has 4GB RAM (3.2GB fre when I tried to
open excel) and my desktop which has 32GB RAM of which most is free.
Does anyone have any clue how to get this working? Perhaps there is a
setting telling wine how much memory it has available?
Host OS opensuse 13.1 x64
Wine version 1.7.28
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
Yesterday I found the descent 3 (linux version) install disk
languishing among my music collection and i have managed to install
and patch the game to v1.4b.
When I attempt to execute /usr/local/bin/descent3 I receive the error
"Descent 3 Message(Error: Illegal font file: lohud.fnt.
)
System Error"
I have searched the web for solutions but the only suggested
resolution is a reinstall and that was for the Microsoft Windows
version - never the less I did try reinstalling and tried running the
game with no patches applied but received the same error message
Has anyone on this list run the game on OpenSUSE 13.2 (or a recent
linux distro), and has anyone ever come across a font file with the
name "lohud.fnt"?
I thought it might be fun to play the game over the weekend but it
looks as though I could spend the time trying to fix this issue
rather than playing the game...I'd appreciate any advice as I'm
stumped for a solution.
regards
Phil Vossler
"......sooner or later that day comes and you can't hide from the
things that you've done anymore." William Adama BSG
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
I have discovered that Inkscape is not exporting to pdf or eps or
printing any object with a gradient fill and a transparency. These
objects come out as white.
Any idea how to fix this?
Opensuse 13.2 x64
Inkscape 0.48
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
After the latest glibc update, systemd crashed as I was restarting dbus,
systemd-logind etc. The only way to resume normal operation was to restart the
system. Has anyone else seen this?
--
Regards,
Peter
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
All,
Just a reminder that older 11/12 system may not handle the leapsecond today
gracefully. If using ntp, placing ntp in 'slew mode' will allow for graceful
handling of the second. The attached script, if run before 7/1 will place ntp in
slew mode, and if run after 7/1 will restore the original configuration.
--
David C. Rankin, J.D.,P.E.
I'm catching up with archives and found a thread on cloning and wanted
to point out that in particular on Btrfs this can be a problem:
"Do not make a block-level copy of a btrfs filesystem to a block
device, and then try to mount either the original or the copy while
both are visible to the same kernel."
https://btrfs.wiki.kernel.org/index.php/Gotchas
The same problem applies to LVM snapshots (thick or thin). And likely
similar problems apply to ext4 and XFS when using metadata
checksumming. This isn't the default yet in ext4, but is the default
with XFS format v5 starting with xfsprogs 3.2.
btrfs-progs 4.1 now has a way to change the fs volume UUID. So after
cloning if there is *any* possibility the two file systems will be
visible to the kernel at the same time while one will be mounted,
first it's best to change the UUID on one of them. This will take a
while as the fs volume UUID is used constantly in the metadata format.
In effect the whole fs (minus data) has to be read and written.
There might still be bugs, but another way to clone a Btrfs volume is
the seed device. Make A a seed device, and it mounts read-only, add a
new device to the volume, then umount and remount, and it mounts
read-write, then delete the seed device and data is migrated to the
new device. But also, the UUID is unique on the new device. After it's
completely, the seed device can be made a non-seed volume again (no
longer mounts read only).
Just an idea.
--
Chris Murphy
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
This describes how to have encrypted /boot with single passphrase
unlock (rather than twice, once for GRUB and once for Linux). It uses
a key file which is on the encrypted volume.
http://www.pavelkogan.com/2014/05/23/luks-full-disk-encryption/
The problem at the moment on openSUSE is it seems you can't have
non-LVM LUKS volumes (just standard partitions). That poses a problem
for encrypted Btrfs, so I wonder how that's supposed to work?
The GRUB crypto work seems solid, even grub-mkconfig appears to
recognize it's on a LUKS volume, and sets up the grub.cfg correctly.
It makes the unencrypted, separate /boot seem antiquated. And also in
a Btrfs context where we want /boot snapshot along with /lib/modules
so they're in parity, is kinda important.
--
Chris Murphy
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
How can a raw disk partition be busy?
I am able to read/write to it with 'dd':
time dd if=/dev/sdd1 of=/dev/null bs=16M count=128
2147483648 bytes (2.1 GB) copied, 5.70285 s, 377 MB/s
5.72sec 0.00usr 2.21sys (38.77% cpu)
> time dd if=/dev/zero of=/dev/sdd1 bs=16M count=128
2147483648 bytes (2.1 GB) copied, 7.65681 s, 280 MB/s
7.66sec 0.00usr 2.82sys (36.94% cpu)
I've never seen an unformatted raw partition on a disk be
busy before...?
lsof & fuser turned up nada...
FWIW, I'm trying to create a new rootdisk that can hold
root+usr+usrshare
Maybe this is a sign that I'm being drawn toward
the wrong path....
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
A month or so ago I started getting the following message when I
cross-compile Windows apps using MinGW from OBS.
icon_c.lib: error adding symbols: File in wrong format
The lib/dll files have not been recompiled in over 4 years. I am
guessing what has changed is the MinGW. Oddly, it only complains about
a couple files. Most all works great.
Anyone else having problems linking with some libs?
Of course I do not have the source for these libs so I cannot recompile them.
--
Roger Oberholtzer
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org