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

TUMBLEWEED Update from Linux version 5.3.8-1-default to Linux version 5.3.11-1-default breaks wireless

$
0
0
Hello,
with updating from Linux version 5.3.8-1-default to Linux version 5.3.11-1-default I am not able to use wireless anymore. :'(

I am using the following device:
Code:

04:01.0 Network controller: Qualcomm Atheros AR9227 Wireless Network Adapter (rev 01)
04:01.0 0280: 168c:002d (rev 01)

With Linux version 5.3.8-1-default I can see the following in the journalctl:
Code:

-- Logs begin at Mon 2019-05-06 16:05:22 CEST, end at Sat 2019-11-23 17:42:13 CET. --
Nov 23 09:42:19 willnixWlan kernel: microcode: microcode updated early to revision 0x27, date = 2019-02-26
Nov 23 09:42:19 willnixWlan kernel: Linux version 5.3.8-1-default (geeko@buildhost) (gcc version 9.2.1 20190903 [gcc-9-branch revision 275330] (SUSE Linux)) #1 SMP Wed Oct 30 07:12:05 UTC 2019 (ea4c828)
.
Nov 23 09:42:22 willnixWlan kernel: ath9k 0000:04:01.0: enabling device (0000 -> 0002)
.
Nov 23 09:42:22 willnixWlan systemd-udevd[516]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 23 09:42:22 willnixWlan kernel: ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Nov 23 09:42:22 willnixWlan kernel: ieee80211 phy0: Atheros AR9287 Rev:2 mem=0xffffac3e80cf0000, irq=16
Nov 23 09:42:22 willnixWlan kernel: ath9k 0000:04:01.0 wlp4s1: renamed from wlan0
.
Nov 23 09:42:22 willnixWlan systemd[1]: Starting wicked AutoIPv4 supplicant service...
Nov 23 09:42:22 willnixWlan systemd[1]: Starting wicked DHCPv4 supplicant service...
Nov 23 09:42:22 willnixWlan systemd[1]: Starting wicked DHCPv6 supplicant service...
.
Nov 23 09:42:23 willnixWlan systemd[1]: Started wicked DHCPv4 supplicant service.
Nov 23 09:42:23 willnixWlan systemd[1]: Started wicked DHCPv6 supplicant service.
Nov 23 09:42:23 willnixWlan systemd[1]: Starting wicked network management service daemon...
.
Nov 23 09:42:48 willnixWlan dbus-daemon[1108]: [system] Failed to activate service 'fi.epitest.hostap.WPASupplicant': timed out (service_start_timeout=25000ms)
Nov 23 09:42:48 willnixWlan wickedd[1163]: ni_wpa_interface_bind(wlp4s1): Operation not permitted
Nov 23 09:42:48 willnixWlan wickedd[1163]: wpa_supplicant doesn't know interface wlp4s1
Nov 23 09:42:48 willnixWlan wickedd-nanny[1262]: device wlp4s1: call to org.opensuse.Network.Wireless.changeDevice() failed: General failure
Nov 23 09:42:48 willnixWlan wickedd-nanny[1262]: wlp4s1: failed to bring up device, still continuing
Nov 23 09:42:48 willnixWlan wicked[1263]: lo              up
Nov 23 09:42:48 willnixWlan wicked[1263]: eno1            device-not-running
Nov 23 09:42:48 willnixWlan wicked[1263]: wlp4s1          device-not-running
Nov 23 09:42:48 willnixWlan systemd[1]: Started wicked managed network interfaces.
Nov 23 09:42:48 willnixWlan systemd[1]: Reached target Network.
.
.
.
Nov 23 09:42:48 willnixWlan systemd[1]: Started wlan_if_up.service.
Nov 23 09:42:48 willnixWlan systemd[1]: Starting WPA Supplicant daemon...
Nov 23 09:42:48 willnixWlan systemd[1]: Started WPA Supplicant daemon.
.
Nov 23 09:42:48 willnixWlan wickedd[1163]: unable to translate eap protocol PWD
.
Nov 23 09:42:49 willnixWlan kernel: wlp4s1: authenticate with 24:65:11:05:3f:c0
Nov 23 09:42:49 willnixWlan kernel: wlp4s1: send auth to 24:65:11:05:3f:c0 (try 1/3)
Nov 23 09:42:49 willnixWlan kernel: wlp4s1: authenticated
Nov 23 09:42:49 willnixWlan kernel: wlp4s1: associate with 24:65:11:05:3f:c0 (try 1/3)
Nov 23 09:42:49 willnixWlan kernel: wlp4s1: RX AssocResp from 24:65:11:05:3f:c0 (capab=0x431 status=0 aid=1)
Nov 23 09:42:49 willnixWlan kernel: wlp4s1: associated
Nov 23 09:42:49 willnixWlan wickedd-dhcp4[1122]: wlp4s1: Request to acquire DHCPv4 lease with UUID 08f1d85d-2e9e-0900-8b04-000006000000
Nov 23 09:42:49 willnixWlan wickedd-dhcp6[1125]: wlp4s1: Request to acquire DHCPv6 lease with UUID 08f1d85d-2e9e-0900-8b04-000007000000 in mode auto
Nov 23 09:42:49 willnixWlan kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s1: link becomes ready

Then doing the update
Code:

-- Reboot --
Nov 23 15:57:14 willnixWlan kernel: ath9k 0000:04:01.0 wlp4s1: renamed from wlan0

Nov 23 15:57:40 willnixWlan systemd[1]: Reached target Network.
.
.
Nov 23 15:57:43 willnixWlan kernel: wlp4s1: authenticate with 24:65:11:05:3f:c0
Nov 23 15:57:43 willnixWlan kernel: wlp4s1: send auth to 24:65:11:05:3f:c0 (try 1/3)
Nov 23 15:57:43 willnixWlan kernel: wlp4s1: authenticated
Nov 23 15:57:43 willnixWlan kernel: wlp4s1: associate with 24:65:11:05:3f:c0 (try 1/3)
Nov 23 15:57:43 willnixWlan kernel: wlp4s1: RX AssocResp from 24:65:11:05:3f:c0 (capab=0x431 status=0 aid=1)
Nov 23 15:57:43 willnixWlan kernel: wlp4s1: associated
Nov 23 15:57:43 willnixWlan wickedd-dhcp4[1115]: wlp4s1: Request to acquire DHCPv4 lease with UUID e548d95d-6930-0300-e904-000006000000
Nov 23 15:57:43 willnixWlan wickedd-dhcp6[1116]: wlp4s1: Request to acquire DHCPv6 lease with UUID e548d95d-6930-0300-e904-000007000000 in mode auto
Nov 23 15:57:43 willnixWlan kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s1: link becomes ready
Nov 23 15:57:44 willnixWlan wickedd-dhcp4[1115]: wlp4s1: Committed DHCPv4 lease with address 192.168.178.21 (lease time 864000 sec, renew in 432000 sec, rebind in 756000 sec)
Nov 23 15:57:44 willnixWlan avahi-daemon[1104]: Joining mDNS multicast group on interface wlp4s1.IPv4 with address 192.168.178.21.
Nov 23 15:57:44 willnixWlan avahi-daemon[1104]: New relevant interface wlp4s1.IPv4 for mDNS.
Nov 23 15:57:44 willnixWlan avahi-daemon[1104]: Registering new address record for 192.168.178.21 on wlp4s1.IPv4.
Nov 23 15:57:45 willnixWlan avahi-daemon[1104]: Joining mDNS multicast group on interface wlp4s1.IPv6 with address fe80::b248:7aff:febf:7199.
Nov 23 15:57:45 willnixWlan avahi-daemon[1104]: New relevant interface wlp4s1.IPv6 for mDNS.
Nov 23 15:57:45 willnixWlan avahi-daemon[1104]: Registering new address record for fe80::b248:7aff:febf:7199 on wlp4s1.*.
Nov 23 15:57:46 willnixWlan avahi-daemon[1104]: Leaving mDNS multicast group on interface wlp4s1.IPv6 with address fe80::b248:7aff:febf:7199.
Nov 23 15:57:46 willnixWlan avahi-daemon[1104]: Joining mDNS multicast group on interface wlp4s1.IPv6 with address 2002:4e2b:b460:0:b248:7aff:febf:7199.
Nov 23 15:57:46 willnixWlan avahi-daemon[1104]: Registering new address record for 2002:4e2b:b460:0:b248:7aff:febf:7199 on wlp4s1.*.
Nov 23 15:57:46 willnixWlan avahi-daemon[1104]: Withdrawing address record for fe80::b248:7aff:febf:7199 on wlp4s1.
Nov 23 15:57:47 willnixWlan avahi-daemon[1104]: Registering new address record for 2002:4e2b:b460:0:c836:f798:6a8d:ba7a on wlp4s1.*.
Nov 23 15:57:47 willnixWlan systemd[1]: wlan_if_up.service: Succeeded.
Nov 23 15:57:47 willnixWlan wickedd-dhcp6[1116]: wlp4s1: Committing empty DHCPv6 lease
.
.
Nov 23 16:31:38 willnixWlan PackageKit[4041]: update-packages transaction /5_dddbbacb from uid 1001 finished with success after 1831918ms
.
Nov 23 16:31:54 willnixWlan plasmashell[2826]: PK error: "Download (curl) error for 'http://packman.inode.at/suse/openSUSE_Tumbleweed/repodata/repomd.xml':\nError code: Connection failed\nError message: Could not resolve host: packman.inode.at\n" type:
.
Nov 23 16:33:52 willnixWlan dbus-daemon[1106]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.13" (uid=0 pid=1257 comm="/usr/sbin/wickedd --systemd --foreground ") interface="fi.epitest.hostap.WPASupplicant.Interface" member="removeNetwork" error name="(unset)" requested_reply="0" destination="fi.epitest.hostap.WPASupplicant" (bus)
Nov 23 16:33:52 willnixWlan wickedd[1257]: wlp4s1: failed to remove network
Nov 23 16:33:52 willnixWlan wicked[32537]: eno1            device-ready
Nov 23 16:33:52 willnixWlan wicked[32537]: wlp4s1          device-ready
Nov 23 16:33:52 willnixWlan systemd[1]: wicked.service: Succeeded.
Nov 23 16:33:52 willnixWlan systemd[1]: Stopped wicked managed network interfaces.
Nov 23 16:33:52 willnixWlan systemd[1]: Stopping wicked network nanny service...
Nov 23 16:33:52 willnixWlan systemd[1]: wickedd-nanny.service: Succeeded.
Nov 23 16:33:52 willnixWlan systemd[1]: Stopped wicked network nanny service.
Nov 23 16:33:52 willnixWlan systemd[1]: Stopping wicked network management service daemon...
Nov 23 16:33:52 willnixWlan systemd[1]: wickedd.service: Succeeded.

.
.
-- Reboot --
Nov 23 16:34:19 willnixWlan kernel: microcode: microcode updated early to revision 0x27, date = 2019-02-26
Nov 23 16:34:19 willnixWlan kernel: Linux version 5.3.11-1-default (geeko@buildhost) (gcc version 9.2.1 20190903 [gcc-9-branch revision 275330] (SUSE Linux)) #1 SMP Tue Nov 12 18:57:39 UTC 2019 (0a195a8)
Nov 23 16:34:19 willnixWlan kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.11-1-default root=UUID=74c38799-8fc9-480e-bab9-b62ad23f8aaf resume=/dev/disk/by-uuid/f0087c95-02f8-4e28-8952-56b8de9055a7 splash=silent quiet showopts
.
.
.
Nov 23 16:34:22 willnixWlan kernel: ath9k 0000:04:01.0: enabling device (0000 -> 0002)
.
.
Nov 23 16:34:22 willnixWlan kernel: ath9k 0000:04:01.0 wlp4s1: renamed from wlan0
Nov 23 16:34:22 willnixWlan systemd-udevd[500]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.





Nov 23 16:34:23 willnixWlan systemd[1]: Starting wicked AutoIPv4 supplicant service...







Nov 23 16:34:23 willnixWlan systemd[1]: Started wicked network management service daemon.
Nov 23 16:34:23 willnixWlan systemd[1]: Starting wicked network nanny service...
Nov 23 16:34:23 willnixWlan systemd[1]: Started wicked network nanny service.
Nov 23 16:34:23 willnixWlan systemd[1]: Starting wicked managed network interfaces...
Nov 23 16:34:23 willnixWlan kernel: No iBFT detected.
Nov 23 16:34:23 willnixWlan dbus-daemon[1097]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.13" (uid=0 pid=1251 comm="/usr/sbin/wickedd --systemd --foreground ") interface="fi.epitest.hostap.WPASupplicant" member="getInterface" error name="(unset)" requested_reply="0" destination="fi.epitest.hostap.WPASupplicant" (bus)
Nov 23 16:34:23 willnixWlan wickedd[1251]: ni_wpa_interface_bind(wlp4s1): Interrupted system call
Nov 23 16:34:23 willnixWlan wickedd[1251]: wpa_supplicant doesn't know interface wlp4s1
Nov 23 16:34:23 willnixWlan wickedd-nanny[1262]: device wlp4s1: call to org.opensuse.Network.Wireless.changeDevice() failed: General failure
Nov 23 16:34:23 willnixWlan wickedd-nanny[1262]: wlp4s1: failed to bring up device, still continuing
Nov 23 16:34:23 willnixWlan wickedd[1251]: ni_process_reap: process 1266 has not exited yet; now doing a blocking waitpid()



Nov 23 16:34:25 willnixWlan ModemManager[1093]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin
Nov 23 16:34:25 willnixWlan ModemManager[1093]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.3/0000:03:00.0/0000:04:01.0': not supported by any plugin
Nov 23 16:34:26 willnixWlan wicked[1263]: lo              setup-in-progress
Nov 23 16:34:26 willnixWlan wicked[1263]: eno1            setup-in-progress
Nov 23 16:34:26 willnixWlan wicked[1263]: wlp4s1          device-not-running
Nov 23 16:34:26 willnixWlan systemd[1]: Started wicked managed network interfaces.
Nov 23 16:34:26 willnixWlan systemd[1]: Reached target Network.

Any help welcome

How to clean .obscpio and .obsinfo so it can be submit to factory?

$
0
0
So I have been trying to get a font package to factory for a while now.

I stuck with how do I "clean" the package. Currently, I am using _service file with obs_scm.

Factory want me to remove .obsinfo, but .obsinfo is generated from _service, so what do I have to change in the _service?

Factory only allow mode="disabled",mode="localonly", and mode="buildtime"

But if I change the default mode to the above, the .obscpio will disappear and failed.



https://build.opensuse.org/package/show/home:andythe_great/cadsondemak-fonts



Thanks





TUMBLEWEED I cant share a shared folder in virt-manager/gnome-boxes

$
0
0
I'm trying to use Virt-Manager in my Opesuse Tumbleweed (PC and Laptop). I have installed a Windows MV with spice-guest-agent and spice-webdav installed. (i did some test with Fedora too)

I tried to share a folder with remote-viewer but it's disabled, I can't tick any option.


Then I tried to do the same with gnome-boxes, and I got no folder options (I cant attach a image by I exced size Post)

I tried to repeat in a Fedora MV Nested (gnome-boxes + virt-manager MV ) and I have found no problems with the same test, I can share a folder both programs, so I guess It's need to install some package to get it work.

Any idea?

Thanks!!

LEAP 15.1 Preparation for dual boot with WIN 10

$
0
0
Hi all,

Let me first quickly give you some context, to understand where I am in the process of moving to openSUSE.

A couple of weeks ago, out of curiosity and because of not being happy with Windows behaviour on this "old" computer, I decided to try Linux again (after some disappointments many years ago). I installed VMWare on Windows 10 and tried out several distro's as virtual machines: MX Linux, Manjaro, openSUSE Leap 15.1 and Tumbleweed,... After playing around with them, Manjaro didn't work out, I seriously crippled the Tumbleweed installation (my bad!) and I did not really like the XFCE of MX Linux. openSUSE never disappointed: good ease of use, yast tool and I personally like the clean, professional look of KDE Plasma. I got Google drive working, chromium, video playback, LibreOffice works just fine for some basic home usage, in short openSUSE LEAP 15.1 it will be. Next step is to install a dual boot on this machine, and really start using Linux daily.

My hardware : ATI Radeon HD5700 1 Gb DDR5 , AMD Phenom II X4 955 3.2Ghz, 8 Gb Ram, connected to wired LAN network, 1 Tb hard disk (400Gb Free), BENQ screen 1920x1080.

Current partitions :
1. 100 MB NTFS (53% free)
2. 930 GB NTFS (47% free) -- the windows C: => reduce by 330 GB ??
3. 850 MB Repair Partitions (100% free) => delete ??

What I want to do :
1. 100 MB NTFS (53% free)
2. 600 GB NTFS (500 used, so 100 GB free) -- the windows C:
3. create / in ext4 30 Gb
4. create /home ext4 284 Gb
5. create swap 16 Gb

My questions:
1. do I resize with windows disk partitioner or during the openSUSE install?
2. I still don't understand the warnings and issues in other posts around EFI / BIOS / MBR ? What do I need to do to succesfully install the GRUB2 bootloader?
3. Is it safe to delete the windows repair partition ? (because I want to have my swap at the end of the disk)
4. any other suggestions or remarks to my proposed partitions?

Cheers!
J

TUMBLEWEED why pacman to play video

$
0
0
Hello,
I'm a new user of opensuse. I tried it some years ago, and I retried it just now. I remember last time to play video was the most difficult thing to do. Now I found that is the same. But this time I succeded to install well packman version of codec and video works well. But I would ask why standard codec of tumbleweed works only with mpeg2? What is the technical reason, and there is a possible way to play them with standard codec of tumbleweed rpm?

Thank you very much.

TUMBLEWEED Yast "package groups" view missing in Software Management

$
0
0
Hi everyone. I'm new to Tumbleweed (couple of months now) having first tried Leap. Really impressed with TW so far.

Whilst using Leap, Yast software management module had a useful 'package groups' tools under the 'view' tab. However, after installing TW 'package groups' is not there. I installed Gnome on both Leap and TW so I don't think the environment is the problem. There doesn't appear to be any missing add-on packages in the repositories and there is nothing in dconf-editor that relates to this. So is this simply down to using TW instead of Leap?

Rich

LEAP 15.1 How to install VirtualBox Guest Additions on Windows 7 guest with openSUSE host

$
0
0
I'm having trouble finding/recognizing the Guest Additions from a Leap 15.1 Host to be able to supply them to Windows 7 running in a VirtualBox.

virtualbox.org claims they are distributed as a .iso with their form of the distribution. Maybe I've missed it but I don't find such in the openSUSE .rpm's.

Yast2 isn't showing me any doc rpm's when I search for virtualbox.

Any help would be greatly appreciated.

LEAP 15.1 Nextcloud integration in Dolphin

$
0
0
Hi all. My question is can we Sync a folder in Dolphin (on the Leap 15.1 Desktop) with our Nextcloud Server? - or are we limited to using Webdav to open files on Nextcloud. My plan was to be able to sync a Folder on my Mobile Phone to Nextcloud Server to a Folder on my Desktop and for this to happen automatically.

The nextcloud-client is installed. It opens a window with two tabs - General and Network.

Dophin file manager does not appear to have a sync tool. If I select a folder and right click, I see not way to enable Sync. However if I select a single file in that folder and right click a "Share" menu appears offering to link it to Nextcloud. When I select this - a window appears with Nextcloud Upload highlighted. This window remains blank. It has options to run or cancel the operation. The run button is greyed out.

I can use webav to open files in the Nextcloud Server, but I want a sync facility to synchronize files across my internet tools. When I google I get a detailed explanation of how to do this in Nautilus File manager, but not much help with Dolphin.

Any ideas on how to proceed?

LEAP 15.1 external drive /home empty with btrfs, xfs /home shows

$
0
0
Curious if somebody can explain something I ran into. I have two external drives with Leap 15.1 installs. One was done as separate partitions and has an xfs home partition, one--for whatever reason--was a single partition btrfs with the home folder included.
When I attach these to my main system as an external drive to grab files the xfs partition will mount and show user folders in the /home and files. The btrfs one will mount and show all file systems except the /home folder shows as empty.
I'm curious if this is because of some internal /home mounting issue with the linux filesystem, User login related, or just some odd behaviour with btrfs and /home partitions.

Thanks in advance

LEAP 15.1 Akonadi & Evolution

$
0
0
According to https://userbase.kde.org/Akonadi
Quote:

The Akonadi framework is responsible for providing applications with a centralized database to store, index and retrieve the user's personal information. This includes the user's emails, contacts, calendars, events, journals, alarms, notes, etc. In SC 4.4, KAddressBook became the first application to start using the Akonadi framework. In SC 4.7, KMail, KOrganizer, KJots, etc. were updated to use Akonadi as well. In addition, several Plasma widgets also use Akonadi to store and retrieve calendar events, notes, etc.
All I really need is KMail & KAddressBook so I've been removing other Akonadi applications in an effort to make this whole unstable ediface less crash-prone. However there are still 18 Akonadi processes running, all of which presumably want to fiddle with the database.

Does anyone have any insights in how to simplify the default PIM installation? Can I just get rid of PIM altogether if I migrate to some other email client?

Does anyone have an opinion on Evolution?

David L.

Cross Build Failure to Raspbian_9.0 arm7l

$
0
0
Hi,

On an x86-64 openSUSE Leap 15.1 system I am trying to cross-build a
package with osc to Raspbian 9.0 armv7l using the following command

osc build Raspbian_9.0 armv7l

It fails with the following build log.

https://pastebin.com/raw/yQp0Kfyc

An attempt for Raspbian_10 fails in the same manner.

I have tried pre-installing qemu-user{-static} the Debian / Raspbian package but it does not help.

I'm afraid I cannot find documentation detailing such an action.

Any help would be appreciated.

Regards,
Mark

LEAP 15.1 Applicatie: Schermrecorder

$
0
0
Hallo,


Ik ben op zoek naar software dat het scherm kan opnemen.
Een schermrecorder voor beeld en geluid.


Wie weet een mooie applicatie welke onder Suse Leap 15.1 draait.


Alvast bedankt.

LEAP 15.1 KDE startet nicht

$
0
0
Hallo,
plötzlich lese ich beim Start, daß temp directory /temp out of space sei und dann
"KDE is unable to start".

Weiß jemand, was man da tun kann?

mfg
mgbd

TUMBLEWEED Important btrfs subvolumes like /root and /opt are unmounted during boot

$
0
0
Hello, for some time now I noticed that some very important btrfs subvolumes (like /root and /opt) are not mounted when I am logged in, but get mounted without problems if I run `mount -a`.

Checking the journal from boot time, it seems they get mounted in the beginning, get unmounted soon afterwards, and finally only few of them get remounted. In detail, I see the following messages after boot:

Code:

Nov 25 11:59:16  systemd[1]: Condition check resulted in dracut pre-mount hook being skipped.
Nov 25 11:59:16  systemd[1]: Mounting /sysroot...
Nov 25 11:59:16  systemd[1]: Mounted /sysroot.
Nov 25 11:59:16  systemd[1]: Condition check resulted in dracut mount hook being skipped.
Nov 25 11:59:17  systemd[1]: Mounting /.snapshots...
Nov 25 11:59:17  systemd[1]: Mounting /boot/efi...
Nov 25 11:59:17  systemd[1]: Mounting /boot/grub2/i386-pc...
Nov 25 11:59:17  systemd[1]: Mounting /boot/grub2/x86_64-efi...
Nov 25 11:59:17  systemd[1]: Mounting /home...
Nov 25 11:59:17  systemd[1]: opt.mount: Directory /opt to mount over is not empty, mounting anyway.
Nov 25 11:59:17  systemd[1]: Mounting /opt...
Nov 25 11:59:17  systemd[1]: Mounting /root...
Nov 25 11:59:17  systemd[1]: Mounting /srv...
Nov 25 11:59:17  systemd[1]: Mounting /tmp...
Nov 25 11:59:17  systemd[1]: Mounting /usr/local...
Nov 25 11:59:17  systemd[1]: Mounting /var...
Nov 25 11:59:17  systemd[1]: Mounted /.snapshots.
Nov 25 11:59:17  systemd[1]: Mounted /boot/grub2/i386-pc.
Nov 25 11:59:17  systemd[1]: Mounted /boot/grub2/x86_64-efi.
Nov 25 11:59:17  systemd[1]: Mounted /home.
Nov 25 11:59:17  systemd[1]: Mounted /opt.
Nov 25 11:59:17  systemd[1]: Mounted /root.
Nov 25 11:59:17  systemd[1]: Mounted /srv.
Nov 25 11:59:17  systemd[1]: Mounted /tmp.
Nov 25 11:59:17  systemd[1]: Mounted /usr/local.
Nov 25 11:59:17  systemd[1]: Mounted /var.
Nov 25 11:59:17  kernel: FAT-fs (nvme0n1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Nov 25 11:59:17  systemd[1]: Mounted /boot/efi.

But a few seconds all the partitions get unmounted:
Code:

Nov 25 11:59:19  systemd[1]: Unmounting /.snapshots...
Nov 25 11:59:19  systemd[1]: Unmounting /boot/grub2/i386-pc...
Nov 25 11:59:19  systemd[1]: Unmounting /boot/grub2/x86_64-efi...
Nov 25 11:59:19  systemd[1]: Unmounting /home...
Nov 25 11:59:19  systemd[1]: Unmounting /opt...
Nov 25 11:59:19  systemd[1]: Unmounting /root...
Nov 25 11:59:19  systemd[1]: Unmounting /srv...
Nov 25 11:59:19  systemd[1]: Unmounting /usr/local...
[ ... ]
Nov 25 11:59:19  systemd[1]: \x2esnapshots.mount: Succeeded.
Nov 25 11:59:19  systemd[1]: Unmounted /.snapshots.
Nov 25 11:59:19  systemd[1]: boot-grub2-i386\x2dpc.mount: Succeeded.
Nov 25 11:59:19  systemd[1]: Unmounted /boot/grub2/i386-pc.
Nov 25 11:59:19  systemd[1]: boot-grub2-x86_64\x2defi.mount: Succeeded.
Nov 25 11:59:19  systemd[1]: Unmounted /boot/grub2/x86_64-efi.
Nov 25 11:59:19  systemd[1]: home.mount: Succeeded.
Nov 25 11:59:19  systemd[1]: Unmounted /home.
Nov 25 11:59:19  systemd[1]: opt.mount: Succeeded.
Nov 25 11:59:19  systemd[1]: Unmounted /opt.
Nov 25 11:59:19  systemd[1]: root.mount: Succeeded.
Nov 25 11:59:19  systemd[1]: Unmounted /root.
Nov 25 11:59:19  systemd[1]: srv.mount: Succeeded.
Nov 25 11:59:19  systemd[1]: Unmounted /srv.
Nov 25 11:59:19  systemd[1]: usr-local.mount: Succeeded.
Nov 25 11:59:19  systemd[1]: Unmounted /usr/local.
Nov 25 11:59:19  systemd[1]: Condition check resulted in /dev/system/root being skipped.
Nov 25 11:59:19  systemd[1]: Found device /dev/mapper/system-root.
Nov 25 11:59:19  systemd[1]: Found device /dev/system/swap.
Nov 25 11:59:19  systemd[1]: systemd-update-utmp.service: Succeeded.
Nov 25 11:59:19  systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
Nov 25 11:59:19  systemd[1]: Requested transaction contradicts existing jobs: Resource deadlock avoided
Nov 25 11:59:19  systemd[1]: Requested transaction contradicts existing jobs: Resource deadlock avoided
Nov 25 11:59:43  systemd[1]: Unmounting /tmp...
Nov 25 11:59:43  systemd[1]: Started Scrub btrfs filesystem, verify block checksums.
Nov 25 11:59:43  systemd[1]: tmp.mount: Succeeded.
Nov 25 11:59:43  systemd[1]: Unmounted /tmp.

Even though /home was unmounted, it gets remounted later when I login as user:
Code:

Nov 25 12:00:02  sddm[2445]: Authenticated successfully
Nov 25 12:00:02  sddm-greeter[2497]: Message received from daemon: LoginSucceeded
Nov 25 12:00:02  systemd[1]: Created slice User Slice of UID 1000.
Nov 25 12:00:02  systemd[1]: Starting User Runtime Directory /run/user/1000...
Nov 25 12:00:02  systemd-logind[2486]: New session 2 of user jimis.
Nov 25 12:00:02  systemd[1]: Mounting /home...
Nov 25 12:00:02  systemd[1]: Mounted /home.
Nov 25 12:00:02  systemd[1]: Started User Runtime Directory /run/user/1000.
Nov 25 12:00:02  systemd[1]: Starting User Manager for UID 1000...

But the rest of the important partitions remain unmounted until I run `mount -a`.

Any idea what's going on? How can I trace systemd dependencies and figure out
what is causing the unmounting of the subvolumes?

Thank you in advance.


P.S. here is my /etc/fstab:
Code:

/dev/system/root  /                      btrfs  defaults                      0  0
/dev/system/root  /var                    btrfs  subvol=/@/var                0  0
/dev/system/root  /usr/local              btrfs  subvol=/@/usr/local          0  0
/dev/system/root  /tmp                    btrfs  subvol=/@/tmp                0  0
/dev/system/root  /srv                    btrfs  subvol=/@/srv                0  0
/dev/system/root  /root                  btrfs  subvol=/@/root                0  0
/dev/system/root  /opt                    btrfs  subvol=/@/opt                0  0
/dev/system/root  /home                  btrfs  subvol=/@/home                0  0
/dev/system/root  /boot/grub2/x86_64-efi  btrfs  subvol=/@/boot/grub2/x86_64-efi  0  0
/dev/system/root  /boot/grub2/i386-pc    btrfs  subvol=/@/boot/grub2/i386-pc  0  0
UUID=123A-567B    /boot/efi              vfat  defaults                      0  0
/dev/system/swap  swap                    swap  defaults                      0  0
/dev/system/root  /.snapshots            btrfs  subvol=/@/.snapshots          0  0

TUMBLEWEED POssible to install Teamspeak3 (3.3.2 64bit) on TW?

$
0
0
Tried:
1. Right-click > make executable > run... (nothing)
2. Right-click > open with > Yast software (nothing)
3. Right-click > Actions > Konsole (get licence agreement, but no action beyond that)
4. Oneclick (but there is only an experiemental Leap package)

Anything else?

LEAP 15.1 Aigital MP4 Player - music titles out of order - creation date

$
0
0
https://www.amazon.com/Aigital-Suppo...4750913&sr=8-2

I'v had this Aigital MP4 player for while (NTFS file system). When it was connected via USB on opensuse, I renamed all the files in a few folders to make the song title visible in the player.
'01 artist name - song title' --> '01 song title'

Now the songs are out of order. In #1 is now at the end. Others have 3 or more files out of order.

I contacted tech support. The sorting order is based on creation date. So, I have to erase all the files in the folders(disordered). And copy each file one at time to get the order right again. That is 100's of files.

To avoid copying all the files again and again, I've tried using the 'touch' command to alter the times and dates. This isn't working.

Code:

for i in *.flac;do (touch -mt 11182245."${i:0:2}" "$i");done
filelist structure: [xx song title]

Code:

ls --full-time
The above code appears to work, but the player shows files (songs out of order). Copying the files one at a time does give an ordered list in the player.

Need help...

LEAP 15.1 NPO content

$
0
0
De NPO schermt zijn content bij uitzending gemist af.
Ik gebruik als browser firefox op Suse leap 15.1 met KDE.

Daarnaast schrijft NPO dat ze het platform Linux niet ondersteunen.

Weet iemand hoe de beveiliging van NPO binnen firefox is te omzeilen.
Of een applicatie die de content kan downloaden van de NPO server.

LEAP 15.0 tomcat 8.5.49 -shutdown.sh message: NOTE: Picked up JDK_JAVA_OPTIONS:

$
0
0
Hello!
How are you?

I did install tomcat 8.5.49. After install and configure, in test it starts ok at navigator but, in terminal when use command shutdown.sh it shows:

NOTE: Picked up JDK_JAVA_OPTIONS: --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED
--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED

I am reading and searching to solve this but, sorry, I do not understand where put the lines.
In setenv.sh? after JAVA_HOME

Or?

Thank you attention

OTHER VERSION VNC black screen after monitor change

$
0
0
I have an old Opensuse server (can't access it at the moment remotely) I think it is V10 with KDE desktop.

I have had to move all our servers and that has meant taking them out of a rack and stopping using the rack mount monitor. I have replaced it with a normal old monitor. Both have used a KVM switch.

Everything is working except for VNC which just produces a black screen on the remote PC.

Presumably the resolution\refresh rate is different and that is a problem.

How do I get the VNC system to recognise the new monitor?

Thanks

TUMBLEWEED Autoyast swap auto partitioning doesn't work correctly

$
0
0
Hi community,

I'm using autoyast to perform an auto installation of tumbleweed on a laptop with 16 gigs of RAM using an existing manual install as a template.
As seen in the code snippet form the autoinst.xml file posted below, I have configured the partitioning for boot/efi to auto, swap to auto and root as max.
The problem is that during installation yast sets the SWAP to 1 gig instead of 16.
Anyone know how to fix this? I can't resort to hardcoding the SWAP as i'll use this autoyast config on laptops with various RAM sized.
I have attached images with the desired disk partitioning I'm trying to emulate with autoyast.

Code:

    <partitioning config:type="list">
    <drive>
      <device>/dev/system</device>
      <enable_snapshots config:type="boolean">false</enable_snapshots>
      <initialize config:type="boolean">true</initialize>
      <partitions config:type="list">
        <partition>
          <create config:type="boolean">true</create>
          <filesystem config:type="symbol">swap</filesystem>
          <format config:type="boolean">true</format>
          <lv_name>swap</lv_name>
          <mount>swap</mount>
          <mountby config:type="symbol">device</mountby>
          <pool config:type="boolean">false</pool>
          <resize config:type="boolean">false</resize>
          <size>auto</size>
          <stripes config:type="integer">1</stripes>
          <stripesize config:type="integer">0</stripesize>
        </partition>
        <partition>
          <create config:type="boolean">true</create>
          <filesystem config:type="symbol">ext4</filesystem>
          <format config:type="boolean">true</format>
          <lv_name>root</lv_name>
          <mount>/</mount>
          <mountby config:type="symbol">device</mountby>
          <pool config:type="boolean">false</pool>
          <resize config:type="boolean">false</resize>
          <size>max</size>
          <stripes config:type="integer">1</stripes>
          <stripesize config:type="integer">0</stripesize>
        </partition>
      </partitions>
      <pesize>auto</pesize>
      <type config:type="symbol">CT_LVM</type>
    </drive>
    <drive>
      <device>/dev/nvme0n1</device>
      <disklabel>gpt</disklabel>
      <enable_snapshots config:type="boolean">false</enable_snapshots>
      <initialize config:type="boolean">true</initialize>
      <partitions config:type="list">
        <partition>
          <create config:type="boolean">true</create>
          <filesystem config:type="symbol">vfat</filesystem>
          <format config:type="boolean">true</format>
          <mount>/boot/efi</mount>
          <mountby config:type="symbol">uuid</mountby>
          <partition_id config:type="integer">259</partition_id>
          <partition_nr config:type="integer">1</partition_nr>
          <resize config:type="boolean">false</resize>
          <size>auto</size>
        </partition>
        <partition>
          <create config:type="boolean">true</create>
          <crypt_fs config:type="boolean">true</crypt_fs>
          <crypt_key>justatest</crypt_key>
          <format config:type="boolean">true</format>
          <loop_fs config:type="boolean">true</loop_fs>
          <lvm_group>system</lvm_group>
          <partition_id config:type="integer">142</partition_id>
          <partition_nr config:type="integer">2</partition_nr>
          <resize config:type="boolean">false</resize>
          <size>max</size>
        </partition>
      </partitions>
      <type config:type="symbol">CT_DISK</type>
      <use>all</use>
    </drive>
  </partitioning>



Viewing all 40713 articles
Browse latest View live