- openSUSE Support

[opensuse-support] Re: [opensuse-factory] Two Questions 2 - 1: XFCE locale
by Carlos E. R. 28 Feb '19

28 Feb '19

On 28/02/2019 15.10, Marco Calistri wrote: Moved reply to opensuse-support. > Sorry to ask here but since Tumbleweed is a bit more specific than for > example Ubuntu, I've not found any answers on the Web. > > If you think my post is too "off-topic", I invite you to reply to my > personal email and not on the list. > > 1 - How to set locale so that XFCE Desktop and system environment is > correctly configured to a specific language. > > After my attempts to configure an user to use Portuguese at his login > (attempt failed because it remained in English) once I logged back to my > user login which was set in Italian, I found it was in English and > despite many different approaches, including Yast Language, I haven't be > able to roll-back to my previous locale. > > In order to be able to do it, I had to add the following statement to my > .bashrc: > > export LC_CTYPE=it_IT.UTF-8 The correct method is to edit or create file /home/{username}/.i18n, like this: cer@Telcontar:~> cat .i18n # used by /etc/profile.d/lang.sh #CER - if it doesn't work edit /etc/profile.d/lang.sh, see Bugzilla 567324 LC_TIME=en_DK.UTF-8 LC_MONETARY=es_ES@euro LC_NUMERIC=es_ES@euro LC_PAPER=es_ES@euro LC_TELEPHONE=es_ES@euro LC_MEASUREMENT=es_ES@euro LC_NAME=es_ES@euro cer@Telcontar:~> Of course you do not need to change all variables, just only those you want. Each user has this way full customization, separate from other users. It affects the command line and at least XFCE. > > When I executed "locale" *before* adding such line in .bashrc, it was > reporting two times that variable and giving an error: > > LANG=it_IT.UTF-8 > LC_CTYPE=it_IT.UTF-8, it_IT.UTF-8 > LC_NUMERIC="it_IT.UTF-8" > LC_TIME="it_IT.UTF-8" > LC_COLLATE="it_IT.UTF-8" > LC_MONETARY="it_IT.UTF-8" > LC_MESSAGES="it_IT.UTF-8" > LC_PAPER="it_IT.UTF-8" > LC_NAME="it_IT.UTF-8" > LC_ADDRESS="it_IT.UTF-8" > LC_TELEPHONE="it_IT.UTF-8" > LC_MEASUREMENT="it_IT.UTF-8" > LC_IDENTIFICATION="it_IT.UTF-8" > LC_ALL= I don't see the error listed there. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

1 0

[opensuse-support] How can I find what when wrong: Dependency failed for Hibernate
by Carlos E. R. 28 Feb '19

28 Feb '19

Hi, after recovery from hibernate (which crashes the machine on the second or third hibernation), I get on log: <3.4> 2019-02-28 11:43:18 Telcontar systemd 1 - - Dependency failed for Hibernate. And: Telcontar:~ # systemctl status hibernate.target ● hibernate.target - Hibernate Loaded: loaded (/usr/lib/systemd/system/hibernate.target; static; vendor preset: disabled) Active: inactive (dead) Docs: man:systemd.special(7) Feb 28 11:43:18 Telcontar systemd[1]: hibernate.target: Bound to unit systemd-hibernate.service, but unit isn't active. Feb 28 11:43:18 Telcontar systemd[1]: Dependency failed for Hibernate. Feb 28 11:43:18 Telcontar systemd[1]: hibernate.target: Job hibernate.target/start failed with result 'dependency'. Telcontar:~ # What dependendency? Is there a command that will tell me exactly what dependency failed, and then why? Because as far as I can see, it succeeded. <4.5> 2019-02-28 03:44:41 Telcontar su - - - (to root) cer on pts/19 <10.6> 2019-02-28 03:44:41 Telcontar su - - - pam_unix(su-l:session): session opened for user root by (uid=1000) <10.6> 2019-02-28 03:45:04 Telcontar su - - - pam_unix(su-l:session): session closed for user root <10.3> 2019-02-28 03:52:50 Telcontar su - - - The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control <10.3> 2019-02-28 03:52:50 Telcontar su - - - gkr-pam: couldn't unlock the login keyring. <4.5> 2019-02-28 03:52:50 Telcontar su - - - (to root) cer on pts/33 <10.6> 2019-02-28 03:52:50 Telcontar su - - - pam_unix(su-l:session): session opened for user root by (uid=1000) <4.4> 2019-02-28 03:52:59 Telcontar systemd-logind 1664 - - /etc/systemd/sleep.conf:1: Assignment outside of section. Ignoring. <3.6> 2019-02-28 03:52:59 Telcontar systemd 1 - - Reached target Sleep. <3.6> 2019-02-28 03:52:59 Telcontar systemd 1 - - Starting Hibernate... <3.4> 2019-02-28 03:52:59 Telcontar systemd-sleep 23288 - - /etc/systemd/sleep.conf:1: Assignment outside of section. Ignoring. <0.7> 2019-02-28 03:52:59 Telcontar kernel - - - [55681.307503] PM: Hibernation mode set to 'platform' <3.6> 2019-02-28 03:52:59 Telcontar systemd-sleep 23288 - - INFO: running /usr/lib/systemd/system-sleep/grub2.sleep for hibernate <3.6> 2019-02-28 03:52:59 Telcontar systemd-sleep 23288 - - INFO: Running prepare-grub .. <3.6> 2019-02-28 03:52:59 Telcontar systemd-sleep 23288 - - 2019-02-28 03:52:59+01:00 - Hibernating the system now... <3.4> 2019-02-28 03:52:59 Telcontar systemd-sh - - - Hibernating the system now... <3.6> 2019-02-28 03:52:59 Telcontar systemd-sleep 23288 - - service: no such service upsd.service <3.6> 2019-02-28 03:53:00 Telcontar systemd-sleep 23288 - - running kernel is grub menu entry Main_openSUSE (vmlinuz-4.12.14-lp150.12.48-default) <3.6> 2019-02-28 03:53:00 Telcontar systemd-sleep 23288 - - preparing boot-loader: selecting entry Main_openSUSE, kernel /boot/4.12.14-lp150.12.48-default <3.6> 2019-02-28 03:53:02 Telcontar systemd-sleep 23288 - - running /usr/sbin/grub2-once "Main_openSUSE" <3.6> 2019-02-28 03:53:02 Telcontar systemd-sleep 23288 - - time needed for sync: 1.9 seconds, time needed for grub: 0.2 seconds. <3.6> 2019-02-28 03:53:02 Telcontar systemd-sleep 23288 - - INFO: Done. <3.6> 2019-02-28 03:53:04 Telcontar systemd-sleep 23288 - - Suspending system... <0.6> 2019-02-28 03:53:04 Telcontar kernel - - - [55686.369949] PM: Syncing filesystems ... <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55686.648814] PM: done. <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55686.648816] Freezing user space processes ... (elapsed 0.001 seconds) done. <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55686.650775] OOM killer disabled. <0.7> 2019-02-28 11:41:48 Telcontar kernel - - - [55686.650888] PM: Marking nosave pages: [mem 0x00000000-0x00000fff] <0.7> 2019-02-28 11:41:48 Telcontar kernel - - - [55686.650889] PM: Marking nosave pages: [mem 0x0009f000-0x000fffff] <0.7> 2019-02-28 11:41:48 Telcontar kernel - - - [55686.650892] PM: Marking nosave pages: [mem 0xbff90000-0xffffffff] <0.7> 2019-02-28 11:41:48 Telcontar kernel - - - [55686.651492] PM: Basic memory bitmaps created <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55686.651518] PM: Preallocating image memory... <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55697.732216] usb 6-2: USB disconnect, device number 4 <0.4> 2019-02-28 11:41:48 Telcontar kernel - - - [55701.971713] done (allocated 786298 pages) <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55701.971718] PM: Allocated 3145192 kbytes in 15.31 seconds (205.43 MB/s) <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55701.971719] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. <0.4> 2019-02-28 11:41:48 Telcontar kernel - - - [55701.973662] Suspending console(s) (use no_console_suspend to debug) <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55701.974639] serial 00:02: disabled <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55701.976724] pciehp 0000:00:1c.3:pcie004: Slot(0-2): Card present <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55701.976732] pciehp 0000:00:1c.2:pcie004: Slot(0-1): Card present <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55701.976778] pciehp 0000:00:1c.0:pcie004: Slot(0): Card present <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.180402] PM: freeze of devices complete after 206.728 msecs <0.4> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.180403] PM: secret key is invalid <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.180858] PM: late freeze of devices complete after 0.453 msecs <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.181840] PM: noirq freeze of devices complete after 0.980 msecs <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.182409] ACPI: Preparing to enter system sleep state S4 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.182778] PM: Saving platform NVS memory <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.183006] Disabling non-boot CPUs ... <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.184470] smpboot: CPU 1 is now offline <0.5> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.185141] Broke affinity for irq 19 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.186172] smpboot: CPU 2 is now offline <0.5> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.186962] Broke affinity for irq 19 <0.5> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.186972] Broke affinity for irq 26 <0.5> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.186974] Broke affinity for irq 27 <0.5> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.186977] Broke affinity for irq 30 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.187985] smpboot: CPU 3 is now offline <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.188206] PM: Creating hibernation image: <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.313962] PM: Need to copy 785103 pages <0.7> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.313965] PM: Normal pages needed: 785103 + 1024, available pages: 1311673 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.189515] PM: Restoring platform NVS memory <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.189853] Suspended for 28103.374 seconds <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.189901] Enabling non-boot CPUs ... <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.190004] x86: Booting SMP configuration: <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.190005] smpboot: Booting Node 0 Processor 1 APIC 0x1 <0.4> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.192750] cache: parent cpu1 should not be sleeping <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.193023] CPU1 is up <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.193116] smpboot: Booting Node 0 Processor 2 APIC 0x2 <0.4> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.195898] cache: parent cpu2 should not be sleeping <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.196209] CPU2 is up <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.196265] smpboot: Booting Node 0 Processor 3 APIC 0x3 <0.4> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.199034] cache: parent cpu3 should not be sleeping <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.199446] CPU3 is up <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.204614] ACPI: Waking up from system sleep state S4 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.226137] PM: noirq restore of devices complete after 21.290 msecs <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.226585] PM: early restore of devices complete after 0.423 msecs <0.4> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.329888] usb usb3: root hub lost power or was reset <0.4> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.329893] usb usb4: root hub lost power or was reset <0.4> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.329920] usb usb5: root hub lost power or was reset <0.4> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.329950] usb usb1: root hub lost power or was reset <0.4> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.329984] usb usb6: root hub lost power or was reset <0.4> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.329987] usb usb7: root hub lost power or was reset <0.4> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.330021] usb usb8: root hub lost power or was reset <0.4> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.330078] usb usb2: root hub lost power or was reset <0.7> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.333832] ehci-pci 0000:00:1a.7: cache line size of 32 is not supported <0.7> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.333953] ehci-pci 0000:00:1d.7: cache line size of 32 is not supported <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.334052] pciehp 0000:00:1c.0:pcie004: Timeout on hotplug command 0x1038 (issued 55698572 msec ago) <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.334053] pciehp 0000:00:1c.5:pcie004: Timeout on hotplug command 0x1038 (issued 55698572 msec ago) <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.334065] pciehp 0000:00:1c.4:pcie004: Timeout on hotplug command 0x1038 (issued 55698572 msec ago) <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.334069] pciehp 0000:00:1c.2:pcie004: Timeout on hotplug command 0x1038 (issued 55698572 msec ago) <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.334072] pciehp 0000:00:1c.3:pcie004: Timeout on hotplug command 0x1038 (issued 55698572 msec ago) <0.5> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.340451] sd 8:0:0:0: [sda] Starting disk <0.5> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.340477] sd 8:0:1:0: [sdb] Starting disk <0.5> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.340506] sd 9:0:0:0: [sdc] Starting disk <0.5> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.340529] sd 9:0:1:0: [sdd] Starting disk <0.5> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.340551] sd 10:0:0:0: [sde] Starting disk <0.3> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.450492] snd_hda_intel 0000:03:00.0: CORB reset timeout#1, CORBRP = 0 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.464673] rtc_cmos 00:01: System wakeup disabled by ACPI <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.466135] serial 00:02: activated <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.768226] ata6: SATA link down (SStatus 0 SControl 300) <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.768536] ata5: SATA link down (SStatus 0 SControl 300) <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.776259] ata7: SATA link down (SStatus 0 SControl 300) <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.776297] ata8: SATA link down (SStatus 0 SControl 300) <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.810100] ata11: SATA link up 3.0 Gbps (SStatus 123 SControl 300) <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.810235] ata12: SATA link up 1.5 Gbps (SStatus 113 SControl 300) <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.812580] ata11.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.812582] ata11.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.812629] ata12.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.812631] ata12.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.812633] ata12.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out <0.7> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.812707] ata11.00: ACPI cmd c6/00:01:00:00:00:a0 (SET MULTIPLE MODE) succeeded <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.812709] ata11.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out <0.4> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.815290] ata11.00: supports DRM functions and may not be fully accessible <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.817453] ata12.00: configured for UDMA/133 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.818084] usb 2-5: reset high-speed USB device number 4 using ehci-pci <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.818085] usb 1-2: reset high-speed USB device number 3 using ehci-pci <0.4> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.820008] ata11.00: supports DRM functions and may not be fully accessible <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.821874] ata11.00: configured for UDMA/133 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.847909] r8169 0000:07:00.0 eth1: link down <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.848193] r8169 0000:06:00.0 eth0: link down <0.5> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.906094] firewire_core 0000:08:02.0: rediscovered device fw0 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.954083] usb 3-1: reset low-speed USB device number 2 using uhci_hcd <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.958082] usb 8-2: reset low-speed USB device number 2 using uhci_hcd <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55702.958089] usb 7-2: reset low-speed USB device number 2 using uhci_hcd <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.126123] ata9.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300) <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.126134] ata9.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300) <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.128415] ata9.01: ACPI cmd ef/03:45:00:00:00:b0 (SET FEATURES) filtered out <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.128418] ata9.01: ACPI cmd ef/03:0c:00:00:00:b0 (SET FEATURES) filtered out <0.7> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.128652] ata9.01: ACPI cmd c6/00:10:00:00:00:b0 (SET MULTIPLE MODE) succeeded <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.128655] ata9.01: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.130129] ata10.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300) <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.130141] ata10.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300) <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.132428] ata10.01: ACPI cmd ef/03:45:00:00:00:b0 (SET FEATURES) filtered out <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.132430] ata10.01: ACPI cmd ef/03:0c:00:00:00:b0 (SET FEATURES) filtered out <0.7> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.132632] ata10.01: ACPI cmd c6/00:10:00:00:00:b0 (SET MULTIPLE MODE) succeeded <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.132635] ata10.01: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.133408] ata9.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.133411] ata9.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out <0.7> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.133627] ata9.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) succeeded <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.133629] ata9.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.137381] ata10.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.137383] ata10.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out <0.7> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.137598] ata10.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) succeeded <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.137600] ata10.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.144828] ata10.00: configured for UDMA/133 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.158416] ata9.00: configured for UDMA/133 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.163090] ata9.01: configured for UDMA/133 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.168585] ata10.01: configured for UDMA/133 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55703.270084] usb 2-5.4: reset high-speed USB device number 6 using ehci-pci <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55704.716929] r8169 0000:06:00.0 eth0: link up <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266203] <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266204] floppy driver state <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266204] ------------------- <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266211] now=4308818304 last interrupt=4294893801 diff=13924503 last called handler=reset_interrupt [floppy] <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266212] timeout_message=lock fdc <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266213] last output bytes: <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266214] 8 90 4294893785 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266215] 8 90 4294893785 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266216] 8 80 4294893785 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266216] 8 80 4294893797 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266217] 8 90 4294893797 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266218] 8 90 4294893797 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266219] 8 90 4294893797 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266220] e 80 4294893797 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266221] 13 80 4294893797 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266221] 0 90 4294893797 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266222] 1a 90 4294893797 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266223] 0 90 4294893797 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266224] 12 90 4294893797 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266225] 0 90 4294893797 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266226] 14 90 4294893797 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266227] 18 90 4294893797 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266227] 8 80 4294893801 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266228] 8 80 4294893801 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266229] 8 80 429489380 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266230] 8 80 4294893801 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266231] last result at 4294893801 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266231] last redo_fd_request at 4294893801 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266236] status=0 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266237] fdc_busy=1 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266240] do_floppy=reset_interrupt [floppy] <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266241] cont=ffffffffa0141420 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266242] current_req= (null) <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266243] command_status=-1 <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266243] <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.266246] floppy0: floppy timeout called <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.422500] PM: restore of devices complete after 4092.536 msecs <0.7> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.422855] PM: Image restored successfully. <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.422857] PM: Trampoline freed <0.7> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.422880] PM: Basic memory bitmaps freed <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.422881] OOM killer enabled. <0.6> 2019-02-28 11:41:48 Telcontar kernel - - - [55706.422881] Restarting tasks ... done. <3.6> 2019-02-28 11:41:49 Telcontar systemd-sleep 23288 - - System resumed. <3.4> 2019-02-28 11:41:49 Telcontar rtkit-daemon 9872 - - The canary thread is apparently starving. Taking action. <3.6> 2019-02-28 11:41:49 Telcontar rtkit-daemon 9872 - - Demoting known real-time threads. <3.5> 2019-02-28 11:41:49 Telcontar rtkit-daemon 9872 - - Successfully demoted thread 9876 of process 9870 (/usr/bin/pulseaudio). <3.5> 2019-02-28 11:41:49 Telcontar rtkit-daemon 9872 - - Successfully demoted thread 9875 of process 9870 (/usr/bin/pulseaudio). <3.5> 2019-02-28 11:41:49 Telcontar rtkit-daemon 9872 - - Successfully demoted thread 9870 of process 9870 (/usr/bin/pulseaudio). <3.5> 2019-02-28 11:41:49 Telcontar rtkit-daemon 9872 - - Demoted 3 threads. <3.6> 2019-02-28 11:41:49 Telcontar systemd-sleep 23288 - - INFO: running /usr/lib/systemd/system-sleep/grub2.sleep for hibernate <3.6> 2019-02-28 11:41:49 Telcontar systemd-sleep 23288 - - INFO: Running grub-once-restore .. <3.6> 2019-02-28 11:41:49 Telcontar systemd-sleep 23288 - - 2019-02-28 11:41:49+01:00 - Thawing the system now)... <3.4> 2019-02-28 11:41:49 Telcontar systemd-sh - - - Thawing the system now... <3.6> 2019-02-28 11:41:49 Telcontar systemd-sleep 23288 - - INFO: Done. <3.6> 2019-02-28 11:41:50 Telcontar systemd 1 - - Started Timeline of Snapper Snapshots. <3.6> 2019-02-28 11:41:50 Telcontar systemd-sleep 23288 - - service: no such service upsd.service <3.4> 2019-02-28 11:41:50 Telcontar systemd-sleep 23718 - - /usr/lib/systemd/system-sleep/nut.sh failed with error code 1. <3.6> 2019-02-28 11:41:50 Telcontar dbus-daemon 1543 - - [system] Activating service name='org.opensuse.Snapper' requested by ':1.772' (uid=0 pid=23755 comm="/usr/lib/snapper/systemd-helper --timeline ") (using servicehelper) <3.6> 2019-02-28 11:41:50 Telcontar dbus-daemon 1543 - - [system] Successfully activated service 'org.opensuse.Snapper' <3.6> 2019-02-28 11:41:50 Telcontar systemd-sleep 23288 - - tput: No value for $TERM and no -T specified <3.4> 2019-02-28 11:41:51 Telcontar wickedd 1708 - - route ipv4 0.0.0.0/0 via 192.168.1.1 dev eth0#2 type unicast table main scope universe protocol boot covered by a ipv4:static lease <1.5> 2019-02-28 11:41:51 Telcontar dns-resolver - - - ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... <1.5> 2019-02-28 11:41:51 Telcontar dns-resolver - - - You can find my version in /etc/resolv.conf.netconfig <3.3> 2019-02-28 11:41:51 Telcontar wickedd 1708 - - ni_process_reap: process 23765 has not exited yet; now doing a blocking waitpid() <1.7> 2019-02-28 11:41:51 Telcontar konversation 9946 - - Connection broken with state 5 and error: "The remote host closed the connection" <1.5> 2019-02-28 11:41:51 Telcontar dns-resolver - - - ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... <1.5> 2019-02-28 11:41:51 Telcontar dns-resolver - - - You can find my version in /etc/resolv.conf.netconfig <3.3> 2019-02-28 11:41:51 Telcontar wickedd 1708 - - ni_process_reap: process 23891 has not exited yet; now doing a blocking waitpid() <3.6> 2019-02-28 11:42:18 Telcontar systemd 1 - - Started Leafnode NNTP server (127.0.0.1:40882). <3.6> 2019-02-28 11:42:18 Telcontar systemd 1 - - Started Leafnode NNTP server (127.0.0.1:40880). <3.4> 2019-02-28 11:43:18 Telcontar systemd-sleep 23288 - - system-sleep terminated by signal ALRM. <3.3> 2019-02-28 11:43:18 Telcontar systemd-sleep 23288 - - Execution failed: Protocol error <3.6> 2019-02-28 11:43:18 Telcontar systemd 1 - - Started Hibernate. <3.6> 2019-02-28 11:43:18 Telcontar systemd 1 - - sleep.target: Unit not needed anymore. Stopping. <3.6> 2019-02-28 11:43:18 Telcontar systemd 1 - - Stopped target Sleep. <3.5> 2019-02-28 11:43:18 Telcontar systemd 1 - - hibernate.target: Bound to unit systemd-hibernate.service, but unit isn't active. <3.4> 2019-02-28 11:43:18 Telcontar systemd 1 - - Dependency failed for Hibernate. <4.6> 2019-02-28 11:43:18 Telcontar systemd-logind 1664 - - Operation 'sleep' finished. <3.5> 2019-02-28 11:43:18 Telcontar systemd 1 - - hibernate.target: Job hibernate.target/start failed with result 'dependency'. Maybe this? <3.6> 2019-02-28 03:52:59 Telcontar systemd-sleep 23288 - - service: no such service upsd.service or this? <3.4> 2019-02-28 11:41:50 Telcontar systemd-sleep 23718 - - /usr/lib/systemd/system-sleep/nut.sh failed with error code 1. I also notice this: <4.4> 2019-02-28 03:52:59 Telcontar systemd-logind 1664 - - /etc/systemd/sleep.conf:1: Assignment outside of section. Ignoring. cer@Telcontar:~> cat /etc/systemd/sleep.conf HibernateMode=shutdown cer@Telcontar:~> Changing to: [sleep] HibernateMode=shutdown and will see. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

2 2

[opensuse-support] Need help with a correct and safe setup of postgres10 for akonadi/kontact
by stakanov 28 Feb '19

28 Feb '19

This post has four questions (for parts). Premises: I will refer to following internet pages (1) Demystifying Akonadi (Stephan Kügler) https://vizzzion.org/blog/2010/08/demystifying-akonadi/ (2) Bringing Kmail and PostgreSQL together https://vinzv.de/en/bringing-kmail-and-postgresql-together/ (3) thread on KDE.org Akonadi: change to use Postgres https://mail.kde.org/pipermail/kdepim-users/2017-November/001040.html (4) The opensuse page of postgres https://en.opensuse.org/SDB:PostgreSQL And indications to me stakanov of user knurpth time ago on opensuse(at)opensuseorg Now, my problem. If I well understand, you need to create a user in postgres. This is mentioned in (2) as well as in (4). First question: (4) states that it is safer not to set a password, and (2) does not explain why, but does create a user. At the same time it is advised to create a user without password (4). Now I have set up one machine according to (2), getting a message at the end that the user was set to "trusted" for local use. I think this is intended, but I am not sure. So: is this O.K.? I did not set any password. Second question: In another machine, I did set up postgres96 to use it with kontact/kmail. But I did so using only the second step of (2), that is, I did NOT create a user account. (That was obviously before reading all this). I am using postgres in the meanwhile for two users, and from a purely practical point of view it seams to run well. a) is this setup unsafe? b) if it is, is it advisable to create one user at the time, for every user account using akonadi on the system? c) can I create the user(s) now, and what issues I have to expect (given that data of two users is already there). Third question: according to (1) "Akonadi does not store user data, it caches it" Question: is this true also for the use with postgres10 or 96? If it is, I suppose the storage in /user/home is the same as for mysql? Or is the data itself stored in data_directory --------------------- /var/lib/pgsql/data (1 row) (by using: sudo -u postgres psql -c "show data_directory;") https://stackoverflow.com/questions/1137060/where-does-postgresql-store-the… If it is, I suppose the storage in /user/home is the same as for mysql? Why do I do all this: I would like to point out that the reasons for change to postgres were constant problems with filters and indexes that vanished completely by using postgres. Although I can understand the argument that it is very safe to run mySQL the way it is configured, I have to say, safety has sense if you do not loose data and if usability and stability is granted. Which was not my case, YMMV. So just to make you understand why I did change (and why I am prone to change also every other machine on this behalf). On the other hand it should be as safe as possible. So that raises the next question: Fourth and last question: Is there a Apparmor Profile to be used with postges and what other profiles in Apparmor should I set up (if any needed). Thank you in advance. _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0

[opensuse-support] [TW] Python-sip problem..
by Daniele 25 Feb '19

25 Feb '19

Hello guys, I'm few snapshot behinde (20190126) and I still have python-sip-common and python3-sip from https://download.opensuse.org/repositories/home:/wolfi323:/branches:/KDE:/Q… There was a problem with python-sip and backintime around January. Now, lost of problem "dupping" to current snapshot.. # zypper dup .. Problem: problem with installed package python2-sip-4.19.13-27.1.x86_64 Solution 1: install python2-sip-4.19.14-1.1.x86_64 (with vendor change) obs://build.opensuse.org/home:wolfi323 --> openSUSE Solution 2: keep obsolete python2-sip-4.19.13-27.1.x86_64 Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): 1 Problem: problem with installed package python3-sip-4.19.13-27.1.x86_64 Solution 1: install python3-sip-4.19.14-1.1.x86_64 (with vendor change) obs://build.opensuse.org/home:wolfi323 --> openSUSE Solution 2: keep obsolete python3-sip-4.19.13-27.1.x86_64 Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): 1 .... Problem: python3-sip-4.19.13-27.1.x86_64 requires python3-sip-common = 4.19.13, but this requirement cannot be provided deleted providers: python-sip-common-4.19.13-2.1.x86_64 Solution 1: Following actions will be done: keep obsolete python-sip-common-4.19.13-2.1.x86_64 keep obsolete python3-qt4-4.12.3-1.1.x86_64 Solution 2: deinstallation of python3-qt4-4.12.3-1.1.x86_64 Solution 3: break python3-sip-4.19.13-27.1.x86_64 by ignoring some of its dependencies ... I stop here. Why last problem ? The resolver should see previous steps or I'm wrong ? What to do ? Thanks, Daniele. -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 5

[opensuse-support] Tumbleweed: Problem with name resolution
by Stefan Vater 25 Feb '19

25 Feb '19

Hi, after a large zypper dup last week on Monday, my internet connection refuses to work concerning proper name resolution. This is a problem with wicked and NetworkManager. The problem is that I cannot access websites with my browser, and any program which relies on name resolution cannot get anything from the internet. nslookup works however Also, /etc/resolv.conf is updated correctly and I have also tried "netconfig - f update" without success (although it updates /var/run/netconfig/resolv.conf and with this the symlink). ip addr gives me: 2: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 88:b1:11:ff:f7:6c brd ff:ff:ff:ff:ff:ff inet 192.168.0.6/24 brd 192.168.0.255 scope global dynamic noprefixroute wlp2s0 valid_lft 600509sec preferred_lft 600509sec inet6 fe80::28b1:35d2:e28f:4e6/64 scope link noprefixroute valid_lft forever preferred_lft forever and ip route: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 20600 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.6 metric 600 which looks pretty much the same as on a working machine, connected to the same network. The only difference between the two machines I found so far, is that there are some additional lines in the journal of the affected machine: Feb 25 09:28:44 linux NetworkManager[1277]: <trace> [1551083324.6444] policy: set-hostname: updating hostname (routing and dns) Feb 25 09:28:44 linux NetworkManager[1277]: <trace> [1551083324.6446] hostname: transient hostname retrieval failed Feb 25 09:28:44 linux NetworkManager[1277]: <trace> [1551083324.6447] policy: get-hostname: "linux" Feb 25 09:28:44 linux NetworkManager[1277]: <trace> [1551083324.6448] hostname: transient hostname retrieval failed Feb 25 09:28:44 linux NetworkManager[1277]: <trace> [1551083324.6449] policy: get-hostname: "linux" Feb 25 09:28:44 linux NetworkManager[1277]: <trace> [1551083324.6450] policy: set-hostname: hostname already set to 'linux> The additional lines are tose with "transient hostname retrieval failed" in it. If anyone can help me, that would be appreciated. -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

6 19

[opensuse-support] BTRFS raid 1
by jdd＠dodin.org 25 Feb '19

25 Feb '19

some infos on the subject ** is it possible to make a btrfs add from a running root, then balance to raid 1 no problem (usual caution here) ** once done will it be possible to boot (from uefi) to any partition (sda2 or sdb2)? no my case is probably a bit special; I run a pretty large laptop with dvd writer so I removed the writer and set in place a caddy with (now) a ssd, where I installed Leap 15 nothing to notice, until I run the raid thing. main disk (also a ssd) was at start msdos formatted (due to history reason). I reformatted it as GPT now. at boot: immediately go to uefi firmware without notice. There I finally noticed the computer only sees one disk (main one), do not see the caddy disk. see also that CSM/compatibility mode was up. Removed it and now I boot with no problem my raid1 system I guess only grub on main disk starts and setting raid may have broken the fake gpt msdos entry this computer is said (by the net) to not be able to boot a hard drive from a caddy, so if the main disk fails, I may have to swap it for the caddy one to boot jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0

[opensuse-support] Kodi, Chrome, and Chromecast question
by Carlos E. R. 24 Feb '19

24 Feb '19

Hi, I read about a trick to send content from kodi to a chromecast device (why there is no addon to send directly to chromecast I do not understand). First, in Kodi (obviously using openSUSE), Setup, services, Control, activate "remote control via http". I did this on port 8081 and opened the firewall for it. Then, in another computer (obviously using openSUSE), open Chrome and point it to the computer that has kodi, access the web page there. This works. Finally, in Chrome, activate the item to cast the screen to the Google Chromecast device (this also works, but). The problem is that when I click on the browser to view a movie, it displays on the remote computer, not on the computer that is running Chrome, so that there is no movie to be sent to the chromecast! What am I doing wrong? How do I have the movie displayed on the local computer that runs the web browser? Or, did I understand wrong, and another Chrome also has to run on the remote computer, and set it to cast to the google chromecast? Daft. The web browser says now and then "attempting websockets reconnect" and then "lost websockets recconnect". Apparently, this should use port 9090, which is opened in the kodi machine firewall, so I have no idea what it is and why it fails. Nothing related in the local or remote firewall. The controls on the web browser (bottom status line) to play, pause, fast forward/backward do not work. And the status line says nothing is playing, despite that something is indeed playing in Kodi. On the top-right of the web browser, there are two tabs. One says kodi, another local. If I click kodi, the movie plays on the remote kodi (and pause works, but only pause, no fast forward). If I click local tab instead, it plays on the remote kodi, but beneath the normal screen. Map: computer room sitting room 1) machine running kodi 2) laptop running Chrome. has the media library 3) Chromecast and TV -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

2 2

[opensuse-support] BTRFS raid 1
by jdd＠dodin.org 23 Feb '19

23 Feb '19

Hello, I now have two ssd of around 450Gb each on my PC. I have a root (/) of 100Gb - it's /dev/sda2 I would like to secure this root with an other 100Gb partition in /dev/sdb2 I'm unsure of the best way to do so :-( * make a btrfs raid 1. ** is it possible to make a btrfs add from a running root, or do I need to boot on some recovery system? ** once done will it be possible to boot (from uefi) to any partition (sda2 or sdb2)? in case sda2 fails, do the system boot? from here: https://btrfs.wiki.kernel.org/index.php/Incremental_Backup#Doing_it_by_hand… I don't understand how to recover the backup in case of failure of the main system :-( thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

4 6

[opensuse-support] Grub takes a long time to decrypt /
by Bob Williams 23 Feb '19

23 Feb '19

I have openSUSE Leap 15.0 installed on my laptop, with both / and /home (separate partitions, both on SSDs) encrypted. On booting, grub2 asks for the passphrase to decrypt /, then takes about 10 seconds to offer an OS to load (there's only one). When Leap gets the passphrase to decrypt /home, it immediately proceeds with loading the operating system. Why does grub take so long? It's definitely the rate-limiting step in the whole process. I have tried reducing GRUB_TIMEOUT to 1, and yes, I did run 'grub2-mkconfig -o /boot/grub2/grub.cfg' afterwards. GRUB_DISTRIBUTOR= GRUB_DEFAULT=saved GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=1 GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/mapper/cr_sdb3 splash=silent quiet showopts" GRUB_CMDLINE_LINUX="" Is there anything else I can tweak to reduce the boot time? -- Bob

2 2

[opensuse-support] Default PDF viewer
by Carlos E. R. 22 Feb '19

22 Feb '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have to use the proprietary PDF viewer Foxit (because Evince is not capable of taking snapshots, ie, photos in graphic mode). Foxit has a feature in preferences to "Make Foxit the default PDF viewer". I said no, but both LibreOffice and Midnight commander open PDFs now in Foxit instead of evince. I want to revert this action, but I have no idea how Foxit did the change. Mime type list perhaps? No, the mime.type files have not changed. I'm using XFCE on 15.0 - -- Cheers Carlos E. R. (from 15.0 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXG8BOxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVJqIAoIpAXWjFSpOpP7rps/JJ ms+R7c4TAJ9XxaDbG4tjkT6VBFDIX4rOSwuaoA== =ithO -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

4 4