Hi,
For some time I've been using a private repo for various programs I've
repackaged. It's a very simple setup based on createrepo.
Now my TW machine refuses to use this repo, complaining that
File 'repomd.xml' from repository 'lmn_private' is signed with an
unknown key '.....'
I've done the following checks:
1. Downloaded $REPO/repodata/repomd.xml
2. Downloaded $REPO/repodata/repomd.xml.asc
3. Ran gpg --verify repomd.xml.asc repomd.xml
The output matches the key reported by zypper.
4. Verified that the key is known to rpm using rpm -qi gpg-pubkey-...-.....
The body of the key known to RPM and the public key used to sign the
packages are identical.
The verification fails on my TW machine, with
zypper-1.14.5-1.1.x86_64
libzypp-17.3.1-1.1.x86_64
But works on a Leap 42.3 server with
zypper-1.13.32-5.12.1.x86_64
libzypp-16.15.6-5.12.1.x86_64
I'm not sure where to go next from here, what else can I try?
Thanks,
Robert
--
http://robert.muntea.nu/
--
To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org
Hi, after snapshot 726 Lmms does not start anymore:
>lmms
VST sync support disabled in your configuration
free(): invalid pointer
Aborted (core dumped)
I was few snapshot behind so I don't know exactly since when..
It happens only to me ?
Thanks,
Daniele.
--
To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org
Dear Support ,
LibreOffice : Date Column Format
since abt 10 days problem appears with Date Column Format.
Date Column Format is set to Language English USA : MM/DD/YY
For example today we have 07/28/18 in Date-Column :
then if i use next cell below , in Date Column , and try
to enter for August 03, 2018 , as 08/03/18 , then
LO flips that to "03/08/18"
nevertheless , when i check that cell-format it remains
MM/DD/YY
.....
something odd is happening :(
thanks
regards
.....
--
To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org
During my zypper dup in order to download the latest snapshot installing went
well up to "(63/197) Installing: kernel-default-4.17.7-1.3.x86_64 ..100%>[-]."
Than it stopped and has not moved an inch leaving me with an unfinished
update.
I was expecting the dracut information but that does not seem to come (one
hour now) and I will keep it in this state untill I get some help and
instructions on how to proceed.
--
opensuse:tumbleweed:20180720
Qt: 5.11.1 KDE Frameworks: 5.47.0 - KDE Plasma: 5.13.3 - kwin 5.13.3
kmail2 5.8.3 - akonadiserver 5.8.3 - Kernel: 4.17.6-1-default
--
To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org
Have since some days a problem with installing new programs or to do an
update. The main information is :
can't create transaction lock on /usr/lib/sysimage/rpm/.rpm.lock (Read-only
file system)
To solve this problem I found somebody promoting to rebuild the database.
Resulting in:
# rpm --rebuilddb
error:# rpm --rebuilddb
error: can't create transaction lock on /usr/lib/sysimage/rpm/.rpm.lock (Read-
only file system)
What is keeping me of repairing this problem. Deleting of the lock file is not
possible even not with the force addition.
Any ideas?
--
opensuse:tumbleweed:20180714
Qt: 5.11.1 KDE Frameworks: 5.47.0 - KDE Plasma: 5.13.3 - kwin 5.13.3
kmail2 5.8.2 - akonadiserver 5.8.2 - Kernel: 4.17.5-1-default
--
To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org
Hi Folks,
The chump is stumped! I'm having problems with kscreenlocker when unlocking
with a pin for a smartcard. I've already reported the bug on bugzilla and on KDE's
bugtracking system, but no one has touched them for more than a week. Maybe
I can find help here?
First, the smartcards work with KDM for console logins, it's only kscreenlocker that fails.
So the reader, pcscd, libcoolkey, and pam_pkcs11 all work. Everything also works on
42.x installs.
Running pam_pkcs11 in debug mode shows kcheckpass calling pam_pkcs11, but fails
to find a certificate. kcheckpass is apparently a component of kscreenlocker.
So I looked to upgrade kscreenlocker from KDE:Frameworks5 (RPM) but hit a failed
libQt5Core.so.5(Qt_5.11) dependency. I'd rather not mess with the guts of KDE
at this time, are there any alternatives? Maybe use a different screen locker?
Any suggestions? I contacted a developer listed on github for kcheckpass but
was rebuffed for having the audacity to try to directly contact him. He hadn't
touch it for years anyway...
Regards,
Lew
--
To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org
Anyone else tried lately? I cannot do any editing of grub stanzas, only look or
F10 or ESC.
--
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org
Happens on installations on two different Intel PCs, hosts ab250 and gx780. Data
below is all from the older gx780.
Nothing in .xsession-errors & no coredump. Xorg.0.log, dmesg tail and journal tail:
http://fm.no-ip.com/Tmp/SUSE/Factory/xorg.0.log-TW20180712plasmacrash-gx780…http://fm.no-ip.com/Tmp/SUSE/Factory/plasmacrashLogs-gx780-TW20180712.txt
Happens whether logging in from greeter (even in safe mode) or using startx.
IceWM works normally.
After deleting all KDE content from ~/.config/ no more crash, though all
settings lost.
I searched for and found no likely match on B.O.O.
The journal for the crash indicates an apparent objection to my xrandr script in
/etc/X11/xinit/xinitrd.d/, overriding the expected result. After the .config
delete, the expected results from xrandr are ignored, unlike in IceWM, which
fully obeys xrandr.
Apparently this is at least two problems. Any ideas besides filing a bug or two
or trying to remember all the desktop settings to try to restore, on each
installation (I have several others yet to update since weeks or months)?
---------------
# inxi -G
Graphics: Card-1: Intel 4 Series Integrated Graphics driver: i915 v: kernel
Display: server: X.Org 1.19.6 driver: modesetting unloaded:
fbdev,intel,vesa
resolution: 2560x1080~60Hz
OpenGL: renderer: Mesa DRI Intel Q45/Q43 v: 2.1 Mesa 18.1.3
# lspci -nnk | grep -A3 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation 4 Series Chipset
Integrated Graphics Controller [8086:2e12] (rev 03)
Subsystem: Dell Device [1028:0420]
Kernel driver in use: i915
Kernel modules: i915
# hwinfo --gfxcard
13: PCI 02.1: 0380 Display controller
[Created at pci.378]
Unique ID: ruGf.zhgSuVs59r0
SysFS ID: /devices/pci0000:00/0000:00:02.1
SysFS BusID: 0000:00:02.1
Hardware Class: graphics card
Model: "Intel 4 Series Chipset Integrated Graphics Controller"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x2e13 "4 Series Chipset Integrated Graphics Controller"
SubVendor: pci 0x1028 "Dell"
SubDevice: pci 0x0420
Revision: 0x03
Memory Range: 0xf7b00000-0xf7bfffff (rw,non-prefetchable)
Module Alias: "pci:v00008086d00002E13sv00001028sd00000420bc03sc80i00"
Config Status: cfg=new, avail=yes, need=no, active=unknown
27: PCI 02.0: 0300 VGA compatible controller (VGA)
[Created at pci.378]
Unique ID: _Znp.SFJq_fZRtDB
SysFS ID: /devices/pci0000:00/0000:00:02.0
SysFS BusID: 0000:00:02.0
Hardware Class: graphics card
Model: "Intel 4 Series Chipset Integrated Graphics Controller"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x2e12 "4 Series Chipset Integrated Graphics Controller"
SubVendor: pci 0x1028 "Dell"
SubDevice: pci 0x0420
Revision: 0x03
Driver: "i915"
Driver Modules: "i915"
Memory Range: 0xf7c00000-0xf7ffffff (rw,non-prefetchable)
Memory Range: 0xe0000000-0xefffffff (ro,non-prefetchable)
I/O Ports: 0xecb0-0xecb7 (rw)
Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled)
IRQ: 16 (3353 events)
I/O Ports: 0x3c0-0x3df (rw)
Module Alias: "pci:v00008086d00002E12sv00001028sd00000420bc03sc00i00"
Driver Info #0:
Driver Status: i915 is active
Driver Activation Cmd: "modprobe i915"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Primary display adapter: #27
--
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org
So, I decided to install tumbleweed on my laptop... very pleased in
general... seems to run faster, I can use my mousepad for the first time
in a year, adapted better to the generic amdgpu driver, so the graphics
look more crisp and clean. Nice. The install was an upgrade from 42.3
via zypper dup after setting up all the tumbleweed repos and removing
the 42.3 repos.
But there are a few problems to get around. The first one is that I can
only run the plasma desktop. I tried booting up and loading LXDE and
XFCE, but when I login to either of those from the display manager, the
screen goes black. I get a mouse cursor, but nothing else. When I hit
ctrl-alt-double backspace to kill X, the actual LXDE or XFCE screen will
pop up for about 30 seconds, and then it will go back to the display
manager.
A possibly related problem - /etc/sysconfig/displaymanager says this:
# Here you can set the default Display manager
(kdm/xdm/gdm/wdm/entrance/console).
# all changes in this file require a restart of the displaymanager
#
DISPLAYMANAGER="sddm"
However, the display manager doesn't actually look like it is sddm. It
looks like it is gdm. I mean, it really is the gnome display manager and
not sddm, unless sddm has been changed in tumbleweed to be exactly like
gdm. I don't know if that is related to the problem of not being able to
run any other DE besides plasma or not.
Any ideas? Not sure what else to post here. Here is a link to my
Xorg.0.log.old file after closing out trying to get into lxde and xfce
and opening up plasma again:
https://pastebin.com/raw/eRJPdNqH
I would not know what to look for in that log file, so I just put the
whole thing there.
--
George
Box: 42.3 | KDE Plasma 5.8 | AMD Phenom IIX4 | 64 | 32GB
Laptop #1: TW | Plasma 5.13 | AMD FX 7TH GEN | 64 | 32GB
Laptop #2: 42.3 | KDE Plasma 5.8 | Core i5 | 64 | 8GB
--
To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org
I installed 15.0 on a previously virgin HD, partitioning in advance, and
directing openSUSE which partitions to use for what. Good so far. Then I
installed Snow Leopard. It wrested boot away from 15.0, so I installed rEFInd on
the OS X system partition. That worked as advertised with no fuss necessary,
allowing selection among OS X, 15.0, shutdown, reboot, and more that I don't
remember. Then I ran YaST2 bootloader to see what would happen. Sure enough, it:
1-usurped control from rEFInd, and
2-omitted OS X from among the Grub2 menu choices.
I used efibootmgr to reset the order:
# efibootmgr
BootCurrent: 0000
BootOrder: 0000,0001
Boot0000* opensuse
Boot0001* rEFInd Goot Manager
Boot0080* Mac OS X
BootFFFF*
# efibootmgr -o 0001,0000
BootCurrent: 0000
BootOrder: 0001,0000
Boot0000* opensuse
Boot0001* rEFInd Goot Manager
Boot0080* Mac OS X
BootFFFF*
but Grub still shows up instead of rEFInd on reboot.
There is no BIOS to change boot order on Mactel. What can be done to prevent
openSUSE from stealing boot control from rEFInd?
--
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org