Quantcast
Channel: openSUSE Forums
Viewing all 40713 articles
Browse latest View live
↧

Hello & New to OpenSuSE

April 6, 2021, 2:26 am
$
0
0
Hi All,

Old person and new to OpenSUSE, using old(ish) hardware.

I guess I have been trying various flavours of Linux for ages - was using Mint for around a year but upgraded my hardware and it no longer worked so have come across to OS (should have done so from the beginning).

My OS machine is an HP XW8600 from approx 2005.

It has 32Gb Ram, Dual Intel Xeon 2.50Ghz cpu's (for 8 cores), Nividia FX4800 GPU, 1 x 480 Gb SSD and 4 x 500 Gb SAS in raid with a 680 Gb logical drive - Oh and it weighs a ton !!.

Eventually will get Samba sorted to share the logical drive and possibly even DHCP and DNS Server's so that I can retire my 2012 R2 Domain Controller.

So the Covid aware virtual bar is open and its lemonades all round.
↧
Search

LEAP 15.2 Wireguard Peer funktioniert nicht

April 6, 2021, 3:08 am
$
0
0
Hallöchen,

ich habe hier ein Problem mit Wireguard:
auf meinem Telekom-Router läuft ein Wireguard-Server. Die Dort expertierte Konfigurationsdatei funktioniert ohne Probleme unter diversen Tablets und Smartphones (iPad, Samsung Tablet, Android Smartphone) in Verbindung mit den Wireguard-apps.
Jetzt habe ich versucht unter KDE diese Datei in den Netzwerkmanager als VPN zu importieren. Die Datei wird auch importiert, die Schlüssel usw. stehen auch anscheinend an den Stellen, wo sie hin gehören.
Ich bekomme aber keine Verbindung zu meinem Netzwerk zustande. (DynsDNS auf dem Router läuft und von den anderen Geräten klappt der Zugriff auch).

Wie kann ich den Fehler finden?

Gruß
mairo
↧
↧

New ARM Tumbleweed snapshot 20210401 released!

April 6, 2021, 3:10 am
$
0
0
Please note that this mail was generated by a script.
The described changes are computed based on the aarch64 DVD.
The full online repo contains too many changes to be listed here.

More...
↧

LEAP 15.3 Upgrade to 15.2 without Nouveau

April 6, 2021, 3:34 am
$
0
0
When I put in the command to upgrade from 15.1 to 15.2, I got a warning that it would include the Nouveau driver. The warning said Nouveau wasn't recommended for KDE, which is what I use, and plus I had a bunch of problems with the Optimus-Nouveau thing when I first installed openSUSE. How do I do the upgrade without accepting Nouveau?



↧

Upgrading to the next PostgreSQL version

April 6, 2021, 5:10 am
$
0
0
We upgraded our internal PostgreSQL cluster to the latest version last week. Time passes by so quickly: we installed our PostgreSQL cluster around 2008. At least, this was the time of the first public MirrorBrain release 2.2, which was the reason to run a PostgreSQL installation for openSUSE. But MirrorBrain...

More...
↧
↧

LEAP 15.3 encrypted swap on raid1 not working

April 6, 2021, 6:07 am
$
0
0
Hi,
I'm doing some installation tests with LEAP 15.3 BETA and I encountered a problem with encrypted swap.
The layout I choosed for my swap is raid1 with an encrypted swap over it, recreated at boot time with a random key. This layout is supported by the yast installer and I already used it in the past (LEAP 15.2, LEAP 42, etc..).

This time the installer gave me an error during the filesystem creation. I told it to ignore and continue and the resulting system was bootable but without swap.

I checked the relevant configuration files:

/etc/fstab
Code:
...
/dev/mapper/cr_swap                        swap      swap  defaults            0  0
...
/etc/crypttab
Code:
...
cr_swap /dev/md2        /dev/urandom    swap
...
Config files looks fine, it seems that the installer has done its job.

I tried to restart crypttab service with this result:
Code:
systemctl restart cryptsetup.target
Please enter passphrase for disk cr_swap on swap: *********             
A dependency job for cryptsetup.target failed. See 'journalctl -xe' for details

journalctl -xe

The job identifier is 4086 and the job result is failed.
Apr 06 14:53:03 opensuse153 systemd[1]: Dependency failed for Local Encrypted Volumes.
Subject: A start job for unit cryptsetup.target has failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A start job for unit cryptsetup.target has finished with a failure.
The job identifier is 4071 and the job result is dependency.
Apr 06 14:53:03 opensuse153 systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with result 'dependency'.
Apr 06 14:53:03 opensuse153 systemd[1]: Reached target Block Device Preparation for /dev/mapper/cr_swap.
Subject: A start job for unit blockdev@dev-mapper-cr_swap.target has finished successfully
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A start job for unit blockdev@dev-mapper-cr_swap.target has finished successfully.
The job identifier is 4225.
Apr 06 14:53:03 opensuse153 systemd[1]: Stopped target Block Device Preparation for /dev/mapper/cr_swap.
Subject: A stop job for unit blockdev@dev-mapper-cr_swap.target has finished
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A stop job for unit blockdev@dev-mapper-cr_swap.target has finished.
The job identifier is 4231 and the job result is done.
It is very strange because it should not ask me for a password, it should use /dev/urandom.

After that I tried to create the same setup manually:

Code:
cryptsetup --debug open --type plain /dev/md2 cr_swap
# cryptsetup 2.3.4 processing "cryptsetup --debug open --type plain /dev/md2 cr_swap"
# Running command open.
# Locking memory.
# Installing SIGINT/SIGTERM handler.
# Unblocking interruption on signal.
# Allocating context for crypt device /dev/md2.
# Trying to open and read device /dev/md2 with direct-io.
# Initialising device-mapper backend library.
# Formatting device /dev/md2 as type PLAIN.
# Crypto backend (OpenSSL 1.1.1d  10 Sep 2019) initialized in cryptsetup library version 2.3.4.
# Detected kernel Linux 5.3.18-52-default x86_64.
# Interactive passphrase entry requested.
Enter passphrase for /dev/md2:
# Activating volume cr_swap [keyslot -1] using passphrase.
# dm version  [ opencount flush ]  [16384] (*1)
# dm versions  [ opencount flush ]  [16384] (*1)
# Detected dm-ioctl version 4.42.0.
# Detected dm-crypt version 1.22.0.
# Device-mapper backend running with UDEV support enabled.
# dm status cr_swap  [ opencount noflush ]  [16384] (*1)
# Plain: hashing passphrase using ripemd160.
# Trying to activate PLAIN device cr_swap using cipher aes-cbc-essiv:sha256.
# dm versions  [ opencount flush ]  [16384] (*1)
# dm status cr_swap  [ opencount noflush ]  [16384] (*1)
# Calculated device size is 2097024 sectors (RW), offset 0.
# DM-UUID is CRYPT-PLAIN-cr_swap
# Udev cookie 0xd4d22b9 (semid 17) created
# Udev cookie 0xd4d22b9 (semid 17) incremented to 1
# Udev cookie 0xd4d22b9 (semid 17) incremented to 2
# Udev cookie 0xd4d22b9 (semid 17) assigned to CREATE task(0) with flags DISABLE_LIBRARY_FALLBACK        (0x20)
# dm create cr_swap CRYPT-PLAIN-cr_swap [ opencount flush ]  [16384] (*1)
# dm reload cr_swap  [ opencount flush securedata ]  [16384] (*1)
device-mapper: reload ioctl on  failed: No such file or directory
# Udev cookie 0xd4d22b9 (semid 17) decremented to 1
# Udev cookie 0xd4d22b9 (semid 17) incremented to 2
# Udev cookie 0xd4d22b9 (semid 17) assigned to REMOVE task(2) with flags DISABLE_LIBRARY_FALLBACK        (0x20)
# dm remove cr_swap  [ opencount flush securedata ]  [16384] (*1)
# dm versions  [ opencount flush ]  [16384] (*1)
# dm status cr_swap  [ opencount noflush ]  [16384] (*1)
# Udev cookie 0xd4d22b9 (semid 17) decremented to 1
# Udev cookie 0xd4d22b9 (semid 17) waiting for zero
# Udev cookie 0xd4d22b9 (semid 17) destroyed
# Releasing crypt device /dev/md2 context.
# Releasing device-mapper backend.
# Unlocking memory.
Command failed with code -1 (wrong or missing parameters).
It fails again. It looks like device mapper is missing something, but what?

In the same machine I have a luks encrypted device (with password) which is working fine. The problem seems related to plain encrypted device (swap with random key should be implemented as a plain ecrypted device)

Any ideas? Any similar experiences?

Thank you in advance
↧

TUMBLEWEED Update issue

April 6, 2021, 10:23 am
$
0
0
Code:
Problem: libOpenImageIO2_1-2.1.17.0-1.13.i586 requires libOpenColorIO.so.1, but this requirement cannot be provided
  not installable providers: libOpenColorIO1-1.1.1-2.8.i586[http-download.opensuse.org-3de67a27]
                  libOpenColorIO1-1.1.1-2.8.i586[http-download.opensuse.org-9c129f69]
                  libOpenColorIO1-1.1.1-2.8.i586[openSUSE_20191112-0]
 Solution 1: Following actions will be done:
  install libOpenColorIO1-1.1.1-2.8.i586 despite the inferior architecture
  install libopenvdb7_1-7.1.0-1.5.i586 despite the inferior architecture
  install libpugixml1-1.11.4-1.4.i586 despite the inferior architecture
  install libtbb2-2020.3-2.5.i586 despite the inferior architecture
  install libblosc1-1.20.1-1.4.i586 despite the inferior architecture
  install libtinyxml0-2.6.2-9.23.i586 despite the inferior architecture
  install libyaml-cpp0_6-0.6.3-1.6.i586 despite the inferior architecture
  deinstallation of libOpenImageIO2_2-2.2.12.0-1.1.x86_64
  remove lock to allow removal of mame-0.226-1.1.x86_64
  deinstallation of libOpenImageDenoise0-1.2.2-1.3.x86_64
 Solution 2: deinstallation of libOpenImageIO2_1-2.1.17.0-1.12.x86_64
 Solution 3: keep obsolete libOpenImageIO2_1-2.1.17.0-1.12.x86_64
 Solution 4: break libOpenImageIO2_1-2.1.17.0-1.13.i586 by ignoring some of its dependencies

I have no idea on how to solve this.

Is this related to the pacman message on top of the forum?

The link I have to pacman in yast:

http://ftp.gwdg.de/pub/linux/misc/pa...SE_Tumbleweed/
↧

TUMBLEWEED Desktop Icon Arrangement on KDE Plasma

April 6, 2021, 10:39 am
$
0
0
Hi everyone, I have just started using openSUSE. I have already set up a working workstation system.
I find an anomaly that I cannot resolve.
The icons on the desktop move and don't stay where I put them.
Also I can't find a way to position the icons NOT aligned to the grid.
Specifically, for example, when I click on the ASA firewall manager, the software opens and the icon moves to the top left.

Any idea what I may have mistakenly configured?

Thanks a lot to everyone
↧
Search

LEAP 15.2 Druckdialog übernimmt nicht die Einstellungen aus CUPS

April 6, 2021, 10:43 am
$
0
0
Hallöchen,

mein Drucker (Brother MFC-J4510DW) druckt und scannt eingetlich ohne Probleme. Allerdings ist eins ärgerlich: Sowohl in Cups, als auch in Yast, als auch in den KDE-Systemeinstellungen wird mir als Standard-Druckqualität "fast" angezeigt. So wollte ich es auch. ABER: Wenn ich aus einer anwendung (zB. Firefox oder Okulat) drucken möchte ist die Druckqualität immer auf "best". Ich muss dann immer alles per Hand umstellen....
Warum ist das so???

Gruß
mairo
↧
↧

LEAP 15.3 Samba Shares for Windows

April 6, 2021, 11:57 am
$
0
0
Hi All,

I have tried in vain to sort this myself but have now got into a BIG mess (why does it have to be so **** hard ?).

On my machine I have the following partition setup

File System: NTFS
Mount Point: /tmp/Folly_Data
Mount By: Volume Label
Label: Folly_Data
UUID: 26E71D7E25588

This is mounted, I have configured smb.conf with the following

[global]
workgroup = Folly.Office
netbios name = Folly_Data
server string = ""
local master = yes
os level = 65
passdb backend = tdbsam
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
usershare allow guests = No
ldap admin dn =
wins server =
wins support = No

[Folly_Data]
available = Yes
browseable = Yes
inherit acls = No
path = /tmp/Folly_Data
read only = No
guest ok = Yes

and restarted smb.service/nmb.service

I can see the share from my Windows machine but have no permission to write to it (Permission Denied), I have tried

sudo chmod -R 777 /tmp/Folly_Data
sudo chown -R "myusername /tmp/Folly_Data

This hasn't worked , Dolphin still shows the owner and group as root (I am guessing that this is what my problem is but dont really know)

Can someone point me in the right direction please ? - Sensible answers please

Regards
↧

LEAP 15.2 leap 15.2 after upgrade kde taking over 5 minutes to start up from login

April 6, 2021, 2:13 pm
$
0
0
After upgrade to 15.2 time to startup from login screen to KDE being ready to respond can be 5 minutes. On 15.1 time was less than 20 secs.

Suggested commands do not seem to show any KDE startup information that is useful.

x64Cru_150G:~ # systemd-analyze blame
8min 40.609s fstrim.service
8min 22.759s mandb.service
20.826s backup-rpmdb.service
7.276s wicked.service
3.832s user@1001.service
2.511s systemd-udev-settle.service
1.251s lvm2-monitor.service
1.110s display-manager.service
962ms apparmor.service
723ms dracut-initqueue.service
716ms postfix.service
582ms firewalld.service
579ms systemd-udevd.service
549ms ca-certificates.service
472ms initrd-switch-root.service
470ms systemd-hwdb-update.service
249ms polkit.service
242ms backup-sysconfig.service
220ms upower.service
205ms ModemManager.service
203ms systemd-journal-catalog-update.service

x64Cru_150G:~ # systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @13.896s
└─display-manager.service @12.785s +1.110s
└─systemd-user-sessions.service @12.743s +37ms
└─network.target @12.739s
└─wicked.service @5.461s +7.276s
└─wickedd-nanny.service @5.420s +39ms
└─wickedd.service @5.370s +49ms
└─wickedd-auto4.service @5.316s +52ms
└─network-pre.target @5.312s
└─firewalld.service @4.729s +582ms
└─polkit.service @4.478s +249ms
└─basic.target @4.409s
└─sockets.target @4.409s
└─avahi-daemon.socket @4.408s
└─sysinit.target @4.398s
└─sys-fs-fuse-connections.mount @34.439s +3ms
└─systemd-modules-load.service @255ms +37ms
└─system.slice

There is no info that I can detect in the Journal that tells me the reason for the long login. If the cannot be fixed I will have to abandon opensuse. Time is better after system updates, and I reboot that day. However, if system is off for several days then the login time returns to 5 minutes.

regards,
Bob
↧

OTHER VERSION does virtualbox work on leap 15.2 rt kernel?

April 6, 2021, 2:41 pm
$
0
0
I get the "kernel driver not installed (rc=-1908)" when trying to start a Virtualbox VM in the rt kernel. Performing the suggested /sbin/vboxconfig doesn't work either:

cat /var/log/virtualbox.log
=== Building 'vboxdrv' module ===
make[1]: Entering directory '/usr/src/kernel-modules/virtualbox/src/vboxdrv'
/usr/src/kernel-modules/virtualbox/src/vboxdrv/Makefile-header.gmk:193: *** Error: unable to find the headers of the Linux kernel to build against (KERN_DIR=/lib/modules/5.3.18-lp152.3.2-rt/build). Specify KERN_VER=<version> (currently 5.3.18-lp152.3.2-rt) and run Make again. Stop.
make[1]: Leaving directory '/usr/src/kernel-modules/virtualbox/src/vboxdrv'
make: *** [Makefile:59: vboxdrv] Error 2

I noticed I had a 3.5-rt kernel, but that just hung when trying to log in, so rebooted the 3.2-rt kernel I had been using all along.

Other info:

uname -a
Linux localhost.localdomain 5.3.18-lp152.3.2-rt #1 SMP PREEMPT_RT Mon May 18 10:32:23 UTC 2020 (b1281f3) x86_64 x86_64 x86_64 GNU/Linux


sudo zypper se -si virtualbox vbox kernel
Loading repository data...
Reading installed packages...

S | Name | Type | Version | Arch | Repository
---+----------------------------------+---------+--------------------------------------+--------+--------------------------
i+ | devel_kernel | pattern | 20170319-lp152.6.3 | x86_64 | Main Repository
i+ | kernel-default | package | 5.3.18-lp152.66.2 | x86_64 | openSUSE:Leap:15.2:Update
i+ | kernel-default | package | 5.3.18-lp152.66.2 | x86_64 | Main Update Repository
i+ | kernel-default | package | 5.3.18-lp152.63.1 | x86_64 | openSUSE:Leap:15.2:Update
i+ | kernel-default | package | 5.3.18-lp152.63.1 | x86_64 | Main Update Repository
i+ | kernel-default-devel | package | 5.3.18-lp152.66.2 | x86_64 | openSUSE:Leap:15.2:Update
i+ | kernel-default-devel | package | 5.3.18-lp152.66.2 | x86_64 | Main Update Repository
i+ | kernel-default-devel | package | 5.3.18-lp152.63.1 | x86_64 | openSUSE:Leap:15.2:Update
i+ | kernel-default-devel | package | 5.3.18-lp152.63.1 | x86_64 | Main Update Repository
i | kernel-devel | package | 5.3.18-lp152.66.2 | noarch | openSUSE:Leap:15.2:Update
i | kernel-devel | package | 5.3.18-lp152.66.2 | noarch | Main Update Repository
i | kernel-devel | package | 5.3.18-lp152.63.1 | noarch | openSUSE:Leap:15.2:Update
i | kernel-devel | package | 5.3.18-lp152.63.1 | noarch | Main Update Repository
i+ | kernel-devel-rt | package | 5.3.18-lp152.3.5.1 | noarch | openSUSE:Leap:15.2:Update
i+ | kernel-devel-rt | package | 5.3.18-lp152.3.5.1 | noarch | Main Update Repository
i+ | kernel-firmware | package | 20200107-lp152.2.6.1 | noarch | openSUSE:Leap:15.2:Update
i+ | kernel-firmware | package | 20200107-lp152.2.6.1 | noarch | Main Update Repository
i+ | kernel-macros | package | 5.3.18-lp152.66.2 | noarch | openSUSE:Leap:15.2:Update
i+ | kernel-macros | package | 5.3.18-lp152.66.2 | noarch | Main Update Repository
i | kernel-preempt | package | 5.3.18-lp152.66.2 | x86_64 | openSUSE:Leap:15.2:Update
i | kernel-preempt | package | 5.3.18-lp152.66.2 | x86_64 | Main Update Repository
i | kernel-preempt-devel | package | 5.3.18-lp152.66.2 | x86_64 | openSUSE:Leap:15.2:Update
i | kernel-preempt-devel | package | 5.3.18-lp152.66.2 | x86_64 | Main Update Repository
i | kernel-preempt-devel | package | 5.3.18-lp152.63.1 | x86_64 | openSUSE:Leap:15.2:Update
i | kernel-preempt-devel | package | 5.3.18-lp152.63.1 | x86_64 | Main Update Repository
i+ | kernel-rt | package | 5.3.18-lp152.3.5.1 | x86_64 | openSUSE:Leap:15.2:Update
i+ | kernel-rt | package | 5.3.18-lp152.3.5.1 | x86_64 | Main Update Repository
i+ | kernel-rt | package | 5.3.18-lp152.3.2.1 | x86_64 | openSUSE:Leap:15.2:Update
i+ | kernel-rt | package | 5.3.18-lp152.3.2.1 | x86_64 | Main Update Repository
i | kernel-rt-devel | package | 5.3.18-lp152.3.5.1 | x86_64 | openSUSE:Leap:15.2:Update
i | kernel-rt-devel | package | 5.3.18-lp152.3.5.1 | x86_64 | Main Update Repository
i | kernel-source | package | 5.3.18-lp152.66.2 | noarch | openSUSE:Leap:15.2:Update
i | kernel-source | package | 5.3.18-lp152.66.2 | noarch | Main Update Repository
i | kernel-source | package | 5.3.18-lp152.63.1 | noarch | openSUSE:Leap:15.2:Update
i | kernel-source | package | 5.3.18-lp152.63.1 | noarch | Main Update Repository
i+ | kernel-source-rt | package | 5.3.18-lp152.3.5.1 | noarch | openSUSE:Leap:15.2:Update
i+ | kernel-source-rt | package | 5.3.18-lp152.3.5.1 | noarch | Main Update Repository
i | kernel-syms | package | 5.3.18-lp152.66.2 | x86_64 | openSUSE:Leap:15.2:Update
i | kernel-syms | package | 5.3.18-lp152.66.2 | x86_64 | Main Update Repository
i | kernel-syms | package | 5.3.18-lp152.63.1 | x86_64 | openSUSE:Leap:15.2:Update
i | kernel-syms | package | 5.3.18-lp152.63.1 | x86_64 | Main Update Repository
i+ | nfs-kernel-server | package | 2.1.1-lp152.9.6.1 | x86_64 | openSUSE:Leap:15.2:Update
i+ | nfs-kernel-server | package | 2.1.1-lp152.9.6.1 | x86_64 | Main Update Repository
i+ | patterns-devel-base-devel_kernel | package | 20170319-lp152.6.3 | x86_64 | Main Repository
i+ | purge-kernels-service | package | 0-lp152.4.1 | noarch | Main Repository
i | python3-virtualbox | package | 6.1.18-lp152.2.14.1 | x86_64 | openSUSE:Leap:15.2:Update
i | python3-virtualbox | package | 6.1.18-lp152.2.14.1 | x86_64 | Main Update Repository
i+ | virtualbox | package | 6.1.18-lp152.2.14.1 | x86_64 | openSUSE:Leap:15.2:Update
i+ | virtualbox | package | 6.1.18-lp152.2.14.1 | x86_64 | Main Update Repository
i+ | virtualbox-devel | package | 6.1.18-lp152.2.14.1 | x86_64 | openSUSE:Leap:15.2:Update
i+ | virtualbox-devel | package | 6.1.18-lp152.2.14.1 | x86_64 | Main Update Repository
i+ | virtualbox-guest-tools | package | 6.1.18-lp152.2.14.1 | x86_64 | openSUSE:Leap:15.2:Update
i+ | virtualbox-guest-tools | package | 6.1.18-lp152.2.14.1 | x86_64 | Main Update Repository
i+ | virtualbox-host-source | package | 6.1.18-lp152.2.14.1 | noarch | openSUSE:Leap:15.2:Update
i+ | virtualbox-host-source | package | 6.1.18-lp152.2.14.1 | noarch | Main Update Repository
i | virtualbox-kmp-default | package | 6.1.18_k5.3.18_lp152.63-lp152.2.14.1 | x86_64 | openSUSE:Leap:15.2:Update
i | virtualbox-kmp-default | package | 6.1.18_k5.3.18_lp152.63-lp152.2.14.1 | x86_64 | Main Update Repository
i | virtualbox-kmp-preempt | package | 6.1.18_k5.3.18_lp152.63-lp152.2.14.1 | x86_64 | openSUSE:Leap:15.2:Update
i | virtualbox-kmp-preempt | package | 6.1.18_k5.3.18_lp152.63-lp152.2.14.1 | x86_64 | Main Update Repository
i | virtualbox-qt | package | 6.1.18-lp152.2.14.1 | x86_64 | openSUSE:Leap:15.2:Update
i | virtualbox-qt | package | 6.1.18-lp152.2.14.1 | x86_64 | Main Update Repository
↧

LEAP 15.2 Snapshot folder location?

April 6, 2021, 7:46 pm
$
0
0
Where is the default folder location for the snapshot's? I want to change it to another hd to preserve disk space on the main hd. And, where do I actually make this change being its not available as a Menu or xml option on the Virtual Machine Manager's UI?
↧
↧

LEAP 15.2 Can't install MATE Desktop Environment

April 6, 2021, 11:50 pm
$
0
0
Using instructions here: https://en.opensuse.org/Portal:MATE


Code:
The installation was only partially successful.
The following packages cannot be installed patterns-openSUSE-mate
Code:
2021-04-07 08:05:10 <1> lin(25621) [zypper] repos.cc(add_repo):1268 Repository successfully added: --------------------------------------
2021-04-07 08:05:10 <1> lin(25621) [zypper] repos.cc(add_repo):1268 - alias      : X11_MATE_Current
2021-04-07 08:05:10 <1> lin(25621) [zypper] repos.cc(add_repo):1268 - name        : The latest official release of MATE (openSUSE_Leap_15.2)
2021-04-07 08:05:10 <1> lin(25621) [zypper] repos.cc(add_repo):1268 - enabled    : 1
2021-04-07 08:05:10 <1> lin(25621) [zypper] repos.cc(add_repo):1268 - autorefresh : 0
2021-04-07 08:05:10 <1> lin(25621) [zypper] repos.cc(add_repo):1268 - url        : https://download.opensuse.org/repositories/X11:/MATE:/Current/openSUSE_Leap_15.2/
2021-04-07 08:05:10 <1> lin(25621) [zypp++] RepoInfo.cc(probeCache):65 Probed cached type NONE at /var/cache/zypp/raw/X11_MATE_Current
2021-04-07 08:05:10 <1> lin(25621) [zypper] repos.cc(add_repo):1268 - type        : NONE
2021-04-07 08:05:10 <1> lin(25621) [zypper] repos.cc(add_repo):1268 - priority    : 99
2021-04-07 08:05:10 <1> lin(25621) [zypper] repos.cc(add_repo):1268 - gpgcheck    : Y repoD(Y)* sig? pkgD(Y)*
2021-04-07 08:05:10 <1> lin(25621) [zypper] repos.cc(add_repo):1268 - gpgkey      : https://download.opensuse.org/repositories/X11:/MATE:/Current/openSUSE_Leap_15.2/repodata/repomd.xml.key
2021-04-07 08:05:10 <1> lin(25621) [zypper] repos.cc(add_repo):1268 - filePath:    /etc/zypp/repos.d/X11_MATE_Current.repo
2021-04-07 08:05:10 <1> lin(25621) [zypper] repos.cc(add_repo):1268 - metadataPath: /var/cache/zypp/raw/X11_MATE_Current
2021-04-07 08:05:10 <1> lin(25621) [zypper] repos.cc(add_repo):1268 - packagesPath: /var/cache/zypp/packages/X11_MATE_Current
2021-04-07 08:05:10 <1> lin(25621) [zypper] repos.cc(add_repo):1268
2021-04-07 08:05:10 <2> lin(25621) [zypper] Zypper.h(setExitCode):164 setExitCode 0
2021-04-07 08:05:10 <1> lin(25621) [zypper] Zypper.cc(doCommand):685 Done
2021-04-07 08:05:10 <1> lin(25621) [zypper] Zypper.cc(cleanup):737 START
2021-04-07 08:05:10 <1> lin(25621) [zypp] PathInfo.cc(dirForEach):562 readdir /usr/lib/zypp/plugins/appdata
2021-04-07 08:05:10 <1> lin(25621) [zypp++] RepoInfo.cc(probeCache):65 Probed cached type rpm-md at /var/cache/zypp/raw/NVIDIA
2021-04-07 08:05:10 <1> lin(25621) [zypp++] RepoInfo.cc(probeCache):65 Probed cached type NONE at /var/cache/zypp/raw/X11_MATE_Current
2021-04-07 08:05:10 <1> lin(25621) [zypp++] RepoInfo.cc(probeCache):65 Probed cached type rpm-md at /var/cache/zypp/raw/download.opensuse.org-non-oss
2021-04-07 08:05:10 <1> lin(25621) [zypp++] RepoInfo.cc(probeCache):65 Probed cached type rpm-md at /var/cache/zypp/raw/download.opensuse.org-non-oss_1
2021-04-07 08:05:10 <1> lin(25621) [zypp++] RepoInfo.cc(probeCache):65 Probed cached type rpm-md at /var/cache/zypp/raw/download.opensuse.org-oss
2021-04-07 08:05:10 <1> lin(25621) [zypp++] RepoInfo.cc(probeCache):65 Probed cached type rpm-md at /var/cache/zypp/raw/download.opensuse.org-oss_1
2021-04-07 08:05:10 <1> lin(25621) [zypp++] RepoInfo.cc(probeCache):65 Probed cached type rpm-md at /var/cache/zypp/raw/http-download.opensuse.org-a2593d2f
2021-04-07 08:05:10 <1> lin(25621) [zypp++] RepoInfo.cc(probeCache):65 Probed cached type rpm-md at /var/cache/zypp/raw/https-download.opensuse.org-175386cd
2021-04-07 08:05:10 <1> lin(25621) [zypp++] RepoInfo.cc(probeCache):65 Probed cached type rpm-md at /var/cache/zypp/raw/https-download.opensuse.org-80b6df95
2021-04-07 08:05:10 <1> lin(25621) [zypp++] RepoInfo.cc(probeCache):65 Probed cached type rpm-md at /var/cache/zypp/raw/https-download.opensuse.org-966a59b1
2021-04-07 08:05:10 <1> lin(25621) [zypp++] RepoInfo.cc(probeCache):65 Probed cached type rpm-md at /var/cache/zypp/raw/mozilla
2021-04-07 08:05:10 <1> lin(25621) [zypp++] RepoInfo.cc(probeCache):65 Probed cached type rpm-md at /var/cache/zypp/raw/packman_new
2021-04-07 08:05:10 <1> lin(25621) [zypp++] RepoInfo.cc(probeCache):65 Probed cached type rpm-md at /var/cache/zypp/raw/repo-update
2021-04-07 08:05:10 <1> lin(25621) [zypp::exec++] ExternalProgram.cc(start_program):260 Executing '/usr/lib/zypp/plugins/appdata/InstallAppdata' '-R' 'NVIDIA' '-t' 'rpm-md' '-p' '/var/cache/zypp/raw/NVIDIA' '-R' 'X11_MATE_Current' '-t' 'NONE' '-p' '/var/cache/zypp/raw/X11_MATE_Current' '-R' 'download.opensuse.org-non-oss' '-t' 'rpm-md' '-p' '/var/cache/zypp/raw/download.opensuse.org-non-oss' '-R' 'download.opensuse.org-non-oss_1' '-t' 'rpm-md' '-p' '/var/cache/zypp/raw/download.opensuse.org-non-oss_1' '-R' 'download.opensuse.org-oss' '-t' 'rpm-md' '-p' '/var/cache/zypp/raw/download.opensuse.org-oss' '-R' 'download.opensuse.org-oss_1' '-t' 'rpm-md' '-p' '/var/cache/zypp/raw/download.opensuse.org-oss_1' '-R' 'http-download.opensuse.org-a2593d2f' '-t' 'rpm-md' '-p' '/var/cache/zypp/raw/http-download.opensuse.org-a2593d2f' '-R' 'https-download.opensuse.org-175386cd' '-t' 'rpm-md' '-p' '/var/cache/zypp/raw/https-download.opensuse.org-175386cd' '-R' 'https-download.opensuse.org-80b6df95' '-t' 'rpm-md' '-p' '/var/cache/zypp/raw/https-download.opensuse.org-80b6df95' '-R' 'https-download.opensuse.org-966a59b1' '-t' 'rpm-md' '-p' '/var/cache/zypp/raw/https-download.opensuse.org-966a59b1' '-R' 'mozilla' '-t' 'rpm-md' '-p' '/var/cache/zypp/raw/mozilla' '-R' 'packman_new' '-t' 'rpm-md' '-p' '/var/cache/zypp/raw/packman_new' '-R' 'repo-update' '-t' 'rpm-md' '-p' '/var/cache/zypp/raw/repo-update' < '/dev/null' > '/dev/null'
2021-04-07 08:05:10 <1> lin(25621) [zypp::exec++] ExternalProgram.cc(start_program):444 pid 25623 launched
2021-04-07 08:05:10 <1> lin(25621) [zypper] main.cc(~Bye):86 ===== Exiting main() =====
2021-04-07 08:05:10 <1> lin(25621) [zypper] Zypper.cc(~Zypper):196 Zypper instance destroyed. Bye!
2021-04-07 08:05:10 <1> lin(25621) [zypp] PathInfo.cc(recursive_rmdir):435 recursive_rmdir /var/tmp/zypp.NJr2aI
2021-04-07 08:05:10 <1> lin(25621) [zypp++] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/zypp.NJr2aI{d 0700 0/0}
2021-04-07 08:05:10 <1> lin(25621) [zypp] ZYppFactory.cc(_openLockFile):167 Open lockfile /run/zypp.pid
2021-04-07 08:05:10 <1> lin(25621) [zypp] ZYppFactory.cc(~ZYppGlobalLock):116 Cleaned lock file. (25621)
2021-04-07 08:05:10 <1> lin(25621) [zypp] ZYppFactory.cc(_closeLockFile):185 Close lockfile /run/zypp.pid
2021-04-07 08:05:10 <1> lin(25621) [zypp] ZYppFactory.cc(~ZYpp):317 ZYpp is off...
is it please working for others ?
↧

TUMBLEWEED Wacom pen not being recognised after recent updates in Tumbleweed

April 7, 2021, 2:51 am
$
0
0
I have a Wacom Intuos 5 Pro pen tablet. It always was recognised as the in system settings. Now it is seen as
Code:
unknwon Waltop device ox26 [0026]
and the buttons don't match properly etc. I have tried reinstalling all the Wacom related files and the KCM for tablet recognition. All that fixed this one time it happened before after another update. I can't seem to find my way out of this problem. Any help would be much appreciated.
↧
Search

LEAP 15.2 mate-terminal - almost invisible menu

April 7, 2021, 2:54 am
$
0
0
menu text color is white.
TraditionalGreen theme is used.





Anyone know please how to make text readable ?
↧

LEAP 15.2 VPN client with pre-shared key (PSK) authentication

April 7, 2021, 5:36 am
$
0
0
Hello,
a need to configure VPN client with the following parameters,
- ip adress
- user/pass
- PKK ( pre-shared key)

I was trying to use openfortivpn, but it seems like openfortivpn can be use only for VPN SSL connection.
Since I have to authenticate by PSK probably I need VPN IPsec.

Does somebody know which linux vpn client will be the best to set-up this configuration ?
Or how to configure VPN IPsec this connection on OpenSuse LEAP 15.2 ?

Best Regards,
↧
↧

openSUSE-SU-2021:0515-1: important: Security update for chromium

April 7, 2021, 6:20 am
$
0
0
openSUSE Security Update: Security update for chromium ______________________________________________________________________________ Announcement ID: openSUSE-SU-2021:0515-1 Rating: important References: #1184256 Cross-References: CVE-2021-21194 CVE-2021-21195 CVE-2021-21196 CVE-2021-21197 CVE-2021-21198 CVE-2021-21199 Affected Products: openSUSE Backports SLE-15-SP2 ______________________________________________________________________________ An update that fixes 6 vulnerabilities is now available. Description: This update for chromium fixes the following issues: Update to 89.0.4389.114 boo#1184256 - CVE-2021-21194: Use after free in screen capture - CVE-2021-21195: Use after free in V8 - CVE-2021-21196: Heap buffer overflow in TabStrip - CVE-2021-21197: Heap buffer overflow in TabStrip - CVE-2021-21198: Out of bounds read in IPC - CVE-2021-21199: Use Use after free in Aura This update was imported from the openSUSE:Leap:15.2:Update update project. Patch Instructions: To install this openSUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". Alternatively you can run the command listed for your product: - openSUSE Backports SLE-15-SP2: zypper in -t patch openSUSE-2021-515=1 Package List: - openSUSE Backports SLE-15-SP2 (aarch64 x86_64): chromedriver-89.0.4389.114-bp152.2.68.1 chromium-89.0.4389.114-bp152.2.68.1 References: https://www.suse.com/security/cve/CVE-2021-21194.html https://www.suse.com/security/cve/CVE-2021-21195.html https://www.suse.com/security/cve/CVE-2021-21196.html https://www.suse.com/security/cve/CVE-2021-21197.html https://www.suse.com/security/cve/CVE-2021-21198.html https://www.suse.com/security/cve/CVE-2021-21199.html https://bugzilla.suse.com/1184256

More...
↧

LEAP 15.2 MATE: Application and Places menu buttons are not visible

April 7, 2021, 7:14 am
↧

TUMBLEWEED What is the best partitioning/encryption layout for a desktop user?

April 7, 2021, 9:58 am
$
0
0
Greetings!

As a new Linux user, I find the whole partitioning and encryption business in Linux is rather complicated. Of course, you can simply use a guided partitioner in OpenSUSE (or similar easy setups from other distributions) and just check the mark to encrypt the device, but this doesn't do exactly what I want.

And what I want is (from most important to least):

  1. Full encryption of all my internal partitions/drives. From what I've read the only thing you can't encrypt is efi partion. Is that correct?
  2. No need to enter a password separately for every encrypted partition.
  3. Ability to suspend to disk.
  4. Flexibility to expand/shrink encrypted partition if necessary. And to add new encrypted internal drives without the need to enter separate password for them on boot.
  5. Easy reinstall.


Some layouts I consider:


  1. Single encrypted BTRFS partition, no lvm


From my research, I think a single btrfs root partition without a separate home must be what I want. It is flexible - you don't need to preallocate space for root and home. And I believe, it is easy to reinstall - if you reinstall the system the installer should recognize @home subvolume and not destroy/overwrite it, but mount it as a new home, at least if you use btrfs on your new installation too. Correct?

It will be nice to have everything including swap on one btrfs partition. Cause if you have swap on a separate partition then you have to encrypt it separately, and use a separate password to unlock it, right? (I am aware that of lvm, but we don't use it in this layout).

It is easy to create a swap partition in installer, but is it possible and how to create a working btrfs swap subvolume? And can we then use it to suspend to disk?

From what I understand you can expand a btrfs partition and add new drives in it. But since we have an encrypted btrfs partion, in another words a partion in an encrypted LUKS container, we can't expand it or add new drives in it it, because we cannot expand a luks container, unless it is inside an lvm, am I correct?

So, if we add new drives that we want to encrypt in this layout, we have to encrypt them separately, and enter separate passwords for them on boot, right?



  1. Single encrypted LVM partition.


Say now we have a btrfs partion like previously, but inside an encrypted LVM.

Now we don't have to worry about separate swap a partition, because it is inside an encrypted LVM anyway.

On the other hand I've read that LVM makes data recovery from LUKS encrypted partitions much more difficult. And we still can't expand it, because it is encrypted, right?

Also, with btrfs, LVM feels redundant, because btrfs has all the features of LVM, such as flexible partioning, snapshots, etc.



  1. LUKS on LVM. Volume group with multiple LVs, that have luks encrypted partitions inside them.


For example we have an LV that contains encrypted root partion, and we can have an LV for another drive. That way we can expand our LVs and encrypted partions they contain, but we still need to have separate passwords for other drives, if I understand correctly. And this whole setup is quite complicated.

-----


Possible solution for entering password multiple times with multiple partitions:

Since we have boot partition encrypted we have 2 enter password at least twice on boot. There is a way to avoid that, as described here, but according to this statement in this thread:

Quote:
The disadvantage: you now have an encryption key in a file in the root file system. And you also have it in the "initrd". The more copies, the more likely that it will leak. However, the file in the root file system is readable only by root, and the "initrd" is readable only by root. So some folk think this is a reasonable approach.

If you later install Xen support on a UEFI machine, the "initrd" will be copied to the EFI partition. And that make it readable by anyone with sufficient access to your machine. So the encryption key has been made more readily accessible, which is risky.
It comes with security compromise. And entering the password twice is fine by me then.

But if we have more than 1 encrypted partition we would have to type password more for every additional partition we have. It seems one (and only?) way to avoid this is to create a keyfile somewhere in the root partition and configure cryptab and fstab to automatically use it to decrypt other partitions after the root partition is decrypted. It seems it doesn't come with all security compromises of decrypting the root with keyfile, because for non-root partitions, we don't add keyfiles to initframs. Is that correct?


In overall, does what I wrote here makes sense? What partitioning and encryption layout can you suggest given my requirements? Something I described above or something else? If you use encryption yourself, how do you paritition you drives?
↧
Viewing all 40713 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>